1 Changes in version 0.4.3.7 - 2020-11-12
2 Tor 0.4.3.7 backports several bugfixes from later releases. It
3 includes a fix for TROVE-2020-005, a security issue that could be
4 used, under certain cases, by an adversary to observe traffic patterns
5 on a limited number of circuits intended for a different relay.
7 Please be aware that support for the 0.4.3.x series will end on 15
8 January 2020. Please upgrade to 0.4.4.x or 0.4.5.x before then, or
9 downgrade to 0.3.5.x, which will be supported until at least 1
12 o Major features (fallback directory list, backport form 0.4.4.3-alpha):
13 - Replace the 148 fallback directories originally included in Tor
14 0.4.1.4-rc (of which around 105 are still functional) with a list
15 of 144 fallbacks generated in July 2020. Closes ticket 40061.
17 o Major bugfixes (security, backport from 0.4.5.1-alpha):
18 - When completing a channel, relays now check more thoroughly to
19 make sure that it matches any pending circuits before attaching
20 those circuits. Previously, address correctness and Ed25519
21 identities were not checked in this case, but only when extending
22 circuits on an existing channel. Fixes bug 40080; bugfix on
23 0.2.7.2-alpha. Resolves TROVE-2020-005.
25 o Major bugfixes (NSS, backport from 0.4.4.3-alpha):
26 - When running with NSS enabled, make sure that NSS knows to expect
27 nonblocking sockets. Previously, we set our TCP sockets as
28 nonblocking, but did not tell NSS, which in turn could lead to
29 unexpected blocking behavior. Fixes bug 40035; bugfix
32 o Minor features (security, backport from 0.4.4.4-rc):
33 - Channels using obsolete versions of the Tor link protocol are no
34 longer allowed to circumvent address-canonicity checks. (This is
35 only a minor issue, since such channels have no way to set ed25519
36 keys, and therefore should always be rejected for circuits that
37 specify ed25519 identities.) Closes ticket 40081.
39 o Minor features (subprotocol versions, backport from 0.4.5.1-alpha):
40 - Tor no longer allows subprotocol versions larger than 63.
41 Previously version numbers up to UINT32_MAX were allowed, which
42 significantly complicated our code. Implements proposal 318;
45 o Minor features (tests, backport from 0.4.4.5):
46 - Our "make check" target now runs the unit tests in 8 parallel
47 chunks. Doing this speeds up hardened CI builds by more than a
48 factor of two. Closes ticket 40098.
50 o Minor features (tests, v2 onion services, backport from 0.4.5.1-alpha):
51 - Fix a rendezvous cache unit test that was triggering an underflow
52 on the global rend cache allocation. Fixes bug 40125; bugfix
54 - Fix another rendezvous cache unit test that was triggering an
55 underflow on the global rend cache allocation. Fixes bug 40126;
56 bugfix on 0.2.8.1-alpha.
58 o Minor bugfixes (correctness, buffers, backport from 0.4.4.4-rc):
59 - Fix a correctness bug that could cause an assertion failure if we
60 ever tried using the buf_move_all() function with an empty input
61 buffer. As far as we know, no released versions of Tor do this.
62 Fixes bug 40076; bugfix on 0.3.3.1-alpha.
64 o Minor bugfixes (logging, backport from 0.4.5.1-alpha):
65 - Remove a debug logging statement that uselessly spammed the logs.
66 Fixes bug 40135; bugfix on 0.3.5.0-alpha.
68 o Minor bugfixes (rate limiting, bridges, pluggable transports, backport from 0.4.4.4-rc):
69 - On a bridge, treat all connections from an ExtORPort as remote by
70 default for the purposes of rate-limiting. Previously, bridges
71 would treat the connection as local unless they explicitly
72 received a "USERADDR" command. ExtORPort connections still count
73 as local if there is a USERADDR command with an explicit local
74 address. Fixes bug 33747; bugfix on 0.2.5.1-alpha.
76 o Minor bugfixes (relay configuration, crash, backport from 0.4.5.1-alpha):
77 - Avoid a fatal assert() when failing to create a listener
78 connection for an address that was in use. Fixes bug 40073; bugfix
81 o Minor bugfixes (relay, usability, backport from 0.4.4.3-alpha):
82 - Adjust the rules for when to warn about having too many
83 connections to other relays. Previously we'd tolerate up to 1.5
84 connections per relay on average. Now we tolerate more connections
85 for directory authorities, and raise the number of total
86 connections we need to see before we warn. Fixes bug 33880; bugfix
89 o Minor bugfixes (tests, 0.4.4.5):
90 - Fix the behavior of the rend_cache/clean_v2_descs_as_dir when run
91 on its own. Previously, it would exit with an error. Fixes bug
92 40099; bugfix on 0.2.8.1-alpha.
94 o Minor bugfixes (v2 onion services, backport from 0.4.5.1-alpha):
95 - For HSFETCH commands on v2 onion services addresses, check the
96 length of bytes decoded, not the base32 length. Fixes bug 34400;
97 bugfix on 0.4.1.1-alpha. Patch by Neel Chauhan.
99 o Minor bugfixes (windows, backport from 0.4.4.4-rc):
100 - Fix a bug that prevented Tor from starting if its log file grew
101 above 2GB. Fixes bug 31036; bugfix on 0.2.1.8-alpha.
103 o Deprecated features (onion service v2, backport form 0.4.4.2-alpha):
104 - Add a deprecation warning for version 2 onion services. Closes
107 o Removed features (backport from 0.4.4.3-alpha):
108 - Our "check-local" test target no longer tries to use the
109 Coccinelle semantic patching tool parse all the C files. While it
110 is a good idea to try to make sure Coccinelle works on our C
111 before we run a Coccinelle patch, doing so on every test run has
112 proven to be disruptive. You can still run this tool manually with
113 "make check-cocci". Closes ticket 40030. ticket 40030.
116 Changes in version 0.4.3.6 - 2020-07-09
117 Tor 0.4.3.6 backports several bugfixes from later releases, including
118 some affecting usability.
120 This release also fixes TROVE-2020-001, a medium-severity denial of
121 service vulnerability affecting all versions of Tor when compiled with
122 the NSS encryption library. (This is not the default configuration.)
123 Using this vulnerability, an attacker could cause an affected Tor
124 instance to crash remotely. This issue is also tracked as CVE-2020-
125 15572. Anybody running a version of Tor built with the NSS library
126 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
129 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
130 - Fix a crash due to an out-of-bound memory access when Tor is
131 compiled with NSS support. Fixes bug 33119; bugfix on
132 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
135 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
136 - Use the correct 64-bit printf format when compiling with MINGW on
137 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
139 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
140 - Resume use of preemptively-built circuits when UseEntryGuards is set
141 to 0. We accidentally disabled this feature with that config
142 setting, leading to slower load times. Fixes bug 34303; bugfix
145 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
146 - Fix a compiler warning on platforms with 32-bit time_t values.
147 Fixes bug 40028; bugfix on 0.3.2.8-rc.
149 o Minor bugfixes (linux seccomp sandbox, nss, backport from 0.4.4.1-alpha):
150 - Fix a startup crash when tor is compiled with --enable-nss and
151 sandbox support is enabled. Fixes bug 34130; bugfix on
152 0.3.5.1-alpha. Patch by Daniel Pinto.
154 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
155 - Downgrade a noisy log message that could occur naturally when
156 receiving an extrainfo document that we no longer want. Fixes bug
157 16016; bugfix on 0.2.6.3-alpha.
159 o Minor bugfixes (manual page, backport from 0.4.4.1-alpha):
160 - Update the man page to reflect that MinUptimeHidServDirectoryV2
161 defaults to 96 hours. Fixes bug 34299; bugfix on 0.2.6.3-alpha.
163 o Minor bugfixes (onion service v3, backport from 0.4.4.1-alpha):
164 - Prevent an assert() that would occur when cleaning the client
165 descriptor cache, and attempting to close circuits for a non-
166 decrypted descriptor (lacking client authorization). Fixes bug
167 33458; bugfix on 0.4.2.1-alpha.
169 o Minor bugfixes (portability, backport from 0.4.4.1-alpha):
170 - Fix a portability error in the configure script, where we were
171 using "==" instead of "=". Fixes bug 34233; bugfix on 0.4.3.5.
173 o Minor bugfixes (relays, backport from 0.4.4.1-alpha):
174 - Stop advertising incorrect IPv6 ORPorts in relay and bridge
175 descriptors, when the IPv6 port was configured as "auto". Fixes
176 bug 32588; bugfix on 0.2.3.9-alpha.
178 o Documentation (backport from 0.4.4.1-alpha):
179 - Fix several doxygen warnings related to imbalanced groups. Closes
183 Changes in version 0.4.3.5 - 2020-05-15
184 Tor 0.4.3.5 is the first stable release in the 0.4.3.x series. This
185 series adds support for building without relay code enabled, and
186 implements functionality needed for OnionBalance with v3 onion
187 services. It includes significant refactoring of our configuration and
188 controller functionality, and fixes numerous smaller bugs and
191 Per our support policy, we support each stable release series for nine
192 months after its first stable release, or three months after the first
193 stable release of the next series: whichever is longer. This means
194 that 0.4.3.x will be supported until around February 2021--later, if
195 0.4.4.x is later than anticipated.
197 Note also that support for 0.4.1.x is about to end on May 20 of this
198 year; 0.4.2.x will be supported until September 15. We still plan to
199 continue supporting 0.3.5.x, our long-term stable series, until
202 Below are the changes since 0.4.3.4-rc. For a complete list of changes
203 since 0.4.2.6, see the ReleaseNotes file.
205 o Minor bugfixes (compiler compatibility):
206 - Avoid compiler warnings from Clang 10 related to the use of GCC-
207 style "/* falls through */" comments. Both Clang and GCC allow
208 __attribute__((fallthrough)) instead, so that's what we're using
209 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
210 - Fix compilation warnings with GCC 10.0.1. Fixes bug 34077; bugfix
213 o Minor bugfixes (logging):
214 - Stop truncating IPv6 addresses and ports in channel and connection
215 logs. Fixes bug 33918; bugfix on 0.2.4.4-alpha.
216 - Fix a logic error in a log message about whether an address was
217 invalid. Previously, the code would never report that onion
218 addresses were onion addresses. Fixes bug 34131; bugfix
222 Changes in version 0.4.3.4-rc - 2020-04-13
223 Tor 0.4.3.4-rc is the first release candidate in its series. It fixes
224 several bugs from earlier versions, including one affecting DoS
225 defenses on bridges using pluggable transports.
227 o Major bugfixes (DoS defenses, bridges, pluggable transport):
228 - Fix a bug that was preventing DoS defenses from running on bridges
229 with a pluggable transport. Previously, the DoS subsystem was not
230 given the transport name of the client connection, thus failed to
231 find the GeoIP cache entry for that client address. Fixes bug
232 33491; bugfix on 0.3.3.2-alpha.
234 o Minor feature (sendme, flow control):
235 - Default to sending SENDME version 1 cells. (Clients are already
236 sending these, because of a consensus parameter telling them to do
237 so: this change only affects what clients would do if the
238 consensus didn't contain a recommendation.) Closes ticket 33623.
240 o Minor features (testing):
241 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
242 variable to specify a list of space-separated test cases that
243 should not be executed. We will use this to disable certain tests
244 that are failing on Appveyor because of mismatched OpenSSL
245 libraries. Part of ticket 33643.
247 o Minor bugfixes (--disable-module-relay):
248 - Fix an assertion failure when Tor is built without the relay
249 module, and then invoked with the "User" option. Fixes bug 33668;
250 bugfix on 0.4.3.1-alpha.
252 o Minor bugfixes (--disable-module-relay,--disable-module-dirauth):
253 - Set some output arguments in the relay and dirauth module stubs,
254 to guard against future stub argument handling bugs like 33668.
255 Fixes bug 33674; bugfix on 0.4.3.1-alpha.
257 o Minor bugfixes (build system):
258 - Correctly output the enabled module in the configure summary.
259 Before that, the list shown was just plain wrong. Fixes bug 33646;
260 bugfix on 0.4.3.2-alpha.
262 o Minor bugfixes (client, IPv6):
263 - Stop forcing all non-SocksPorts to prefer IPv6 exit connections.
264 Instead, prefer IPv6 connections by default, but allow users to
265 change their configs using the "NoPreferIPv6" port flag. Fixes bug
266 33608; bugfix on 0.4.3.1-alpha.
267 - Revert PreferIPv6 set by default on the SocksPort because it broke
268 the torsocks use case. Tor doesn't have a way for an application
269 to request the hostname to be resolved for a specific IP version,
270 but torsocks requires that. Up until now, IPv4 was used by default
271 so torsocks is expecting that, and can't handle a possible IPv6
272 being returned. Fixes bug 33804; bugfix on 0.4.3.1-alpha.
274 o Minor bugfixes (key portability):
275 - When reading PEM-encoded key data, tolerate CRLF line-endings even
276 if we are not running on Windows. Previously, non-Windows hosts
277 would reject these line-endings in certain positions, making
278 certain key files hard to move from one host to another. Fixes bug
279 33032; bugfix on 0.3.5.1-alpha.
281 o Minor bugfixes (logging):
282 - Flush stderr, stdout, and file logs during shutdown, if supported
283 by the OS. This change helps make sure that any final logs are
284 recorded. Fixes bug 33087; bugfix on 0.4.1.6.
285 - Stop closing stderr and stdout during shutdown. Closing these file
286 descriptors can hide sanitiser logs. Fixes bug 33087; bugfix
289 o Minor bugfixes (onion services v3):
290 - Relax severity of a log message that can appear naturally when
291 decoding onion service descriptors as a relay. Also add some
292 diagnostics to debug any future bugs in that area. Fixes bug
293 31669; bugfix on 0.3.0.1-alpha.
294 - Block a client-side assertion by disallowing the registration of
295 an x25519 client auth key that's all zeroes. Fixes bug 33545;
296 bugfix on 0.4.3.1-alpha. Based on patch from "cypherpunks".
298 o Code simplification and refactoring:
299 - Disable our coding standards best practices tracker in our git
300 hooks. (0.4.3 branches only.) Closes ticket 33678.
303 - Avoid conflicts between the fake sockets in tor's unit tests, and
304 real file descriptors. Resolves issues running unit tests with
305 GitHub Actions, where the process that embeds or launches the
306 tests has already opened a large number of file descriptors. Fixes
307 bug 33782; bugfix on 0.2.8.1-alpha. Found and fixed by
311 - In our Appveyor Windows CI, copy required DLLs to test and app
312 directories, before running tor's tests. This ensures that tor.exe
313 and test*.exe use the correct version of each DLL. This fix is not
314 required, but we hope it will avoid DLL search issues in future.
315 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
316 - On Appveyor, skip the crypto/openssl_version test, which is
317 failing because of a mismatched library installation. Fix
321 Changes in version 0.4.3.3-alpha - 2020-03-18
322 Tor 0.4.3.3-alpha fixes several bugs in previous releases, including
323 TROVE-2020-002, a major denial-of-service vulnerability that affected
324 all released Tor instances since 0.2.1.5-alpha. Using this
325 vulnerability, an attacker could cause Tor instances to consume a huge
326 amount of CPU, disrupting their operations for several seconds or
327 minutes. This attack could be launched by anybody against a relay, or
328 by a directory cache against any client that had connected to it. The
329 attacker could launch this attack as much as they wanted, thereby
330 disrupting service or creating patterns that could aid in traffic
331 analysis. This issue was found by OSS-Fuzz, and is also tracked
334 We do not have reason to believe that this attack is currently being
335 exploited in the wild, but nonetheless we advise everyone to upgrade
336 as soon as packages are available.
338 o Major bugfixes (security, denial-of-service):
339 - Fix a denial-of-service bug that could be used by anyone to
340 consume a bunch of CPU on any Tor relay or authority, or by
341 directories to consume a bunch of CPU on clients or hidden
342 services. Because of the potential for CPU consumption to
343 introduce observable timing patterns, we are treating this as a
344 high-severity security issue. Fixes bug 33119; bugfix on
345 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
346 as TROVE-2020-002 and CVE-2020-10592.
348 o Major bugfixes (circuit padding, memory leak):
349 - Avoid a remotely triggered memory leak in the case that a circuit
350 padding machine is somehow negotiated twice on the same circuit.
351 Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
352 This is also tracked as TROVE-2020-004 and CVE-2020-10593.
354 o Major bugfixes (directory authority):
355 - Directory authorities will now send a 503 (not enough bandwidth)
356 code to clients when under bandwidth pressure. Known relays and
357 other authorities will always be answered regardless of the
358 bandwidth situation. Fixes bug 33029; bugfix on 0.1.2.5-alpha.
360 o Minor features (diagnostic):
361 - Improve assertions and add some memory-poisoning code to try to
362 track down possible causes of a rare crash (32564) in the EWMA
363 code. Closes ticket 33290.
365 o Minor features (directory authorities):
366 - Directory authorities now reject descriptors from relays running
367 Tor versions from the 0.2.9 and 0.4.0 series. The 0.3.5 series is
368 still allowed. Resolves ticket 32672. Patch by Neel Chauhan.
370 o Minor features (usability):
371 - Include more information when failing to parse a configuration
372 value. This should make it easier to tell what's going wrong when
373 a configuration file doesn't parse. Closes ticket 33460.
375 o Minor bugfix (relay, configuration):
376 - Warn if the ContactInfo field is not set, and tell the relay
377 operator that not having a ContactInfo field set might cause their
378 relay to get rejected in the future. Fixes bug 33361; bugfix
381 o Minor bugfixes (coding best practices checks):
382 - Allow the "practracker" script to read unicode files when using
383 Python 2. We made the script use unicode literals in 0.4.3.1-alpha,
384 but didn't change the codec for opening files. Fixes bug 33374;
385 bugfix on 0.4.3.1-alpha.
387 o Minor bugfixes (continuous integration):
388 - Remove the buggy and unused mirroring job. Fixes bug 33213; bugfix
391 o Minor bugfixes (onion service v3, client):
392 - Remove a BUG() warning that would cause a stack trace if an onion
393 service descriptor was freed while we were waiting for a
394 rendezvous circuit to complete. Fixes bug 28992; bugfix
397 o Minor bugfixes (onion services v3):
398 - Fix an assertion failure that could result from a corrupted
399 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
400 bugfix on 0.3.3.1-alpha. This issue is also tracked
403 o Documentation (manpage):
404 - Alphabetize the Server and Directory server sections of the tor
405 manpage. Also split Statistics options into their own section of
406 the manpage. Closes ticket 33188. Work by Swati Thacker as part of
407 Google Season of Docs.
408 - Document the __OwningControllerProcess torrc option and specify
409 its polling interval. Resolves issue 32971.
411 o Testing (Travis CI):
412 - Remove a redundant distcheck job. Closes ticket 33194.
413 - Sort the Travis jobs in order of speed: putting the slowest jobs
414 first takes full advantage of Travis job concurrency. Closes
416 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
417 previously configured to fast_finish (which requires
418 allow_failure), to speed up the build. Closes ticket 33195.
419 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
420 tool to produce detailed diagnostic output. Closes ticket 32792.
423 Changes in version 0.4.3.2-alpha - 2020-02-10
424 This is the second stable alpha release in the Tor 0.4.3.x series. It
425 fixes several bugs present in the previous alpha release. Anybody
426 running the previous alpha should upgrade, and look for bugs in this
429 o Major bugfixes (onion service client, authorization):
430 - On a NEWNYM signal, purge entries from the ephemeral client
431 authorization cache. The permanent ones are kept. Fixes bug 33139;
432 bugfix on 0.4.3.1-alpha.
434 o Minor features (best practices tracker):
435 - Practracker now supports a --regen-overbroad option to regenerate
436 the exceptions file, but only to revise exceptions to be _less_
437 tolerant of best-practices violations. Closes ticket 32372.
439 o Minor features (continuous integration):
440 - Run Doxygen Makefile target on Travis, so we can learn about
441 regressions in our internal documentation. Closes ticket 32455.
442 - Stop allowing failures on the Travis CI stem tests job. It looks
443 like all the stem hangs we were seeing before are now fixed.
446 o Minor bugfixes (build system):
447 - Revise configure options that were either missing or incorrect in
448 the configure summary. Fixes bug 32230; bugfix on 0.4.3.1-alpha.
450 o Minor bugfixes (controller protocol):
451 - Fix a memory leak introduced by refactoring of control reply
452 formatting code. Fixes bug 33039; bugfix on 0.4.3.1-alpha.
453 - Fix a memory leak in GETINFO responses. Fixes bug 33103; bugfix
455 - When receiving "ACTIVE" or "DORMANT" signals on the control port,
456 report them as SIGNAL events. Previously we would log a bug
457 warning. Fixes bug 33104; bugfix on 0.4.0.1-alpha.
459 o Minor bugfixes (logging):
460 - If we encounter a bug when flushing a buffer to a TLS connection,
461 only log the bug once per invocation of the Tor process.
462 Previously we would log with every occurrence, which could cause
463 us to run out of disk space. Fixes bug 33093; bugfix
465 - When logging a bug, do not say "Future instances of this warning
466 will be silenced" unless we are actually going to silence them.
467 Previously we would say this whenever a BUG() check failed in the
468 code. Fixes bug 33095; bugfix on 0.4.1.1-alpha.
470 o Minor bugfixes (onion service v2):
471 - Move a series of v2 onion service warnings to protocol-warning
472 level because they can all be triggered remotely by a malformed
473 request. Fixes bug 32706; bugfix on 0.1.1.14-alpha.
475 o Minor bugfixes (onion service v3, client authorization):
476 - When removing client authorization credentials using the control
477 port, also remove the associated descriptor, so the onion service
478 can no longer be contacted. Fixes bug 33148; bugfix
481 o Minor bugfixes (pluggable transports):
482 - When receiving a message on standard error from a pluggable
483 transport, log it at info level, rather than as a warning. Fixes
484 bug 33005; bugfix on 0.4.0.1-alpha.
486 o Minor bugfixes (rust, build):
487 - Fix a syntax warning given by newer versions of Rust that was
488 creating problems for our continuous integration. Fixes bug 33212;
489 bugfix on 0.3.5.1-alpha.
491 o Minor bugfixes (TLS bug handling):
492 - When encountering a bug in buf_read_from_tls(), return a "MISC"
493 error code rather than "WANTWRITE". This change might help avoid
494 some CPU-wasting loops if the bug is ever triggered. Bug reported
495 by opara. Fixes bug 32673; bugfix on 0.3.0.4-alpha.
497 o Code simplification and refactoring (mainloop):
498 - Simplify the ip_address_changed() function by removing redundant
499 checks. Closes ticket 33091.
501 o Documentation (manpage):
502 - Split "Circuit Timeout" options and "Node Selection" options into
503 their own sections of the tor manpage. Closes tickets 32928 and
504 32929. Work by Swati Thacker as part of Google Season of Docs.
507 Changes in version 0.4.2.6 - 2020-01-30
508 This is the second stable release in the 0.4.2.x series. It backports
509 several bugfixes from 0.4.3.1-alpha, including some that had affected
510 the Linux seccomp2 sandbox or Windows services. If you're running with
511 one of those configurations, you'll probably want to upgrade;
512 otherwise, you should be fine with 0.4.2.5.
514 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
515 - Correct how we use libseccomp. Particularly, stop assuming that
516 rules are applied in a particular order or that more rules are
517 processed after the first match. Neither is the case! In
518 libseccomp <2.4.0 this led to some rules having no effect.
519 libseccomp 2.4.0 changed how rules are generated, leading to a
520 different ordering, which in turn led to a fatal crash during
521 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
523 - Fix crash when reloading logging configuration while the
524 experimental sandbox is enabled. Fixes bug 32841; bugfix on
525 0.4.1.7. Patch by Peter Gerber.
527 o Minor bugfixes (correctness checks, backport from 0.4.3.1-alpha):
528 - Use GCC/Clang's printf-checking feature to make sure that
529 tor_assertf() arguments are correctly typed. Fixes bug 32765;
530 bugfix on 0.4.1.1-alpha.
532 o Minor bugfixes (logging, crash, backport from 0.4.3.1-alpha):
533 - Avoid a possible crash when trying to log a (fatal) assertion
534 failure about mismatched magic numbers in configuration objects.
535 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
537 o Minor bugfixes (testing, backport from 0.4.3.1-alpha):
538 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
539 test_practracker.sh script. Doing so caused a test failure. Fixes
540 bug 32705; bugfix on 0.4.2.1-alpha.
541 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
542 skipping practracker checks. Fixes bug 32705; bugfix
545 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
546 - Initialize the publish/subscribe system when running as a windows
547 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
549 o Testing (backport from 0.4.3.1-alpha):
550 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
551 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
552 fix the sandbox errors in 32722. Closes ticket 32240.
553 - Re-enable the Travis CI macOS Chutney build, but don't let it
554 prevent the Travis job from finishing. (The Travis macOS jobs are
555 slow, so we don't want to have it delay the whole CI process.)
558 o Testing (continuous integration, backport from 0.4.3.1-alpha):
559 - Use zstd in our Travis Linux builds. Closes ticket 32242.
562 Changes in version 0.4.1.8 - 2020-01-30
563 This release backports several bugfixes from later release series,
564 including some that had affected the Linux seccomp2 sandbox or Windows
565 services. If you're running with one of those configurations, you'll
566 probably want to upgrade; otherwise, you should be fine with your
567 current version of 0.4.1.x.
569 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
570 - Correct how we use libseccomp. Particularly, stop assuming that
571 rules are applied in a particular order or that more rules are
572 processed after the first match. Neither is the case! In
573 libseccomp <2.4.0 this led to some rules having no effect.
574 libseccomp 2.4.0 changed how rules are generated, leading to a
575 different ordering, which in turn led to a fatal crash during
576 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
578 - Fix crash when reloading logging configuration while the
579 experimental sandbox is enabled. Fixes bug 32841; bugfix on
580 0.4.1.7. Patch by Peter Gerber.
582 o Minor bugfixes (crash, backport form 0.4.2.4-rc):
583 - When running Tor with an option like --verify-config or
584 --dump-config that does not start the event loop, avoid crashing
585 if we try to exit early because of an error. Fixes bug 32407;
586 bugfix on 0.3.3.1-alpha.
588 o Minor bugfixes (windows service, backport from 0.4.3.1-alpha):
589 - Initialize the publish/subscribe system when running as a windows
590 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
592 o Testing (backport from 0.4.3.1-alpha):
593 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
594 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
595 fix the sandbox errors in 32722. Closes ticket 32240.
596 - Re-enable the Travis CI macOS Chutney build, but don't let it
597 prevent the Travis job from finishing. (The Travis macOS jobs are
598 slow, so we don't want to have it delay the whole CI process.)
601 o Testing (continuous integration, backport from 0.4.3.1-alpha):
602 - Use zstd in our Travis Linux builds. Closes ticket 32242.
605 Changes in version 0.4.3.1-alpha - 2020-01-22
606 This is the first alpha release in the 0.4.3.x series. It includes
607 improved support for application integration of onion services, support
608 for building in a client-only mode, and newly improved internal
609 documentation (online at https://src-ref.docs.torproject.org/tor/). It
610 also has numerous other small bugfixes and features, as well as
611 improvements to our code's internal organization that should help us
612 write better code in the future.
614 o New system requirements:
615 - When building Tor, you now need to have Python 3 in order to run
616 the integration tests. (Python 2 is officially unsupported
617 upstream, as of 1 Jan 2020.) Closes ticket 32608.
619 o Major features (build system):
620 - The relay code can now be disabled using the --disable-module-relay
621 configure option. When this option is set, we also disable the
622 dirauth module. Closes ticket 32123.
623 - When Tor is compiled --disable-module-relay, we also omit the code
624 used to act as a directory cache. Closes ticket 32487.
626 o Major features (directory authority, ed25519):
627 - Add support for banning a relay's ed25519 keys in the approved-
628 routers file. This will help us migrate away from RSA keys in the
629 future. Previously, only RSA keys could be banned in approved-
630 routers. Resolves ticket 22029. Patch by Neel Chauhan.
632 o Major features (onion service, controller):
633 - New control port commands to manage client-side onion service
634 authorization credentials. The ONION_CLIENT_AUTH_ADD command adds
635 a credential, ONION_CLIENT_AUTH_REMOVE deletes a credential, and
636 ONION_CLIENT_AUTH_VIEW lists the credentials. Closes ticket 30381.
638 o Major features (onion service, SOCKS5):
639 - Introduce a new SocksPort flag, ExtendedErrors, to support more
640 detailed error codes in information for applications that support
641 them. Closes ticket 30382; implements proposal 304.
643 o Major features (proxy):
644 - In addition to its current supported proxy types (HTTP CONNECT,
645 SOCKS4, and SOCKS5), Tor can now make its OR connections through a
646 HAProxy server. A new torrc option was added to specify the
647 address/port of the server: TCPProxy <protocol> <host>:<port>.
648 Currently the only supported protocol for the option is haproxy.
649 Closes ticket 31518. Patch done by Suphanat Chunhapanya (haxxpop).
651 o Major bugfixes (linux seccomp sandbox):
652 - Correct how we use libseccomp. Particularly, stop assuming that
653 rules are applied in a particular order or that more rules are
654 processed after the first match. Neither is the case! In
655 libseccomp <2.4.0 this led to some rules having no effect.
656 libseccomp 2.4.0 changed how rules are generated, leading to a
657 different ordering, which in turn led to a fatal crash during
658 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
660 - Fix crash when reloading logging configuration while the
661 experimental sandbox is enabled. Fixes bug 32841; bugfix on
662 0.4.1.7. Patch by Peter Gerber.
664 o Major bugfixes (networking):
665 - Correctly handle IPv6 addresses in SOCKS5 RESOLVE_PTR requests,
666 and accept strings as well as binary addresses. Fixes bug 32315;
667 bugfix on 0.3.5.1-alpha.
669 o Major bugfixes (onion service):
670 - Report HS circuit failure back into the HS subsystem so we take
671 appropriate action with regards to the client introduction point
672 failure cache. This improves reachability of onion services, since
673 now clients notice failing introduction circuits properly. Fixes
674 bug 32020; bugfix on 0.3.2.1-alpha.
676 o Minor feature (configure, build system):
677 - Output a list of enabled/disabled features at the end of the
678 configure process in a pleasing way. Closes ticket 31373.
680 o Minor feature (heartbeat, onion service):
681 - Add the DoS INTRODUCE2 defenses counter to the heartbeat DoS
682 message. Closes ticket 31371.
684 o Minor features (configuration validation):
685 - Configuration validation can now be done by per-module callbacks,
686 rather than a global validation function. This will let us reduce
687 the size of config.c and some of its more cumbersome functions.
690 o Minor features (configuration):
691 - If a configured hardware crypto accelerator in AccelName is
692 prefixed with "!", Tor now exits when it cannot be found. Closes
694 - We now use flag-driven logic to warn about obsolete configuration
695 fields, so that we can include their names. In 0.4.2, we used a
696 special type, which prevented us from generating good warnings.
697 Implements ticket 32404.
699 o Minor features (controller):
700 - Add stream isolation data to STREAM event. Closes ticket 19859.
701 - Implement a new GETINFO command to fetch microdescriptor
702 consensus. Closes ticket 31684.
704 o Minor features (debugging, directory system):
705 - Don't crash when we find a non-guard with a guard-fraction value
706 set. Instead, log a bug warning, in an attempt to figure out how
707 this happened. Diagnostic for ticket 32868.
709 o Minor features (defense in depth):
710 - Add additional checks around tor_vasprintf() usage, in case the
711 function returns an error. Patch by Tobias Stoeckmann. Fixes
714 o Minor features (developer tooling):
715 - Remove the 0.2.9.x series branches from git scripts (git-merge-
716 forward.sh, git-pull-all.sh, git-push-all.sh, git-setup-dirs.sh).
719 o Minor features (developer tools):
720 - Add a check_cocci_parse.sh script that checks that new code is
721 parseable by Coccinelle. Add an exceptions file for unparseable
722 files, and run the script from travis CI. Closes ticket 31919.
723 - Call the check_cocci_parse.sh script from a 'check-cocci' Makefile
724 target. Closes ticket 31919.
725 - Add a rename_c_identifiers.py tool to rename a bunch of C
726 identifiers at once, and generate a well-formed commit message
727 describing the change. This should help with refactoring. Closes
729 - Add some scripts in "scripts/coccinelle" to invoke the Coccinelle
730 semantic patching tool with the correct flags. These flags are
731 fairly easy to forget, and these scripts should help us use
732 Coccinelle more effectively in the future. Closes ticket 31705.
734 o Minor features (Doxygen):
735 - Update Doxygen configuration file to a more recent template (from
736 1.8.15). Closes ticket 32110.
737 - "make doxygen" now works with out-of-tree builds. Closes
739 - Make sure that doxygen outputs documentation for all of our C
740 files. Previously, some were missing @file declarations, causing
741 them to be ignored. Closes ticket 32307.
742 - Our "make doxygen" target now respects --enable-fatal-warnings by
743 default, and does not warn about items that are missing
744 documentation. To warn about missing documentation, run configure
745 with the "--enable-missing-doc-warnings" flag: doing so suspends
746 fatal warnings for doxygen. Closes ticket 32385.
748 o Minor features (git scripts):
749 - Add TOR_EXTRA_CLONE_ARGS to git-setup-dirs.sh for git clone
750 customisation. Closes ticket 32347.
751 - Add git-setup-dirs.sh, which sets up an upstream git repository
752 and worktrees for tor maintainers. Closes ticket 29603.
753 - Add TOR_EXTRA_REMOTE_* to git-setup-dirs.sh for a custom extra
754 remote. Closes ticket 32347.
755 - Call the check_cocci_parse.sh script from the git commit and push
756 hooks. Closes ticket 31919.
757 - Make git-push-all.sh skip unchanged branches when pushing to
758 upstream. The script already skipped unchanged test branches.
760 - Make git-setup-dirs.sh create a master symlink in the worktree
761 directory. Closes ticket 32347.
762 - Skip unmodified source files when doing some existing git hook
763 checks. Related to ticket 31919.
765 o Minor features (IPv6, client):
766 - Make Tor clients tell dual-stack exits that they prefer IPv6
767 connections. This change is equivalent to setting the PreferIPv6
768 flag on SOCKSPorts (and most other listener ports). Tor Browser
769 has been setting this flag for some time, and we want to remove a
770 client distinguisher at exits. Closes ticket 32637.
772 o Minor features (portability, android):
773 - When building for Android, disable some tests that depend on $HOME
774 and/or pwdb, which Android doesn't have. Closes ticket 32825.
775 Patch from Hans-Christoph Steiner.
777 o Minor features (relay modularity):
778 - Split the relay and server pluggable transport config code into
779 separate files in the relay module. Disable this code when the
780 relay module is disabled. Closes part of ticket 32213.
781 - When the relay module is disabled, reject attempts to set the
782 ORPort, DirPort, DirCache, BridgeRelay, ExtORPort, or
783 ServerTransport* options, rather than ignoring the values of these
784 options. Closes part of ticket 32213.
786 o Minor features (relay):
787 - When the relay module is disabled, change the default config so
788 that DirCache is 0, and ClientOnly is 1. Closes ticket 32410.
790 o Minor features (release tools):
791 - Port our ChangeLog formatting and sorting tools to Python 3.
794 o Minor features (testing):
795 - Detect some common failure cases for test_parseconf.sh in
796 src/test/conf_failures. Closes ticket 32451.
797 - Allow test_parseconf.sh to test expected log outputs for successful
798 configs, as well as failed configs. Closes ticket 32451.
799 - The test_parseconf.sh script now supports result variants for any
800 combination of the optional libraries lzma, nss, and zstd. Closes
803 o Minor features (tests, Android):
804 - When running the unit tests on Android, create temporary files in
805 a subdirectory of /data/local/tmp. Closes ticket 32172. Based on a
806 patch from Hans-Christoph Steiner.
808 o Minor bugfixes (bridges):
809 - Lowercase the configured value of BridgeDistribution before adding
810 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
812 o Minor bugfixes (build system):
813 - Fix "make autostyle" for out-of-tree builds. Fixes bug 32370;
814 bugfix on 0.4.1.2-alpha.
816 o Minor bugfixes (configuration handling):
817 - Make control_event_conf_changed() take in a config_line_t instead
818 of a smartlist of alternating key/value entries. Fixes bug 31531;
819 bugfix on 0.2.3.3-alpha. Patch by Neel Chauhan.
821 o Minor bugfixes (configuration):
822 - Check for multiplication overflow when parsing memory units inside
823 configuration. Fixes bug 30920; bugfix on 0.0.9rc1.
824 - When dumping the configuration, stop adding a trailing space after
825 the option name when there is no option value. This issue only
826 affects options that accept an empty value or list. (Most options
827 reject empty values, or delete the entire line from the dumped
828 options.) Fixes bug 32352; bugfix on 0.0.9pre6.
829 - Avoid changing the user's value of HardwareAccel as stored by
830 SAVECONF, when AccelName is set but HardwareAccel is not. Fixes
831 bug 32382; bugfix on 0.2.2.1-alpha.
832 - When creating a KeyDirectory with the same location as the
833 DataDirectory (not recommended), respect the DataDirectory's
834 group-readable setting if one has not been set for the
835 KeyDirectory. Fixes bug 27992; bugfix on 0.3.3.1-alpha.
837 o Minor bugfixes (controller):
838 - In routerstatus_has_changed(), check all the fields that are
839 output over the control port. Fixes bug 20218; bugfix
842 o Minor bugfixes (correctness checks):
843 - Use GCC/Clang's printf-checking feature to make sure that
844 tor_assertf() arguments are correctly typed. Fixes bug 32765;
845 bugfix on 0.4.1.1-alpha.
847 o Minor bugfixes (developer tools):
848 - Allow paths starting with ./ in scripts/add_c_file.py. Fixes bug
849 31336; bugfix on 0.4.1.2-alpha.
851 o Minor bugfixes (dirauth module):
852 - Split the dirauth config code into a separate file in the dirauth
853 module. Disable this code when the dirauth module is disabled.
855 - When the dirauth module is disabled, reject attempts to set the
856 AuthoritativeDir option, rather than ignoring the value of the
857 option. Fixes bug 32213; bugfix on 0.3.4.1-alpha.
859 o Minor bugfixes (embedded Tor):
860 - When starting Tor any time after the first time in a process,
861 register the thread in which it is running as the main thread.
862 Previously, we only did this on Windows, which could lead to bugs
863 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
866 o Minor bugfixes (git scripts):
867 - Avoid sleeping before the last push in git-push-all.sh. Closes
869 - Forward all unrecognised arguments in git-push-all.sh to git push.
872 o Minor bugfixes (hidden service v3):
873 - Do not rely on a "circuit established" flag for intro circuits but
874 instead always query the HS circuit map. This is to avoid sync
875 issue with that flag and the map. Fixes bug 32094; bugfix
878 o Minor bugfixes (logging, crash):
879 - Avoid a possible crash when trying to log a (fatal) assertion
880 failure about mismatched magic numbers in configuration objects.
881 Fixes bug 32771; bugfix on 0.4.2.1-alpha.
883 o Minor bugfixes (onion service v2):
884 - When sending the INTRO cell for a v2 Onion Service, look at the
885 failure cache alongside timeout values to check if the intro point
886 is marked as failed. Previously, we only looked at the relay
887 timeout values. Fixes bug 25568; bugfix on 0.2.7.3-rc. Patch by
890 o Minor bugfixes (onion services v3, client):
891 - Properly handle the client rendezvous circuit timeout. Previously
892 Tor would sometimes timeout a rendezvous circuit awaiting the
893 introduction ACK, and find itself unable to re-establish all
894 circuits because the rendezvous circuit timed out too early. Fixes
895 bug 32021; bugfix on 0.3.2.1-alpha.
897 o Minor bugfixes (onion services):
898 - In cancel_descriptor_fetches(), use
899 connection_list_by_type_purpose() instead of
900 connection_list_by_type_state(). Fixes bug 32639; bugfix on
901 0.3.2.1-alpha. Patch by Neel Chauhan.
903 o Minor bugfixes (scripts):
904 - Fix update_versions.py for out-of-tree builds. Fixes bug 32371;
905 bugfix on 0.4.0.1-alpha.
907 o Minor bugfixes (test):
908 - Use the same code to find the tor binary in all of our test
909 scripts. This change makes sure we are always using the coverage
910 binary when coverage is enabled. Fixes bug 32368; bugfix
913 o Minor bugfixes (testing):
914 - Stop ignoring "tor --dump-config" errors in test_parseconf.sh.
915 Fixes bug 32468; bugfix on 0.4.2.1-alpha.
916 - When TOR_DISABLE_PRACTRACKER is set, do not apply it to the
917 test_practracker.sh script. Doing so caused a test failure. Fixes
918 bug 32705; bugfix on 0.4.2.1-alpha.
919 - When TOR_DISABLE_PRACTRACKER is set, log a notice to stderr when
920 skipping practracker checks. Fixes bug 32705; bugfix
923 o Minor bugfixes (tests):
924 - Our option-validation tests no longer depend on specially
925 configured non-default, non-passing sets of options. Previously,
926 the tests had been written to assume that options would _not_ be
927 set to their defaults, which led to needless complexity and
928 verbosity. Fixes bug 32175; bugfix on 0.2.8.1-alpha.
930 o Minor bugfixes (windows service):
931 - Initialize the publish/subscribe system when running as a windows
932 service. Fixes bug 32778; bugfix on 0.4.1.1-alpha.
934 o Deprecated features:
935 - Deprecate the ClientAutoIPv6ORPort option. This option was not
936 true "Happy Eyeballs", and often failed on connections that
937 weren't reliably dual-stack. Closes ticket 32942. Patch by
941 - Provide a quickstart guide for a Circuit Padding Framework, and
942 documentation for researchers to implement and study circuit
943 padding machines. Closes ticket 28804.
944 - Add documentation in 'HelpfulTools.md' to describe how to build a
945 tag file. Closes ticket 32779.
946 - Create a high-level description of the long-term software
947 architecture goals. Closes ticket 32206.
948 - Describe the --dump-config command in the manual page. Closes
950 - Unite coding advice from this_not_that.md in torguts repo into our
951 coding standards document. Resolves ticket 31853.
954 - Our Doxygen configuration no longer generates LaTeX output. The
955 reference manual produced by doing this was over 4000 pages long,
956 and generally unusable. Closes ticket 32099.
957 - The option "TestingEstimatedDescriptorPropagationTime" is now
958 marked as obsolete. It has had no effect since 0.3.0.7, when
959 clients stopped rejecting consensuses "from the future". Closes
961 - We no longer support consensus methods before method 28; these
962 methods were only used by authorities running versions of Tor that
963 are now at end-of-life. In effect, this means that clients,
964 relays, and authorities now assume that authorities will be
965 running version 0.3.5.x or later. Closes ticket 32695.
968 - Add more test cases for tor's UTF-8 validation function. Also,
969 check the arguments passed to the function for consistency. Closes
971 - Improve test coverage for relay and dirauth config code, focusing
972 on option validation and normalization. Closes ticket 32213.
973 - Improve the consistency of test_parseconf.sh output, and run all
974 the tests, even if one fails. Closes ticket 32213.
975 - Re-enable the Travis CI macOS Chutney build, but don't let it
976 prevent the Travis job from finishing. (The Travis macOS jobs are
977 slow, so we don't want to have it delay the whole CI process.)
979 - Run the practracker unit tests in the pre-commit git hook. Closes
981 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
982 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
983 fix the sandbox errors in 32722. Closes ticket 32240.
985 o Code simplification and refactoring (channel):
986 - Channel layer had a variable length cell handler that was not used
987 and thus removed. Closes ticket 32892.
989 o Code simplification and refactoring (configuration):
990 - Immutability is now implemented as a flag on individual
991 configuration options rather than as part of the option-transition
992 checking code. Closes ticket 32344.
993 - Instead of keeping a list of configuration options to check for
994 relative paths, check all the options whose type is "FILENAME".
995 Solves part of ticket 32339.
996 - Our default log (which ordinarily sends NOTICE-level messages to
997 standard output) is now handled in a more logical manner.
998 Previously, we replaced the configured log options if they were
999 empty. Now, we interpret an empty set of log options as meaning
1000 "use the default log". Closes ticket 31999.
1001 - Remove some unused arguments from the options_validate() function,
1002 to simplify our code and tests. Closes ticket 32187.
1003 - Simplify the options_validate() code so that it looks at the
1004 default options directly, rather than taking default options as an
1005 argument. This change lets us simplify its interface. Closes
1007 - Use our new configuration architecture to move most authority-
1008 related options to the directory authority module. Closes
1010 - When parsing the command line, handle options that determine our
1011 "quiet level" and our mode of operation (e.g., --dump-config and
1012 so on) all in one table. Closes ticket 32003.
1014 o Code simplification and refactoring (controller):
1015 - Create a new abstraction for formatting control protocol reply
1016 lines based on key-value pairs. Refactor some existing control
1017 protocol code to take advantage of this. Closes ticket 30984.
1018 - Create a helper function that can fetch network status or
1019 microdesc consensuses. Closes ticket 31684.
1021 o Code simplification and refactoring (dirauth modularization):
1022 - Remove the last remaining HAVE_MODULE_DIRAUTH inside a function.
1023 Closes ticket 32163.
1024 - Replace some confusing identifiers in process_descs.c. Closes
1026 - Simplify some relay and dirauth config code. Closes ticket 32213.
1028 o Code simplification and refactoring (misc):
1029 - Make all the structs we declare follow the same naming convention
1030 of ending with "_t". Closes ticket 32415.
1031 - Move and rename some configuration-related code for clarity.
1032 Closes ticket 32304.
1033 - Our include.am files are now broken up by subdirectory.
1034 Previously, src/core/include.am covered all of the subdirectories
1035 in "core", "feature", and "app". Closes ticket 32137.
1036 - Remove underused NS*() macros from test code: they make our tests
1037 more confusing, especially for code-formatting tools. Closes
1040 o Code simplification and refactoring (relay modularization):
1041 - Disable relay_periodic when the relay module is disabled. Closes
1043 - Disable relay_sys when the relay module is disabled. Closes
1046 o Code simplification and refactoring (tool support):
1047 - Add numerous missing dependencies to our include files, so that
1048 they can be included in different reasonable orders and still
1049 compile. Addresses part of ticket 32764.
1050 - Fix some parts of our code that were difficult for Coccinelle to
1051 parse. Related to ticket 31705.
1052 - Fix some small issues in our code that prevented automatic
1053 formatting tools from working. Addresses part of ticket 32764.
1055 o Documentation (manpage):
1056 - Alphabetize the Client Options section of the tor manpage. Closes
1058 - Alphabetize the General Options section of the tor manpage. Closes
1060 - In the tor(1) manpage, reword and improve formatting of the
1061 COMMAND-LINE OPTIONS and DESCRIPTION sections. Closes ticket
1062 32277. Based on work by Swati Thacker as part of Google Season
1064 - In the tor(1) manpage, reword and improve formatting of the FILES,
1065 SEE ALSO, and BUGS sections. Closes ticket 32176. Based on work by
1066 Swati Thacker as part of Google Season of Docs.
1068 o Testing (circuit, EWMA):
1069 - Add unit tests for circuitmux and EWMA subsystems. Closes
1072 o Testing (continuous integration):
1073 - Use zstd in our Travis Linux builds. Closes ticket 32242.
1076 Changes in version 0.4.2.5 - 2019-12-09
1077 This is the first stable release in the 0.4.2.x series. This series
1078 improves reliability and stability, and includes several stability and
1079 correctness improvements for onion services. It also fixes many smaller
1080 bugs present in previous series.
1082 Per our support policy, we will support the 0.4.2.x series for nine
1083 months, or until three months after the release of a stable 0.4.3.x:
1084 whichever is longer. If you need longer-term support, please stick
1085 with 0.3.5.x, which will we plan to support until Feb 2022.
1087 Per our support policy, we will support the 0.4.2.x series for nine
1088 months, or until three months after the release of a stable 0.4.3.x:
1089 whichever is longer. If you need longer-term support, please stick
1090 with 0.3.5.x, which will we plan to support until Feb 2022.
1092 Below are the changes since 0.4.1.4-rc. For a complete list of changes
1093 since 0.4.1.5, see the ReleaseNotes file.
1095 o Minor features (geoip):
1096 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1097 Country database. Closes ticket 32685.
1100 - Require C99 standards-conforming code in Travis CI, but allow GNU
1101 gcc extensions. Also activates clang's -Wtypedef-redefinition
1102 warnings. Build some jobs with -std=gnu99, and some jobs without.
1103 Closes ticket 32500.
1106 Changes in version 0.4.1.7 - 2019-12-09
1107 This release backports several bugfixes to improve stability and
1108 correctness. Anyone experiencing build problems or crashes with 0.4.1.6,
1109 including all relays relying on AccountingMax, should upgrade.
1111 o Major features (directory authorities, backport from 0.4.2.2-alpha):
1112 - Directory authorities now reject relays running all currently
1113 deprecated release series. The currently supported release series
1114 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
1116 o Major bugfixes (embedded Tor, backport from 0.4.2.2-alpha):
1117 - Avoid a possible crash when restarting Tor in embedded mode and
1118 enabling a different set of publish/subscribe messages. Fixes bug
1119 31898; bugfix on 0.4.1.1-alpha.
1121 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
1122 - Relays now respect their AccountingMax bandwidth again. When
1123 relays entered "soft" hibernation (which typically starts when
1124 we've hit 90% of our AccountingMax), we had stopped checking
1125 whether we should enter hard hibernation. Soft hibernation refuses
1126 new connections and new circuits, but the existing circuits can
1127 continue, meaning that relays could have exceeded their configured
1128 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1130 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1131 - Stop ignoring torrc options after an %include directive, when the
1132 included directory ends with a file that does not contain any
1133 config options (but does contain comments or whitespace). Fixes
1134 bug 31408; bugfix on 0.3.1.1-alpha.
1136 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1137 - Onion services now always use the exact number of intro points
1138 configured with the HiddenServiceNumIntroductionPoints option (or
1139 fewer if nodes are excluded). Before, a service could sometimes
1140 pick more intro points than configured. Fixes bug 31548; bugfix
1143 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1144 - When building on Appveyor and Travis, pass the "-k" flag to make,
1145 so that we are informed of all compilation failures, not just the
1146 first one or two. Closes ticket 31372.
1148 o Minor features (geoip, backport from 0.4.2.5):
1149 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1150 Country database. Closes ticket 32685.
1152 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1153 - Avoid spurious errors when Appveyor CI fails before the install step.
1154 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1156 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1157 - Fix a BUG() assertion that occurs within a very small race window
1158 between when a client intro circuit opens and when its descriptor
1159 gets cleaned up from the cache. The circuit is now closed early,
1160 which will trigger a re-fetch of the descriptor and continue the
1161 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1163 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1164 - Avoid trying to read data from closed connections, which can cause
1165 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1166 30344; bugfix on 0.1.1.1-alpha.
1168 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1169 - On abort, try harder to flush the output buffers of log messages.
1170 On some platforms (macOS), log messages could be discarded when
1171 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1172 - Report the tor version whenever an assertion fails. Previously, we
1173 only reported the Tor version on some crashes, and some non-fatal
1174 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1175 - When tor aborts due to an error, close log file descriptors before
1176 aborting. Closing the logs makes some OSes flush log file buffers,
1177 rather than deleting buffered log lines. Fixes bug 31594; bugfix
1180 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1181 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
1182 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
1183 - Disable backtrace signal handlers when shutting down tor. Fixes
1184 bug 31614; bugfix on 0.2.5.2-alpha.
1185 - Rate-limit our the logging message about the obsolete .exit
1186 notation. Previously, there was no limit on this warning, which
1187 could potentially be triggered many times by a hostile website.
1188 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1190 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1191 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1192 cell on a connection using the obsolete v1 link protocol. Log a
1193 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1195 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1196 - Reset the periodic events' "enabled" flag when Tor is shut down
1197 cleanly. Previously, this flag was left on, which caused periodic
1198 events not to be re-enabled when Tor was relaunched in-process
1199 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1202 o Minor bugfixes (multithreading, backport from 0.4.2.2-alpha):
1203 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
1204 31736; bugfix on 0.0.7.
1206 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
1207 - Remove overly strict assertions that triggered when a pluggable
1208 transport failed to launch. Fixes bug 31091; bugfix
1210 - Remove an assertion in the Unix process backend. This assertion
1211 would trigger when we failed to find the executable for a child
1212 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1214 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1215 - Avoid crashing when starting with a corrupt keys directory where
1216 the old ntor key and the new ntor key are identical. Fixes bug
1217 30916; bugfix on 0.2.4.8-alpha.
1219 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
1220 - When testing port rebinding, don't busy-wait for tor to log.
1221 Instead, actually sleep for a short time before polling again.
1222 Also improve the formatting of control commands and log messages.
1223 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1225 o Minor bugfixes (tests, SunOS, backport from 0.4.2.2-alpha):
1226 - Avoid a map_anon_nofork test failure due to a signed/unsigned
1227 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
1229 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
1230 - Log bugs about the TLS read buffer's length only once, rather than
1231 filling the logs with similar warnings. Fixes bug 31939; bugfix
1234 o Documentation (backport from 0.4.2.2-alpha):
1235 - Explain why we can't destroy the backtrace buffer mutex. Explain
1236 why we don't need to destroy the log mutex. Closes ticket 31736.
1238 o Testing (continuous integration, backport from 0.4.2.3-alpha):
1239 - Disable all but one Travis CI macOS build, to mitigate slow
1240 scheduling of Travis macOS jobs. Closes ticket 32177.
1241 - Run the chutney IPv6 networks as part of Travis CI. Closes
1243 - Simplify the Travis CI build matrix, and optimise for build time.
1244 Closes ticket 31859.
1245 - Use Windows Server 2019 instead of Windows Server 2016 in our
1246 Appveyor builds. Closes ticket 32086.
1248 o Testing (continuous integration, backport from 0.4.2.4-rc):
1249 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1250 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1251 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1252 until we can fix some Bionic permissions issues (see ticket
1253 32240). Related to ticket 31919.
1254 - Install the mingw OpenSSL package in Appveyor. This makes sure
1255 that the OpenSSL headers and libraries match in Tor's Appveyor
1256 builds. (This bug was triggered by an Appveyor image update.)
1257 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1259 o Testing (continuous integration, backport from 0.4.2.5):
1260 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
1261 extensions. Also activates clang's -Wtypedef-redefinition warnings.
1262 Build some jobs with -std=gnu99, and some jobs without.
1263 Closes ticket 32500.
1266 Changes in version 0.4.0.6 - 2019-12-09
1267 This is the second stable release in the 0.4.0.x series. This release
1268 backports several bugfixes to improve stability and correctness. Anyone
1269 experiencing build problems or crashes with 0.4.0.5, including all relays
1270 relying on AccountingMax, should upgrade.
1272 Note that, per our support policy, support for the 0.4.0.x series will end
1273 on 2 Feb 2020. Anyone still running 0.4.0.x should plan to upgrade to the
1274 latest stable release, or downgrade to 0.3.5.x, which will get long-term
1275 support until 1 Feb 2022.
1277 o Directory authority changes (backport from 0.4.1.5):
1278 - The directory authority "dizum" has a new IP address. Closes
1281 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
1282 - Consider our directory information to have changed when our list
1283 of bridges changes. Previously, Tor would not re-compute the
1284 status of its directory information when bridges changed, and
1285 therefore would not realize that it was no longer able to build
1286 circuits. Fixes part of bug 29875.
1287 - Do not count previously configured working bridges towards our
1288 total of working bridges. Previously, when Tor's list of bridges
1289 changed, it would think that the old bridges were still usable,
1290 and delay fetching router descriptors for the new ones. Fixes part
1291 of bug 29875; bugfix on 0.3.0.1-alpha.
1293 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
1294 - When considering upgrading circuits from "waiting for guard" to
1295 "open", always ignore circuits that are marked for close. Otherwise,
1296 we can end up in the situation where a subsystem is notified that
1297 a closing circuit has just opened, leading to undesirable
1298 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
1300 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
1301 - Properly clean up the introduction point map when circuits change
1302 purpose from onion service circuits to pathbias, measurement, or
1303 other circuit types. This should fix some service-side instances
1304 of introduction point failure. Fixes bug 29034; bugfix
1307 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
1308 - Fix an unreachable bug in which an introduction point could try to
1309 send an INTRODUCE_ACK with a status code that Trunnel would refuse
1310 to encode, leading the relay to assert(). We've consolidated the
1311 ABI values into Trunnel now. Fixes bug 30454; bugfix
1313 - Clients can now handle unknown status codes from INTRODUCE_ACK
1314 cells. (The NACK behavior will stay the same.) This will allow us
1315 to extend status codes in the future without breaking the normal
1316 client behavior. Fixes another part of bug 30454; bugfix
1319 o Major bugfixes (relay, backport from 0.4.2.3-alpha):
1320 - Relays now respect their AccountingMax bandwidth again. When
1321 relays entered "soft" hibernation (which typically starts when
1322 we've hit 90% of our AccountingMax), we had stopped checking
1323 whether we should enter hard hibernation. Soft hibernation refuses
1324 new connections and new circuits, but the existing circuits can
1325 continue, meaning that relays could have exceeded their configured
1326 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
1328 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1329 - Stop ignoring torrc options after an %include directive, when the
1330 included directory ends with a file that does not contain any
1331 config options (but does contain comments or whitespace). Fixes
1332 bug 31408; bugfix on 0.3.1.1-alpha.
1334 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1335 - Onion services now always use the exact number of intro points
1336 configured with the HiddenServiceNumIntroductionPoints option (or
1337 fewer if nodes are excluded). Before, a service could sometimes
1338 pick more intro points than configured. Fixes bug 31548; bugfix
1341 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
1342 - Add a "--list-modules" command to print a list of which compile-
1343 time modules are enabled. Closes ticket 30452.
1345 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
1346 - Remove sudo configuration lines from .travis.yml as they are no
1347 longer needed with current Travis build environment. Resolves
1350 o Minor features (continuous integration, backport from 0.4.1.4-rc):
1351 - Our Travis configuration now uses Chutney to run some network
1352 integration tests automatically. Closes ticket 29280.
1354 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1355 - When building on Appveyor and Travis, pass the "-k" flag to make,
1356 so that we are informed of all compilation failures, not just the
1357 first one or two. Closes ticket 31372.
1359 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
1360 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
1361 in December 2018 (of which ~122 were still functional), with a
1362 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
1363 in June 2019. Closes ticket 28795.
1365 o Minor features (geoip, backport from 0.4.2.5):
1366 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1367 Country database. Closes ticket 32685.
1369 o Minor features (stem tests, backport from 0.4.2.1-alpha):
1370 - Change "make test-stem" so it only runs the stem tests that use
1371 tor. This change makes test-stem faster and more reliable. Closes
1374 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1375 - Avoid spurious errors when Appveyor CI fails before the install step.
1376 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1378 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
1379 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1380 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1382 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
1383 - Fix a logic error that prevented the SessionGroup sub-option from
1384 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
1386 o Minor bugfixes (circuit padding, backport from 0.4.1.4-rc):
1387 - On relays, properly check that a padding machine is absent before
1388 logging a warning about it being absent. Fixes bug 30649; bugfix
1391 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1392 - Fix a BUG() assertion that occurs within a very small race window
1393 between when a client intro circuit opens and when its descriptor
1394 gets cleaned up from the cache. The circuit is now closed early,
1395 which will trigger a re-fetch of the descriptor and continue the
1396 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1398 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
1399 - Don't believe clock skew results from NETINFO cells that appear to
1400 arrive before we sent the VERSIONS cells they are responding to.
1401 Previously, we would accept them up to 3 minutes "in the past".
1402 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1404 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
1405 - Fix a compilation warning on Windows about casting a function
1406 pointer for GetTickCount64(). Fixes bug 31374; bugfix
1409 o Minor bugfixes (compilation, backport from 0.4.1.5):
1410 - Avoid using labs() on time_t, which can cause compilation warnings
1411 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1413 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
1414 - Suppress spurious float-conversion warnings from GCC when calling
1415 floating-point classifier functions on FreeBSD. Fixes part of bug
1416 31687; bugfix on 0.3.1.5-alpha.
1418 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
1419 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
1420 due to missing declarations of abort(), and prevent other such
1421 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
1423 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
1424 - Fix a bug that prevented us from supporting SOCKS5 proxies that
1425 want authentication along with configured (but unused!)
1426 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
1428 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1429 - Avoid trying to read data from closed connections, which can cause
1430 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1431 30344; bugfix on 0.1.1.1-alpha.
1433 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
1434 - Allow the test-stem job to fail in Travis, because it sometimes
1435 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
1436 - Skip test_rebind on macOS in Travis, because it is unreliable on
1437 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1438 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
1439 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1441 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
1442 - Avoid a set of possible code paths that could try to use freed
1443 memory in routerlist_free() while Tor was exiting. Fixes bug
1444 31003; bugfix on 0.1.2.2-alpha.
1446 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
1447 - Stop crashing after parsing an unknown descriptor purpose
1448 annotation. We think this bug can only be triggered by modifying a
1449 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
1451 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
1452 - Move the "bandwidth-file-headers" line in directory authority
1453 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
1456 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1457 - On abort, try harder to flush the output buffers of log messages.
1458 On some platforms (macOS), log messages could be discarded when
1459 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1460 - Report the tor version whenever an assertion fails. Previously, we
1461 only reported the Tor version on some crashes, and some non-fatal
1462 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1464 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
1465 - When extracting an IPv6 address from a PF-based proxy, verify that
1466 we are actually configured to receive an IPv6 address, and log an
1467 internal error if not. Fixes part of bug 31687; bugfix
1470 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
1471 - When tor is missing descriptors for some primary entry guards,
1472 make the log message less alarming. It's normal for descriptors to
1473 expire, as long as tor fetches new ones soon after. Fixes bug
1474 31657; bugfix on 0.3.3.1-alpha.
1476 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
1477 - Do not log a warning when running with an OpenSSL version other
1478 than the one Tor was compiled with, if the two versions should be
1479 compatible. Previously, we would warn whenever the version was
1480 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
1482 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
1483 - Change log level of message "Hash of session info was not as
1484 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1487 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1488 - Rate-limit our the logging message about the obsolete .exit
1489 notation. Previously, there was no limit on this warning, which
1490 could potentially be triggered many times by a hostile website.
1491 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1493 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1494 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1495 cell on a connection using the obsolete v1 link protocol. Log a
1496 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1498 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1499 - Reset the periodic events' "enabled" flag when Tor is shut down
1500 cleanly. Previously, this flag was left on, which caused periodic
1501 events not to be re-enabled when Tor was relaunched in-process
1502 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1505 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
1506 - Avoid a minor memory leak that could occur on relays when failing
1507 to create a "keys" directory. Fixes bug 30148; bugfix
1510 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
1511 - Fix a trivial memory leak when parsing an invalid value
1512 from a download schedule in the configuration. Fixes bug
1513 30894; bugfix on 0.3.4.1-alpha.
1515 o Minor bugfixes (NetBSD, backport from 0.4.1.2-alpha):
1516 - Fix usage of minherit() on NetBSD and other platforms that define
1517 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
1518 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
1520 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
1521 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
1522 implemenation) when failing to load an onion service client
1523 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
1525 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
1526 - When purging the DNS cache because of an out-of-memory condition,
1527 try purging just the older entries at first. Previously, we would
1528 always purge the whole thing. Fixes bug 29617; bugfix
1531 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
1532 - Avoid crashing in our tor_vasprintf() implementation on systems
1533 that define neither vasprintf() nor _vscprintf(). (This bug has
1534 been here long enough that we question whether people are running
1535 Tor on such systems, but we're applying the fix out of caution.)
1536 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
1539 o Minor bugfixes (process management, backport from 0.4.2.3-alpha):
1540 - Remove overly strict assertions that triggered when a pluggable
1541 transport failed to launch. Fixes bug 31091; bugfix
1543 - Remove an assertion in the Unix process backend. This assertion
1544 would trigger when we failed to find the executable for a child
1545 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
1547 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1548 - Avoid crashing when starting with a corrupt keys directory where
1549 the old ntor key and the new ntor key are identical. Fixes bug
1550 30916; bugfix on 0.2.4.8-alpha.
1552 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
1553 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1554 31463; bugfix on 0.3.5.4-alpha.
1556 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
1557 - When testing port rebinding, don't busy-wait for tor to log.
1558 Instead, actually sleep for a short time before polling again.
1559 Also improve the formatting of control commands and log messages.
1560 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
1562 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
1563 - Log bugs about the TLS read buffer's length only once, rather than
1564 filling the logs with similar warnings. Fixes bug 31939; bugfix
1567 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
1568 - Always retry v2 single onion service intro and rend circuits with
1569 a 3-hop path. Previously, v2 single onion services used a 3-hop
1570 path when rendezvous circuits were retried after a remote or
1571 delayed failure, but a 1-hop path for immediate retries. Fixes bug
1572 23818; bugfix on 0.2.9.3-alpha.
1573 - Make v3 single onion services fall back to a 3-hop intro, when all
1574 intro points are unreachable via a 1-hop path. Previously, v3
1575 single onion services failed when all intro nodes were unreachable
1576 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
1578 o Documentation (backport from 0.4.2.1-alpha):
1579 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
1580 notice.html so that operators no longer have to host it
1581 themselves. Closes ticket 31089.
1583 o Testing (backport from 0.4.1.2-alpha):
1584 - Specify torrc paths (with empty files) when launching tor in
1585 integration tests; refrain from reading user and system torrcs.
1586 Resolves issue 29702.
1588 o Testing (continuous integration, backport from 0.4.1.1-alpha):
1589 - In Travis, show stem's tor log after failure. Closes ticket 30234.
1591 o Testing (continuous integration, backport from 0.4.1.5):
1592 - In Travis, make stem log a controller trace to the console, and
1593 tail stem's tor log after failure. Closes ticket 30591.
1594 - In Travis, only run the stem tests that use a tor binary. Closes
1597 o Testing (continuous integration, backport from 0.4.2.3-alpha):
1598 - Disable all but one Travis CI macOS build, to mitigate slow
1599 scheduling of Travis macOS jobs. Closes ticket 32177.
1600 - Run the chutney IPv6 networks as part of Travis CI. Closes
1602 - Simplify the Travis CI build matrix, and optimise for build time.
1603 Closes ticket 31859.
1604 - Use Windows Server 2019 instead of Windows Server 2016 in our
1605 Appveyor builds. Closes ticket 32086.
1607 o Testing (continuous integration, backport from 0.4.2.4-rc):
1608 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
1609 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
1610 until we can fix some Bionic permissions issues (see ticket
1611 32240). Related to ticket 31919.
1612 - Install the mingw OpenSSL package in Appveyor. This makes sure
1613 that the OpenSSL headers and libraries match in Tor's Appveyor
1614 builds. (This bug was triggered by an Appveyor image update.)
1615 Fixes bug 32449; bugfix on 0.3.5.6-rc.
1616 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
1618 o Testing (continuous integration, backport from 0.4.2.5):
1619 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
1620 extensions. Also activates clang's -Wtypedef-redefinition warnings.
1621 Build some jobs with -std=gnu99, and some jobs without.
1622 Closes ticket 32500.
1624 Changes in version 0.3.5.9 - 2019-12-09
1625 Tor 0.3.5.9 backports serveral fixes from later releases, including
1626 several that affect bridge users, relay stability, onion services,
1629 o Directory authority changes (backport from 0.4.1.5):
1630 - The directory authority "dizum" has a new IP address. Closes
1633 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
1634 - Consider our directory information to have changed when our list
1635 of bridges changes. Previously, Tor would not re-compute the
1636 status of its directory information when bridges changed, and
1637 therefore would not realize that it was no longer able to build
1638 circuits. Fixes part of bug 29875.
1639 - Do not count previously configured working bridges towards our
1640 total of working bridges. Previously, when Tor's list of bridges
1641 changed, it would think that the old bridges were still usable,
1642 and delay fetching router descriptors for the new ones. Fixes part
1643 of bug 29875; bugfix on 0.3.0.1-alpha.
1645 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
1646 - When considering upgrading circuits from "waiting for guard" to
1647 "open", always ignore circuits that are marked for close. Otherwise,
1648 we can end up in the situation where a subsystem is notified that
1649 a closing circuit has just opened, leading to undesirable
1650 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
1652 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
1653 - When running with NSS, disable TLS 1.2 ciphersuites that use
1654 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
1655 these ciphersuites don't work -- which caused relays to fail to
1656 handshake with one another when these ciphersuites were enabled.
1657 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
1659 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
1660 - Properly clean up the introduction point map when circuits change
1661 purpose from onion service circuits to pathbias, measurement, or
1662 other circuit types. This should fix some service-side instances
1663 of introduction point failure. Fixes bug 29034; bugfix
1666 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
1667 - Fix an unreachable bug in which an introduction point could try to
1668 send an INTRODUCE_ACK with a status code that Trunnel would refuse
1669 to encode, leading the relay to assert(). We've consolidated the
1670 ABI values into Trunnel now. Fixes bug 30454; bugfix
1672 - Clients can now handle unknown status codes from INTRODUCE_ACK
1673 cells. (The NACK behavior will stay the same.) This will allow us
1674 to extend status codes in the future without breaking the normal
1675 client behavior. Fixes another part of bug 30454; bugfix
1678 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
1679 - Stop ignoring torrc options after an %include directive, when the
1680 included directory ends with a file that does not contain any
1681 config options (but does contain comments or whitespace). Fixes
1682 bug 31408; bugfix on 0.3.1.1-alpha.
1684 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
1685 - Onion services now always use the exact number of intro points
1686 configured with the HiddenServiceNumIntroductionPoints option (or
1687 fewer if nodes are excluded). Before, a service could sometimes
1688 pick more intro points than configured. Fixes bug 31548; bugfix
1691 o Minor features (address selection, backport from 0.4.0.3-alpha):
1692 - Treat the subnet 100.64.0.0/10 as public for some purposes;
1693 private for others. This subnet is the RFC 6598 (Carrier Grade
1694 NAT) IP range, and is deployed by many ISPs as an alternative to
1695 RFC 1918 that does not break existing internal networks. Tor now
1696 blocks SOCKS and control ports on these addresses and warns users
1697 if client ports or ExtORPorts are listening on a RFC 6598 address.
1698 Closes ticket 28525. Patch by Neel Chauhan.
1700 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
1701 - Make bandwidth authorities ignore relays that are reported in the
1702 bandwidth file with the flag "vote=0". This change allows us to
1703 report unmeasured relays for diagnostic reasons without including
1704 their bandwidth in the bandwidth authorities' vote. Closes
1707 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
1708 - Add a "--list-modules" command to print a list of which compile-
1709 time modules are enabled. Closes ticket 30452.
1711 o Minor features (continuous integration, backport from 0.4.0.4-rc):
1712 - On Travis Rust builds, cleanup Rust registry and refrain from
1713 caching the "target/" directory to speed up builds. Resolves
1716 o Minor features (continuous integration, backport from 0.4.0.5):
1717 - In Travis, tell timelimit to use stem's backtrace signals, and
1718 launch python directly from timelimit, so python receives the
1719 signals from timelimit, rather than make. Closes ticket 30117.
1721 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
1722 - Remove sudo configuration lines from .travis.yml as they are no
1723 longer needed with current Travis build environment. Resolves
1726 o Minor features (continuous integration, backport from 0.4.1.4-rc):
1727 - Our Travis configuration now uses Chutney to run some network
1728 integration tests automatically. Closes ticket 29280.
1730 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
1731 - When building on Appveyor and Travis, pass the "-k" flag to make,
1732 so that we are informed of all compilation failures, not just the
1733 first one or two. Closes ticket 31372.
1735 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
1736 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
1737 in December 2018 (of which ~122 were still functional), with a
1738 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
1739 in June 2019. Closes ticket 28795.
1741 o Minor features (geoip, backport from 0.4.2.5):
1742 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
1743 Country database. Closes ticket 32685.
1745 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
1746 - Try to log an error from NSS (if there is any) and a more useful
1747 description of our situation if we are using NSS and a call to
1748 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
1750 o Minor features (stem tests, backport from 0.4.2.1-alpha):
1751 - Change "make test-stem" so it only runs the stem tests that use
1752 tor. This change makes test-stem faster and more reliable. Closes
1755 o Minor bugfixes (security, backport from 0.4.0.4-rc):
1756 - Verify in more places that we are not about to create a buffer
1757 with more than INT_MAX bytes, to avoid possible OOB access in the
1758 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
1759 fixed by Tobias Stoeckmann.
1760 - Fix a potential double free bug when reading huge bandwidth files.
1761 The issue is not exploitable in the current Tor network because
1762 the vulnerable code is only reached when directory authorities
1763 read bandwidth files, but bandwidth files come from a trusted
1764 source (usually the authorities themselves). Furthermore, the
1765 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
1766 which are not used by any of the current authorities. Fixes bug
1767 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
1770 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
1771 - Reset coverage state on disk after Travis CI has finished. This
1772 should prevent future coverage merge errors from causing the test
1773 suite for the "process" subsystem to fail. The process subsystem
1774 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
1776 - Terminate test-stem if it takes more than 9.5 minutes to run.
1777 (Travis terminates the job after 10 minutes of no output.)
1778 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
1780 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
1781 - Avoid spurious errors when Appveyor CI fails before the install step.
1782 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
1784 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
1785 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
1786 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
1788 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
1789 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
1790 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
1793 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
1794 - Fix a logic error that prevented the SessionGroup sub-option from
1795 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
1797 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
1798 - Fix a BUG() assertion that occurs within a very small race window
1799 between when a client intro circuit opens and when its descriptor
1800 gets cleaned up from the cache. The circuit is now closed early,
1801 which will trigger a re-fetch of the descriptor and continue the
1802 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
1804 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
1805 - Don't believe clock skew results from NETINFO cells that appear to
1806 arrive before we sent the VERSIONS cells they are responding to.
1807 Previously, we would accept them up to 3 minutes "in the past".
1808 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1810 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
1811 - Fix a compilation warning on Windows about casting a function
1812 pointer for GetTickCount64(). Fixes bug 31374; bugfix
1815 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
1816 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
1817 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
1819 o Minor bugfixes (compilation, backport from 0.4.1.5):
1820 - Avoid using labs() on time_t, which can cause compilation warnings
1821 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
1823 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
1824 - Suppress spurious float-conversion warnings from GCC when calling
1825 floating-point classifier functions on FreeBSD. Fixes part of bug
1826 31687; bugfix on 0.3.1.5-alpha.
1828 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
1829 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
1830 due to missing declarations of abort(), and prevent other such
1831 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
1833 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
1834 - Fix a bug that prevented us from supporting SOCKS5 proxies that
1835 want authentication along with configured (but unused!)
1836 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
1838 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
1839 - Avoid trying to read data from closed connections, which can cause
1840 needless loops in Libevent and infinite loops in Shadow. Fixes bug
1841 30344; bugfix on 0.1.1.1-alpha.
1843 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
1844 - Allow the test-stem job to fail in Travis, because it sometimes
1845 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
1846 - Skip test_rebind on macOS in Travis, because it is unreliable on
1847 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1848 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
1849 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
1851 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
1852 - Avoid a set of possible code paths that could try to use freed
1853 memory in routerlist_free() while Tor was exiting. Fixes bug
1854 31003; bugfix on 0.1.2.2-alpha.
1856 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
1857 - Stop crashing after parsing an unknown descriptor purpose
1858 annotation. We think this bug can only be triggered by modifying a
1859 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
1861 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
1862 - Move the "bandwidth-file-headers" line in directory authority
1863 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
1866 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
1867 - On abort, try harder to flush the output buffers of log messages.
1868 On some platforms (macOS), log messages could be discarded when
1869 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1870 - Report the tor version whenever an assertion fails. Previously, we
1871 only reported the Tor version on some crashes, and some non-fatal
1872 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
1874 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
1875 - When extracting an IPv6 address from a PF-based proxy, verify that
1876 we are actually configured to receive an IPv6 address, and log an
1877 internal error if not. Fixes part of bug 31687; bugfix
1880 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
1881 - When tor is missing descriptors for some primary entry guards,
1882 make the log message less alarming. It's normal for descriptors to
1883 expire, as long as tor fetches new ones soon after. Fixes bug
1884 31657; bugfix on 0.3.3.1-alpha.
1886 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
1887 - Avoid logging that we are relaxing a circuit timeout when that
1888 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
1890 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
1891 - Correct a misleading error message when IPv4Only or IPv6Only is
1892 used but the resolved address can not be interpreted as an address
1893 of the specified IP version. Fixes bug 13221; bugfix on
1894 0.2.3.9-alpha. Patch from Kris Katterjohn.
1895 - Log the correct port number for listening sockets when "auto" is
1896 used to let Tor pick the port number. Previously, port 0 was
1897 logged instead of the actual port number. Fixes bug 29144; bugfix
1898 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1899 - Stop logging a BUG() warning when Tor is waiting for exit
1900 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
1902 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
1903 - Do not log a warning when running with an OpenSSL version other
1904 than the one Tor was compiled with, if the two versions should be
1905 compatible. Previously, we would warn whenever the version was
1906 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
1908 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
1909 - Change log level of message "Hash of session info was not as
1910 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
1913 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
1914 - Rate-limit our the logging message about the obsolete .exit
1915 notation. Previously, there was no limit on this warning, which
1916 could potentially be triggered many times by a hostile website.
1917 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
1919 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
1920 - Do not log a nonfatal assertion failure when receiving a VERSIONS
1921 cell on a connection using the obsolete v1 link protocol. Log a
1922 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
1924 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
1925 - Reset the periodic events' "enabled" flag when Tor is shut down
1926 cleanly. Previously, this flag was left on, which caused periodic
1927 events not to be re-enabled when Tor was relaunched in-process
1928 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
1931 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
1932 - Avoid a minor memory leak that could occur on relays when failing
1933 to create a "keys" directory. Fixes bug 30148; bugfix
1936 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
1937 - Fix a trivial memory leak when parsing an invalid value
1938 from a download schedule in the configuration. Fixes bug
1939 30894; bugfix on 0.3.4.1-alpha.
1941 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
1942 - Refactor the shared random state's memory management so that it
1943 actually takes ownership of the shared random value pointers.
1944 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
1946 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
1947 - Stop leaking parts of the shared random state in the shared-random
1948 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
1950 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
1951 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
1952 implemenation) when failing to load an onion service client
1953 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
1955 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
1956 - When purging the DNS cache because of an out-of-memory condition,
1957 try purging just the older entries at first. Previously, we would
1958 always purge the whole thing. Fixes bug 29617; bugfix
1961 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
1962 - Avoid crashing in our tor_vasprintf() implementation on systems
1963 that define neither vasprintf() nor _vscprintf(). (This bug has
1964 been here long enough that we question whether people are running
1965 Tor on such systems, but we're applying the fix out of caution.)
1966 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
1969 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
1970 - Avoid crashing when starting with a corrupt keys directory where
1971 the old ntor key and the new ntor key are identical. Fixes bug
1972 30916; bugfix on 0.2.4.8-alpha.
1974 o Minor bugfixes (rust, backport from 0.4.0.5):
1975 - Abort on panic in all build profiles, instead of potentially
1976 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
1978 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
1979 - Correctly exclude a redundant rust build job in Travis. Fixes bug
1980 31463; bugfix on 0.3.5.4-alpha.
1982 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
1983 - Allow connections to single onion services to remain idle without
1984 being disconnected. Previously, relays acting as rendezvous points
1985 for single onion services were mistakenly closing idle rendezvous
1986 circuits after 60 seconds, thinking that they were unused
1987 directory-fetching circuits that had served their purpose. Fixes
1988 bug 29665; bugfix on 0.2.1.26.
1990 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
1991 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
1992 relay and bridge extra-info documents. Fixes bug 29017; bugfix
1995 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
1996 - Downgrade some LOG_ERR messages in the address/* tests to
1997 warnings. The LOG_ERR messages were occurring when we had no
1998 configured network. We were failing the unit tests, because we
1999 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
2000 29530; bugfix on 0.3.5.8.
2001 - Fix our gcov wrapper script to look for object files at the
2002 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
2004 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
2005 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
2006 recent test-network.sh to use new chutney features in CI. Fixes
2007 bug 29703; bugfix on 0.2.9.1-alpha.
2008 - Fix a test failure on Windows caused by an unexpected "BUG"
2009 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
2012 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
2013 - When testing port rebinding, don't busy-wait for tor to log.
2014 Instead, actually sleep for a short time before polling again.
2015 Also improve the formatting of control commands and log messages.
2016 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2018 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
2019 - When classifying a client's selection of TLS ciphers, if the
2020 client ciphers are not yet available, do not cache the result.
2021 Previously, we had cached the unavailability of the cipher list
2022 and never looked again, which in turn led us to assume that the
2023 client only supported the ancient V1 link protocol. This, in turn,
2024 was causing Stem integration tests to stall in some cases. Fixes
2025 bug 30021; bugfix on 0.2.4.8-alpha.
2027 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
2028 - Log bugs about the TLS read buffer's length only once, rather than
2029 filling the logs with similar warnings. Fixes bug 31939; bugfix
2032 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2033 - Always retry v2 single onion service intro and rend circuits with
2034 a 3-hop path. Previously, v2 single onion services used a 3-hop
2035 path when rendezvous circuits were retried after a remote or
2036 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2037 23818; bugfix on 0.2.9.3-alpha.
2038 - Make v3 single onion services fall back to a 3-hop intro, when all
2039 intro points are unreachable via a 1-hop path. Previously, v3
2040 single onion services failed when all intro nodes were unreachable
2041 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2043 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
2044 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
2045 Windows Server 2012 R2 job. The remaining 2 jobs still provide
2046 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
2047 fast_finish, so failed jobs terminate the build immediately. Fixes
2048 bug 29601; bugfix on 0.3.5.4-alpha.
2050 o Documentation (backport from 0.4.2.1-alpha):
2051 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2052 notice.html so that operators no longer have to host it
2053 themselves. Closes ticket 31089.
2055 o Testing (backport from 0.4.1.2-alpha):
2056 - Specify torrc paths (with empty files) when launching tor in
2057 integration tests; refrain from reading user and system torrcs.
2058 Resolves issue 29702.
2060 o Testing (continuous integration, backport from 0.4.1.1-alpha):
2061 - In Travis, show stem's tor log after failure. Closes ticket 30234.
2063 o Testing (continuous integration, backport from 0.4.1.5):
2064 - In Travis, make stem log a controller trace to the console, and
2065 tail stem's tor log after failure. Closes ticket 30591.
2066 - In Travis, only run the stem tests that use a tor binary. Closes
2069 o Testing (continuous integration, backport from 0.4.2.3-alpha):
2070 - Disable all but one Travis CI macOS build, to mitigate slow
2071 scheduling of Travis macOS jobs. Closes ticket 32177.
2072 - Run the chutney IPv6 networks as part of Travis CI. Closes
2074 - Simplify the Travis CI build matrix, and optimise for build time.
2075 Closes ticket 31859.
2076 - Use Windows Server 2019 instead of Windows Server 2016 in our
2077 Appveyor builds. Closes ticket 32086.
2079 o Testing (continuous integration, backport from 0.4.2.4-rc):
2080 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2081 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2082 until we can fix some Bionic permissions issues (see ticket
2083 32240). Related to ticket 31919.
2084 - Install the mingw OpenSSL package in Appveyor. This makes sure
2085 that the OpenSSL headers and libraries match in Tor's Appveyor
2086 builds. (This bug was triggered by an Appveyor image update.)
2087 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2088 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2090 o Testing (continuous integration, backport from 0.4.2.5):
2091 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
2092 extensions. Also activates clang's -Wtypedef-redefinition warnings.
2093 Build some jobs with -std=gnu99, and some jobs without.
2094 Closes ticket 32500.
2096 Changes in version 0.4.2.4-rc - 2019-11-15
2097 Tor 0.4.2.4-rc is the first release candidate in its series. It fixes
2098 several bugs from earlier versions, including a few that would result in
2099 stack traces or incorrect behavior.
2101 o Minor features (build system):
2102 - Make pkg-config use --prefix when cross-compiling, if
2103 PKG_CONFIG_PATH is not set. Closes ticket 32191.
2105 o Minor features (geoip):
2106 - Update geoip and geoip6 to the November 6 2019 Maxmind GeoLite2
2107 Country database. Closes ticket 32440.
2109 o Minor bugfixes (client, onion service v3):
2110 - Fix a BUG() assertion that occurs within a very small race window
2111 between when a client intro circuit opens and when its descriptor
2112 gets cleaned up from the cache. The circuit is now closed early,
2113 which will trigger a re-fetch of the descriptor and continue the
2114 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
2116 o Minor bugfixes (code quality):
2117 - Fix "make check-includes" so it runs correctly on out-of-tree
2118 builds. Fixes bug 31335; bugfix on 0.3.5.1-alpha.
2120 o Minor bugfixes (configuration):
2121 - Log the option name when skipping an obsolete option. Fixes bug
2122 32295; bugfix on 0.4.2.1-alpha.
2124 o Minor bugfixes (crash):
2125 - When running Tor with an option like --verify-config or
2126 --dump-config that does not start the event loop, avoid crashing
2127 if we try to exit early because of an error. Fixes bug 32407;
2128 bugfix on 0.3.3.1-alpha.
2130 o Minor bugfixes (directory):
2131 - When checking if a directory connection is anonymous, test if the
2132 circuit was marked for close before looking at its channel. This
2133 avoids a BUG() stacktrace if the circuit was previously closed.
2134 Fixes bug 31958; bugfix on 0.4.2.1-alpha.
2136 o Minor bugfixes (shellcheck):
2137 - Fix minor shellcheck errors in the git-*.sh scripts. Fixes bug
2138 32402; bugfix on 0.4.2.1-alpha.
2139 - Start checking most scripts for shellcheck errors again. Fixes bug
2140 32402; bugfix on 0.4.2.1-alpha.
2142 o Testing (continuous integration):
2143 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
2144 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
2145 until we can fix some Bionic permissions issues (see ticket
2146 32240). Related to ticket 31919.
2147 - Install the mingw OpenSSL package in Appveyor. This makes sure
2148 that the OpenSSL headers and libraries match in Tor's Appveyor
2149 builds. (This bug was triggered by an Appveyor image update.)
2150 Fixes bug 32449; bugfix on 0.3.5.6-rc.
2151 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
2154 Changes in version 0.4.2.3-alpha - 2019-10-24
2155 This release fixes several bugs from the previous alpha release, and
2156 from earlier versions of Tor.
2158 o Major bugfixes (relay):
2159 - Relays now respect their AccountingMax bandwidth again. When
2160 relays entered "soft" hibernation (which typically starts when
2161 we've hit 90% of our AccountingMax), we had stopped checking
2162 whether we should enter hard hibernation. Soft hibernation refuses
2163 new connections and new circuits, but the existing circuits can
2164 continue, meaning that relays could have exceeded their configured
2165 AccountingMax. Fixes bug 32108; bugfix on 0.4.0.1-alpha.
2167 o Major bugfixes (v3 onion services):
2168 - Onion services now always use the exact number of intro points
2169 configured with the HiddenServiceNumIntroductionPoints option (or
2170 fewer if nodes are excluded). Before, a service could sometimes
2171 pick more intro points than configured. Fixes bug 31548; bugfix
2174 o Minor feature (onion services, control port):
2175 - The ADD_ONION command's keyword "BEST" now defaults to ED25519-V3
2176 (v3) onion services. Previously it defaulted to RSA1024 (v2).
2177 Closes ticket 29669.
2179 o Minor features (testing):
2180 - When running tests that attempt to look up hostnames, replace the
2181 libc name lookup functions with ones that do not actually touch
2182 the network. This way, the tests complete more quickly in the
2183 presence of a slow or missing DNS resolver. Closes ticket 31841.
2185 o Minor features (testing, continuous integration):
2186 - Disable all but one Travis CI macOS build, to mitigate slow
2187 scheduling of Travis macOS jobs. Closes ticket 32177.
2188 - Run the chutney IPv6 networks as part of Travis CI. Closes
2190 - Simplify the Travis CI build matrix, and optimise for build time.
2191 Closes ticket 31859.
2192 - Use Windows Server 2019 instead of Windows Server 2016 in our
2193 Appveyor builds. Closes ticket 32086.
2195 o Minor bugfixes (build system):
2196 - Interpret "--disable-module-dirauth=no" correctly. Fixes bug
2197 32124; bugfix on 0.3.4.1-alpha.
2198 - Interpret "--with-tcmalloc=no" correctly. Fixes bug 32124; bugfix
2200 - Stop failing when jemalloc is requested, but tcmalloc is not
2201 found. Fixes bug 32124; bugfix on 0.3.5.1-alpha.
2202 - When pkg-config is not installed, or a library that depends on
2203 pkg-config is not found, tell the user what to do to fix the
2204 problem. Fixes bug 31922; bugfix on 0.3.1.1-alpha.
2206 o Minor bugfixes (connections):
2207 - Avoid trying to read data from closed connections, which can cause
2208 needless loops in Libevent and infinite loops in Shadow. Fixes bug
2209 30344; bugfix on 0.1.1.1-alpha.
2211 o Minor bugfixes (error handling):
2212 - Always lock the backtrace buffer before it is used. Fixes bug
2213 31734; bugfix on 0.2.5.3-alpha.
2215 o Minor bugfixes (mainloop, periodic events, in-process API):
2216 - Reset the periodic events' "enabled" flag when Tor is shut down
2217 cleanly. Previously, this flag was left on, which caused periodic
2218 events not to be re-enabled when Tor was relaunched in-process
2219 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
2222 o Minor bugfixes (process management):
2223 - Remove overly strict assertions that triggered when a pluggable
2224 transport failed to launch. Fixes bug 31091; bugfix
2226 - Remove an assertion in the Unix process backend. This assertion
2227 would trigger when we failed to find the executable for a child
2228 process. Fixes bug 31810; bugfix on 0.4.0.1-alpha.
2230 o Minor bugfixes (testing):
2231 - Avoid intermittent test failures due to a test that had relied on
2232 inconsistent timing sources. Fixes bug 31995; bugfix
2234 - When testing port rebinding, don't busy-wait for tor to log.
2235 Instead, actually sleep for a short time before polling again.
2236 Also improve the formatting of control commands and log messages.
2237 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
2239 o Minor bugfixes (tls, logging):
2240 - Log bugs about the TLS read buffer's length only once, rather than
2241 filling the logs with similar warnings. Fixes bug 31939; bugfix
2244 o Minor bugfixes (v3 onion services):
2245 - Fix an implicit conversion from ssize_t to size_t discovered by
2246 Coverity. Fixes bug 31682; bugfix on 0.4.2.1-alpha.
2247 - Fix a memory leak in an unlikely error code path when encoding HS
2248 DoS establish intro extension cell. Fixes bug 32063; bugfix
2250 - When cleaning up intro circuits for a v3 onion service, don't
2251 remove circuits that have an established or pending circuit, even
2252 if they ran out of retries. This way, we don't remove a circuit on
2253 its last retry. Fixes bug 31652; bugfix on 0.3.2.1-alpha.
2256 - Correct the description of "GuardLifetime". Fixes bug 31189;
2257 bugfix on 0.3.0.1-alpha.
2258 - Make clear in the man page, in both the bandwidth section and the
2259 AccountingMax section, that Tor counts in powers of two, not
2260 powers of ten: 1 GByte is 1024*1024*1024 bytes, not one billion
2261 bytes. Resolves ticket 32106.
2264 Changes in version 0.4.2.2-alpha - 2019-10-07
2265 This release fixes several bugs from the previous alpha release, and
2266 from earlier versions. It also includes a change in authorities, so
2267 that they begin to reject the currently unsupported release series.
2269 o Major features (directory authorities):
2270 - Directory authorities now reject relays running all currently
2271 deprecated release series. The currently supported release series
2272 are: 0.2.9, 0.3.5, 0.4.0, 0.4.1, and 0.4.2. Closes ticket 31549.
2274 o Major bugfixes (embedded Tor):
2275 - Avoid a possible crash when restarting Tor in embedded mode and
2276 enabling a different set of publish/subscribe messages. Fixes bug
2277 31898; bugfix on 0.4.1.1-alpha.
2279 o Major bugfixes (torrc parsing):
2280 - Stop ignoring torrc options after an %include directive, when the
2281 included directory ends with a file that does not contain any
2282 config options (but does contain comments or whitespace). Fixes
2283 bug 31408; bugfix on 0.3.1.1-alpha.
2285 o Minor features (auto-formatting scripts):
2286 - When annotating C macros, never generate a line that our check-
2287 spaces script would reject. Closes ticket 31759.
2288 - When annotating C macros, try to remove cases of double-negation.
2289 Closes ticket 31779.
2291 o Minor features (continuous integration):
2292 - When building on Appveyor and Travis, pass the "-k" flag to make,
2293 so that we are informed of all compilation failures, not just the
2294 first one or two. Closes ticket 31372.
2296 o Minor features (geoip):
2297 - Update geoip and geoip6 to the October 1 2019 Maxmind GeoLite2
2298 Country database. Closes ticket 31931.
2300 o Minor features (maintenance scripts):
2301 - Add a Coccinelle script to detect bugs caused by incrementing or
2302 decrementing a variable inside a call to log_debug(). Since
2303 log_debug() is a macro whose arguments are conditionally
2304 evaluated, it is usually an error to do this. One such bug was
2305 30628, in which SENDME cells were miscounted by a decrement
2306 operator inside a log_debug() call. Closes ticket 30743.
2308 o Minor features (onion services v3):
2309 - Assist users who try to setup v2 client authorization in v3 onion
2310 services by pointing them to the right documentation. Closes
2313 o Minor bugfixes (Appveyor continuous integration):
2314 - Avoid spurious errors when Appveyor CI fails before the install
2315 step. Fixes bug 31884; bugfix on 0.3.4.2-alpha.
2317 o Minor bugfixes (best practices tracker):
2318 - When listing overbroad exceptions, do not also list problems, and
2319 do not list insufficiently broad exceptions. Fixes bug 31338;
2320 bugfix on 0.4.2.1-alpha.
2322 o Minor bugfixes (controller protocol):
2323 - Fix the MAPADDRESS controller command to accept one or more
2324 arguments. Previously, it required two or more arguments, and
2325 ignored the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2327 o Minor bugfixes (logging):
2328 - Add a missing check for HAVE_PTHREAD_H, because the backtrace code
2329 uses mutexes. Fixes bug 31614; bugfix on 0.2.5.2-alpha.
2330 - Disable backtrace signal handlers when shutting down tor. Fixes
2331 bug 31614; bugfix on 0.2.5.2-alpha.
2332 - Rate-limit our the logging message about the obsolete .exit
2333 notation. Previously, there was no limit on this warning, which
2334 could potentially be triggered many times by a hostile website.
2335 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
2336 - When initialising log domain masks, only set known log domains.
2337 Fixes bug 31854; bugfix on 0.2.1.1-alpha.
2339 o Minor bugfixes (logging, protocol violations):
2340 - Do not log a nonfatal assertion failure when receiving a VERSIONS
2341 cell on a connection using the obsolete v1 link protocol. Log a
2342 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
2344 o Minor bugfixes (modules):
2345 - Explain what the optional Directory Authority module is, and what
2346 happens when it is disabled. Fixes bug 31825; bugfix
2349 o Minor bugfixes (multithreading):
2350 - Avoid some undefined behaviour when freeing mutexes. Fixes bug
2351 31736; bugfix on 0.0.7.
2353 o Minor bugfixes (relay):
2354 - Avoid crashing when starting with a corrupt keys directory where
2355 the old ntor key and the new ntor key are identical. Fixes bug
2356 30916; bugfix on 0.2.4.8-alpha.
2358 o Minor bugfixes (tests, SunOS):
2359 - Avoid a map_anon_nofork test failure due to a signed/unsigned
2360 integer comparison. Fixes bug 31897; bugfix on 0.4.1.1-alpha.
2362 o Code simplification and refactoring:
2363 - Refactor connection_control_process_inbuf() to reduce the size of
2364 a practracker exception. Closes ticket 31840.
2365 - Refactor the microdescs_parse_from_string() function into smaller
2366 pieces, for better comprehensibility. Closes ticket 31675.
2367 - Use SEVERITY_MASK_IDX() to find the LOG_* mask indexes in the unit
2368 tests and fuzzers, rather than using hard-coded values. Closes
2370 - Interface for function `decrypt_desc_layer` cleaned up. Closes
2374 - Document the signal-safe logging behaviour in the tor man page.
2375 Also add some comments to the relevant functions. Closes
2377 - Explain why we can't destroy the backtrace buffer mutex. Explain
2378 why we don't need to destroy the log mutex. Closes ticket 31736.
2379 - The Tor source code repository now includes a (somewhat dated)
2380 description of Tor's modular architecture, in doc/HACKING/design.
2381 This is based on the old "tor-guts.git" repository, which we are
2382 adopting and superseding. Closes ticket 31849.
2385 Changes in version 0.4.1.6 - 2019-09-19
2386 This release backports several bugfixes to improve stability and
2387 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
2388 or experiencing reliability issues with single onion services, should
2391 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
2392 - Tolerate systems (including some Android installations) where
2393 madvise and MADV_DONTDUMP are available at build-time, but not at
2394 run time. Previously, these systems would notice a failed syscall
2395 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
2396 - Tolerate systems (including some Linux installations) where
2397 madvise and/or MADV_DONTFORK are available at build-time, but not
2398 at run time. Previously, these systems would notice a failed
2399 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
2401 o Minor features (stem tests, backport from 0.4.2.1-alpha):
2402 - Change "make test-stem" so it only runs the stem tests that use
2403 tor. This change makes test-stem faster and more reliable. Closes
2406 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
2407 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2408 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2410 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
2411 - Add more stub functions to fix compilation on Android with link-
2412 time optimization when --disable-module-dirauth is used.
2413 Previously, these compilation settings would make the compiler
2414 look for functions that didn't exist. Fixes bug 31552; bugfix
2416 - Suppress spurious float-conversion warnings from GCC when calling
2417 floating-point classifier functions on FreeBSD. Fixes part of bug
2418 31687; bugfix on 0.3.1.5-alpha.
2420 o Minor bugfixes (controller protocol):
2421 - Fix the MAPADDRESS controller command to accept one or more
2422 arguments. Previously, it required two or more arguments, and ignored
2423 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
2425 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
2426 - When extracting an IPv6 address from a PF-based proxy, verify that
2427 we are actually configured to receive an IPv6 address, and log an
2428 internal error if not. Fixes part of bug 31687; bugfix
2431 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
2432 - When tor is missing descriptors for some primary entry guards,
2433 make the log message less alarming. It's normal for descriptors to
2434 expire, as long as tor fetches new ones soon after. Fixes bug
2435 31657; bugfix on 0.3.3.1-alpha.
2437 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
2438 - Change log level of message "Hash of session info was not as
2439 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2442 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
2443 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2444 31463; bugfix on 0.3.5.4-alpha.
2446 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
2447 - Always retry v2 single onion service intro and rend circuits with
2448 a 3-hop path. Previously, v2 single onion services used a 3-hop
2449 path when rendezvous circuits were retried after a remote or
2450 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2451 23818; bugfix on 0.2.9.3-alpha.
2453 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
2454 - Always retry v3 single onion service intro and rend circuits with
2455 a 3-hop path. Previously, v3 single onion services used a 3-hop
2456 path when rend circuits were retried after a remote or delayed
2457 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2458 bugfix on 0.3.2.1-alpha.
2459 - Make v3 single onion services fall back to a 3-hop intro, when all
2460 intro points are unreachable via a 1-hop path. Previously, v3
2461 single onion services failed when all intro nodes were unreachable
2462 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2464 o Documentation (backport from 0.4.2.1-alpha):
2465 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2466 notice.html so that operators no longer have to host it
2467 themselves. Closes ticket 31089.
2470 Changes in version 0.4.2.1-alpha - 2019-09-17
2471 This is the first alpha release in the 0.4.2.x series. It adds new
2472 defenses for denial-of-service attacks against onion services. It also
2473 includes numerous kinds of bugfixes and refactoring to help improve
2474 Tor's stability and ease of development.
2476 o Major features (onion service v3, denial of service):
2477 - Add onion service introduction denial of service defenses. Intro
2478 points can now rate-limit client introduction requests, using
2479 parameters that can be sent by the service within the
2480 ESTABLISH_INTRO cell. If the cell extension for this is not used,
2481 the intro point will honor the consensus parameters. Closes
2484 o Major bugfixes (circuit build, guard):
2485 - When considering upgrading circuits from "waiting for guard" to
2486 "open", always ignore circuits that are marked for close.
2487 Previously we could end up in the situation where a subsystem is
2488 notified of a circuit opening, but the circuit is still marked for
2489 close, leading to undesirable behavior. Fixes bug 30871; bugfix
2492 o Major bugfixes (crash, Linux, Android):
2493 - Tolerate systems (including some Android installations) where
2494 madvise and MADV_DONTDUMP are available at build-time, but not at
2495 run time. Previously, these systems would notice a failed syscall
2496 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
2497 - Tolerate systems (including some Linux installations) where
2498 madvise and/or MADV_DONTFORK are available at build-time, but not
2499 at run time. Previously, these systems would notice a failed
2500 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
2502 o Minor features (best practices tracker):
2503 - Our best-practices tracker now integrates with our include-checker
2504 tool to keep track of how many layering violations we have not yet
2505 fixed. We hope to reduce this number over time to improve Tor's
2506 modularity. Closes ticket 31176.
2507 - Add a TOR_PRACTRACKER_OPTIONS variable for passing arguments to
2508 practracker from the environment. We may want this for continuous
2509 integration. Closes ticket 31309.
2510 - Give a warning rather than an error when a practracker exception
2511 is violated by a small amount, add a --list-overbroad option to
2512 practracker that lists exceptions that are stricter than they need
2513 to be, and provide an environment variable for disabling
2514 practracker. Closes ticket 30752.
2515 - Our best-practices tracker now looks at headers as well as C
2516 files. Closes ticket 31175.
2518 o Minor features (build system):
2519 - Add --disable-manpage and --disable-html-manual options to
2520 configure script. This will enable shortening build times by not
2521 building documentation. Resolves issue 19381.
2523 o Minor features (compilation):
2524 - Log a more useful error message when we are compiling and one of
2525 the compile-time hardening options we have selected can be linked
2526 but not executed. Closes ticket 27530.
2528 o Minor features (configuration):
2529 - The configuration code has been extended to allow splitting
2530 configuration data across multiple objects. Previously, all
2531 configuration data needed to be kept in a single object, which
2532 tended to become bloated. Closes ticket 31240.
2534 o Minor features (continuous integration):
2535 - When running CI builds on Travis, put some random data in
2536 ~/.torrc, to make sure no tests are reading the Tor configuration
2537 file from its default location. Resolves issue 30102.
2539 o Minor features (debugging):
2540 - Log a nonfatal assertion failure if we encounter a configuration
2541 line whose command is "CLEAR" but which has a nonempty value. This
2542 should be impossible, according to the rules of our configuration
2543 line parsing. Closes ticket 31529.
2545 o Minor features (git hooks):
2546 - Our pre-commit git hook now checks for a special file before
2547 running practracker, so that practracker only runs on branches
2548 that are based on master. Since the pre-push hook calls the pre-
2549 commit hook, practracker will also only run before pushes of
2550 branches based on master. Closes ticket 30979.
2552 o Minor features (git scripts):
2553 - Add a "--" command-line argument, to separate git-push-all.sh
2554 script arguments from arguments that are passed through to git
2555 push. Closes ticket 31314.
2556 - Add a -r <remote-name> argument to git-push-all.sh, so the script
2557 can push test branches to a personal remote. Closes ticket 31314.
2558 - Add a -t <test-branch-prefix> argument to git-merge-forward.sh and
2559 git-push-all.sh, which makes these scripts create, merge forward,
2560 and push test branches. Closes ticket 31314.
2561 - Add a -u argument to git-merge-forward.sh, so that the script can
2562 re-use existing test branches after a merge failure and fix.
2563 Closes ticket 31314.
2564 - Add a TOR_GIT_PUSH env var, which sets the default git push
2565 command and arguments for git-push-all.sh. Closes ticket 31314.
2566 - Add a TOR_PUSH_DELAY variable to git-push-all.sh, which makes the
2567 script push master and maint branches with a delay between each
2568 branch. These delays trigger the CI jobs in a set order, which
2569 should show the most likely failures first. Also make pushes
2570 atomic by default, and make the script pass any command-line
2571 arguments to git push. Closes ticket 29879.
2572 - Call the shellcheck script from the pre-commit hook. Closes
2574 - Skip pushing test branches that are the same as a remote
2575 maint/release/master branch in git-push-all.sh by default. Add a
2576 -s argument, so git-push-all.sh can push all test branches. Closes
2579 o Minor features (IPv6, logging):
2580 - Log IPv6 addresses as well as IPv4 addresses when describing
2581 routerinfos, routerstatuses, and nodes. Closes ticket 21003.
2583 o Minor features (onion service v3):
2584 - Do not allow single hop clients to fetch or post an HS descriptor
2585 from an HSDir. Closes ticket 24964.
2587 o Minor features (onion service):
2588 - Disallow single-hop clients at the introduction point. We've
2589 removed Tor2web support a while back and single-hop rendezvous
2590 attempts are blocked at the relays. This change should remove load
2591 off the network from spammy clients. Close ticket 24963.
2593 o Minor features (stem tests):
2594 - Change "make test-stem" so it only runs the stem tests that use
2595 tor. This change makes test-stem faster and more reliable. Closes
2598 o Minor features (testing):
2599 - Add a script to invoke "tor --dump-config" and "tor
2600 --verify-config" with various configuration options, and see
2601 whether tor's resulting configuration or error messages are what
2602 we expect. Use it for integration testing of our +Option and
2603 /Option flags. Closes ticket 31637.
2604 - Improve test coverage for our existing configuration parsing and
2605 management API. Closes ticket 30893.
2606 - Add integration tests to make sure that practracker gives the
2607 outputs we expect. Closes ticket 31477.
2608 - The practracker self-tests are now run as part of the Tor test
2609 suite. Closes ticket 31304.
2611 o Minor features (token bucket):
2612 - Implement a generic token bucket that uses a single counter, for
2613 use in anti-DoS onion service work. Closes ticket 30687.
2615 o Minor bugfixes (best practices tracker):
2616 - Fix a few issues in the best-practices script, including tests,
2617 tab tolerance, error reporting, and directory-exclusion logic.
2618 Fixes bug 29746; bugfix on 0.4.1.1-alpha.
2619 - When running check-best-practices, only consider files in the src
2620 subdirectory. Previously we had recursively considered all
2621 subdirectories, which made us get confused by the temporary
2622 directories made by "make distcheck". Fixes bug 31578; bugfix
2625 o Minor bugfixes (build system):
2626 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
2627 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
2629 o Minor bugfixes (chutney, makefiles, documentation):
2630 - "make test-network-all" now shows the warnings from each test-
2631 network.sh run on the console, so developers see new warnings
2632 early. We've also improved the documentation for this feature, and
2633 renamed a Makefile variable so the code is self-documenting. Fixes
2634 bug 30455; bugfix on 0.3.0.4-rc.
2636 o Minor bugfixes (compilation):
2637 - Add more stub functions to fix compilation on Android with link-
2638 time optimization when --disable-module-dirauth is used.
2639 Previously, these compilation settings would make the compiler
2640 look for functions that didn't exist. Fixes bug 31552; bugfix
2642 - Suppress spurious float-conversion warnings from GCC when calling
2643 floating-point classifier functions on FreeBSD. Fixes part of bug
2644 31687; bugfix on 0.3.1.5-alpha.
2646 o Minor bugfixes (configuration):
2647 - Invalid floating-point values in the configuration file are now
2648 treated as errors in the configuration. Previously, they were
2649 ignored and treated as zero. Fixes bug 31475; bugfix on 0.0.1.
2651 o Minor bugfixes (coverity):
2652 - Add an assertion when parsing a BEGIN cell so that coverity can be
2653 sure that we are not about to dereference a NULL address. Fixes
2654 bug 31026; bugfix on 0.2.4.7-alpha. This is CID 1447296.
2655 - In our siphash implementation, when building for coverity, use
2656 memcpy in place of a switch statement, so that coverity can tell
2657 we are not accessing out-of-bounds memory. Fixes bug 31025; bugfix
2658 on 0.2.8.1-alpha. This is tracked as CID 1447293 and 1447295.
2659 - Fix several coverity warnings from our unit tests. Fixes bug
2660 31030; bugfix on 0.2.4.1-alpha, 0.3.2.1-alpha, and 0.4.0.1-alpha.
2662 o Minor bugfixes (developer tooling):
2663 - Only log git script changes in the post-merge script when the
2664 merge was to the master branch. Fixes bug 31040; bugfix
2667 o Minor bugfixes (directory authorities):
2668 - Return a distinct status when formatting annotations fails. Fixes
2669 bug 30780; bugfix on 0.2.0.8-alpha.
2671 o Minor bugfixes (error handling):
2672 - On abort, try harder to flush the output buffers of log messages.
2673 On some platforms (macOS), log messages could be discarded when
2674 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2675 - Report the tor version whenever an assertion fails. Previously, we
2676 only reported the Tor version on some crashes, and some non-fatal
2677 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
2678 - When tor aborts due to an error, close log file descriptors before
2679 aborting. Closing the logs makes some OSes flush log file buffers,
2680 rather than deleting buffered log lines. Fixes bug 31594; bugfix
2683 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6):
2684 - When extracting an IPv6 address from a PF-based proxy, verify that
2685 we are actually configured to receive an IPv6 address, and log an
2686 internal error if not. Fixes part of bug 31687; bugfix
2689 o Minor bugfixes (git hooks):
2690 - Remove a duplicate call to practracker from the pre-push hook. The
2691 pre-push hook already calls the pre-commit hook, which calls
2692 practracker. Fixes bug 31462; bugfix on 0.4.1.1-alpha.
2694 o Minor bugfixes (git scripts):
2695 - Stop hard-coding the bash path in the git scripts. Some OSes don't
2696 have bash in /usr/bin, others have an ancient bash at this path.
2697 Fixes bug 30840; bugfix on 0.4.0.1-alpha.
2698 - Stop hard-coding the tor master branch name and worktree path in
2699 the git scripts. Fixes bug 30841; bugfix on 0.4.0.1-alpha.
2700 - Allow git-push-all.sh to be run from any directory. Previously,
2701 the script only worked if run from an upstream worktree directory.
2702 Closes ticket 31678.
2704 o Minor bugfixes (guards):
2705 - When tor is missing descriptors for some primary entry guards,
2706 make the log message less alarming. It's normal for descriptors to
2707 expire, as long as tor fetches new ones soon after. Fixes bug
2708 31657; bugfix on 0.3.3.1-alpha.
2710 o Minor bugfixes (ipv6):
2711 - Check for private IPv6 addresses alongside their IPv4 equivalents
2712 when authorities check descriptors. Previously, we only checked
2713 for private IPv4 addresses. Fixes bug 31088; bugfix on
2714 0.2.3.21-rc. Patch by Neel Chauhan.
2715 - When parsing microdescriptors, we should check the IPv6 exit
2716 policy alongside IPv4. Previously, we checked both exit policies
2717 for only router info structures, while microdescriptors were
2718 IPv4-only. Fixes bug 27284; bugfix on 0.2.3.1-alpha. Patch by
2721 o Minor bugfixes (logging):
2722 - Change log level of message "Hash of session info was not as
2723 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
2725 - Fix a code issue that would have broken our parsing of log domains
2726 as soon as we had 33 of them. Fortunately, we still only have 29.
2727 Fixes bug 31451; bugfix on 0.4.1.4-rc.
2729 o Minor bugfixes (memory management):
2730 - Stop leaking a small amount of memory in nt_service_install(), in
2731 unreachable code. Fixes bug 30799; bugfix on 0.2.0.7-alpha. Patch
2734 o Minor bugfixes (networking, IP addresses):
2735 - When parsing addresses via Tor's internal DNS lookup API, reject
2736 IPv4 addresses in square brackets, and accept IPv6 addresses in
2737 square brackets. This change completes the work started in 23082,
2738 making address parsing consistent between tor's internal DNS
2739 lookup and address parsing APIs. Fixes bug 30721; bugfix
2741 - When parsing addresses via Tor's internal address:port parsing and
2742 DNS lookup APIs, require IPv6 addresses with ports to have square
2743 brackets. But allow IPv6 addresses without ports, whether or not
2744 they have square brackets. Fixes bug 30721; bugfix
2747 o Minor bugfixes (onion service v3):
2748 - When purging the client descriptor cache, close any introduction
2749 point circuits associated with purged cache entries. This avoids
2750 picking those circuits later when connecting to the same
2751 introduction points. Fixes bug 30921; bugfix on 0.3.2.1-alpha.
2753 o Minor bugfixes (onion services):
2754 - In the hs_ident_circuit_t data structure, remove the unused field
2755 circuit_type and the respective argument in hs_ident_circuit_new().
2756 This field was set by clients (for introduction) and services (for
2757 introduction and rendezvous) but was never used afterwards. Fixes
2758 bug 31490; bugfix on 0.3.2.1-alpha. Patch by Neel Chauhan.
2760 o Minor bugfixes (operator tools):
2761 - Make tor-print-ed-signing-cert(1) print certificate expiration
2762 date in RFC 1123 and UNIX timestamp formats, to make output
2763 machine readable. Fixes bug 31012; bugfix on 0.3.5.1-alpha.
2765 o Minor bugfixes (rust):
2766 - Correctly exclude a redundant rust build job in Travis. Fixes bug
2767 31463; bugfix on 0.3.5.4-alpha.
2768 - Raise the minimum rustc version to 1.31.0, as checked by configure
2769 and CI. Fixes bug 31442; bugfix on 0.3.5.4-alpha.
2771 o Minor bugfixes (sendme, code structure):
2772 - Rename the trunnel SENDME file definition from sendme.trunnel to
2773 sendme_cell.trunnel to avoid having twice sendme.{c|h} in the
2774 repository. Fixes bug 30769; bugfix on 0.4.1.1-alpha.
2776 o Minor bugfixes (statistics):
2777 - Stop removing the ed25519 signature if the extra info file is too
2778 big. If the signature data was removed, but the keyword was kept,
2779 this could result in an unparseable extra info file. Fixes bug
2780 30958; bugfix on 0.2.7.2-alpha.
2782 o Minor bugfixes (subsystems):
2783 - Make the subsystem init order match the subsystem module
2784 dependencies. Call windows process security APIs as early as
2785 possible. Initialize logging before network and time, so that
2786 network and time can use logging. Fixes bug 31615; bugfix
2789 o Minor bugfixes (testing):
2790 - Teach the util/socketpair_ersatz test to work correctly when we
2791 have no network stack configured. Fixes bug 30804; bugfix
2794 o Minor bugfixes (v2 single onion services):
2795 - Always retry v2 single onion service intro and rend circuits with
2796 a 3-hop path. Previously, v2 single onion services used a 3-hop
2797 path when rendezvous circuits were retried after a remote or
2798 delayed failure, but a 1-hop path for immediate retries. Fixes bug
2799 23818; bugfix on 0.2.9.3-alpha.
2801 o Minor bugfixes (v3 single onion services):
2802 - Always retry v3 single onion service intro and rend circuits with
2803 a 3-hop path. Previously, v3 single onion services used a 3-hop
2804 path when rend circuits were retried after a remote or delayed
2805 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
2806 bugfix on 0.3.2.1-alpha.
2807 - Make v3 single onion services fall back to a 3-hop intro, when all
2808 intro points are unreachable via a 1-hop path. Previously, v3
2809 single onion services failed when all intro nodes were unreachable
2810 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
2813 - Improve documentation in circuit padding subsystem. Patch by
2814 Tobias Pulls. Closes ticket 31113.
2815 - Include an example usage for IPv6 ORPort in our sample torrc.
2816 Closes ticket 31320; patch from Ali Raheem.
2817 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
2818 notice.html so that operators no longer have to host it
2819 themselves. Closes ticket 31089.
2822 - No longer include recommended package digests in votes as detailed
2823 in proposal 301. The RecommendedPackages torrc option is
2824 deprecated and will no longer have any effect. "package" lines
2825 will still be considered when computing consensuses for consensus
2826 methods that include them. (This change has no effect on the list
2827 of recommended Tor versions, which is still in use.) Closes
2829 - Remove torctl.in from contrib/dist directory. Resolves
2833 - Run shellcheck for all non-third-party shell scripts that are
2834 shipped with Tor. Closes ticket 29533.
2835 - When checking shell scripts, ignore any user-created directories.
2836 Closes ticket 30967.
2838 o Code simplification and refactoring (config handling):
2839 - Extract our variable manipulation code from confparse.c to a new
2840 lower-level typedvar.h module. Closes ticket 30864.
2841 - Lower another layer of object management from confparse.c to a
2842 more general tool. Now typed structure members are accessible via
2843 an abstract type. Implements ticket 30914.
2844 - Move our backend logic for working with configuration and state
2845 files into a lower-level library, since it no longer depends on
2846 any tor-specific functionality. Closes ticket 31626.
2847 - Numerous simplifications in configuration-handling logic: remove
2848 duplicated macro definitions, replace magical names with flags,
2849 and refactor "TestingTorNetwork" to use the same default-option
2850 logic as the rest of Tor. Closes ticket 30935.
2851 - Replace our ad-hoc set of flags for configuration variables and
2852 configuration variable types with fine-grained orthogonal flags
2853 corresponding to the actual behavior we want. Closes ticket 31625.
2855 o Code simplification and refactoring (misc):
2856 - Eliminate some uses of lower-level control reply abstractions,
2857 primarily in the onion_helper functions. Closes ticket 30889.
2858 - Rework bootstrap tracking to use the new publish-subscribe
2859 subsystem. Closes ticket 29976.
2860 - Rewrite format_node_description() and router_get_verbose_nickname()
2861 to use strlcpy() and strlcat(). The previous implementation used
2862 memcpy() and pointer arithmetic, which was error-prone. Closes
2863 ticket 31545. This is CID 1452819.
2864 - Split extrainfo_dump_to_string() into smaller functions. Closes
2866 - Use the ptrdiff_t type consistently for expressing variable
2867 offsets and pointer differences. Previously we incorrectly (but
2868 harmlessly) used int and sometimes off_t for these cases. Closes
2870 - Use the subsystems mechanism to manage the main event loop code.
2871 Closes ticket 30806.
2872 - Various simplifications and minor improvements to the circuit
2873 padding machines. Patch by Tobias Pulls. Closes tickets 31112
2876 o Documentation (hard-coded directories):
2877 - Improve the documentation for the DirAuthority and FallbackDir
2878 torrc options. Closes ticket 30955.
2880 o Documentation (tor.1 man page):
2881 - Fix typo in tor.1 man page: the option is "--help", not "-help".
2882 Fixes bug 31008; bugfix on 0.2.2.9-alpha.
2885 Changes in version 0.4.1.5 - 2019-08-20
2886 This is the first stable release in the 0.4.1.x series. This series
2887 adds experimental circuit-level padding, authenticated SENDME cells to
2888 defend against certain attacks, and several performance improvements
2889 to save on CPU consumption. It fixes bugs in bootstrapping and v3
2890 onion services. It also includes numerous smaller features and
2891 bugfixes on earlier versions.
2893 Per our support policy, we will support the 0.4.1.x series for nine
2894 months, or until three months after the release of a stable 0.4.2.x:
2895 whichever is longer. If you need longer-term support, please stick
2896 with 0.3.5.x, which will we plan to support until Feb 2022.
2898 Below are the changes since 0.4.1.4-rc. For a complete list of changes
2899 since 0.4.0.5, see the ReleaseNotes file.
2901 o Directory authority changes:
2902 - The directory authority "dizum" has a new IP address. Closes
2905 o Minor features (circuit padding logging):
2906 - Demote noisy client-side warn logs about circuit padding to
2907 protocol warnings. Add additional log messages and circuit ID
2908 fields to help with bug 30992 and any other future issues.
2910 o Minor bugfixes (circuit padding negotiation):
2911 - Bump the circuit padding protocol version to explicitly signify
2912 that the HS setup machine support is finalized in 0.4.1.x-stable.
2913 This also means that 0.4.1.x-alpha clients will not negotiate
2914 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
2915 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
2916 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
2918 o Minor bugfixes (circuit padding):
2919 - Ignore non-padding cells on padding circuits. This addresses
2920 various warning messages from subsystems that were not expecting
2921 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
2923 o Minor bugfixes (clock skew detection):
2924 - Don't believe clock skew results from NETINFO cells that appear to
2925 arrive before we sent the VERSIONS cells they are responding to.
2926 Previously, we would accept them up to 3 minutes "in the past".
2927 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2929 o Minor bugfixes (compatibility, standards compliance):
2930 - Fix a bug that would invoke undefined behavior on certain
2931 operating systems when trying to asprintf() a string exactly
2932 INT_MAX bytes long. We don't believe this is exploitable, but it's
2933 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
2934 Found and fixed by Tobias Stoeckmann.
2936 o Minor bugfixes (compilation warning):
2937 - Fix a compilation warning on Windows about casting a function
2938 pointer for GetTickCount64(). Fixes bug 31374; bugfix
2941 o Minor bugfixes (compilation):
2942 - Avoid using labs() on time_t, which can cause compilation warnings
2943 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
2945 o Minor bugfixes (distribution):
2946 - Do not ship any temporary files found in the
2947 scripts/maint/practracker directory. Fixes bug 31311; bugfix
2950 o Testing (continuous integration):
2951 - In Travis, make stem log a controller trace to the console, and
2952 tail stem's tor log after failure. Closes ticket 30591.
2953 - In Travis, only run the stem tests that use a tor binary. Closes
2957 Changes in version 0.4.1.4-rc - 2019-07-25
2958 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
2959 updates to a new list of fallback directories. If no new bugs are
2960 found, the next release in the 0.4.1.x serious should be stable.
2962 o Major bugfixes (circuit build, guard):
2963 - When considering upgrading circuits from "waiting for guard" to
2964 "open", always ignore circuits that are marked for close. Otherwise,
2965 we can end up in the situation where a subsystem is notified that
2966 a closing circuit has just opened, leading to undesirable
2967 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
2969 o Minor features (continuous integration):
2970 - Our Travis configuration now uses Chutney to run some network
2971 integration tests automatically. Closes ticket 29280.
2973 o Minor features (fallback directory list):
2974 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
2975 in December 2018 (of which ~122 were still functional), with a
2976 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
2977 in June 2019. Closes ticket 28795.
2979 o Minor bugfixes (circuit padding):
2980 - On relays, properly check that a padding machine is absent before
2981 logging a warning about it being absent. Fixes bug 30649; bugfix
2983 - Add two NULL checks in unreachable places to silence Coverity (CID
2984 144729 and 1447291) and better future-proof ourselves. Fixes bug
2985 31024; bugfix on 0.4.1.1-alpha.
2987 o Minor bugfixes (crash on exit):
2988 - Avoid a set of possible code paths that could try to use freed
2989 memory in routerlist_free() while Tor was exiting. Fixes bug
2990 31003; bugfix on 0.1.2.2-alpha.
2992 o Minor bugfixes (logging):
2993 - Fix a conflict between the flag used for messaging-domain log
2994 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
2997 o Minor bugfixes (memory leaks):
2998 - Fix a trivial memory leak when parsing an invalid value from a
2999 download schedule in the configuration. Fixes bug 30894; bugfix
3002 o Code simplification and refactoring:
3003 - Remove some dead code from circpad_machine_remove_token() to fix
3004 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
3008 Changes in version 0.4.1.3-alpha - 2019-06-25
3009 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
3010 alpha, most of them from earlier release series.
3012 o Major bugfixes (Onion service reachability):
3013 - Properly clean up the introduction point map when circuits change
3014 purpose from onion service circuits to pathbias, measurement, or
3015 other circuit types. This should fix some service-side instances
3016 of introduction point failure. Fixes bug 29034; bugfix
3019 o Minor features (geoip):
3020 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
3021 Country database. Closes ticket 30852.
3023 o Minor features (logging):
3024 - Give a more useful assertion failure message if we think we have
3025 minherit() but we fail to make a region non-inheritable. Give a
3026 compile-time warning if our support for minherit() is incomplete.
3027 Closes ticket 30686.
3029 o Minor bugfixes (circuit isolation):
3030 - Fix a logic error that prevented the SessionGroup sub-option from
3031 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
3033 o Minor bugfixes (continuous integration):
3034 - Allow the test-stem job to fail in Travis, because it sometimes
3035 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
3036 - Skip test_rebind on macOS in Travis, because it is unreliable on
3037 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3038 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
3039 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
3041 o Minor bugfixes (directory authorities):
3042 - Stop crashing after parsing an unknown descriptor purpose
3043 annotation. We think this bug can only be triggered by modifying a
3044 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
3046 o Minor bugfixes (pluggable transports):
3047 - When running as a bridge with pluggable transports, always publish
3048 pluggable transport information in our extrainfo descriptor, even
3049 if ExtraInfoStatistics is 0. This information is needed by
3050 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
3053 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
3054 Closes ticket 30630.
3057 Changes in version 0.4.1.2-alpha - 2019-06-06
3058 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
3059 previous alpha, and some much older. It also contains minor testing
3060 improvements, and an improvement to the security of our authenticated
3061 SENDME implementation.
3063 o Major bugfixes (bridges):
3064 - Consider our directory information to have changed when our list
3065 of bridges changes. Previously, Tor would not re-compute the
3066 status of its directory information when bridges changed, and
3067 therefore would not realize that it was no longer able to build
3068 circuits. Fixes part of bug 29875.
3069 - Do not count previously configured working bridges towards our
3070 total of working bridges. Previously, when Tor's list of bridges
3071 changed, it would think that the old bridges were still usable,
3072 and delay fetching router descriptors for the new ones. Fixes part
3073 of bug 29875; bugfix on 0.3.0.1-alpha.
3075 o Major bugfixes (flow control, SENDME):
3076 - Decrement the stream-level package window after packaging a cell.
3077 Previously, it was done inside a log_debug() call, meaning that if
3078 debug logs were not enabled, the decrement would never happen, and
3079 thus the window would be out of sync with the other end point.
3080 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
3082 o Major bugfixes (onion service reachability):
3083 - Properly clean up the introduction point map and associated state
3084 when circuits change purpose from onion service circuits to
3085 pathbias, measurement, or other circuit types. This may fix some
3086 instances of introduction point failure. Fixes bug 29034; bugfix
3089 o Minor features (authenticated SENDME):
3090 - Ensure that there is enough randomness on every circuit to prevent
3091 an attacker from successfully predicting the hashes they will need
3092 to include in authenticated SENDME cells. At a random interval, if
3093 we have not sent randomness already, we now leave some extra space
3094 at the end of a cell that we can fill with random bytes. Closes
3097 o Minor features (continuous integration):
3098 - When running coverage builds on Travis, we now set
3099 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
3102 o Minor features (maintenance):
3103 - Add a new "make autostyle" target that developers can use to apply
3104 all automatic Tor style and consistency conversions to the
3105 codebase. Closes ticket 30539.
3107 o Minor features (testing):
3108 - The circuitpadding tests now use a reproducible RNG implementation,
3109 so that if a test fails, we can learn why. Part of ticket 28878.
3110 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
3111 to set the RNG seed for tests that use a reproducible RNG. Part of
3113 - When running tests in coverage mode, take additional care to make
3114 our coverage deterministic, so that we can accurately track
3115 changes in code coverage. Closes ticket 30519.
3117 o Minor bugfixes (configuration, proxies):
3118 - Fix a bug that prevented us from supporting SOCKS5 proxies that
3119 want authentication along with configured (but unused!)
3120 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
3122 o Minor bugfixes (controller):
3123 - POSTDESCRIPTOR requests should work again. Previously, they were
3124 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
3126 - Repair the HSFETCH command so that it works again. Previously, it
3127 expected a body when it shouldn't have. Fixes bug 30646; bugfix
3130 o Minor bugfixes (developer tooling):
3131 - Fix pre-push hook to allow fixup and squash commits when pushing
3132 to non-upstream git remote. Fixes bug 30286; bugfix
3135 o Minor bugfixes (directory authority):
3136 - Move the "bandwidth-file-headers" line in directory authority
3137 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
3140 o Minor bugfixes (NetBSD):
3141 - Fix usage of minherit() on NetBSD and other platforms that define
3142 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
3143 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
3145 o Minor bugfixes (out-of-memory handler):
3146 - When purging the DNS cache because of an out-of-memory condition,
3147 try purging just the older entries at first. Previously, we would
3148 always purge the whole thing. Fixes bug 29617; bugfix
3151 o Minor bugfixes (portability):
3152 - Avoid crashing in our tor_vasprintf() implementation on systems
3153 that define neither vasprintf() nor _vscprintf(). (This bug has
3154 been here long enough that we question whether people are running
3155 Tor on such systems, but we're applying the fix out of caution.)
3156 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
3159 o Minor bugfixes (shutdown, libevent, memory safety):
3160 - Avoid use-after-free bugs when shutting down, by making sure that
3161 we shut down libevent only after shutting down all of its users.
3162 We believe these are harmless in practice, since they only occur
3163 on the shutdown path, and do not involve any attacker-controlled
3164 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
3166 o Minor bugfixes (static analysis):
3167 - Fix several spurious Coverity warnings about the unit tests, to
3168 lower our chances of missing real warnings in the future. Fixes
3169 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
3172 - Specify torrc paths (with empty files) when launching tor in
3173 integration tests; refrain from reading user and system torrcs.
3174 Resolves issue 29702.
3177 Changes in version 0.4.1.1-alpha - 2019-05-22
3178 This is the first alpha in the 0.4.1.x series. It introduces
3179 lightweight circuit padding to make some onion-service circuits harder
3180 to distinguish, includes a new "authenticated SENDME" feature to make
3181 certain denial-of-service attacks more difficult, and improves
3182 performance in several areas.
3184 o Major features (circuit padding):
3185 - Onion service clients now add padding cells at the start of their
3186 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
3187 look more like general purpose Exit traffic. The overhead for this
3188 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
3189 extra upstream cell and 10 downstream cells for INTRODUCE
3190 circuits. This feature is only enabled when also supported by the
3191 circuit's middle node. (Clients may specify fixed middle nodes
3192 with the MiddleNodes option, and may force-disable this feature
3193 with the CircuitPadding option.) Closes ticket 28634.
3195 o Major features (code organization):
3196 - Tor now includes a generic publish-subscribe message-passing
3197 subsystem that we can use to organize intermodule dependencies. We
3198 hope to use this to reduce dependencies between modules that don't
3199 need to be related, and to generally simplify our codebase. Closes
3202 o Major features (controller protocol):
3203 - Controller commands are now parsed using a generalized parsing
3204 subsystem. Previously, each controller command was responsible for
3205 parsing its own input, which led to strange inconsistencies.
3206 Closes ticket 30091.
3208 o Major features (flow control):
3209 - Implement authenticated SENDMEs as detailed in proposal 289. A
3210 SENDME cell now includes the digest of the traffic that it
3211 acknowledges, so that once an end point receives the SENDME, it
3212 can confirm the other side's knowledge of the previous cells that
3213 were sent, and prevent certain types of denial-of-service attacks.
3214 This behavior is controlled by two new consensus parameters: see
3215 the proposal for more details. Fixes ticket 26288.
3217 o Major features (performance):
3218 - Our node selection algorithm now excludes nodes in linear time.
3219 Previously, the algorithm was quadratic, which could slow down
3220 heavily used onion services. Closes ticket 30307.
3222 o Major features (performance, RNG):
3223 - Tor now constructs a fast secure pseudorandom number generator for
3224 each thread, to use when performance is critical. This PRNG is
3225 based on AES-CTR, using a buffering construction similar to
3226 libottery and the (newer) OpenBSD arc4random() code. It
3227 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
3228 small outputs. Although we believe it to be cryptographically
3229 strong, we are only using it when necessary for performance.
3230 Implements tickets 29023 and 29536.
3232 o Major bugfixes (onion service v3):
3233 - Fix an unreachable bug in which an introduction point could try to
3234 send an INTRODUCE_ACK with a status code that Trunnel would refuse
3235 to encode, leading the relay to assert(). We've consolidated the
3236 ABI values into Trunnel now. Fixes bug 30454; bugfix
3238 - Clients can now handle unknown status codes from INTRODUCE_ACK
3239 cells. (The NACK behavior will stay the same.) This will allow us
3240 to extend status codes in the future without breaking the normal
3241 client behavior. Fixes another part of bug 30454; bugfix
3244 o Minor features (circuit padding):
3245 - We now use a fast PRNG when scheduling circuit padding. Part of
3247 - Allow the padding machine designer to pick the edges of their
3248 histogram instead of trying to compute them automatically using an
3249 exponential formula. Resolves some undefined behavior in the case
3250 of small histograms and allows greater flexibility on machine
3251 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
3252 - Allow circuit padding machines to hold a circuit open until they
3253 are done padding it. Closes ticket 28780.
3255 o Minor features (compile-time modules):
3256 - Add a "--list-modules" command to print a list of which compile-
3257 time modules are enabled. Closes ticket 30452.
3259 o Minor features (continuous integration):
3260 - Remove sudo configuration lines from .travis.yml as they are no
3261 longer needed with current Travis build environment. Resolves
3263 - In Travis, show stem's tor log after failure. Closes ticket 30234.
3265 o Minor features (controller):
3266 - Add onion service version 3 support to the HSFETCH command.
3267 Previously, only version 2 onion services were supported. Closes
3268 ticket 25417. Patch by Neel Chauhan.
3270 o Minor features (debugging):
3271 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
3272 logging of additional information during assert failure. Now we
3273 can use format strings to include information for trouble
3274 shooting. Resolves ticket 29662.
3276 o Minor features (defense in depth):
3277 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
3278 case a bug causes them to be used later. Closes ticket 30176.
3279 Patch from Tobias Stoeckmann.
3280 - Tor now uses a cryptographically strong PRNG even for decisions
3281 that we do not believe are security-sensitive. Previously, for
3282 performance reasons, we had used a trivially predictable linear
3283 congruential generator algorithm for certain load-balancing and
3284 statistical sampling decisions. Now we use our fast RNG in those
3285 cases. Closes ticket 29542.
3287 o Minor features (developer tools):
3288 - Tor's "practracker" test script now checks for files and functions
3289 that seem too long and complicated. Existing overlong functions
3290 and files are accepted for now, but should eventually be
3291 refactored. Closes ticket 29221.
3292 - Add some scripts used for git maintenance to scripts/git. Closes
3294 - Call practracker from pre-push and pre-commit git hooks to let
3295 developers know if they made any code style violations. Closes
3297 - Add a script to check that each header has a well-formed and
3298 unique guard macro. Closes ticket 29756.
3300 o Minor features (geoip):
3301 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
3302 Country database. Closes ticket 30522.
3304 o Minor features (HTTP tunnel):
3305 - Return an informative web page when the HTTPTunnelPort is used as
3306 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
3308 o Minor features (IPv6, v3 onion services):
3309 - Make v3 onion services put IPv6 addresses in service descriptors.
3310 Before this change, service descriptors only contained IPv4
3311 addresses. Implements 26992.
3313 o Minor features (modularity):
3314 - The "--disable-module-dirauth" compile-time option now disables
3315 even more dirauth-only code. Closes ticket 30345.
3317 o Minor features (performance):
3318 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
3319 1.1.1 and later), since they tend to be faster than tiny-keccak.
3320 Closes ticket 28837.
3322 o Minor features (testing):
3323 - Tor's unit test code now contains helper functions to replace the
3324 PRNG with a deterministic or reproducible version for testing.
3325 Previously, various tests implemented this in various ways.
3326 Implements ticket 29732.
3327 - We now have a script, cov-test-determinism.sh, to identify places
3328 where our unit test coverage has become nondeterministic. Closes
3330 - Check that representative subsets of values of `int` and `unsigned
3331 int` can be represented by `void *`. Resolves issue 29537.
3333 o Minor bugfixes (bridge authority):
3334 - Bridge authorities now set bridges as running or non-running when
3335 about to dump their status to a file. Previously, they set bridges
3336 as running in response to a GETINFO command, but those shouldn't
3337 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
3338 Patch by Neel Chauhan.
3340 o Minor bugfixes (channel padding statistics):
3341 - Channel padding write totals and padding-enabled totals are now
3342 counted properly in relay extrainfo descriptors. Fixes bug 29231;
3343 bugfix on 0.3.1.1-alpha.
3345 o Minor bugfixes (circuit padding):
3346 - Add a "CircuitPadding" torrc option to disable circuit padding.
3347 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
3348 - Allow circuit padding machines to specify that they do not
3349 contribute much overhead, and provide consensus flags and torrc
3350 options to force clients to only use these low overhead machines.
3351 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
3352 - Provide a consensus parameter to fully disable circuit padding, to
3353 be used in emergency network overload situations. Fixes bug 30173;
3354 bugfix on 0.4.0.1-alpha.
3355 - The circuit padding subsystem will no longer schedule padding if
3356 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
3357 - Inspect a circuit-level cell queue before sending padding, to
3358 avoid sending padding while too much data is already queued. Fixes
3359 bug 29204; bugfix on 0.4.0.1-alpha.
3360 - Avoid calling monotime_absolute_usec() in circuit padding machines
3361 that do not use token removal or circuit RTT estimation. Fixes bug
3362 29085; bugfix on 0.4.0.1-alpha.
3364 o Minor bugfixes (compilation, unusual configurations):
3365 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
3366 due to missing declarations of abort(), and prevent other such
3367 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
3369 o Minor bugfixes (controller protocol):
3370 - Teach the controller parser to distinguish an object preceded by
3371 an argument list from one without. Previously, it couldn't
3372 distinguish an argument list from the first line of a multiline
3373 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
3375 o Minor bugfixes (directory authority, ipv6):
3376 - Directory authorities with IPv6 support now always mark themselves
3377 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
3378 Patch by Neel Chauhan.
3380 o Minor bugfixes (documentation):
3381 - Improve the documentation for using MapAddress with ".exit". Fixes
3382 bug 30109; bugfix on 0.1.0.1-rc.
3383 - Improve the monotonic time module and function documentation to
3384 explain what "monotonic" actually means, and document some results
3385 that have surprised people. Fixes bug 29640; bugfix
3387 - Use proper formatting when providing an example on quoting options
3388 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
3390 o Minor bugfixes (logging):
3391 - Do not log a warning when running with an OpenSSL version other
3392 than the one Tor was compiled with, if the two versions should be
3393 compatible. Previously, we would warn whenever the version was
3394 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
3395 - Warn operators when the MyFamily option is set but ContactInfo is
3396 missing, as the latter should be set too. Fixes bug 25110; bugfix
3399 o Minor bugfixes (memory leak):
3400 - Avoid a minor memory leak that could occur on relays when failing
3401 to create a "keys" directory. Fixes bug 30148; bugfix
3404 o Minor bugfixes (onion services):
3405 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
3406 implemenation) when failing to load an onion service client
3407 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
3408 - When refusing to launch a controller's HSFETCH request because of
3409 rate-limiting, respond to the controller with a new response,
3410 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
3411 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
3413 - When relaunching a circuit to a rendezvous service, mark the
3414 circuit as needing high-uptime routers as appropriate. Fixes bug
3415 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
3416 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
3417 (IPv6 support for v3 onion services is still incomplete: see
3418 ticket 23493 for details.) Fixes bug 23588; bugfix on
3419 0.3.2.1-alpha. Patch by Neel Chauhan.
3421 o Minor bugfixes (onion services, performance):
3422 - When building circuits to onion services, call tor_addr_parse()
3423 less often. Previously, we called tor_addr_parse() in
3424 circuit_is_acceptable() even if its output wasn't used. This
3425 change should improve performance when building circuits. Fixes
3426 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
3428 o Minor bugfixes (performance):
3429 - When checking whether a node is a bridge, use a fast check to make
3430 sure that its identity is set. Previously, we used a constant-time
3431 check, which is not necessary in this case. Fixes bug 30308;
3432 bugfix on 0.3.5.1-alpha.
3434 o Minor bugfixes (pluggable transports):
3435 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
3436 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
3438 o Minor bugfixes (probability distributions):
3439 - Refactor and improve parts of the probability distribution code
3440 that made Coverity complain. Fixes bug 29805; bugfix
3443 o Minor bugfixes (python):
3444 - Stop assuming that /usr/bin/python3 exists. For scripts that work
3445 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
3446 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
3448 o Minor bugfixes (relay):
3449 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
3450 is auto, act as if ExitRelay is 1. Previously, we would ignore
3451 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
3452 0.3.5.1-alpha. Patch by Neel Chauhan.
3454 o Minor bugfixes (stats):
3455 - When ExtraInfoStatistics is 0, stop including bandwidth usage
3456 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
3457 bridge statistics by country in extra-info documents. Fixes bug
3458 29018; bugfix on 0.2.4.1-alpha.
3460 o Minor bugfixes (testing):
3461 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
3462 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
3463 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
3464 - Fix some incorrect code in the v3 onion service unit tests. Fixes
3465 bug 29243; bugfix on 0.3.2.1-alpha.
3466 - In the "routerkeys/*" tests, check the return values of mkdir()
3467 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
3468 Found by Coverity as CID 1444254.
3469 - Split test_utils_general() into several smaller test functions.
3470 This makes it easier to perform resource deallocation on assert
3471 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
3472 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
3474 o Minor bugfixes (tor-resolve):
3475 - Fix a memory leak in tor-resolve that could happen if Tor gave it
3476 a malformed SOCKS response. (Memory leaks in tor-resolve don't
3477 actually matter, but it's good to fix them anyway.) Fixes bug
3478 30151; bugfix on 0.4.0.1-alpha.
3480 o Code simplification and refactoring:
3481 - Abstract out the low-level formatting of replies on the control
3482 port. Implements ticket 30007.
3483 - Add several assertions in an attempt to fix some Coverity
3484 warnings. Closes ticket 30149.
3485 - Introduce a connection_dir_buf_add() helper function that checks
3486 for compress_state of dir_connection_t and automatically writes a
3487 string to directory connection with or without compression.
3488 Resolves issue 28816.
3489 - Make the base32_decode() API return the number of bytes written,
3490 for consistency with base64_decode(). Closes ticket 28913.
3491 - Move most relay-only periodic events out of mainloop.c into the
3492 relay subsystem. Closes ticket 30414.
3493 - Refactor and encapsulate parts of the codebase that manipulate
3494 crypt_path_t objects. Resolves issue 30236.
3495 - Refactor several places in our code that Coverity incorrectly
3496 believed might have memory leaks. Closes ticket 30147.
3497 - Remove redundant return values in crypto_format, and the
3498 associated return value checks elsewhere in the code. Make the
3499 implementations in crypto_format consistent, and remove redundant
3500 code. Resolves ticket 29660.
3501 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
3502 it is not a constant-time function. Closes ticket 30309.
3503 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
3504 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
3505 bugfix on 0.3.2.1-alpha.
3506 - Simplify v3 onion service link specifier handling code. Fixes bug
3507 23576; bugfix on 0.3.2.1-alpha.
3508 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
3509 code. Resolves ticket 29108.
3510 - Split control.c into several submodules, in preparation for
3511 distributing its current responsibilities throughout the codebase.
3512 Closes ticket 29894.
3513 - Start to move responsibility for knowing about periodic events to
3514 the appropriate subsystems, so that the mainloop doesn't need to
3515 know all the periodic events in the rest of the codebase.
3516 Implements tickets 30293 and 30294.
3519 - Document how to find git commits and tags for bug fixes in
3520 CodingStandards.md. Update some file documentation. Closes
3524 - Remove the linux-tor-prio.sh script from contrib/operator-tools
3525 directory. Resolves issue 29434.
3526 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
3527 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
3530 o Code simplification and refactoring (shell scripts):
3531 - Clean up many of our shell scripts to fix shellcheck warnings.
3532 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
3533 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
3534 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
3535 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
3536 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
3537 nagios-check-tor-authority-cert (ticket 29071),
3538 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
3539 (ticket 29060), test_key_expiration.sh (ticket 30002),
3540 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
3543 o Testing (chutney):
3544 - In "make test-network-all", test IPv6-only v3 single onion
3545 services, using the chutney network single-onion-v23-ipv6-md.
3546 Closes ticket 27251.
3549 Changes in version 0.4.0.5 - 2019-05-02
3550 This is the first stable release in the 0.4.0.x series. It contains
3551 improvements for power management and bootstrap reporting, as well as
3552 preliminary backend support for circuit padding to prevent some kinds
3553 of traffic analysis. It also continues our work in refactoring Tor for
3554 long-term maintainability.
3556 Per our support policy, we will support the 0.4.0.x series for nine
3557 months, or until three months after the release of a stable 0.4.1.x:
3558 whichever is longer. If you need longer-term support, please stick
3559 with 0.3.5.x, which will we plan to support until Feb 2022.
3561 Below are the changes since 0.4.0.4-rc. For a complete list of changes
3562 since 0.3.5.7, see the ReleaseNotes file.
3564 o Minor features (continuous integration):
3565 - In Travis, tell timelimit to use stem's backtrace signals, and
3566 launch python directly from timelimit, so python receives the
3567 signals from timelimit, rather than make. Closes ticket 30117.
3569 o Minor features (diagnostic):
3570 - Add more diagnostic log messages in an attempt to solve the issue
3571 of NUL bytes appearing in a microdescriptor cache. Related to
3574 o Minor features (testing):
3575 - Use the approx_time() function when setting the "Expires" header
3576 in directory replies, to make them more testable. Needed for
3579 o Minor bugfixes (rust):
3580 - Abort on panic in all build profiles, instead of potentially
3581 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
3583 o Minor bugfixes (shellcheck):
3584 - Look for scripts in their correct locations during "make
3585 shellcheck". Previously we had looked in the wrong place during
3586 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
3588 o Minor bugfixes (testing):
3589 - Check the time in the "Expires" header using approx_time(). Fixes
3590 bug 30001; bugfix on 0.4.0.4-rc.
3592 o Minor bugfixes (UI):
3593 - Lower log level of unlink() errors during bootstrap. Fixes bug
3594 29930; bugfix on 0.4.0.1-alpha.
3597 Changes in version 0.4.0.4-rc - 2019-04-11
3598 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
3599 several bugs from earlier versions, including some that had affected
3600 stability, and one that prevented relays from working with NSS.
3602 o Major bugfixes (NSS, relay):
3603 - When running with NSS, disable TLS 1.2 ciphersuites that use
3604 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
3605 these ciphersuites don't work -- which caused relays to fail to
3606 handshake with one another when these ciphersuites were enabled.
3607 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
3609 o Minor features (bandwidth authority):
3610 - Make bandwidth authorities ignore relays that are reported in the
3611 bandwidth file with the flag "vote=0". This change allows us to
3612 report unmeasured relays for diagnostic reasons without including
3613 their bandwidth in the bandwidth authorities' vote. Closes
3615 - When a directory authority is using a bandwidth file to obtain the
3616 bandwidth values that will be included in the next vote, serve
3617 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
3620 o Minor features (circuit padding):
3621 - Stop warning about undefined behavior in the probability
3622 distribution tests. Float division by zero may technically be
3623 undefined behavior in C, but it's well defined in IEEE 754.
3624 Partial backport of 29298. Closes ticket 29527; bugfix
3627 o Minor features (continuous integration):
3628 - On Travis Rust builds, cleanup Rust registry and refrain from
3629 caching the "target/" directory to speed up builds. Resolves
3632 o Minor features (dormant mode):
3633 - Add a DormantCanceledByStartup option to tell Tor that it should
3634 treat a startup event as cancelling any previous dormant state.
3635 Integrators should use this option with caution: it should only be
3636 used if Tor is being started because of something that the user
3637 did, and not if Tor is being automatically started in the
3638 background. Closes ticket 29357.
3640 o Minor features (geoip):
3641 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
3642 Country database. Closes ticket 29992.
3644 o Minor features (NSS, diagnostic):
3645 - Try to log an error from NSS (if there is any) and a more useful
3646 description of our situation if we are using NSS and a call to
3647 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
3649 o Minor bugfixes (security):
3650 - Fix a potential double free bug when reading huge bandwidth files.
3651 The issue is not exploitable in the current Tor network because
3652 the vulnerable code is only reached when directory authorities
3653 read bandwidth files, but bandwidth files come from a trusted
3654 source (usually the authorities themselves). Furthermore, the
3655 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
3656 which are not used by any of the current authorities. Fixes bug
3657 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
3659 - Verify in more places that we are not about to create a buffer
3660 with more than INT_MAX bytes, to avoid possible OOB access in the
3661 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
3662 fixed by Tobias Stoeckmann.
3664 o Minor bugfix (continuous integration):
3665 - Reset coverage state on disk after Travis CI has finished. This
3666 should prevent future coverage merge errors from causing the test
3667 suite for the "process" subsystem to fail. The process subsystem
3668 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
3670 - Terminate test-stem if it takes more than 9.5 minutes to run.
3671 (Travis terminates the job after 10 minutes of no output.)
3672 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
3674 o Minor bugfixes (bootstrap reporting):
3675 - During bootstrap reporting, correctly distinguish pluggable
3676 transports from plain proxies. Fixes bug 28925; bugfix
3679 o Minor bugfixes (C correctness):
3680 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
3681 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
3684 o Minor bugfixes (circuitpadding testing):
3685 - Minor tweaks to avoid rare test failures related to timers and
3686 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
3688 o Minor bugfixes (directory authorities):
3689 - Actually include the bandwidth-file-digest line in directory
3690 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
3692 o Minor bugfixes (logging):
3693 - On Windows, when errors cause us to reload a consensus from disk,
3694 tell the user that we are retrying at log level "notice".
3695 Previously we only logged this information at "info", which was
3696 confusing because the errors themselves were logged at "warning".
3697 Improves previous fix for 28614. Fixes bug 30004; bugfix
3700 o Minor bugfixes (pluggable transports):
3701 - Restore old behavior when it comes to discovering the path of a
3702 given Pluggable Transport executable file. A change in
3703 0.4.0.1-alpha had broken this behavior on paths containing a
3704 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
3706 o Minor bugfixes (testing):
3707 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
3708 recent test-network.sh to use new chutney features in CI. Fixes
3709 bug 29703; bugfix on 0.2.9.1-alpha.
3710 - Fix a test failure on Windows caused by an unexpected "BUG"
3711 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
3714 o Minor bugfixes (TLS protocol):
3715 - When classifying a client's selection of TLS ciphers, if the
3716 client ciphers are not yet available, do not cache the result.
3717 Previously, we had cached the unavailability of the cipher list
3718 and never looked again, which in turn led us to assume that the
3719 client only supported the ancient V1 link protocol. This, in turn,
3720 was causing Stem integration tests to stall in some cases. Fixes
3721 bug 30021; bugfix on 0.2.4.8-alpha.
3723 o Code simplification and refactoring:
3724 - Introduce a connection_dir_buf_add() helper function that detects
3725 whether compression is in use, and adds a string accordingly.
3726 Resolves issue 28816.
3727 - Refactor handle_get_next_bandwidth() to use
3728 connection_dir_buf_add(). Implements ticket 29897.
3731 - Clarify that Tor performs stream isolation among *Port listeners
3732 by default. Resolves issue 29121.
3735 Changes in version 0.4.0.3-alpha - 2019-03-22
3736 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
3737 bugs from earlier versions.
3739 o Minor features (address selection):
3740 - Treat the subnet 100.64.0.0/10 as public for some purposes;
3741 private for others. This subnet is the RFC 6598 (Carrier Grade
3742 NAT) IP range, and is deployed by many ISPs as an alternative to
3743 RFC 1918 that does not break existing internal networks. Tor now
3744 blocks SOCKS and control ports on these addresses and warns users
3745 if client ports or ExtORPorts are listening on a RFC 6598 address.
3746 Closes ticket 28525. Patch by Neel Chauhan.
3748 o Minor features (geoip):
3749 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
3750 Country database. Closes ticket 29666.
3752 o Minor bugfixes (circuitpadding):
3753 - Inspect the circuit-level cell queue before sending padding, to
3754 avoid sending padding when too much data is queued. Fixes bug
3755 29204; bugfix on 0.4.0.1-alpha.
3757 o Minor bugfixes (logging):
3758 - Correct a misleading error message when IPv4Only or IPv6Only is
3759 used but the resolved address can not be interpreted as an address
3760 of the specified IP version. Fixes bug 13221; bugfix on
3761 0.2.3.9-alpha. Patch from Kris Katterjohn.
3762 - Log the correct port number for listening sockets when "auto" is
3763 used to let Tor pick the port number. Previously, port 0 was
3764 logged instead of the actual port number. Fixes bug 29144; bugfix
3765 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3766 - Stop logging a BUG() warning when Tor is waiting for exit
3767 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
3769 o Minor bugfixes (memory management):
3770 - Refactor the shared random state's memory management so that it
3771 actually takes ownership of the shared random value pointers.
3772 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
3774 o Minor bugfixes (memory management, testing):
3775 - Stop leaking parts of the shared random state in the shared-random
3776 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
3778 o Minor bugfixes (pluggable transports):
3779 - Fix an assertion failure crash bug when a pluggable transport is
3780 terminated during the bootstrap phase. Fixes bug 29562; bugfix
3783 o Minor bugfixes (Rust, protover):
3784 - Add a missing "Padding" value to the Rust implementation of
3785 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
3787 o Minor bugfixes (single onion services):
3788 - Allow connections to single onion services to remain idle without
3789 being disconnected. Previously, relays acting as rendezvous points
3790 for single onion services were mistakenly closing idle rendezvous
3791 circuits after 60 seconds, thinking that they were unused
3792 directory-fetching circuits that had served their purpose. Fixes
3793 bug 29665; bugfix on 0.2.1.26.
3795 o Minor bugfixes (stats):
3796 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
3797 relay and bridge extra-info documents. Fixes bug 29017; bugfix
3800 o Minor bugfixes (testing):
3801 - Downgrade some LOG_ERR messages in the address/* tests to
3802 warnings. The LOG_ERR messages were occurring when we had no
3803 configured network. We were failing the unit tests, because we
3804 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
3805 29530; bugfix on 0.3.5.8.
3806 - Fix our gcov wrapper script to look for object files at the
3807 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
3808 - Decrease the false positive rate of stochastic probability
3809 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
3811 o Minor bugfixes (Windows, CI):
3812 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
3813 Windows Server 2012 R2 job. The remaining 2 jobs still provide
3814 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
3815 fast_finish, so failed jobs terminate the build immediately. Fixes
3816 bug 29601; bugfix on 0.3.5.4-alpha.
3819 Changes in version 0.3.5.8 - 2019-02-21
3820 Tor 0.3.5.8 backports several fixes from later releases, including fixes
3821 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
3824 It also includes a fix for a medium-severity security bug affecting Tor
3825 0.3.2.1-alpha and later. All Tor instances running an affected release
3826 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3828 o Major bugfixes (cell scheduler, KIST, security):
3829 - Make KIST consider the outbuf length when computing what it can
3830 put in the outbuf. Previously, KIST acted as though the outbuf
3831 were empty, which could lead to the outbuf becoming too full. It
3832 is possible that an attacker could exploit this bug to cause a Tor
3833 client or relay to run out of memory and crash. Fixes bug 29168;
3834 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3835 TROVE-2019-001 and CVE-2019-8955.
3837 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
3838 - Gracefully handle empty username/password fields in SOCKS5
3839 username/password auth message and allow SOCKS5 handshake to
3840 continue. Previously, we had rejected these handshakes, breaking
3841 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
3843 o Minor features (compilation, backport from 0.4.0.2-alpha):
3844 - Compile correctly when OpenSSL is built with engine support
3845 disabled, or with deprecated APIs disabled. Closes ticket 29026.
3846 Patches from "Mangix".
3848 o Minor features (geoip):
3849 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3850 Country database. Closes ticket 29478.
3852 o Minor features (testing, backport from 0.4.0.2-alpha):
3853 - Treat all unexpected ERR and BUG messages as test failures. Closes
3856 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
3857 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
3858 connection waiting for a descriptor that we actually have in the
3859 cache. It turns out that this can actually happen, though it is
3860 rare. Now, tor will recover and retry the descriptor. Fixes bug
3861 28669; bugfix on 0.3.2.4-alpha.
3863 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
3864 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
3865 IPv6 socket was bound using an address family of AF_INET instead
3866 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
3869 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3870 - Update Cargo.lock file to match the version made by the latest
3871 version of Rust, so that "make distcheck" will pass again. Fixes
3872 bug 29244; bugfix on 0.3.3.4-alpha.
3874 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
3875 - Select guards even if the consensus has expired, as long as the
3876 consensus is still reasonably live. Fixes bug 24661; bugfix
3879 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
3880 - Compile correctly on OpenBSD; previously, we were missing some
3881 headers required in order to detect it properly. Fixes bug 28938;
3882 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
3884 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
3885 - Describe the contents of the v3 onion service client authorization
3886 files correctly: They hold public keys, not private keys. Fixes
3887 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
3889 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
3890 - Rework rep_hist_log_link_protocol_counts() to iterate through all
3891 link protocol versions when logging incoming/outgoing connection
3892 counts. Tor no longer skips version 5, and we won't have to
3893 remember to update this function when new link protocol version is
3894 developed. Fixes bug 28920; bugfix on 0.2.6.10.
3896 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
3897 - Log more information at "warning" level when unable to read a
3898 private key; log more information at "info" level when unable to
3899 read a public key. We had warnings here before, but they were lost
3900 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
3902 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
3903 - The amount of total available physical memory is now determined
3904 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
3905 when it is defined and a 64-bit variant is not available. Fixes
3906 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
3908 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3909 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
3910 than one private key for a hidden service. Fixes bug 29040; bugfix
3912 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
3913 "debug" level. Tor used to log it as a warning, which caused very
3914 long log lines to appear for some users. Fixes bug 29135; bugfix
3916 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3917 as a warning. Instead, log it as a protocol warning, because there
3918 is nothing that relay operators can do to fix it. Fixes bug 29029;
3919 bugfix on 0.2.5.7-rc.
3921 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
3922 - Mark outdated dirservers when Tor only has a reasonably live
3923 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
3925 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
3926 - Detect and suppress "bug" warnings from the util/time test on
3927 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
3928 - Do not log an error-level message if we fail to find an IPv6
3929 network interface from the unit tests. Fixes bug 29160; bugfix
3932 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
3933 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
3934 Some users took this phrasing to mean that the mentioned guard was
3935 under their control or responsibility, which it is not. Fixes bug
3936 28895; bugfix on Tor 0.3.0.1-alpha.
3939 Changes in version 0.3.4.11 - 2019-02-21
3940 Tor 0.3.4.11 is the third stable release in its series. It includes
3941 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
3942 later. All Tor instances running an affected release should upgrade to
3943 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3945 o Major bugfixes (cell scheduler, KIST, security):
3946 - Make KIST consider the outbuf length when computing what it can
3947 put in the outbuf. Previously, KIST acted as though the outbuf
3948 were empty, which could lead to the outbuf becoming too full. It
3949 is possible that an attacker could exploit this bug to cause a Tor
3950 client or relay to run out of memory and crash. Fixes bug 29168;
3951 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3952 TROVE-2019-001 and CVE-2019-8955.
3954 o Minor features (geoip):
3955 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3956 Country database. Closes ticket 29478.
3958 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3959 - Update Cargo.lock file to match the version made by the latest
3960 version of Rust, so that "make distcheck" will pass again. Fixes
3961 bug 29244; bugfix on 0.3.3.4-alpha.
3963 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3964 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
3965 as a warning. Instead, log it as a protocol warning, because there
3966 is nothing that relay operators can do to fix it. Fixes bug 29029;
3967 bugfix on 0.2.5.7-rc.
3970 Changes in version 0.3.3.12 - 2019-02-21
3971 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
3972 0.3.2.1-alpha and later. All Tor instances running an affected release
3973 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
3975 This release marks the end of support for the Tor 0.3.3.x series. We
3976 recommend that users switch to either the Tor 0.3.4 series (supported
3977 until at least 10 June 2019), or the Tor 0.3.5 series, which will
3978 receive long-term support until at least 1 Feb 2022.
3980 o Major bugfixes (cell scheduler, KIST, security):
3981 - Make KIST consider the outbuf length when computing what it can
3982 put in the outbuf. Previously, KIST acted as though the outbuf
3983 were empty, which could lead to the outbuf becoming too full. It
3984 is possible that an attacker could exploit this bug to cause a Tor
3985 client or relay to run out of memory and crash. Fixes bug 29168;
3986 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
3987 TROVE-2019-001 and CVE-2019-8955.
3989 o Minor features (geoip):
3990 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
3991 Country database. Closes ticket 29478.
3993 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
3994 - Update Cargo.lock file to match the version made by the latest
3995 version of Rust, so that "make distcheck" will pass again. Fixes
3996 bug 29244; bugfix on 0.3.3.4-alpha.
3998 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
3999 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4000 as a warning. Instead, log it as a protocol warning, because there
4001 is nothing that relay operators can do to fix it. Fixes bug 29029;
4002 bugfix on 0.2.5.7-rc.
4005 Changes in version 0.4.0.2-alpha - 2019-02-21
4006 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
4007 bugs from earlier versions, including several that had broken
4008 backward compatibility.
4010 It also includes a fix for a medium-severity security bug affecting Tor
4011 0.3.2.1-alpha and later. All Tor instances running an affected release
4012 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
4014 o Major bugfixes (cell scheduler, KIST, security):
4015 - Make KIST consider the outbuf length when computing what it can
4016 put in the outbuf. Previously, KIST acted as though the outbuf
4017 were empty, which could lead to the outbuf becoming too full. It
4018 is possible that an attacker could exploit this bug to cause a Tor
4019 client or relay to run out of memory and crash. Fixes bug 29168;
4020 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
4021 TROVE-2019-001 and CVE-2019-8955.
4023 o Major bugfixes (networking):
4024 - Gracefully handle empty username/password fields in SOCKS5
4025 username/password auth messsage and allow SOCKS5 handshake to
4026 continue. Previously, we had rejected these handshakes, breaking
4027 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
4029 o Major bugfixes (windows, startup):
4030 - When reading a consensus file from disk, detect whether it was
4031 written in text mode, and re-read it in text mode if so. Always
4032 write consensus files in binary mode so that we can map them into
4033 memory later. Previously, we had written in text mode, which
4034 confused us when we tried to map the file on windows. Fixes bug
4035 28614; bugfix on 0.4.0.1-alpha.
4037 o Minor features (compilation):
4038 - Compile correctly when OpenSSL is built with engine support
4039 disabled, or with deprecated APIs disabled. Closes ticket 29026.
4040 Patches from "Mangix".
4042 o Minor features (developer tooling):
4043 - Check that bugfix versions in changes files look like Tor versions
4044 from the versions spec. Warn when bugfixes claim to be on a future
4045 release. Closes ticket 27761.
4046 - Provide a git pre-commit hook that disallows committing if we have
4047 any failures in our code and changelog formatting checks. It is
4048 now available in scripts/maint/pre-commit.git-hook. Implements
4051 o Minor features (directory authority):
4052 - When a directory authority is using a bandwidth file to obtain
4053 bandwidth values, include the digest of that file in the vote.
4054 Closes ticket 26698.
4056 o Minor features (geoip):
4057 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
4058 Country database. Closes ticket 29478.
4060 o Minor features (testing):
4061 - Treat all unexpected ERR and BUG messages as test failures. Closes
4064 o Minor bugfixes (build, compatibility, rust):
4065 - Update Cargo.lock file to match the version made by the latest
4066 version of Rust, so that "make distcheck" will pass again. Fixes
4067 bug 29244; bugfix on 0.3.3.4-alpha.
4069 o Minor bugfixes (compilation):
4070 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
4071 29169; bugfix on 0.4.0.1-alpha.
4072 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
4073 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
4075 o Minor bugfixes (documentation):
4076 - Describe the contents of the v3 onion service client authorization
4077 files correctly: They hold public keys, not private keys. Fixes
4078 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
4080 o Minor bugfixes (linux seccomp sandbox):
4081 - Fix startup crash when experimental sandbox support is enabled.
4082 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
4084 o Minor bugfixes (logging):
4085 - Avoid logging that we are relaxing a circuit timeout when that
4086 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
4087 - Log more information at "warning" level when unable to read a
4088 private key; log more information at "info" level when unable to
4089 read a public key. We had warnings here before, but they were lost
4090 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
4092 o Minor bugfixes (misc):
4093 - The amount of total available physical memory is now determined
4094 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
4095 when it is defined and a 64-bit variant is not available. Fixes
4096 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
4098 o Minor bugfixes (onion services):
4099 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
4100 than one private key for a hidden service. Fixes bug 29040; bugfix
4102 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
4103 "debug" level. Tor used to log it as a warning, which caused very
4104 long log lines to appear for some users. Fixes bug 29135; bugfix
4106 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
4107 as a warning. Instead, log it as a protocol warning, because there
4108 is nothing that relay operators can do to fix it. Fixes bug 29029;
4109 bugfix on 0.2.5.7-rc.
4111 o Minor bugfixes (scheduler):
4112 - When re-adding channels to the pending list, check the correct
4113 channel's sched_heap_idx. This issue has had no effect in mainline
4114 Tor, but could have led to bugs down the road in improved versions
4115 of our circuit scheduling code. Fixes bug 29508; bugfix
4118 o Minor bugfixes (tests):
4119 - Fix intermittent failures on an adaptive padding test. Fixes one
4120 case of bug 29122; bugfix on 0.4.0.1-alpha.
4121 - Disable an unstable circuit-padding test that was failing
4122 intermittently because of an ill-defined small histogram. Such
4123 histograms will be allowed again after 29298 is implemented. Fixes
4124 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
4125 - Detect and suppress "bug" warnings from the util/time test on
4126 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
4127 - Do not log an error-level message if we fail to find an IPv6
4128 network interface from the unit tests. Fixes bug 29160; bugfix
4132 - In the manpage entry describing MapAddress torrc setting, use
4133 example IP addresses from ranges specified for use in documentation
4134 by RFC 5737. Resolves issue 28623.
4137 - Remove the old check-tor script. Resolves issue 29072.
4140 Changes in version 0.4.0.1-alpha - 2019-01-18
4141 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
4142 introduces improved features for power and bandwidth conservation,
4143 more accurate reporting of bootstrap progress for user interfaces, and
4144 an experimental backend for an exciting new adaptive padding feature.
4145 There is also the usual assortment of bugfixes and minor features, all
4148 o Major features (battery management, client, dormant mode):
4149 - When Tor is running as a client, and it is unused for a long time,
4150 it can now enter a "dormant" state. When Tor is dormant, it avoids
4151 network and CPU activity until it is reawoken either by a user
4152 request or by a controller command. For more information, see the
4153 configuration options starting with "Dormant". Implements tickets
4155 - The client's memory of whether it is "dormant", and how long it
4156 has spent idle, persists across invocations. Implements
4158 - There is a DormantOnFirstStartup option that integrators can use
4159 if they expect that in many cases, Tor will be installed but
4162 o Major features (bootstrap reporting):
4163 - When reporting bootstrap progress, report the first connection
4164 uniformly, regardless of whether it's a connection for building
4165 application circuits. This allows finer-grained reporting of early
4166 progress than previously possible, with the improvements of ticket
4167 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
4168 - When reporting bootstrap progress, treat connecting to a proxy or
4169 pluggable transport as separate from having successfully used that
4170 proxy or pluggable transport to connect to a relay. Closes tickets
4173 o Major features (circuit padding):
4174 - Implement preliminary support for the circuit padding portion of
4175 Proposal 254. The implementation supports Adaptive Padding (aka
4176 WTF-PAD) state machines for use between experimental clients and
4177 relays. Support is also provided for APE-style state machines that
4178 use probability distributions instead of histograms to specify
4179 inter-packet delay. At the moment, Tor does not provide any
4180 padding state machines that are used in normal operation: for now,
4181 this feature exists solely for experimentation. Closes
4184 o Major features (refactoring):
4185 - Tor now uses an explicit list of its own subsystems when
4186 initializing and shutting down. Previously, these systems were
4187 managed implicitly in various places throughout the codebase.
4188 (There may still be some subsystems using the old system.) Closes
4191 o Minor features (bootstrap reporting):
4192 - When reporting bootstrap progress, stop distinguishing between
4193 situations where only internal paths are available and situations
4194 where external paths are available. Previously, Tor would often
4195 erroneously report that it had only internal paths. Closes
4198 o Minor features (continuous integration):
4199 - Log Python version during each Travis CI job. Resolves
4202 o Minor features (controller):
4203 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
4204 Implements ticket 28843.
4206 o Minor features (developer tooling):
4207 - Provide a git hook script to prevent "fixup!" and "squash!"
4208 commits from ending up in the master branch, as scripts/main/pre-
4209 push.git-hook. Closes ticket 27993.
4211 o Minor features (directory authority):
4212 - Directory authorities support a new consensus algorithm, under
4213 which the family lines in microdescriptors are encoded in a
4214 canonical form. This change makes family lines more compressible
4215 in transit, and on the client. Closes ticket 28266; implements
4218 o Minor features (directory authority, relay):
4219 - Authorities now vote on a "StaleDesc" flag to indicate that a
4220 relay's descriptor is so old that the relay should upload again
4221 soon. Relays treat this flag as a signal to upload a new
4222 descriptor. This flag will eventually let us remove the
4223 'published' date from routerstatus entries, and make our consensus
4224 diffs much smaller. Closes ticket 26770; implements proposal 293.
4226 o Minor features (fallback directory mirrors):
4227 - Update the fallback whitelist based on operator opt-ins and opt-
4228 outs. Closes ticket 24805, patch by Phoul.
4230 o Minor features (FreeBSD):
4231 - On FreeBSD-based systems, warn relay operators if the
4232 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
4233 Closes ticket 28518.
4235 o Minor features (HTTP standards compliance):
4236 - Stop sending the header "Content-type: application/octet-stream"
4237 along with transparently compressed documents: this confused
4238 browsers. Closes ticket 28100.
4240 o Minor features (IPv6):
4241 - We add an option ClientAutoIPv6ORPort, to make clients randomly
4242 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
4243 every time a node is loaded from a new consensus or bridge config.
4244 We expect that this option will enable clients to bootstrap more
4245 quickly without having to determine whether they support IPv4,
4246 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
4247 - When using addrs_in_same_network_family(), avoid choosing circuit
4248 paths that pass through the same IPv6 subnet more than once.
4249 Previously, we only checked IPv4 subnets. Closes ticket 24393.
4250 Patch by Neel Chauhan.
4252 o Minor features (log messages):
4253 - Improve log message in v3 onion services that could print out
4254 negative revision counters. Closes ticket 27707. Patch
4257 o Minor features (memory usage):
4258 - Save memory by storing microdescriptor family lists with a more
4259 compact representation. Closes ticket 27359.
4260 - Tor clients now use mmap() to read consensus files from disk, so
4261 that they no longer need keep the full text of a consensus in
4262 memory when parsing it or applying a diff. Closes ticket 27244.
4264 o Minor features (parsing):
4265 - Directory authorities now validate that router descriptors and
4266 ExtraInfo documents are in a valid subset of UTF-8, and reject
4267 them if they are not. Closes ticket 27367.
4269 o Minor features (performance):
4270 - Cache the results of summarize_protocol_flags(), so that we don't
4271 have to parse the same protocol-versions string over and over.
4272 This should save us a huge number of malloc calls on startup, and
4273 may reduce memory fragmentation with some allocators. Closes
4275 - Remove a needless memset() call from get_token_arguments, thereby
4276 speeding up the tokenization of directory objects by about 20%.
4277 Closes ticket 28852.
4278 - Replace parse_short_policy() with a faster implementation, to
4279 improve microdescriptor parsing time. Closes ticket 28853.
4280 - Speed up directory parsing a little by avoiding use of the non-
4281 inlined strcmp_len() function. Closes ticket 28856.
4282 - Speed up microdescriptor parsing by about 30%, to help improve
4283 startup time. Closes ticket 28839.
4285 o Minor features (pluggable transports):
4286 - Add support for emitting STATUS updates to Tor's control port from
4287 a pluggable transport process. Closes ticket 28846.
4288 - Add support for logging to Tor's logging subsystem from a
4289 pluggable transport process. Closes ticket 28180.
4291 o Minor features (process management):
4292 - Add a new process API for handling child processes. This new API
4293 allows Tor to have bi-directional communication with child
4294 processes on both Unix and Windows. Closes ticket 28179.
4295 - Use the subsystem manager to initialize and shut down the process
4296 module. Closes ticket 28847.
4298 o Minor features (relay):
4299 - When listing relay families, list them in canonical form including
4300 the relay's own identity, and try to give a more useful set of
4301 warnings. Part of ticket 28266 and proposal 298.
4303 o Minor features (required protocols):
4304 - Before exiting because of a missing required protocol, Tor will
4305 now check the publication time of the consensus, and not exit
4306 unless the consensus is newer than the Tor program's own release
4307 date. Previously, Tor would not check the consensus publication
4308 time, and so might exit because of a missing protocol that might
4309 no longer be required in a current consensus. Implements proposal
4310 297; closes ticket 27735.
4312 o Minor features (testing):
4313 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
4314 networks. Closes ticket 28840. Patch by Rob Jansen.
4316 o Minor bugfixes (client, clock skew):
4317 - Bootstrap successfully even when Tor's clock is behind the clocks
4318 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
4319 - Select guards even if the consensus has expired, as long as the
4320 consensus is still reasonably live. Fixes bug 24661; bugfix
4323 o Minor bugfixes (compilation):
4324 - Compile correctly on OpenBSD; previously, we were missing some
4325 headers required in order to detect it properly. Fixes bug 28938;
4326 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
4328 o Minor bugfixes (directory clients):
4329 - Mark outdated dirservers when Tor only has a reasonably live
4330 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
4332 o Minor bugfixes (directory mirrors):
4333 - Even when a directory mirror's clock is behind the clocks on the
4334 authorities, we now allow the mirror to serve "future"
4335 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
4337 o Minor bugfixes (DNS):
4338 - Gracefully handle an empty or absent resolve.conf file by falling
4339 back to using "localhost" as a DNS server (and hoping it works).
4340 Previously, we would just stop running as an exit. Fixes bug
4341 21900; bugfix on 0.2.1.10-alpha.
4343 o Minor bugfixes (guards):
4344 - In count_acceptable_nodes(), the minimum number is now one bridge
4345 or guard node, and two non-guard nodes for a circuit. Previously,
4346 we had added up the sum of all nodes with a descriptor, but that
4347 could cause us to build failing circuits when we had either too
4348 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
4349 0.2.3.1-alpha. Patch by Neel Chauhan.
4351 o Minor bugfixes (IPv6):
4352 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
4353 IPv6 socket was bound using an address family of AF_INET instead
4354 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
4357 o Minor bugfixes (logging):
4358 - Rework rep_hist_log_link_protocol_counts() to iterate through all
4359 link protocol versions when logging incoming/outgoing connection
4360 counts. Tor no longer skips version 5, and we won't have to
4361 remember to update this function when new link protocol version is
4362 developed. Fixes bug 28920; bugfix on 0.2.6.10.
4364 o Minor bugfixes (networking):
4365 - Introduce additional checks into tor_addr_parse() to reject
4366 certain incorrect inputs that previously were not detected. Fixes
4367 bug 23082; bugfix on 0.2.0.10-alpha.
4369 o Minor bugfixes (onion service v3, client):
4370 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
4371 connection waiting for a descriptor that we actually have in the
4372 cache. It turns out that this can actually happen, though it is
4373 rare. Now, tor will recover and retry the descriptor. Fixes bug
4374 28669; bugfix on 0.3.2.4-alpha.
4376 o Minor bugfixes (periodic events):
4377 - Refrain from calling routerlist_remove_old_routers() from
4378 check_descriptor_callback(). Instead, create a new hourly periodic
4379 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
4381 o Minor bugfixes (pluggable transports):
4382 - Make sure that data is continously read from standard output and
4383 standard error pipes of a pluggable transport child-process, to
4384 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
4385 bugfix on 0.2.3.6-alpha.
4387 o Minor bugfixes (unit tests):
4388 - Instead of relying on hs_free_all() to clean up all onion service
4389 objects in test_build_descriptors(), we now deallocate them one by
4390 one. This lets Coverity know that we are not leaking memory there
4391 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
4393 o Minor bugfixes (usability):
4394 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
4395 Some users took this phrasing to mean that the mentioned guard was
4396 under their control or responsibility, which it is not. Fixes bug
4397 28895; bugfix on Tor 0.3.0.1-alpha.
4399 o Code simplification and refactoring:
4400 - Reimplement NETINFO cell parsing and generation to rely on
4401 trunnel-generated wire format handling code. Closes ticket 27325.
4402 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
4404 - Rework SOCKS wire format handling to rely on trunnel-generated
4405 parsing/generation code. Resolves ticket 27620.
4406 - Split out bootstrap progress reporting from control.c into a
4407 separate file. Part of ticket 27402.
4408 - The .may_include files that we use to describe our directory-by-
4409 directory dependency structure now describe a noncircular
4410 dependency graph over the directories that they cover. Our
4411 checkIncludes.py tool now enforces this noncircularity. Closes
4415 - Mention that you cannot add a new onion service if Tor is already
4416 running with Sandbox enabled. Closes ticket 28560.
4417 - Improve ControlPort documentation. Mention that it accepts
4418 address:port pairs, and can be used multiple times. Closes
4420 - Document the exact output of "tor --version". Closes ticket 28889.
4423 - Stop responding to the 'GETINFO status/version/num-concurring' and
4424 'GETINFO status/version/num-versioning' control port commands, as
4425 those were deprecated back in 0.2.0.30. Also stop listing them in
4426 output of 'GETINFO info/names'. Resolves ticket 28757.
4427 - The scripts used to generate and maintain the list of fallback
4428 directories have been extracted into a new "fallback-scripts"
4429 repository. Closes ticket 27914.
4432 - Run shellcheck for scripts in the in scripts/ directory. Closes
4434 - Add unit tests for tokenize_string() and get_next_token()
4435 functions. Resolves ticket 27625.
4437 o Code simplification and refactoring (onion service v3):
4438 - Consolidate the authorized client descriptor cookie computation
4439 code from client and service into one function. Closes
4442 o Code simplification and refactoring (shell scripts):
4443 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
4445 - Fix issues that shellcheck found in chutney-git-bisect.sh.
4446 Resolves ticket 28006.
4447 - Fix issues that shellcheck found in updateRustDependencies.sh.
4448 Resolves ticket 28012.
4449 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
4450 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
4451 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
4452 - Fix shellcheck warnings in scripts/test/coverage. Resolves
4456 Changes in version 0.3.3.11 - 2019-01-07
4457 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
4458 numerous fixes, including an important fix for anyone using OpenSSL
4459 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
4460 to this version, or to a later series.
4462 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
4463 We anticipate that this will be the last release of Tor 0.3.3, unless
4464 some major bug is before then. Some time between now and then, users
4465 should switch to either the Tor 0.3.4 series (supported until at least
4466 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
4467 support until at least 1 Feb 2022.
4469 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4470 - Fix our usage of named groups when running as a TLS 1.3 client in
4471 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4472 running as a relay, which caused clients to fail to negotiate TLS
4473 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4476 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
4477 - Fix a use-after-free error that could be caused by passing Tor an
4478 impossible set of options that would fail during options_act().
4479 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
4481 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
4482 - Only run one online rust build in Travis, to reduce network
4483 errors. Skip offline rust builds on Travis for Linux gcc, because
4484 they're redundant. Implements ticket 27252.
4485 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
4486 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
4487 Linux with default settings, because all the non-default builds
4488 use gcc on Linux. Implements ticket 27252.
4490 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
4491 - Use the Travis Homebrew addon to install packages on macOS during
4492 Travis CI. The package list is the same, but the Homebrew addon
4493 does not do a `brew update` by default. Implements ticket 27738.
4495 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4496 - Replace the 150 fallbacks originally introduced in Tor
4497 0.3.3.1-alpha in January 2018 (of which ~115 were still
4498 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4499 removed) generated in December 2018. Closes ticket 24803.
4501 o Minor features (geoip):
4502 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4503 Country database. Closes ticket 29012.
4505 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4506 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4507 key export function from handling long labels. When this bug is
4508 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4509 version of OpenSSL without this bug when it becomes available.
4510 Closes ticket 28973.
4512 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4513 - Update relay descriptor on bandwidth changes only when the uptime
4514 is smaller than 24h, in order to reduce the efficiency of guard
4515 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4517 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
4518 - Avoid undefined behavior in an end-of-string check when parsing
4519 the BEGIN line in a directory object. Fixes bug 28202; bugfix
4522 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
4523 - Rewrite our assertion macros so that they no longer suppress the
4524 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
4526 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4527 - Initialize a variable unconditionally in aes_new_cipher(), since
4528 some compilers cannot tell that we always initialize it before
4529 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4531 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
4532 - Log additional info when we get a relay that shares an ed25519 ID
4533 with a different relay, instead making a BUG() warning. Fixes bug
4534 27800; bugfix on 0.3.2.1-alpha.
4536 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4537 - When a user requests a group-readable DataDirectory, give it to
4538 them. Previously, when the DataDirectory and the CacheDirectory
4539 were the same, the default setting (0) for
4540 CacheDirectoryGroupReadable would override the setting for
4541 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4544 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
4545 - When the onion service directory can't be created or has the wrong
4546 permissions, do not log a stack trace. Fixes bug 27335; bugfix
4549 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
4550 - Close all SOCKS request (for the same .onion) if the newly fetched
4551 descriptor is unusable. Before that, we would close only the first
4552 one leaving the other hanging and let to time out by themselves.
4553 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
4555 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4556 - Don't warn so loudly when Tor is unable to decode an onion
4557 descriptor. This can now happen as a normal use case if a client
4558 gets a descriptor with client authorization but the client is not
4559 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4561 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4562 - When deleting an ephemeral onion service (DEL_ONION), do not close
4563 any rendezvous circuits in order to let the existing client
4564 connections finish by themselves or closed by the application. The
4565 HS v2 is doing that already so now we have the same behavior for
4566 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4568 o Minor bugfixes (HTTP tunnel):
4569 - Fix a bug warning when closing an HTTP tunnel connection due to
4570 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
4573 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4574 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4575 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4577 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
4578 - Ensure circuitmux queues are empty before scheduling or sending
4579 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
4581 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
4582 - Reject protocol names containing bytes other than alphanumeric
4583 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
4586 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
4587 - Compute protover votes correctly in the rust version of the
4588 protover code. Previously, the protover rewrite in 24031 allowed
4589 repeated votes from the same voter for the same protocol version
4590 to be counted multiple times in protover_compute_vote(). Fixes bug
4591 27649; bugfix on 0.3.3.5-rc.
4592 - Reject protover names that contain invalid characters. Fixes bug
4593 27687; bugfix on 0.3.3.1-alpha.
4595 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
4596 - protover_all_supported() would attempt to allocate up to 16GB on
4597 some inputs, leading to a potential memory DoS. Fixes bug 27206;
4598 bugfix on 0.3.3.5-rc.
4600 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
4601 - Fix a potential null dereference in protover_all_supported(). Add
4602 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
4603 - Return a string that can be safely freed by C code, not one
4604 created by the rust allocator, in protover_all_supported(). Fixes
4605 bug 27740; bugfix on 0.3.3.1-alpha.
4606 - Fix an API mismatch in the rust implementation of
4607 protover_compute_vote(). This bug could have caused crashes on any
4608 directory authorities running Tor with Rust (which we do not yet
4609 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
4611 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
4612 - If a unit test running in a subprocess exits abnormally or with a
4613 nonzero status code, treat the test as having failed, even if the
4614 test reported success. Without this fix, memory leaks don't cause
4615 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
4616 bugfix on 0.2.2.4-alpha.
4618 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
4619 - Treat backtrace test failures as expected on BSD-derived systems
4620 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
4621 (FreeBSD failures have been treated as expected since 18204 in
4622 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
4624 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4625 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4626 bugfix on 0.3.0.1-alpha.
4629 Changes in version 0.3.4.10 - 2019-01-07
4630 Tor 0.3.4.9 is the second stable release in its series; it backports
4631 numerous fixes, including an important fix for relays, and for anyone
4632 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
4635 As a reminder, the Tor 0.3.4 series will be supported until 10 June
4636 2019. Some time between now and then, users should switch to the Tor
4637 0.3.5 series, which will receive long-term support until at least 1
4640 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
4641 - Fix our usage of named groups when running as a TLS 1.3 client in
4642 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4643 running as a relay, which caused clients to fail to negotiate TLS
4644 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4647 o Major bugfixes (relay, directory, backport from 0.3.5.7):
4648 - Always reactivate linked connections in the main loop so long as
4649 any linked connection has been active. Previously, connections
4650 serving directory information wouldn't get reactivated after the
4651 first chunk of data was sent (usually 32KB), which would prevent
4652 clients from bootstrapping. Fixes bug 28912; bugfix on
4653 0.3.4.1-alpha. Patch by "cypherpunks3".
4655 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
4656 - Always show the configure and test logs, and upload them as build
4657 artifacts, when building for Windows using Appveyor CI.
4660 o Minor features (controller, backport from 0.3.5.1-alpha):
4661 - For purposes of CIRC_BW-based dropped cell detection, track half-
4662 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
4663 bias check cells to arrive without counting it as dropped until
4664 either the END arrives, or the windows are empty. Closes
4667 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
4668 - Replace the 150 fallbacks originally introduced in Tor
4669 0.3.3.1-alpha in January 2018 (of which ~115 were still
4670 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4671 removed) generated in December 2018. Closes ticket 24803.
4673 o Minor features (geoip):
4674 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
4675 Country database. Closes ticket 28395.
4677 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
4678 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4679 key export function from handling long labels. When this bug is
4680 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4681 version of OpenSSL without this bug when it becomes available.
4682 Closes ticket 28973.
4684 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
4685 - Initialize a variable unconditionally in aes_new_cipher(), since
4686 some compilers cannot tell that we always initialize it before
4687 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4689 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
4690 - Avoid a logging a BUG() stacktrace when closing connection held
4691 open because the write side is rate limited but not the read side.
4692 Now, the connection read side is simply shut down until Tor is
4693 able to flush the connection and close it. Fixes bug 27750; bugfix
4696 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
4697 - Manually configure the zstd compiler options, when building using
4698 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
4699 not come with a pkg-config file. Fixes bug 28454; bugfix
4701 - Stop using an external OpenSSL install, and stop installing MSYS2
4702 packages, when building using mingw on Appveyor Windows CI. Fixes
4703 bug 28399; bugfix on 0.3.4.1-alpha.
4705 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
4706 - Explicitly specify the path to the OpenSSL library and do not
4707 download OpenSSL from Pacman, but instead use the library that is
4708 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
4710 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
4711 - When a user requests a group-readable DataDirectory, give it to
4712 them. Previously, when the DataDirectory and the CacheDirectory
4713 were the same, the default setting (0) for
4714 CacheDirectoryGroupReadable would override the setting for
4715 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
4718 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
4719 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4720 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4722 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
4723 - Don't warn so loudly when Tor is unable to decode an onion
4724 descriptor. This can now happen as a normal use case if a client
4725 gets a descriptor with client authorization but the client is not
4726 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
4728 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
4729 - When deleting an ephemeral onion service (DEL_ONION), do not close
4730 any rendezvous circuits in order to let the existing client
4731 connections finish by themselves or closed by the application. The
4732 HS v2 is doing that already so now we have the same behavior for
4733 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4735 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
4736 - Update relay descriptor on bandwidth changes only when the uptime
4737 is smaller than 24h, in order to reduce the efficiency of guard
4738 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
4740 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
4741 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4742 bugfix on 0.3.0.1-alpha.
4745 Changes in version 0.3.5.7 - 2019-01-07
4746 Tor 0.3.5.7 is the first stable release in its series; it includes
4747 compilation and portability fixes, and a fix for a severe problem
4748 affecting directory caches.
4750 The Tor 0.3.5 series includes several new features and performance
4751 improvements, including client authorization for v3 onion services,
4752 cleanups to bootstrap reporting, support for improved bandwidth-
4753 measurement tools, experimental support for NSS in place of OpenSSL,
4754 and much more. It also begins a full reorganization of Tor's code
4755 layout, for improved modularity and maintainability in the future.
4756 Finally, there is the usual set of performance improvements and
4757 bugfixes that we try to do in every release series.
4759 There are a couple of changes in the 0.3.5 that may affect
4760 compatibility. First, the default version for newly created onion
4761 services is now v3. Use the HiddenServiceVersion option if you want to
4762 override this. Second, some log messages related to bootstrapping have
4763 changed; if you use stem, you may need to update to the latest version
4764 so it will recognize them.
4766 We have designated 0.3.5 as a "long-term support" (LTS) series: we
4767 will continue to patch major bugs in typical configurations of 0.3.5
4768 until at least 1 Feb 2022. (We do not plan to provide long-term
4769 support for embedding, Rust support, NSS support, running a directory
4770 authority, or unsupported platforms. For these, you will need to stick
4771 with the latest stable release.)
4773 Below are the changes since 0.3.5.6-rc. For a complete list of changes
4774 since 0.3.4.9, see the ReleaseNotes file.
4776 o Major bugfixes (relay, directory):
4777 - Always reactivate linked connections in the main loop so long as
4778 any linked connection has been active. Previously, connections
4779 serving directory information wouldn't get reactivated after the
4780 first chunk of data was sent (usually 32KB), which would prevent
4781 clients from bootstrapping. Fixes bug 28912; bugfix on
4782 0.3.4.1-alpha. Patch by "cypherpunks3".
4784 o Minor features (compilation):
4785 - When possible, place our warning flags in a separate file, to
4786 avoid flooding verbose build logs. Closes ticket 28924.
4788 o Minor features (geoip):
4789 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
4790 Country database. Closes ticket 29012.
4792 o Minor features (OpenSSL bug workaround):
4793 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
4794 key export function from handling long labels. When this bug is
4795 detected, Tor will disable TLS 1.3. We recommend upgrading to a
4796 version of OpenSSL without this bug when it becomes available.
4797 Closes ticket 28973.
4799 o Minor features (performance):
4800 - Remove about 96% of the work from the function that we run at
4801 startup to test our curve25519_basepoint implementation. Since
4802 this function has yet to find an actual failure, we now only run
4803 it for 8 iterations instead of 200. Based on our profile
4804 information, this change should save around 8% of our startup time
4805 on typical desktops, and may have a similar effect on other
4806 platforms. Closes ticket 28838.
4807 - Stop re-validating our hardcoded Diffie-Hellman parameters on
4808 every startup. Doing this wasted time and cycles, especially on
4809 low-powered devices. Closes ticket 28851.
4811 o Minor bugfixes (compilation):
4812 - Fix compilation for Android by adding a missing header to
4813 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
4815 o Minor bugfixes (correctness):
4816 - Fix an unreached code path where we checked the value of
4817 "hostname" inside send_resolved_hostname_cell(). Previously, we
4818 used it before checking it; now we check it first. Fixes bug
4819 28879; bugfix on 0.1.2.7-alpha.
4821 o Minor bugfixes (testing):
4822 - Make sure that test_rebind.py actually obeys its timeout, even
4823 when it receives a large number of log messages. Fixes bug 28883;
4824 bugfix on 0.3.5.4-alpha.
4825 - Stop running stem's unit tests as part of "make test-stem", but
4826 continue to run stem's unit and online tests during "make test-
4827 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
4829 o Minor bugfixes (windows services):
4830 - Make Tor start correctly as an NT service again: previously it was
4831 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
4833 o Code simplification and refactoring:
4834 - When parsing a port configuration, make it more obvious to static
4835 analyzer tools that we always initialize the address. Closes
4839 Changes in version 0.3.5.6-rc - 2018-12-18
4840 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
4841 It is the first release candidate in the 0.3.5.x series; if no further
4842 huge bugs are found, our next release may be the stable 0.3.5.x.
4844 o Minor features (continuous integration, Windows):
4845 - Always show the configure and test logs, and upload them as build
4846 artifacts, when building for Windows using Appveyor CI.
4849 o Minor features (fallback directory list):
4850 - Replace the 150 fallbacks originally introduced in Tor
4851 0.3.3.1-alpha in January 2018 (of which ~115 were still
4852 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
4853 removed) generated in December 2018. Closes ticket 24803.
4855 o Minor features (geoip):
4856 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
4857 Country database. Closes ticket 28744.
4859 o Minor bugfixes (compilation):
4860 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
4861 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
4863 o Minor bugfixes (continuous integration, Windows):
4864 - Explicitly specify the path to the OpenSSL library and do not
4865 download OpenSSL from Pacman, but instead use the library that is
4866 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
4868 o Minor bugfixes (onion service v3):
4869 - When deleting an ephemeral onion service (DEL_ONION), do not close
4870 any rendezvous circuits in order to let the existing client
4871 connections finish by themselves or closed by the application. The
4872 HS v2 is doing that already so now we have the same behavior for
4873 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
4875 o Minor bugfixes (restart-in-process, boostrap):
4876 - Add missing resets of bootstrap tracking state when shutting down
4877 (regression caused by ticket 27169). Fixes bug 28524; bugfix
4880 o Minor bugfixes (testing):
4881 - Use a separate DataDirectory for the test_rebind script.
4882 Previously, this script would run using the default DataDirectory,
4883 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
4884 Patch from Taylor R Campbell.
4885 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
4886 bugfix on 0.3.0.1-alpha.
4888 o Minor bugfixes (Windows):
4889 - Correctly identify Windows 8.1, Windows 10, and Windows Server
4890 2008 and later from their NT versions. Fixes bug 28096; bugfix on
4891 0.2.2.34; reported by Keifer Bly.
4892 - On recent Windows versions, the GetVersionEx() function may report
4893 an earlier Windows version than the running OS. To avoid user
4894 confusion, add "[or later]" to Tor's version string on affected
4895 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
4897 - Remove Windows versions that were never supported by the
4898 GetVersionEx() function. Stop duplicating the latest Windows
4899 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
4900 reported by Keifer Bly.
4903 - Increase logging and tag all log entries with timestamps in
4904 test_rebind.py. Provides diagnostics for issue 28229.
4906 o Code simplification and refactoring (shared random, dirauth):
4907 - Change many tor_assert() to use BUG() instead. The idea is to not
4908 crash a dirauth but rather scream loudly with a stacktrace and let
4909 it continue run. The shared random subsystem is very resilient and
4910 if anything wrong happens with it, at worst a non coherent value
4911 will be put in the vote and discarded by the other authorities.
4912 Closes ticket 19566.
4914 o Documentation (onion services):
4915 - Document in the man page that changing ClientOnionAuthDir value or
4916 adding a new file in the directory will not work at runtime upon
4917 sending a HUP if Sandbox 1. Closes ticket 28128.
4918 - Note in the man page that the only real way to fully revoke an
4919 onion service v3 client authorization is by restarting the tor
4920 process. Closes ticket 28275.
4923 Changes in version 0.3.5.5-alpha - 2018-11-16
4924 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
4925 including several that we hope to backport to older release series in
4928 o Major bugfixes (OpenSSL, portability):
4929 - Fix our usage of named groups when running as a TLS 1.3 client in
4930 OpenSSL 1.1.1. Previously, we only initialized EC groups when
4931 running as a relay, which caused clients to fail to negotiate TLS
4932 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
4935 o Minor features (geoip):
4936 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
4937 Country database. Closes ticket 28395.
4939 o Minor bugfixes (compilation):
4940 - Initialize a variable unconditionally in aes_new_cipher(), since
4941 some compilers cannot tell that we always initialize it before
4942 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
4944 o Minor bugfixes (connection, relay):
4945 - Avoid a logging a BUG() stacktrace when closing connection held
4946 open because the write side is rate limited but not the read side.
4947 Now, the connection read side is simply shut down until Tor is
4948 able to flush the connection and close it. Fixes bug 27750; bugfix
4951 o Minor bugfixes (continuous integration, Windows):
4952 - Manually configure the zstd compiler options, when building using
4953 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
4954 not come with a pkg-config file. Fixes bug 28454; bugfix
4956 - Stop using an external OpenSSL install, and stop installing MSYS2
4957 packages, when building using mingw on Appveyor Windows CI. Fixes
4958 bug 28399; bugfix on 0.3.4.1-alpha.
4960 o Minor bugfixes (documentation):
4961 - Make Doxygen work again after the code movement in the 0.3.5
4962 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
4964 o Minor bugfixes (Linux seccomp2 sandbox):
4965 - Permit the "shutdown()" system call, which is apparently used by
4966 OpenSSL under some circumstances. Fixes bug 28183; bugfix
4969 o Minor bugfixes (logging):
4970 - Stop talking about the Named flag in log messages. Clients have
4971 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
4974 o Minor bugfixes (memory leaks):
4975 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
4976 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
4978 o Minor bugfixes (onion services):
4979 - On an intro point for a version 3 onion service, stop closing
4980 introduction circuits on an NACK. This lets the client decide
4981 whether to reuse the circuit or discard it. Previously, we closed
4982 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
4983 0.3.2.1-alpha. Patch by Neel Chaunan.
4984 - When replacing a descriptor in the client cache, make sure to
4985 close all client introduction circuits for the old descriptor, so
4986 we don't end up with unusable leftover circuits. Fixes bug 27471;
4987 bugfix on 0.3.2.1-alpha.
4990 Changes in version 0.3.5.4-alpha - 2018-11-08
4991 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
4992 improves our continuous integration support. It continues our attempts
4993 to stabilize this alpha branch and build it into a foundation for an
4994 acceptable long-term-support release.
4996 o Major bugfixes (compilation, rust):
4997 - Rust tests can now build and run successfully with the
4998 --enable-fragile-hardening option enabled. Doing this currently
4999 requires the rust beta channel; it will be possible with stable
5000 rust once Rust version 1.31 is released. Patch from Alex Crichton.
5001 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
5003 o Major bugfixes (embedding, main loop):
5004 - When DisableNetwork becomes set, actually disable periodic events
5005 that are already enabled. (Previously, we would refrain from
5006 enabling new ones, but we would leave the old ones turned on.)
5007 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
5009 o Minor features (continuous integration):
5010 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
5012 - Add new CI job to Travis configuration to run stem-based
5013 integration tests. Closes ticket 27913.
5015 o Minor features (Windows, continuous integration):
5016 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
5017 Appveyor's CI. Closes ticket 28318.
5019 o Minor bugfixes (C correctness, also in 0.3.4.9):
5020 - Avoid undefined behavior in an end-of-string check when parsing
5021 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5024 o Minor bugfixes (compilation):
5025 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
5026 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
5028 o Minor bugfixes (compilation, OpenSolaris):
5029 - Fix compilation on OpenSolaris and its descendants by adding a
5030 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
5033 o Minor bugfixes (configuration):
5034 - Refuse to start with relative file paths and RunAsDaemon set
5035 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
5038 o Minor bugfixes (directory authority, also in 0.3.4.9):
5039 - Log additional info when we get a relay that shares an ed25519 ID
5040 with a different relay, instead of a BUG() warning with a
5041 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
5043 o Minor bugfixes (onion service v3):
5044 - Build the service descriptor's signing key certificate before
5045 uploading, so we always have a fresh one: leaving no chances for
5046 it to expire service side. Fixes bug 27838; bugfix
5049 o Minor bugfixes (onion service v3, client authorization):
5050 - Fix an assert() when adding a client authorization for the first
5051 time and then sending a HUP signal to the service. Before that,
5052 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
5054 o Minor bugfixes (onion services):
5055 - Unless we have explicitly set HiddenServiceVersion, detect the
5056 onion service version and then look for invalid options.
5057 Previously, we did the reverse, but that broke existing configs
5058 which were pointed to a v2 service and had options like
5059 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
5060 0.3.5.1-alpha. Patch by Neel Chauhan.
5062 o Minor bugfixes (portability):
5063 - Make the OPE code (which is used for v3 onion services) run
5064 correctly on big-endian platforms. Fixes bug 28115; bugfix
5067 o Minor bugfixes (protover, rust):
5068 - Reject extra commas in version strings. Fixes bug 27197; bugfix
5071 o Minor bugfixes (relay shutdown, systemd):
5072 - Notify systemd of ShutdownWaitLength so it can be set to longer
5073 than systemd's TimeoutStopSec. In Tor's systemd service file, set
5074 TimeoutSec to 60 seconds to allow Tor some time to shut down.
5075 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
5077 o Minor bugfixes (rust, also in 0.3.4.9):
5078 - Fix a potential null dereference in protover_all_supported(). Add
5079 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5080 - Return a string that can be safely freed by C code, not one
5081 created by the rust allocator, in protover_all_supported(). Fixes
5082 bug 27740; bugfix on 0.3.3.1-alpha.
5084 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
5085 - Fix an API mismatch in the rust implementation of
5086 protover_compute_vote(). This bug could have caused crashes on any
5087 directory authorities running Tor with Rust (which we do not yet
5088 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5090 o Minor bugfixes (testing):
5091 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
5092 27968; bugfix on 0.3.5.1-alpha.
5094 o Minor bugfixes (testing, also in 0.3.4.9):
5095 - Treat backtrace test failures as expected on BSD-derived systems
5096 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5097 (FreeBSD failures have been treated as expected since 18204 in
5098 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5100 o Documentation (onion service manpage):
5101 - Improve HSv3 client authorization by making some options more
5102 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
5105 Changes in version 0.3.4.9 - 2018-11-02
5106 Tor 0.3.4.9 is the second stable release in its series; it backports
5107 numerous fixes, including a fix for a bandwidth management bug that
5108 was causing memory exhaustion on relays. Anyone running an earlier
5109 version of Tor 0.3.4.9 should upgrade.
5111 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
5112 - Fix compilation on ARM (and other less-used CPUs) when compiling
5113 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5115 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
5116 - Make sure Tor bootstraps and works properly if only the
5117 ControlPort is set. Prior to this fix, Tor would only bootstrap
5118 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5119 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5121 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
5122 - When our write bandwidth limit is exhausted, stop writing on the
5123 connection. Previously, we had a typo in the code that would make
5124 us stop reading instead, leading to relay connections being stuck
5125 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5128 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
5129 - Fix a use-after-free error that could be caused by passing Tor an
5130 impossible set of options that would fail during options_act().
5131 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5133 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
5134 - Don't do a distcheck with --disable-module-dirauth in Travis.
5135 Implements ticket 27252.
5136 - Only run one online rust build in Travis, to reduce network
5137 errors. Skip offline rust builds on Travis for Linux gcc, because
5138 they're redundant. Implements ticket 27252.
5139 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5140 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5141 Linux with default settings, because all the non-default builds
5142 use gcc on Linux. Implements ticket 27252.
5144 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
5145 - Use the Travis Homebrew addon to install packages on macOS during
5146 Travis CI. The package list is the same, but the Homebrew addon
5147 does not do a `brew update` by default. Implements ticket 27738.
5149 o Minor features (geoip):
5150 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
5151 Country database. Closes ticket 27991.
5153 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
5154 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5155 difference algorithm for 32-bit Apple platforms. Previously, it
5156 would overflow when calculating the difference between two times
5157 more than 47 days apart. Fixes part of bug 27139; bugfix
5159 - Improve the precision of our 32-bit millisecond difference
5160 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5161 bugfix on 0.3.4.1-alpha.
5162 - Relax the tolerance on the mainloop/update_time_jumps test when
5163 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5166 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
5167 - Avoid undefined behavior in an end-of-string check when parsing
5168 the BEGIN line in a directory object. Fixes bug 28202; bugfix
5171 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
5172 - Only install the necessary mingw packages during our appveyor
5173 builds. This change makes the build a little faster, and prevents
5174 a conflict with a preinstalled mingw openssl that appveyor now
5175 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
5177 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
5178 - Rewrite our assertion macros so that they no longer suppress the
5179 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5181 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
5182 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5183 27464; bugfix on 0.3.4.1-alpha.
5185 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
5186 - Log additional info when we get a relay that shares an ed25519 ID
5187 with a different relay, instead making a BUG() warning. Fixes bug
5188 27800; bugfix on 0.3.2.1-alpha.
5190 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
5191 - Avoid a double-close when shutting down a stalled directory
5192 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5194 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
5195 - Fix a bug warning when closing an HTTP tunnel connection due to an
5196 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5199 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
5200 - Ensure circuitmux queues are empty before scheduling or sending
5201 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5203 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
5204 - When the onion service directory can't be created or has the wrong
5205 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5208 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
5209 - Close all SOCKS request (for the same .onion) if the newly fetched
5210 descriptor is unusable. Before that, we would close only the first
5211 one leaving the other hanging and let to time out by themselves.
5212 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5214 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
5215 - When selecting a v3 rendezvous point, don't only look at the
5216 protover, but also check whether the curve25519 onion key is
5217 present. This way we avoid picking a relay that supports the v3
5218 rendezvous but for which we don't have the microdescriptor. Fixes
5219 bug 27797; bugfix on 0.3.2.1-alpha.
5221 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
5222 - Reject protocol names containing bytes other than alphanumeric
5223 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5226 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
5227 - Compute protover votes correctly in the rust version of the
5228 protover code. Previously, the protover rewrite in 24031 allowed
5229 repeated votes from the same voter for the same protocol version
5230 to be counted multiple times in protover_compute_vote(). Fixes bug
5231 27649; bugfix on 0.3.3.5-rc.
5232 - Reject protover names that contain invalid characters. Fixes bug
5233 27687; bugfix on 0.3.3.1-alpha.
5235 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
5236 - protover_all_supported() would attempt to allocate up to 16GB on
5237 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5238 bugfix on 0.3.3.5-rc.
5240 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
5241 - Fix an API mismatch in the rust implementation of
5242 protover_compute_vote(). This bug could have caused crashes on any
5243 directory authorities running Tor with Rust (which we do not yet
5244 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
5246 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
5247 - Fix a potential null dereference in protover_all_supported(). Add
5248 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
5249 - Return a string that can be safely freed by C code, not one
5250 created by the rust allocator, in protover_all_supported(). Fixes
5251 bug 27740; bugfix on 0.3.3.1-alpha.
5253 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
5254 - If a unit test running in a subprocess exits abnormally or with a
5255 nonzero status code, treat the test as having failed, even if the
5256 test reported success. Without this fix, memory leaks don't cause
5257 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5258 bugfix on 0.2.2.4-alpha.
5260 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
5261 - Make the hs_service tests use the same time source when creating
5262 the introduction point and when testing it. Now tests work better
5263 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5266 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
5267 - Treat backtrace test failures as expected on BSD-derived systems
5268 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
5269 (FreeBSD failures have been treated as expected since 18204 in
5270 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
5273 Changes in version 0.3.5.3-alpha - 2018-10-17
5274 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
5275 versions. One important fix for relays addresses a problem with rate-
5276 limiting code from back in 0.3.4.x: If the fix works out, we'll be
5277 backporting it soon. This release is still an alpha, but we hope it's
5278 getting closer and closer to stability.
5280 o Major features (onion services):
5281 - Version 3 onion services can now use the per-service
5282 HiddenServiceExportCircuitID option to differentiate client
5283 circuits. It communicates with the service by using the HAProxy
5284 protocol to assign virtual IP addresses to inbound client
5285 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
5287 o Major bugfixes (compilation):
5288 - Fix compilation on ARM (and other less-used CPUs) when compiling
5289 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
5291 o Major bugfixes (initialization, crash):
5292 - Fix an assertion crash that would stop Tor from starting up if it
5293 tried to activate a periodic event too early. Fixes bug 27861;
5294 bugfix on 0.3.5.1-alpha.
5296 o Major bugfixes (mainloop, bootstrap):
5297 - Make sure Tor bootstraps and works properly if only the
5298 ControlPort is set. Prior to this fix, Tor would only bootstrap
5299 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
5300 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
5302 o Major bugfixes (relay):
5303 - When our write bandwidth limit is exhausted, stop writing on the
5304 connection. Previously, we had a typo in the code that would make
5305 us stop reading instead, leading to relay connections being stuck
5306 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
5309 o Minor features (continuous integration):
5310 - Use the Travis Homebrew addon to install packages on macOS during
5311 Travis CI. The package list is the same, but the Homebrew addon
5312 does not do a `brew update` by default. Implements ticket 27738.
5313 - Report what program produced the mysterious core file that we
5314 occasionally see on Travis CI during make distcheck. Closes
5317 o Minor features (geoip):
5318 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
5319 Country database. Closes ticket 27991.
5321 o Minor bugfixes (code safety):
5322 - Rewrite our assertion macros so that they no longer suppress the
5323 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
5326 o Minor bugfixes (compilation):
5327 - Compile the ed25519-donna code with a correct declaration of
5328 crypto_strongest_rand(). Previously, we built it with one type,
5329 but linked it against another in the unit tests, which caused
5330 compilation failures with LTO enabled. This could have caused
5331 other undefined behavior in the tests. Fixes bug 27728; bugfix
5334 o Minor bugfixes (compilation, netbsd):
5335 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
5338 o Minor bugfixes (continuous integration, appveyor):
5339 - Install only the necessary mingw packages during our appveyor
5340 builds. This change makes the build a little faster, and prevents
5341 a conflict with a preinstalled mingw openssl that appveyor now
5342 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
5344 o Minor bugfixes (directory permissions):
5345 - When a user requests a group-readable DataDirectory, give it to
5346 them. Previously, when the DataDirectory and the CacheDirectory
5347 were the same, the default setting (0) for
5348 CacheDirectoryGroupReadable would override the setting for
5349 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
5352 o Minor bugfixes (memory leaks):
5353 - Fix a small memory leak when calling Tor with --dump-config. Fixes
5354 bug 27893; bugfix on 0.3.2.1-alpha.
5356 o Minor bugfixes (networking):
5357 - In retry_listeners_ports(), make sure that we're removing a member
5358 of old_conns smartlist at most once. Fixes bug 27808; bugfix
5360 - Refrain from attempting socket rebinding when old and new
5361 listeners are in different address families. Fixes bug 27928;
5362 bugfix on 0.3.5.1-alpha.
5364 o Minor bugfixes (onion service v3):
5365 - Stop dumping a stack trace when trying to connect to an intro
5366 point without having a descriptor for it. Fixes bug 27774; bugfix
5368 - Don't warn so loudly when Tor is unable to decode an onion
5369 descriptor. This can now happen as a normal use case if a client
5370 gets a descriptor with client authorization but the client is not
5371 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
5372 - When selecting a v3 rendezvous point, don't only look at the
5373 protover, but also check whether the curve25519 onion key is
5374 present. This way we avoid picking a relay that supports the v3
5375 rendezvous but for which we don't have the microdescriptor. Fixes
5376 bug 27797; bugfix on 0.3.2.1-alpha.
5378 o Minor bugfixes (protover):
5379 - Reject protocol names containing bytes other than alphanumeric
5380 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
5383 o Minor bugfixes (testing):
5384 - Make the hs_service tests use the same time source when creating
5385 the introduction point and when testing it. Now tests work better
5386 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
5388 - In test_rebind.py, check if the Python version is in the supported
5389 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
5391 o Code simplification and refactoring:
5392 - Divide more large Tor source files -- especially ones that span
5393 multiple areas of functionality -- into smaller parts, including
5394 onion.c and main.c. Closes ticket 26747.
5395 - Divide the "routerparse.c" module into separate modules for each
5396 group of parsed objects. Closes ticket 27924.
5397 - Move protover_rust.c to the same place protover.c was moved to.
5398 Closes ticket 27814.
5399 - Split directory.c into separate pieces for client, server, and
5400 common functionality. Closes ticket 26744.
5401 - Split the non-statistics-related parts from the rephist.c and
5402 geoip.c modules. Closes ticket 27892.
5403 - Split the router.c file into relay-only and shared components, to
5404 help with future modularization. Closes ticket 27864.
5407 - In the tor-resolve(1) manpage, fix the reference to socks-
5408 extensions.txt by adding a web URL. Resolves ticket 27853.
5409 - Mention that we require Python to be 2.7 or newer for some
5410 integration tests that we ship with Tor. Resolves ticket 27677.
5413 Changes in version 0.3.5.2-alpha - 2018-09-21
5414 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
5415 that made Tor think it had run out of sockets. Anybody running a relay
5416 or an onion service on 0.3.5.1-alpha should upgrade.
5418 o Major bugfixes (relay bandwidth statistics):
5419 - When we close relayed circuits, report the data in the circuit
5420 queues as being written in our relay bandwidth stats. This
5421 mitigates guard discovery and other attacks that close circuits
5422 for the explicit purpose of noticing this discrepancy in
5423 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
5425 o Major bugfixes (socket accounting):
5426 - In our socket accounting code, count a socket as closed even when
5427 it is closed indirectly by the TLS layer. Previously, we would
5428 count these sockets as still in use, and incorrectly believe that
5429 we had run out of sockets. Fixes bug 27795; bugfix
5432 o Minor bugfixes (32-bit OSX and iOS, timing):
5433 - Fix an integer overflow bug in our optimized 32-bit millisecond-
5434 difference algorithm for 32-bit Apple platforms. Previously, it
5435 would overflow when calculating the difference between two times
5436 more than 47 days apart. Fixes part of bug 27139; bugfix
5438 - Improve the precision of our 32-bit millisecond difference
5439 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
5440 bugfix on 0.3.4.1-alpha.
5441 - Relax the tolerance on the mainloop/update_time_jumps test when
5442 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
5445 o Minor bugfixes (onion service v3):
5446 - Close all SOCKS request (for the same .onion) if the newly fetched
5447 descriptor is unusable. Before that, we would close only the first
5448 one leaving the other hanging and let to time out by themselves.
5449 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
5451 o Minor bugfixes (memory leak):
5452 - Fix an unlikely memory leak when trying to read a private key from
5453 a ridiculously large file. Fixes bug 27764; bugfix on
5454 0.3.5.1-alpha. This is CID 1439488.
5456 o Minor bugfixes (NSS):
5457 - Correctly detect failure to open a dummy TCP socket when stealing
5458 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
5461 o Minor bugfixes (rust):
5462 - protover_all_supported() would attempt to allocate up to 16GB on
5463 some inputs, leading to a potential memory DoS. Fixes bug 27206;
5464 bugfix on 0.3.3.5-rc.
5466 o Minor bugfixes (testing):
5467 - Revise the "conditionvar_timeout" test so that it succeeds even on
5468 heavily loaded systems where the test threads are not scheduled
5469 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
5471 o Code simplification and refactoring:
5472 - Divide the routerlist.c and dirserv.c modules into smaller parts.
5473 Closes ticket 27799.
5476 Changes in version 0.3.5.1-alpha - 2018-09-18
5477 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
5478 client authorization for modern (v3) onion services, improves
5479 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
5480 support for NSS in place of OpenSSL, and much more.
5482 o Major features (onion services, UI change):
5483 - For a newly created onion service, the default version is now 3.
5484 Tor still supports existing version 2 services, but the operator
5485 now needs to set "HiddenServiceVersion 2" in order to create a new
5486 version 2 service. For existing services, Tor now learns the
5487 version by reading the key file. Closes ticket 27215.
5489 o Major features (relay, UI change):
5490 - Relays no longer run as exits by default. If the "ExitRelay"
5491 option is auto (or unset), and no exit policy is specified with
5492 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
5493 Previously in this case, we allowed exit traffic and logged a
5494 warning message. Closes ticket 21530. Patch by Neel Chauhan.
5495 - Tor now validates that the ContactInfo config option is valid UTF-
5496 8 when parsing torrc. Closes ticket 27428.
5498 o Major features (bootstrap):
5499 - Don't report directory progress until after a connection to a
5500 relay or bridge has succeeded. Previously, we'd report 80%
5501 progress based on cached directory information when we couldn't
5502 even connect to the network. Closes ticket 27169.
5504 o Major features (new code layout):
5505 - Nearly all of Tor's source code has been moved around into more
5506 logical places. The "common" directory is now divided into a set
5507 of libraries in "lib", and files in the "or" directory have been
5508 split into "core" (logic absolutely needed for onion routing),
5509 "feature" (independent modules in Tor), and "app" (to configure
5510 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
5511 more information. Closes ticket 26481.
5513 This refactoring is not complete: although the libraries have been
5514 refactored to be acyclic, the main body of Tor is still too
5515 interconnected. We will attempt to improve this in the future.
5517 o Major features (onion services v3):
5518 - Implement onion service client authorization at the descriptor
5519 level: only authorized clients can decrypt a service's descriptor
5520 to find out how to contact it. A new torrc option was added to
5521 control this client side: ClientOnionAuthDir <path>. On the
5522 service side, if the "authorized_clients/" directory exists in the
5523 onion service directory path, client configurations are read from
5524 the files within. See the manpage for more details. Closes ticket
5525 27547. Patch done by Suphanat Chunhapanya (haxxpop).
5526 - Improve revision counter generation in next-gen onion services.
5527 Onion services can now scale by hosting multiple instances on
5528 different hosts without synchronization between them, which was
5529 previously impossible because descriptors would get rejected by
5530 HSDirs. Addresses ticket 25552.
5532 o Major features (portability, cryptography, experimental, TLS):
5533 - Tor now has the option to compile with the NSS library instead of
5534 OpenSSL. This feature is experimental, and we expect that bugs may
5535 remain. It is mainly intended for environments where Tor's
5536 performance is not CPU-bound, and where NSS is already known to be
5537 installed. To try it out, configure Tor with the --enable-nss
5538 flag. Closes tickets 26631, 26815, and 26816.
5540 If you are experimenting with this option and using an old cached
5541 consensus, Tor may fail to start. To solve this, delete your
5542 "cached-consensus" and "cached-microdesc-consensus" files,
5543 (if present), and restart Tor.
5545 o Major bugfixes (directory authority):
5546 - Actually check that the address we get from DirAuthority
5547 configuration line is valid IPv4. Explicitly disallow DirAuthority
5548 address to be a DNS hostname. Fixes bug 26488; bugfix
5551 o Major bugfixes (restart-in-process):
5552 - Fix a use-after-free error that could be caused by passing Tor an
5553 impossible set of options that would fail during options_act().
5554 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
5556 o Minor features (admin tools):
5557 - Add a new --key-expiration option to print the expiration date of
5558 the signing cert in an ed25519_signing_cert file. Resolves
5561 o Minor features (build):
5562 - If you pass the "--enable-pic" option to configure, Tor will try
5563 to tell the compiler to build position-independent code suitable
5564 to link into a dynamic library. (The default remains -fPIE, for
5565 code suitable for a relocatable executable.) Closes ticket 23846.
5567 o Minor features (code correctness, testing):
5568 - Tor's build process now includes a "check-includes" make target to
5569 verify that no module of Tor relies on any headers from a higher-
5570 level module. We hope to use this feature over time to help
5571 refactor our codebase. Closes ticket 26447.
5573 o Minor features (code layout):
5574 - We have a new "lowest-level" error-handling API for use by code
5575 invoked from within the logging module. With this interface, the
5576 logging code is no longer at risk of calling into itself if a
5577 failure occurs while it is trying to log something. Closes
5580 o Minor features (compilation):
5581 - Tor's configure script now supports a --with-malloc= option to
5582 select your malloc implementation. Supported options are
5583 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
5584 default). Addresses part of ticket 20424. Based on a patch from
5587 o Minor features (config):
5588 - The "auto" keyword in torrc is now case-insensitive. Closes
5591 o Minor features (continuous integration):
5592 - Don't do a distcheck with --disable-module-dirauth in Travis.
5593 Implements ticket 27252.
5594 - Install libcap-dev and libseccomp2-dev so these optional
5595 dependencies get tested on Travis CI. Closes ticket 26560.
5596 - Only run one online rust build in Travis, to reduce network
5597 errors. Skip offline rust builds on Travis for Linux gcc, because
5598 they're redundant. Implements ticket 27252.
5599 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
5600 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
5601 Linux with default settings, because all the non-default builds
5602 use gcc on Linux. Implements ticket 27252.
5604 o Minor features (controller):
5605 - Emit CIRC_BW events as soon as we detect that we processed an
5606 invalid or otherwise dropped cell on a circuit. This allows
5607 vanguards and other controllers to react more quickly to dropped
5608 cells. Closes ticket 27678.
5609 - For purposes of CIRC_BW-based dropped cell detection, track half-
5610 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
5611 bias check cells to arrive without counting it as dropped until
5612 either the END arrives, or the windows are empty. Closes
5614 - Implement a 'GETINFO md/all' controller command to enable getting
5615 all known microdescriptors. Closes ticket 8323.
5616 - The GETINFO command now support an "uptime" argument, to return
5617 Tor's uptime in seconds. Closes ticket 25132.
5619 o Minor features (denial-of-service avoidance):
5620 - Make our OOM handler aware of the DNS cache so that it doesn't
5621 fill up the memory. This check is important for our DoS mitigation
5622 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
5624 o Minor features (development):
5625 - Tor's makefile now supports running the "clippy" Rust style tool
5626 on our Rust code. Closes ticket 22156.
5628 o Minor features (directory authority):
5629 - There is no longer an artificial upper limit on the length of
5630 bandwidth lines. Closes ticket 26223.
5631 - When a bandwidth file is used to obtain the bandwidth measurements,
5632 include this bandwidth file headers in the votes. Closes
5634 - Improved support for networks with only a single authority or a
5635 single fallback directory. Patch from Gabriel Somlo. Closes
5638 o Minor features (embedding API):
5639 - The Tor controller API now supports a function to launch Tor with
5640 a preconstructed owning controller FD, so that embedding
5641 applications don't need to manage controller ports and
5642 authentication. Closes ticket 24204.
5643 - The Tor controller API now has a function that returns the name
5644 and version of the backend implementing the API. Closes
5647 o Minor features (geoip):
5648 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
5649 Country database. Closes ticket 27631.
5651 o Minor features (memory management):
5652 - Get Libevent to use the same memory allocator as Tor, by calling
5653 event_set_mem_functions() during initialization. Resolves
5656 o Minor features (memory usage):
5657 - When not using them, store legacy TAP public onion keys in DER-
5658 encoded format, rather than as expanded public keys. This should
5659 save several megabytes on typical clients. Closes ticket 27246.
5661 o Minor features (OpenSSL):
5662 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
5663 than our own. Resolves ticket 19979.
5665 o Minor features (Rust, code quality):
5666 - Improve rust code quality in the rust protover implementation by
5667 making it more idiomatic. Includes changing an internal API to
5668 take &str instead of &String. Closes ticket 26492.
5670 o Minor features (testing):
5671 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
5672 chutney. Implements ticket 27211.
5674 o Minor features (tor-resolve):
5675 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
5676 Side-effect of the refactoring for ticket 26526.
5678 o Minor features (UI):
5679 - Log each included configuration file or directory as we read it,
5680 to provide more visibility about where Tor is reading from. Patch
5681 from Unto Sten; closes ticket 27186.
5682 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
5683 Closes ticket 26703.
5685 o Minor bugfixes (bootstrap):
5686 - Try harder to get descriptors in non-exit test networks, by using
5687 the mid weight for the third hop when there are no exits. Fixes
5688 bug 27237; bugfix on 0.2.6.2-alpha.
5690 o Minor bugfixes (C correctness):
5691 - Avoid casting smartlist index to int implicitly, as it may trigger
5692 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
5693 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
5694 - Use time_t for all values in
5695 predicted_ports_prediction_time_remaining(). Rework the code that
5696 computes difference between durations/timestamps. Fixes bug 27165;
5697 bugfix on 0.3.1.1-alpha.
5699 o Minor bugfixes (client, memory usage):
5700 - When not running as a directory cache, there is no need to store
5701 the text of the current consensus networkstatus in RAM.
5702 Previously, however, clients would store it anyway, at a cost of
5703 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
5706 o Minor bugfixes (client, reachableaddresses):
5707 - Instead of adding a "reject *:*" line to ReachableAddresses when
5708 loading the configuration, add one to the policy after parsing it
5709 in parse_reachable_addresses(). This prevents extra "reject *.*"
5710 lines from accumulating on reloads. Fixes bug 20874; bugfix on
5711 0.1.1.5-alpha. Patch by Neel Chauhan.
5713 o Minor bugfixes (code quality):
5714 - Rename sandbox_getaddrinfo() and other functions to no longer
5715 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
5716 bugfix on 0.2.7.1-alpha.
5718 o Minor bugfixes (configuration, Onion Services):
5719 - In rend_service_parse_port_config(), disallow any input to remain
5720 after address-port pair was parsed. This will catch address and
5721 port being whitespace-separated by mistake of the user. Fixes bug
5722 27044; bugfix on 0.2.9.10.
5724 o Minor bugfixes (continuous integration):
5725 - Stop reinstalling identical packages in our Windows CI. Fixes bug
5726 27464; bugfix on 0.3.4.1-alpha.
5728 o Minor bugfixes (controller):
5729 - Consider all routerinfo errors other than "not a server" to be
5730 transient for the purpose of "GETINFO exit-policy/*" controller
5731 request. Print stacktrace in the unlikely case of failing to
5732 recompute routerinfo digest. Fixes bug 27034; bugfix
5735 o Minor bugfixes (directory connection shutdown):
5736 - Avoid a double-close when shutting down a stalled directory
5737 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
5739 o Minor bugfixes (HTTP tunnel):
5740 - Fix a bug warning when closing an HTTP tunnel connection due to an
5741 HTTP request we couldn't handle. Fixes bug 26470; bugfix
5744 o Minor bugfixes (ipv6):
5745 - In addrs_in_same_network_family(), we choose the subnet size based
5746 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
5747 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
5748 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
5750 o Minor bugfixes (logging):
5751 - As a precaution, do an early return from log_addr_has_changed() if
5752 Tor is running as client. Also, log a stack trace for debugging as
5753 this function should only be called when Tor runs as server. Fixes
5754 bug 26892; bugfix on 0.1.1.9-alpha.
5755 - Refrain from mentioning bug 21018 in the logs, as it is already
5756 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
5758 o Minor bugfixes (logging, documentation):
5759 - When SafeLogging is enabled, scrub IP address in
5760 channel_tls_process_netinfo_cell(). Also, add a note to manpage
5761 that scrubbing is not guaranteed on loglevels below Notice. Fixes
5762 bug 26882; bugfix on 0.2.4.10-alpha.
5764 o Minor bugfixes (netflow padding):
5765 - Ensure circuitmux queues are empty before scheduling or sending
5766 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
5768 o Minor bugfixes (onion service v2):
5769 - Log at level "info", not "warning", in the case that we do not
5770 have a consensus when a .onion request comes in. This can happen
5771 normally while bootstrapping. Fixes bug 27040; bugfix
5774 o Minor bugfixes (onion service v3):
5775 - When the onion service directory can't be created or has the wrong
5776 permissions, do not log a stack trace. Fixes bug 27335; bugfix
5779 o Minor bugfixes (OS compatibility):
5780 - Properly handle configuration changes that move a listener to/from
5781 wildcard IP address. If the first attempt to bind a socket fails,
5782 close the old listener and try binding the socket again. Fixes bug
5783 17873; bugfix on 0.0.8pre-1.
5785 o Minor bugfixes (performance)::
5786 - Rework node_is_a_configured_bridge() to no longer call
5787 node_get_all_orports(), which was performing too many memory
5788 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
5790 o Minor bugfixes (relay statistics):
5791 - Update relay descriptor on bandwidth changes only when the uptime
5792 is smaller than 24h, in order to reduce the efficiency of guard
5793 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
5795 o Minor bugfixes (relays):
5796 - Consider the fact that we'll be making direct connections to our
5797 entry and guard nodes when computing the fraction of nodes that
5798 have their descriptors. Also, if we are using bridges and there is
5799 at least one bridge with a full descriptor, treat the fraction of
5800 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
5801 Patch by Neel Chauhan.
5802 - Update the message logged on relays when DirCache is disabled.
5803 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
5804 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
5806 o Minor bugfixes (rust, protover):
5807 - Compute protover votes correctly in the rust version of the
5808 protover code. Previously, the protover rewrite in 24031 allowed
5809 repeated votes from the same voter for the same protocol version
5810 to be counted multiple times in protover_compute_vote(). Fixes bug
5811 27649; bugfix on 0.3.3.5-rc.
5812 - Reject protover names that contain invalid characters. Fixes bug
5813 27687; bugfix on 0.3.3.1-alpha.
5815 o Minor bugfixes (testing):
5816 - Fix two unit tests to work when HOME environment variable is not
5817 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
5818 - If a unit test running in a subprocess exits abnormally or with a
5819 nonzero status code, treat the test as having failed, even if the
5820 test reported success. Without this fix, memory leaks don't cause
5821 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
5822 bugfix on 0.2.2.4-alpha.
5823 - When logging a version mismatch in our openssl_version tests,
5824 report the actual offending version strings. Fixes bug 26152;
5825 bugfix on 0.2.9.1-alpha.
5826 - Fix forking tests on Windows when there is a space somewhere in
5827 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
5829 o Code simplification and refactoring:
5830 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
5831 longer needed. Closes ticket 26502.
5832 - Include paths to header files within Tor are now qualified by
5833 directory within the top-level src directory.
5834 - Many structures have been removed from the centralized "or.h"
5835 header, and moved into their own headers. This will allow us to
5836 reduce the number of places in the code that rely on each
5837 structure's contents and layout. Closes ticket 26383.
5838 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
5839 - Remove GetAdaptersAddresses_fn_t. The code that used it was
5840 removed as part of the 26481 refactor. Closes ticket 27467.
5841 - Rework Tor SOCKS server code to use Trunnel and benefit from
5842 autogenerated functions for parsing and generating SOCKS wire
5843 format. New implementation is cleaner, more maintainable and
5844 should be less prone to heartbleed-style vulnerabilities.
5845 Implements a significant fraction of ticket 3569.
5846 - Split sampled_guards_update_from_consensus() and
5847 select_entry_guard_for_circuit() into subfunctions. In
5848 entry_guards_update_primary() unite three smartlist enumerations
5849 into one and move smartlist comparison code out of the function.
5850 Closes ticket 21349.
5851 - Tor now assumes that you have standards-conformant stdint.h and
5852 inttypes.h headers when compiling. Closes ticket 26626.
5853 - Unify our bloom filter logic. Previously we had two copies of this
5854 code: one for routerlist filtering, and one for address set
5855 calculations. Closes ticket 26510.
5856 - Use the simpler strcmpstart() helper in
5857 rend_parse_v2_service_descriptor instead of strncmp(). Closes
5859 - Utility functions that can perform a DNS lookup are now wholly
5860 separated from those that can't, in separate headers and C
5861 modules. Closes ticket 26526.
5864 - Copy paragraph and URL to Tor's code of conduct document from
5865 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
5866 - Remove old instructions from INSTALL document. Closes ticket 26588.
5867 - Warn users that they should not include MyFamily line(s) in their
5868 torrc when running Tor bridge. Closes ticket 26908.
5871 - Tor no longer supports building with the dmalloc library. For
5872 debugging memory issues, we suggest using gperftools or msan
5873 instead. Closes ticket 26426.
5874 - Tor no longer attempts to run on Windows environments without the
5875 GetAdaptersAddresses() function. This function has existed since
5876 Windows XP, which is itself already older than we support.
5877 - Remove Tor2web functionality for version 2 onion services. The
5878 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
5879 (This feature was never shipped in vanilla Tor and it was only
5880 possible to use this feature by building the support at compile
5881 time. Tor2webMode is not implemented for version 3 onion services.)
5882 Closes ticket 26367.
5885 Changes in version 0.2.9.17 - 2018-09-10
5886 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
5888 o Minor features (compatibility, backport from 0.3.4.8):
5889 - Tell OpenSSL to maintain backward compatibility with previous
5890 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5891 ciphers are disabled by default. Closes ticket 27344.
5893 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5894 - Enable macOS builds in our Travis CI configuration. Closes
5896 - Install libcap-dev and libseccomp2-dev so these optional
5897 dependencies get tested on Travis CI. Closes ticket 26560.
5898 - Run asciidoc during Travis CI. Implements ticket 27087.
5899 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5901 o Minor features (geoip):
5902 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
5903 Country database. Closes ticket 27089.
5905 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
5906 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
5907 tell the compiler not to include the system malloc implementation.
5908 Fixes bug 20424; bugfix on 0.2.0.20-rc.
5910 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
5911 - Silence a spurious compiler warning on the GetAdaptersAddresses
5912 function pointer cast. This issue is already fixed by 26481 in
5913 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
5914 bugfix on 0.2.3.11-alpha.
5915 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
5916 supported, and always fails. Some compilers warn about the
5917 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
5920 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
5921 - Don't link or search for pthreads when building for Windows, even
5922 if we are using build environment (like mingw) that provides a
5923 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
5925 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
5926 - Skip a pair of unreliable key generation tests on Windows, until
5927 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
5928 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
5930 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
5931 - Pass the module flags to distcheck configure, and log the flags
5932 before running configure. (Backported to 0.2.9 and later as a
5933 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
5935 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
5936 - When a Travis build fails, and showing a log fails, keep trying to
5937 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
5938 - When we use echo in Travis, don't pass a --flag as the first
5939 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
5941 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
5942 - When voting for recommended versions, make sure that all of the
5943 versions are well-formed and parsable. Fixes bug 26485; bugfix
5946 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
5947 - Fix a bug in out sandboxing rules for the openat() syscall.
5948 Previously, no openat() call would be permitted, which would break
5949 filesystem operations on recent glibc versions. Fixes bug 25440;
5950 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
5952 o Minor bugfixes (onion services, backport from 0.3.4.8):
5953 - Silence a spurious compiler warning in
5954 rend_client_send_introduction(). Fixes bug 27463; bugfix
5957 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
5958 - Log a protocol warning when single onion services or Tor2web clients
5959 fail to authenticate direct connections to relays.
5960 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
5962 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
5963 - Disable core dumps in test_bt.sh, to avoid failures in "make
5964 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
5966 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
5967 - Before running make test-network-all, delete old logs and test
5968 result files, to avoid spurious failures. Fixes bug 27295; bugfix
5971 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
5972 - Our "tortls/cert_matches_key" unit test no longer relies on
5973 OpenSSL internals. Previously, it relied on unsupported OpenSSL
5974 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
5975 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
5977 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
5978 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
5979 27185; bugfix on 0.2.2.2-alpha.
5982 Changes in version 0.3.2.12 - 2018-09-10
5983 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
5985 o Minor features (compatibility, backport from 0.3.4.8):
5986 - Tell OpenSSL to maintain backward compatibility with previous
5987 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
5988 ciphers are disabled by default. Closes ticket 27344.
5990 o Minor features (continuous integration, backport from 0.3.4.7-rc):
5991 - Enable macOS builds in our Travis CI configuration. Closes
5993 - Install libcap-dev and libseccomp2-dev so these optional
5994 dependencies get tested on Travis CI. Closes ticket 26560.
5995 - Run asciidoc during Travis CI. Implements ticket 27087.
5996 - Use ccache in our Travis CI configuration. Closes ticket 26952.
5998 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
5999 - Use cargo cache in our Travis CI configuration. Closes
6002 o Minor features (controller, backport from 0.3.4.6-rc):
6003 - The control port now exposes the list of HTTPTunnelPorts and
6004 ExtOrPorts via GETINFO net/listeners/httptunnel and
6005 net/listeners/extor respectively. Closes ticket 26647.
6007 o Minor features (directory authorities, backport from 0.3.4.7-rc):
6008 - Authorities no longer vote to make the subprotocol version
6009 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6010 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6012 o Minor features (geoip):
6013 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6014 Country database. Closes ticket 27089.
6016 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6017 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6018 tell the compiler not to include the system malloc implementation.
6019 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6020 - Don't try to use a pragma to temporarily disable the
6021 -Wunused-const-variable warning if the compiler doesn't support
6022 it. Fixes bug 26785; bugfix on 0.3.2.11.
6024 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6025 - Silence a spurious compiler warning on the GetAdaptersAddresses
6026 function pointer cast. This issue is already fixed by 26481 in
6027 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6028 bugfix on 0.2.3.11-alpha.
6029 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6030 supported, and always fails. Some compilers warn about the
6031 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6034 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6035 - Don't link or search for pthreads when building for Windows, even
6036 if we are using build environment (like mingw) that provides a
6037 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6039 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6040 - Skip a pair of unreliable key generation tests on Windows, until
6041 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6042 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6044 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6045 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6046 - Pass the module flags to distcheck configure, and log the flags
6047 before running configure. (Backported to 0.2.9 and later as a
6048 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6050 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6051 - When a Travis build fails, and showing a log fails, keep trying to
6052 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6053 - When we use echo in Travis, don't pass a --flag as the first
6054 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6056 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6057 - When voting for recommended versions, make sure that all of the
6058 versions are well-formed and parsable. Fixes bug 26485; bugfix
6061 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6062 - Fix a bug in out sandboxing rules for the openat() syscall.
6063 Previously, no openat() call would be permitted, which would break
6064 filesystem operations on recent glibc versions. Fixes bug 25440;
6065 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6067 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
6068 - Improve the log message when connection initiators fail to
6069 authenticate direct connections to relays. Fixes bug 26927; bugfix
6072 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
6073 - Fix bug that causes services to not ever rotate their descriptors
6074 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6077 o Minor bugfixes (onion services, backport from 0.3.4.8):
6078 - Silence a spurious compiler warning in
6079 rend_client_send_introduction(). Fixes bug 27463; bugfix
6082 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6083 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6085 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6086 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6087 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6088 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6090 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6091 - Log a protocol warning when single onion services or Tor2web clients
6092 fail to authenticate direct connections to relays.
6093 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6095 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6096 - Disable core dumps in test_bt.sh, to avoid failures in "make
6097 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6099 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6100 - When running make test-network-all, use the mixed+hs-v2 network.
6101 (A previous fix to chutney removed v3 onion services from the
6102 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6103 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6104 - Before running make test-network-all, delete old logs and test
6105 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6108 o Minor bugfixes (testing, openssl compatibility):
6109 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
6110 internals. Previously, it relied on unsupported OpenSSL behavior in
6111 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
6112 bugfix on 0.2.5.1-alpha.
6114 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6115 - Our "tortls/cert_matches_key" unit test no longer relies on
6116 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6117 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6118 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6120 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6121 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6122 27185; bugfix on 0.2.2.2-alpha.
6125 Changes in version 0.3.3.10 - 2018-09-10
6126 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
6128 o Minor features (bug workaround, backport from 0.3.4.7-rc):
6129 - Compile correctly on systems that provide the C11 stdatomic.h
6130 header, but where C11 atomic functions don't actually compile.
6131 Closes ticket 26779; workaround for Debian issue 903709.
6133 o Minor features (compatibility, backport from 0.3.4.8):
6134 - Tell OpenSSL to maintain backward compatibility with previous
6135 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6136 ciphers are disabled by default. Closes ticket 27344.
6138 o Minor features (continuous integration, backport from 0.3.4.7-rc):
6139 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6140 - Enable macOS builds in our Travis CI configuration. Closes
6142 - Install libcap-dev and libseccomp2-dev so these optional
6143 dependencies get tested on Travis CI. Closes ticket 26560.
6144 - Run asciidoc during Travis CI. Implements ticket 27087.
6145 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6147 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
6148 - Use cargo cache in our Travis CI configuration. Closes
6151 o Minor features (controller, backport from 0.3.4.6-rc):
6152 - The control port now exposes the list of HTTPTunnelPorts and
6153 ExtOrPorts via GETINFO net/listeners/httptunnel and
6154 net/listeners/extor respectively. Closes ticket 26647.
6156 o Minor features (directory authorities, backport from 0.3.4.7-rc):
6157 - Authorities no longer vote to make the subprotocol version
6158 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6159 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6161 o Minor features (geoip):
6162 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6163 Country database. Closes ticket 27089.
6165 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
6166 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6167 tell the compiler not to include the system malloc implementation.
6168 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6169 - Don't try to use a pragma to temporarily disable the
6170 -Wunused-const-variable warning if the compiler doesn't support
6171 it. Fixes bug 26785; bugfix on 0.3.2.11.
6173 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
6174 - Silence a spurious compiler warning on the GetAdaptersAddresses
6175 function pointer cast. This issue is already fixed by 26481 in
6176 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6177 bugfix on 0.2.3.11-alpha.
6178 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6179 supported, and always fails. Some compilers warn about the
6180 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6183 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
6184 - Don't link or search for pthreads when building for Windows, even
6185 if we are using build environment (like mingw) that provides a
6186 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6188 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
6189 - Skip a pair of unreliable key generation tests on Windows, until
6190 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6191 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6193 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
6194 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6195 - Pass the module flags to distcheck configure, and log the flags
6196 before running configure. (Backported to 0.2.9 and later as a
6197 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6199 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
6200 - When a Travis build fails, and showing a log fails, keep trying to
6201 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6202 - When we use echo in Travis, don't pass a --flag as the first
6203 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6205 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
6206 - When voting for recommended versions, make sure that all of the
6207 versions are well-formed and parsable. Fixes bug 26485; bugfix
6210 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
6211 - Always call tor_free_all() when leaving tor_run_main(). When we
6212 did not, restarting tor in-process would cause an assertion
6213 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6215 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
6216 - Fix a bug in our sandboxing rules for the openat() syscall.
6217 Previously, no openat() call would be permitted, which would break
6218 filesystem operations on recent glibc versions. Fixes bug 25440;
6219 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6221 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
6222 - Improve the log message when connection initiators fail to
6223 authenticate direct connections to relays. Fixes bug 26927; bugfix
6226 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
6227 - Fix bug that causes services to not ever rotate their descriptors
6228 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6231 o Minor bugfixes (onion services, backport from 0.3.4.8):
6232 - Silence a spurious compiler warning in
6233 rend_client_send_introduction(). Fixes bug 27463; bugfix
6236 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
6237 - Work around two different bugs in the OS X 10.10 and later SDKs
6238 that would prevent us from successfully targeting earlier versions
6239 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6241 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
6242 - Fix compilation of the unit tests on GNU/Hurd, which does not
6243 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6246 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
6247 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6249 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6250 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6251 - Protover parsing was accepting the presence of whitespace in
6252 version strings, which the C implementation would choke on, e.g.
6253 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6254 - Protover parsing was ignoring a 2nd hyphen and everything after
6255 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6257 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6258 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6259 - cd to ${abs_top_builddir}/src/rust before running cargo in
6260 src/test/test_rust.sh. This makes the working directory consistent
6261 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6263 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
6264 - Log a protocol warning when single onion services or Tor2web clients
6265 fail to authenticate direct connections to relays.
6266 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
6268 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
6269 - Disable core dumps in test_bt.sh, to avoid failures in "make
6270 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6272 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
6273 - When running make test-network-all, use the mixed+hs-v2 network.
6274 (A previous fix to chutney removed v3 onion services from the
6275 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6276 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6277 - Before running make test-network-all, delete old logs and test
6278 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6281 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
6282 - Our "tortls/cert_matches_key" unit test no longer relies on
6283 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6284 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6285 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6287 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
6288 - Stop sending ed25519 link specifiers in v3 onion service introduce
6289 cells and descriptors, when the rendezvous or introduction point
6290 doesn't support ed25519 link authentication. Fixes bug 26627;
6291 bugfix on 0.3.2.4-alpha.
6293 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
6294 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6295 27185; bugfix on 0.2.2.2-alpha.
6298 Changes in version 0.3.4.8 - 2018-09-10
6299 Tor 0.3.4.8 is the first stable release in its series; it includes
6300 compilation and portability fixes.
6302 The Tor 0.3.4 series includes improvements for running Tor in
6303 low-power and embedded environments, which should help performance in
6304 general. We've begun work on better modularity, and included preliminary
6305 changes on the directory authority side to accommodate a new bandwidth
6306 measurement system. We've also integrated more continuous-integration
6307 systems into our development process, and made corresponding changes to
6308 Tor's testing infrastructure. Finally, we've continued to refine
6309 our anti-denial-of-service code.
6311 Below are the changes since 0.3.4.7-rc. For a complete list of changes
6312 since 0.3.3.9, see the ReleaseNotes file.
6314 o Minor features (compatibility):
6315 - Tell OpenSSL to maintain backward compatibility with previous
6316 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
6317 ciphers are disabled by default. Closes ticket 27344.
6319 o Minor features (continuous integration):
6320 - Log the compiler path and version during Appveyor builds.
6321 Implements ticket 27449.
6322 - Show config.log and test-suite.log after failed Appveyor builds.
6323 Also upload the zipped full logs as a build artifact. Implements
6326 o Minor bugfixes (compilation):
6327 - Silence a spurious compiler warning on the GetAdaptersAddresses
6328 function pointer cast. This issue is already fixed by 26481 in
6329 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
6330 bugfix on 0.2.3.11-alpha.
6331 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
6332 supported, and always fails. Some compilers warn about the
6333 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
6336 o Minor bugfixes (continuous integration):
6337 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
6338 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
6339 Executables compiled for 64-bit Windows with this version of gcc
6340 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
6341 27460; bugfix on 0.3.4.1-alpha.
6342 - When a Travis build fails, and showing a log fails, keep trying to
6343 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
6344 - When we use echo in Travis, don't pass a --flag as the first
6345 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
6347 o Minor bugfixes (onion services):
6348 - Silence a spurious compiler warning in
6349 rend_client_send_introduction(). Fixes bug 27463; bugfix
6352 o Minor bugfixes (testing, chutney):
6353 - When running make test-network-all, use the mixed+hs-v2 network.
6354 (A previous fix to chutney removed v3 onion services from the
6355 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
6356 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
6357 - Before running make test-network-all, delete old logs and test
6358 result files, to avoid spurious failures. Fixes bug 27295; bugfix
6361 Changes in version 0.3.4.7-rc - 2018-08-24
6362 Tor 0.3.4.7-rc fixes several small compilation, portability, and
6363 correctness issues in previous versions of Tor. This version is a
6364 release candidate: if no serious bugs are found, we expect that the
6365 stable 0.3.4 release will be (almost) the same as this release.
6367 o Minor features (bug workaround):
6368 - Compile correctly on systems that provide the C11 stdatomic.h
6369 header, but where C11 atomic functions don't actually compile.
6370 Closes ticket 26779; workaround for Debian issue 903709.
6372 o Minor features (continuous integration):
6373 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
6374 - Enable macOS builds in our Travis CI configuration. Closes
6376 - Install libcap-dev and libseccomp2-dev so these optional
6377 dependencies get tested on Travis CI. Closes ticket 26560.
6378 - Only post Appveyor IRC notifications when the build fails.
6379 Implements ticket 27275.
6380 - Run asciidoc during Travis CI. Implements ticket 27087.
6381 - Use ccache in our Travis CI configuration. Closes ticket 26952.
6383 o Minor features (continuous integration, rust):
6384 - Use cargo cache in our Travis CI configuration. Closes
6387 o Minor features (directory authorities):
6388 - Authorities no longer vote to make the subprotocol version
6389 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
6390 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
6392 o Minor features (geoip):
6393 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
6394 Country database. Closes ticket 27089.
6396 o Minor bugfixes (compilation, windows):
6397 - Don't link or search for pthreads when building for Windows, even
6398 if we are using build environment (like mingw) that provides a
6399 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
6401 o Minor bugfixes (continuous integration):
6402 - Improve Appveyor CI IRC logging. Generate correct branches and
6403 URLs for pull requests and tags. Use unambiguous short commits.
6404 Fixes bug 26979; bugfix on master.
6405 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
6406 - Pass the module flags to distcheck configure, and log the flags
6407 before running configure. (Backported to 0.2.9 and later as a
6408 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
6410 o Minor bugfixes (in-process restart):
6411 - Always call tor_free_all() when leaving tor_run_main(). When we
6412 did not, restarting tor in-process would cause an assertion
6413 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
6415 o Minor bugfixes (linux seccomp2 sandbox):
6416 - Fix a bug in out sandboxing rules for the openat() syscall.
6417 Previously, no openat() call would be permitted, which would break
6418 filesystem operations on recent glibc versions. Fixes bug 25440;
6419 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
6421 o Minor bugfixes (onion services):
6422 - Fix bug that causes services to not ever rotate their descriptors
6423 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
6426 o Minor bugfixes (portability):
6427 - Fix compilation of the unit tests on GNU/Hurd, which does not
6428 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
6431 o Minor bugfixes (rust):
6432 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
6434 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
6435 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
6436 - Protover parsing was accepting the presence of whitespace in
6437 version strings, which the C implementation would choke on, e.g.
6438 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
6439 - Protover parsing was ignoring a 2nd hyphen and everything after
6440 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
6442 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
6443 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
6444 - cd to ${abs_top_builddir}/src/rust before running cargo in
6445 src/test/test_rust.sh. This makes the working directory consistent
6446 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
6448 o Minor bugfixes (testing, bootstrap):
6449 - When calculating bootstrap progress, check exit policies and the
6450 exit flag. Previously, Tor would only check the exit flag, which
6451 caused race conditions in small and fast networks like chutney.
6452 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
6454 o Minor bugfixes (testing, openssl compatibility):
6455 - Our "tortls/cert_matches_key" unit test no longer relies on
6456 OpenSSL internals. Previously, it relied on unsupported OpenSSL
6457 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
6458 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
6460 o Minor bugfixes (Windows, compilation):
6461 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
6462 27185; bugfix on 0.2.2.2-alpha.
6465 Changes in version 0.3.4.6-rc - 2018-08-06
6466 Tor 0.3.4.6-rc fixes several small compilation, portability, and
6467 correctness issues in previous versions of Tor. This version is a
6468 release candidate: if no serious bugs are found, we expect that the
6469 stable 0.3.4 release will be (almost) the same as this release.
6471 o Major bugfixes (event scheduler):
6472 - When we enable a periodic event, schedule it in the event loop
6473 rather than running it immediately. Previously, we would re-run
6474 periodic events immediately in the middle of (for example)
6475 changing our options, with unpredictable effects. Fixes bug 27003;
6476 bugfix on 0.3.4.1-alpha.
6478 o Minor features (compilation):
6479 - When building Tor, prefer to use Python 3 over Python 2, and more
6480 recent (contemplated) versions over older ones. Closes
6482 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
6483 tell the compiler not to include the system malloc implementation.
6484 Fixes bug 20424; bugfix on 0.2.0.20-rc.
6485 - Don't try to use a pragma to temporarily disable the
6486 -Wunused-const-variable warning if the compiler doesn't support
6487 it. Fixes bug 26785; bugfix on 0.3.2.11.
6489 o Minor bugfixes (continuous integration):
6490 - Skip a pair of unreliable key generation tests on Windows, until
6491 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
6492 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
6494 o Minor features (controller):
6495 - The control port now exposes the list of HTTPTunnelPorts and
6496 ExtOrPorts via GETINFO net/listeners/httptunnel and
6497 net/listeners/extor respectively. Closes ticket 26647.
6499 o Minor bugfixes (directory authority):
6500 - When voting for recommended versions, make sure that all of the
6501 versions are well-formed and parsable. Fixes bug 26485; bugfix
6504 o Minor features (geoip):
6505 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6506 Country database. Closes ticket 26674.
6508 o Minor features (Rust, portability):
6509 - Rust cross-compilation is now supported. Closes ticket 25895.
6511 o Minor bugfixes (compilation):
6512 - Update build system so that tor builds again with --disable-unittests
6513 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
6514 - Fix a compilation warning on some versions of GCC when building
6515 code that calls routerinfo_get_my_routerinfo() twice, assuming
6516 that the second call will succeed if the first one did. Fixes bug
6517 26269; bugfix on 0.2.8.2-alpha.
6519 o Minor bugfixes (controller):
6520 - Report the port correctly when a port is configured to bind to
6521 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
6522 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
6523 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
6524 on 0.3.3.1-alpha. Patch by "akwizgran".
6526 o Minor bugfixes (correctness, flow control):
6527 - Upon receiving a stream-level SENDME cell, verify that our window
6528 has not grown too large. Fixes bug 26214; bugfix on svn
6531 o Minor bugfixes (memory, correctness):
6532 - Fix a number of small memory leaks identified by coverity. Fixes
6533 bug 26467; bugfix on numerous Tor versions.
6535 o Minor bugfixes (logging):
6536 - Improve the log message when connection initiators fail to
6537 authenticate direct connections to relays. Fixes bug 26927; bugfix
6540 o Minor bugfixes (portability):
6541 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
6542 26994; bugfix on 0.3.4.1-alpha.
6543 - Work around two different bugs in the OS X 10.10 and later SDKs
6544 that would prevent us from successfully targeting earlier versions
6545 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
6547 o Minor bugfixes (single onion services, Tor2web):
6548 - Log a protocol warning when single onion services or Tor2web
6549 clients fail to authenticate direct connections to relays. Fixes
6550 bug 26924; bugfix on 0.2.9.1-alpha.
6552 o Minor bugfixes (testing):
6553 - Disable core dumps in test_bt.sh, to avoid failures in "make
6554 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
6556 o Minor bugfixes (testing, compatibility):
6557 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
6558 only to pass strings (rather than "bytes" objects) to the Python
6559 subprocess module. Python 3 on Windows seems to require this.
6560 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
6561 0.3.1.1-alpha (for hs_ntor_ref.py).
6563 o Minor bugfixes (v3 onion services):
6564 - Stop sending ed25519 link specifiers in v3 onion service introduce
6565 cells and descriptors, when the rendezvous or introduction point
6566 doesn't support ed25519 link authentication. Fixes bug 26627;
6567 bugfix on 0.3.2.4-alpha.
6570 Changes in version 0.3.4.5-rc - 2018-07-13
6571 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
6572 bridge relays should upgrade.
6574 o Directory authority changes:
6575 - The "Bifroest" bridge authority has been retired; the new bridge
6576 authority is "Serge", and it is operated by George from the
6577 TorBSD project. Closes ticket 26771.
6580 Changes in version 0.3.3.9 - 2018-07-13
6581 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
6582 bridge relays should upgrade.
6584 o Directory authority changes:
6585 - The "Bifroest" bridge authority has been retired; the new bridge
6586 authority is "Serge", and it is operated by George from the
6587 TorBSD project. Closes ticket 26771.
6590 Changes in version 0.3.2.11 - 2018-07-13
6591 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
6592 bridge relays should upgrade. We also take this opportunity to backport
6595 o Directory authority changes:
6596 - The "Bifroest" bridge authority has been retired; the new bridge
6597 authority is "Serge", and it is operated by George from the
6598 TorBSD project. Closes ticket 26771.
6600 o Directory authority changes (backport from 0.3.3.7):
6601 - Add an IPv6 address for the "dannenberg" directory authority.
6602 Closes ticket 26343.
6604 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6605 - When directory authorities read a zero-byte bandwidth file, they
6606 would previously log a warning with the contents of an
6607 uninitialised buffer. They now log a warning about the empty file
6608 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6610 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
6611 - Correctly detect when onion services get disabled after HUP. Fixes
6612 bug 25761; bugfix on 0.3.2.1.
6614 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6615 - Explicitly permit the poll() system call when the Linux
6616 seccomp2-based sandbox is enabled: apparently, some versions of
6617 libc use poll() when calling getpwnam(). Closes ticket 25313.
6619 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
6620 - Update the Travis CI configuration to use the stable Rust channel,
6621 now that we have decided to require that. Closes ticket 25714.
6623 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6624 - Our .travis.yml configuration now includes support for testing the
6625 results of "make distcheck". (It's not uncommon for "make check"
6626 to pass but "make distcheck" to fail.) Closes ticket 25814.
6627 - Our Travis CI configuration now integrates with the Coveralls
6628 coverage analysis tool. Closes ticket 25818.
6630 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6631 - Add several checks to detect whether Tor relays are uploading
6632 their descriptors without specifying why they regenerated them.
6633 Diagnostic for ticket 25686.
6635 o Minor features (compilation, backport from 0.3.4.4-rc):
6636 - When building Tor, prefer to use Python 3 over Python 2, and more
6637 recent (contemplated) versions over older ones. Closes
6640 o Minor features (geoip):
6641 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6642 Country database. Closes ticket 26674.
6644 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6645 - Upon receiving a malformed connected cell, stop processing the
6646 cell immediately. Previously we would mark the connection for
6647 close, but continue processing the cell as if the connection were
6648 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6650 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6651 - Allow the nanosleep() system call, which glibc uses to implement
6652 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6654 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6655 - When running the hs_ntor_ref.py test, make sure only to pass
6656 strings (rather than "bytes" objects) to the Python subprocess
6657 module. Python 3 on Windows seems to require this. Fixes bug
6658 26535; bugfix on 0.3.1.1-alpha.
6659 - When running the ntor_ref.py test, make sure only to pass strings
6660 (rather than "bytes" objects) to the Python subprocess module.
6661 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6664 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6665 - Work around a change in OpenSSL 1.1.1 where return values that
6666 would previously indicate "no password" now indicate an empty
6667 password. Without this workaround, Tor instances running with
6668 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6669 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6671 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
6672 - Document that the PerConnBW{Rate,Burst} options will fall back to
6673 their corresponding consensus parameters only if those parameters
6674 are set. Previously we had claimed that these values would always
6675 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
6677 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6678 - Fix a compilation warning on some versions of GCC when building
6679 code that calls routerinfo_get_my_routerinfo() twice, assuming
6680 that the second call will succeed if the first one did. Fixes bug
6681 26269; bugfix on 0.2.8.2-alpha.
6683 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6684 - Don't consider Tor running as a client if the ControlPort is open,
6685 but no actual client ports are open. Fixes bug 26062; bugfix
6688 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6689 - Prevent a possible out-of-bounds smartlist read in
6690 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6692 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6693 - Fix a very unlikely (impossible, we believe) null pointer
6694 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6695 Coverity; this is CID 1430932.
6697 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
6698 - Fix a memory leak when a v3 onion service is configured and gets a
6699 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
6700 - When parsing the descriptor signature, look for the token plus an
6701 extra white-space at the end. This is more correct but also will
6702 allow us to support new fields that might start with "signature".
6703 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
6705 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6706 - Relays now correctly block attempts to re-extend to the previous
6707 relay by Ed25519 identity. Previously they would warn in this
6708 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6711 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
6712 - Avoid a crash when running with DirPort set but ORPort turned off.
6713 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
6715 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
6716 - Silence unused-const-variable warnings in zstd.h with some GCC
6717 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
6719 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
6720 - Avoid intermittent test failures due to a test that had relied on
6721 onion service introduction point creation finishing within 5
6722 seconds of real clock time. Fixes bug 25450; bugfix
6725 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
6726 - Fix a C99 compliance issue in our configuration script that caused
6727 compilation issues when compiling Tor with certain versions of
6728 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
6730 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6731 - Fix a number of small memory leaks identified by coverity. Fixes
6732 bug 26467; bugfix on numerous Tor versions.
6734 o Code simplification and refactoring (backport from 0.3.3.5-rc):
6735 - Move the list of default directory authorities to its own file.
6736 Closes ticket 24854. Patch by "beastr0".
6739 Changes in version 0.2.9.16 - 2018-07-13
6740 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
6741 bridge relays should upgrade. We also take this opportunity to backport
6744 o Directory authority changes:
6745 - The "Bifroest" bridge authority has been retired; the new bridge
6746 authority is "Serge", and it is operated by George from the
6747 TorBSD project. Closes ticket 26771.
6749 o Directory authority changes (backport from 0.3.3.7):
6750 - Add an IPv6 address for the "dannenberg" directory authority.
6751 Closes ticket 26343.
6753 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
6754 - When directory authorities read a zero-byte bandwidth file, they
6755 would previously log a warning with the contents of an
6756 uninitialised buffer. They now log a warning about the empty file
6757 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
6759 o Minor features (sandbox, backport from 0.3.3.4-alpha):
6760 - Explicitly permit the poll() system call when the Linux
6761 seccomp2-based sandbox is enabled: apparently, some versions of
6762 libc use poll() when calling getpwnam(). Closes ticket 25313.
6764 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
6765 - Our .travis.yml configuration now includes support for testing the
6766 results of "make distcheck". (It's not uncommon for "make check"
6767 to pass but "make distcheck" to fail.) Closes ticket 25814.
6768 - Our Travis CI configuration now integrates with the Coveralls
6769 coverage analysis tool. Closes ticket 25818.
6771 o Minor features (compilation, backport from 0.3.4.4-rc):
6772 - When building Tor, prefer to use Python 3 over Python 2, and more
6773 recent (contemplated) versions over older ones. Closes
6776 o Minor features (geoip):
6777 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6778 Country database. Closes ticket 26674.
6780 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
6781 - Upon receiving a malformed connected cell, stop processing the
6782 cell immediately. Previously we would mark the connection for
6783 close, but continue processing the cell as if the connection were
6784 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
6786 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
6787 - Allow the nanosleep() system call, which glibc uses to implement
6788 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
6790 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6791 - When running the ntor_ref.py test, make sure only to pass strings
6792 (rather than "bytes" objects) to the Python subprocess module.
6793 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6796 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
6797 - Work around a change in OpenSSL 1.1.1 where return values that
6798 would previously indicate "no password" now indicate an empty
6799 password. Without this workaround, Tor instances running with
6800 OpenSSL 1.1.1 would accept descriptors that other Tor instances
6801 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
6803 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6804 - Fix a compilation warning on some versions of GCC when building
6805 code that calls routerinfo_get_my_routerinfo() twice, assuming
6806 that the second call will succeed if the first one did. Fixes bug
6807 26269; bugfix on 0.2.8.2-alpha.
6809 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
6810 - Don't consider Tor running as a client if the ControlPort is open,
6811 but no actual client ports are open. Fixes bug 26062; bugfix
6814 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
6815 - Prevent a possible out-of-bounds smartlist read in
6816 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
6818 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
6819 - Fix a very unlikely (impossible, we believe) null pointer
6820 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
6821 Coverity; this is CID 1430932.
6823 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6824 - Fix a number of small memory leaks identified by coverity. Fixes
6825 bug 26467; bugfix on numerous Tor versions.
6827 o Code simplification and refactoring (backport from 0.3.3.5-rc):
6828 - Move the list of default directory authorities to its own file.
6829 Closes ticket 24854. Patch by "beastr0".
6832 Changes in version 0.3.4.4-rc - 2018-07-09
6833 Tor 0.3.4.4-rc fixes several small compilation, portability, and
6834 correctness issues in previous versions of Tor. This version is a
6835 release candidate: if no serious bugs are found, we expect that the
6836 stable 0.3.4 release will be (almost) the same as this release.
6838 o Minor features (compilation):
6839 - When building Tor, prefer to use Python 3 over Python 2, and more
6840 recent (contemplated) versions over older ones. Closes
6843 o Minor features (geoip):
6844 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6845 Country database. Closes ticket 26674.
6847 o Minor features (Rust, portability):
6848 - Rust cross-compilation is now supported. Closes ticket 25895.
6850 o Minor bugfixes (compilation):
6851 - Fix a compilation warning on some versions of GCC when building
6852 code that calls routerinfo_get_my_routerinfo() twice, assuming
6853 that the second call will succeed if the first one did. Fixes bug
6854 26269; bugfix on 0.2.8.2-alpha.
6856 o Minor bugfixes (control port):
6857 - Report the port correctly when a port is configured to bind to
6858 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
6859 - Handle the HSADDRESS= argument to the HSPOST command properly.
6860 (Previously, this argument was misparsed and thus ignored.) Fixes
6861 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
6863 o Minor bugfixes (correctness, flow control):
6864 - Upon receiving a stream-level SENDME cell, verify that our window
6865 has not grown too large. Fixes bug 26214; bugfix on svn
6868 o Minor bugfixes (memory, correctness):
6869 - Fix a number of small memory leaks identified by coverity. Fixes
6870 bug 26467; bugfix on numerous Tor versions.
6872 o Minor bugfixes (testing, compatibility):
6873 - When running the hs_ntor_ref.py test, make sure only to pass
6874 strings (rather than "bytes" objects) to the Python subprocess
6875 module. Python 3 on Windows seems to require this. Fixes bug
6876 26535; bugfix on 0.3.1.1-alpha.
6877 - When running the ntor_ref.py test, make sure only to pass strings
6878 (rather than "bytes" objects) to the Python subprocess module.
6879 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6883 Changes in version 0.3.3.8 - 2018-07-09
6884 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
6885 fixes for a memory leak affecting directory authorities.
6887 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
6888 - Stop leaking memory on directory authorities when planning to
6889 vote. This bug was crashing authorities by exhausting their
6890 memory. Fixes bug 26435; bugfix on 0.3.3.6.
6892 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
6893 - Make sure that failing tests in Rust will actually cause the build
6894 to fail: previously, they were ignored. Fixes bug 26258; bugfix
6897 o Minor features (compilation, backport from 0.3.4.4-rc):
6898 - When building Tor, prefer to use Python 3 over Python 2, and more
6899 recent (contemplated) versions over older ones. Closes
6902 o Minor features (geoip):
6903 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
6904 Country database. Closes ticket 26674.
6906 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
6907 - Add several checks to detect whether Tor relays are uploading
6908 their descriptors without specifying why they regenerated them.
6909 Diagnostic for ticket 25686.
6911 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
6912 - Don't count path selection failures as circuit build failures.
6913 This change should eliminate cases where Tor blames its guard or
6914 the network for situations like insufficient microdescriptors
6915 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
6918 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
6919 - Fix a compilation warning on some versions of GCC when building
6920 code that calls routerinfo_get_my_routerinfo() twice, assuming
6921 that the second call will succeed if the first one did. Fixes bug
6922 26269; bugfix on 0.2.8.2-alpha.
6924 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
6925 - Handle the HSADDRESS= argument to the HSPOST command properly.
6926 (Previously, this argument was misparsed and thus ignored.) Fixes
6927 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
6929 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
6930 - Fix a number of small memory leaks identified by coverity. Fixes
6931 bug 26467; bugfix on numerous Tor versions.
6933 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
6934 - Relays now correctly block attempts to re-extend to the previous
6935 relay by Ed25519 identity. Previously they would warn in this
6936 case, but not actually reject the attempt. Fixes bug 26158; bugfix
6939 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
6940 - When shutting down, Tor now clears all the flags in the control.c
6941 module. This should prevent a bug where authentication cookies are
6942 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
6944 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
6945 - When running the hs_ntor_ref.py test, make sure only to pass
6946 strings (rather than "bytes" objects) to the Python subprocess
6947 module. Python 3 on Windows seems to require this. Fixes bug
6948 26535; bugfix on 0.3.1.1-alpha.
6949 - When running the ntor_ref.py test, make sure only to pass strings
6950 (rather than "bytes" objects) to the Python subprocess module.
6951 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
6955 Changes in version 0.3.4.3-alpha - 2018-06-26
6956 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
6957 one that was causing stability issues on directory authorities.
6959 o Major bugfixes (directory authority):
6960 - Stop leaking memory on directory authorities when planning to
6961 vote. This bug was crashing authorities by exhausting their
6962 memory. Fixes bug 26435; bugfix on 0.3.3.6.
6964 o Major bugfixes (rust, testing):
6965 - Make sure that failing tests in Rust will actually cause the build
6966 to fail: previously, they were ignored. Fixes bug 26258; bugfix
6969 o Minor feature (directory authorities):
6970 - Stop warning about incomplete bw lines before the first complete
6971 bw line has been found, so that additional header lines can be
6972 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
6974 o Minor features (relay, diagnostic):
6975 - Add several checks to detect whether Tor relays are uploading
6976 their descriptors without specifying why they regenerated them.
6977 Diagnostic for ticket 25686.
6979 o Minor features (unit tests):
6980 - Test complete bandwidth measurements files, and test that
6981 incomplete bandwidth lines only give warnings when the end of the
6982 header has not been detected. Fixes bug 25947; bugfix
6985 o Minor bugfixes (compilation):
6986 - Refrain from compiling unit testing related object files when
6987 --disable-unittests is set to configure script. Fixes bug 24891;
6988 bugfix on 0.2.5.1-alpha.
6989 - When linking the libtor_testing.a library, only include the
6990 dirauth object files once. Previously, they were getting added
6991 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
6992 - The --enable-fatal-warnings flag now affects Rust code as well.
6993 Closes ticket 26245.
6995 o Minor bugfixes (onion services):
6996 - Recompute some consensus information after detecting a clock jump,
6997 or after transitioning from a non-live consensus to a live
6998 consensus. We do this to avoid having an outdated state, and
6999 miscalculating the index for next-generation onion services. Fixes
7000 bug 24977; bugfix on 0.3.2.1-alpha.
7002 o Minor bugfixes (relay):
7003 - Relays now correctly block attempts to re-extend to the previous
7004 relay by Ed25519 identity. Previously they would warn in this
7005 case, but not actually reject the attempt. Fixes bug 26158; bugfix
7008 o Minor bugfixes (testing):
7009 - Fix compilation of the doctests in the Rust crypto crate. Fixes
7010 bug 26415; bugfix on 0.3.4.1-alpha.
7011 - Instead of trying to read the geoip configuration files from
7012 within the unit tests, instead create our own ersatz files with
7013 just enough geoip data in the format we expect. Trying to read
7014 from the source directory created problems on Windows with mingw,
7015 where the build system's paths are not the same as the platform's
7016 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
7017 - Refrain from trying to get an item from an empty smartlist in
7018 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
7019 to catch improper smartlist usage. Furthermore, enable
7020 DEBUG_SMARTLIST globally when build is configured with fragile
7021 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
7024 Changes in version 0.3.3.7 - 2018-06-12
7025 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
7026 fixes for bugs affecting compatibility and stability.
7028 o Directory authority changes:
7029 - Add an IPv6 address for the "dannenberg" directory authority.
7030 Closes ticket 26343.
7032 o Minor features (geoip):
7033 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
7034 Country database. Closes ticket 26351.
7036 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
7037 - Work around a change in OpenSSL 1.1.1 where return values that
7038 would previously indicate "no password" now indicate an empty
7039 password. Without this workaround, Tor instances running with
7040 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7041 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7043 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
7044 - Silence unused-const-variable warnings in zstd.h with some GCC
7045 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7047 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
7048 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
7049 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
7050 miscounting the total number of circuits for these field values.)
7051 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
7053 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
7054 - Prevent a possible out-of-bounds smartlist read in
7055 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7057 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
7058 - Only select relays when they have the descriptors we prefer to use
7059 for them. This change fixes a bug where we could select a relay
7060 because it had _some_ descriptor, but reject it later with a
7061 nonfatal assertion error because it didn't have the exact one we
7062 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
7065 Changes in version 0.3.4.2-alpha - 2018-06-12
7066 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
7067 release, and forward-ports an authority-only security fix from 0.3.3.6.
7069 o Directory authority changes:
7070 - Add an IPv6 address for the "dannenberg" directory authority.
7071 Closes ticket 26343.
7073 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
7074 - Fix a bug that could have allowed an attacker to force a directory
7075 authority to use up all its RAM by passing it a maliciously
7076 crafted protocol versions string. Fixes bug 25517; bugfix on
7077 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
7079 o Minor features (continuous integration):
7080 - Add the necessary configuration files for continuous integration
7081 testing on Windows, via the Appveyor platform. Closes ticket
7082 25549. Patches from Marcin Cieślak and Isis Lovecruft.
7084 o Minor features (geoip):
7085 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
7086 Country database. Closes ticket 26351.
7088 o Minor bugfixes (compatibility, openssl):
7089 - Work around a change in OpenSSL 1.1.1 where return values that
7090 would previously indicate "no password" now indicate an empty
7091 password. Without this workaround, Tor instances running with
7092 OpenSSL 1.1.1 would accept descriptors that other Tor instances
7093 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
7095 o Minor bugfixes (compilation):
7096 - Silence unused-const-variable warnings in zstd.h with some GCC
7097 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
7098 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
7099 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
7100 - Avoid a compiler warning when casting the return value of
7101 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
7102 26283; bugfix on 0.2.4.10-alpha.
7104 o Minor bugfixes (control port):
7105 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
7106 CIRC_BW events. Previously, such cells were counted entirely in
7107 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
7110 o Minor bugfixes (controller):
7111 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
7112 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
7113 miscounting the total number of circuits for these field values.)
7114 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
7116 o Minor bugfixes (hardening):
7117 - Prevent a possible out-of-bounds smartlist read in
7118 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
7120 o Minor bugfixes (onion services):
7121 - Fix a bug that blocked the creation of ephemeral v3 onion
7122 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
7124 o Minor bugfixes (test coverage tools):
7125 - Update our "cov-diff" script to handle output from the latest
7126 version of gcov, and to remove extraneous timestamp information
7127 from its output. Fixes bugs 26101 and 26102; bugfix
7131 Changes in version 0.3.3.6 - 2018-05-22
7132 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
7133 backports several important fixes from the 0.3.4.1-alpha.
7135 The Tor 0.3.3 series includes controller support and other
7136 improvements for v3 onion services, official support for embedding Tor
7137 within other applications, and our first non-trivial module written in
7138 the Rust programming language. (Rust is still not enabled by default
7139 when building Tor.) And as usual, there are numerous other smaller
7140 bugfixes, features, and improvements.
7142 Below are the changes since 0.3.3.5-rc. For a list of all changes
7143 since 0.3.2.10, see the ReleaseNotes file.
7145 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
7146 - When directory authorities read a zero-byte bandwidth file, they
7147 would previously log a warning with the contents of an
7148 uninitialised buffer. They now log a warning about the empty file
7149 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7151 o Major bugfixes (security, directory authority, denial-of-service):
7152 - Fix a bug that could have allowed an attacker to force a directory
7153 authority to use up all its RAM by passing it a maliciously
7154 crafted protocol versions string. Fixes bug 25517; bugfix on
7155 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
7157 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
7158 - Avoid a rare assertion failure in the circuit build timeout code
7159 if we fail to allow any circuits to actually complete. Fixes bug
7160 25733; bugfix on 0.2.2.2-alpha.
7162 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
7163 - Avoid a crash when testing router reachability on a router that
7164 could have an ed25519 ID, but which does not. Fixes bug 25415;
7165 bugfix on 0.3.3.2-alpha.
7167 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
7168 - Correctly detect when onion services get disabled after HUP. Fixes
7169 bug 25761; bugfix on 0.3.2.1.
7171 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
7172 - Impose a limit on circuit cell queue size. The limit can be
7173 controlled by a consensus parameter. Fixes bug 25226; bugfix
7176 o Minor features (compatibility, backport from 0.3.4.1-alpha):
7177 - Avoid some compilation warnings with recent versions of LibreSSL.
7178 Closes ticket 26006.
7180 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
7181 - Our .travis.yml configuration now includes support for testing the
7182 results of "make distcheck". (It's not uncommon for "make check"
7183 to pass but "make distcheck" to fail.) Closes ticket 25814.
7184 - Our Travis CI configuration now integrates with the Coveralls
7185 coverage analysis tool. Closes ticket 25818.
7187 o Minor features (geoip):
7188 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
7189 database. Closes ticket 26104.
7191 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
7192 - Don't consider Tor running as a client if the ControlPort is open,
7193 but no actual client ports are open. Fixes bug 26062; bugfix
7196 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
7197 - Upon receiving a malformed connected cell, stop processing the
7198 cell immediately. Previously we would mark the connection for
7199 close, but continue processing the cell as if the connection were
7200 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
7202 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
7203 - Stop saying in the manual that clients cache ipv4 dns answers from
7204 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7205 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7206 we forgot to say so in the man page. Fixes bug 26052; bugfix
7209 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
7210 - Allow the nanosleep() system call, which glibc uses to implement
7211 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7213 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
7214 - Fix a memory leak when a v3 onion service is configured and gets a
7215 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7216 - When parsing the descriptor signature, look for the token plus an
7217 extra white-space at the end. This is more correct but also will
7218 allow us to support new fields that might start with "signature".
7219 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7221 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
7222 - Avoid a crash when running with DirPort set but ORPort turned off.
7223 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7225 o Documentation (backport from 0.3.4.1-alpha):
7226 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
7227 ticket 25857. Patch from "CTassisF".
7230 Changes in version 0.3.4.1-alpha - 2018-05-17
7231 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
7232 includes refactoring to begin reducing Tor's binary size and idle CPU
7233 usage on mobile, along with prep work for new bandwidth scanners,
7234 improvements to the experimental "vanguards" feature, and numerous
7235 other small features and bugfixes.
7237 o New system requirements:
7238 - Tor no longer tries to support old operating systems without
7239 mmap() or some local equivalent. Apparently, compilation on such
7240 systems has been broken for some time, without anybody noticing or
7241 complaining. Closes ticket 25398.
7243 o Major feature (directory authority, modularization):
7244 - The directory authority subsystem has been modularized. The code
7245 is now located in src/or/dirauth/, and is compiled in by default.
7246 To disable the module, the configure option
7247 --disable-module-dirauth has been added. This module may be
7248 disabled by default in some future release. Closes ticket 25610.
7250 o Major features (main loop, CPU usage):
7251 - When Tor is disabled (via DisableNetwork or via hibernation), it
7252 no longer needs to run any per-second events. This change should
7253 make it easier for mobile applications to disable Tor while the
7254 device is sleeping, or Tor is not running. Closes ticket 26063.
7255 - Tor no longer enables all of its periodic events by default.
7256 Previously, Tor would enable all possible main loop events,
7257 regardless of whether it needed them. Furthermore, many of these
7258 events are now disabled with Tor is hibernating or DisableNetwork
7259 is set. This is a big step towards reducing client CPU usage by
7260 reducing the amount of wake-ups the daemon does. Closes ticket
7262 - The bandwidth-limitation logic has been refactored so that
7263 bandwidth calculations are performed on-demand, rather than every
7264 TokenBucketRefillInterval milliseconds. This change should improve
7265 the granularity of our bandwidth calculations, and limit the
7266 number of times that the Tor process needs to wake up when it is
7267 idle. Closes ticket 25373.
7268 - Move responsibility for many operations from a once-per-second
7269 callback to a callback that is only scheduled as needed. Moving
7270 this functionality has allowed us to disable the callback when
7271 Tor's network is disabled. Once enough items are removed from our
7272 once-per-second callback, we can eliminate it entirely to conserve
7273 CPU when idle. The functionality removed includes: closing
7274 connections, circuits, and channels (ticket 25932); consensus
7275 voting (25937); flushing log callbacks (25951); honoring delayed
7276 SIGNEWNYM requests (25949); rescanning the consensus cache
7277 (25931); saving the state file to disk (25948); warning relay
7278 operators about unreachable ports (25952); and keeping track of
7279 Tor's uptime (26009).
7281 o Major bugfixes (directory authorities, security):
7282 - When directory authorities read a zero-byte bandwidth file, they
7283 would previously log a warning with the contents of an
7284 uninitialised buffer. They now log a warning about the empty file
7285 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
7287 o Major bugfixes (crash):
7288 - Avoid a rare assertion failure in the circuit build timeout code
7289 if we fail to allow any circuits to actually complete. Fixes bug
7290 25733; bugfix on 0.2.2.2-alpha.
7292 o Major bugfixes (directory authority):
7293 - Avoid a crash when testing router reachability on a router that
7294 could have an ed25519 ID, but which does not. Fixes bug 25415;
7295 bugfix on 0.3.3.2-alpha.
7297 o Major bugfixes (onion service):
7298 - Correctly detect when onion services get disabled after HUP. Fixes
7299 bug 25761; bugfix on 0.3.2.1.
7301 o Major bugfixes (protover, voting):
7302 - Revise Rust implementation of protover to use a more memory-
7303 efficient voting algorithm and corresponding data structures, thus
7304 avoiding a potential (but small impact) DoS attack where specially
7305 crafted protocol strings would expand to several potential
7306 megabytes in memory. In the process, several portions of code were
7307 revised to be methods on new, custom types, rather than functions
7308 taking interchangeable types, thus increasing type safety of the
7309 module. Custom error types and handling were added as well, in
7310 order to facilitate better error dismissal/handling in outside
7311 crates and avoid mistakenly passing an internal error string to C
7312 over the FFI boundary. Many tests were added, and some previous
7313 differences between the C and Rust implementations have been
7314 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
7316 o Major bugfixes (relay, denial of service):
7317 - Impose a limit on circuit cell queue size. The limit can be
7318 controlled by a consensus parameter. Fixes bug 25226; bugfix
7321 o Minor features (accounting):
7322 - When Tor becomes dormant, it now uses a scheduled event to wake up
7323 at the right time. Previously, we would use the per-second timer
7324 to check whether to wake up, but we no longer have any per-second
7325 timers enabled when the network is disabled. Closes ticket 26064.
7327 o Minor features (code quality):
7328 - Add optional spell-checking for the Tor codebase, using the
7329 "misspell" program. To use this feature, run "make check-typos".
7330 Closes ticket 25024.
7332 o Minor features (compatibility):
7333 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
7334 the no-deprecated option, and builds correctly with them. Closes
7335 tickets 19429, 19981, and 25353.
7336 - Avoid some compilation warnings with recent versions of LibreSSL.
7337 Closes ticket 26006.
7339 o Minor features (compression, zstd):
7340 - When running with zstd, Tor now considers using advanced functions
7341 that the zstd maintainers have labeled as potentially unstable. To
7342 prevent breakage, Tor will only use this functionality when the
7343 runtime version of the zstd library matches the version with which
7344 Tor was compiled. Closes ticket 25162.
7346 o Minor features (configuration):
7347 - The "DownloadSchedule" options have been renamed to end with
7348 "DownloadInitialDelay". The old names are still allowed, but will
7349 produce a warning. Comma-separated lists are still permitted for
7350 these options, but all values after the first are ignored (as they
7351 have been since 0.2.9). Closes ticket 23354.
7353 o Minor features (continuous integration):
7354 - Our .travis.yml configuration now includes support for testing the
7355 results of "make distcheck". (It's not uncommon for "make check"
7356 to pass but "make distcheck" to fail.) Closes ticket 25814.
7357 - Our Travis CI configuration now integrates with the Coveralls
7358 coverage analysis tool. Closes ticket 25818.
7360 o Minor features (control port):
7361 - Introduce GETINFO "current-time/{local,utc}" to return the local
7362 and UTC times respectively in ISO format. This helps a controller
7363 like Tor Browser detect a time-related error. Closes ticket 25511.
7364 Patch by Neel Chauhan.
7365 - Introduce new fields to the CIRC_BW event. There are two new
7366 fields in each of the read and written directions. The DELIVERED
7367 fields report the total valid data on the circuit, as measured by
7368 the payload sizes of verified and error-checked relay command
7369 cells. The OVERHEAD fields report the total unused bytes in each
7370 of these cells. Closes ticket 25903.
7372 o Minor features (directory authority):
7373 - Directory authorities now open their key-pinning files as O_SYNC,
7374 to limit their chances of accidentally writing partial lines.
7375 Closes ticket 23909.
7377 o Minor features (directory authority, forward compatibility):
7378 - Make the lines of the measured bandwidth file able to contain
7379 their entries in any order. Previously, the node_id entry needed
7380 to come first. Closes ticket 26004.
7382 o Minor features (entry guards):
7383 - Introduce a new torrc option NumPrimaryGuards for controlling the
7384 number of primary guards. Closes ticket 25843.
7386 o Minor features (geoip):
7387 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
7388 database. Closes ticket 26104.
7390 o Minor features (performance):
7391 - Avoid a needless call to malloc() when processing an incoming
7392 relay cell. Closes ticket 24914.
7393 - Make our timing-wheel code run a tiny bit faster on 32-bit
7394 platforms, by preferring 32-bit math to 64-bit. Closes
7396 - Avoid a needless malloc()/free() pair every time we handle an ntor
7397 handshake. Closes ticket 25150.
7399 o Minor features (testing):
7400 - Add a unit test for voting_schedule_get_start_of_next_interval().
7401 Closes ticket 26014, and helps make unit test coverage
7403 - A new unittests module specifically for testing the functions in
7404 the (new-ish) bridges.c module has been created with new
7405 unittests, raising the code coverage percentages. Closes 25425.
7406 - We now have improved testing for addressmap_get_virtual_address()
7407 function. This should improve our test coverage, and make our test
7408 coverage more deterministic. Closes ticket 25993.
7410 o Minor features (timekeeping, circuit scheduling):
7411 - When keeping track of how busy each circuit have been recently on
7412 a given connection, use coarse-grained monotonic timers rather
7413 than gettimeofday(). This change should marginally increase
7414 accuracy and performance. Implements part of ticket 25927.
7416 o Minor bugfixes (bandwidth management):
7417 - Consider ourselves "low on write bandwidth" if we have exhausted
7418 our write bandwidth some time in the last second. This was the
7419 documented behavior before, but the actual behavior was to change
7420 this value every TokenBucketRefillInterval. Fixes bug 25828;
7421 bugfix on 0.2.3.5-alpha.
7423 o Minor bugfixes (C correctness):
7424 - Add a missing lock acquisition in the shutdown code of the control
7425 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
7426 Coverity; this is CID 1433643.
7428 o Minor bugfixes (circuit path selection):
7429 - Don't count path selection failures as circuit build failures.
7430 This change should eliminate cases where Tor blames its guard or
7431 the network for situations like insufficient microdescriptors
7432 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
7435 o Minor bugfixes (client):
7436 - Don't consider Tor running as a client if the ControlPort is open,
7437 but no actual client ports are open. Fixes bug 26062; bugfix
7440 o Minor bugfixes (code style):
7441 - Fixed multiple includes of transports.h in src/or/connection.c
7442 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
7443 - Remove the unused variable n_possible from the function
7444 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
7446 o Minor bugfixes (control interface):
7447 - Respond with more human-readable error messages to GETINFO exit-
7448 policy/* requests. Also, let controller know if an error is
7449 transient (response code 551) or not (response code 552). Fixes
7450 bug 25852; bugfix on 0.2.8.1-alpha.
7452 o Minor bugfixes (controller):
7453 - Make CIRC_BW event reflect the total of all data sent on a
7454 circuit, including padding and dropped cells. Also fix a mis-
7455 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
7456 bugfix on 0.2.5.2-alpha.
7458 o Minor bugfixes (correctness, client):
7459 - Upon receiving a malformed connected cell, stop processing the cell
7460 immediately. Previously we would mark the connection for close, but
7461 continue processing the cell as if the connection were open. Fixes bug
7462 26072; bugfix on 0.2.4.7-alpha.
7464 o Minor bugfixes (directory client):
7465 - When unverified-consensus is verified, rename it to cached-
7466 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
7467 - Fixed launching a certificate fetch always during the scheduled
7468 periodic consensus fetch by fetching only in those cases when
7469 consensus are waiting for certs. Fixes bug 24740; bugfix
7472 o Minor bugfixes (documentation):
7473 - Stop saying in the manual that clients cache ipv4 dns answers from
7474 exit relays. We haven't used them since 0.2.6.3-alpha, and in
7475 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
7476 we forgot to say so in the man page. Fixes bug 26052; bugfix
7479 o Minor bugfixes (error reporting):
7480 - Improve tolerance for directory authorities with skewed clocks.
7481 Previously, an authority with a clock more than 60 seconds ahead
7482 could cause a client with a correct clock to warn that the
7483 client's clock was behind. Now the clocks of a majority of
7484 directory authorities have to be ahead of the client before this
7485 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
7487 o Minor bugfixes (Linux seccomp2 sandbox):
7488 - Allow the nanosleep() system call, which glibc uses to implement
7489 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
7491 o Minor bugfixes (onion service):
7492 - Fix a memory leak when a v3 onion service is configured and gets a
7493 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
7494 - When parsing the descriptor signature, look for the token plus an
7495 extra white-space at the end. This is more correct but also will
7496 allow us to support new fields that might start with "signature".
7497 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
7499 o Minor bugfixes (path selection):
7500 - Only select relays when they have the descriptors we prefer to use
7501 for them. This change fixes a bug where we could select a relay
7502 because it had _some_ descriptor, but reject it later with a
7503 nonfatal assertion error because it didn't have the exact one we
7504 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
7506 o Minor bugfixes (portability):
7507 - Do not align mmap length, as it is not required by POSIX, and the
7508 getpagesize function is deprecated. Fixes bug 25399; bugfix
7511 o Minor bugfixes (portability, FreeBSD):
7512 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
7513 does not stringify on FreeBSD, so we switch to tor_asprintf().
7514 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
7516 o Minor bugfixes (relay statistics):
7517 - When a relay is collecting internal statistics about how many
7518 create cell requests it has seen of each type, accurately count
7519 the requests from relays that temporarily fall out of the
7520 consensus. (To be extra conservative, we were already ignoring
7521 requests from clients in our counts, and we continue ignoring them
7522 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
7524 o Minor bugfixes (relay, crash):
7525 - Avoid a crash when running with DirPort set but ORPort turned off.
7526 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
7528 o Minor bugfixes (restart-in-process):
7529 - When shutting down, Tor now clears all the flags in the control.c
7530 module. This should prevent a bug where authentication cookies are
7531 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
7533 o Minor bugfixes (testing):
7534 - When testing workqueue event-cancellation, make sure that we
7535 actually cancel an event, and that cancel each event with equal
7536 probability. (It was previously possible, though extremely
7537 unlikely, for our event-canceling test not to cancel any events.)
7538 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
7539 - Repeat part of the test in test_client_pick_intro() a number of
7540 times, to give it consistent coverage. Fixes bug 25996; bugfix
7542 - Remove randomness from the hs_common/responsible_hsdirs test, so
7543 that it always takes the same path through the function it tests.
7544 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
7545 - Change the behavior of the "channel/outbound" test so that it
7546 never causes a 10-second rollover for the EWMA circuitmux code.
7547 Previously, this behavior would happen randomly, and result in
7548 fluctuating test coverage. Fixes bug 25994; bugfix
7550 - Use X509_new() to allocate certificates that will be freed later
7551 with X509_free(). Previously, some parts of the unit tests had
7552 used tor_malloc_zero(), which is incorrect, and which caused test
7553 failures on Windows when they were built with extra hardening.
7554 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
7556 - While running the circuit_timeout test, fix the PRNG to a
7557 deterministic AES stream, so that the test coverage from this test
7558 will itself be deterministic. Fixes bug 25995; bugfix
7561 o Minor bugfixes (vanguards):
7562 - Allow the last hop in a vanguard circuit to be the same as our
7563 first, to prevent the adversary from influencing guard node choice
7564 by choice of last hop. Also prevent the creation of A - B - A
7565 paths, or A - A paths, which are forbidden by relays. Fixes bug
7566 25870; bugfix on 0.3.3.1-alpha.
7568 o Code simplification and refactoring:
7569 - Remove duplicate code in parse_{c,s}method_line and bootstrap
7570 their functionalities into a single function. Fixes bug 6236;
7571 bugfix on 0.2.3.6-alpha.
7572 - We remove the PortForwarding and PortForwardingHelper options,
7573 related functions, and the port_forwarding tests. These options
7574 were used by the now-deprecated Vidalia to help ordinary users
7575 become Tor relays or bridges. Closes ticket 25409. Patch by
7577 - In order to make the OR and dir checking function in router.c less
7578 confusing we renamed some functions and
7579 consider_testing_reachability() has been split into
7580 router_should_check_reachability() and
7581 router_do_reachability_checks(). Also we improved the documentation
7582 in some functions. Closes ticket 18918.
7583 - Initial work to isolate Libevent usage to a handful of modules in
7584 our codebase, to simplify our call structure, and so that we can
7585 more easily change event loops in the future if needed. Closes
7587 - Introduce a function to call getsockname() and return tor_addr_t,
7588 to save a little complexity throughout the codebase. Closes
7590 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
7591 as hsdir_index is always present. Also, we move hsdir_index_t into
7592 or.h. Closes ticket 23094. Patch by Neel Chauhan.
7593 - Merge functions used for describing nodes and suppress the
7594 functions that do not allocate memory for the output buffer
7595 string. NODE_DESC_BUF_LEN constant and format_node_description()
7596 function cannot be used externally from router.c module anymore.
7597 Closes ticket 25432. Patch by valentecaio.
7598 - Our main loop has been simplified so that all important operations
7599 happen inside events. Previously, some operations had to happen
7600 outside the event loop, to prevent infinite sequences of event
7601 activations. Closes ticket 25374.
7602 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
7603 it in register_intro_circ() and service_intro_point_new(). This
7604 prevents the digest from being re-calculated each time. Closes
7605 ticket 23107. Patch by Neel Chauhan.
7606 - Refactor token-bucket implementations to use a common backend.
7607 Closes ticket 25766.
7608 - Remove extern declaration of stats_n_seconds_working variable from
7609 main, protecting its accesses with get_uptime() and reset_uptime()
7610 functions. Closes ticket 25081, patch by “valentecaio”.
7611 - Remove our previous logic for "cached gettimeofday()" -- our
7612 coarse monotonic timers are fast enough for this purpose, and far
7613 less error-prone. Implements part of ticket 25927.
7614 - Remove the return value for fascist_firewall_choose_address_base(),
7615 and sister functions such as fascist_firewall_choose_address_node()
7616 and fascist_firewall_choose_address_rs(). Also, while we're here,
7617 initialize the ap argument as leaving it uninitialized can pose a
7618 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
7619 - Rename two fields of connection_t struct. timestamp_lastwritten is
7620 renamed to timestamp_last_write_allowed and timestamp_lastread is
7621 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
7623 - Since Tor requires C99, remove our old workaround code for libc
7624 implementations where free(NULL) doesn't work. Closes ticket 24484.
7625 - Use our standard rate-limiting code to deal with excessive
7626 libevent failures, rather than the hand-rolled logic we had
7627 before. Closes ticket 26016.
7628 - We remove the return value of node_get_prim_orport() and
7629 node_get_prim_dirport(), and introduce node_get_prim_orport() in
7630 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
7631 check for a null address. Closes ticket 23873. Patch by
7633 - We switch to should_record_bridge_info() in
7634 geoip_note_client_seen() and options_need_geoip_info() instead of
7635 accessing the configuration values directly. Fixes bug 25290;
7636 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
7638 o Deprecated features:
7639 - As we are not recommending 0.2.5 anymore, we require relays that
7640 once had an ed25519 key associated with their RSA key to always
7641 have that key, instead of allowing them to drop back to a version
7642 that didn't support ed25519. This means they need to use a new RSA
7643 key if they want to downgrade to an older version of tor without
7644 ed25519. Closes ticket 20522.
7647 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
7648 ticket 25857. Patch from "CTassisF".
7651 - Directory authorities will no longer support voting according to
7652 any consensus method before consensus method 25. This keeps
7653 authorities compatible with all authorities running 0.2.9.8 and
7654 later, and does not break any clients or relays. Implements ticket
7655 24378 and proposal 290.
7656 - The PortForwarding and PortForwardingHelper features have been
7657 removed. The reasoning is, given that implementations of NAT
7658 traversal protocols within common consumer grade routers are
7659 frequently buggy, and that the target audience for a NAT punching
7660 feature is a perhaps less-technically-inclined relay operator,
7661 when the helper fails to setup traversal the problems are usually
7662 deep, ugly, and very router specific, making them horrendously
7663 impossible for technical support to reliable assist with, and thus
7664 resulting in frustration all around. Unfortunately, relay
7665 operators who would like to run relays behind NATs will need to
7666 become more familiar with the port forwarding configurations on
7667 their local router. Closes 25409.
7668 - The TestingEnableTbEmptyEvent option has been removed. It was used
7669 in testing simulations to measure how often connection buckets
7670 were emptied, in order to improve our scheduling, but it has not
7671 been actively used in years. Closes ticket 25760.
7672 - The old "round-robin" circuit multiplexer (circuitmux)
7673 implementation has been removed, along with a fairly large set of
7674 code that existed to support it. It has not been the default
7675 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
7676 but it still required an unreasonable amount of memory and CPU.
7677 Closes ticket 25268.
7680 Changes in version 0.3.3.5-rc - 2018-04-15
7681 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
7682 including some that could affect reliability or correctness.
7684 This is the first release candidate in the 0.3.3 series. If we find no
7685 new bugs or regression here, then the first stable 0.3.3 release will
7686 be nearly identical to this one.
7688 o Major bugfixes (security, protover, voting):
7689 - Revise Rust implementation of protover to use a more memory-
7690 efficient voting algorithm and corresponding data structures, thus
7691 avoiding a potential memory-based DoS attack where specially
7692 crafted protocol strings would expand to fill available memory.
7693 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
7695 o Major bugfixes (performance, load balancing):
7696 - Directory authorities no longer vote in favor of the Guard flag
7697 for relays without directory support. Starting in Tor
7698 0.3.0.1-alpha, clients have been avoiding using such relays in the
7699 Guard position, leading to increasingly broken load balancing for
7700 the 5%-or-so of Guards that don't advertise directory support.
7701 Fixes bug 22310; bugfix on 0.3.0.6.
7703 o Minor feature (continuous integration):
7704 - Update the Travis CI configuration to use the stable Rust channel,
7705 now that we have decided to require that. Closes ticket 25714.
7707 o Minor features (config options):
7708 - Change the way the default value for MaxMemInQueues is calculated.
7709 We now use 40% of the hardware RAM if the system has 8 GB RAM or
7710 more. Otherwise we use the former value of 75%. Closes
7713 o Minor features (geoip):
7714 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
7715 Country database. Closes ticket 25718.
7717 o Minor bugfixes (client):
7718 - When using a listed relay as a bridge, and also using
7719 microdescriptors, and considering that relay as a non-bridge in a
7720 circuit, treat its microdescriptor as a valid source of
7721 information about that relay. This change should prevent a non-
7722 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
7724 o Minor bugfixes (controller):
7725 - Restore the correct operation of the RESOLVE command, which had
7726 been broken since we added the ability to enable/disable DNS on
7727 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
7729 o Minor bugfixes (distribution, compilation, rust):
7730 - Build correctly when the rust dependencies submodule is loaded,
7731 but the TOR_RUST_DEPENDENCIES environment variable is not set.
7732 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
7733 - Actually include all of our Rust source in our source
7734 distributions. (Previously, a few of the files were accidentally
7735 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
7737 o Minor bugfixes (documentation):
7738 - Document that the PerConnBW{Rate,Burst} options will fall back to
7739 their corresponding consensus parameters only if those parameters
7740 are set. Previously we had claimed that these values would always
7741 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
7742 - Revert a misformatting issue in the ExitPolicy documentation.
7743 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
7745 o Minor bugfixes (exit relay DNS retries):
7746 - Re-attempt timed-out DNS queries 3 times before failure, since our
7747 timeout is 5 seconds for them, but clients wait 10-15. Also allow
7748 slightly more timeouts per resolver when an exit has multiple
7749 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
7751 o Minor bugfixes (onion services):
7752 - Re-instate counting the client HSDir fetch circuits against the
7753 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
7755 - Remove underscores from the _HSLayer{2,3}Nodes options. This
7756 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
7757 Fixes bug 25581; bugfix on 0.3.3.1-alpha
7759 o Code simplification and refactoring:
7760 - Move the list of default directory authorities to its own file.
7761 Closes ticket 24854. Patch by "beastr0".
7763 o Documentation (manpage, denial of service):
7764 - Provide more detail about the denial-of-service options, by
7765 listing each mitigation and explaining how they relate. Closes
7769 Changes in version 0.3.3.4-alpha - 2018-03-29
7770 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
7771 the alpha testing of earlier releases in its series. We are
7772 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
7774 o New system requirements:
7775 - When built with Rust, Tor now depends on version 0.2.39 of the
7776 libc crate. Closes tickets 25310 and 25664.
7778 o Major bugfixes (relay, connection):
7779 - If we have failed to connect to a relay and received a connection
7780 refused, timeout, or similar error (at the TCP level), do not try
7781 that same address/port again for 60 seconds after the failure has
7782 occurred. Fixes bug 24767; bugfix on 0.0.6.
7784 o Minor features (geoip):
7785 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
7786 Country database. Closes ticket 25469.
7788 o Minor features (log messages):
7789 - Improve log message in the out-of-memory handler to include
7790 information about memory usage from the different compression
7791 backends. Closes ticket 25372.
7793 o Minor features (sandbox):
7794 - Explicitly permit the poll() system call when the Linux
7795 seccomp2-based sandbox is enabled: apparently, some versions of
7796 libc use poll() when calling getpwnam(). Closes ticket 25313.
7798 o Minor bugfixes (C correctness):
7799 - Fix a very unlikely (impossible, we believe) null pointer
7800 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
7801 Coverity; this is CID 1430932.
7803 o Minor bugfixes (channel, client):
7804 - Better identify client connection when reporting to the geoip
7805 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
7807 o Minor bugfixes (compilation):
7808 - Fix a C99 compliance issue in our configuration script that caused
7809 compilation issues when compiling Tor with certain versions of
7810 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
7812 o Minor bugfixes (controller, reliability):
7813 - Avoid a (nonfatal) assertion failure when extending a one-hop
7814 circuit from the controller to become a multihop circuit. Fixes
7815 bug 24903; bugfix on 0.2.5.2-alpha.
7817 o Major bugfixes (networking):
7818 - Tor will no longer reject IPv6 address strings from Tor Browser
7819 when they are passed as hostnames in SOCKS5 requests. Fixes bug
7820 25036, bugfix on Tor 0.3.1.2.
7822 o Minor bugfixes (networking):
7823 - string_is_valid_hostname() will not consider IP strings to be
7824 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
7826 o Minor bugfixes (onion service v3):
7827 - Avoid an assertion failure when the next onion service
7828 descriptor rotation type is out of sync with the consensus's
7829 valid-after time. Instead, log a warning message with extra
7830 information, so we can better hunt down the cause of this
7831 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
7833 o Minor bugfixes (testing):
7834 - Avoid intermittent test failures due to a test that had relied on
7835 onion service introduction point creation finishing within 5
7836 seconds of real clock time. Fixes bug 25450; bugfix
7838 - Rust crates are now automatically detected and tested. Previously,
7839 some crates were not tested by `make test-rust` due to a static
7840 string in the `src/test/test_rust.sh` script specifying which
7841 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
7843 o Minor bugfixes (testing, benchmarks):
7844 - Fix a crash when running benchmark tests on win32 systems. The
7845 crash was due to a mutex that wasn't initialized before logging
7846 and options were initialized. Fixes bug 25479; bugfix
7849 o Minor bugfixes (warnings, ipv6):
7850 - Avoid a bug warning that could occur when trying to connect to a
7851 relay over IPv6. This warning would occur on a Tor instance that
7852 downloads router descriptors, but prefers to use microdescriptors.
7853 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
7855 o Code simplification and refactoring:
7856 - Remove the old (deterministic) directory retry logic entirely:
7857 We've used exponential backoff exclusively for some time. Closes
7861 - Improved the documentation of AccountingStart parameter. Closes
7863 - Update the documentation for "Log" to include the current list of
7864 logging domains. Closes ticket 25378.
7867 Changes in version 0.3.1.10 - 2018-03-03
7868 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
7871 It includes an important security fix for a remote crash attack
7872 against directory authorities, tracked as TROVE-2018-001.
7874 This release also backports our new system for improved resistance to
7875 denial-of-service attacks against relays.
7877 This release also fixes several minor bugs and annoyances from
7880 All directory authorities should upgrade to one of the versions
7881 released today. Relays running 0.3.1.x may wish to update to one of
7882 the versions released today, for the DoS mitigations.
7884 Please note: according to our release calendar, Tor 0.3.1 will no
7885 longer be supported after 1 July 2018. If you will be running Tor
7886 after that date, you should make sure to plan to upgrade to the latest
7887 stable version, or downgrade to 0.2.9 (which will receive long-term
7890 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
7891 - Fix a protocol-list handling bug that could be used to remotely crash
7892 directory authorities with a null-pointer exception. Fixes bug 25074;
7893 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
7896 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
7897 - Give relays some defenses against the recent network overload. We
7898 start with three defenses (default parameters in parentheses).
7899 First: if a single client address makes too many concurrent
7900 connections (>100), hang up on further connections. Second: if a
7901 single client address makes circuits too quickly (more than 3 per
7902 second, with an allowed burst of 90) while also having too many
7903 connections open (3), refuse new create cells for the next while
7904 (1-2 hours). Third: if a client asks to establish a rendezvous
7905 point to you directly, ignore the request. These defenses can be
7906 manually controlled by new torrc options, but relays will also
7907 take guidance from consensus parameters, so there's no need to
7908 configure anything manually. Implements ticket 24902.
7910 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
7911 - Update the sandbox rules so that they should now work correctly
7912 with Glibc 2.26. Closes ticket 24315.
7914 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
7915 - Fix an "off by 2" error in counting rendezvous failures on the
7916 onion service side. While we thought we would stop the rendezvous
7917 attempt after one failed circuit, we were actually making three
7918 circuit attempts before giving up. Now switch to a default of 2,
7919 and allow the consensus parameter "hs_service_max_rdv_failures" to
7920 override. Fixes bug 24895; bugfix on 0.0.6.
7922 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
7923 - Add Link protocol version 5 to the supported protocols list. Fixes
7924 bug 25070; bugfix on 0.3.1.1-alpha.
7926 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
7927 - Fix a set of false positives where relays would consider
7928 connections to other relays as being client-only connections (and
7929 thus e.g. deserving different link padding schemes) if those
7930 relays fell out of the consensus briefly. Now we look only at the
7931 initial handshake and whether the connection authenticated as a
7932 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
7934 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
7935 - Make our OOM handler aware of the geoip client history cache so it
7936 doesn't fill up the memory. This check is important for IPv6 and
7937 our DoS mitigation subsystem. Closes ticket 25122.
7939 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
7940 - Change relay bandwidth reporting stats interval from 4 hours to 24
7941 hours in order to reduce the efficiency of guard discovery
7942 attacks. Fixes ticket 23856.
7944 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
7945 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
7946 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
7947 since they neither disabled TLS 1.3 nor enabled any of the
7948 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
7949 Closes ticket 24978.
7951 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
7952 - The fallback directory list has been re-generated based on the
7953 current status of the network. Tor uses fallback directories to
7954 bootstrap when it doesn't yet have up-to-date directory
7955 information. Closes ticket 24801.
7956 - Make the default DirAuthorityFallbackRate 0.1, so that clients
7957 prefer to bootstrap from fallback directory mirrors. This is a
7958 follow-up to 24679, which removed weights from the default
7959 fallbacks. Implements ticket 24681.
7961 o Minor features (geoip):
7962 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
7965 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
7966 - Use the actual observed address of an incoming relay connection,
7967 not the canonical address of the relay from its descriptor, when
7968 making decisions about how to handle the incoming connection.
7969 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
7971 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
7972 - Directory authorities, when refusing a descriptor from a rejected
7973 relay, now explicitly tell the relay (in its logs) to set a valid
7974 ContactInfo address and contact the bad-relays@ mailing list.
7975 Fixes bug 25170; bugfix on 0.2.9.1.
7977 o Minor bugfixes (address selection, backport from 0.3.2.9):
7978 - When the fascist_firewall_choose_address_ functions don't find a
7979 reachable address, set the returned address to the null address
7980 and port. This is a precautionary measure, because some callers do
7981 not check the return value. Fixes bug 24736; bugfix
7984 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
7985 - Fetch descriptors aggressively whenever we lack enough to build
7986 circuits, regardless of how many descriptors we are missing.
7987 Previously, we would delay launching the fetch when we had fewer
7988 than 15 missing descriptors, even if some of those descriptors
7989 were blocking circuits from building. Fixes bug 23985; bugfix on
7990 0.1.1.11-alpha. The effects of this bug became worse in
7991 0.3.0.3-alpha, when we began treating missing descriptors from our
7992 primary guards as a reason to delay circuits.
7993 - Don't try fetching microdescriptors from relays that have failed
7994 to deliver them in the past. Fixes bug 23817; bugfix
7997 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
7998 - Fix a signed/unsigned comparison warning introduced by our fix to
7999 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8001 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
8002 - Avoid a crash when attempting to use the seccomp2 sandbox together
8003 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8006 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8007 - Fix a possible crash on malformed consensus. If a consensus had
8008 contained an unparseable protocol line, it could have made clients
8009 and relays crash with a null-pointer exception. To exploit this
8010 issue, however, an attacker would need to be able to subvert the
8011 directory authority system. Fixes bug 25251; bugfix on
8012 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8014 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
8015 - Recover better from empty or corrupt files in the consensus cache
8016 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
8017 - When a consensus diff calculation is only partially successful,
8018 only record the successful parts as having succeeded. Partial
8019 success can happen if (for example) one compression method fails
8020 but the others succeed. Previously we misrecorded all the
8021 calculations as having succeeded, which would later cause a
8022 nonfatal assertion failure. Fixes bug 24086; bugfix
8025 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
8026 - Tor now updates its guard state when it reads a consensus
8027 regardless of whether it's missing descriptors. That makes tor use
8028 its primary guards to fetch descriptors in some edge cases where
8029 it would previously have used fallback directories. Fixes bug
8030 23862; bugfix on 0.3.0.1-alpha.
8032 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8033 - Don't treat inability to store a cached consensus object as a bug:
8034 it can happen normally when we are out of disk space. Fixes bug
8035 24859; bugfix on 0.3.1.1-alpha.
8037 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
8038 - When queuing DESTROY cells on a channel, only queue the circuit-id
8039 and reason fields: not the entire 514-byte cell. This fix should
8040 help mitigate any bugs or attacks that fill up these queues, and
8041 free more RAM for other uses. Fixes bug 24666; bugfix
8044 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
8045 - When closing a connection via close_connection_immediately(), we
8046 mark it as "not blocked on bandwidth", to prevent later calls from
8047 trying to unblock it, and give it permission to read. This fixes a
8048 backtrace warning that can happen on relays under various
8049 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8051 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
8052 - When selecting relays by bandwidth, avoid a rounding error that
8053 could sometimes cause load to be imbalanced incorrectly.
8054 Previously, we would always round upwards; now, we round towards
8055 the nearest integer. This had the biggest effect when a relay's
8056 weight adjustments should have given it weight 0, but it got
8057 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8058 - When calculating the fraction of nodes that have descriptors, and
8059 all nodes in the network have zero bandwidths, count the number of
8060 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8061 - Actually log the total bandwidth in compute_weighted_bandwidths().
8062 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8064 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8065 - Improve the performance of our consensus-diff application code
8066 when Tor is built with the --enable-fragile-hardening option set.
8067 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8069 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8070 - Don't exit the Tor process if setrlimit() fails to change the file
8071 limit (which can happen sometimes on some versions of OSX). Fixes
8072 bug 21074; bugfix on 0.0.9pre5.
8074 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
8075 - Fix a bug in the bit-counting parts of our timing-wheel code on
8076 MSVC. (Note that MSVC is still not a supported build platform, due
8077 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
8080 o Minor bugfixes (relay, partial backport):
8081 - Make the internal channel_is_client() function look at what sort
8082 of connection handshake the other side used, rather than whether
8083 the other side ever sent a create_fast cell to us. Backports part
8084 of the fixes from bugs 22805 and 24898.
8086 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8087 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8089 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8090 bugfix on 0.2.9.4-alpha.
8092 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8093 - Update the "rust dependencies" submodule to be a project-level
8094 repository, rather than a user repository. Closes ticket 25323.
8097 Changes in version 0.2.9.15 - 2018-03-03
8098 Tor 0.2.9.15 backports important security and stability bugfixes from
8101 It includes an important security fix for a remote crash attack
8102 against directory authorities, tracked as TROVE-2018-001.
8104 This release also backports our new system for improved resistance to
8105 denial-of-service attacks against relays.
8107 This release also fixes several minor bugs and annoyances from
8110 All directory authorities should upgrade to one of the versions
8111 released today. Relays running 0.2.9.x may wish to update to one of
8112 the versions released today, for the DoS mitigations.
8114 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8115 - Fix a protocol-list handling bug that could be used to remotely crash
8116 directory authorities with a null-pointer exception. Fixes bug 25074;
8117 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8120 o Major features (denial-of-service mitigation):
8121 - Give relays some defenses against the recent network overload. We
8122 start with three defenses (default parameters in parentheses).
8123 First: if a single client address makes too many concurrent
8124 connections (>100), hang up on further connections. Second: if a
8125 single client address makes circuits too quickly (more than 3 per
8126 second, with an allowed burst of 90) while also having too many
8127 connections open (3), refuse new create cells for the next while
8128 (1-2 hours). Third: if a client asks to establish a rendezvous
8129 point to you directly, ignore the request. These defenses can be
8130 manually controlled by new torrc options, but relays will also
8131 take guidance from consensus parameters, so there's no need to
8132 configure anything manually. Implements ticket 24902.
8134 o Major bugfixes (bootstrapping):
8135 - Fetch descriptors aggressively whenever we lack enough to build
8136 circuits, regardless of how many descriptors we are missing.
8137 Previously, we would delay launching the fetch when we had fewer
8138 than 15 missing descriptors, even if some of those descriptors
8139 were blocking circuits from building. Fixes bug 23985; bugfix on
8140 0.1.1.11-alpha. The effects of this bug became worse in
8141 0.3.0.3-alpha, when we began treating missing descriptors from our
8142 primary guards as a reason to delay circuits.
8144 o Major bugfixes (onion services, retry behavior):
8145 - Fix an "off by 2" error in counting rendezvous failures on the
8146 onion service side. While we thought we would stop the rendezvous
8147 attempt after one failed circuit, we were actually making three
8148 circuit attempts before giving up. Now switch to a default of 2,
8149 and allow the consensus parameter "hs_service_max_rdv_failures" to
8150 override. Fixes bug 24895; bugfix on 0.0.6.
8152 o Minor feature (relay statistics):
8153 - Change relay bandwidth reporting stats interval from 4 hours to 24
8154 hours in order to reduce the efficiency of guard discovery
8155 attacks. Fixes ticket 23856.
8157 o Minor features (compatibility, OpenSSL):
8158 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8159 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8160 since they neither disabled TLS 1.3 nor enabled any of the
8161 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8162 Closes ticket 24978.
8164 o Minor features (denial-of-service avoidance):
8165 - Make our OOM handler aware of the geoip client history cache so it
8166 doesn't fill up the memory. This check is important for IPv6 and
8167 our DoS mitigation subsystem. Closes ticket 25122.
8169 o Minor features (fallback directory mirrors):
8170 - The fallback directory list has been re-generated based on the
8171 current status of the network. Tor uses fallback directories to
8172 bootstrap when it doesn't yet have up-to-date directory
8173 information. Closes ticket 24801.
8174 - Make the default DirAuthorityFallbackRate 0.1, so that clients
8175 prefer to bootstrap from fallback directory mirrors. This is a
8176 follow-up to 24679, which removed weights from the default
8177 fallbacks. Implements ticket 24681.
8179 o Minor features (geoip):
8180 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8183 o Minor features (linux seccomp2 sandbox):
8184 - Update the sandbox rules so that they should now work correctly
8185 with Glibc 2.26. Closes ticket 24315.
8187 o Minor bugfix (channel connection):
8188 - Use the actual observed address of an incoming relay connection,
8189 not the canonical address of the relay from its descriptor, when
8190 making decisions about how to handle the incoming connection.
8191 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8193 o Minor bugfix (directory authority):
8194 - Directory authorities, when refusing a descriptor from a rejected
8195 relay, now explicitly tell the relay (in its logs) to set a valid
8196 ContactInfo address and contact the bad-relays@ mailing list.
8197 Fixes bug 25170; bugfix on 0.2.9.1.
8199 o Minor bugfixes (address selection):
8200 - When the fascist_firewall_choose_address_ functions don't find a
8201 reachable address, set the returned address to the null address
8202 and port. This is a precautionary measure, because some callers do
8203 not check the return value. Fixes bug 24736; bugfix
8206 o Minor bugfixes (compilation):
8207 - Fix a signed/unsigned comparison warning introduced by our fix to
8208 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
8210 o Minor bugfixes (control port, linux seccomp2 sandbox):
8211 - Avoid a crash when attempting to use the seccomp2 sandbox together
8212 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
8215 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8216 - Fix a possible crash on malformed consensus. If a consensus had
8217 contained an unparseable protocol line, it could have made clients
8218 and relays crash with a null-pointer exception. To exploit this
8219 issue, however, an attacker would need to be able to subvert the
8220 directory authority system. Fixes bug 25251; bugfix on
8221 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8223 o Minor bugfixes (memory usage):
8224 - When queuing DESTROY cells on a channel, only queue the circuit-id
8225 and reason fields: not the entire 514-byte cell. This fix should
8226 help mitigate any bugs or attacks that fill up these queues, and
8227 free more RAM for other uses. Fixes bug 24666; bugfix
8230 o Minor bugfixes (network layer):
8231 - When closing a connection via close_connection_immediately(), we
8232 mark it as "not blocked on bandwidth", to prevent later calls from
8233 trying to unblock it, and give it permission to read. This fixes a
8234 backtrace warning that can happen on relays under various
8235 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
8237 o Minor bugfixes (OSX):
8238 - Don't exit the Tor process if setrlimit() fails to change the file
8239 limit (which can happen sometimes on some versions of OSX). Fixes
8240 bug 21074; bugfix on 0.0.9pre5.
8242 o Minor bugfixes (path selection):
8243 - When selecting relays by bandwidth, avoid a rounding error that
8244 could sometimes cause load to be imbalanced incorrectly.
8245 Previously, we would always round upwards; now, we round towards
8246 the nearest integer. This had the biggest effect when a relay's
8247 weight adjustments should have given it weight 0, but it got
8248 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
8249 - When calculating the fraction of nodes that have descriptors, and
8250 all nodes in the network have zero bandwidths, count the number of
8251 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
8252 - Actually log the total bandwidth in compute_weighted_bandwidths().
8253 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
8255 o Minor bugfixes (portability, msvc):
8256 - Fix a bug in the bit-counting parts of our timing-wheel code on
8257 MSVC. (Note that MSVC is still not a supported build platform, due
8258 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
8261 o Minor bugfixes (relay):
8262 - Make the internal channel_is_client() function look at what sort
8263 of connection handshake the other side used, rather than whether
8264 the other side ever sent a create_fast cell to us. Backports part
8265 of the fixes from bugs 22805 and 24898.
8267 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8268 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8270 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8271 bugfix on 0.2.9.4-alpha.
8274 Changes in version 0.3.2.10 - 2018-03-03
8275 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
8276 backports a number of bugfixes, including important fixes for security
8279 It includes an important security fix for a remote crash attack
8280 against directory authorities, tracked as TROVE-2018-001.
8282 Additionally, it backports a fix for a bug whose severity we have
8283 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
8284 triggered in order to crash relays with a use-after-free pattern. As
8285 such, we are now tracking that bug as TROVE-2018-002 and
8286 CVE-2018-0491, and backporting it to earlier releases. This bug
8287 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
8290 This release also backports our new system for improved resistance to
8291 denial-of-service attacks against relays.
8293 This release also fixes several minor bugs and annoyances from
8296 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
8297 today, for the fix to TROVE-2018-002. Directory authorities should
8298 also upgrade. (Relays on earlier versions might want to update too for
8299 the DoS mitigations.)
8301 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
8302 - Fix a protocol-list handling bug that could be used to remotely crash
8303 directory authorities with a null-pointer exception. Fixes bug 25074;
8304 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8307 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
8308 - Avoid adding the same channel twice in the KIST scheduler pending
8309 list, which could lead to remote denial-of-service use-after-free
8310 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
8312 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
8313 - Give relays some defenses against the recent network overload. We
8314 start with three defenses (default parameters in parentheses).
8315 First: if a single client address makes too many concurrent
8316 connections (>100), hang up on further connections. Second: if a
8317 single client address makes circuits too quickly (more than 3 per
8318 second, with an allowed burst of 90) while also having too many
8319 connections open (3), refuse new create cells for the next while
8320 (1-2 hours). Third: if a client asks to establish a rendezvous
8321 point to you directly, ignore the request. These defenses can be
8322 manually controlled by new torrc options, but relays will also
8323 take guidance from consensus parameters, so there's no need to
8324 configure anything manually. Implements ticket 24902.
8326 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
8327 - Fix an "off by 2" error in counting rendezvous failures on the
8328 onion service side. While we thought we would stop the rendezvous
8329 attempt after one failed circuit, we were actually making three
8330 circuit attempts before giving up. Now switch to a default of 2,
8331 and allow the consensus parameter "hs_service_max_rdv_failures" to
8332 override. Fixes bug 24895; bugfix on 0.0.6.
8333 - New-style (v3) onion services now obey the "max rendezvous circuit
8334 attempts" logic. Previously they would make as many rendezvous
8335 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
8336 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
8338 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
8339 - Add Link protocol version 5 to the supported protocols list. Fixes
8340 bug 25070; bugfix on 0.3.1.1-alpha.
8342 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
8343 - Fix a set of false positives where relays would consider
8344 connections to other relays as being client-only connections (and
8345 thus e.g. deserving different link padding schemes) if those
8346 relays fell out of the consensus briefly. Now we look only at the
8347 initial handshake and whether the connection authenticated as a
8348 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8350 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
8351 - The scheduler subsystem was failing to promptly notice changes in
8352 consensus parameters, making it harder to switch schedulers
8353 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
8355 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
8356 - Make our OOM handler aware of the geoip client history cache so it
8357 doesn't fill up the memory. This check is important for IPv6 and
8358 our DoS mitigation subsystem. Closes ticket 25122.
8360 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
8361 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8362 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8363 since they neither disabled TLS 1.3 nor enabled any of the
8364 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8365 Closes ticket 24978.
8367 o Minor features (geoip):
8368 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8371 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
8372 - When logging a failure to create an onion service's descriptor,
8373 also log what the problem with the descriptor was. Diagnostic
8376 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
8377 - Use the actual observed address of an incoming relay connection,
8378 not the canonical address of the relay from its descriptor, when
8379 making decisions about how to handle the incoming connection.
8380 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8382 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
8383 - Fix a possible crash on malformed consensus. If a consensus had
8384 contained an unparseable protocol line, it could have made clients
8385 and relays crash with a null-pointer exception. To exploit this
8386 issue, however, an attacker would need to be able to subvert the
8387 directory authority system. Fixes bug 25251; bugfix on
8388 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8390 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
8391 - Directory authorities, when refusing a descriptor from a rejected
8392 relay, now explicitly tell the relay (in its logs) to set a valid
8393 ContactInfo address and contact the bad-relays@ mailing list.
8394 Fixes bug 25170; bugfix on 0.2.9.1.
8396 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
8397 - When building with Rust on OSX, link against libresolv, to work
8398 around the issue at https://github.com/rust-lang/rust/issues/46797.
8399 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
8401 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
8402 - Remove a BUG() statement when a client fetches an onion descriptor
8403 that has a lower revision counter than the one in its cache. This
8404 can happen in normal circumstances due to HSDir desync. Fixes bug
8405 24976; bugfix on 0.3.2.1-alpha.
8407 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
8408 - Don't treat inability to store a cached consensus object as a bug:
8409 it can happen normally when we are out of disk space. Fixes bug
8410 24859; bugfix on 0.3.1.1-alpha.
8412 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
8413 - Improve the performance of our consensus-diff application code
8414 when Tor is built with the --enable-fragile-hardening option set.
8415 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
8417 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
8418 - Don't exit the Tor process if setrlimit() fails to change the file
8419 limit (which can happen sometimes on some versions of OSX). Fixes
8420 bug 21074; bugfix on 0.0.9pre5.
8422 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
8423 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8425 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8426 bugfix on 0.2.9.4-alpha.
8428 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
8429 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
8430 25005; bugfix on 0.3.2.7-rc.
8432 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
8433 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8434 version, when deciding whether a consensus entry can support the
8435 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8436 bugfix on 0.3.2.1-alpha.
8438 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
8439 - Update the "rust dependencies" submodule to be a project-level
8440 repository, rather than a user repository. Closes ticket 25323.
8442 o Documentation (backport from 0.3.3.1-alpha)
8443 - Document that operators who run more than one relay or bridge are
8444 expected to set MyFamily and ContactInfo correctly. Closes
8448 Changes in version 0.3.3.3-alpha - 2018-03-03
8449 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
8450 It includes an important security fix for a remote crash attack
8451 against directory authorities tracked as TROVE-2018-001.
8453 Additionally, with this release, we are upgrading the severity of a
8454 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
8455 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
8456 a use-after-free pattern. As such, we are now tracking that bug as
8457 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
8458 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
8460 This release also fixes several minor bugs and annoyances from
8463 Relays running 0.3.2.x should upgrade to one of the versions released
8464 today, for the fix to TROVE-2018-002. Directory authorities should
8465 also upgrade. (Relays on earlier versions might want to update too for
8466 the DoS mitigations.)
8468 o Major bugfixes (denial-of-service, directory authority):
8469 - Fix a protocol-list handling bug that could be used to remotely crash
8470 directory authorities with a null-pointer exception. Fixes bug 25074;
8471 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
8474 o Minor features (compatibility, OpenSSL):
8475 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
8476 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
8477 since they neither disabled TLS 1.3 nor enabled any of the
8478 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
8479 Closes ticket 24978.
8481 o Minor features (logging):
8482 - Clarify the log messages produced when getrandom() or a related
8483 entropy-generation mechanism gives an error. Closes ticket 25120.
8485 o Minor features (testing):
8486 - Add a "make test-rust" target to run the rust tests only. Closes
8489 o Minor bugfixes (denial-of-service):
8490 - Fix a possible crash on malformed consensus. If a consensus had
8491 contained an unparseable protocol line, it could have made clients
8492 and relays crash with a null-pointer exception. To exploit this
8493 issue, however, an attacker would need to be able to subvert the
8494 directory authority system. Fixes bug 25251; bugfix on
8495 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
8497 o Minor bugfixes (DoS mitigation):
8498 - Add extra safety checks when refilling the circuit creation bucket
8499 to ensure we never set a value above the allowed maximum burst.
8500 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
8501 - When a new consensus arrives, don't update our DoS-mitigation
8502 parameters if we aren't a public relay. Fixes bug 25223; bugfix
8505 o Minor bugfixes (man page, SocksPort):
8506 - Remove dead code from the old "SocksSocket" option, and rename
8507 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
8508 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
8510 o Minor bugfixes (performance):
8511 - Reduce the number of circuits that will be opened at once during
8512 the circuit build timeout phase. This is done by increasing the
8513 idle timeout to 3 minutes, and lowering the maximum number of
8514 concurrent learning circuits to 10. Fixes bug 24769; bugfix
8517 o Minor bugfixes (spec conformance):
8518 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
8520 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
8521 bugfix on 0.2.9.4-alpha.
8523 o Minor bugfixes (spec conformance, rust):
8524 - Resolve a denial-of-service issue caused by an infinite loop in
8525 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
8526 Also tracked as TROVE-2018-003.
8528 o Code simplification and refactoring:
8529 - Update the "rust dependencies" submodule to be a project-level
8530 repository, rather than a user repository. Closes ticket 25323.
8533 Changes in version 0.3.3.2-alpha - 2018-02-10
8534 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
8535 introduces a mechanism to handle the high loads that many relay
8536 operators have been reporting recently. It also fixes several bugs in
8537 older releases. If this new code proves reliable, we plan to backport
8538 it to older supported release series.
8540 o Major features (denial-of-service mitigation):
8541 - Give relays some defenses against the recent network overload. We
8542 start with three defenses (default parameters in parentheses).
8543 First: if a single client address makes too many concurrent
8544 connections (>100), hang up on further connections. Second: if a
8545 single client address makes circuits too quickly (more than 3 per
8546 second, with an allowed burst of 90) while also having too many
8547 connections open (3), refuse new create cells for the next while
8548 (1-2 hours). Third: if a client asks to establish a rendezvous
8549 point to you directly, ignore the request. These defenses can be
8550 manually controlled by new torrc options, but relays will also
8551 take guidance from consensus parameters, so there's no need to
8552 configure anything manually. Implements ticket 24902.
8554 o Major bugfixes (netflow padding):
8555 - Stop adding unneeded channel padding right after we finish
8556 flushing to a connection that has been trying to flush for many
8557 seconds. Instead, treat all partial or complete flushes as
8558 activity on the channel, which will defer the time until we need
8559 to add padding. This fix should resolve confusing and scary log
8560 messages like "Channel padding timeout scheduled 221453ms in the
8561 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8563 o Major bugfixes (protocol versions):
8564 - Add Link protocol version 5 to the supported protocols list. Fixes
8565 bug 25070; bugfix on 0.3.1.1-alpha.
8567 o Major bugfixes (scheduler, consensus):
8568 - The scheduler subsystem was failing to promptly notice changes in
8569 consensus parameters, making it harder to switch schedulers
8570 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
8572 o Minor features (denial-of-service avoidance):
8573 - Make our OOM handler aware of the geoip client history cache so it
8574 doesn't fill up the memory. This check is important for IPv6 and
8575 our DoS mitigation subsystem. Closes ticket 25122.
8577 o Minor features (directory authority):
8578 - When directory authorities are unable to add signatures to a
8579 pending consensus, log the reason why. Closes ticket 24849.
8581 o Minor features (geoip):
8582 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
8585 o Minor features (logging, diagnostic):
8586 - When logging a failure to create an onion service's descriptor,
8587 also log what the problem with the descriptor was. Diagnostic for
8590 o Minor bugfix (channel connection):
8591 - Use the actual observed address of an incoming relay connection,
8592 not the canonical address of the relay from its descriptor, when
8593 making decisions about how to handle the incoming connection.
8594 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
8596 o Minor bugfix (directory authority):
8597 - Directory authorities, when refusing a descriptor from a rejected
8598 relay, now explicitly tell the relay (in its logs) to set a valid
8599 ContactInfo address and contact the bad-relays@ mailing list.
8600 Fixes bug 25170; bugfix on 0.2.9.1.
8602 o Minor bugfixes (all versions of Tor):
8603 - Use the "misspell" tool to detect and fix typos throughout the
8604 source code. Fixes bug 23650; bugfix on various versions of Tor.
8605 Patch from Deepesh Pathak.
8607 o Minor bugfixes (circuit, cannibalization):
8608 - Don't cannibalize preemptively-built circuits if we no longer
8609 recognize their first hop. This situation can happen if our Guard
8610 relay went off the consensus after the circuit was created. Fixes
8611 bug 24469; bugfix on 0.0.6.
8613 o Minor bugfixes (correctness):
8614 - Remove a nonworking, unnecessary check to see whether a circuit
8615 hop's identity digest was set when the circuit failed. Fixes bug
8616 24927; bugfix on 0.2.4.4-alpha.
8618 o Minor bugfixes (logging):
8619 - Don't treat inability to store a cached consensus object as a bug:
8620 it can happen normally when we are out of disk space. Fixes bug
8621 24859; bugfix on 0.3.1.1-alpha.
8622 - Fix a (mostly harmless) race condition when invoking
8623 LOG_PROTOCOL_WARN message from a subthread while the torrc options
8624 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
8626 o Minor bugfixes (onion services):
8627 - Remove a BUG() statement when a client fetches an onion descriptor
8628 that has a lower revision counter than the one in its cache. This
8629 can happen in normal circumstances due to HSDir desync. Fixes bug
8630 24976; bugfix on 0.3.2.1-alpha.
8631 - If we are configured to offer a single onion service, don't log
8632 long-term established one hop rendezvous points in the heartbeat.
8633 Fixes bug 25116; bugfix on 0.2.9.6-rc.
8635 o Minor bugfixes (performance):
8636 - Avoid calling protocol_list_supports_protocol() from inside tight
8637 loops when running with cached routerinfo_t objects. Instead,
8638 summarize the relevant protocols as flags in the routerinfo_t, as
8639 we do for routerstatus_t objects. This change simplifies our code
8640 a little, and saves a large amount of short-term memory allocation
8641 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
8643 o Minor bugfixes (Rust FFI):
8644 - Fix a minor memory leak which would happen whenever the C code
8645 would call the Rust implementation of
8646 protover_get_supported_protocols(). This was due to the C version
8647 returning a static string, whereas the Rust version newly allocated
8648 a CString to pass across the FFI boundary. Consequently, the C
8649 code was not expecting to need to free() what it was given. Fixes
8650 bug 25127; bugfix on 0.3.2.1-alpha.
8652 o Minor bugfixes (scheduler, KIST):
8653 - Avoid adding the same channel twice in the KIST scheduler pending
8654 list, which would waste CPU cycles. Fixes bug 24700; bugfix
8657 o Minor bugfixes (unit test, monotonic time):
8658 - Increase a constant (1msec to 10msec) in the monotonic time test
8659 that makes sure the nsec/usec/msec times read are synchronized.
8660 This change was needed to accommodate slow systems like armel or
8661 when the clock_gettime() is not a VDSO on the running kernel.
8662 Fixes bug 25113; bugfix on 0.2.9.1.
8664 o Minor bugfixes (v3 onion services):
8665 - Look at the "HSRend" protocol version, not the "HSDir" protocol
8666 version, when deciding whether a consensus entry can support the
8667 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
8668 bugfix on 0.3.2.1-alpha.
8670 o Code simplification and refactoring:
8671 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
8673 - Remove a series of counters used to track circuit extend attempts
8674 and connection status but that in reality we aren't using for
8675 anything other than stats logged by a SIGUSR1 signal. Closes
8678 o Documentation (man page):
8679 - The HiddenServiceVersion torrc option accepts only one number:
8680 either version 2 or 3. Closes ticket 25026; bugfix
8684 Changes in version 0.3.3.1-alpha - 2018-01-25
8685 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
8686 several new features to Tor, including several improvements to
8687 bootstrapping, and support for an experimental "vanguards" feature to
8688 resist guard discovery attacks. This series also includes better
8689 support for applications that need to embed Tor or manage v3
8692 o Major features (embedding):
8693 - There is now a documented stable API for programs that need to
8694 embed Tor. See tor_api.h for full documentation and known bugs.
8695 Closes ticket 23684.
8696 - Tor now has support for restarting in the same process.
8697 Controllers that run Tor using the "tor_api.h" interface can now
8698 restart Tor after Tor has exited. This support is incomplete,
8699 however: we fixed crash bugs that prevented it from working at
8700 all, but many bugs probably remain, including a possibility of
8701 security issues. Implements ticket 24581.
8703 o Major features (IPv6, directory documents):
8704 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
8705 consensus. This information makes it easier for IPv6 clients to
8706 bootstrap and choose reachable entry guards. Implements ticket 23826.
8707 - Add consensus method 28, which removes IPv6 ORPorts from
8708 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
8709 are redundant in microdescs. This change will be used by Tor clients
8710 on 0.2.8.x and later. (That is to say, with all Tor clients that
8711 have IPv6 bootstrap and guard support.) Implements ticket 23828.
8712 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
8713 set by different numbers of authorities. Fixes 23870
8716 o Major features (onion service v3, control port):
8717 - The control port now supports commands and events for v3 onion
8718 services. It is now possible to create ephemeral v3 services using
8719 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
8720 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
8721 DEL_ONION) have been extended to support v3 onion services. Closes
8722 ticket 20699; implements proposal 284.
8724 o Major features (onion services):
8725 - Provide torrc options to pin the second and third hops of onion
8726 service circuits to a list of nodes. The option HSLayer2Guards
8727 pins the second hop, and the option HSLayer3Guards pins the third
8728 hop. These options are for use in conjunction with experiments
8729 with "vanguards" for preventing guard enumeration attacks. Closes
8732 o Major features (rust, portability, experimental):
8733 - Tor now ships with an optional implementation of one of its
8734 smaller modules (protover.c) in the Rust programming language. To
8735 try it out, install a Rust build environment, and configure Tor
8736 with "--enable-rust --enable-cargo-online-mode". This should not
8737 cause any user-visible changes, but should help us gain more
8738 experience with Rust, and plan future Rust integration work.
8739 Implementation by Chelsea Komlo. Closes ticket 22840.
8741 o Minor features (storage, configuration):
8742 - Users can store cached directory documents somewhere other than
8743 the DataDirectory by using the CacheDirectory option. Similarly,
8744 the storage location for relay's keys can be overridden with the
8745 KeyDirectory option. Closes ticket 22703.
8747 o Major features (v3 onion services, ipv6):
8748 - When v3 onion service clients send introduce cells, they now
8749 include the IPv6 address of the rendezvous point, if it has one.
8750 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
8751 in future Tor versions, IPv6-only v3 single onion services will be
8752 able to use IPv6 addresses to connect directly to the rendezvous
8753 point. Closes ticket 23577. Patch by Neel Chauhan.
8755 o Major bugfixes (onion services, retry behavior):
8756 - Fix an "off by 2" error in counting rendezvous failures on the
8757 onion service side. While we thought we would stop the rendezvous
8758 attempt after one failed circuit, we were actually making three
8759 circuit attempts before giving up. Now switch to a default of 2,
8760 and allow the consensus parameter "hs_service_max_rdv_failures" to
8761 override. Fixes bug 24895; bugfix on 0.0.6.
8762 - New-style (v3) onion services now obey the "max rendezvous circuit
8763 attempts" logic. Previously they would make as many rendezvous
8764 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
8765 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
8767 o Major bugfixes (relays):
8768 - Fix a set of false positives where relays would consider
8769 connections to other relays as being client-only connections (and
8770 thus e.g. deserving different link padding schemes) if those
8771 relays fell out of the consensus briefly. Now we look only at the
8772 initial handshake and whether the connection authenticated as a
8773 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
8775 o Minor feature (IPv6):
8776 - Make IPv6-only clients wait for microdescs for relays, even if we
8777 were previously using descriptors (or were using them as a bridge)
8778 and have a cached descriptor for them. Implements ticket 23827.
8779 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
8780 them, rather than waiting to download microdescriptors.
8781 Implements ticket 23827.
8783 o Minor features (cleanup):
8784 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
8785 when it stops. Closes ticket 23271.
8787 o Minor features (defensive programming):
8788 - Most of the functions in Tor that free objects have been replaced
8789 with macros that free the objects and set the corresponding
8790 pointers to NULL. This change should help prevent a large class of
8791 dangling pointer bugs. Closes ticket 24337.
8792 - Where possible, the tor_free() macro now only evaluates its input
8793 once. Part of ticket 24337.
8794 - Check that microdesc ed25519 ids are non-zero in
8795 node_get_ed25519_id() before returning them. Implements ticket
8796 24001, patch by "aruna1234".
8798 o Minor features (embedding):
8799 - Tor can now start with a preauthenticated control connection
8800 created by the process that launched it. This feature is meant for
8801 use by programs that want to launch and manage a Tor process
8802 without allowing other programs to manage it as well. For more
8803 information, see the __OwningControllerFD option documented in
8804 control-spec.txt. Closes ticket 23900.
8805 - On most errors that would cause Tor to exit, it now tries to
8806 return from the tor_main() function, rather than calling the
8807 system exit() function. Most users won't notice a difference here,
8808 but it should be significant for programs that run Tor inside
8809 a separate thread: they should now be able to survive Tor's exit
8810 conditions rather than having Tor shut down the entire process.
8811 Closes ticket 23848.
8812 - Applications that want to embed Tor can now tell Tor not to
8813 register any of its own POSIX signal handlers, using the
8814 __DisableSignalHandlers option. Closes ticket 24588.
8816 o Minor features (fallback directory list):
8817 - Avoid selecting fallbacks that change their IP addresses too
8818 often. Select more fallbacks by ignoring the Guard flag, and
8819 allowing lower cutoffs for the Running and V2Dir flags. Also allow
8820 a lower bandwidth, and a higher number of fallbacks per operator
8821 (5% of the list). Implements ticket 24785.
8822 - Update the fallback whitelist and blacklist based on opt-ins and
8823 relay changes. Closes tickets 22321, 24678, 22527, 24135,
8826 o Minor features (fallback directory mirror configuration):
8827 - Add a nickname to each fallback in a C comment. This makes it
8828 easier for operators to find their relays, and allows stem to use
8829 nicknames to identify fallbacks. Implements ticket 24600.
8830 - Add a type and version header to the fallback directory mirror
8831 file. Also add a delimiter to the end of each fallback entry. This
8832 helps external parsers like stem and Relay Search. Implements
8834 - Add an extrainfo cache flag for each fallback in a C comment. This
8835 allows stem to use fallbacks to fetch extra-info documents, rather
8836 than using authorities. Implements ticket 22759.
8837 - Add the generateFallbackDirLine.py script for automatically
8838 generating fallback directory mirror lines from relay fingerprints.
8839 No more typos! Add the lookupFallbackDirContact.py script for
8840 automatically looking up operator contact info from relay
8841 fingerprints. Implements ticket 24706, patch by teor and atagar.
8842 - Reject any fallback directory mirror that serves an expired
8843 consensus. Implements ticket 20942, patch by "minik".
8844 - Remove commas and equals signs from external string inputs to the
8845 fallback list. This avoids format confusion attacks. Implements
8847 - Remove the "weight=10" line from fallback directory mirror
8848 entries. Ticket 24681 will maintain the current fallback weights
8849 by changing Tor's default fallback weight to 10. Implements
8851 - Stop logging excessive information about fallback netblocks.
8852 Implements ticket 24791.
8854 o Minor features (forward-compatibility):
8855 - If a relay supports some link authentication protocol that we do
8856 not recognize, then include that relay's ed25519 key when telling
8857 other relays to extend to it. Previously, we treated future
8858 versions as if they were too old to support ed25519 link
8859 authentication. Closes ticket 20895.
8861 o Minor features (heartbeat):
8862 - Add onion service information to our heartbeat logs, displaying
8863 stats about the activity of configured onion services. Closes
8866 o Minor features (instrumentation, development):
8867 - Add the MainloopStats option to allow developers to get
8868 instrumentation information from the main event loop via the
8869 heartbeat messages. We hope to use this to improve Tor's behavior
8870 when it's trying to sleep. Closes ticket 24605.
8872 o Minor features (log messages):
8873 - Improve a warning message that happens when we fail to re-parse an
8874 old router because of an expired certificate. Closes ticket 20020.
8875 - Make the log more quantitative when we hit MaxMemInQueues
8876 threshold exposing some values. Closes ticket 24501.
8878 o Minor features (logging, android):
8879 - Added support for the Android logging subsystem. Closes
8882 o Minor features (performance):
8883 - Support predictive circuit building for onion service circuits
8884 with multiple layers of guards. Closes ticket 23101.
8885 - Use stdatomic.h where available, rather than mutexes, to implement
8886 atomic_counter_t. Closes ticket 23953.
8888 o Minor features (performance, 32-bit):
8889 - Improve performance on 32-bit systems by avoiding 64-bit division
8890 when calculating the timestamp in milliseconds for channel padding
8891 computations. Implements ticket 24613.
8892 - Improve performance on 32-bit systems by avoiding 64-bit division
8893 when timestamping cells and buffer chunks for OOM calculations.
8894 Implements ticket 24374.
8896 o Minor features (performance, OSX, iOS):
8897 - Use the mach_approximate_time() function (when available) to
8898 implement coarse monotonic time. Having a coarse time function
8899 should avoid a large number of system calls, and improve
8900 performance slightly, especially under load. Closes ticket 24427.
8902 o Minor features (performance, windows):
8903 - Improve performance on Windows Vista and Windows 7 by adjusting
8904 TCP send window size according to the recommendation from
8905 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
8908 o Major features (relay):
8909 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
8910 operator to use a more reasonable ("reduced") exit policy, rather
8911 than the default one. If you want to run an exit node without
8912 thinking too hard about which ports to allow, this one is for you.
8913 Closes ticket 13605. Patch from Neel Chauhan.
8915 o Minor features (testing, debugging, embedding):
8916 - For development purposes, Tor now has a mode in which it runs for
8917 a few seconds, then stops, and starts again without exiting the
8918 process. This mode is meant to help us debug various issues with
8919 ticket 23847. To use this feature, compile with
8920 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
8921 environment variable. This is expected to crash a lot, and is
8922 really meant for developers only. It will likely be removed in a
8923 future release. Implements ticket 24583.
8925 o Minor bugfix (network IPv6 test):
8926 - Tor's test scripts now check if "ping -6 ::1" works when the user
8927 runs "make test-network-all". Fixes bug 24677; bugfix on
8928 0.2.9.3-alpha. Patch by "ffmancera".
8930 o Minor bugfixes (build, rust):
8931 - Fix output of autoconf checks to display success messages for Rust
8932 dependencies and a suitable rustc compiler version. Fixes bug
8933 24612; bugfix on 0.3.1.3-alpha.
8934 - When building with Rust on OSX, link against libresolv, to work
8935 around the issue at https://github.com/rust-lang/rust/issues/46797.
8936 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
8937 - Don't pass the --quiet option to cargo: it seems to suppress some
8938 errors, which is not what we want to do when building. Fixes bug
8939 24518; bugfix on 0.3.1.7.
8940 - Build correctly when building from outside Tor's source tree with
8941 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
8944 o Minor bugfixes (directory authorities, IPv6):
8945 - When creating a routerstatus (vote) from a routerinfo (descriptor),
8946 set the IPv6 address to the unspecified IPv6 address, and
8947 explicitly initialize the port to zero. Fixes bug 24488; bugfix
8950 o Minor bugfixes (fallback directory mirrors):
8951 - Make updateFallbackDirs.py search harder for python. (Some OSs
8952 don't put it in /usr/bin.) Fixes bug 24708; bugfix
8955 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
8956 - When hibernating, close connections normally and allow them to
8957 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
8959 - Do not attempt to launch self-reachability tests when entering
8960 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8961 - Resolve several bugs related to descriptor fetching on bridge
8962 clients with bandwidth accounting enabled. (This combination is
8963 not recommended!) Fixes a case of bug 12062; bugfix
8965 - When hibernating, do not attempt to launch DNS checks. Fixes a
8966 case of bug 12062; bugfix on 0.1.2.2-alpha.
8967 - When hibernating, do not try to upload or download descriptors.
8968 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
8970 o Minor bugfixes (IPv6, bridges):
8971 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
8972 bugfix on 0.2.8.2-alpha.
8973 - Tor now sets IPv6 address in the routerstatus as well as in the
8974 router descriptors when updating addresses for a bridge. Closes
8975 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
8977 o Minor bugfixes (linux seccomp2 sandbox):
8978 - When running with the sandbox enabled, reload configuration files
8979 correctly even when %include was used. Previously we would crash.
8980 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
8982 o Minor bugfixes (memory leaks):
8983 - Avoid possible at-exit memory leaks related to use of Libevent's
8984 event_base_once() function. (This function tends to leak memory if
8985 the event_base is closed before the event fires.) Fixes bug 24584;
8986 bugfix on 0.2.8.1-alpha.
8987 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
8990 o Minor bugfixes (OSX):
8991 - Don't exit the Tor process if setrlimit() fails to change the file
8992 limit (which can happen sometimes on some versions of OSX). Fixes
8993 bug 21074; bugfix on 0.0.9pre5.
8995 o Minor bugfixes (performance, fragile-hardening):
8996 - Improve the performance of our consensus-diff application code
8997 when Tor is built with the --enable-fragile-hardening option set.
8998 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
9000 o Minor bugfixes (performance, timeouts):
9001 - Consider circuits for timeout as soon as they complete a hop. This
9002 is more accurate than applying the timeout in
9003 circuit_expire_building() because that function is only called
9004 once per second, which is now too slow for typical timeouts on the
9005 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
9006 - Use onion service circuits (and other circuits longer than 3 hops)
9007 to calculate a circuit build timeout. Previously, Tor only
9008 calculated its build timeout based on circuits that planned to be
9009 exactly 3 hops long. With this change, we include measurements
9010 from all circuits at the point where they complete their third
9011 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
9013 o Minor bugfixes (testing):
9014 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
9015 bugfix on 0.2.3.1-alpha.
9016 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
9017 25005; bugfix on 0.3.2.7-rc.
9019 o Code simplification and refactoring:
9020 - Remove /usr/athena from search path in configure.ac. Closes
9022 - Remove duplicate code in node_has_curve25519_onion_key() and
9023 node_get_curve25519_onion_key(), and add a check for a zero
9024 microdesc curve25519 onion key. Closes ticket 23966, patch by
9025 "aruna1234" and teor.
9026 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
9027 memory allocations with large numbers of OR connections (e.g.
9028 relays). Closes ticket 24119.
9029 - Separate the function that deletes ephemeral files when Tor
9031 - Small changes to Tor's buf_t API to make it suitable for use as a
9032 general-purpose safe string constructor. Closes ticket 22342.
9033 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
9034 avoid source code identifier confusion. Closes ticket 24467.
9035 - The tor_git_revision[] constant no longer needs to be redeclared
9036 by everything that links against the rest of Tor. Done as part of
9037 ticket 23845, to simplify our external API.
9038 - We make extend_info_from_node() use node_get_curve25519_onion_key()
9039 introduced in ticket 23577 to access the curve25519 public keys
9040 rather than accessing it directly. Closes ticket 23760. Patch by
9042 - Add a function to log channels' scheduler state changes to aid
9043 debugging efforts. Closes ticket 24531.
9046 - Add documentation on how to build tor with Rust dependencies
9047 without having to be online. Closes ticket 22907; bugfix
9049 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
9050 traffic. Closes ticket 24318.
9051 - Document that OutboundBindAddress doesn't apply to DNS requests.
9052 Closes ticket 22145. Patch from Aruna Maurya.
9053 - Document that operators who run more than one relay or bridge are
9054 expected to set MyFamily and ContactInfo correctly. Closes
9057 o Code simplification and refactoring (channels):
9058 - Remove the incoming and outgoing channel queues. These were never
9059 used, but still took up a step in our fast path.
9060 - The majority of the channel unit tests have been rewritten and the
9061 code coverage has now been raised to 83.6% for channel.c. Closes
9063 - Remove other dead code from the channel subsystem: All together,
9064 this cleanup has removed more than 1500 lines of code overall and
9065 adding very little except for unit test.
9067 o Code simplification and refactoring (circuit rendezvous):
9068 - Split the client-side rendezvous circuit lookup into two
9069 functions: one that returns only established circuits and another
9070 that returns all kinds of circuits. Closes ticket 23459.
9072 o Code simplification and refactoring (controller):
9073 - Make most of the variables in networkstatus_getinfo_by_purpose()
9074 const. Implements ticket 24489.
9077 Changes in version 0.3.2.9 - 2018-01-09
9078 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
9080 The 0.3.2 series includes our long-anticipated new onion service
9081 design, with numerous security features. (For more information, see
9082 our blog post at https://blog.torproject.org/fall-harvest.) We also
9083 have a new circuit scheduler algorithm for improved performance on
9084 relays everywhere (see https://blog.torproject.org/kist-and-tell),
9085 along with many smaller features and bugfixes.
9087 Per our stable release policy, we plan to support each stable release
9088 series for at least the next nine months, or for three months after
9089 the first stable release of the next series: whichever is longer. If
9090 you need a release with long-term support, we recommend that you stay
9091 with the 0.2.9 series.
9093 Below is a list of the changes since 0.3.2.8-rc. For a list of all
9094 changes since 0.3.1, see the ReleaseNotes file.
9096 o Minor features (fallback directory mirrors):
9097 - The fallback directory list has been re-generated based on the
9098 current status of the network. Tor uses fallback directories to
9099 bootstrap when it doesn't yet have up-to-date directory
9100 information. Closes ticket 24801.
9101 - Make the default DirAuthorityFallbackRate 0.1, so that clients
9102 prefer to bootstrap from fallback directory mirrors. This is a
9103 follow-up to 24679, which removed weights from the default
9104 fallbacks. Implements ticket 24681.
9106 o Minor features (geoip):
9107 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
9110 o Minor bugfixes (address selection):
9111 - When the fascist_firewall_choose_address_ functions don't find a
9112 reachable address, set the returned address to the null address
9113 and port. This is a precautionary measure, because some callers do
9114 not check the return value. Fixes bug 24736; bugfix
9117 o Minor bugfixes (compilation):
9118 - Resolve a few shadowed-variable warnings in the onion service
9119 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
9121 o Minor bugfixes (portability, msvc):
9122 - Fix a bug in the bit-counting parts of our timing-wheel code on
9123 MSVC. (Note that MSVC is still not a supported build platform, due
9124 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
9128 Changes in version 0.3.2.8-rc - 2017-12-21
9129 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
9130 schedulers that had led servers under heavy load to overload their
9131 outgoing connections. All relay operators running earlier 0.3.2.x
9132 versions should upgrade. This version also includes a mitigation for
9133 over-full DESTROY queues leading to out-of-memory conditions: if it
9134 works, we will soon backport it to earlier release series.
9136 This is the second release candidate in the 0.3.2 series. If we find
9137 no new bugs or regression here, then the first stable 0.3.2 release
9138 will be nearly identical to this.
9140 o Major bugfixes (KIST, scheduler):
9141 - The KIST scheduler did not correctly account for data already
9142 enqueued in each connection's send socket buffer, particularly in
9143 cases when the TCP/IP congestion window was reduced between
9144 scheduler calls. This situation lead to excessive per-connection
9145 buffering in the kernel, and a potential memory DoS. Fixes bug
9146 24665; bugfix on 0.3.2.1-alpha.
9148 o Minor features (geoip):
9149 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
9152 o Minor bugfixes (hidden service v3):
9153 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
9154 the probability of reaching a service for a client missing
9155 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
9157 o Minor bugfixes (memory usage):
9158 - When queuing DESTROY cells on a channel, only queue the circuit-id
9159 and reason fields: not the entire 514-byte cell. This fix should
9160 help mitigate any bugs or attacks that fill up these queues, and
9161 free more RAM for other uses. Fixes bug 24666; bugfix
9164 o Minor bugfixes (scheduler, KIST):
9165 - Use a sane write limit for KISTLite when writing onto a connection
9166 buffer instead of using INT_MAX and shoving as much as it can.
9167 Because the OOM handler cleans up circuit queues, we are better
9168 off at keeping them in that queue instead of the connection's
9169 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
9172 Changes in version 0.3.2.7-rc - 2017-12-14
9173 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
9174 including some that could affect reliability or correctness.
9176 This is the first release candidate in the 0.3.2 series. If we find no
9177 new bugs or regression here, then the first stable 0.3.2. release will
9178 be nearly identical to this.
9180 o Major bugfixes (circuit prediction):
9181 - Fix circuit prediction logic so that a client doesn't treat a port
9182 as being "handled" by a circuit if that circuit already has
9183 isolation settings on it. This change should make Tor clients more
9184 responsive by improving their chances of having a pre-created
9185 circuit ready for use when a request arrives. Fixes bug 18859;
9186 bugfix on 0.2.3.3-alpha.
9188 o Minor features (logging):
9189 - Provide better warnings when the getrandom() syscall fails. Closes
9192 o Minor features (portability):
9193 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
9194 (It doesn't yet work with the sandbox enabled.) Closes
9197 o Minor bugfixes (bridge clients, bootstrap):
9198 - Retry directory downloads when we get our first bridge descriptor
9199 during bootstrap or while reconnecting to the network. Keep
9200 retrying every time we get a bridge descriptor, until we have a
9201 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
9202 - Stop delaying bridge descriptor fetches when we have cached bridge
9203 descriptors. Instead, only delay bridge descriptor fetches when we
9204 have at least one reachable bridge. Fixes part of bug 24367;
9205 bugfix on 0.2.0.3-alpha.
9206 - Stop delaying directory fetches when we have cached bridge
9207 descriptors. Instead, only delay bridge descriptor fetches when
9208 all our bridges are definitely unreachable. Fixes part of bug
9209 24367; bugfix on 0.2.0.3-alpha.
9211 o Minor bugfixes (compilation):
9212 - Fix a signed/unsigned comparison warning introduced by our fix to
9213 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
9215 o Minor bugfixes (correctness):
9216 - Fix several places in our codebase where a C compiler would be
9217 likely to eliminate a check, based on assuming that undefined
9218 behavior had not happened elsewhere in the code. These cases are
9219 usually a sign of redundant checking or dubious arithmetic. Found
9220 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
9221 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
9224 o Minor bugfixes (onion service v3):
9225 - Fix a race where an onion service would launch a new intro circuit
9226 after closing an old one, but fail to register it before freeing
9227 the previously closed circuit. This bug was making the service
9228 unable to find the established intro circuit and thus not upload
9229 its descriptor, thus making a service unavailable for up to 24
9230 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
9232 o Minor bugfixes (scheduler, KIST):
9233 - Properly set the scheduler state of an unopened channel in the
9234 KIST scheduler main loop. This prevents a harmless but annoying
9235 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
9236 - Avoid a possible integer overflow when computing the available
9237 space on the TCP buffer of a channel. This had no security
9238 implications; but could make KIST allow too many cells on a
9239 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
9240 - Downgrade to "info" a harmless warning about the monotonic time
9241 moving backwards: This can happen on platform not supporting
9242 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
9245 Changes in version 0.3.2.6-alpha - 2017-12-01
9246 This version of Tor is the latest in the 0.3.2 alpha series. It
9247 includes fixes for several important security issues. All Tor users
9248 should upgrade to this release, or to one of the other releases coming
9251 o Major bugfixes (security):
9252 - Fix a denial of service bug where an attacker could use a
9253 malformed directory object to cause a Tor instance to pause while
9254 OpenSSL would try to read a passphrase from the terminal. (Tor
9255 instances run without a terminal, which is the case for most Tor
9256 packages, are not impacted.) Fixes bug 24246; bugfix on every
9257 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9258 Found by OSS-Fuzz as testcase 6360145429790720.
9259 - Fix a denial of service issue where an attacker could crash a
9260 directory authority using a malformed router descriptor. Fixes bug
9261 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9263 - When checking for replays in the INTRODUCE1 cell data for a
9264 (legacy) onion service, correctly detect replays in the RSA-
9265 encrypted part of the cell. We were previously checking for
9266 replays on the entire cell, but those can be circumvented due to
9267 the malleability of Tor's legacy hybrid encryption. This fix helps
9268 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9269 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9272 o Major bugfixes (security, onion service v2):
9273 - Fix a use-after-free error that could crash v2 Tor onion services
9274 when they failed to open circuits while expiring introduction
9275 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9276 also tracked as TROVE-2017-013 and CVE-2017-8823.
9278 o Major bugfixes (security, relay):
9279 - When running as a relay, make sure that we never build a path
9280 through ourselves, even in the case where we have somehow lost the
9281 version of our descriptor appearing in the consensus. Fixes part
9282 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9283 as TROVE-2017-012 and CVE-2017-8822.
9284 - When running as a relay, make sure that we never choose ourselves
9285 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9286 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9288 o Minor feature (relay statistics):
9289 - Change relay bandwidth reporting stats interval from 4 hours to 24
9290 hours in order to reduce the efficiency of guard discovery
9291 attacks. Fixes ticket 23856.
9293 o Minor features (directory authority):
9294 - Add an IPv6 address for the "bastet" directory authority. Closes
9297 o Minor bugfixes (client):
9298 - By default, do not enable storage of client-side DNS values. These
9299 values were unused by default previously, but they should not have
9300 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
9303 Changes in version 0.3.1.9 - 2017-12-01:
9304 Tor 0.3.1.9 backports important security and stability fixes from the
9305 0.3.2 development series. All Tor users should upgrade to this
9306 release, or to another of the releases coming out today.
9308 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9309 - Fix a denial of service bug where an attacker could use a
9310 malformed directory object to cause a Tor instance to pause while
9311 OpenSSL would try to read a passphrase from the terminal. (Tor
9312 instances run without a terminal, which is the case for most Tor
9313 packages, are not impacted.) Fixes bug 24246; bugfix on every
9314 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9315 Found by OSS-Fuzz as testcase 6360145429790720.
9316 - Fix a denial of service issue where an attacker could crash a
9317 directory authority using a malformed router descriptor. Fixes bug
9318 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9320 - When checking for replays in the INTRODUCE1 cell data for a
9321 (legacy) onion service, correctly detect replays in the RSA-
9322 encrypted part of the cell. We were previously checking for
9323 replays on the entire cell, but those can be circumvented due to
9324 the malleability of Tor's legacy hybrid encryption. This fix helps
9325 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9326 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9329 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9330 - Fix a use-after-free error that could crash v2 Tor onion services
9331 when they failed to open circuits while expiring introduction
9332 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9333 also tracked as TROVE-2017-013 and CVE-2017-8823.
9335 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9336 - When running as a relay, make sure that we never build a path
9337 through ourselves, even in the case where we have somehow lost the
9338 version of our descriptor appearing in the consensus. Fixes part
9339 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9340 as TROVE-2017-012 and CVE-2017-8822.
9341 - When running as a relay, make sure that we never choose ourselves
9342 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9343 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9345 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9346 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9347 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9348 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9349 identifying and finding a workaround to this bug and to Moritz,
9350 Arthur Edelstein, and Roger for helping to track it down and
9353 o Minor features (bridge):
9354 - Bridges now include notice in their descriptors that they are
9355 bridges, and notice of their distribution status, based on their
9356 publication settings. Implements ticket 18329. For more fine-
9357 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9360 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9361 - Add an IPv6 address for the "bastet" directory authority. Closes
9364 o Minor features (geoip):
9365 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9368 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9369 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9370 relays, to prevent spurious address resolutions and descriptor
9371 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9372 bugfix on in 0.2.8.1-alpha.
9374 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9375 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9376 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9378 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9379 - When a circuit is marked for close, do not attempt to package any
9380 cells for channels on that circuit. Previously, we would detect
9381 this condition lower in the call stack, when we noticed that the
9382 circuit had no attached channel, and log an annoying message.
9383 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9385 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
9386 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9387 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9390 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9391 - Avoid a crash when transitioning from client mode to bridge mode.
9392 Previously, we would launch the worker threads whenever our
9393 "public server" mode changed, but not when our "server" mode
9394 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9397 Changes in version 0.3.0.13 - 2017-12-01
9398 Tor 0.3.0.13 backports important security and stability bugfixes from
9399 later Tor releases. All Tor users should upgrade to this release, or
9400 to another of the releases coming out today.
9402 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
9403 2018. If you need a release with long-term support, please stick with
9404 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9406 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9407 - Fix a denial of service bug where an attacker could use a
9408 malformed directory object to cause a Tor instance to pause while
9409 OpenSSL would try to read a passphrase from the terminal. (Tor
9410 instances run without a terminal, which is the case for most Tor
9411 packages, are not impacted.) Fixes bug 24246; bugfix on every
9412 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9413 Found by OSS-Fuzz as testcase 6360145429790720.
9414 - Fix a denial of service issue where an attacker could crash a
9415 directory authority using a malformed router descriptor. Fixes bug
9416 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9418 - When checking for replays in the INTRODUCE1 cell data for a
9419 (legacy) onion service, correctly detect replays in the RSA-
9420 encrypted part of the cell. We were previously checking for
9421 replays on the entire cell, but those can be circumvented due to
9422 the malleability of Tor's legacy hybrid encryption. This fix helps
9423 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9424 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9427 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9428 - Fix a use-after-free error that could crash v2 Tor onion services
9429 when they failed to open circuits while expiring introduction
9430 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9431 also tracked as TROVE-2017-013 and CVE-2017-8823.
9433 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9434 - When running as a relay, make sure that we never build a path
9435 through ourselves, even in the case where we have somehow lost the
9436 version of our descriptor appearing in the consensus. Fixes part
9437 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9438 as TROVE-2017-012 and CVE-2017-8822.
9439 - When running as a relay, make sure that we never choose ourselves
9440 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
9441 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
9443 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9444 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9445 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9446 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9447 identifying and finding a workaround to this bug and to Moritz,
9448 Arthur Edelstein, and Roger for helping to track it down and
9451 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9452 - Enable a couple of pieces of Windows hardening: one
9453 (HeapEnableTerminationOnCorruption) that has been on-by-default
9454 since Windows 8, and unavailable before Windows 7; and one
9455 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9456 affect us, but shouldn't do any harm. Closes ticket 21953.
9458 o Minor features (bridge, backport from 0.3.1.9):
9459 - Bridges now include notice in their descriptors that they are
9460 bridges, and notice of their distribution status, based on their
9461 publication settings. Implements ticket 18329. For more fine-
9462 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9465 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9466 - Add an IPv6 address for the "bastet" directory authority. Closes
9469 o Minor features (geoip):
9470 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9473 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9474 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9475 relays, to prevent spurious address resolutions and descriptor
9476 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9477 bugfix on in 0.2.8.1-alpha.
9479 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9480 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9481 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9483 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9484 - When a circuit is marked for close, do not attempt to package any
9485 cells for channels on that circuit. Previously, we would detect
9486 this condition lower in the call stack, when we noticed that the
9487 circuit had no attached channel, and log an annoying message.
9488 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9490 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9491 - Avoid a crash when transitioning from client mode to bridge mode.
9492 Previously, we would launch the worker threads whenever our
9493 "public server" mode changed, but not when our "server" mode
9494 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9496 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9497 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9498 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9501 Changes in version 0.2.9.14 - 2017-12-01
9502 Tor 0.3.0.13 backports important security and stability bugfixes from
9503 later Tor releases. All Tor users should upgrade to this release, or
9504 to another of the releases coming out today.
9506 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
9507 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9508 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9509 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9510 identifying and finding a workaround to this bug and to Moritz,
9511 Arthur Edelstein, and Roger for helping to track it down and
9514 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9515 - Fix a denial of service bug where an attacker could use a
9516 malformed directory object to cause a Tor instance to pause while
9517 OpenSSL would try to read a passphrase from the terminal. (Tor
9518 instances run without a terminal, which is the case for most Tor
9519 packages, are not impacted.) Fixes bug 24246; bugfix on every
9520 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9521 Found by OSS-Fuzz as testcase 6360145429790720.
9522 - Fix a denial of service issue where an attacker could crash a
9523 directory authority using a malformed router descriptor. Fixes bug
9524 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
9526 - When checking for replays in the INTRODUCE1 cell data for a
9527 (legacy) onion service, correctly detect replays in the RSA-
9528 encrypted part of the cell. We were previously checking for
9529 replays on the entire cell, but those can be circumvented due to
9530 the malleability of Tor's legacy hybrid encryption. This fix helps
9531 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9532 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9535 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9536 - Fix a use-after-free error that could crash v2 Tor onion services
9537 when they failed to open circuits while expiring introduction
9538 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9539 also tracked as TROVE-2017-013 and CVE-2017-8823.
9541 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9542 - When running as a relay, make sure that we never build a path
9543 through ourselves, even in the case where we have somehow lost the
9544 version of our descriptor appearing in the consensus. Fixes part
9545 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9546 as TROVE-2017-012 and CVE-2017-8822.
9548 o Minor features (bridge, backport from 0.3.1.9):
9549 - Bridges now include notice in their descriptors that they are
9550 bridges, and notice of their distribution status, based on their
9551 publication settings. Implements ticket 18329. For more fine-
9552 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9555 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9556 - Add an IPv6 address for the "bastet" directory authority. Closes
9559 o Minor features (geoip):
9560 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9563 o Minor features (security, windows, backport from 0.3.1.1-alpha):
9564 - Enable a couple of pieces of Windows hardening: one
9565 (HeapEnableTerminationOnCorruption) that has been on-by-default
9566 since Windows 8, and unavailable before Windows 7; and one
9567 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9568 affect us, but shouldn't do any harm. Closes ticket 21953.
9570 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
9571 - Avoid unnecessary calls to directory_fetches_from_authorities() on
9572 relays, to prevent spurious address resolutions and descriptor
9573 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
9574 bugfix on in 0.2.8.1-alpha.
9576 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
9577 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
9578 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
9580 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
9581 - When a circuit is marked for close, do not attempt to package any
9582 cells for channels on that circuit. Previously, we would detect
9583 this condition lower in the call stack, when we noticed that the
9584 circuit had no attached channel, and log an annoying message.
9585 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
9587 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
9588 - Avoid a crash when transitioning from client mode to bridge mode.
9589 Previously, we would launch the worker threads whenever our
9590 "public server" mode changed, but not when our "server" mode
9591 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9593 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9594 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9595 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9598 Changes in version 0.2.8.17 - 2017-12-01
9599 Tor 0.2.8.17 backports important security and stability bugfixes from
9600 later Tor releases. All Tor users should upgrade to this release, or
9601 to another of the releases coming out today.
9603 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
9604 2018. If you need a release with long-term support, please upgrade with
9605 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9607 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9608 - Fix a denial of service bug where an attacker could use a
9609 malformed directory object to cause a Tor instance to pause while
9610 OpenSSL would try to read a passphrase from the terminal. (Tor
9611 instances run without a terminal, which is the case for most Tor
9612 packages, are not impacted.) Fixes bug 24246; bugfix on every
9613 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9614 Found by OSS-Fuzz as testcase 6360145429790720.
9615 - When checking for replays in the INTRODUCE1 cell data for a
9616 (legacy) onion service, correctly detect replays in the RSA-
9617 encrypted part of the cell. We were previously checking for
9618 replays on the entire cell, but those can be circumvented due to
9619 the malleability of Tor's legacy hybrid encryption. This fix helps
9620 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9621 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9624 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
9625 - Fix a use-after-free error that could crash v2 Tor onion services
9626 when they failed to open circuits while expiring introduction
9627 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
9628 also tracked as TROVE-2017-013 and CVE-2017-8823.
9630 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9631 - When running as a relay, make sure that we never build a path through
9632 ourselves, even in the case where we have somehow lost the version of
9633 our descriptor appearing in the consensus. Fixes part of bug 21534;
9634 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
9637 o Minor features (bridge, backport from 0.3.1.9):
9638 - Bridges now include notice in their descriptors that they are
9639 bridges, and notice of their distribution status, based on their
9640 publication settings. Implements ticket 18329. For more fine-
9641 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9644 o Minor features (directory authority, backport from 0.3.2.6-alpha):
9645 - Add an IPv6 address for the "bastet" directory authority. Closes
9648 o Minor features (geoip):
9649 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9652 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
9653 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
9654 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
9657 Changes in version 0.2.5.16 - 2017-12-01
9658 Tor 0.2.5.13 backports important security and stability bugfixes from
9659 later Tor releases. All Tor users should upgrade to this release, or
9660 to another of the releases coming out today.
9662 Note: the Tor 0.2.5 series will no longer be supported after 1 May
9663 2018. If you need a release with long-term support, please upgrade to
9664 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
9666 o Major bugfixes (security, backport from 0.3.2.6-alpha):
9667 - Fix a denial of service bug where an attacker could use a
9668 malformed directory object to cause a Tor instance to pause while
9669 OpenSSL would try to read a passphrase from the terminal. (Tor
9670 instances run without a terminal, which is the case for most Tor
9671 packages, are not impacted.) Fixes bug 24246; bugfix on every
9672 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
9673 Found by OSS-Fuzz as testcase 6360145429790720.
9674 - When checking for replays in the INTRODUCE1 cell data for a
9675 (legacy) onion service, correctly detect replays in the RSA-
9676 encrypted part of the cell. We were previously checking for
9677 replays on the entire cell, but those can be circumvented due to
9678 the malleability of Tor's legacy hybrid encryption. This fix helps
9679 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
9680 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
9683 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
9684 - When running as a relay, make sure that we never build a path
9685 through ourselves, even in the case where we have somehow lost the
9686 version of our descriptor appearing in the consensus. Fixes part
9687 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
9688 as TROVE-2017-012 and CVE-2017-8822.
9690 o Minor features (bridge, backport from 0.3.1.9):
9691 - Bridges now include notice in their descriptors that they are
9692 bridges, and notice of their distribution status, based on their
9693 publication settings. Implements ticket 18329. For more fine-
9694 grained control of how a bridge is distributed, upgrade to 0.3.2.x
9697 o Minor features (geoip):
9698 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9702 Changes in version 0.3.2.5-alpha - 2017-11-22
9703 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
9704 fixes several stability and reliability bugs, including a fix for
9705 intermittent bootstrapping failures that some people have been seeing
9706 since the 0.3.0.x series.
9708 Please test this alpha out -- many of these fixes will soon be
9709 backported to stable Tor versions if no additional bugs are found
9712 o Major bugfixes (bootstrapping):
9713 - Fetch descriptors aggressively whenever we lack enough to build
9714 circuits, regardless of how many descriptors we are missing.
9715 Previously, we would delay launching the fetch when we had fewer
9716 than 15 missing descriptors, even if some of those descriptors
9717 were blocking circuits from building. Fixes bug 23985; bugfix on
9718 0.1.1.11-alpha. The effects of this bug became worse in
9719 0.3.0.3-alpha, when we began treating missing descriptors from our
9720 primary guards as a reason to delay circuits.
9721 - Don't try fetching microdescriptors from relays that have failed
9722 to deliver them in the past. Fixes bug 23817; bugfix
9725 o Minor features (directory authority):
9726 - Make the "Exit" flag assignment only depend on whether the exit
9727 policy allows connections to ports 80 and 443. Previously relays
9728 would get the Exit flag if they allowed connections to one of
9729 these ports and also port 6667. Resolves ticket 23637.
9731 o Minor features (geoip):
9732 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
9735 o Minor features (linux seccomp2 sandbox):
9736 - Update the sandbox rules so that they should now work correctly
9737 with Glibc 2.26. Closes ticket 24315.
9739 o Minor features (logging):
9740 - Downgrade a pair of log messages that could occur when an exit's
9741 resolver gave us an unusual (but not forbidden) response. Closes
9743 - Improve the message we log when re-enabling circuit build timeouts
9744 after having received a consensus. Closes ticket 20963.
9746 o Minor bugfixes (compilation):
9747 - Fix a memory leak warning in one of the libevent-related
9748 configuration tests that could occur when manually specifying
9749 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
9750 Found and patched by Alex Xu.
9751 - When detecting OpenSSL on Windows from our configure script, make
9752 sure to try linking with the ws2_32 library. Fixes bug 23783;
9753 bugfix on 0.3.2.2-alpha.
9755 o Minor bugfixes (control port, linux seccomp2 sandbox):
9756 - Avoid a crash when attempting to use the seccomp2 sandbox together
9757 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
9760 o Minor bugfixes (control port, onion services):
9761 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
9762 HS_DESC event when a service is not able to upload a descriptor.
9763 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
9765 o Minor bugfixes (directory cache):
9766 - Recover better from empty or corrupt files in the consensus cache
9767 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
9768 - When a consensus diff calculation is only partially successful,
9769 only record the successful parts as having succeeded. Partial
9770 success can happen if (for example) one compression method fails
9771 but the others succeed. Previously we misrecorded all the
9772 calculations as having succeeded, which would later cause a
9773 nonfatal assertion failure. Fixes bug 24086; bugfix
9776 o Minor bugfixes (logging):
9777 - Only log once if we notice that KIST support is gone. Fixes bug
9778 24158; bugfix on 0.3.2.1-alpha.
9779 - Suppress a log notice when relay descriptors arrive. We already
9780 have a bootstrap progress for this so no need to log notice
9781 everytime tor receives relay descriptors. Microdescriptors behave
9782 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
9784 o Minor bugfixes (network layer):
9785 - When closing a connection via close_connection_immediately(), we
9786 mark it as "not blocked on bandwidth", to prevent later calls from
9787 trying to unblock it, and give it permission to read. This fixes a
9788 backtrace warning that can happen on relays under various
9789 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
9791 o Minor bugfixes (onion services):
9792 - The introduction circuit was being timed out too quickly while
9793 waiting for the rendezvous circuit to complete. Keep the intro
9794 circuit around longer instead of timing out and reopening new ones
9795 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
9796 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
9797 so it matches dir-spec.txt. Fixes bug 24262; bugfix
9799 - Silence a warning about failed v3 onion descriptor uploads that
9800 can happen naturally under certain edge cases. Fixes part of bug
9801 23662; bugfix on 0.3.2.1-alpha.
9803 o Minor bugfixes (tests):
9804 - Fix a memory leak in one of the bridge-distribution test cases.
9805 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
9806 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
9807 to correctly handle cases where a caller gives it an RSA key of
9808 under 160 bits. (This is not actually a bug in Tor itself, but
9809 rather in our fuzzing code.) Fixes bug 24247; bugfix on
9810 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
9813 - Add notes in man page regarding OS support for the various
9814 scheduler types. Attempt to use less jargon in the scheduler
9815 section. Closes ticket 24254.
9818 Changes in version 0.3.2.4-alpha - 2017-11-08
9819 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
9820 It fixes several stability and reliability bugs, especially including
9821 a major reliability issue that has been plaguing fast exit relays in
9824 o Major bugfixes (exit relays, DNS):
9825 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
9826 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
9827 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
9828 identifying and finding a workaround to this bug and to Moritz,
9829 Arthur Edelstein, and Roger for helping to track it down and
9832 o Major bugfixes (scheduler, channel):
9833 - Stop processing scheduled channels if they closed while flushing
9834 cells. This can happen if the write on the connection fails
9835 leading to the channel being closed while in the scheduler loop.
9836 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
9838 o Minor features (logging, scheduler):
9839 - Introduce a SCHED_BUG() function to log extra information about
9840 the scheduler state if we ever catch a bug in the scheduler.
9841 Closes ticket 23753.
9843 o Minor features (removed deprecations):
9844 - The ClientDNSRejectInternalAddresses flag can once again be set in
9845 non-testing Tor networks, so long as they do not use the default
9846 directory authorities. This change also removes the deprecation of
9847 this flag from 0.2.9.2-alpha. Closes ticket 21031.
9849 o Minor features (testing):
9850 - Our fuzzing tests now test the encrypted portions of v3 onion
9851 service descriptors. Implements more of 21509.
9853 o Minor bugfixes (directory client):
9854 - On failure to download directory information, delay retry attempts
9855 by a random amount based on the "decorrelated jitter" algorithm.
9856 Our previous delay algorithm tended to produce extra-long delays
9857 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
9859 o Minor bugfixes (IPv6, v3 single onion services):
9860 - Remove buggy code for IPv6-only v3 single onion services, and
9861 reject attempts to configure them. This release supports IPv4,
9862 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
9863 stack v3 single onion services. Fixes bug 23820; bugfix
9866 o Minor bugfixes (logging, relay):
9867 - Give only a protocol warning when the ed25519 key is not
9868 consistent between the descriptor and microdescriptor of a relay.
9869 This can happen, for instance, if the relay has been flagged
9870 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
9872 o Minor bugfixes (manpage, onion service):
9873 - Document that the HiddenServiceNumIntroductionPoints option is
9874 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
9875 bugfix on 0.3.2.1-alpha.
9877 o Minor bugfixes (memory leaks):
9878 - Fix a minor memory leak at exit in the KIST scheduler. This bug
9879 should have no user-visible impact. Fixes bug 23774; bugfix
9881 - Fix a memory leak when decrypting a badly formatted v3 onion
9882 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
9883 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
9885 o Minor bugfixes (onion services):
9886 - Cache some needed onion service client information instead of
9887 constantly computing it over and over again. Fixes bug 23623;
9888 bugfix on 0.3.2.1-alpha.
9889 - Properly retry HSv3 descriptor fetches when missing required
9890 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
9892 o Minor bugfixes (path selection):
9893 - When selecting relays by bandwidth, avoid a rounding error that
9894 could sometimes cause load to be imbalanced incorrectly.
9895 Previously, we would always round upwards; now, we round towards
9896 the nearest integer. This had the biggest effect when a relay's
9897 weight adjustments should have given it weight 0, but it got
9898 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
9899 - When calculating the fraction of nodes that have descriptors, and
9900 all nodes in the network have zero bandwidths, count the number of
9901 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
9902 - Actually log the total bandwidth in compute_weighted_bandwidths().
9903 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
9905 o Minor bugfixes (relay, crash):
9906 - Avoid a crash when transitioning from client mode to bridge mode.
9907 Previously, we would launch the worker threads whenever our
9908 "public server" mode changed, but not when our "server" mode
9909 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
9911 o Minor bugfixes (testing):
9912 - Fix a spurious fuzzing-only use of an uninitialized value. Found
9913 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
9914 - Test that IPv6-only clients can use microdescriptors when running
9915 "make test-network-all". Requires chutney master 61c28b9 or later.
9916 Closes ticket 24109.
9919 Changes in version 0.3.2.3-alpha - 2017-10-27
9920 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
9921 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
9922 directory authority, Bastet.
9924 o Directory authority changes:
9925 - Add "Bastet" as a ninth directory authority to the default list.
9926 Closes ticket 23910.
9927 - The directory authority "Longclaw" has changed its IP address.
9928 Closes ticket 23592.
9930 o Minor features (bridge):
9931 - Bridge relays can now set the BridgeDistribution config option to
9932 add a "bridge-distribution-request" line to their bridge
9933 descriptor, which tells BridgeDB how they'd like their bridge
9934 address to be given out. (Note that as of Oct 2017, BridgeDB does
9935 not yet implement this feature.) As a side benefit, this feature
9936 provides a way to distinguish bridge descriptors from non-bridge
9937 descriptors. Implements tickets 18329.
9939 o Minor features (client, entry guards):
9940 - Improve log messages when missing descriptors for primary guards.
9941 Resolves ticket 23670.
9943 o Minor features (geoip):
9944 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
9947 o Minor bugfixes (bridge):
9948 - Overwrite the bridge address earlier in the process of retrieving
9949 its descriptor, to make sure we reach it on the configured
9950 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
9952 o Minor bugfixes (documentation):
9953 - Document better how to read gcov, and what our gcov postprocessing
9954 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
9956 o Minor bugfixes (entry guards):
9957 - Tor now updates its guard state when it reads a consensus
9958 regardless of whether it's missing descriptors. That makes tor use
9959 its primary guards to fetch descriptors in some edge cases where
9960 it would previously have used fallback directories. Fixes bug
9961 23862; bugfix on 0.3.0.1-alpha.
9963 o Minor bugfixes (hidden service client):
9964 - When handling multiple SOCKS request for the same .onion address,
9965 only fetch the service descriptor once.
9966 - When a descriptor fetch fails with a non-recoverable error, close
9967 all pending SOCKS requests for that .onion. Fixes bug 23653;
9968 bugfix on 0.3.2.1-alpha.
9970 o Minor bugfixes (hidden service):
9971 - Always regenerate missing hidden service public key files. Prior
9972 to this, if the public key was deleted from disk, it wouldn't get
9973 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
9975 - Make sure that we have a usable ed25519 key when the intro point
9976 relay supports ed25519 link authentication. Fixes bug 24002;
9977 bugfix on 0.3.2.1-alpha.
9979 o Minor bugfixes (hidden service, v2):
9980 - When reloading configured hidden services, copy all information
9981 from the old service object. Previously, some data was omitted,
9982 causing delays in descriptor upload, and other bugs. Fixes bug
9983 23790; bugfix on 0.2.1.9-alpha.
9985 o Minor bugfixes (memory safety, defensive programming):
9986 - Clear the target address when node_get_prim_orport() returns
9987 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
9989 o Minor bugfixes (relay):
9990 - Avoid a BUG warning when receiving a dubious CREATE cell while an
9991 option transition is in progress. Fixes bug 23952; bugfix
9994 o Minor bugfixes (testing):
9995 - Adjust the GitLab CI configuration to more closely match that of
9996 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
9997 - Prevent scripts/test/coverage from attempting to move gcov output
9998 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
9999 - When running unit tests as root, skip a test that would fail
10000 because it expects a permissions error. This affects some
10001 continuous integration setups. Fixes bug 23758; bugfix
10003 - Stop unconditionally mirroring the tor repository in GitLab CI.
10004 This prevented developers from enabling GitLab CI on master. Fixes
10005 bug 23755; bugfix on 0.3.2.2-alpha.
10006 - Fix the hidden service v3 descriptor decoding fuzzing to use the
10007 latest decoding API correctly. Fixes bug 21509; bugfix
10010 o Minor bugfixes (warnings):
10011 - When we get an HTTP request on a SOCKS port, tell the user about
10012 the new HTTPTunnelPort option. Previously, we would give a "Tor is
10013 not an HTTP Proxy" message, which stopped being true when
10014 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
10018 Changes in version 0.2.5.15 - 2017-10-25
10019 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
10020 series. It also adds a new directory authority, Bastet.
10022 Note: the Tor 0.2.5 series will no longer be supported after 1 May
10023 2018. If you need a release with long-term support, please upgrade to
10024 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10026 o Directory authority changes:
10027 - Add "Bastet" as a ninth directory authority to the default list.
10028 Closes ticket 23910.
10029 - The directory authority "Longclaw" has changed its IP address.
10030 Closes ticket 23592.
10032 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10033 - Avoid an assertion failure bug affecting our implementation of
10034 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10035 handling of "0xx" differs from what we had expected. Fixes bug
10036 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10038 o Minor features (geoip):
10039 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10042 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10043 - Fix a memset() off the end of an array when packing cells. This
10044 bug should be harmless in practice, since the corrupted bytes are
10045 still in the same structure, and are always padding bytes,
10046 ignored, or immediately overwritten, depending on compiler
10047 behavior. Nevertheless, because the memset()'s purpose is to make
10048 sure that any other cell-handling bugs can't expose bytes to the
10049 network, we need to fix it. Fixes bug 22737; bugfix on
10050 0.2.4.11-alpha. Fixes CID 1401591.
10052 o Build features (backport from 0.3.1.5-alpha):
10053 - Tor's repository now includes a Travis Continuous Integration (CI)
10054 configuration file (.travis.yml). This is meant to help new
10055 developers and contributors who fork Tor to a Github repository be
10056 better able to test their changes, and understand what we expect
10057 to pass. To use this new build feature, you must fork Tor to your
10058 Github account, then go into the "Integrations" menu in the
10059 repository settings for your fork and enable Travis, then push
10060 your changes. Closes ticket 22636.
10063 Changes in version 0.2.8.16 - 2017-10-25
10064 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
10065 series, including a bugfix for a crash issue that had affected relays
10066 under memory pressure. It also adds a new directory authority, Bastet.
10068 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
10069 2018. If you need a release with long-term support, please stick with
10070 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10072 o Directory authority changes:
10073 - Add "Bastet" as a ninth directory authority to the default list.
10074 Closes ticket 23910.
10075 - The directory authority "Longclaw" has changed its IP address.
10076 Closes ticket 23592.
10078 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10079 - Fix a timing-based assertion failure that could occur when the
10080 circuit out-of-memory handler freed a connection's output buffer.
10081 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10083 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10084 - Remove longclaw's IPv6 address, as it will soon change. Authority
10085 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10086 3/8 directory authorities with IPv6 addresses, but there are also
10087 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10089 o Minor features (geoip):
10090 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10094 Changes in version 0.2.9.13 - 2017-10-25
10095 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
10096 series, including a bugfix for a crash issue that had affected relays
10097 under memory pressure. It also adds a new directory authority, Bastet.
10099 o Directory authority changes:
10100 - Add "Bastet" as a ninth directory authority to the default list.
10101 Closes ticket 23910.
10102 - The directory authority "Longclaw" has changed its IP address.
10103 Closes ticket 23592.
10105 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10106 - Fix a timing-based assertion failure that could occur when the
10107 circuit out-of-memory handler freed a connection's output buffer.
10108 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10110 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10111 - Remove longclaw's IPv6 address, as it will soon change. Authority
10112 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10113 3/8 directory authorities with IPv6 addresses, but there are also
10114 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10116 o Minor features (geoip):
10117 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10120 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
10121 - When a directory authority rejects a descriptor or extrainfo with
10122 a given digest, mark that digest as undownloadable, so that we do
10123 not attempt to download it again over and over. We previously
10124 tried to avoid downloading such descriptors by other means, but we
10125 didn't notice if we accidentally downloaded one anyway. This
10126 behavior became problematic in 0.2.7.2-alpha, when authorities
10127 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10130 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10131 - Clear the address when node_get_prim_orport() returns early.
10132 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10134 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
10135 - When running as a Windows service, set the ID of the main thread
10136 correctly. Failure to do so made us fail to send log messages to
10137 the controller in 0.2.1.16-rc, slowed down controller event
10138 delivery in 0.2.7.3-rc and later, and crash with an assertion
10139 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10140 Patch and diagnosis from "Vort".
10143 Changes in version 0.3.0.12 - 2017-10-25
10144 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
10145 series, including a bugfix for a crash issue that had affected relays
10146 under memory pressure. It also adds a new directory authority, Bastet.
10148 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
10149 2018. If you need a release with long-term support, please stick with
10150 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
10152 o Directory authority changes:
10153 - Add "Bastet" as a ninth directory authority to the default list.
10154 Closes ticket 23910.
10155 - The directory authority "Longclaw" has changed its IP address.
10156 Closes ticket 23592.
10158 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10159 - Fix a timing-based assertion failure that could occur when the
10160 circuit out-of-memory handler freed a connection's output buffer.
10161 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10163 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10164 - Remove longclaw's IPv6 address, as it will soon change. Authority
10165 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10166 3/8 directory authorities with IPv6 addresses, but there are also
10167 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10169 o Minor features (geoip):
10170 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10173 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
10174 - When a directory authority rejects a descriptor or extrainfo with
10175 a given digest, mark that digest as undownloadable, so that we do
10176 not attempt to download it again over and over. We previously
10177 tried to avoid downloading such descriptors by other means, but we
10178 didn't notice if we accidentally downloaded one anyway. This
10179 behavior became problematic in 0.2.7.2-alpha, when authorities
10180 began pinning Ed25519 keys. Fixes bug 22349; bugfix
10183 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
10184 - Avoid a possible double close of a circuit by the intro point on
10185 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10186 bugfix on 0.3.0.1-alpha.
10188 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10189 - Clear the address when node_get_prim_orport() returns early.
10190 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10192 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
10193 - When running as a Windows service, set the ID of the main thread
10194 correctly. Failure to do so made us fail to send log messages to
10195 the controller in 0.2.1.16-rc, slowed down controller event
10196 delivery in 0.2.7.3-rc and later, and crash with an assertion
10197 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
10198 Patch and diagnosis from "Vort".
10201 Changes in version 0.3.1.8 - 2017-10-25
10202 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
10203 It includes several bugfixes, including a bugfix for a crash issue
10204 that had affected relays under memory pressure. It also adds
10205 a new directory authority, Bastet.
10207 o Directory authority changes:
10208 - Add "Bastet" as a ninth directory authority to the default list.
10209 Closes ticket 23910.
10210 - The directory authority "Longclaw" has changed its IP address.
10211 Closes ticket 23592.
10213 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
10214 - Fix a timing-based assertion failure that could occur when the
10215 circuit out-of-memory handler freed a connection's output buffer.
10216 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10218 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
10219 - Remove longclaw's IPv6 address, as it will soon change. Authority
10220 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10221 3/8 directory authorities with IPv6 addresses, but there are also
10222 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10224 o Minor features (geoip):
10225 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
10228 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
10229 - Fix a compilation warning when building with zstd support on
10230 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10231 and fixed by Andreas Stieger.
10233 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
10234 - Handle a pathological case when decompressing Zstandard data when
10235 the output buffer size is zero. Fixes bug 23551; bugfix
10238 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
10239 - Remove the length limit on HTTP status lines that authorities can
10240 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
10242 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
10243 - Avoid a possible double close of a circuit by the intro point on
10244 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10245 bugfix on 0.3.0.1-alpha.
10247 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
10248 - Clear the address when node_get_prim_orport() returns early.
10249 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
10251 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
10252 - Fix additional channelpadding unit test failures by using mocked
10253 time instead of actual time for all tests. Fixes bug 23608; bugfix
10257 Changes in version 0.3.2.2-alpha - 2017-09-29
10258 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
10259 release fixes several minor bugs in the new scheduler and next-
10260 generation onion services; both features were newly added in the 0.3.2
10261 series. Other fixes in this alpha include several fixes for non-fatal
10262 tracebacks which would appear in logs.
10264 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
10265 alpha does not contain any substantial new features. Minor features
10266 include better testing and logging.
10268 The following comprises the complete list of changes included
10271 o Major bugfixes (relay, crash, assertion failure):
10272 - Fix a timing-based assertion failure that could occur when the
10273 circuit out-of-memory handler freed a connection's output buffer.
10274 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
10276 o Major bugfixes (scheduler):
10277 - If a channel is put into the scheduler's pending list, then it
10278 starts closing, and then if the scheduler runs before it finishes
10279 closing, the scheduler will get stuck trying to flush its cells
10280 while the lower layers refuse to cooperate. Fix that race
10281 condition by giving the scheduler an escape method. Fixes bug
10282 23676; bugfix on 0.3.2.1-alpha.
10284 o Minor features (build, compilation):
10285 - The "check-changes" feature is now part of the "make check" tests;
10286 we'll use it to try to prevent misformed changes files from
10287 accumulating. Closes ticket 23564.
10288 - Tor builds should now fail if there are any mismatches between the
10289 C type representing a configuration variable and the C type the
10290 data-driven parser uses to store a value there. Previously, we
10291 needed to check these by hand, which sometimes led to mistakes.
10292 Closes ticket 23643.
10294 o Minor features (directory authorities):
10295 - Remove longclaw's IPv6 address, as it will soon change. Authority
10296 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
10297 3/8 directory authorities with IPv6 addresses, but there are also
10298 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
10300 o Minor features (hidden service, circuit, logging):
10301 - Improve logging of many callsite in the circuit subsystem to print
10302 the circuit identifier(s).
10303 - Log when we cleanup an intro point from a service so we know when
10304 and for what reason it happened. Closes ticket 23604.
10306 o Minor features (logging):
10307 - Log more circuit information whenever we are about to try to
10308 package a relay cell on a circuit with a nonexistent n_chan.
10309 Attempt to diagnose ticket 8185.
10310 - Improve info-level log identification of particular circuits, to
10311 help with debugging. Closes ticket 23645.
10313 o Minor features (relay):
10314 - When choosing which circuits can be expired as unused, consider
10315 circuits from clients even if those clients used regular CREATE
10316 cells to make them; and do not consider circuits from relays even
10317 if they were made with CREATE_FAST. Part of ticket 22805.
10319 o Minor features (robustness):
10320 - Change several fatal assertions when flushing buffers into non-
10321 fatal assertions, to prevent any recurrence of 23690.
10323 o Minor features (spec conformance, bridge, diagnostic):
10324 - When handling the USERADDR command on an ExtOrPort, warn when the
10325 transports provides a USERADDR with no port. In a future version,
10326 USERADDR commands of this format may be rejected. Detects problems
10327 related to ticket 23080.
10329 o Minor features (testing):
10330 - Add a unit test to make sure that our own generated platform
10331 string will be accepted by directory authorities. Closes
10334 o Minor bugfixes (bootstrapping):
10335 - When warning about state file clock skew, report the correct
10336 direction for the detected skew. Fixes bug 23606; bugfix
10338 - Avoid an assertion failure when logging a state file clock skew
10339 very early in bootstrapping. Fixes bug 23607; bugfix
10342 o Minor bugfixes (build, compilation):
10343 - Fix a compilation warning when building with zstd support on
10344 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
10345 and fixed by Andreas Stieger.
10346 - When searching for OpenSSL, don't accept any OpenSSL library that
10347 lacks TLSv1_1_method(): Tor doesn't build with those versions.
10348 Additionally, look in /usr/local/opt/openssl, if it's present.
10349 These changes together repair the default build on OSX systems
10350 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
10352 o Minor bugfixes (compression):
10353 - Handle a pathological case when decompressing Zstandard data when
10354 the output buffer size is zero. Fixes bug 23551; bugfix
10357 o Minor bugfixes (documentation):
10358 - Fix manpage to not refer to the obsolete (and misspelled)
10359 UseEntryGuardsAsDirectoryGuards parameter in the description of
10360 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
10362 o Minor bugfixes (hidden service v3):
10363 - Don't log an assertion failure when we can't find the right
10364 information to extend to an introduction point. In rare cases,
10365 this could happen, causing a warning, even though tor would
10366 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
10367 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
10368 much bigger so the rendezvous point can't distinguish which hidden
10369 service protocol is being used. Fixes bug 23420; bugfix
10372 o Minor bugfixes (hidden service, relay):
10373 - Avoid a possible double close of a circuit by the intro point on
10374 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
10375 bugfix on 0.3.0.1-alpha.
10377 o Minor bugfixes (logging, relay shutdown, annoyance):
10378 - When a circuit is marked for close, do not attempt to package any
10379 cells for channels on that circuit. Previously, we would detect
10380 this condition lower in the call stack, when we noticed that the
10381 circuit had no attached channel, and log an annoying message.
10382 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
10384 o Minor bugfixes (scheduler):
10385 - When switching schedulers due to a consensus change, we didn't
10386 give the new scheduler a chance to react to the consensus. Fix
10387 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
10388 - Make the KISTSchedRunInterval option a non negative value. With
10389 this, the way to disable KIST through the consensus is to set it
10390 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
10391 - Only notice log the selected scheduler when we switch scheduler
10392 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
10393 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
10394 by a different tv_usec data type. Fixes bug 23575; bugfix
10396 - Make a hard exit if tor is unable to pick a scheduler which can
10397 happen if the user specifies a scheduler type that is not
10398 supported and not other types in Schedulers. Fixes bug 23581;
10399 bugfix on 0.3.2.1-alpha.
10400 - Properly initialize the scheduler last run time counter so it is
10401 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
10403 o Minor bugfixes (testing):
10404 - Capture and detect several "Result does not fit" warnings in unit
10405 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
10407 - Fix additional channelpadding unit test failures by using mocked
10408 time instead of actual time for all tests. Fixes bug 23608; bugfix
10410 - The removal of some old scheduler options caused some tests to
10411 fail on BSD systems. Assume current behavior is correct and make
10412 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
10414 o Code simplification and refactoring:
10415 - Remove various ways of testing circuits and connections for
10416 "clientness"; instead, favor channel_is_client(). Part of
10419 o Deprecated features:
10420 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
10421 now deprecated; they do not apply to relays, and they have had no
10422 effect on clients since 0.2.8.x. Closes ticket 19704.
10425 - HiddenServiceVersion man page entry wasn't mentioning the now
10426 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
10427 - Clarify that the Address option is entirely about setting an
10428 advertised IPv4 address. Closes ticket 18891.
10429 - Clarify the manpage's use of the term "address" to clarify what
10430 kind of address is intended. Closes ticket 21405.
10431 - Document that onion service subdomains are allowed, and ignored.
10432 Closes ticket 18736.
10435 Changes in version 0.3.2.1-alpha - 2017-09-18
10436 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
10437 includes support for our next-generation ("v3") onion service
10438 protocol, and adds a new circuit scheduler for more responsive
10439 forwarding decisions from relays. There are also numerous other small
10440 features and bugfixes here.
10442 Below are the changes since Tor 0.3.1.7.
10444 o Major feature (scheduler, channel):
10445 - Tor now uses new schedulers to decide which circuits should
10446 deliver cells first, in order to improve congestion at relays. The
10447 first type is called "KIST" ("Kernel Informed Socket Transport"),
10448 and is only available on Linux-like systems: it uses feedback from
10449 the kernel to prevent the kernel's TCP buffers from growing too
10450 full. The second new scheduler type is called "KISTLite": it
10451 behaves the same as KIST, but runs on systems without kernel
10452 support for inspecting TCP implementation details. The old
10453 scheduler is still available, under the name "Vanilla". To change
10454 the default scheduler preference order, use the new "Schedulers"
10455 option. (The default preference order is "KIST,KISTLite,Vanilla".)
10457 Matt Traudt implemented KIST, based on research by Rob Jansen,
10458 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
10459 more information, see the design paper at
10460 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
10461 followup implementation paper at https://arxiv.org/abs/1709.01044.
10462 Closes ticket 12541.
10464 o Major features (next-generation onion services):
10465 - Tor now supports the next-generation onion services protocol for
10466 clients and services! As part of this release, the core of
10467 proposal 224 has been implemented and is available for
10468 experimentation and testing by our users. This newer version of
10469 onion services ("v3") features many improvements over the legacy
10472 a) Better crypto (replaced SHA1/DH/RSA1024
10473 with SHA3/ed25519/curve25519)
10475 b) Improved directory protocol, leaking much less information to
10478 c) Improved directory protocol, with smaller surface for
10481 d) Better onion address security against impersonation.
10483 e) More extensible introduction/rendezvous protocol.
10485 f) A cleaner and more modular codebase.
10487 You can identify a next-generation onion address by its length:
10488 they are 56 characters long, as in
10489 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
10491 In the future, we will release more options and features for v3
10492 onion services, but we first need a testing period, so that the
10493 current codebase matures and becomes more robust. Planned features
10494 include: offline keys, advanced client authorization, improved
10495 guard algorithms, and statistics. For full details, see
10498 Legacy ("v2") onion services will still work for the foreseeable
10499 future, and will remain the default until this new codebase gets
10500 tested and hardened. Service operators who want to experiment with
10501 the new system can use the 'HiddenServiceVersion 3' torrc
10502 directive along with the regular onion service configuration
10503 options. We will publish a blog post about this new feature
10506 o Major bugfixes (usability, control port):
10507 - Report trusted clock skew indications as bootstrap errors, so
10508 controllers can more easily alert users when their clocks are
10509 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
10511 o Minor features (bug detection):
10512 - Log a warning message with a stack trace for any attempt to call
10513 get_options() during option validation. This pattern has caused
10514 subtle bugs in the past. Closes ticket 22281.
10516 o Minor features (client):
10517 - You can now use Tor as a tunneled HTTP proxy: use the new
10518 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
10519 requests. Closes ticket 22407.
10520 - Add an extra check to make sure that we always use the newer guard
10521 selection code for picking our guards. Closes ticket 22779.
10522 - When downloading (micro)descriptors, don't split the list into
10523 multiple requests unless we want at least 32 descriptors.
10524 Previously, we split at 4, not 32, which led to significant
10525 overhead in HTTP request size and degradation in compression
10526 performance. Closes ticket 23220.
10528 o Minor features (command line):
10529 - Add a new commandline option, --key-expiration, which prints when
10530 the current signing key is going to expire. Implements ticket
10531 17639; patch by Isis Lovecruft.
10533 o Minor features (control port):
10534 - If an application tries to use the control port as an HTTP proxy,
10535 respond with a meaningful "This is the Tor control port" message,
10536 and log the event. Closes ticket 1667. Patch from Ravi
10538 - Provide better error message for GETINFO desc/(id|name) when not
10539 fetching router descriptors. Closes ticket 5847. Patch by
10541 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
10542 whether Tor will try to download router descriptors and
10543 microdescriptors respectively. Closes ticket 22684.
10544 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
10545 so controllers can tell whether the geoip databases are loaded.
10546 Closes ticket 23237.
10547 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
10548 events. Closes ticket 19254. Patch by "DonnchaC".
10550 o Minor features (development support):
10551 - Developers can now generate a call-graph for Tor using the
10552 "calltool" python program, which post-processes object dumps. It
10553 should work okay on many Linux and OSX platforms, and might work
10554 elsewhere too. To run it, install calltool from
10555 https://gitweb.torproject.org/user/nickm/calltool.git and run
10556 "make callgraph". Closes ticket 19307.
10558 o Minor features (ed25519):
10559 - Add validation function to checks for torsion components in
10560 ed25519 public keys, used by prop224 client-side code. Closes
10561 ticket 22006. Math help by Ian Goldberg.
10563 o Minor features (exit relay, DNS):
10564 - Improve the clarity and safety of the log message from evdns when
10565 receiving an apparently spoofed DNS reply. Closes ticket 3056.
10567 o Minor features (integration, hardening):
10568 - Add a new NoExec option to prevent Tor from running other
10569 programs. When this option is set to 1, Tor will never try to run
10570 another program, regardless of the settings of
10571 PortForwardingHelper, ClientTransportPlugin, or
10572 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
10573 without restarting Tor. Closes ticket 22976.
10575 o Minor features (logging):
10576 - Improve the warning message for specifying a relay by nickname.
10577 The previous message implied that nickname registration was still
10578 part of the Tor network design, which it isn't. Closes
10580 - If the sandbox filter fails to load, suggest to the user that
10581 their kernel might not support seccomp2. Closes ticket 23090.
10583 o Minor features (portability):
10584 - Check at configure time whether uint8_t is the same type as
10585 unsigned char. Lots of existing code already makes this
10586 assumption, and there could be strict aliasing issues if the
10587 assumption is violated. Closes ticket 22410.
10589 o Minor features (relay, configuration):
10590 - Reject attempts to use relative file paths when RunAsDaemon is
10591 set. Previously, Tor would accept these, but the directory-
10592 changing step of RunAsDaemon would give strange and/or confusing
10593 results. Closes ticket 22731.
10595 o Minor features (startup, safety):
10596 - When configured to write a PID file, Tor now exits if it is unable
10597 to do so. Previously, it would warn and continue. Closes
10600 o Minor features (static analysis):
10601 - The BUG() macro has been changed slightly so that Coverity no
10602 longer complains about dead code if the bug is impossible. Closes
10605 o Minor features (testing):
10606 - The default chutney network tests now include tests for the v3
10607 hidden service design. Make sure you have the latest version of
10608 chutney if you want to run these. Closes ticket 22437.
10609 - Add a unit test to verify that we can parse a hardcoded v2 hidden
10610 service descriptor. Closes ticket 15554.
10612 o Minor bugfixes (certificate handling):
10613 - Fix a time handling bug in Tor certificates set to expire after
10614 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
10615 Coverity as CID 1415728.
10617 o Minor bugfixes (client, usability):
10618 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
10619 SOCKS4a requests that contain IP address strings, even when
10620 SafeSocks in enabled, as this prevents user from connecting to
10621 known IP addresses without relying on DNS for resolving. SafeSocks
10622 still rejects SOCKS connections that connect to IP addresses when
10623 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
10624 bugfix on Tor 0.2.6.2-alpha.
10626 o Minor bugfixes (code correctness):
10627 - Call htons() in extend_cell_format() for encoding a 16-bit value.
10628 Previously we used ntohs(), which happens to behave the same on
10629 all the platforms we support, but which isn't really correct.
10630 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
10631 - For defense-in-depth, make the controller's write_escaped_data()
10632 function robust to extremely long inputs. Fixes bug 19281; bugfix
10633 on 0.1.1.1-alpha. Reported by Guido Vranken.
10635 o Minor bugfixes (compilation):
10636 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
10637 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
10639 o Minor bugfixes (consensus expiry):
10640 - Check for adequate directory information correctly. Previously, Tor
10641 would reconsider whether it had sufficient directory information
10642 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
10644 o Minor bugfixes (directory protocol):
10645 - Directory servers now include a "Date:" http header for response
10646 codes other than 200. Clients starting with a skewed clock and a
10647 recent consensus were getting "304 Not modified" responses from
10648 directory authorities, so without the Date header, the client
10649 would never hear about a wrong clock. Fixes bug 23499; bugfix
10651 - Make clients wait for 6 seconds before trying to download a
10652 consensus from an authority. Fixes bug 17750; bugfix
10655 o Minor bugfixes (DoS-resistance):
10656 - If future code asks if there are any running bridges, without
10657 checking if bridges are enabled, log a BUG warning rather than
10658 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
10660 o Minor bugfixes (format strictness):
10661 - Restrict several data formats to decimal. Previously, the
10662 BuildTimeHistogram entries in the state file, the "bw=" entries in
10663 the bandwidth authority file, and the process IDs passed to the
10664 __OwningControllerProcess option could all be specified in hex or
10665 octal as well as in decimal. This was not an intentional feature.
10666 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
10669 o Minor bugfixes (heartbeat):
10670 - If we fail to write a heartbeat message, schedule a retry for the
10671 minimum heartbeat interval number of seconds in the future. Fixes
10672 bug 19476; bugfix on 0.2.3.1-alpha.
10674 o Minor bugfixes (linux seccomp2 sandbox, logging):
10675 - Fix some messages on unexpected errors from the seccomp2 library.
10676 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
10678 o Minor bugfixes (logging):
10679 - Remove duplicate log messages regarding opening non-local
10680 SocksPorts upon parsing config and opening listeners at startup.
10681 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
10682 - Use a more comprehensible log message when telling the user
10683 they've excluded every running exit node. Fixes bug 7890; bugfix
10685 - When logging the number of descriptors we intend to download per
10686 directory request, do not log a number higher than then the number
10687 of descriptors we're fetching in total. Fixes bug 19648; bugfix
10689 - When warning about a directory owned by the wrong user, log the
10690 actual name of the user owning the directory. Previously, we'd log
10691 the name of the process owner twice. Fixes bug 23487; bugfix
10693 - The tor specification says hop counts are 1-based, so fix two log
10694 messages that mistakenly logged 0-based hop counts. Fixes bug
10695 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
10696 Credit to Xiaofan Li for reporting this issue.
10698 o Minor bugfixes (portability):
10699 - Stop using the PATH_MAX variable, which is not defined on GNU
10700 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
10702 o Minor bugfixes (relay):
10703 - When uploading our descriptor for the first time after startup,
10704 report the reason for uploading as "Tor just started" rather than
10705 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
10706 - Avoid unnecessary calls to directory_fetches_from_authorities() on
10707 relays, to prevent spurious address resolutions and descriptor
10708 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
10709 bugfix on in 0.2.8.1-alpha.
10711 o Minor bugfixes (tests):
10712 - Fix a broken unit test for the OutboundAddress option: the parsing
10713 function was never returning an error on failure. Fixes bug 23366;
10714 bugfix on 0.3.0.3-alpha.
10715 - Fix a signed-integer overflow in the unit tests for
10716 dir/download_status_random_backoff, which was untriggered until we
10717 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
10719 o Minor bugfixes (usability, control port):
10720 - Stop making an unnecessary routerlist check in NETINFO clock skew
10721 detection; this was preventing clients from reporting NETINFO clock
10722 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
10724 o Code simplification and refactoring:
10725 - Extract the code for handling newly-open channels into a separate
10726 function from the general code to handle channel state
10727 transitions. This change simplifies our callgraph, reducing the
10728 size of the largest strongly connected component by roughly a
10729 factor of two. Closes ticket 22608.
10730 - Remove dead code for largely unused statistics on the number of
10731 times we've attempted various public key operations. Fixes bug
10732 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
10733 - Remove several now-obsolete functions for asking about old
10734 variants directory authority status. Closes ticket 22311; patch
10736 - Remove some of the code that once supported "Named" and "Unnamed"
10737 routers. Authorities no longer vote for these flags. Closes
10739 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
10740 and old hidden services, to indicate that they aren't suitable for
10741 new protocols or formats. Closes ticket 23026.
10742 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
10743 22521. Patch from Neel Chauhan.
10744 - Split the enormous circuit_send_next_onion_skin() function into
10745 multiple subfunctions. Closes ticket 22804.
10746 - Split the portions of the buffer.c module that handle particular
10747 protocols into separate modules. Part of ticket 23149.
10748 - Use our test macros more consistently, to produce more useful
10749 error messages when our unit tests fail. Add coccinelle patches to
10750 allow us to re-check for test macro uses. Closes ticket 22497.
10752 o Deprecated features:
10753 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
10754 only applies to direct unencrypted HTTP connections to your
10755 directory server, which your Tor probably isn't using. Closes
10759 - Clarify in the manual that "Sandbox 1" is only supported on Linux
10760 kernels. Closes ticket 22677.
10761 - Document all values of PublishServerDescriptor in the manpage.
10762 Closes ticket 15645.
10763 - Improve the documentation for the directory port part of the
10764 DirAuthority line. Closes ticket 20152.
10765 - Restore documentation for the authorities' "approved-routers"
10766 file. Closes ticket 21148.
10768 o Removed features:
10769 - The AllowDotExit option has been removed as unsafe. It has been
10770 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
10771 - The ClientDNSRejectInternalAddresses flag can no longer be set on
10772 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
10773 Closes ticket 21031.
10774 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
10775 nobody was using it any longer. Closes ticket 22377.
10778 Changes in version 0.2.8.15 - 2017-09-18
10779 Tor 0.2.8.15 backports a collection of bugfixes from later
10782 Most significantly, it includes a fix for TROVE-2017-008, a
10783 security bug that affects hidden services running with the
10784 SafeLogging option disabled. For more information, see
10785 https://trac.torproject.org/projects/tor/ticket/23490
10787 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
10788 2018. We suggest that you upgrade to the latest stable release if
10789 possible. If you can't, we recommend that you upgrade at least to
10790 0.2.9, which will be supported until 2020.
10792 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10793 - Avoid an assertion failure bug affecting our implementation of
10794 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10795 handling of "0xx" differs from what we had expected. Fixes bug
10796 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10799 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10802 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10803 - Backport a fix for an "unused variable" warning that appeared
10804 in some versions of mingw. Fixes bug 22838; bugfix on
10807 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10808 - Fix a memset() off the end of an array when packing cells. This
10809 bug should be harmless in practice, since the corrupted bytes are
10810 still in the same structure, and are always padding bytes,
10811 ignored, or immediately overwritten, depending on compiler
10812 behavior. Nevertheless, because the memset()'s purpose is to make
10813 sure that any other cell-handling bugs can't expose bytes to the
10814 network, we need to fix it. Fixes bug 22737; bugfix on
10815 0.2.4.11-alpha. Fixes CID 1401591.
10817 o Build features (backport from 0.3.1.5-alpha):
10818 - Tor's repository now includes a Travis Continuous Integration (CI)
10819 configuration file (.travis.yml). This is meant to help new
10820 developers and contributors who fork Tor to a Github repository be
10821 better able to test their changes, and understand what we expect
10822 to pass. To use this new build feature, you must fork Tor to your
10823 Github account, then go into the "Integrations" menu in the
10824 repository settings for your fork and enable Travis, then push
10825 your changes. Closes ticket 22636.
10828 Changes in version 0.2.9.12 - 2017-09-18
10829 Tor 0.2.9.12 backports a collection of bugfixes from later
10832 Most significantly, it includes a fix for TROVE-2017-008, a
10833 security bug that affects hidden services running with the
10834 SafeLogging option disabled. For more information, see
10835 https://trac.torproject.org/projects/tor/ticket/23490
10837 o Major features (security, backport from 0.3.0.2-alpha):
10838 - Change the algorithm used to decide DNS TTLs on client and server
10839 side, to better resist DNS-based correlation attacks like the
10840 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10841 Feamster. Now relays only return one of two possible DNS TTL
10842 values, and clients are willing to believe DNS TTL values up to 3
10843 hours long. Closes ticket 19769.
10845 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
10846 - Fix a rare crash when sending a begin cell on a circuit whose
10847 linked directory connection had already been closed. Fixes bug
10848 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
10850 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
10851 - Fix a bug that prevented exit nodes from caching DNS records for
10852 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10854 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
10855 - Fix a typo that had prevented TPROXY-based transparent proxying
10856 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
10857 Patch from "d4fq0fQAgoJ".
10859 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
10860 - Avoid an assertion failure bug affecting our implementation of
10861 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
10862 handling of "0xx" differs from what we had expected. Fixes bug
10863 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
10865 o Minor features (code style, backport from 0.3.1.3-alpha):
10866 - Add "Falls through" comments to our codebase, in order to silence
10867 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10868 Stieger. Closes ticket 22446.
10870 o Minor features (geoip):
10871 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10874 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
10875 - Roll over monthly accounting at the configured hour and minute,
10876 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
10877 Found by Andrey Karpov with PVS-Studio.
10879 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
10880 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
10881 bugfix on 0.2.8.1-alpha.
10882 - Fix warnings when building with libscrypt and openssl scrypt support
10883 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
10884 - When building with certain versions the mingw C header files, avoid
10885 float-conversion warnings when calling the C functions isfinite(),
10886 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
10888 o Minor bugfixes (compilation, backport from 0.3.1.7):
10889 - Avoid compiler warnings in the unit tests for running tor_sscanf()
10890 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10892 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
10893 - Backport a fix for an "unused variable" warning that appeared
10894 in some versions of mingw. Fixes bug 22838; bugfix on
10897 o Minor bugfixes (controller, backport from 0.3.1.7):
10898 - Do not crash when receiving a HSPOST command with an empty body.
10899 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10900 - Do not crash when receiving a POSTDESCRIPTOR command with an
10901 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10903 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
10904 - Avoid Coverity build warnings related to our BUG() macro. By
10905 default, Coverity treats BUG() as the Linux kernel does: an
10906 instant abort(). We need to override that so our BUG() macro
10907 doesn't prevent Coverity from analyzing functions that use it.
10908 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
10910 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
10911 - Fix a memset() off the end of an array when packing cells. This
10912 bug should be harmless in practice, since the corrupted bytes are
10913 still in the same structure, and are always padding bytes,
10914 ignored, or immediately overwritten, depending on compiler
10915 behavior. Nevertheless, because the memset()'s purpose is to make
10916 sure that any other cell-handling bugs can't expose bytes to the
10917 network, we need to fix it. Fixes bug 22737; bugfix on
10918 0.2.4.11-alpha. Fixes CID 1401591.
10920 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10921 - When setting the maximum number of connections allowed by the OS,
10922 always allow some extra file descriptors for other files. Fixes
10923 bug 22797; bugfix on 0.2.0.10-alpha.
10925 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
10926 - Avoid a sandbox failure when trying to re-bind to a socket and
10927 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
10929 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
10930 - Permit the fchmod system call, to avoid crashing on startup when
10931 starting with the seccomp2 sandbox and an unexpected set of
10932 permissions on the data directory or its contents. Fixes bug
10933 22516; bugfix on 0.2.5.4-alpha.
10935 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
10936 - Avoid a double-marked-circuit warning that could happen when we
10937 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
10940 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
10941 - Reject version numbers with non-numeric prefixes (such as +, -, or
10942 whitespace). Disallowing whitespace prevents differential version
10943 parsing between POSIX-based and Windows platforms. Fixes bug 21507
10944 and part of 21508; bugfix on 0.0.8pre1.
10946 o Build features (backport from 0.3.1.5-alpha):
10947 - Tor's repository now includes a Travis Continuous Integration (CI)
10948 configuration file (.travis.yml). This is meant to help new
10949 developers and contributors who fork Tor to a Github repository be
10950 better able to test their changes, and understand what we expect
10951 to pass. To use this new build feature, you must fork Tor to your
10952 Github account, then go into the "Integrations" menu in the
10953 repository settings for your fork and enable Travis, then push
10954 your changes. Closes ticket 22636.
10957 Changes in version 0.3.0.11 - 2017-09-18
10958 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
10961 Most significantly, it includes a fix for TROVE-2017-008, a
10962 security bug that affects hidden services running with the
10963 SafeLogging option disabled. For more information, see
10964 https://trac.torproject.org/projects/tor/ticket/23490
10966 o Minor features (code style, backport from 0.3.1.7):
10967 - Add "Falls through" comments to our codebase, in order to silence
10968 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
10969 Stieger. Closes ticket 22446.
10972 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
10975 o Minor bugfixes (compilation, backport from 0.3.1.7):
10976 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
10977 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
10979 o Minor bugfixes (controller, backport from 0.3.1.7):
10980 - Do not crash when receiving a HSPOST command with an empty body.
10981 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
10982 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
10983 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
10985 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
10986 - When setting the maximum number of connections allowed by the OS,
10987 always allow some extra file descriptors for other files. Fixes
10988 bug 22797; bugfix on 0.2.0.10-alpha.
10990 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
10991 - Remove a forgotten debugging message when an introduction point
10992 successfully establishes a hidden service prop224 circuit with
10994 - Change three other log_warn() for an introduction point to
10995 protocol warnings, because they can be failure from the network
10996 and are not relevant to the operator. Fixes bug 23078; bugfix on
10997 0.3.0.1-alpha and 0.3.0.2-alpha.
11000 Changes in version 0.3.1.7 - 2017-09-18
11001 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
11003 With the 0.3.1 series, Tor now serves and downloads directory
11004 information in more compact formats, to save on bandwidth overhead. It
11005 also contains a new padding system to resist netflow-based traffic
11006 analysis, and experimental support for building parts of Tor in Rust
11007 (though no parts of Tor are in Rust yet). There are also numerous
11008 small features, bugfixes on earlier release series, and groundwork for
11009 the hidden services revamp of 0.3.2.
11011 This release also includes a fix for TROVE-2017-008, a security bug
11012 that affects hidden services running with the SafeLogging option
11013 disabled. For more information, see
11014 https://trac.torproject.org/projects/tor/ticket/23490
11016 Per our stable release policy, we plan to support each stable release
11017 series for at least the next nine months, or for three months after
11018 the first stable release of the next series: whichever is longer. If
11019 you need a release with long-term support, we recommend that you stay
11020 with the 0.2.9 series.
11022 Below is a list of the changes since 0.3.1.6-rc. For a list of all
11023 changes since 0.3.0, see the ReleaseNotes file.
11025 o Major bugfixes (security, hidden services, loggging):
11026 - Fix a bug where we could log uninitialized stack when a certain
11027 hidden service error occurred while SafeLogging was disabled.
11028 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
11029 TROVE-2017-008 and CVE-2017-0380.
11031 o Minor features (defensive programming):
11032 - Create a pair of consensus parameters, nf_pad_tor2web and
11033 nf_pad_single_onion, to disable netflow padding in the consensus
11034 for non-anonymous connections in case the overhead is high. Closes
11037 o Minor features (diagnostic):
11038 - Add a stack trace to the bug warnings that can be logged when
11039 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
11040 attempt for bug 23105.
11042 o Minor features (geoip):
11043 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
11046 o Minor bugfixes (compilation):
11047 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
11048 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
11050 o Minor bugfixes (controller):
11051 - Do not crash when receiving a HSPOST command with an empty body.
11052 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
11053 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
11054 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
11056 o Minor bugfixes (relay):
11057 - Inform the geoip and rephist modules about all requests, even on
11058 relays that are only fetching microdescriptors. Fixes a bug
11059 related to 21585; bugfix on 0.3.0.1-alpha.
11061 o Minor bugfixes (unit tests):
11062 - Fix a channelpadding unit test failure on slow systems by using
11063 mocked time instead of actual time. Fixes bug 23077; bugfix
11067 Changes in version 0.3.1.6-rc - 2017-09-05
11068 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
11069 release series, including a bug that produced weird behavior on
11070 Windows directory caches.
11072 This is the first release candidate in the Tor 0.3.1 series. If we
11073 find no new bugs or regressions here, the first stable 0.3.1 release
11074 will be nearly identical to it.
11076 o Major bugfixes (windows, directory cache):
11077 - On Windows, do not try to delete cached consensus documents and
11078 diffs before they are unmapped from memory--Windows won't allow
11079 that. Instead, allow the consensus cache directory to grow larger,
11080 to hold files that might need to stay around longer. Fixes bug
11081 22752; bugfix on 0.3.1.1-alpha.
11083 o Minor features (directory authority):
11084 - Improve the message that authorities report to relays that present
11085 RSA/Ed25519 keypairs that conflict with previously pinned keys.
11086 Closes ticket 22348.
11088 o Minor features (geoip):
11089 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
11092 o Minor features (testing):
11093 - Add more tests for compression backend initialization. Closes
11096 o Minor bugfixes (directory cache):
11097 - Fix a memory leak when recovering space in the consensus cache.
11098 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
11100 o Minor bugfixes (hidden service):
11101 - Increase the number of circuits that a service is allowed to
11102 open over a specific period of time. The value was lower than it
11103 should be (8 vs 12) in the normal case of 3 introduction points.
11104 Fixes bug 22159; bugfix on 0.3.0.5-rc.
11105 - Fix a BUG warning during HSv3 descriptor decoding that could be
11106 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
11107 on 0.3.0.1-alpha. Bug found by "haxxpop".
11108 - Rate-limit the log messages if we exceed the maximum number of
11109 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
11111 o Minor bugfixes (logging, relay):
11112 - Remove a forgotten debugging message when an introduction point
11113 successfully establishes a hidden service prop224 circuit with
11115 - Change three other log_warn() for an introduction point to
11116 protocol warnings, because they can be failure from the network
11117 and are not relevant to the operator. Fixes bug 23078; bugfix on
11118 0.3.0.1-alpha and 0.3.0.2-alpha.
11120 o Minor bugfixes (relay):
11121 - When a relay is not running as a directory cache, it will no
11122 longer generate compressed consensuses and consensus diff
11123 information. Previously, this was a waste of disk and CPU. Fixes
11124 bug 23275; bugfix on 0.3.1.1-alpha.
11126 o Minor bugfixes (robustness, error handling):
11127 - Improve our handling of the cases where OpenSSL encounters a
11128 memory error while encoding keys and certificates. We haven't
11129 observed these errors in the wild, but if they do happen, we now
11130 detect and respond better. Fixes bug 19418; bugfix on all versions
11131 of Tor. Reported by Guido Vranken.
11133 o Minor bugfixes (stability):
11134 - Avoid crashing on a double-free when unable to load or process an
11135 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
11136 with the clang static analyzer.
11138 o Minor bugfixes (testing):
11139 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
11140 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
11141 - Port the hs_ntor handshake test to work correctly with recent
11142 versions of the pysha3 module. Fixes bug 23071; bugfix
11145 o Minor bugfixes (Windows service):
11146 - When running as a Windows service, set the ID of the main thread
11147 correctly. Failure to do so made us fail to send log messages to
11148 the controller in 0.2.1.16-rc, slowed down controller event
11149 delivery in 0.2.7.3-rc and later, and crash with an assertion
11150 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
11151 Patch and diagnosis from "Vort".
11154 Changes in version 0.3.0.10 - 2017-08-02
11155 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
11156 from the current Tor alpha series. OpenBSD users and TPROXY users
11157 should upgrade; others are probably okay sticking with 0.3.0.9.
11159 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
11160 - Tor's repository now includes a Travis Continuous Integration (CI)
11161 configuration file (.travis.yml). This is meant to help new
11162 developers and contributors who fork Tor to a Github repository be
11163 better able to test their changes, and understand what we expect
11164 to pass. To use this new build feature, you must fork Tor to your
11165 Github account, then go into the "Integrations" menu in the
11166 repository settings for your fork and enable Travis, then push
11167 your changes. Closes ticket 22636.
11169 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
11170 - Fix a typo that had prevented TPROXY-based transparent proxying
11171 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11172 Patch from "d4fq0fQAgoJ".
11174 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
11175 - Avoid an assertion failure bug affecting our implementation of
11176 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11177 handling of "0xbar" differs from what we had expected. Fixes bug
11178 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11180 o Minor features (backport from 0.3.1.5-alpha):
11181 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
11184 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
11185 - Roll over monthly accounting at the configured hour and minute,
11186 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
11187 Found by Andrey Karpov with PVS-Studio.
11189 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
11190 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
11191 bugfix on 0.2.8.1-alpha.
11192 - Fix warnings when building with libscrypt and openssl scrypt
11193 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11194 - When building with certain versions of the mingw C header files,
11195 avoid float-conversion warnings when calling the C functions
11196 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11199 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
11200 - Backport a fix for an "unused variable" warning that appeared
11201 in some versions of mingw. Fixes bug 22838; bugfix on
11204 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
11205 - Avoid Coverity build warnings related to our BUG() macro. By
11206 default, Coverity treats BUG() as the Linux kernel does: an
11207 instant abort(). We need to override that so our BUG() macro
11208 doesn't prevent Coverity from analyzing functions that use it.
11209 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11211 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
11212 - When rejecting a router descriptor for running an obsolete version
11213 of Tor without ntor support, warn about the obsolete tor version,
11214 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
11216 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
11217 - Avoid a sandbox failure when trying to re-bind to a socket and
11218 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11220 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
11221 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11222 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11225 Changes in version 0.3.1.5-alpha - 2017-08-01
11226 Tor 0.3.1.5-alpha improves the performance of consensus diff
11227 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
11228 several other bugs. If no serious bugs are found in this version, the
11229 next version will be a release candidate.
11231 This release also marks the end of support for the Tor 0.2.4.x,
11232 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
11233 further bug or security fixes. Anyone still running or distributing
11234 one of those versions should upgrade.
11236 o Major features (build system, continuous integration):
11237 - Tor's repository now includes a Travis Continuous Integration (CI)
11238 configuration file (.travis.yml). This is meant to help new
11239 developers and contributors who fork Tor to a Github repository be
11240 better able to test their changes, and understand what we expect
11241 to pass. To use this new build feature, you must fork Tor to your
11242 Github account, then go into the "Integrations" menu in the
11243 repository settings for your fork and enable Travis, then push
11244 your changes. Closes ticket 22636.
11246 o Major bugfixes (openbsd, denial-of-service):
11247 - Avoid an assertion failure bug affecting our implementation of
11248 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
11249 handling of "0xbar" differs from what we had expected. Fixes bug
11250 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
11252 o Major bugfixes (relay, performance):
11253 - Perform circuit handshake operations at a higher priority than we
11254 use for consensus diff creation and compression. This should
11255 prevent circuits from starving when a relay or bridge receives a
11256 new consensus, especially on lower-powered machines. Fixes bug
11257 22883; bugfix on 0.3.1.1-alpha.
11259 o Minor features (bridge authority):
11260 - Add "fingerprint" lines to the networkstatus-bridges file produced
11261 by bridge authorities. Closes ticket 22207.
11263 o Minor features (directory cache, consensus diff):
11264 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
11265 operators with low-resource environments to adjust the number of
11266 consensuses they'll store and generate diffs from. Most cache
11267 operators should leave it unchanged. Helps to work around
11270 o Minor features (geoip):
11271 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
11274 o Minor features (relay, performance):
11275 - Always start relays with at least two worker threads, to prevent
11276 priority inversion on slow tasks. Part of the fix for bug 22883.
11277 - Allow background work to be queued with different priorities, so
11278 that a big pile of slow low-priority jobs will not starve out
11279 higher priority jobs. This lays the groundwork for a fix for
11282 o Minor bugfixes (build system, rust):
11283 - Fix a problem where Rust toolchains were not being found when
11284 building without --enable-cargo-online-mode, due to setting the
11285 $HOME environment variable instead of $CARGO_HOME. Fixes bug
11286 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
11288 o Minor bugfixes (compatibility, zstd):
11289 - Write zstd epilogues correctly when the epilogue requires
11290 reallocation of the output buffer, even with zstd 1.3.0.
11291 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
11292 22927; bugfix on 0.3.1.1-alpha.
11294 o Minor bugfixes (compilation warnings):
11295 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
11296 22915; bugfix on 0.2.8.1-alpha.
11297 - Fix warnings when building with libscrypt and openssl scrypt
11298 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
11299 - Compile correctly when both openssl 1.1.0 and libscrypt are
11300 detected. Previously this would cause an error. Fixes bug 22892;
11301 bugfix on 0.3.1.1-alpha.
11302 - When building with certain versions of the mingw C header files,
11303 avoid float-conversion warnings when calling the C functions
11304 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
11307 o Minor bugfixes (coverity build support):
11308 - Avoid Coverity build warnings related to our BUG() macro. By
11309 default, Coverity treats BUG() as the Linux kernel does: an
11310 instant abort(). We need to override that so our BUG() macro
11311 doesn't prevent Coverity from analyzing functions that use it.
11312 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
11314 o Minor bugfixes (directory authority):
11315 - When a directory authority rejects a descriptor or extrainfo with
11316 a given digest, mark that digest as undownloadable, so that we do
11317 not attempt to download it again over and over. We previously
11318 tried to avoid downloading such descriptors by other means, but we
11319 didn't notice if we accidentally downloaded one anyway. This
11320 behavior became problematic in 0.2.7.2-alpha, when authorities
11321 began pinning Ed25519 keys. Fixes bug 22349; bugfix
11324 o Minor bugfixes (error reporting, windows):
11325 - When formatting Windows error messages, use the English format to
11326 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
11329 o Minor bugfixes (file limits, osx):
11330 - When setting the maximum number of connections allowed by the OS,
11331 always allow some extra file descriptors for other files. Fixes
11332 bug 22797; bugfix on 0.2.0.10-alpha.
11334 o Minor bugfixes (linux seccomp2 sandbox):
11335 - Avoid a sandbox failure when trying to re-bind to a socket and
11336 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
11338 o Minor bugfixes (memory leaks):
11339 - Fix a small memory leak when validating a configuration that uses
11340 two or more AF_UNIX sockets for the same port type. Fixes bug
11341 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
11343 o Minor bugfixes (unit tests):
11344 - test_consdiff_base64cmp would fail on OS X because while OS X
11345 follows the standard of (less than zero/zero/greater than zero),
11346 it doesn't follow the convention of (-1/0/+1). Make the test
11347 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
11348 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
11349 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
11352 Changes in version 0.3.1.4-alpha - 2017-06-29
11353 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
11354 to use a guard that was in the same network family as a chosen exit
11355 relay. This is a security regression; all clients running earlier
11356 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
11359 This release also fixes several other bugs introduced in 0.3.0.x
11360 and 0.3.1.x, including others that can affect bandwidth usage
11363 o New dependencies:
11364 - To build with zstd and lzma support, Tor now requires the
11365 pkg-config tool at build time. (This requirement was new in
11366 0.3.1.1-alpha, but was not noted at the time. Noting it here to
11367 close ticket 22623.)
11369 o Major bugfixes (path selection, security):
11370 - When choosing which guard to use for a circuit, avoid the exit's
11371 family along with the exit itself. Previously, the new guard
11372 selection logic avoided the exit, but did not consider its family.
11373 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11374 006 and CVE-2017-0377.
11376 o Major bugfixes (compression, zstd):
11377 - Correctly detect a full buffer when decompressing a large zstd-
11378 compressed input. Previously, we would sometimes treat a full
11379 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
11381 o Major bugfixes (directory protocol):
11382 - Ensure that we send "304 Not modified" as HTTP status code when a
11383 client is attempting to fetch a consensus or consensus diff, and
11384 the best one we can send them is one they already have. Fixes bug
11385 22702; bugfix on 0.3.1.1-alpha.
11387 o Major bugfixes (entry guards):
11388 - When starting with an old consensus, do not add new entry guards
11389 unless the consensus is "reasonably live" (under 1 day old). Fixes
11390 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11392 o Minor features (bug mitigation, diagnostics, logging):
11393 - Avoid an assertion failure, and log a better error message, when
11394 unable to remove a file from the consensus cache on Windows.
11395 Attempts to mitigate and diagnose bug 22752.
11397 o Minor features (geoip):
11398 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
11401 o Minor bugfixes (compression):
11402 - When compressing or decompressing a buffer, check for a failure to
11403 create a compression object. Fixes bug 22626; bugfix
11405 - When decompressing a buffer, check for extra data after the end of
11406 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
11407 - When decompressing an object received over an anonymous directory
11408 connection, if we have already decompressed it using an acceptable
11409 compression method, do not reject it for looking like an
11410 unacceptable compression method. Fixes part of bug 22670; bugfix
11412 - When serving directory votes compressed with zlib, do not claim to
11413 have compressed them with zstd. Fixes bug 22669; bugfix
11415 - When spooling compressed data to an output buffer, don't try to
11416 spool more data when there is no more data to spool and we are not
11417 trying to flush the input. Previously, we would sometimes launch
11418 compression requests with nothing to do, which interferes with our
11419 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
11421 o Minor bugfixes (defensive programming):
11422 - Detect and break out of infinite loops in our compression code. We
11423 don't think that any such loops exist now, but it's best to be
11424 safe. Closes ticket 22672.
11425 - Fix a memset() off the end of an array when packing cells. This
11426 bug should be harmless in practice, since the corrupted bytes are
11427 still in the same structure, and are always padding bytes,
11428 ignored, or immediately overwritten, depending on compiler
11429 behavior. Nevertheless, because the memset()'s purpose is to make
11430 sure that any other cell-handling bugs can't expose bytes to the
11431 network, we need to fix it. Fixes bug 22737; bugfix on
11432 0.2.4.11-alpha. Fixes CID 1401591.
11434 o Minor bugfixes (linux seccomp2 sandbox):
11435 - Permit the fchmod system call, to avoid crashing on startup when
11436 starting with the seccomp2 sandbox and an unexpected set of
11437 permissions on the data directory or its contents. Fixes bug
11438 22516; bugfix on 0.2.5.4-alpha.
11439 - Fix a crash in the LZMA module, when the sandbox was enabled, and
11440 liblzma would allocate more than 16 MB of memory. We solve this by
11441 bumping the mprotect() limit in the sandbox module from 16 MB to
11442 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
11444 o Minor bugfixes (logging):
11445 - When decompressing, do not warn if we fail to decompress using a
11446 compression method that we merely guessed. Fixes part of bug
11447 22670; bugfix on 0.1.1.14-alpha.
11448 - When decompressing, treat mismatch between content-encoding and
11449 actual compression type as a protocol warning. Fixes part of bug
11450 22670; bugfix on 0.1.1.9-alpha.
11451 - Downgrade "assigned_to_cpuworker failed" message to info-level
11452 severity. In every case that can reach it, either a better warning
11453 has already been logged, or no warning is warranted. Fixes bug
11454 22356; bugfix on 0.2.6.3-alpha.
11455 - Demote a warn that was caused by libevent delays to info if
11456 netflow padding is less than 4.5 seconds late, or to notice
11457 if it is more (4.5 seconds is the amount of time that a netflow
11458 record might be emitted after, if we chose the maximum timeout).
11459 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
11461 o Minor bugfixes (process behavior):
11462 - When exiting because of an error, always exit with a nonzero exit
11463 status. Previously, we would fail to report an error in our exit
11464 status in cases related to __OwningControllerProcess failure,
11465 lockfile contention, and Ed25519 key initialization. Fixes bug
11466 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
11467 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
11471 - Add a manpage description for the key-pinning-journal file. Closes
11473 - Correctly note that bandwidth accounting values are stored in the
11474 state file, and the bw_accounting file is now obsolete. Closes
11476 - Document more of the files in the Tor data directory, including
11477 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
11478 approved-routers, sr-random, and diff-cache. Found while fixing
11482 Changes in version 0.3.0.9 - 2017-06-29
11483 Tor 0.3.0.9 fixes a path selection bug that would allow a client
11484 to use a guard that was in the same network family as a chosen exit
11485 relay. This is a security regression; all clients running earlier
11486 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
11489 This release also backports several other bugfixes from the 0.3.1.x
11492 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
11493 - When choosing which guard to use for a circuit, avoid the exit's
11494 family along with the exit itself. Previously, the new guard
11495 selection logic avoided the exit, but did not consider its family.
11496 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
11497 006 and CVE-2017-0377.
11499 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
11500 - Don't block bootstrapping when a primary bridge is offline and we
11501 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11502 21969; bugfix on 0.3.0.3-alpha.
11504 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
11505 - When starting with an old consensus, do not add new entry guards
11506 unless the consensus is "reasonably live" (under 1 day old). Fixes
11507 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
11509 o Minor features (geoip):
11510 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
11513 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
11514 - Reject version numbers with non-numeric prefixes (such as +, -, or
11515 whitespace). Disallowing whitespace prevents differential version
11516 parsing between POSIX-based and Windows platforms. Fixes bug 21507
11517 and part of 21508; bugfix on 0.0.8pre1.
11519 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
11520 - Permit the fchmod system call, to avoid crashing on startup when
11521 starting with the seccomp2 sandbox and an unexpected set of
11522 permissions on the data directory or its contents. Fixes bug
11523 22516; bugfix on 0.2.5.4-alpha.
11525 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
11526 - Fix a memset() off the end of an array when packing cells. This
11527 bug should be harmless in practice, since the corrupted bytes are
11528 still in the same structure, and are always padding bytes,
11529 ignored, or immediately overwritten, depending on compiler
11530 behavior. Nevertheless, because the memset()'s purpose is to make
11531 sure that any other cell-handling bugs can't expose bytes to the
11532 network, we need to fix it. Fixes bug 22737; bugfix on
11533 0.2.4.11-alpha. Fixes CID 1401591.
11536 Changes in version 0.3.1.3-alpha - 2017-06-08
11537 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
11538 remotely crash a hidden service with an assertion failure. Anyone
11539 running a hidden service should upgrade to this version, or to some
11540 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
11542 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
11543 that sometimes made relays unreliable, as well as several other
11544 bugfixes described below.
11546 o Major bugfixes (hidden service, relay, security):
11547 - Fix a remotely triggerable assertion failure when a hidden service
11548 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11549 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11550 - Fix a remotely triggerable assertion failure caused by receiving a
11551 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11552 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11555 o Major bugfixes (relay, link handshake):
11556 - When performing the v3 link handshake on a TLS connection, report
11557 that we have the x509 certificate that we actually used on that
11558 connection, even if we have changed certificates since that
11559 connection was first opened. Previously, we would claim to have
11560 used our most recent x509 link certificate, which would sometimes
11561 make the link handshake fail. Fixes one case of bug 22460; bugfix
11564 o Major bugfixes (relays, key management):
11565 - Regenerate link and authentication certificates whenever the key
11566 that signs them changes; also, regenerate link certificates
11567 whenever the signed key changes. Previously, these processes were
11568 only weakly coupled, and we relays could (for minutes to hours)
11569 wind up with an inconsistent set of keys and certificates, which
11570 other relays would not accept. Fixes two cases of bug 22460;
11571 bugfix on 0.3.0.1-alpha.
11572 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11573 send the certificate that matches the x509 certificate that we
11574 used on the TLS connection. Previously, there was a race condition
11575 if the TLS context rotated after we began the TLS handshake but
11576 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11579 o Major bugfixes (torrc, crash):
11580 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
11581 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
11583 o Minor features (code style):
11584 - Add "Falls through" comments to our codebase, in order to silence
11585 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
11586 Stieger. Closes ticket 22446.
11588 o Minor features (diagnostic):
11589 - Add logging messages to try to diagnose a rare bug that seems to
11590 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
11591 think this is happening because of incorrect system clocks, but
11592 we'd like to know for certain. Diagnostic for bug 22466.
11594 o Minor bugfixes (correctness):
11595 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11596 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11598 o Minor bugfixes (directory protocol):
11599 - Check for libzstd >= 1.1, because older versions lack the
11600 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
11602 o Minor bugfixes (link handshake):
11603 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11604 months, and regenerate it when it is within one month of expiring.
11605 Previously, we had generated this certificate at startup with a
11606 ten-year lifetime, but that could lead to weird behavior when Tor
11607 was started with a grossly inaccurate clock. Mitigates bug 22466;
11608 mitigation on 0.3.0.1-alpha.
11610 o Minor bugfixes (storage directories):
11611 - Always check for underflows in the cached storage directory usage.
11612 If the usage does underflow, re-calculate it. Also, avoid a
11613 separate underflow when the usage is not known. Fixes bug 22424;
11614 bugfix on 0.3.1.1-alpha.
11616 o Minor bugfixes (unit tests):
11617 - The unit tests now pass on systems where localhost is misconfigured
11618 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
11622 - Clarify the manpage for the (deprecated) torify script. Closes
11625 Changes in version 0.3.0.8 - 2017-06-08
11626 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
11627 remotely crash a hidden service with an assertion failure. Anyone
11628 running a hidden service should upgrade to this version, or to some
11629 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
11631 Tor 0.3.0.8 also includes fixes for several key management bugs
11632 that sometimes made relays unreliable, as well as several other
11633 bugfixes described below.
11635 o Major bugfixes (hidden service, relay, security, backport
11636 from 0.3.1.3-alpha):
11637 - Fix a remotely triggerable assertion failure when a hidden service
11638 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
11639 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
11640 - Fix a remotely triggerable assertion failure caused by receiving a
11641 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11642 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11645 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
11646 - When performing the v3 link handshake on a TLS connection, report
11647 that we have the x509 certificate that we actually used on that
11648 connection, even if we have changed certificates since that
11649 connection was first opened. Previously, we would claim to have
11650 used our most recent x509 link certificate, which would sometimes
11651 make the link handshake fail. Fixes one case of bug 22460; bugfix
11654 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
11655 - Regenerate link and authentication certificates whenever the key
11656 that signs them changes; also, regenerate link certificates
11657 whenever the signed key changes. Previously, these processes were
11658 only weakly coupled, and we relays could (for minutes to hours)
11659 wind up with an inconsistent set of keys and certificates, which
11660 other relays would not accept. Fixes two cases of bug 22460;
11661 bugfix on 0.3.0.1-alpha.
11662 - When sending an Ed25519 signing->link certificate in a CERTS cell,
11663 send the certificate that matches the x509 certificate that we
11664 used on the TLS connection. Previously, there was a race condition
11665 if the TLS context rotated after we began the TLS handshake but
11666 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
11669 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
11670 - Stop rejecting v3 hidden service descriptors because their size
11671 did not match an old padding rule. Fixes bug 22447; bugfix on
11674 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11675 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11676 December 2016 (of which ~126 were still functional) with a list of
11677 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11678 2017. Resolves ticket 21564.
11680 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
11681 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
11682 bug 22252; bugfix on 0.2.9.3-alpha.
11684 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
11685 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11686 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11688 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
11689 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
11690 months, and regenerate it when it is within one month of expiring.
11691 Previously, we had generated this certificate at startup with a
11692 ten-year lifetime, but that could lead to weird behavior when Tor
11693 was started with a grossly inaccurate clock. Mitigates bug 22466;
11694 mitigation on 0.3.0.1-alpha.
11696 o Minor bugfixes (memory leak, directory authority, backport from
11698 - When directory authorities reject a router descriptor due to
11699 keypinning, free the router descriptor rather than leaking the
11700 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11703 Changes in version 0.2.9.11 - 2017-06-08
11704 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
11705 remotely crash a hidden service with an assertion failure. Anyone
11706 running a hidden service should upgrade to this version, or to some
11707 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11708 are not affected by TROVE-2017-004.)
11710 Tor 0.2.9.11 also backports fixes for several key management bugs
11711 that sometimes made relays unreliable, as well as several other
11712 bugfixes described below.
11714 o Major bugfixes (hidden service, relay, security, backport
11715 from 0.3.1.3-alpha):
11716 - Fix a remotely triggerable assertion failure caused by receiving a
11717 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11718 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11721 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
11722 - When performing the v3 link handshake on a TLS connection, report
11723 that we have the x509 certificate that we actually used on that
11724 connection, even if we have changed certificates since that
11725 connection was first opened. Previously, we would claim to have
11726 used our most recent x509 link certificate, which would sometimes
11727 make the link handshake fail. Fixes one case of bug 22460; bugfix
11730 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11731 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11732 December 2016 (of which ~126 were still functional) with a list of
11733 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11734 2017. Resolves ticket 21564.
11736 o Minor features (future-proofing, backport from 0.3.0.7):
11737 - Tor no longer refuses to download microdescriptors or descriptors if
11738 they are listed as "published in the future". This change will
11739 eventually allow us to stop listing meaningful "published" dates
11740 in microdescriptor consensuses, and thereby allow us to reduce the
11741 resources required to download consensus diffs by over 50%.
11742 Implements part of ticket 21642; implements part of proposal 275.
11744 o Minor features (directory authorities, backport from 0.3.0.4-rc)
11745 - Directory authorities now reject relays running versions
11746 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
11747 suffer from bug 20499 and don't keep their consensus cache
11748 up-to-date. Resolves ticket 20509.
11750 o Minor features (geoip):
11751 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11754 o Minor bugfixes (control port, backport from 0.3.0.6):
11755 - The GETINFO extra-info/digest/<digest> command was broken because
11756 of a wrong base16 decode return value check, introduced when
11757 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
11759 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
11760 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11761 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11763 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
11764 - The getpid() system call is now permitted under the Linux seccomp2
11765 sandbox, to avoid crashing with versions of OpenSSL (and other
11766 libraries) that attempt to learn the process's PID by using the
11767 syscall rather than the VDSO code. Fixes bug 21943; bugfix
11770 o Minor bugfixes (memory leak, directory authority, backport
11771 from 0.3.1.2-alpha):
11772 - When directory authorities reject a router descriptor due to
11773 keypinning, free the router descriptor rather than leaking the
11774 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11776 Changes in version 0.2.8.14 - 2017-06-08
11777 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11778 remotely crash a hidden service with an assertion failure. Anyone
11779 running a hidden service should upgrade to this version, or to some
11780 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11781 are not affected by TROVE-2017-004.)
11783 o Major bugfixes (hidden service, relay, security):
11784 - Fix a remotely triggerable assertion failure caused by receiving a
11785 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11786 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11789 o Minor features (geoip):
11790 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11793 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
11794 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
11795 December 2016 (of which ~126 were still functional) with a list of
11796 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
11797 2017. Resolves ticket 21564.
11799 o Minor bugfixes (correctness):
11800 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11801 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11803 Changes in version 0.2.7.8 - 2017-06-08
11804 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
11805 remotely crash a hidden service with an assertion failure. Anyone
11806 running a hidden service should upgrade to this version, or to some
11807 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11808 are not affected by TROVE-2017-004.)
11810 o Major bugfixes (hidden service, relay, security):
11811 - Fix a remotely triggerable assertion failure caused by receiving a
11812 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11813 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11816 o Minor features (geoip):
11817 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11820 o Minor bugfixes (correctness):
11821 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11822 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11825 Changes in version 0.2.6.12 - 2017-06-08
11826 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
11827 remotely crash a hidden service with an assertion failure. Anyone
11828 running a hidden service should upgrade to this version, or to some
11829 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11830 are not affected by TROVE-2017-004.)
11832 o Major bugfixes (hidden service, relay, security):
11833 - Fix a remotely triggerable assertion failure caused by receiving a
11834 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11835 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11838 o Minor features (geoip):
11839 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11842 o Minor bugfixes (correctness):
11843 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11844 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11846 Changes in version 0.2.5.14 - 2017-06-08
11847 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
11848 remotely crash a hidden service with an assertion failure. Anyone
11849 running a hidden service should upgrade to this version, or to some
11850 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11851 are not affected by TROVE-2017-004.)
11853 o Major bugfixes (hidden service, relay, security):
11854 - Fix a remotely triggerable assertion failure caused by receiving a
11855 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11856 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11859 o Minor features (geoip):
11860 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11863 o Minor bugfixes (correctness):
11864 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11865 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11867 Changes in version 0.2.4.29 - 2017-06-08
11868 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
11869 remotely crash a hidden service with an assertion failure. Anyone
11870 running a hidden service should upgrade to this version, or to some
11871 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
11872 are not affected by TROVE-2017-004.)
11874 o Major bugfixes (hidden service, relay, security):
11875 - Fix a remotely triggerable assertion failure caused by receiving a
11876 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
11877 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
11880 o Minor features (geoip):
11881 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
11884 o Minor bugfixes (correctness):
11885 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
11886 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
11889 Changes in version 0.3.1.2-alpha - 2017-05-26
11890 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
11891 fixes a few bugs found while testing 0.3.1.1-alpha, including a
11892 memory corruption bug that affected relay stability.
11894 o Major bugfixes (crash, relay):
11895 - Fix a memory-corruption bug in relays that set MyFamily.
11896 Previously, they would double-free MyFamily elements when making
11897 the next descriptor or when changing their configuration. Fixes
11898 bug 22368; bugfix on 0.3.1.1-alpha.
11900 o Minor bugfixes (logging):
11901 - Log a better message when a directory authority replies to an
11902 upload with an unexpected status code. Fixes bug 11121; bugfix
11905 o Minor bugfixes (memory leak, directory authority):
11906 - When directory authorities reject a router descriptor due to
11907 keypinning, free the router descriptor rather than leaking the
11908 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
11911 Changes in version 0.3.1.1-alpha - 2017-05-22
11912 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
11913 reduces the bandwidth usage for Tor's directory protocol, adds some
11914 basic padding to resist netflow-based traffic analysis and to serve as
11915 the basis of other padding in the future, and adds rust support to the
11918 It also contains numerous other small features and improvements to
11919 security, correctness, and performance.
11921 Below are the changes since 0.3.0.7.
11923 o Major features (directory protocol):
11924 - Tor relays and authorities can now serve clients an abbreviated
11925 version of the consensus document, containing only the changes
11926 since an older consensus document that the client holds. Clients
11927 now request these documents when available. When both client and
11928 server use this new protocol, they will use far less bandwidth (up
11929 to 94% less) to keep the client's consensus up-to-date. Implements
11930 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
11931 - Tor can now compress directory traffic with lzma or with zstd
11932 compression algorithms, which can deliver better bandwidth
11933 performance. Because lzma is computationally expensive, it's only
11934 used for documents that can be compressed once and served many
11935 times. Support for these algorithms requires that tor is built
11936 with the libzstd and/or liblzma libraries available. Implements
11937 proposal 278; closes ticket 21662.
11938 - Relays now perform the more expensive compression operations, and
11939 consensus diff generation, in worker threads. This separation
11940 avoids delaying the main thread when a new consensus arrives.
11942 o Major features (experimental):
11943 - Tor can now build modules written in Rust. To turn this on, pass
11944 the "--enable-rust" flag to the configure script. It's not time to
11945 get excited yet: currently, there is no actual Rust functionality
11946 beyond some simple glue code, and a notice at startup to tell you
11947 that Rust is running. Still, we hope that programmers and
11948 packagers will try building Tor with Rust support, so that we can
11949 find issues and solve portability problems. Closes ticket 22106.
11951 o Major features (traffic analysis resistance):
11952 - Connections between clients and relays now send a padding cell in
11953 each direction every 1.5 to 9.5 seconds (tunable via consensus
11954 parameters). This padding will not resist specialized
11955 eavesdroppers, but it should be enough to make many ISPs' routine
11956 network flow logging less useful in traffic analysis against
11959 Padding is negotiated using Tor's link protocol, so both relays
11960 and clients must upgrade for this to take effect. Clients may
11961 still send padding despite the relay's version by setting
11962 ConnectionPadding 1 in torrc, and may disable padding by setting
11963 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
11964 users with the torrc option ReducedConnectionPadding. Implements
11965 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
11966 - Relays will publish 24 hour totals of padding and non-padding cell
11967 counts to their extra-info descriptors, unless PaddingStatistics 0
11968 is set in torrc. These 24 hour totals are also rounded to
11969 multiples of 10000.
11971 o Major bugfixes (connection usage):
11972 - We use NETINFO cells to try to determine if both relays involved
11973 in a connection will agree on the canonical status of that
11974 connection. We prefer the connections where this is the case for
11975 extend cells, and try to close connections where relays disagree
11976 on their canonical status early. Also, we now prefer the oldest
11977 valid connection for extend cells. These two changes should reduce
11978 the number of long-term connections that are kept open between
11979 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
11980 - Relays now log hourly statistics (look for
11981 "channel_check_for_duplicates" lines) on the total number of
11982 connections to other relays. If the number of connections per
11983 relay is unexpectedly large, this log message is at notice level.
11984 Otherwise it is at info.
11986 o Major bugfixes (entry guards):
11987 - Don't block bootstrapping when a primary bridge is offline and we
11988 can't get its descriptor. Fixes bug 22325; fixes one case of bug
11989 21969; bugfix on 0.3.0.3-alpha.
11991 o Major bugfixes (linux TPROXY support):
11992 - Fix a typo that had prevented TPROXY-based transparent proxying
11993 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
11994 Patch from "d4fq0fQAgoJ".
11996 o Minor features (security, windows):
11997 - Enable a couple of pieces of Windows hardening: one
11998 (HeapEnableTerminationOnCorruption) that has been on-by-default
11999 since Windows 8, and unavailable before Windows 7; and one
12000 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
12001 affect us, but shouldn't do any harm. Closes ticket 21953.
12003 o Minor features (config options):
12004 - Allow "%include" directives in torrc configuration files. These
12005 directives import the settings from other files, or from all the
12006 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
12007 - Make SAVECONF return an error when overwriting a torrc that has
12008 includes. Using SAVECONF with the FORCE option will allow it to
12009 overwrite torrc even if includes are used. Related to ticket 1922.
12010 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
12011 will work without the FORCE option. Related to ticket 1922.
12013 o Minor features (controller):
12014 - Warn the first time that a controller requests data in the long-
12015 deprecated 'GETINFO network-status' format. Closes ticket 21703.
12017 o Minor features (defaults):
12018 - The default value for UseCreateFast is now 0: clients which
12019 haven't yet received a consensus document will now use a proper
12020 ntor handshake to talk to their directory servers whenever they
12021 can. Closes ticket 21407.
12022 - Onion key rotation and expiry intervals are now defined as a
12023 network consensus parameter, per proposal 274. The default
12024 lifetime of an onion key is increased from 7 to 28 days. Old onion
12025 keys will expire after 7 days by default. This change will make
12026 consensus diffs much smaller, and save significant bandwidth.
12027 Closes ticket 21641.
12029 o Minor features (fallback directory list):
12030 - Update the fallback directory mirror whitelist and blacklist based
12031 on operator emails. Closes task 21121.
12032 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
12033 December 2016 (of which ~126 were still functional) with a list of
12034 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
12035 2017. Resolves ticket 21564.
12037 o Minor features (hidden services, logging):
12038 - Log a message when a hidden service descriptor has fewer
12039 introduction points than specified in
12040 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
12041 - Log a message when a hidden service reaches its introduction point
12042 circuit limit, and when that limit is reset. Follow up to ticket
12043 21594; closes ticket 21622.
12044 - Warn user if multiple entries in EntryNodes and at least one
12045 HiddenService are used together. Pinning EntryNodes along with a
12046 hidden service can be possibly harmful; for instance see ticket
12047 14917 or 21155. Closes ticket 21155.
12049 o Minor features (linux seccomp2 sandbox):
12050 - We now have a document storage backend compatible with the Linux
12051 seccomp2 sandbox. This backend is used for consensus documents and
12052 diffs between them; in the long term, we'd like to use it for
12053 unparseable directory material too. Closes ticket 21645
12054 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
12055 from 1MB to 16MB. This was necessary with the glibc allocator in
12056 order to allow worker threads to allocate more memory -- which in
12057 turn is necessary because of our new use of worker threads for
12058 compression. Closes ticket 22096.
12060 o Minor features (logging):
12061 - Log files are no longer created world-readable by default.
12062 (Previously, most distributors would store the logs in a non-
12063 world-readable location to prevent inappropriate access. This
12064 change is an extra precaution.) Closes ticket 21729; patch
12067 o Minor features (performance):
12068 - Our Keccak (SHA-3) implementation now accesses memory more
12069 efficiently, especially on little-endian systems. Closes
12071 - Add an O(1) implementation of channel_find_by_global_id(), to
12072 speed some controller functions.
12074 o Minor features (relay, configuration):
12075 - The MyFamily option may now be repeated as many times as desired,
12076 for relays that want to configure large families. Closes ticket
12077 4998; patch by Daniel Pinto.
12079 o Minor features (safety):
12080 - Add an explicit check to extrainfo_parse_entry_from_string() for
12081 NULL inputs. We don't believe this can actually happen, but it may
12082 help silence a warning from the Clang analyzer. Closes
12085 o Minor features (testing):
12086 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
12087 When Tor is compiled with this option, we disable a number of
12088 redundant memory-safety failsafes that are intended to stop bugs
12089 from becoming security issues. This makes it easier to hunt for
12090 bugs that would be security issues without the failsafes turned
12091 on. Closes ticket 21439.
12092 - Add a general event-tracing instrumentation support to Tor. This
12093 subsystem will enable developers and researchers to add fine-
12094 grained instrumentation to their Tor instances, for use when
12095 examining Tor network performance issues. There are no trace
12096 events yet, and event-tracing is off by default unless enabled at
12097 compile time. Implements ticket 13802.
12098 - Improve our version parsing tests: add tests for typical version
12099 components, add tests for invalid versions, including numeric
12100 range and non-numeric prefixes. Unit tests 21278, 21450, and
12101 21507. Partially implements 21470.
12103 o Minor bugfixes (bandwidth accounting):
12104 - Roll over monthly accounting at the configured hour and minute,
12105 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
12106 Found by Andrey Karpov with PVS-Studio.
12108 o Minor bugfixes (code correctness):
12109 - Accurately identify client connections by their lack of peer
12110 authentication. This means that we bail out earlier if asked to
12111 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
12114 o Minor bugfixes (configuration):
12115 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
12116 bug 22252; bugfix on 0.2.9.3-alpha.
12118 o Minor bugfixes (connection lifespan):
12119 - Allow more control over how long TLS connections are kept open:
12120 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
12121 single option called CircuitsAvailableTimeout. Also, allow the
12122 consensus to control the default values for both this preference
12123 and the lifespan of relay-to-relay connections. Fixes bug 17592;
12124 bugfix on 0.2.5.5-alpha.
12125 - Increase the initial circuit build timeout testing frequency, to
12126 help ensure that ReducedConnectionPadding clients finish learning
12127 a timeout before their orconn would expire. The initial testing
12128 rate was set back in the days of TAP and before the Tor Browser
12129 updater, when we had to be much more careful about new clients
12130 making lots of circuits. With this change, a circuit build timeout
12131 is learned in about 15-20 minutes, instead of 100-120 minutes.
12133 o Minor bugfixes (controller):
12134 - GETINFO onions/current and onions/detached no longer respond with
12135 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
12136 - Trigger HS descriptor events on the control port when the client
12137 fails to pick a hidden service directory for a hidden service.
12138 This can happen if all the hidden service directories are in
12139 ExcludeNodes, or they have all been queried within the last 15
12140 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
12142 o Minor bugfixes (directory authority):
12143 - When rejecting a router descriptor for running an obsolete version
12144 of Tor without ntor support, warn about the obsolete tor version,
12145 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
12146 - Prevent the shared randomness subsystem from asserting when
12147 initialized by a bridge authority with an incomplete configuration
12148 file. Fixes bug 21586; bugfix on 0.2.9.8.
12150 o Minor bugfixes (exit-side DNS):
12151 - Fix an untriggerable assertion that checked the output of a
12152 libevent DNS error, so that the assertion actually behaves as
12153 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
12154 Karpov using PVS-Studio.
12156 o Minor bugfixes (fallback directories):
12157 - Make the usage example in updateFallbackDirs.py actually work, and
12158 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
12159 - Decrease the guard flag average required to be a fallback. This
12160 allows us to keep relays that have their guard flag removed when
12161 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
12162 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
12163 bugfix on 0.2.8.1-alpha.
12164 - Make sure fallback directory mirrors have the same address, port,
12165 and relay identity key for at least 30 days before they are
12166 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
12168 o Minor bugfixes (hidden services):
12169 - Stop printing a cryptic warning when a hidden service gets a
12170 request to connect to a virtual port that it hasn't configured.
12171 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
12172 - Simplify hidden service descriptor creation by using an existing
12173 flag to check if an introduction point is established. Fixes bug
12174 21599; bugfix on 0.2.7.2-alpha.
12176 o Minor bugfixes (memory leak):
12177 - Fix a small memory leak at exit from the backtrace handler code.
12178 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
12180 o Minor bugfixes (protocol, logging):
12181 - Downgrade a log statement about unexpected relay cells from "bug"
12182 to "protocol warning", because there is at least one use case
12183 where it can be triggered by a buggy tor implementation. Fixes bug
12184 21293; bugfix on 0.1.1.14-alpha.
12186 o Minor bugfixes (testing):
12187 - Use unbuffered I/O for utility functions around the
12188 process_handle_t type. This fixes unit test failures reported on
12189 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
12190 - Make display of captured unit test log messages consistent. Fixes
12191 bug 21510; bugfix on 0.2.9.3-alpha.
12192 - Make test-network.sh always call chutney's test-network.sh.
12193 Previously, this only worked on systems which had bash installed,
12194 due to some bash-specific code in the script. Fixes bug 19699;
12195 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
12197 o Minor bugfixes (voting consistency):
12198 - Reject version numbers with non-numeric prefixes (such as +, -, or
12199 whitespace). Disallowing whitespace prevents differential version
12200 parsing between POSIX-based and Windows platforms. Fixes bug 21507
12201 and part of 21508; bugfix on 0.0.8pre1.
12203 o Minor bugfixes (windows, relay):
12204 - Resolve "Failure from drain_fd: No error" warnings on Windows
12205 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
12207 o Code simplification and refactoring:
12208 - Break up the 630-line function connection_dir_client_reached_eof()
12209 into a dozen smaller functions. This change should help
12210 maintainability and readability of the client directory code.
12211 - Isolate our use of the openssl headers so that they are only
12212 included from our crypto wrapper modules, and from tests that
12213 examine those modules' internals. Closes ticket 21841.
12214 - Simplify our API to launch directory requests, making it more
12215 extensible and less error-prone. Now it's easier to add extra
12216 headers to directory requests. Closes ticket 21646.
12217 - Our base64 decoding functions no longer overestimate the output
12218 space that they need when parsing unpadded inputs. Closes
12220 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
12221 Resolves ticket 22213.
12222 - The logic that directory caches use to spool request to clients,
12223 serving them one part at a time so as not to allocate too much
12224 memory, has been refactored for consistency. Previously there was
12225 a separate spooling implementation per type of spoolable data. Now
12226 there is one common spooling implementation, with extensible data
12227 types. Closes ticket 21651.
12228 - Tor's compression module now supports multiple backends. Part of
12229 the implementation for proposal 278; closes ticket 21663.
12232 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
12233 Closes ticket 21873.
12234 - Correct documentation about the default DataDirectory value.
12235 Closes ticket 21151.
12236 - Document the default behavior of NumEntryGuards and
12237 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
12239 - Document key=value pluggable transport arguments for Bridge lines
12240 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
12241 - Note that bandwidth-limiting options don't affect TCP headers or
12242 DNS. Closes ticket 17170.
12244 o Removed features (configuration options, all in ticket 22060):
12245 - These configuration options are now marked Obsolete, and no longer
12246 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
12247 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
12248 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
12249 in 0.2.9.2-alpha and have now been removed. The previous default
12250 behavior is now always chosen; the previous (less secure) non-
12251 default behavior is now unavailable.
12252 - CloseHSClientCircuitsImmediatelyOnTimeout and
12253 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
12254 0.2.9.2-alpha and now have been removed. HS circuits never close
12255 on circuit build timeout; they have a longer timeout period.
12256 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
12257 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
12258 (and others) to configure listen-only and advertise-only addresses.
12260 o Removed features (tools):
12261 - We've removed the tor-checkkey tool from src/tools. Long ago, we
12262 used it to help people detect RSA keys that were generated by
12263 versions of Debian affected by CVE-2008-0166. But those keys have
12264 been out of circulation for ages, and this tool is no longer
12265 required. Closes ticket 21842.
12268 Changes in version 0.3.0.7 - 2017-05-15
12269 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
12270 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
12271 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
12272 clients are not affected.
12274 o Major bugfixes (hidden service directory, security):
12275 - Fix an assertion failure in the hidden service directory code, which
12276 could be used by an attacker to remotely cause a Tor relay process to
12277 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
12278 should upgrade. This security issue is tracked as TROVE-2017-002.
12279 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
12282 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
12285 o Minor features (future-proofing):
12286 - Tor no longer refuses to download microdescriptors or descriptors
12287 if they are listed as "published in the future". This change will
12288 eventually allow us to stop listing meaningful "published" dates
12289 in microdescriptor consensuses, and thereby allow us to reduce the
12290 resources required to download consensus diffs by over 50%.
12291 Implements part of ticket 21642; implements part of proposal 275.
12293 o Minor bugfixes (Linux seccomp2 sandbox):
12294 - The getpid() system call is now permitted under the Linux seccomp2
12295 sandbox, to avoid crashing with versions of OpenSSL (and other
12296 libraries) that attempt to learn the process's PID by using the
12297 syscall rather than the VDSO code. Fixes bug 21943; bugfix
12301 Changes in version 0.3.0.6 - 2017-04-26
12302 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
12304 With the 0.3.0 series, clients and relays now use Ed25519 keys to
12305 authenticate their link connections to relays, rather than the old
12306 RSA1024 keys that they used before. (Circuit crypto has been
12307 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
12308 the guard selection and replacement algorithm to behave more robustly
12309 in the presence of unreliable networks, and to resist guard-
12312 This series also includes numerous other small features and bugfixes,
12313 along with more groundwork for the upcoming hidden-services revamp.
12315 Per our stable release policy, we plan to support the Tor 0.3.0
12316 release series for at least the next nine months, or for three months
12317 after the first stable release of the 0.3.1 series: whichever is
12318 longer. If you need a release with long-term support, we recommend
12319 that you stay with the 0.2.9 series.
12321 Below are the changes since 0.3.0.5-rc. For a list of all changes
12322 since 0.2.9, see the ReleaseNotes file.
12324 o Minor features (geoip):
12325 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
12328 o Minor bugfixes (control port):
12329 - The GETINFO extra-info/digest/<digest> command was broken because
12330 of a wrong base16 decode return value check, introduced when
12331 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
12333 o Minor bugfixes (crash prevention):
12334 - Fix a (currently untriggerable, but potentially dangerous) crash
12335 bug when base32-encoding inputs whose sizes are not a multiple of
12336 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
12339 Changes in version 0.3.0.5-rc - 2017-04-05
12340 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
12341 0.3.0 release series.
12343 This is the second release candidate in the Tor 0.3.0 series, and has
12344 much fewer changes than the first. If we find no new bugs or
12345 regressions here, the first stable 0.3.0 release will be nearly
12348 o Major bugfixes (crash, directory connections):
12349 - Fix a rare crash when sending a begin cell on a circuit whose
12350 linked directory connection had already been closed. Fixes bug
12351 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
12353 o Major bugfixes (guard selection):
12354 - Fix a guard selection bug where Tor would refuse to bootstrap in
12355 some cases if the user swapped a bridge for another bridge in
12356 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
12357 Reported by "torvlnt33r".
12359 o Minor features (geoip):
12360 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
12363 o Minor bugfix (compilation):
12364 - Fix a warning when compiling hs_service.c. Previously, it had no
12365 exported symbols when compiled for libor.a, resulting in a
12366 compilation warning from clang. Fixes bug 21825; bugfix
12369 o Minor bugfixes (hidden services):
12370 - Make hidden services check for failed intro point connections,
12371 even when they have exceeded their intro point creation limit.
12372 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
12373 - Make hidden services with 8 to 10 introduction points check for
12374 failed circuits immediately after startup. Previously, they would
12375 wait for 5 minutes before performing their first checks. Fixes bug
12376 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
12378 o Minor bugfixes (memory leaks):
12379 - Fix a memory leak when using GETCONF on a port option. Fixes bug
12380 21682; bugfix on 0.3.0.3-alpha.
12382 o Minor bugfixes (relay):
12383 - Avoid a double-marked-circuit warning that could happen when we
12384 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
12387 o Minor bugfixes (tests):
12388 - Run the entry_guard_parse_from_state_full() test with the time set
12389 to a specific date. (The guard state that this test was parsing
12390 contained guards that had expired since the test was first
12391 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
12394 - Update the description of the directory server options in the
12395 manual page, to clarify that a relay no longer needs to set
12396 DirPort in order to be a directory cache. Closes ticket 21720.
12400 Changes in version 0.2.8.13 - 2017-03-03
12401 Tor 0.2.8.13 backports a security fix from later Tor
12402 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
12403 this release, if for some reason they cannot upgrade to a later
12404 release series, and if they build Tor with the --enable-expensive-hardening
12407 Note that support for Tor 0.2.8.x is ending next year: we will not issue
12408 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
12409 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12411 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12412 - Fix an integer underflow bug when comparing malformed Tor
12413 versions. This bug could crash Tor when built with
12414 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12415 0.2.9.8, which were built with -ftrapv by default. In other cases
12416 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12417 on 0.0.8pre1. Found by OSS-Fuzz.
12419 o Minor features (geoip):
12420 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12424 Changes in version 0.2.7.7 - 2017-03-03
12425 Tor 0.2.7.7 backports a number of security fixes from later Tor
12426 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
12427 this release, if for some reason they cannot upgrade to a later
12430 Note that support for Tor 0.2.7.x is ending this year: we will not issue
12431 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
12432 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12434 o Directory authority changes (backport from 0.2.8.5-rc):
12435 - Urras is no longer a directory authority. Closes ticket 19271.
12437 o Directory authority changes (backport from 0.2.9.2-alpha):
12438 - The "Tonga" bridge authority has been retired; the new bridge
12439 authority is "Bifroest". Closes tickets 19728 and 19690.
12441 o Directory authority key updates (backport from 0.2.8.1-alpha):
12442 - Update the V3 identity key for the dannenberg directory authority:
12443 it was changed on 18 November 2015. Closes task 17906. Patch
12446 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12447 - Fix a bug in parsing that could cause clients to read a single
12448 byte past the end of an allocated region. This bug could be used
12449 to cause hardened clients (built with --enable-expensive-hardening)
12450 to crash if they tried to visit a hostile hidden service. Non-
12451 hardened clients are only affected depending on the details of
12452 their platform's memory allocator. Fixes bug 21018; bugfix on
12453 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12454 2016-12-002 and as CVE-2016-1254.
12456 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12457 - Stop a crash that could occur when a client running with DNSPort
12458 received a query with multiple address types, and the first
12459 address type was not supported. Found and fixed by Scott Dial.
12460 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12461 - Prevent a class of security bugs caused by treating the contents
12462 of a buffer chunk as if they were a NUL-terminated string. At
12463 least one such bug seems to be present in all currently used
12464 versions of Tor, and would allow an attacker to remotely crash
12465 most Tor instances, especially those compiled with extra compiler
12466 hardening. With this defense in place, such bugs can't crash Tor,
12467 though we should still fix them as they occur. Closes ticket
12468 20384 (TROVE-2016-10-001).
12470 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12471 - Avoid a difficult-to-trigger heap corruption attack when extending
12472 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12473 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12474 Reported by Guido Vranken.
12476 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12477 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12478 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12480 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12481 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12482 pointer to the previous (uninitialized) key value. The impact here
12483 should be limited to a difficult-to-trigger crash, if OpenSSL is
12484 running an engine that makes key generation failures possible, or
12485 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12486 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12489 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12490 - Fix an integer underflow bug when comparing malformed Tor
12491 versions. This bug could crash Tor when built with
12492 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12493 0.2.9.8, which were built with -ftrapv by default. In other cases
12494 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12495 on 0.0.8pre1. Found by OSS-Fuzz.
12497 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12498 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12499 zero size. Check size argument to memwipe() for underflow. Fixes
12500 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12503 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12504 - Make Tor survive errors involving connections without a
12505 corresponding event object. Previously we'd fail with an
12506 assertion; now we produce a log message. Related to bug 16248.
12508 o Minor features (geoip):
12509 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12513 Changes in version 0.2.6.11 - 2017-03-03
12514 Tor 0.2.6.11 backports a number of security fixes from later Tor
12515 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
12516 this release, if for some reason they cannot upgrade to a later
12519 Note that support for Tor 0.2.6.x is ending this year: we will not issue
12520 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
12521 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12523 o Directory authority changes (backport from 0.2.8.5-rc):
12524 - Urras is no longer a directory authority. Closes ticket 19271.
12526 o Directory authority changes (backport from 0.2.9.2-alpha):
12527 - The "Tonga" bridge authority has been retired; the new bridge
12528 authority is "Bifroest". Closes tickets 19728 and 19690.
12530 o Directory authority key updates (backport from 0.2.8.1-alpha):
12531 - Update the V3 identity key for the dannenberg directory authority:
12532 it was changed on 18 November 2015. Closes task 17906. Patch
12535 o Major features (security fixes, backport from 0.2.9.4-alpha):
12536 - Prevent a class of security bugs caused by treating the contents
12537 of a buffer chunk as if they were a NUL-terminated string. At
12538 least one such bug seems to be present in all currently used
12539 versions of Tor, and would allow an attacker to remotely crash
12540 most Tor instances, especially those compiled with extra compiler
12541 hardening. With this defense in place, such bugs can't crash Tor,
12542 though we should still fix them as they occur. Closes ticket
12543 20384 (TROVE-2016-10-001).
12545 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12546 - Fix a bug in parsing that could cause clients to read a single
12547 byte past the end of an allocated region. This bug could be used
12548 to cause hardened clients (built with --enable-expensive-hardening)
12549 to crash if they tried to visit a hostile hidden service. Non-
12550 hardened clients are only affected depending on the details of
12551 their platform's memory allocator. Fixes bug 21018; bugfix on
12552 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12553 2016-12-002 and as CVE-2016-1254.
12555 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12556 - Stop a crash that could occur when a client running with DNSPort
12557 received a query with multiple address types, and the first
12558 address type was not supported. Found and fixed by Scott Dial.
12559 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12561 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12562 - Fix an error that could cause us to read 4 bytes before the
12563 beginning of an openssl string. This bug could be used to cause
12564 Tor to crash on systems with unusual malloc implementations, or
12565 systems with unusual hardening installed. Fixes bug 17404; bugfix
12568 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12569 - Avoid a difficult-to-trigger heap corruption attack when extending
12570 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12571 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12572 Reported by Guido Vranken.
12574 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12575 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12576 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12578 o Major bugfixes (guard selection, backport from 0.2.7.6):
12579 - Actually look at the Guard flag when selecting a new directory
12580 guard. When we implemented the directory guard design, we
12581 accidentally started treating all relays as if they have the Guard
12582 flag during guard selection, leading to weaker anonymity and worse
12583 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12586 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12587 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12588 pointer to the previous (uninitialized) key value. The impact here
12589 should be limited to a difficult-to-trigger crash, if OpenSSL is
12590 running an engine that makes key generation failures possible, or
12591 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12592 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12595 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12596 - Fix an integer underflow bug when comparing malformed Tor
12597 versions. This bug could crash Tor when built with
12598 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12599 0.2.9.8, which were built with -ftrapv by default. In other cases
12600 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12601 on 0.0.8pre1. Found by OSS-Fuzz.
12603 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12604 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12605 zero size. Check size argument to memwipe() for underflow. Fixes
12606 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12609 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12610 - Make Tor survive errors involving connections without a
12611 corresponding event object. Previously we'd fail with an
12612 assertion; now we produce a log message. Related to bug 16248.
12614 o Minor features (geoip):
12615 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12618 o Minor bugfixes (compilation, backport from 0.2.7.6):
12619 - Fix a compilation warning with Clang 3.6: Do not check the
12620 presence of an address which can never be NULL. Fixes bug 17781.
12623 Changes in version 0.2.5.13 - 2017-03-03
12624 Tor 0.2.5.13 backports a number of security fixes from later Tor
12625 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
12626 this release, if for some reason they cannot upgrade to a later
12629 Note that support for Tor 0.2.5.x is ending next year: we will not issue
12630 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
12631 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
12633 o Directory authority changes (backport from 0.2.8.5-rc):
12634 - Urras is no longer a directory authority. Closes ticket 19271.
12636 o Directory authority changes (backport from 0.2.9.2-alpha):
12637 - The "Tonga" bridge authority has been retired; the new bridge
12638 authority is "Bifroest". Closes tickets 19728 and 19690.
12640 o Directory authority key updates (backport from 0.2.8.1-alpha):
12641 - Update the V3 identity key for the dannenberg directory authority:
12642 it was changed on 18 November 2015. Closes task 17906. Patch
12645 o Major features (security fixes, backport from 0.2.9.4-alpha):
12646 - Prevent a class of security bugs caused by treating the contents
12647 of a buffer chunk as if they were a NUL-terminated string. At
12648 least one such bug seems to be present in all currently used
12649 versions of Tor, and would allow an attacker to remotely crash
12650 most Tor instances, especially those compiled with extra compiler
12651 hardening. With this defense in place, such bugs can't crash Tor,
12652 though we should still fix them as they occur. Closes ticket
12653 20384 (TROVE-2016-10-001).
12655 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12656 - Fix a bug in parsing that could cause clients to read a single
12657 byte past the end of an allocated region. This bug could be used
12658 to cause hardened clients (built with --enable-expensive-hardening)
12659 to crash if they tried to visit a hostile hidden service. Non-
12660 hardened clients are only affected depending on the details of
12661 their platform's memory allocator. Fixes bug 21018; bugfix on
12662 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12663 2016-12-002 and as CVE-2016-1254.
12665 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
12666 - Stop a crash that could occur when a client running with DNSPort
12667 received a query with multiple address types, and the first
12668 address type was not supported. Found and fixed by Scott Dial.
12669 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12671 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12672 - Fix an error that could cause us to read 4 bytes before the
12673 beginning of an openssl string. This bug could be used to cause
12674 Tor to crash on systems with unusual malloc implementations, or
12675 systems with unusual hardening installed. Fixes bug 17404; bugfix
12678 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12679 - Avoid a difficult-to-trigger heap corruption attack when extending
12680 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12681 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12682 Reported by Guido Vranken.
12684 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12685 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12686 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12688 o Major bugfixes (guard selection, backport from 0.2.7.6):
12689 - Actually look at the Guard flag when selecting a new directory
12690 guard. When we implemented the directory guard design, we
12691 accidentally started treating all relays as if they have the Guard
12692 flag during guard selection, leading to weaker anonymity and worse
12693 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12696 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12697 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12698 pointer to the previous (uninitialized) key value. The impact here
12699 should be limited to a difficult-to-trigger crash, if OpenSSL is
12700 running an engine that makes key generation failures possible, or
12701 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12702 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12705 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12706 - Fix an integer underflow bug when comparing malformed Tor
12707 versions. This bug could crash Tor when built with
12708 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12709 0.2.9.8, which were built with -ftrapv by default. In other cases
12710 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12711 on 0.0.8pre1. Found by OSS-Fuzz.
12713 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12714 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12715 zero size. Check size argument to memwipe() for underflow. Fixes
12716 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12719 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12720 - Make Tor survive errors involving connections without a
12721 corresponding event object. Previously we'd fail with an
12722 assertion; now we produce a log message. Related to bug 16248.
12724 o Minor features (geoip):
12725 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12728 o Minor bugfixes (compilation, backport from 0.2.7.6):
12729 - Fix a compilation warning with Clang 3.6: Do not check the
12730 presence of an address which can never be NULL. Fixes bug 17781.
12732 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
12733 - Check for failures from crypto_early_init, and refuse to continue.
12734 A previous typo meant that we could keep going with an
12735 uninitialized crypto library, and would have OpenSSL initialize
12736 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12737 when implementing ticket 4900. Patch by "teor".
12739 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12740 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12741 a client authorized hidden service. Fixes bug 15823; bugfix
12745 Changes in version 0.2.4.28 - 2017-03-03
12746 Tor 0.2.4.28 backports a number of security fixes from later Tor
12747 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
12748 this release, if for some reason they cannot upgrade to a later
12751 Note that support for Tor 0.2.4.x is ending soon: we will not issue
12752 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
12753 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
12755 o Directory authority changes (backport from 0.2.8.5-rc):
12756 - Urras is no longer a directory authority. Closes ticket 19271.
12758 o Directory authority changes (backport from 0.2.9.2-alpha):
12759 - The "Tonga" bridge authority has been retired; the new bridge
12760 authority is "Bifroest". Closes tickets 19728 and 19690.
12762 o Directory authority key updates (backport from 0.2.8.1-alpha):
12763 - Update the V3 identity key for the dannenberg directory authority:
12764 it was changed on 18 November 2015. Closes task 17906. Patch
12767 o Major features (security fixes, backport from 0.2.9.4-alpha):
12768 - Prevent a class of security bugs caused by treating the contents
12769 of a buffer chunk as if they were a NUL-terminated string. At
12770 least one such bug seems to be present in all currently used
12771 versions of Tor, and would allow an attacker to remotely crash
12772 most Tor instances, especially those compiled with extra compiler
12773 hardening. With this defense in place, such bugs can't crash Tor,
12774 though we should still fix them as they occur. Closes ticket
12775 20384 (TROVE-2016-10-001).
12777 o Major bugfixes (parsing, security, backport from 0.2.9.8):
12778 - Fix a bug in parsing that could cause clients to read a single
12779 byte past the end of an allocated region. This bug could be used
12780 to cause hardened clients (built with --enable-expensive-hardening)
12781 to crash if they tried to visit a hostile hidden service. Non-
12782 hardened clients are only affected depending on the details of
12783 their platform's memory allocator. Fixes bug 21018; bugfix on
12784 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
12785 2016-12-002 and as CVE-2016-1254.
12787 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
12788 - Fix an error that could cause us to read 4 bytes before the
12789 beginning of an openssl string. This bug could be used to cause
12790 Tor to crash on systems with unusual malloc implementations, or
12791 systems with unusual hardening installed. Fixes bug 17404; bugfix
12794 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
12795 - Avoid a difficult-to-trigger heap corruption attack when extending
12796 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12797 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12798 Reported by Guido Vranken.
12800 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
12801 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12802 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12804 o Major bugfixes (guard selection, backport from 0.2.7.6):
12805 - Actually look at the Guard flag when selecting a new directory
12806 guard. When we implemented the directory guard design, we
12807 accidentally started treating all relays as if they have the Guard
12808 flag during guard selection, leading to weaker anonymity and worse
12809 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12812 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
12813 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12814 pointer to the previous (uninitialized) key value. The impact here
12815 should be limited to a difficult-to-trigger crash, if OpenSSL is
12816 running an engine that makes key generation failures possible, or
12817 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12818 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12821 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
12822 - Fix an integer underflow bug when comparing malformed Tor
12823 versions. This bug could crash Tor when built with
12824 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12825 0.2.9.8, which were built with -ftrapv by default. In other cases
12826 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12827 on 0.0.8pre1. Found by OSS-Fuzz.
12829 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
12830 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12831 zero size. Check size argument to memwipe() for underflow. Fixes
12832 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12835 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
12836 - Make Tor survive errors involving connections without a
12837 corresponding event object. Previously we'd fail with an
12838 assertion; now we produce a log message. Related to bug 16248.
12840 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
12841 - Make it harder for attackers to overload hidden services with
12842 introductions, by blocking multiple introduction requests on the
12843 same circuit. Resolves ticket 15515.
12845 o Minor features (geoip):
12846 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12849 o Minor bugfixes (compilation, backport from 0.2.7.6):
12850 - Fix a compilation warning with Clang 3.6: Do not check the
12851 presence of an address which can never be NULL. Fixes bug 17781.
12853 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12854 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12855 a client authorized hidden service. Fixes bug 15823; bugfix
12859 Changes in version 0.3.0.4-rc - 2017-03-01
12860 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
12861 0.3.0 release series, and introduces a few reliability features to
12862 keep them from coming back.
12864 This is the first release candidate in the Tor 0.3.0 series. If we
12865 find no new bugs or regressions here, the first stable 0.3.0 release
12866 will be nearly identical to it.
12868 o Major bugfixes (bridges):
12869 - When the same bridge is configured multiple times with the same
12870 identity, but at different address:port combinations, treat those
12871 bridge instances as separate guards. This fix restores the ability
12872 of clients to configure the same bridge with multiple pluggable
12873 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
12875 o Major bugfixes (hidden service directory v3):
12876 - Stop crashing on a failed v3 hidden service descriptor lookup
12877 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
12879 o Major bugfixes (parsing):
12880 - When parsing a malformed content-length field from an HTTP
12881 message, do not read off the end of the buffer. This bug was a
12882 potential remote denial-of-service attack against Tor clients and
12883 relays. A workaround was released in October 2016, to prevent this
12884 bug from crashing Tor. This is a fix for the underlying issue,
12885 which should no longer matter (if you applied the earlier patch).
12886 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
12887 using AFL (http://lcamtuf.coredump.cx/afl/).
12888 - Fix an integer underflow bug when comparing malformed Tor
12889 versions. This bug could crash Tor when built with
12890 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
12891 0.2.9.8, which were built with -ftrapv by default. In other cases
12892 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
12893 on 0.0.8pre1. Found by OSS-Fuzz.
12895 o Minor feature (protocol versioning):
12896 - Add new protocol version for proposal 224. HSIntro now advertises
12897 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
12899 o Minor features (directory authorities):
12900 - Directory authorities now reject descriptors that claim to be
12901 malformed versions of Tor. Helps prevent exploitation of
12903 - Reject version numbers with components that exceed INT32_MAX.
12904 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
12905 Fixes bug 21450; bugfix on 0.0.8pre1.
12906 - Directory authorities now reject relays running versions
12907 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
12908 suffer from bug 20499 and don't keep their consensus cache
12909 up-to-date. Resolves ticket 20509.
12911 o Minor features (geoip):
12912 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
12915 o Minor features (reliability, crash):
12916 - Try better to detect problems in buffers where they might grow (or
12917 think they have grown) over 2 GB in size. Diagnostic for
12920 o Minor features (testing):
12921 - During 'make test-network-all', if tor logs any warnings, ask
12922 chutney to output them. Requires a recent version of chutney with
12923 the 21572 patch. Implements 21570.
12925 o Minor bugfixes (certificate expiration time):
12926 - Avoid using link certificates that don't become valid till some
12927 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
12929 o Minor bugfixes (code correctness):
12930 - Repair a couple of (unreachable or harmless) cases of the risky
12931 comparison-by-subtraction pattern that caused bug 21278.
12932 - Remove a redundant check for the UseEntryGuards option from the
12933 options_transition_affects_guards() function. Fixes bug 21492;
12934 bugfix on 0.3.0.1-alpha.
12936 o Minor bugfixes (directory mirrors):
12937 - Allow relays to use directory mirrors without a DirPort: these
12938 relays need to be contacted over their ORPorts using a begindir
12939 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
12940 - Clarify the message logged when a remote relay is unexpectedly
12941 missing an ORPort or DirPort: users were confusing this with a
12942 local port. Fixes another case of bug 20711; bugfix
12945 o Minor bugfixes (guards):
12946 - Don't warn about a missing guard state on timeout-measurement
12947 circuits: they aren't supposed to be using guards. Fixes an
12948 instance of bug 21007; bugfix on 0.3.0.1-alpha.
12949 - Silence a BUG() warning when attempting to use a guard whose
12950 descriptor we don't know, and make this scenario less likely to
12951 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
12953 o Minor bugfixes (hidden service):
12954 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
12955 cells. Previously, we were using sizeof() on a pointer, instead of
12956 the real destination buffer. Fortunately, that value was only used
12957 to double-check that there was enough room--which was already
12958 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
12960 o Minor bugfixes (testing):
12961 - Fix Raspbian build issues related to missing socket errno in
12962 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
12964 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
12965 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
12966 - Use bash in src/test/test-network.sh. This ensures we reliably
12967 call chutney's newer tools/test-network.sh when available. Fixes
12968 bug 21562; bugfix on 0.2.9.1-alpha.
12971 - Small fixes to the fuzzing documentation. Closes ticket 21472.
12974 Changes in version 0.2.9.10 - 2017-03-01
12975 Tor 0.2.9.10 backports a security fix from later Tor release. It also
12976 includes fixes for some major issues affecting directory authorities,
12977 LibreSSL compatibility, and IPv6 correctness.
12979 The Tor 0.2.9.x release series is now marked as a long-term-support
12980 series. We intend to backport security fixes to 0.2.9.x until at
12981 least January of 2020.
12983 o Major bugfixes (directory authority, 0.3.0.3-alpha):
12984 - During voting, when marking a relay as a probable sybil, do not
12985 clear its BadExit flag: sybils can still be bad in other ways
12986 too. (We still clear the other flags.) Fixes bug 21108; bugfix
12989 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
12990 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
12991 any IPv6 addresses. Instead, only reject a port over IPv6 if the
12992 exit policy rejects that port on more than an IPv6 /16 of
12993 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
12994 which rejected a relay's own IPv6 address by default. Fixes bug
12995 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
12997 o Major bugfixes (parsing, also in 0.3.0.4-rc):
12998 - Fix an integer underflow bug when comparing malformed Tor
12999 versions. This bug could crash Tor when built with
13000 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
13001 0.2.9.8, which were built with -ftrapv by default. In other cases
13002 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
13003 on 0.0.8pre1. Found by OSS-Fuzz.
13005 o Minor features (directory authorities, also in 0.3.0.4-rc):
13006 - Directory authorities now reject descriptors that claim to be
13007 malformed versions of Tor. Helps prevent exploitation of
13009 - Reject version numbers with components that exceed INT32_MAX.
13010 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
13011 Fixes bug 21450; bugfix on 0.0.8pre1.
13013 o Minor features (geoip):
13014 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
13017 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
13018 - Autoconf now checks to determine if OpenSSL structures are opaque,
13019 instead of explicitly checking for OpenSSL version numbers. Part
13021 - Support building with recent LibreSSL code that uses opaque
13022 structures. Closes ticket 21359.
13024 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
13025 - Repair a couple of (unreachable or harmless) cases of the risky
13026 comparison-by-subtraction pattern that caused bug 21278.
13028 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
13029 - The tor-resolve command line tool now rejects hostnames over 255
13030 characters in length. Previously, it would silently truncate them,
13031 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
13032 Patch by "junglefowl".
13035 Changes in version 0.3.0.3-alpha - 2017-02-03
13036 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
13037 0.3.0.x development series, including some that could cause
13038 authorities to behave badly. There is also a fix for a longstanding
13039 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
13040 includes some smaller features and bugfixes.
13042 The Tor 0.3.0.x release series is now in patch-freeze: no additional
13043 features will be considered for inclusion in 0.3.0.x. We suspect that
13044 some bugs will probably remain, however, and we encourage people to
13047 o Major bugfixes (directory authority):
13048 - During voting, when marking a relay as a probable sybil, do not
13049 clear its BadExit flag: sybils can still be bad in other ways
13050 too. (We still clear the other flags.) Fixes bug 21108; bugfix
13052 - When deciding whether we have just found a router to be reachable,
13053 do not penalize it for not having performed an Ed25519 link
13054 handshake if it does not claim to support an Ed25519 handshake.
13055 Previously, we would treat such relays as non-running. Fixes bug
13056 21107; bugfix on 0.3.0.1-alpha.
13058 o Major bugfixes (entry guards):
13059 - Stop trying to build circuits through entry guards for which we
13060 have no descriptor. Also, stop crashing in the case that we *do*
13061 accidentally try to build a circuit in such a state. Fixes bug
13062 21242; bugfix on 0.3.0.1-alpha.
13064 o Major bugfixes (IPv6 Exits):
13065 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
13066 any IPv6 addresses. Instead, only reject a port over IPv6 if the
13067 exit policy rejects that port on more than an IPv6 /16 of
13068 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
13069 which rejected a relay's own IPv6 address by default. Fixes bug
13070 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
13072 o Minor feature (client):
13073 - Enable IPv6 traffic on the SocksPort by default. To disable this,
13074 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
13076 o Minor feature (fallback scripts):
13077 - Add a check_existing mode to updateFallbackDirs.py, which checks
13078 if fallbacks in the hard-coded list are working. Closes ticket
13079 20174. Patch by haxxpop.
13081 o Minor features (ciphersuite selection):
13082 - Clients now advertise a list of ciphersuites closer to the ones
13083 preferred by Firefox. Closes part of ticket 15426.
13084 - Allow relays to accept a wider range of ciphersuites, including
13085 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
13087 o Minor features (controller, configuration):
13088 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
13089 and so on, now comes with a __*Port variant that will not be saved
13090 to the torrc file by the controller's SAVECONF command. This
13091 change allows TorBrowser to set up a single-use domain socket for
13092 each time it launches Tor. Closes ticket 20956.
13093 - The GETCONF command can now query options that may only be
13094 meaningful in context-sensitive lists. This allows the controller
13095 to query the mixed SocksPort/__SocksPort style options introduced
13096 in feature 20956. Implements ticket 21300.
13098 o Minor features (portability, compilation):
13099 - Autoconf now checks to determine if OpenSSL structures are opaque,
13100 instead of explicitly checking for OpenSSL version numbers. Part
13102 - Support building with recent LibreSSL code that uses opaque
13103 structures. Closes ticket 21359.
13105 o Minor features (relay):
13106 - We now allow separation of exit and relay traffic to different
13107 source IP addresses, using the OutboundBindAddressExit and
13108 OutboundBindAddressOR options respectively. Closes ticket 17975.
13109 Written by Michael Sonntag.
13111 o Minor bugfix (logging):
13112 - Don't recommend the use of Tor2web in non-anonymous mode.
13113 Recommending Tor2web is a bad idea because the client loses all
13114 anonymity. Tor2web should only be used in specific cases by users
13115 who *know* and understand the issues. Fixes bug 21294; bugfix
13118 o Minor bugfixes (client):
13119 - Always recover from failures in extend_info_from_node(), in an
13120 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
13121 bugfix on 0.2.3.1-alpha.
13123 o Minor bugfixes (client, entry guards):
13124 - Fix a bug warning (with backtrace) when we fail a channel that
13125 circuits to fallback directories on it. Fixes bug 21128; bugfix
13127 - Fix a spurious bug warning (with backtrace) when removing an
13128 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
13129 - Fix a bug of the new guard algorithm where tor could stall for up
13130 to 10 minutes before retrying a guard after a long period of no
13131 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
13132 - Do not try to build circuits until we have descriptors for our
13133 primary entry guards. Related to fix for bug 21242.
13135 o Minor bugfixes (configure, autoconf):
13136 - Rename the configure option --enable-expensive-hardening to
13137 --enable-fragile-hardening. Expensive hardening makes the tor
13138 daemon abort when some kinds of issues are detected. Thus, it
13139 makes tor more at risk of remote crashes but safer against RCE or
13140 heartbleed bug category. We now try to explain this issue in a
13141 message from the configure script. Fixes bug 21290; bugfix
13144 o Minor bugfixes (controller):
13145 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
13146 20824; bugfix on 0.3.0.1-alpha.
13148 o Minor bugfixes (hidden service):
13149 - Clean up the code for expiring intro points with no associated
13150 circuits. It was causing, rarely, a service with some expiring
13151 introduction points to not open enough additional introduction
13152 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
13153 - Stop setting the torrc option HiddenServiceStatistics to "0" just
13154 because we're not a bridge or relay. Instead, we preserve whatever
13155 value the user set (or didn't set). Fixes bug 21150; bugfix
13157 - Resolve two possible underflows which could lead to creating and
13158 closing a lot of introduction point circuits in a non-stop loop.
13159 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
13161 o Minor bugfixes (portability):
13162 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
13163 It is supported by OpenBSD itself, and also by most OpenBSD
13164 variants (such as Bitrig). Fixes bug 20980; bugfix
13166 - When mapping a file of length greater than SIZE_MAX, do not
13167 silently truncate its contents. This issue could occur on 32 bit
13168 systems with large file support and files which are larger than 4
13169 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
13171 o Minor bugfixes (tor-resolve):
13172 - The tor-resolve command line tool now rejects hostnames over 255
13173 characters in length. Previously, it would silently truncate them,
13174 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
13175 Patch by "junglefowl".
13177 o Minor bugfixes (Windows services):
13178 - Be sure to initialize the monotonic time subsystem before using
13179 it, even when running as an NT service. Fixes bug 21356; bugfix
13183 Changes in version 0.3.0.2-alpha - 2017-01-23
13184 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
13185 cause relays and clients to crash, even if they were not built with
13186 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
13187 versions, and also affects 0.3.0.1-alpha: all relays running an affected
13188 version should upgrade.
13190 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
13191 time-to-live values, makes directory authorities enforce the 1-to-1
13192 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
13193 client-side onion service reachability bug, does better at selecting
13194 the set of fallback directories, and more.
13196 o Major bugfixes (security, also in 0.2.9.9):
13197 - Downgrade the "-ftrapv" option from "always on" to "only on when
13198 --enable-expensive-hardening is provided." This hardening option, like
13199 others, can turn survivable bugs into crashes--and having it on by
13200 default made a (relatively harmless) integer overflow bug into a
13201 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
13204 o Major features (security):
13205 - Change the algorithm used to decide DNS TTLs on client and server
13206 side, to better resist DNS-based correlation attacks like the
13207 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
13208 Feamster. Now relays only return one of two possible DNS TTL
13209 values, and clients are willing to believe DNS TTL values up to 3
13210 hours long. Closes ticket 19769.
13212 o Major features (directory authority, security):
13213 - The default for AuthDirPinKeys is now 1: directory authorities
13214 will reject relays where the RSA identity key matches a previously
13215 seen value, but the Ed25519 key has changed. Closes ticket 18319.
13217 o Major bugfixes (client, guard, crash):
13218 - In circuit_get_global_origin_list(), return the actual list of
13219 origin circuits. The previous version of this code returned the
13220 list of all the circuits, and could have caused strange bugs,
13221 including possible crashes. Fixes bug 21118; bugfix
13224 o Major bugfixes (client, onion service, also in 0.2.9.9):
13225 - Fix a client-side onion service reachability bug, where multiple
13226 socks requests to an onion service (or a single slow request)
13227 could cause us to mistakenly mark some of the service's
13228 introduction points as failed, and we cache that failure so
13229 eventually we run out and can't reach the service. Also resolves a
13230 mysterious "Remote server sent bogus reason code 65021" log
13231 warning. The bug was introduced in ticket 17218, where we tried to
13232 remember the circuit end reason as a uint16_t, which mangled
13233 negative values. Partially fixes bug 21056 and fixes bug 20307;
13234 bugfix on 0.2.8.1-alpha.
13236 o Major bugfixes (DNS):
13237 - Fix a bug that prevented exit nodes from caching DNS records for
13238 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
13240 o Minor features (controller):
13241 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
13242 shared-random values to the controller. Closes ticket 19925.
13244 o Minor features (entry guards):
13245 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
13246 break regression tests.
13247 - Require UseEntryGuards when UseBridges is set, in order to make
13248 sure bridges aren't bypassed. Resolves ticket 20502.
13250 o Minor features (fallback directories):
13251 - Select 200 fallback directories for each release. Closes
13253 - Allow 3 fallback relays per operator, which is safe now that we
13254 are choosing 200 fallback relays. Closes ticket 20912.
13255 - Exclude relays affected by bug 20499 from the fallback list.
13256 Exclude relays from the fallback list if they are running versions
13257 known to be affected by bug 20499, or if in our tests they deliver
13258 a stale consensus (i.e. one that expired more than 24 hours ago).
13259 Closes ticket 20539.
13260 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
13262 - Require fallback directories to have the same address and port for
13263 7 days (now that we have enough relays with this stability).
13264 Relays whose OnionOO stability timer is reset on restart by bug
13265 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
13266 this issue. Closes ticket 20880; maintains short-term fix
13268 - Require fallbacks to have flags for 90% of the time (weighted
13269 decaying average), rather than 95%. This allows at least 73% of
13270 clients to bootstrap in the first 5 seconds without contacting an
13271 authority. Part of ticket 18828.
13272 - Annotate updateFallbackDirs.py with the bandwidth and consensus
13273 weight for each candidate fallback. Closes ticket 20878.
13274 - Make it easier to change the output sort order of fallbacks.
13275 Closes ticket 20822.
13276 - Display the relay fingerprint when downloading consensuses from
13277 fallbacks. Closes ticket 20908.
13279 o Minor features (geoip, also in 0.2.9.9):
13280 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13283 o Minor features (next-gen onion service directories):
13284 - Remove the "EnableOnionServicesV3" consensus parameter that we
13285 introduced in 0.3.0.1-alpha: relays are now always willing to act
13286 as v3 onion service directories. Resolves ticket 19899.
13288 o Minor features (linting):
13289 - Enhance the changes file linter to warn on Tor versions that are
13290 prefixed with "tor-". Closes ticket 21096.
13292 o Minor features (logging):
13293 - In several places, describe unset ed25519 keys as "<unset>",
13294 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
13296 o Minor bugfix (control protocol):
13297 - The reply to a "GETINFO config/names" request via the control
13298 protocol now spells the type "Dependent" correctly. This is a
13299 breaking change in the control protocol. (The field seems to be
13300 ignored by the most common known controllers.) Fixes bug 18146;
13301 bugfix on 0.1.1.4-alpha.
13303 o Minor bugfixes (bug resilience):
13304 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
13305 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
13306 Hans Jerry Illikainen.
13308 o Minor bugfixes (build):
13309 - Replace obsolete Autoconf macros with their modern equivalent and
13310 prevent similar issues in the future. Fixes bug 20990; bugfix
13313 o Minor bugfixes (client, guards):
13314 - Fix bug where Tor would think that there are circuits waiting for
13315 better guards even though those circuits have been freed. Fixes
13316 bug 21142; bugfix on 0.3.0.1-alpha.
13318 o Minor bugfixes (config):
13319 - Don't assert on startup when trying to get the options list and
13320 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
13321 options so of course they aren't ready yet. Fixes bug 21062;
13322 bugfix on 0.2.9.3-alpha.
13324 o Minor bugfixes (controller):
13325 - Make the GETINFO interface for inquiring about entry guards
13326 support the new guards backend. Fixes bug 20823; bugfix
13329 o Minor bugfixes (dead code):
13330 - Remove a redundant check for PidFile changes at runtime in
13331 options_transition_allowed(): this check is already performed
13332 regardless of whether the sandbox is active. Fixes bug 21123;
13333 bugfix on 0.2.5.4-alpha.
13335 o Minor bugfixes (documentation):
13336 - Update the tor manual page to document every option that can not
13337 be changed while tor is running. Fixes bug 21122.
13339 o Minor bugfixes (fallback directories):
13340 - Stop failing when a relay has no uptime data in
13341 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
13342 - Avoid checking fallback candidates' DirPorts if they are down in
13343 OnionOO. When a relay operator has multiple relays, this
13344 prioritizes relays that are up over relays that are down. Fixes
13345 bug 20926; bugfix on 0.2.8.3-alpha.
13346 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
13347 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
13349 o Minor bugfixes (guards, bootstrapping):
13350 - When connecting to a directory guard during bootstrap, do not mark
13351 the guard as successful until we receive a good-looking directory
13352 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
13354 o Minor bugfixes (onion services):
13355 - Fix the config reload pruning of old vs new services so it
13356 actually works when both ephemeral and non-ephemeral services are
13357 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
13358 - Allow the number of introduction points to be as low as 0, rather
13359 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
13361 o Minor bugfixes (IPv6):
13362 - Make IPv6-using clients try harder to find an IPv6 directory
13363 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
13364 - When IPv6 addresses have not been downloaded yet (microdesc
13365 consensus documents don't list relay IPv6 addresses), use hard-
13366 coded addresses for authorities, fallbacks, and configured
13367 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
13368 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
13370 o Minor bugfixes (memory leaks):
13371 - Fix a memory leak when configuring hidden services. Fixes bug
13372 20987; bugfix on 0.3.0.1-alpha.
13374 o Minor bugfixes (portability, also in 0.2.9.9):
13375 - Avoid crashing when Tor is built using headers that contain
13376 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13377 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13379 - Fix Libevent detection on platforms without Libevent 1 headers
13380 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13382 o Minor bugfixes (relay):
13383 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
13384 initializing the keys would reset the DataDirectory to 0700
13385 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
13386 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
13388 o Minor bugfixes (testing):
13389 - Remove undefined behavior from the backtrace generator by removing
13390 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
13392 o Minor bugfixes (unit tests):
13393 - Allow the unit tests to pass even when DNS lookups of bogus
13394 addresses do not fail as expected. Fixes bug 20862 and 20863;
13395 bugfix on unit tests introduced in 0.2.8.1-alpha
13396 through 0.2.9.4-alpha.
13398 o Code simplification and refactoring:
13399 - Refactor code to manipulate global_origin_circuit_list into
13400 separate functions. Closes ticket 20921.
13402 o Documentation (formatting):
13403 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
13404 blocks were incorrectly appearing. Closes ticket 20885.
13406 o Documentation (man page):
13407 - Clarify many options in tor.1 and add some min/max values for
13408 HiddenService options. Closes ticket 21058.
13411 Changes in version 0.2.9.9 - 2017-01-23
13412 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
13413 cause relays and clients to crash, even if they were not built with
13414 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
13415 versions, and also affects 0.3.0.1-alpha: all relays running an affected
13416 version should upgrade.
13418 This release also resolves a client-side onion service reachability
13419 bug, and resolves a pair of small portability issues.
13421 o Major bugfixes (security):
13422 - Downgrade the "-ftrapv" option from "always on" to "only on when
13423 --enable-expensive-hardening is provided." This hardening option,
13424 like others, can turn survivable bugs into crashes -- and having
13425 it on by default made a (relatively harmless) integer overflow bug
13426 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
13427 bugfix on 0.2.9.1-alpha.
13429 o Major bugfixes (client, onion service):
13430 - Fix a client-side onion service reachability bug, where multiple
13431 socks requests to an onion service (or a single slow request)
13432 could cause us to mistakenly mark some of the service's
13433 introduction points as failed, and we cache that failure so
13434 eventually we run out and can't reach the service. Also resolves a
13435 mysterious "Remote server sent bogus reason code 65021" log
13436 warning. The bug was introduced in ticket 17218, where we tried to
13437 remember the circuit end reason as a uint16_t, which mangled
13438 negative values. Partially fixes bug 21056 and fixes bug 20307;
13439 bugfix on 0.2.8.1-alpha.
13441 o Minor features (geoip):
13442 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
13445 o Minor bugfixes (portability):
13446 - Avoid crashing when Tor is built using headers that contain
13447 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
13448 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
13450 - Fix Libevent detection on platforms without Libevent 1 headers
13451 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
13454 Changes in version 0.3.0.1-alpha - 2016-12-19
13455 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
13456 series. It strengthens Tor's link and circuit handshakes by
13457 identifying relays by their Ed25519 keys, improves the algorithm that
13458 clients use to choose and maintain their list of guards, and includes
13459 additional backend support for the next-generation hidden service
13460 design. It also contains numerous other small features and
13461 improvements to security, correctness, and performance.
13463 Below are the changes since 0.2.9.8.
13465 o Major features (guard selection algorithm):
13466 - Tor's guard selection algorithm has been redesigned from the
13467 ground up, to better support unreliable networks and restrictive
13468 sets of entry nodes, and to better resist guard-capture attacks by
13469 hostile local networks. Implements proposal 271; closes
13472 o Major features (next-generation hidden services):
13473 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
13474 prop224 aka "Next Generation Hidden Services". Service and clients
13475 don't use this functionality yet. Closes ticket 19043. Based on
13476 initial code by Alec Heifetz.
13477 - Relays now support the HSDir version 3 protocol, so that they can
13478 can store and serve v3 descriptors. This is part of the next-
13479 generation onion service work detailed in proposal 224. Closes
13482 o Major features (protocol, ed25519 identity keys):
13483 - Relays now use Ed25519 to prove their Ed25519 identities and to
13484 one another, and to clients. This algorithm is faster and more
13485 secure than the RSA-based handshake we've been doing until now.
13486 Implements the second big part of proposal 220; Closes
13488 - Clients now support including Ed25519 identity keys in the EXTEND2
13489 cells they generate. By default, this is controlled by a consensus
13490 parameter, currently disabled. You can turn this feature on for
13491 testing by setting ExtendByEd25519ID in your configuration. This
13492 might make your traffic appear different than the traffic
13493 generated by other users, however. Implements part of ticket
13494 15056; part of proposal 220.
13495 - Relays now understand requests to extend to other relays by their
13496 Ed25519 identity keys. When an Ed25519 identity key is included in
13497 an EXTEND2 cell, the relay will only extend the circuit if the
13498 other relay can prove ownership of that identity. Implements part
13499 of ticket 15056; part of proposal 220.
13501 o Major bugfixes (scheduler):
13502 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
13503 caused the channel scheduler to behave more or less randomly,
13504 rather than preferring channels with higher-priority circuits.
13505 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
13507 o Minor features (controller):
13508 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
13509 rather than "unrecognized." Closes ticket 20389; patch from
13512 o Minor features (diagnostic, directory client):
13513 - Warn when we find an unexpected inconsistency in directory
13514 download status objects. Prevents some negative consequences of
13517 o Minor features (directory authority):
13518 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
13519 default) to control whether authorities should try to probe relays
13520 by their Ed25519 link keys. This option will go away in a few
13521 releases--unless we encounter major trouble in our ed25519 link
13522 protocol rollout, in which case it will serve as a safety option.
13524 o Minor features (directory cache):
13525 - Relays and bridges will now refuse to serve the consensus they
13526 have if they know it is too old for a client to use. Closes
13529 o Minor features (ed25519 link handshake):
13530 - Advertise support for the ed25519 link handshake using the
13531 subprotocol-versions mechanism, so that clients can tell which
13532 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
13534 o Minor features (fingerprinting resistance, authentication):
13535 - Extend the length of RSA keys used for TLS link authentication to
13536 2048 bits. (These weren't used for forward secrecy; for forward
13537 secrecy, we used P256.) Closes ticket 13752.
13539 o Minor features (infrastructure):
13540 - Implement smartlist_add_strdup() function. Replaces the use of
13541 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
13543 o Minor bugfixes (client):
13544 - When clients that use bridges start up with a cached consensus on
13545 disk, they were ignoring it and downloading a new one. Now they
13546 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
13548 o Minor bugfixes (configuration):
13549 - Accept non-space whitespace characters after the severity level in
13550 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
13551 - Support "TByte" and "TBytes" units in options given in bytes.
13552 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
13553 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
13555 o Minor bugfixes (consensus weight):
13556 - Add new consensus method that initializes bw weights to 1 instead
13557 of 0. This prevents a zero weight from making it all the way to
13558 the end (happens in small testing networks) and causing an error.
13559 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
13561 o Minor bugfixes (descriptors):
13562 - Correctly recognise downloaded full descriptors as valid, even
13563 when using microdescriptors as circuits. This affects clients with
13564 FetchUselessDescriptors set, and may affect directory authorities.
13565 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
13567 o Minor bugfixes (directory system):
13568 - Download all consensus flavors, descriptors, and authority
13569 certificates when FetchUselessDescriptors is set, regardless of
13570 whether tor is a directory cache or not. Fixes bug 20667; bugfix
13571 on all recent tor versions.
13572 - Bridges and relays now use microdescriptors (like clients do)
13573 rather than old-style router descriptors. Now bridges will blend
13574 in with clients in terms of the circuits they build. Fixes bug
13575 6769; bugfix on 0.2.3.2-alpha.
13577 o Minor bugfixes (ed25519 certificates):
13578 - Correctly interpret ed25519 certificates that would expire some
13579 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
13581 o Minor bugfixes (hidden services):
13582 - Stop ignoring misconfigured hidden services. Instead, refuse to
13583 start tor until the misconfigurations have been corrected. Fixes
13584 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
13587 o Minor bugfixes (memory leak at exit):
13588 - Fix a small harmless memory leak at exit of the previously unused
13589 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
13592 o Minor bugfixes (util):
13593 - When finishing writing a file to disk, if we were about to replace
13594 the file with the temporary file created before and we fail to
13595 replace it, remove the temporary file so it doesn't stay on disk.
13596 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
13598 o Minor bugfixes (Windows):
13599 - Check for getpagesize before using it to mmap files. This fixes
13600 compilation in some MinGW environments. Fixes bug 20530; bugfix on
13601 0.1.2.1-alpha. Reported by "ice".
13603 o Code simplification and refactoring:
13604 - Abolish all global guard context in entrynodes.c; replace with new
13605 guard_selection_t structure as preparation for proposal 271.
13606 Closes ticket 19858.
13607 - Introduce rend_service_is_ephemeral() that tells if given onion
13608 service is ephemeral. Replace unclear NULL-checkings for service
13609 directory with this function. Closes ticket 20526.
13610 - Extract magic numbers in circuituse.c into defined variables.
13611 - Refactor circuit_is_available_for_use to remove unnecessary check.
13612 - Refactor circuit_predict_and_launch_new for readability and
13613 testability. Closes ticket 18873.
13614 - Refactor large if statement in purpose_needs_anonymity to use
13615 switch statement instead. Closes part of ticket 20077.
13616 - Refactor the hashing API to return negative values for errors, as
13617 is done as throughout the codebase. Closes ticket 20717.
13618 - Remove data structures that were used to index or_connection
13619 objects by their RSA identity digests. These structures are fully
13620 redundant with the similar structures used in the
13621 channel abstraction.
13622 - Remove duplicate code in the channel_write_*cell() functions.
13623 Closes ticket 13827; patch from Pingl.
13624 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
13625 use only purpose_needs_anonymity. Closes part of ticket 20077.
13626 - The code to generate and parse EXTEND and EXTEND2 cells has been
13627 replaced with code automatically generated by the
13631 - Include the "TBits" unit in Tor's man page. Fixes part of bug
13632 20622; bugfix on 0.2.5.1-alpha.
13633 - Change '1' to 'weight_scale' in consensus bw weights calculation
13634 comments, as that is reality. Closes ticket 20273. Patch
13636 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
13637 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
13639 - Stop the man page from incorrectly stating that HiddenServiceDir
13640 must already exist. Fixes 20486.
13641 - Clarify that when ClientRejectInternalAddresses is enabled (which
13642 is the default), multicast DNS hostnames for machines on the local
13643 network (of the form *.local) are also rejected. Closes
13646 o Removed features:
13647 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
13648 limit for relays running on a single IP applies to authority IP
13649 addresses as well as to non-authority IP addresses. Closes
13651 - The UseDirectoryGuards torrc option no longer exists: all users
13652 that use entry guards will also use directory guards. Related to
13653 proposal 271; implements part of ticket 20831.
13656 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
13657 from "overcaffeinated".
13658 - Perform the coding style checks when running the tests and fail
13659 when coding style violations are found. Closes ticket 5500.
13660 - Add tests for networkstatus_compute_bw_weights_v10.
13661 - Add unit tests circuit_predict_and_launch_new.
13662 - Extract dummy_origin_circuit_new so it can be used by other
13666 Changes in version 0.2.8.12 - 2016-12-19
13667 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
13668 below) where Tor clients could crash when attempting to visit a
13669 hostile hidden service. Clients are recommended to upgrade as packages
13670 become available for their systems.
13672 It also includes an updated list of fallback directories, backported
13675 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
13676 backported to 0.2.8 in the future.
13678 o Major bugfixes (parsing, security, backported from 0.2.9.8):
13679 - Fix a bug in parsing that could cause clients to read a single
13680 byte past the end of an allocated region. This bug could be used
13681 to cause hardened clients (built with --enable-expensive-hardening)
13682 to crash if they tried to visit a hostile hidden service. Non-
13683 hardened clients are only affected depending on the details of
13684 their platform's memory allocator. Fixes bug 21018; bugfix on
13685 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13686 2016-12-002 and as CVE-2016-1254.
13688 o Minor features (fallback directory list, backported from 0.2.9.8):
13689 - Replace the 81 remaining fallbacks of the 100 originally
13690 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13691 fallbacks (123 new, 54 existing, 27 removed) generated in December
13692 2016. Resolves ticket 20170.
13694 o Minor features (geoip, backported from 0.2.9.7-rc):
13695 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
13699 Changes in version 0.2.9.8 - 2016-12-19
13700 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
13702 The Tor 0.2.9 series makes mandatory a number of security features
13703 that were formerly optional. It includes support for a new shared-
13704 randomness protocol that will form the basis for next generation
13705 hidden services, includes a single-hop hidden service mode for
13706 optimizing .onion services that don't actually want to be hidden,
13707 tries harder not to overload the directory authorities with excessive
13708 downloads, and supports a better protocol versioning scheme for
13709 improved compatibility with other implementations of the Tor protocol.
13711 And of course, there are numerous other bugfixes and improvements.
13713 This release also includes a fix for a medium-severity issue (bug
13714 21018 below) where Tor clients could crash when attempting to visit a
13715 hostile hidden service. Clients are recommended to upgrade as packages
13716 become available for their systems.
13718 Below are the changes since 0.2.9.7-rc. For a list of all changes
13719 since 0.2.8, see the ReleaseNotes file.
13721 o Major bugfixes (parsing, security):
13722 - Fix a bug in parsing that could cause clients to read a single
13723 byte past the end of an allocated region. This bug could be used
13724 to cause hardened clients (built with --enable-expensive-hardening)
13725 to crash if they tried to visit a hostile hidden service. Non-
13726 hardened clients are only affected depending on the details of
13727 their platform's memory allocator. Fixes bug 21018; bugfix on
13728 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
13729 2016-12-002 and as CVE-2016-1254.
13731 o Minor features (fallback directory list):
13732 - Replace the 81 remaining fallbacks of the 100 originally
13733 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
13734 fallbacks (123 new, 54 existing, 27 removed) generated in December
13735 2016. Resolves ticket 20170.
13738 Changes in version 0.2.9.7-rc - 2016-12-12
13739 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
13740 including a few that had prevented tests from passing on
13743 o Minor features (geoip):
13744 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
13747 o Minor bugfix (build):
13748 - The current Git revision when building from a local repository is
13749 now detected correctly when using git worktrees. Fixes bug 20492;
13750 bugfix on 0.2.3.9-alpha.
13752 o Minor bugfixes (directory authority):
13753 - When computing old Tor protocol line version in protover, we were
13754 looking at 0.2.7.5 twice instead of a specific case for
13755 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
13757 o Minor bugfixes (download scheduling):
13758 - Resolve a "bug" warning when considering a download schedule whose
13759 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
13761 o Minor bugfixes (logging):
13762 - Downgrade a harmless log message about the
13763 pending_entry_connections list from "warn" to "info". Mitigates
13766 o Minor bugfixes (memory leak):
13767 - Fix a small memory leak when receiving AF_UNIX connections on a
13768 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
13769 - When moving a signed descriptor object from a source to an
13770 existing destination, free the allocated memory inside that
13771 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
13773 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
13774 - Fix a memory leak and use-after-free error when removing entries
13775 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
13776 0.2.5.5-alpha. Patch from "cypherpunks".
13778 o Minor bugfixes (portability):
13779 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
13780 Fixes bug 20935; bugfix on 0.2.9.6-rc.
13782 o Minor bugfixes (unit tests):
13783 - Stop expecting NetBSD unit tests to report success for ipfw. Part
13784 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
13785 - Fix tolerances in unit tests for monotonic time comparisons
13786 between nanoseconds and microseconds. Previously, we accepted a 10
13787 us difference only, which is not realistic on every platform's
13788 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
13789 - Remove a double-free in the single onion service unit test. Stop
13790 ignoring a return value. Make future changes less error-prone.
13791 Fixes bug 20864; bugfix on 0.2.9.6-rc.
13794 Changes in version 0.2.8.11 - 2016-12-08
13795 Tor 0.2.8.11 backports fixes for additional portability issues that
13796 could prevent Tor from building correctly on OSX Sierra, or with
13797 OpenSSL 1.1. Affected users should upgrade; others can safely stay
13800 o Minor bugfixes (portability):
13801 - Avoid compilation errors when building on OSX Sierra. Sierra began
13802 to support the getentropy() and clock_gettime() APIs, but created
13803 a few problems in doing so. Tor 0.2.9 has a more thorough set of
13804 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
13805 monotonic time interfaces. Fixes bug 20865. Bugfix
13808 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13809 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
13810 architectures. Closes ticket 20588.
13813 Changes in version 0.2.8.10 - 2016-12-02
13814 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
13815 unusable after they left standby mode. It also backports fixes for
13816 a few portability issues and a small but problematic memory leak.
13818 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
13819 - When Tor leaves standby because of a new application request, open
13820 circuits as needed to serve that request. Previously, we would
13821 potentially wait a very long time. Fixes part of bug 19969; bugfix
13824 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
13825 - Clients now respond to new application stream requests immediately
13826 when they arrive, rather than waiting up to one second before
13827 starting to handle them. Fixes part of bug 19969; bugfix
13830 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
13831 - Work around a bug in the OSX 10.12 SDK that would prevent us from
13832 successfully targeting earlier versions of OSX. Resolves
13835 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
13836 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
13837 20551; bugfix on 0.2.1.1-alpha.
13839 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
13840 - Work around a memory leak in OpenSSL 1.1 when encoding public
13841 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
13843 o Minor features (geoip):
13844 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
13847 Changes in version 0.2.9.6-rc - 2016-12-02
13848 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
13849 version. We hope that it will be ready to become stable soon, and we
13850 encourage everyone to test this release. If no showstopper bugs are
13851 found here, the next 0.2.9 release will be stable.
13853 o Major bugfixes (relay, resolver, logging):
13854 - For relays that don't know their own address, avoid attempting a
13855 local hostname resolve for each descriptor we download. This
13856 will cut down on the number of "Success: chose address 'x.x.x.x'"
13857 log lines, and also avoid confusing clock jumps if the resolver
13858 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
13860 o Minor bugfixes (client, fascistfirewall):
13861 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
13862 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
13864 o Minor bugfixes (hidden services):
13865 - Stop ignoring the anonymity status of saved keys for hidden
13866 services and single onion services when first starting tor.
13867 Instead, refuse to start tor if any hidden service key has been
13868 used in a different hidden service anonymity mode. Fixes bug
13869 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
13871 o Minor bugfixes (portability):
13872 - Work around a bug in the OSX 10.12 SDK that would prevent us from
13873 successfully targeting earlier versions of OSX. Resolves
13875 - Run correctly when built on Windows build environments that
13876 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
13878 o Minor bugfixes (single onion services, Tor2web):
13879 - Stop complaining about long-term one-hop circuits deliberately
13880 created by single onion services and Tor2web. These log messages
13881 are intended to diagnose issue 8387, which relates to circuits
13882 hanging around forever for no reason. Fixes bug 20613; bugfix on
13883 0.2.9.1-alpha. Reported by "pastly".
13885 o Minor bugfixes (unit tests):
13886 - Stop spurious failures in the local interface address discovery
13887 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
13891 - Correct the minimum bandwidth value in torrc.sample, and queue a
13892 corresponding change for torrc.minimal. Closes ticket 20085.
13895 Changes in version 0.2.9.5-alpha - 2016-11-08
13896 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
13897 version. We believe one or two probably remain, and we encourage
13898 everyone to test this release.
13900 o Major bugfixes (client performance):
13901 - Clients now respond to new application stream requests immediately
13902 when they arrive, rather than waiting up to one second before
13903 starting to handle them. Fixes part of bug 19969; bugfix
13906 o Major bugfixes (client reliability):
13907 - When Tor leaves standby because of a new application request, open
13908 circuits as needed to serve that request. Previously, we would
13909 potentially wait a very long time. Fixes part of bug 19969; bugfix
13912 o Major bugfixes (download scheduling):
13913 - When using an exponential backoff schedule, do not give up on
13914 downloading just because we have failed a bunch of times. Since
13915 each delay is longer than the last, retrying indefinitely won't
13916 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
13917 - If a consensus expires while we are waiting for certificates to
13918 download, stop waiting for certificates.
13919 - If we stop waiting for certificates less than a minute after we
13920 started downloading them, do not consider the certificate download
13921 failure a separate failure. Fixes bug 20533; bugfix
13923 - Remove the maximum delay on exponential-backoff scheduling. Since
13924 we now allow an infinite number of failures (see ticket 20536), we
13925 must now allow the time to grow longer on each failure. Fixes part
13926 of bug 20534; bugfix on 0.2.9.1-alpha.
13927 - Make our initial download delays closer to those from 0.2.8. Fixes
13928 another part of bug 20534; bugfix on 0.2.9.1-alpha.
13929 - When determining when to download a directory object, handle times
13930 after 2038 if the operating system supports them. (Someday this
13931 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
13932 - When using exponential backoff in test networks, use a lower
13933 exponent, so the delays do not vary as much. This helps test
13934 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
13936 o Minor features (geoip):
13937 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
13940 o Minor bugfixes (client directory scheduling):
13941 - Treat "relay too busy to answer request" as a failed request and a
13942 reason to back off on our retry frequency. This is safe now that
13943 exponential backoffs retry indefinitely, and avoids a bug where we
13944 would reset our download schedule erroneously. Fixes bug 20593;
13945 bugfix on 0.2.9.1-alpha.
13947 o Minor bugfixes (client, logging):
13948 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
13949 assume all nodes support EXTEND2. Use ntor whenever a key is
13950 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
13951 - On DNSPort, stop logging a BUG warning on a failed hostname
13952 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
13954 o Minor bugfixes (hidden services):
13955 - When configuring hidden services, check every hidden service
13956 directory's permissions. Previously, we only checked the last
13957 hidden service. Fixes bug 20529; bugfix the work to fix 13942
13960 o Minor bugfixes (portability):
13961 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
13962 architectures. Closes ticket 20588.
13963 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
13964 removed the ECDH ciphers which caused the tests to fail on
13965 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
13966 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
13967 20551; bugfix on 0.2.1.1-alpha.
13969 o Minor bugfixes (relay bootstrap):
13970 - Ensure relays don't make multiple connections during bootstrap.
13971 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
13973 o Minor bugfixes (relay):
13974 - Work around a memory leak in OpenSSL 1.1 when encoding public
13975 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
13976 - Avoid a small memory leak when informing worker threads about
13977 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
13978 - Do not try to parallelize workers more than 16x without the user
13979 explicitly configuring us to do so, even if we do detect more than
13980 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
13982 o Minor bugfixes (single onion services):
13983 - Start correctly when creating a single onion service in a
13984 directory that did not previously exist. Fixes bug 20484; bugfix
13987 o Minor bugfixes (testing):
13988 - Avoid a unit test failure on systems with over 16 detectable CPU
13989 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
13992 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
13993 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
13994 - Module-level documentation for several more modules. Closes
13995 tickets 19287 and 19290.
13998 Changes in version 0.2.8.9 - 2016-10-17
13999 Tor 0.2.8.9 backports a fix for a security hole in previous versions
14000 of Tor that would allow a remote attacker to crash a Tor client,
14001 hidden service, relay, or authority. All Tor users should upgrade to
14002 this version, or to 0.2.9.4-alpha. Patches will be released for older
14005 o Major features (security fixes, also in 0.2.9.4-alpha):
14006 - Prevent a class of security bugs caused by treating the contents
14007 of a buffer chunk as if they were a NUL-terminated string. At
14008 least one such bug seems to be present in all currently used
14009 versions of Tor, and would allow an attacker to remotely crash
14010 most Tor instances, especially those compiled with extra compiler
14011 hardening. With this defense in place, such bugs can't crash Tor,
14012 though we should still fix them as they occur. Closes ticket
14013 20384 (TROVE-2016-10-001).
14015 o Minor features (geoip):
14016 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
14020 Changes in version 0.2.9.4-alpha - 2016-10-17
14021 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
14022 that would allow a remote attacker to crash a Tor client, hidden
14023 service, relay, or authority. All Tor users should upgrade to this
14024 version, or to 0.2.8.9. Patches will be released for older versions
14027 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
14028 previous versions of Tor, including the implementation of a feature to
14029 future- proof the Tor ecosystem against protocol changes, some bug
14030 fixes necessary for Tor Browser to use unix domain sockets correctly,
14031 and several portability improvements. We anticipate that this will be
14032 the last alpha in the Tor 0.2.9 series, and that the next release will
14033 be a release candidate.
14035 o Major features (security fixes):
14036 - Prevent a class of security bugs caused by treating the contents
14037 of a buffer chunk as if they were a NUL-terminated string. At
14038 least one such bug seems to be present in all currently used
14039 versions of Tor, and would allow an attacker to remotely crash
14040 most Tor instances, especially those compiled with extra compiler
14041 hardening. With this defense in place, such bugs can't crash Tor,
14042 though we should still fix them as they occur. Closes ticket
14043 20384 (TROVE-2016-10-001).
14045 o Major features (subprotocol versions):
14046 - Tor directory authorities now vote on a set of recommended
14047 subprotocol versions, and on a set of required subprotocol
14048 versions. Clients and relays that lack support for a _required_
14049 subprotocol version will not start; those that lack support for a
14050 _recommended_ subprotocol version will warn the user to upgrade.
14051 Closes ticket 19958; implements part of proposal 264.
14052 - Tor now uses "subprotocol versions" to indicate compatibility.
14053 Previously, versions of Tor looked at the declared Tor version of
14054 a relay to tell whether they could use a given feature. Now, they
14055 should be able to rely on its declared subprotocol versions. This
14056 change allows compatible implementations of the Tor protocol(s) to
14057 exist without pretending to be 100% bug-compatible with particular
14058 releases of Tor itself. Closes ticket 19958; implements part of
14061 o Minor feature (fallback directories):
14062 - Remove broken fallbacks from the hard-coded fallback directory
14063 list. Closes ticket 20190; patch by teor.
14065 o Minor features (client, directory):
14066 - Since authorities now omit all routers that lack the Running and
14067 Valid flags, we assume that any relay listed in the consensus must
14068 have those flags. Closes ticket 20001; implements part of
14071 o Minor features (compilation, portability):
14072 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
14075 o Minor features (development tools, etags):
14076 - Teach the "make tags" Makefile target how to correctly find
14077 "MOCK_IMPL" function definitions. Patch from nherring; closes
14080 o Minor features (geoip):
14081 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
14084 o Minor features (unix domain sockets):
14085 - When configuring a unix domain socket for a SocksPort,
14086 ControlPort, or Hidden service, you can now wrap the address in
14087 quotes, using C-style escapes inside the quotes. This allows unix
14088 domain socket paths to contain spaces.
14090 o Minor features (virtual addresses):
14091 - Increase the maximum number of bits for the IPv6 virtual network
14092 prefix from 16 to 104. In this way, the condition for address
14093 allocation is less restrictive. Closes ticket 20151; feature
14096 o Minor bugfixes (address discovery):
14097 - Stop reordering IP addresses returned by the OS. This makes it
14098 more likely that Tor will guess the same relay IP address every
14099 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
14100 Reported by René Mayrhofer, patch by "cypherpunks".
14102 o Minor bugfixes (client, unix domain sockets):
14103 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
14104 the client address is meaningless. Fixes bug 20261; bugfix
14107 o Minor bugfixes (compilation, OpenBSD):
14108 - Detect Libevent2 functions correctly on systems that provide
14109 libevent2, but where libevent1 is linked with -levent. Fixes bug
14110 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
14112 o Minor bugfixes (configuration):
14113 - When parsing quoted configuration values from the torrc file,
14114 handle windows line endings correctly. Fixes bug 19167; bugfix on
14115 0.2.0.16-alpha. Patch from "Pingl".
14117 o Minor bugfixes (getpass):
14118 - Defensively fix a non-triggerable heap corruption at do_getpass()
14119 to protect ourselves from mistakes in the future. Fixes bug
14120 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
14123 o Minor bugfixes (hidden service):
14124 - Allow hidden services to run on IPv6 addresses even when the
14125 IPv6Exit option is not set. Fixes bug 18357; bugfix
14129 - Add module-level internal documentation for 36 C files that
14130 previously didn't have a high-level overview. Closes ticket #20385.
14132 o Required libraries:
14133 - When building with OpenSSL, Tor now requires version 1.0.1 or
14134 later. OpenSSL 1.0.0 and earlier are no longer supported by the
14135 OpenSSL team, and should not be used. Closes ticket 20303.
14138 Changes in version 0.2.9.3-alpha - 2016-09-23
14139 Tor 0.2.9.3-alpha adds improved support for entities that want to make
14140 high-performance services available through the Tor .onion mechanism
14141 without themselves receiving anonymity as they host those services. It
14142 also tries harder to ensure that all steps on a circuit are using the
14143 strongest crypto possible, strengthens some TLS properties, and
14144 resolves several bugs -- including a pair of crash bugs from the 0.2.8
14145 series. Anybody running an earlier version of 0.2.9.x should upgrade.
14147 o Major bugfixes (crash, also in 0.2.8.8):
14148 - Fix a complicated crash bug that could affect Tor clients
14149 configured to use bridges when replacing a networkstatus consensus
14150 in which one of their bridges was mentioned. OpenBSD users saw
14151 more crashes here, but all platforms were potentially affected.
14152 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
14154 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
14155 - Fix a timing-dependent assertion failure that could occur when we
14156 tried to flush from a circuit after having freed its cells because
14157 of an out-of-memory condition. Fixes bug 20203; bugfix on
14158 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
14161 o Major features (circuit building, security):
14162 - Authorities, relays and clients now require ntor keys in all
14163 descriptors, for all hops (except for rare hidden service protocol
14164 cases), for all circuits, and for all other roles. Part of
14166 - Tor authorities, relays, and clients only use ntor, except for
14167 rare cases in the hidden service protocol. Part of ticket 19163.
14169 o Major features (single-hop "hidden" services):
14170 - Add experimental HiddenServiceSingleHopMode and
14171 HiddenServiceNonAnonymousMode options. When both are set to 1,
14172 every hidden service on a Tor instance becomes a non-anonymous
14173 Single Onion Service. Single Onions make one-hop (direct)
14174 connections to their introduction and rendezvous points. One-hop
14175 circuits make Single Onion servers easily locatable, but clients
14176 remain location-anonymous. This is compatible with the existing
14177 hidden service implementation, and works on the current tor
14178 network without any changes to older relays or clients. Implements
14179 proposal 260, completes ticket 17178. Patch by teor and asn.
14181 o Major features (resource management):
14182 - Tor can now notice it is about to run out of sockets, and
14183 preemptively close connections of lower priority. (This feature is
14184 off by default for now, since the current prioritizing method is
14185 yet not mature enough. You can enable it by setting
14186 "DisableOOSCheck 0", but watch out: it might close some sockets
14187 you would rather have it keep.) Closes ticket 18640.
14189 o Major bugfixes (circuit building):
14190 - Hidden service client-to-intro-point and service-to-rendezvous-
14191 point circuits use the TAP key supplied by the protocol, to avoid
14192 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
14194 o Major bugfixes (compilation, OpenBSD):
14195 - Fix a Libevent-detection bug in our autoconf script that would
14196 prevent Tor from linking successfully on OpenBSD. Patch from
14197 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
14199 o Major bugfixes (hidden services):
14200 - Clients now require hidden services to include the TAP keys for
14201 their intro points in the hidden service descriptor. This prevents
14202 an inadvertent upgrade to ntor, which a malicious hidden service
14203 could use to distinguish clients by consensus version. Fixes bug
14204 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
14206 o Minor features (security, TLS):
14207 - Servers no longer support clients that without AES ciphersuites.
14208 (3DES is no longer considered an acceptable cipher.) We believe
14209 that no such Tor clients currently exist, since Tor has required
14210 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
14212 o Minor feature (fallback directories):
14213 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
14214 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
14215 2016. Closes ticket 20190; patch by teor.
14217 o Minor features (geoip, also in 0.2.8.8):
14218 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
14221 o Minor feature (port flags):
14222 - Add new flags to the *Port options to finer control over which
14223 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
14224 and the synthetic flag OnionTrafficOnly, which is equivalent to
14225 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
14226 18693; patch by "teor".
14228 o Minor features (directory authority):
14229 - After voting, if the authorities decide that a relay is not
14230 "Valid", they no longer include it in the consensus at all. Closes
14231 ticket 20002; implements part of proposal 272.
14233 o Minor features (testing):
14234 - Disable memory protections on OpenBSD when performing our unit
14235 tests for memwipe(). The test deliberately invokes undefined
14236 behavior, and the OpenBSD protections interfere with this. Patch
14237 from "rubiate". Closes ticket 20066.
14239 o Minor features (testing, ipv6):
14240 - Add the single-onion and single-onion-ipv6 chutney targets to
14241 "make test-network-all". This requires a recent chutney version
14242 with the single onion network flavours (git c72a652 or later).
14243 Closes ticket 20072; patch by teor.
14244 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
14245 tests. Remove bridges+hs, as it's somewhat redundant. This
14246 requires a recent chutney version that supports IPv6 clients,
14247 relays, and authorities. Closes ticket 20069; patch by teor.
14249 o Minor features (Tor2web):
14250 - Make Tor2web clients respect ReachableAddresses. This feature was
14251 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
14252 0.2.8.7. Implements feature 20034. Patch by teor.
14254 o Minor features (unit tests):
14255 - We've done significant work to make the unit tests run faster.
14256 - Our link-handshake unit tests now check that when invalid
14257 handshakes fail, they fail with the error messages we expected.
14258 - Our unit testing code that captures log messages no longer
14259 prevents them from being written out if the user asked for them
14260 (by passing --debug or --info or or --notice --warn to the "test"
14261 binary). This change prevents us from missing unexpected log
14262 messages simply because we were looking for others. Related to
14264 - The unit tests now log all warning messages with the "BUG" flag.
14265 Previously, they only logged errors by default. This change will
14266 help us make our testing code more correct, and make sure that we
14267 only hit this code when we mean to. In the meantime, however,
14268 there will be more warnings in the unit test logs than before.
14269 This is preparatory work for ticket 19999.
14270 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
14271 assertion as a test failure.
14273 o Minor bug fixes (circuits):
14274 - Use the CircuitBuildTimeout option whenever
14275 LearnCircuitBuildTimeout is disabled. Previously, we would respect
14276 the option when a user disabled it, but not when it was disabled
14277 because some other option was set. Fixes bug 20073; bugfix on
14278 0.2.4.12-alpha. Patch by teor.
14280 o Minor bugfixes (allocation):
14281 - Change how we allocate memory for large chunks on buffers, to
14282 avoid a (currently impossible) integer overflow, and to waste less
14283 space when allocating unusually large chunks. Fixes bug 20081;
14284 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
14285 - Always include orconfig.h before including any other C headers.
14286 Sometimes, it includes macros that affect the behavior of the
14287 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
14288 first version to use AC_USE_SYSTEM_EXTENSIONS).
14289 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
14290 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
14291 Patch from Gisle Vanem.
14292 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
14293 They apparently require a set of annotations that we aren't
14294 currently using, and they create false positives in our pthreads
14295 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
14297 o Minor bugfixes (directory authority):
14298 - Die with a more useful error when the operator forgets to place
14299 the authority_signing_key file into the keys directory. This
14300 avoids an uninformative assert & traceback about having an invalid
14301 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
14302 - When allowing private addresses, mark Exits that only exit to
14303 private locations as such. Fixes bug 20064; bugfix
14306 o Minor bugfixes (documentation):
14307 - Document the default PathsNeededToBuildCircuits value that's used
14308 by clients when the directory authorities don't set
14309 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
14310 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
14311 - Fix manual for the User option: it takes a username, not a UID.
14312 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
14315 o Minor bugfixes (hidden services):
14316 - Stop logging intro point details to the client log on certain
14317 error conditions. Fixed as part of bug 20012; bugfix on
14318 0.2.4.8-alpha. Patch by teor.
14320 o Minor bugfixes (IPv6, testing):
14321 - Check for IPv6 correctly on Linux when running test networks.
14322 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
14324 o Minor bugfixes (Linux seccomp2 sandbox):
14325 - Add permission to run the sched_yield() and sigaltstack() system
14326 calls, in order to support versions of Tor compiled with asan or
14327 ubsan code that use these calls. Now "sandbox 1" and
14328 "--enable-expensive-hardening" should be compatible on more
14329 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
14331 o Minor bugfixes (logging):
14332 - When logging a message from the BUG() macro, be explicit about
14333 what we were asserting. Previously we were confusing what we were
14334 asserting with what the bug was. Fixes bug 20093; bugfix
14336 - When we are unable to remove the bw_accounting file, do not warn
14337 if the reason we couldn't remove it was that it didn't exist.
14338 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
14340 o Minor bugfixes (option parsing):
14341 - Count unix sockets when counting client listeners (SOCKS, Trans,
14342 NATD, and DNS). This has no user-visible behaviour changes: these
14343 options are set once, and never read. Required for correct
14344 behaviour in ticket 17178. Fixes bug 19677; bugfix on
14345 0.2.6.3-alpha. Patch by teor.
14347 o Minor bugfixes (options):
14348 - Check the consistency of UseEntryGuards and EntryNodes more
14349 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
14351 - Stop changing the configured value of UseEntryGuards on
14352 authorities and Tor2web clients. Fixes bug 20074; bugfix on
14353 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
14356 o Minor bugfixes (Tor2web):
14357 - Prevent Tor2web clients running hidden services, these services
14358 are not anonymous due to the one-hop client paths. Fixes bug
14359 19678. Patch by teor.
14361 o Minor bugfixes (unit tests):
14362 - Fix a shared-random unit test that was failing on big endian
14363 architectures due to internal representation of a integer copied
14364 to a buffer. The test is changed to take a full 32 bytes of data
14365 and use the output of a python script that make the COMMIT and
14366 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
14368 - The tor_tls_server_info_callback unit test no longer crashes when
14369 debug-level logging is turned on. Fixes bug 20041; bugfix
14373 Changes in version 0.2.8.8 - 2016-09-23
14374 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
14375 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
14376 who select public relays as their bridges.
14378 o Major bugfixes (crash):
14379 - Fix a complicated crash bug that could affect Tor clients
14380 configured to use bridges when replacing a networkstatus consensus
14381 in which one of their bridges was mentioned. OpenBSD users saw
14382 more crashes here, but all platforms were potentially affected.
14383 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
14385 o Major bugfixes (relay, OOM handler):
14386 - Fix a timing-dependent assertion failure that could occur when we
14387 tried to flush from a circuit after having freed its cells because
14388 of an out-of-memory condition. Fixes bug 20203; bugfix on
14389 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
14392 o Minor feature (fallback directories):
14393 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
14394 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
14395 2016. Closes ticket 20190; patch by teor.
14397 o Minor features (geoip):
14398 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
14402 Changes in version 0.2.9.2-alpha - 2016-08-24
14403 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
14404 several new features and bugfixes. It also includes an important
14405 authority update and an important bugfix from 0.2.8.7. Everyone who
14406 sets the ReachableAddresses option, and all bridges, are strongly
14407 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
14409 o Directory authority changes (also in 0.2.8.7):
14410 - The "Tonga" bridge authority has been retired; the new bridge
14411 authority is "Bifroest". Closes tickets 19728 and 19690.
14413 o Major bugfixes (client, security, also in 0.2.8.7):
14414 - Only use the ReachableAddresses option to restrict the first hop
14415 in a path. In earlier versions of 0.2.8.x, it would apply to
14416 every hop in the path, with a possible degradation in anonymity
14417 for anyone using an uncommon ReachableAddress setting. Fixes bug
14418 19973; bugfix on 0.2.8.2-alpha.
14420 o Major features (user interface):
14421 - Tor now supports the ability to declare options deprecated, so
14422 that we can recommend that people stop using them. Previously,
14423 this was done in an ad-hoc way. Closes ticket 19820.
14425 o Major bugfixes (directory downloads):
14426 - Avoid resetting download status for consensuses hourly, since we
14427 already have another, smarter retry mechanism. Fixes bug 8625;
14428 bugfix on 0.2.0.9-alpha.
14430 o Minor features (config):
14431 - Warn users when descriptor and port addresses are inconsistent.
14432 Mitigates bug 13953; patch by teor.
14434 o Minor features (geoip):
14435 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
14438 o Minor features (user interface):
14439 - There is a new --list-deprecated-options command-line option to
14440 list all of the deprecated options. Implemented as part of
14443 o Minor bugfixes (code style):
14444 - Fix an integer signedness conversion issue in the case conversion
14445 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
14447 o Minor bugfixes (compilation):
14448 - Build correctly on versions of libevent2 without support for
14449 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
14451 - Fix a compilation warning on GCC versions before 4.6. Our
14452 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
14453 when it is also required as an argument to the compiler pragma.
14454 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
14456 o Minor bugfixes (compilation, also in 0.2.8.7):
14457 - Remove an inappropriate "inline" in tortls.c that was causing
14458 warnings on older versions of GCC. Fixes bug 19903; bugfix
14461 o Minor bugfixes (fallback directories, also in 0.2.8.7):
14462 - Avoid logging a NULL string pointer when loading fallback
14463 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
14464 and 0.2.8.1-alpha. Report and patch by "rubiate".
14466 o Minor bugfixes (logging):
14467 - Log a more accurate message when we fail to dump a microdescriptor.
14468 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
14470 o Minor bugfixes (memory leak):
14471 - Fix a series of slow memory leaks related to parsing torrc files
14472 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
14474 o Deprecated features:
14475 - A number of DNS-cache-related sub-options for client ports are now
14476 deprecated for security reasons, and may be removed in a future
14477 version of Tor. (We believe that client-side DNS caching is a bad
14478 idea for anonymity, and you should not turn it on.) The options
14479 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
14480 UseIPv4Cache, and UseIPv6Cache.
14481 - A number of options are deprecated for security reasons, and may
14482 be removed in a future version of Tor. The options are:
14483 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
14484 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
14485 CloseHSClientCircuitsImmediatelyOnTimeout,
14486 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
14487 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
14488 UseNTorHandshake, and WarnUnsafeSocks.
14489 - The *ListenAddress options are now deprecated as unnecessary: the
14490 corresponding *Port options should be used instead. These options
14491 may someday be removed. The affected options are:
14492 ControlListenAddress, DNSListenAddress, DirListenAddress,
14493 NATDListenAddress, ORListenAddress, SocksListenAddress,
14494 and TransListenAddress.
14497 - Correct the IPv6 syntax in our documentation for the
14498 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
14501 - We no longer include the (dead, deprecated) bufferevent code in
14502 Tor. Closes ticket 19450. Based on a patch from U+039b.
14505 Changes in version 0.2.8.7 - 2016-08-24
14506 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
14507 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
14508 who sets the ReachableAddresses option, and all bridges, are strongly
14509 encouraged to upgrade.
14511 o Directory authority changes:
14512 - The "Tonga" bridge authority has been retired; the new bridge
14513 authority is "Bifroest". Closes tickets 19728 and 19690.
14515 o Major bugfixes (client, security):
14516 - Only use the ReachableAddresses option to restrict the first hop
14517 in a path. In earlier versions of 0.2.8.x, it would apply to
14518 every hop in the path, with a possible degradation in anonymity
14519 for anyone using an uncommon ReachableAddress setting. Fixes bug
14520 19973; bugfix on 0.2.8.2-alpha.
14522 o Minor features (geoip):
14523 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
14526 o Minor bugfixes (compilation):
14527 - Remove an inappropriate "inline" in tortls.c that was causing
14528 warnings on older versions of GCC. Fixes bug 19903; bugfix
14531 o Minor bugfixes (fallback directories):
14532 - Avoid logging a NULL string pointer when loading fallback
14533 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
14534 and 0.2.8.1-alpha. Report and patch by "rubiate".
14537 Changes in version 0.2.9.1-alpha - 2016-08-08
14538 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
14539 series. It improves our support for hardened builds and compiler
14540 warnings, deploys some critical infrastructure for improvements to
14541 hidden services, includes a new timing backend that we hope to use for
14542 better support for traffic padding, makes it easier for programmers to
14543 log unexpected events, and contains other small improvements to
14544 security, correctness, and performance.
14546 Below are the changes since 0.2.8.6.
14548 o New system requirements:
14549 - Tor now requires Libevent version 2.0.10-stable or later. Older
14550 versions of Libevent have less efficient backends for several
14551 platforms, and lack the DNS code that we use for our server-side
14552 DNS support. This implements ticket 19554.
14553 - Tor now requires zlib version 1.2 or later, for security,
14554 efficiency, and (eventually) gzip support. (Back when we started,
14555 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
14556 released in 2003. We recommend the latest version.)
14558 o Major features (build, hardening):
14559 - Tor now builds with -ftrapv by default on compilers that support
14560 it. This option detects signed integer overflow (which C forbids),
14561 and turns it into a hard-failure. We do not apply this option to
14562 code that needs to run in constant time to avoid side-channels;
14563 instead, we use -fwrapv in that code. Closes ticket 17983.
14564 - When --enable-expensive-hardening is selected, stop applying the
14565 clang/gcc sanitizers to code that needs to run in constant time.
14566 Although we are aware of no introduced side-channels, we are not
14567 able to prove that there are none. Related to ticket 17983.
14569 o Major features (compilation):
14570 - Our big list of extra GCC warnings is now enabled by default when
14571 building with GCC (or with anything like Clang that claims to be
14572 GCC-compatible). To make all warnings into fatal compilation
14573 errors, pass --enable-fatal-warnings to configure. Closes
14575 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
14576 turn on C and POSIX extensions. (Previously, we attempted to do
14577 this on an ad hoc basis.) Closes ticket 19139.
14579 o Major features (directory authorities, hidden services):
14580 - Directory authorities can now perform the shared randomness
14581 protocol specified by proposal 250. Using this protocol, directory
14582 authorities generate a global fresh random value every day. In the
14583 future, this value will be used by hidden services to select
14584 HSDirs. This release implements the directory authority feature;
14585 the hidden service side will be implemented in the future as part
14586 of proposal 224. Resolves ticket 16943; implements proposal 250.
14588 o Major features (downloading, random exponential backoff):
14589 - When we fail to download an object from a directory service, wait
14590 for an (exponentially increasing) randomized amount of time before
14591 retrying, rather than a fixed interval as we did before. This
14592 prevents a group of Tor instances from becoming too synchronized,
14593 or a single Tor instance from becoming too predictable, in its
14594 download schedule. Closes ticket 15942.
14596 o Major bugfixes (exit policies):
14597 - Avoid disclosing exit outbound bind addresses, configured port
14598 bind addresses, and local interface addresses in relay descriptors
14599 by default under ExitPolicyRejectPrivate. Instead, only reject
14600 these (otherwise unlisted) addresses if
14601 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
14602 0.2.7.2-alpha. Patch by teor.
14604 o Major bugfixes (hidden service client):
14605 - Allow Tor clients with appropriate controllers to work with
14606 FetchHidServDescriptors set to 0. Previously, this option also
14607 disabled descriptor cache lookup, thus breaking hidden services
14608 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
14610 o Minor features (build, hardening):
14611 - Detect and work around a libclang_rt problem that would prevent
14612 clang from finding __mulodi4() on some 32-bit platforms, and thus
14613 keep -ftrapv from linking on those systems. Closes ticket 19079.
14614 - When building on a system without runtime support for the runtime
14615 hardening options, try to log a useful warning at configuration
14616 time, rather than an incomprehensible warning at link time. If
14617 expensive hardening was requested, this warning becomes an error.
14618 Closes ticket 18895.
14620 o Minor features (code safety):
14621 - In our integer-parsing functions, ensure that maxiumum value we
14622 give is no smaller than the minimum value. Closes ticket 19063;
14625 o Minor features (controller):
14626 - Implement new GETINFO queries for all downloads that use
14627 download_status_t to schedule retries. This allows controllers to
14628 examine the schedule for pending downloads. Closes ticket 19323.
14629 - Allow controllers to configure basic client authorization on
14630 hidden services when they create them with the ADD_ONION control
14631 command. Implements ticket 15588. Patch by "special".
14632 - Fire a STATUS_SERVER controller event whenever the hibernation
14633 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
14635 o Minor features (directory authority):
14636 - Directory authorities now only give the Guard flag to a relay if
14637 they are also giving it the Stable flag. This change allows us to
14638 simplify path selection for clients. It should have minimal effect
14639 in practice, since >99% of Guards already have the Stable flag.
14640 Implements ticket 18624.
14641 - Directory authorities now write their v3-status-votes file out to
14642 disk earlier in the consensus process, so we have a record of the
14643 votes even if we abort the consensus process. Resolves
14646 o Minor features (hidden service):
14647 - Stop being so strict about the payload length of "rendezvous1"
14648 cells. We used to be locked in to the "TAP" handshake length, and
14649 now we can handle better handshakes like "ntor". Resolves
14652 o Minor features (infrastructure, time):
14653 - Tor now uses the operating system's monotonic timers (where
14654 available) for internal fine-grained timing. Previously we would
14655 look at the system clock, and then attempt to compensate for the
14656 clock running backwards. Closes ticket 18908.
14657 - Tor now includes an improved timer backend, so that we can
14658 efficiently support tens or hundreds of thousands of concurrent
14659 timers, as will be needed for some of our planned anti-traffic-
14660 analysis work. This code is based on William Ahern's "timeout.c"
14661 project, which implements a "tickless hierarchical timing wheel".
14662 Closes ticket 18365.
14664 o Minor features (logging):
14665 - Provide a more useful warning message when configured with an
14666 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
14667 - When dumping unparseable router descriptors, optionally store them
14668 in separate files, named by digest, up to a configurable size
14669 limit. You can change the size limit by setting the
14670 MaxUnparseableDescSizeToLog option, and disable this feature by
14671 setting that option to 0. Closes ticket 18322.
14672 - Add a set of macros to check nonfatal assertions, for internal
14673 use. Migrating more of our checks to these should help us avoid
14674 needless crash bugs. Closes ticket 18613.
14676 o Minor features (performance):
14677 - Change the "optimistic data" extension from "off by default" to
14678 "on by default". The default was ordinarily overridden by a
14679 consensus option, but when clients were bootstrapping for the
14680 first time, they would not have a consensus to get the option
14681 from. Changing this default saves a round-trip during startup.
14682 Closes ticket 18815.
14684 o Minor features (relay, usability):
14685 - When the directory authorities refuse a bad relay's descriptor,
14686 encourage the relay operator to contact us. Many relay operators
14687 won't notice this line in their logs, but it's a win if even a few
14688 learn why we don't like what their relay was doing. Resolves
14691 o Minor features (testing):
14692 - Let backtrace tests work correctly under AddressSanitizer. Fixes
14693 part of bug 18934; bugfix on 0.2.5.2-alpha.
14694 - Move the test-network.sh script to chutney, and modify tor's test-
14695 network.sh to call the (newer) chutney version when available.
14696 Resolves ticket 19116. Patch by teor.
14697 - Use the lcov convention for marking lines as unreachable, so that
14698 we don't count them when we're generating test coverage data.
14699 Update our coverage tools to understand this convention. Closes
14702 o Minor bugfixes (bootstrap):
14703 - Remember the directory we fetched the consensus or previous
14704 certificates from, and use it to fetch future authority
14705 certificates. This change improves bootstrapping performance.
14706 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
14708 o Minor bugfixes (build):
14709 - The test-stem and test-network makefile targets now depend only on
14710 the tor binary that they are testing. Previously, they depended on
14711 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
14712 patch from "cypherpunks".
14714 o Minor bugfixes (circuits):
14715 - Make sure extend_info_from_router() is only called on servers.
14716 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
14718 o Minor bugfixes (compilation):
14719 - When building with Clang, use a full set of GCC warnings.
14720 (Previously, we included only a subset, because of the way we
14721 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
14723 o Minor bugfixes (directory authority):
14724 - Authorities now sort the "package" lines in their votes, for ease
14725 of debugging. (They are already sorted in consensus documents.)
14726 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
14727 - When parsing a detached signature, make sure we use the length of
14728 the digest algorithm instead of an hardcoded DIGEST256_LEN in
14729 order to avoid comparing bytes out-of-bounds with a smaller digest
14730 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
14732 o Minor bugfixes (documentation):
14733 - Document the --passphrase-fd option in the tor manpage. Fixes bug
14734 19504; bugfix on 0.2.7.3-rc.
14735 - Fix the description of the --passphrase-fd option in the
14736 tor-gencert manpage. The option is used to pass the number of a
14737 file descriptor to read the passphrase from, not to read the file
14738 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
14740 o Minor bugfixes (ephemeral hidden service):
14741 - When deleting an ephemeral hidden service, close its intro points
14742 even if they are not completely open. Fixes bug 18604; bugfix
14745 o Minor bugfixes (guard selection):
14746 - Use a single entry guard even if the NumEntryGuards consensus
14747 parameter is not provided. Fixes bug 17688; bugfix
14749 - Don't mark guards as unreachable if connection_connect() fails.
14750 That function fails for local reasons, so it shouldn't reveal
14751 anything about the status of the guard. Fixes bug 14334; bugfix
14754 o Minor bugfixes (hidden service client):
14755 - Increase the minimum number of internal circuits we preemptively
14756 build from 2 to 3, so a circuit is available when a client
14757 connects to another onion service. Fixes bug 13239; bugfix
14760 o Minor bugfixes (logging):
14761 - When logging a directory ownership mismatch, log the owning
14762 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
14764 o Minor bugfixes (memory leaks):
14765 - Fix a small, uncommon memory leak that could occur when reading a
14766 truncated ed25519 key file. Fixes bug 18956; bugfix
14769 o Minor bugfixes (testing):
14770 - Allow clients to retry HSDirs much faster in test networks. Fixes
14771 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
14772 - Disable ASAN's detection of segmentation faults while running
14773 test_bt.sh, so that we can make sure that our own backtrace
14774 generation code works. Fixes another aspect of bug 18934; bugfix
14775 on 0.2.5.2-alpha. Patch from "cypherpunks".
14776 - Fix the test-network-all target on out-of-tree builds by using the
14777 correct path to the test driver script. Fixes bug 19421; bugfix
14780 o Minor bugfixes (time):
14781 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
14782 bugfix on all released tor versions.
14783 - When computing the difference between two times in milliseconds,
14784 we now round to the nearest millisecond correctly. Previously, we
14785 could sometimes round in the wrong direction. Fixes bug 19428;
14786 bugfix on 0.2.2.2-alpha.
14788 o Minor bugfixes (user interface):
14789 - Display a more accurate number of suppressed messages in the log
14790 rate-limiter. Previously, there was a potential integer overflow
14791 in the counter. Now, if the number of messages hits a maximum, the
14792 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
14794 - Fix a typo in the passphrase prompt for the ed25519 identity key.
14795 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
14797 o Code simplification and refactoring:
14798 - Remove redundant declarations of the MIN macro. Closes
14800 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
14801 Closes ticket 18462; patch from "icanhasaccount".
14802 - Split the 600-line directory_handle_command_get function into
14803 separate functions for different URL types. Closes ticket 16698.
14806 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
14807 ticket 19153. Patch from "U+039b".
14809 o Removed features:
14810 - Remove support for "GET /tor/bytes.txt" DirPort request, and
14811 "GETINFO dir-usage" controller request, which were only available
14812 via a compile-time option in Tor anyway. Feature was added in
14813 0.2.2.1-alpha. Resolves ticket 19035.
14814 - There is no longer a compile-time option to disable support for
14815 TransPort. (If you don't want TransPort; just don't use it.) Patch
14816 from "U+039b". Closes ticket 19449.
14819 - Run more workqueue tests as part of "make check". These had
14820 previously been implemented, but you needed to know special
14821 command-line options to enable them.
14822 - We now have unit tests for our code to reject zlib "compression
14823 bombs". (Fortunately, the code works fine.)
14826 Changes in version 0.2.8.6 - 2016-08-02
14828 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
14830 The Tor 0.2.8 series improves client bootstrapping performance,
14831 completes the authority-side implementation of improved identity
14832 keys for relays, and includes numerous bugfixes and performance
14833 improvements throughout the program. This release continues to
14834 improve the coverage of Tor's test suite. For a full list of
14835 changes since Tor 0.2.7, see the ReleaseNotes file.
14837 Changes since 0.2.8.5-rc:
14839 o Minor features (geoip):
14840 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
14843 o Minor bugfixes (compilation):
14844 - Fix a compilation warning in the unit tests on systems where char
14845 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
14847 o Minor bugfixes (fallback directories):
14848 - Remove 1 fallback that was on the hardcoded list, then opted-out,
14849 leaving 89 of the 100 fallbacks originally introduced in Tor
14850 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
14852 o Minor bugfixes (Linux seccomp2 sandbox):
14853 - Allow more syscalls when running with "Sandbox 1" enabled:
14854 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
14855 some systems, these are required for Tor to start. Fixes bug
14856 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
14857 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
14858 so that get_interface_address6_via_udp_socket_hack() can work.
14859 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
14862 Changes in version 0.2.8.5-rc - 2016-07-07
14863 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
14864 series. If we find no new bugs or regressions here, the first stable
14865 0.2.8 release will be identical to it. It has a few small bugfixes
14866 against previous versions.
14868 o Directory authority changes:
14869 - Urras is no longer a directory authority. Closes ticket 19271.
14871 o Major bugfixes (heartbeat):
14872 - Fix a regression that would crash Tor when the periodic
14873 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
14874 0.2.8.1-alpha. Reported by "kubaku".
14876 o Minor features (build):
14877 - Tor now again builds with the recent OpenSSL 1.1 development
14878 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
14879 - When building manual pages, set the timezone to "UTC", so that the
14880 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
14881 Patch from intrigeri.
14883 o Minor bugfixes (fallback directory selection):
14884 - Avoid errors during fallback selection if there are no eligible
14885 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
14888 o Minor bugfixes (IPv6, microdescriptors):
14889 - Don't check node addresses when we only have a routerstatus. This
14890 allows IPv6-only clients to bootstrap by fetching microdescriptors
14891 from fallback directory mirrors. (The microdescriptor consensus
14892 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
14895 o Minor bugfixes (logging):
14896 - Reduce pointlessly verbose log messages when directory servers
14897 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
14898 0.2.8.1-alpha. Patch by teor.
14899 - When a fallback directory changes its fingerprint from the hard-
14900 coded fingerprint, log a less severe, more explanatory log
14901 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
14903 o Minor bugfixes (Linux seccomp2 sandboxing):
14904 - Allow statistics to be written to disk when "Sandbox 1" is
14905 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
14906 0.2.6.1-alpha respectively.
14908 o Minor bugfixes (user interface):
14909 - Remove a warning message "Service [scrubbed] not found after
14910 descriptor upload". This message appears when one uses HSPOST
14911 control command to upload a service descriptor. Since there is
14912 only a descriptor and no service, showing this message is
14913 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
14915 o Fallback directory list:
14916 - Add a comment to the generated fallback directory list that
14917 explains how to comment out unsuitable fallbacks in a way that's
14918 compatible with the stem fallback parser.
14919 - Update fallback whitelist and blacklist based on relay operator
14920 emails. Blacklist unsuitable (non-working, over-volatile)
14921 fallbacks. Resolves ticket 19071. Patch by teor.
14922 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
14923 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
14924 ticket 19071; patch by teor.
14927 Changes in version 0.2.8.4-rc - 2016-06-15
14928 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
14929 If we find no new bugs or regressions here, the first stable 0.2.8
14930 release will be identical to it. It has a few small bugfixes against
14933 o Major bugfixes (user interface):
14934 - Correctly give a warning in the cases where a relay is specified
14935 by nickname, and one such relay is found, but it is not officially
14936 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
14938 o Minor features (build):
14939 - Tor now builds once again with the recent OpenSSL 1.1 development
14940 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
14942 o Minor features (geoip):
14943 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
14946 o Minor bugfixes (compilation):
14947 - Cause the unit tests to compile correctly on mingw64 versions that
14948 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
14950 o Minor bugfixes (downloading):
14951 - Predict more correctly whether we'll be downloading over HTTP when
14952 we determine the maximum length of a URL. This should avoid a
14953 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
14957 Changes in version 0.2.8.3-alpha - 2016-05-26
14958 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
14959 the course of the 0.2.8 development cycle. It improves the behavior of
14960 directory clients, fixes several crash bugs, fixes a gap in compiler
14961 hardening, and allows the full integration test suite to run on
14964 o Major bugfixes (security, client, DNS proxy):
14965 - Stop a crash that could occur when a client running with DNSPort
14966 received a query with multiple address types, and the first
14967 address type was not supported. Found and fixed by Scott Dial.
14968 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
14970 o Major bugfixes (security, compilation):
14971 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
14972 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
14973 cause a compiler warning, thereby making other checks fail, and
14974 needlessly disabling compiler-hardening support. Fixes one case of
14975 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
14977 o Major bugfixes (security, directory authorities):
14978 - Fix a crash and out-of-bounds write during authority voting, when
14979 the list of relays includes duplicate ed25519 identity keys. Fixes
14980 bug 19032; bugfix on 0.2.8.2-alpha.
14982 o Major bugfixes (client, bootstrapping):
14983 - Check if bootstrap consensus downloads are still needed when the
14984 linked connection attaches. This prevents tor making unnecessary
14985 begindir-style connections, which are the only directory
14986 connections tor clients make since the fix for 18483 was merged.
14987 - Fix some edge cases where consensus download connections may not
14988 have been closed, even though they were not needed. Related to fix
14990 - Make relays retry consensus downloads the correct number of times,
14991 rather than the more aggressive client retry count. Fixes part of
14993 - Stop downloading consensuses when we have a consensus, even if we
14994 don't have all the certificates for it yet. Fixes bug 18809;
14995 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
14997 o Major bugfixes (directory mirrors):
14998 - Decide whether to advertise begindir support in the the same way
14999 we decide whether to advertise our DirPort. Allowing these
15000 decisions to become out-of-sync led to surprising behavior like
15001 advertising begindir support when hibernation made us not
15002 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
15005 o Major bugfixes (IPv6 bridges, client):
15006 - Actually use IPv6 addresses when selecting directory addresses for
15007 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
15010 o Major bugfixes (key management):
15011 - If OpenSSL fails to generate an RSA key, do not retain a dangling
15012 pointer to the previous (uninitialized) key value. The impact here
15013 should be limited to a difficult-to-trigger crash, if OpenSSL is
15014 running an engine that makes key generation failures possible, or
15015 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
15016 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
15019 o Major bugfixes (testing):
15020 - Fix a bug that would block 'make test-network-all' on systems where
15021 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
15022 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
15023 bugfix on 0.2.8.1-alpha.
15025 o Minor features (clients):
15026 - Make clients, onion services, and bridge relays always use an
15027 encrypted begindir connection for directory requests. Resolves
15028 ticket 18483. Patch by "teor".
15030 o Minor features (fallback directory mirrors):
15031 - Give each fallback the same weight for client selection; restrict
15032 fallbacks to one per operator; report fallback directory detail
15033 changes when rebuilding list; add new fallback directory mirrors
15034 to the whitelist; and many other minor simplifications and fixes.
15035 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
15036 0.2.8.1-alpha; patch by "teor".
15037 - Replace the 21 fallbacks generated in January 2016 and included in
15038 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
15039 2016. Closes task 17158; patch by "teor".
15041 o Minor features (geoip):
15042 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
15045 o Minor bugfixes (assert, portability):
15046 - Fix an assertion failure in memarea.c on systems where "long" is
15047 shorter than the size of a pointer. Fixes bug 18716; bugfix
15050 o Minor bugfixes (bootstrap):
15051 - Consistently use the consensus download schedule for authority
15052 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
15054 o Minor bugfixes (build):
15055 - Remove a pair of redundant AM_CONDITIONAL declarations from
15056 configure.ac. Fixes one final case of bug 17744; bugfix
15058 - Resolve warnings when building on systems that are concerned with
15059 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
15061 - When libscrypt.h is found, but no libscrypt library can be linked,
15062 treat libscrypt as absent. Fixes bug 19161; bugfix
15065 o Minor bugfixes (client):
15066 - Turn all TestingClientBootstrap* into non-testing torrc options.
15067 This changes simply renames them by removing "Testing" in front of
15068 them and they do not require TestingTorNetwork to be enabled
15069 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
15070 - Make directory node selection more reliable, mainly for IPv6-only
15071 clients and clients with few reachable addresses. Fixes bug 18929;
15072 bugfix on 0.2.8.1-alpha. Patch by "teor".
15074 o Minor bugfixes (controller, microdescriptors):
15075 - Make GETINFO dir/status-vote/current/consensus conform to the
15076 control specification by returning "551 Could not open cached
15077 consensus..." when not caching consensuses. Fixes bug 18920;
15078 bugfix on 0.2.2.6-alpha.
15080 o Minor bugfixes (crypto, portability):
15081 - The SHA3 and SHAKE routines now produce the correct output on Big
15082 Endian systems. No code calls either algorithm yet, so this is
15083 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
15084 - Tor now builds again with the recent OpenSSL 1.1 development
15085 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
15088 o Minor bugfixes (directories):
15089 - When fetching extrainfo documents, compare their SHA256 digests
15090 and Ed25519 signing key certificates with the routerinfo that led
15091 us to fetch them, rather than with the most recent routerinfo.
15092 Otherwise we generate many spurious warnings about mismatches.
15093 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
15095 o Minor bugfixes (logging):
15096 - When we can't generate a signing key because OfflineMasterKey is
15097 set, do not imply that we should have been able to load it. Fixes
15098 bug 18133; bugfix on 0.2.7.2-alpha.
15099 - Stop periodic_event_dispatch() from blasting twelve lines per
15100 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
15101 - When rejecting a misformed INTRODUCE2 cell, only log at
15102 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
15104 o Minor bugfixes (pluggable transports):
15105 - Avoid reporting a spurious error when we decide that we don't need
15106 to terminate a pluggable transport because it has already exited.
15107 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
15109 o Minor bugfixes (pointer arithmetic):
15110 - Fix a bug in memarea_alloc() that could have resulted in remote
15111 heap write access, if Tor had ever passed an unchecked size to
15112 memarea_alloc(). Fortunately, all the sizes we pass to
15113 memarea_alloc() are pre-checked to be less than 128 kilobytes.
15114 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
15117 o Minor bugfixes (relays):
15118 - Consider more config options when relays decide whether to
15119 regenerate their descriptor. Fixes more of bug 12538; bugfix
15121 - Resolve some edge cases where we might launch an ORPort
15122 reachability check even when DisableNetwork is set. Noticed while
15123 fixing bug 18616; bugfix on 0.2.3.9-alpha.
15125 o Minor bugfixes (statistics):
15126 - We now include consensus downloads via IPv6 in our directory-
15127 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
15129 o Minor bugfixes (testing):
15130 - Allow directories in small networks to bootstrap by skipping
15131 DirPort checks when the consensus has no exits. Fixes bug 19003;
15132 bugfix on 0.2.8.1-alpha. Patch by teor.
15133 - Fix a small memory leak that would occur when the
15134 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
15135 bugfix on 0.2.5.2-alpha.
15137 o Minor bugfixes (time handling):
15138 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
15139 field. Otherwise, our unit tests crash on Windows. Fixes bug
15140 18977; bugfix on 0.2.2.25-alpha.
15143 - Document the contents of the 'datadir/keys' subdirectory in the
15144 manual page. Closes ticket 17621.
15145 - Stop recommending use of nicknames to identify relays in our
15146 MapAddress documentation. Closes ticket 18312.
15149 Changes in version 0.2.8.2-alpha - 2016-03-28
15150 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
15151 bugs in earlier versions of Tor, including some that prevented
15152 authorities using Tor 0.2.7.x from running correctly. IPv6 and
15153 directory support should also be much improved.
15155 o New system requirements:
15156 - Tor no longer supports versions of OpenSSL with a broken
15157 implementation of counter mode. (This bug was present in OpenSSL
15158 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
15159 longer runs with, these versions.
15160 - Tor no longer attempts to support platforms where the "time_t"
15161 type is unsigned. (To the best of our knowledge, only OpenVMS does
15162 this, and Tor has never actually built on OpenVMS.) Closes
15164 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
15165 later (released in 2008 and 2009 respectively). If you are
15166 building Tor from the git repository instead of from the source
15167 distribution, and your tools are older than this, you will need to
15168 upgrade. Closes ticket 17732.
15170 o Major bugfixes (security, pointers):
15171 - Avoid a difficult-to-trigger heap corruption attack when extending
15172 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
15173 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
15174 Reported by Guido Vranken.
15176 o Major bugfixes (bridges, pluggable transports):
15177 - Modify the check for OR connections to private addresses. Allow
15178 bridges on private addresses, including pluggable transports that
15179 ignore the (potentially private) address in the bridge line. Fixes
15180 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
15182 o Major bugfixes (compilation):
15183 - Repair hardened builds under the clang compiler. Previously, our
15184 use of _FORTIFY_SOURCE would conflict with clang's address
15185 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
15187 o Major bugfixes (crash on shutdown):
15188 - Correctly handle detaching circuits from muxes when shutting down.
15189 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
15190 - Fix an assert-on-exit bug related to counting memory usage in
15191 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
15193 o Major bugfixes (crash on startup):
15194 - Fix a segfault during startup: If a Unix domain socket was
15195 configured as listener (such as a ControlSocket or a SocksPort
15196 "unix:" socket), and tor was started as root but not configured to
15197 switch to another user, tor would segfault while trying to string
15198 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
15201 o Major bugfixes (dns proxy mode, crash):
15202 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
15203 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
15205 o Major bugfixes (relays, bridge clients):
15206 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
15207 bridge clients use the address configured in the bridge line.
15208 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
15211 o Major bugfixes (voting):
15212 - Actually enable support for authorities to match routers by their
15213 Ed25519 identities. Previously, the code had been written, but
15214 some debugging code that had accidentally been left in the
15215 codebase made it stay turned off. Fixes bug 17702; bugfix
15217 - When collating votes by Ed25519 identities, authorities now
15218 include a "NoEdConsensus" flag if the ed25519 value (or lack
15219 thereof) for a server does not reflect the majority consensus.
15220 Related to bug 17668; bugfix on 0.2.7.2-alpha.
15221 - When generating a vote with keypinning disabled, never include two
15222 entries for the same ed25519 identity. This bug was causing
15223 authorities to generate votes that they could not parse when a
15224 router violated key pinning by changing its RSA identity but
15225 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
15226 18318. Bugfix on 0.2.7.2-alpha.
15228 o Minor features (security, win32):
15229 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
15230 attack. Fixes bug 18123; bugfix on all tor versions. Patch
15233 o Minor features (bug-resistance):
15234 - Make Tor survive errors involving connections without a
15235 corresponding event object. Previously we'd fail with an
15236 assertion; now we produce a log message. Related to bug 16248.
15238 o Minor features (build):
15239 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
15240 as having possible IPFW support. Closes ticket 18448. Patch from
15241 Steven Chamberlain.
15243 o Minor features (code hardening):
15244 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
15245 level code, to harden against accidental failures to NUL-
15246 terminate. Part of ticket 17852. Patch from jsturgix. Found
15249 o Minor features (crypto):
15250 - Validate the hard-coded Diffie-Hellman parameters and ensure that
15251 p is a safe prime, and g is a suitable generator. Closes
15254 o Minor features (geoip):
15255 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
15258 o Minor features (hidden service directory):
15259 - Streamline relay-side hsdir handling: when relays consider whether
15260 to accept an uploaded hidden service descriptor, they no longer
15261 check whether they are one of the relays in the network that is
15262 "supposed" to handle that descriptor. Implements ticket 18332.
15264 o Minor features (IPv6):
15265 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
15266 to 1, tor prefers IPv6 directory addresses.
15267 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
15268 avoids using IPv4 for client OR and directory connections.
15269 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
15270 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
15271 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
15273 o Minor features (linux seccomp2 sandbox):
15274 - Reject attempts to change our Address with "Sandbox 1" enabled.
15275 Changing Address with Sandbox turned on would never actually work,
15276 but previously it would fail in strange and confusing ways. Found
15277 while fixing 18548.
15279 o Minor features (robustness):
15280 - Exit immediately with an error message if the code attempts to use
15281 Libevent without having initialized it. This should resolve some
15282 frequently-made mistakes in our unit tests. Closes ticket 18241.
15284 o Minor features (unix domain sockets):
15285 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
15286 Unix domain sockets without checking the permissions on the parent
15287 directory. (Tor checks permissions by default because some
15288 operating systems only check permissions on the parent directory.
15289 However, some operating systems do look at permissions on the
15290 socket, and tor's default check is unneeded.) Closes ticket 18458.
15293 o Minor bugfixes (exit policies, security):
15294 - Refresh an exit relay's exit policy when interface addresses
15295 change. Previously, tor only refreshed the exit policy when the
15296 configured external address changed. Fixes bug 18208; bugfix on
15297 0.2.7.3-rc. Patch by teor.
15299 o Minor bugfixes (security, hidden services):
15300 - Prevent hidden services connecting to client-supplied rendezvous
15301 addresses that are reserved as internal or multicast. Fixes bug
15302 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
15304 o Minor bugfixes (build):
15305 - Do not link the unit tests against both the testing and non-
15306 testing versions of the static libraries. Fixes bug 18490; bugfix
15308 - Avoid spurious failures from configure files related to calling
15309 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
15310 0.2.0.1-alpha. Patch from "cypherpunks".
15311 - Silence spurious clang-scan warnings in the ed25519_donna code by
15312 explicitly initializing some objects. Fixes bug 18384; bugfix on
15313 0.2.7.2-alpha. Patch by teor.
15315 o Minor bugfixes (client, bootstrap):
15316 - Count receipt of new microdescriptors as progress towards
15317 bootstrapping. Previously, with EntryNodes set, Tor might not
15318 successfully repopulate the guard set on bootstrapping. Fixes bug
15319 16825; bugfix on 0.2.3.1-alpha.
15321 o Minor bugfixes (code correctness):
15322 - Update to the latest version of Trunnel, which tries harder to
15323 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
15324 by clang address sanitizer. Fixes bug 18373; bugfix
15327 o Minor bugfixes (configuration):
15328 - Fix a tiny memory leak when parsing a port configuration ending in
15329 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
15331 o Minor bugfixes (containers):
15332 - If we somehow attempt to construct a heap with more than
15333 1073741822 elements, avoid an integer overflow when maintaining
15334 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
15336 o Minor bugfixes (correctness):
15337 - Fix a bad memory handling bug that would occur if we had queued a
15338 cell on a channel's incoming queue. Fortunately, we can't actually
15339 queue a cell like that as our code is constructed today, but it's
15340 best to avoid this kind of error, even if there isn't any code
15341 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
15343 o Minor bugfixes (directory):
15344 - When generating a URL for a directory server on an IPv6 address,
15345 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
15346 on 0.2.3.9-alpha. Patch from Malek.
15348 o Minor bugfixes (fallback directory mirrors):
15349 - When requesting extrainfo descriptors from a trusted directory
15350 server, check whether it is an authority or a fallback directory
15351 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
15352 0.2.4.7-alpha. Reported by atagar, patch by teor.
15354 o Minor bugfixes (hidden service, client):
15355 - Handle the case where the user makes several fast consecutive
15356 requests to the same .onion address. Previously, the first six
15357 requests would each trigger a descriptor fetch, each picking a
15358 directory (there are 6 overall) and the seventh one would fail
15359 because no directories were left, thereby triggering a close on
15360 all current directory connections asking for the hidden service.
15361 The solution here is to not close the connections if we have
15362 pending directory fetches. Fixes bug 15937; bugfix
15365 o Minor bugfixes (hidden service, control port):
15366 - Add the onion address to the HS_DESC event for the UPLOADED action
15367 both on success or failure. It was previously hardcoded with
15368 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
15370 o Minor bugfixes (hidden service, directory):
15371 - Bridges now refuse "rendezvous2" (hidden service descriptor)
15372 publish attempts. Suggested by ticket 18332.
15374 o Minor bugfixes (linux seccomp2 sandbox):
15375 - Allow the setrlimit syscall, and the prlimit and prlimit64
15376 syscalls, which some libc implementations use under the hood.
15377 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
15378 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
15379 enabled and no DNS resolvers configured. This should help TAILS
15380 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
15381 - Fix the sandbox's interoperability with unix domain sockets under
15382 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
15384 o Minor bugfixes (logging):
15385 - When logging information about an unparsable networkstatus vote or
15386 consensus, do not say "vote" when we mean consensus. Fixes bug
15387 18368; bugfix on 0.2.0.8-alpha.
15388 - Scrub service name in "unrecognized service ID" log messages.
15389 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
15390 - Downgrade logs and backtraces about IP versions to info-level.
15391 Only log backtraces once each time tor runs. Assists in diagnosing
15392 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
15393 Christian, patch by teor.
15395 o Minor bugfixes (memory safety):
15396 - Avoid freeing an uninitialized pointer when opening a socket fails
15397 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
15398 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
15400 - Correctly duplicate addresses in get_interface_address6_list().
15401 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
15402 patch by "cypherpunks".
15403 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
15405 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
15406 18672; bugfix on 0.2.5.1-alpha.
15408 o Minor bugfixes (private directory):
15409 - Prevent a race condition when creating private directories. Fixes
15410 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
15411 Patch from jsturgix. Found with Flawfinder.
15413 o Minor bugfixes (test networks, IPv6):
15414 - Allow internal IPv6 addresses in descriptors in test networks.
15415 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
15418 o Minor bugfixes (testing):
15419 - We no longer disable assertions in the unit tests when coverage is
15420 enabled. Instead, we require you to say --disable-asserts-in-tests
15421 to the configure script if you need assertions disabled in the
15422 unit tests (for example, if you want to perform branch coverage).
15423 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
15425 o Minor bugfixes (time parsing):
15426 - Avoid overflow in tor_timegm when parsing dates in and after 2038
15427 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
15428 0.0.2pre14. Patch by teor.
15430 o Minor bugfixes (tor-gencert):
15431 - Correctly handle the case where an authority operator enters a
15432 passphrase but sends an EOF before sending a newline. Fixes bug
15433 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
15435 o Code simplification and refactoring:
15436 - Quote all the string interpolations in configure.ac -- even those
15437 which we are pretty sure can't contain spaces. Closes ticket
15438 17744. Patch from zerosion.
15439 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
15440 inplace, so there's no need to have a separate implementation for
15441 the non-inplace code. Closes ticket 18258. Patch from Malek.
15442 - Simplify return types for some crypto functions that can't
15443 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
15446 - Change build messages to refer to "Fedora" instead of "Fedora
15447 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
15448 Patches from "icanhasaccount" and "cypherpunks".
15450 o Removed features:
15451 - We no longer maintain an internal freelist in memarea.c.
15452 Allocators should be good enough to make this code unnecessary,
15453 and it's doubtful that it ever had any performance benefit.
15456 - Fix several warnings from clang's address sanitizer produced in
15458 - Treat backtrace test failures as expected on FreeBSD until we
15459 solve bug 17808. Closes ticket 18204.
15462 Changes in version 0.2.8.1-alpha - 2016-02-04
15463 Tor 0.2.8.1-alpha is the first alpha release in its series. It
15464 includes numerous small features and bugfixes against previous Tor
15465 versions, and numerous small infrastructure improvements. The most
15466 notable features are a set of improvements to the directory subsystem.
15468 o Major features (security, Linux):
15469 - When Tor starts as root on Linux and is told to switch user ID, it
15470 can now retain the capability to bind to low ports. By default,
15471 Tor will do this only when it's switching user ID and some low
15472 ports have been configured. You can change this behavior with the
15473 new option KeepBindCapabilities. Closes ticket 8195.
15475 o Major features (directory system):
15476 - When bootstrapping multiple consensus downloads at a time, use the
15477 first one that starts downloading, and close the rest. This
15478 reduces failures when authorities or fallback directories are slow
15479 or down. Together with the code for feature 15775, this feature
15480 should reduces failures due to fallback churn. Implements ticket
15481 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
15482 "mikeperry" and "teor".
15483 - Include a trial list of 21 default fallback directories, generated
15484 in January 2016, based on an opt-in survey of suitable relays.
15485 Doing this should make clients bootstrap more quickly and reliably,
15486 and reduce the load on the directory authorities. Closes ticket
15487 15775. Patch by "teor".
15488 Candidates identified using an OnionOO script by "weasel", "teor",
15489 "gsathya", and "karsten".
15490 - Previously only relays that explicitly opened a directory port
15491 (DirPort) accepted directory requests from clients. Now all
15492 relays, with and without a DirPort, accept and serve tunneled
15493 directory requests that they receive through their ORPort. You can
15494 disable this behavior using the new DirCache option. Closes
15497 o Major key updates:
15498 - Update the V3 identity key for the dannenberg directory authority:
15499 it was changed on 18 November 2015. Closes task 17906. Patch
15502 o Minor features (security, clock):
15503 - Warn when the system clock appears to move back in time (when the
15504 state file was last written in the future). Tor doesn't know that
15505 consensuses have expired if the clock is in the past. Patch by
15506 "teor". Implements ticket 17188.
15508 o Minor features (security, exit policies):
15509 - ExitPolicyRejectPrivate now rejects more private addresses by
15510 default. Specifically, it now rejects the relay's outbound bind
15511 addresses (if configured), and the relay's configured port
15512 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
15513 0.2.0.11-alpha. Patch by "teor".
15515 o Minor features (security, memory erasure):
15516 - Set the unused entries in a smartlist to NULL. This helped catch
15517 a (harmless) bug, and shouldn't affect performance too much.
15518 Implements ticket 17026.
15519 - Use SecureMemoryWipe() function to securely clean memory on
15520 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
15521 Implements feature 17986.
15522 - Use explicit_bzero or memset_s when present. Previously, we'd use
15523 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
15524 from <logan@hackers.mu> and <selven@hackers.mu>.
15525 - Make memwipe() do nothing when passed a NULL pointer or buffer of
15526 zero size. Check size argument to memwipe() for underflow. Fixes
15527 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
15530 o Minor features (security, RNG):
15531 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
15532 positively are not allowed to fail. Previously we depended on
15533 internal details of OpenSSL's behavior. Closes ticket 17686.
15534 - Never use the system entropy output directly for anything besides
15535 seeding the PRNG. When we want to generate important keys, instead
15536 of using system entropy directly, we now hash it with the PRNG
15537 stream. This may help resist certain attacks based on broken OS
15538 entropy implementations. Closes part of ticket 17694.
15539 - Use modern system calls (like getentropy() or getrandom()) to
15540 generate strong entropy on platforms that have them. Closes
15543 o Minor features (accounting):
15544 - Added two modes to the AccountingRule option: One for limiting
15545 only the number of bytes sent ("AccountingRule out"), and one for
15546 limiting only the number of bytes received ("AccountingRule in").
15547 Closes ticket 15989; patch from "unixninja92".
15549 o Minor features (build):
15550 - Since our build process now uses "make distcheck", we no longer
15551 force "make dist" to depend on "make check". Closes ticket 17893;
15552 patch from "cypherpunks."
15553 - Tor now builds successfully with the recent OpenSSL 1.1
15554 development branch, and with the latest LibreSSL. Closes tickets
15555 17549, 17921, and 17984.
15557 o Minor features (controller):
15558 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
15559 tickets 16774 and 17817. Patch by George Tankersley.
15560 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
15561 service descriptor from a service's local hidden service
15562 descriptor cache. Closes ticket 14846.
15563 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
15564 controllers can examine the the reject rules added by
15565 ExitPolicyRejectPrivate. This makes it easier for stem to display
15568 o Minor features (crypto):
15569 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
15571 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
15572 - When allocating a digest state object, allocate no more space than
15573 we actually need. Previously, we would allocate as much space as
15574 the state for the largest algorithm would need. This change saves
15575 up to 672 bytes per circuit. Closes ticket 17796.
15576 - Improve performance when hashing non-multiple of 8 sized buffers,
15577 based on Andrew Moon's public domain SipHash-2-4 implementation.
15578 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
15580 o Minor features (directory downloads):
15581 - Wait for busy authorities and fallback directories to become non-
15582 busy when bootstrapping. (A similar change was made in 6c443e987d
15583 for directory caches chosen from the consensus.) Closes ticket
15584 17864; patch by "teor".
15585 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
15586 directory mirrors. The default is 1; set it to 0 to disable
15587 fallbacks. Implements ticket 17576. Patch by "teor".
15589 o Minor features (geoip):
15590 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
15593 o Minor features (IPv6):
15594 - Add an argument 'ipv6=address:orport' to the DirAuthority and
15595 FallbackDir torrc options, to specify an IPv6 address for an
15596 authority or fallback directory. Add hard-coded ipv6 addresses for
15597 directory authorities that have them. Closes ticket 17327; patch
15598 from Nick Mathewson and "teor".
15599 - Add address policy assume_action support for IPv6 addresses.
15600 - Limit IPv6 mask bits to 128.
15601 - Warn when comparing against an AF_UNSPEC address in a policy, it's
15602 almost always a bug. Closes ticket 17863; patch by "teor".
15603 - Allow users to configure directory authorities and fallback
15604 directory servers with IPv6 addresses and ORPorts. Resolves
15606 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
15607 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
15608 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
15609 17638; bugfix on 0.0.2pre8. Patch by "teor".
15611 o Minor features (logging):
15612 - When logging to syslog, allow a tag to be added to the syslog
15613 identity (the string prepended to every log message). The tag can
15614 be configured with SyslogIdentityTag and defaults to none. Setting
15615 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
15618 o Minor features (portability):
15619 - Use timingsafe_memcmp() where available. Closes ticket 17944;
15620 patch from <logan@hackers.mu>.
15622 o Minor features (relay, address discovery):
15623 - Add a family argument to get_interface_addresses_raw() and
15624 subfunctions to make network interface address interogation more
15625 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
15626 types of interfaces from the operating system. Resolves
15628 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
15629 fails to enumerate interface addresses using the platform-specific
15630 API, have it rely on the UDP socket fallback technique to try and
15631 find out what IP addresses (both IPv4 and IPv6) our machine has.
15632 Resolves ticket 17951.
15634 o Minor features (replay cache):
15635 - The replay cache now uses SHA256 instead of SHA1. Implements
15636 feature 8961. Patch by "teor", issue reported by "rransom".
15638 o Minor features (unix file permissions):
15639 - Defer creation of Unix sockets until after setuid. This avoids
15640 needing CAP_CHOWN and CAP_FOWNER when using systemd's
15641 CapabilityBoundingSet, or chown and fowner when using SELinux.
15642 Implements part of ticket 17562. Patch from Jamie Nguyen.
15643 - If any directory created by Tor is marked as group readable, the
15644 filesystem group is allowed to be either the default GID or the
15645 root user. Allowing root to read the DataDirectory prevents the
15646 need for CAP_READ_SEARCH when using systemd's
15647 CapabilityBoundingSet, or dac_read_search when using SELinux.
15648 Implements part of ticket 17562. Patch from Jamie Nguyen.
15649 - Introduce a new DataDirectoryGroupReadable option. If it is set to
15650 1, the DataDirectory will be made readable by the default GID.
15651 Implements part of ticket 17562. Patch from Jamie Nguyen.
15653 o Minor bugfixes (accounting):
15654 - The max bandwidth when using 'AccountRule sum' is now correctly
15655 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
15656 from "unixninja92".
15658 o Minor bugfixes (code correctness):
15659 - When closing an entry connection, generate a warning if we should
15660 have sent an end cell for it but we haven't. Fixes bug 17876;
15661 bugfix on 0.2.3.2-alpha.
15662 - Assert that allocated memory held by the reputation code is freed
15663 according to its internal counters. Fixes bug 17753; bugfix
15665 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
15668 o Minor bugfixes (compilation):
15669 - Mark all object files that include micro-revision.i as depending
15670 on it, so as to make parallel builds more reliable. Fixes bug
15671 17826; bugfix on 0.2.5.1-alpha.
15672 - Don't try to use the pthread_condattr_setclock() function unless
15673 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
15674 17819; bugfix on 0.2.6.3-alpha.
15675 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
15677 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
15678 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
15679 - Fix search for libevent libraries on OpenBSD (and other systems
15680 that install libevent 1 and libevent 2 in parallel). Fixes bug
15681 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
15682 - Isolate environment variables meant for tests from the rest of the
15683 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
15684 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
15686 - Remove config.log only from make distclean, not from make clean.
15687 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
15689 o Minor bugfixes (crypto):
15690 - Check the return value of HMAC() and assert on failure. Fixes bug
15691 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
15693 o Minor bugfixes (fallback directories):
15694 - Mark fallbacks as "too busy" when they return a 503 response,
15695 rather than just marking authorities. Fixes bug 17572; bugfix on
15696 0.2.4.7-alpha. Patch by "teor".
15698 o Minor bugfixes (IPv6):
15699 - Update the limits in max_dl_per_request for IPv6 address length.
15700 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
15702 o Minor bugfixes (linux seccomp2 sandbox):
15703 - Fix a crash when using offline master ed25519 keys with the Linux
15704 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
15706 o Minor bugfixes (logging):
15707 - In log messages that include a function name, use __FUNCTION__
15708 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
15709 with clang __PRETTY_FUNCTION__ has extra information we don't
15710 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
15712 - Remove needless quotes from a log message about unparseable
15713 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
15715 o Minor bugfixes (portability):
15716 - Remove an #endif from configure.ac so that we correctly detect the
15717 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
15720 o Minor bugfixes (relays):
15721 - Check that both the ORPort and DirPort (if present) are reachable
15722 before publishing a relay descriptor. Otherwise, relays publish a
15723 descriptor with DirPort 0 when the DirPort reachability test takes
15724 longer than the ORPort reachability test. Fixes bug 18050; bugfix
15725 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
15727 o Minor bugfixes (relays, hidden services):
15728 - Refuse connection requests to private OR addresses unless
15729 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
15730 then refuse to send any cells to a private address. Fixes bugs
15731 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
15733 o Minor bugfixes (safe logging):
15734 - When logging a malformed hostname received through socks4, scrub
15735 it if SafeLogging says we should. Fixes bug 17419; bugfix
15738 o Minor bugfixes (statistics code):
15739 - Consistently check for overflow in round_*_to_next_multiple_of
15740 functions, and add unit tests with additional and maximal values.
15741 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
15742 - Handle edge cases in the laplace functions: avoid division by
15743 zero, avoid taking the log of zero, and silence clang type
15744 conversion warnings using round and trunc. Add unit tests for edge
15745 cases with maximal values. Fixes part of bug 13192; bugfix
15748 o Minor bugfixes (testing):
15749 - The test for log_heartbeat was incorrectly failing in timezones
15750 with non-integer offsets. Instead of comparing the end of the time
15751 string against a constant, compare it to the output of
15752 format_local_iso_time when given the correct input. Fixes bug
15753 18039; bugfix on 0.2.5.4-alpha.
15754 - Make unit tests pass on IPv6-only systems, and systems without
15755 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
15756 bugfix on 0.2.7.3-rc. Patch by "teor".
15757 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
15759 - Check the full results of SHA256 and SHA512 digests in the unit
15760 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
15762 o Code simplification and refactoring:
15763 - Move logging of redundant policy entries in
15764 policies_parse_exit_policy_internal into its own function. Closes
15765 ticket 17608; patch from "juce".
15766 - Extract the more complicated parts of circuit_mark_for_close()
15767 into a new function that we run periodically before circuits are
15768 freed. This change removes more than half of the functions
15769 currently in the "blob". Closes ticket 17218.
15770 - Clean up a little duplicated code in
15771 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
15773 - Decouple the list of streams waiting to be attached to circuits
15774 from the overall connection list. This change makes it possible to
15775 attach streams quickly while simplifying Tor's callgraph and
15776 avoiding O(N) scans of the entire connection list. Closes
15778 - When a direct directory request fails immediately on launch,
15779 instead of relaunching that request from inside the code that
15780 launches it, instead mark the connection for teardown. This change
15781 simplifies Tor's callback and prevents the directory-request
15782 launching code from invoking itself recursively. Closes
15784 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
15785 use them. Closes ticket 17926.
15788 - Add a description of the correct use of the '--keygen' command-
15789 line option. Closes ticket 17583; based on text by 's7r'.
15790 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
15791 - Explain actual minima for BandwidthRate. Closes ticket 16382.
15792 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
15793 - Mention torspec URL in the manpage and point the reader to it
15794 whenever we mention a document that belongs in torspce. Fixes
15797 o Removed features:
15798 - Remove client-side support for connecting to Tor relays running
15799 versions of Tor before 0.2.3.6-alpha. These relays didn't support
15800 the v3 TLS handshake protocol, and are no longer allowed on the
15801 Tor network. Implements the client side of ticket 11150. Based on
15802 patches by Tom van der Woerdt.
15805 - Add unit tests to check for common RNG failure modes, such as
15806 returning all zeroes, identical values, or incrementing values
15807 (OpenSSL's rand_predictable feature). Patch by "teor".
15808 - Log more information when the backtrace tests fail. Closes ticket
15809 17892. Patch from "cypherpunks."
15810 - Always test both ed25519 backends, so that we can be sure that our
15811 batch-open replacement code works. Part of ticket 16794.
15812 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
15813 portion of ticket 16831.
15814 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
15815 util_format.c, directory.c, and options_validate.c. Closes tickets
15816 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
15818 - Unit tests for directory_handle_command_get. Closes ticket 17004.
15819 Patch from Reinaldo de Souza Jr.
15822 Changes in version 0.2.7.6 - 2015-12-10
15823 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
15824 well as a minor bug in hidden service reliability.
15826 o Major bugfixes (guard selection):
15827 - Actually look at the Guard flag when selecting a new directory
15828 guard. When we implemented the directory guard design, we
15829 accidentally started treating all relays as if they have the Guard
15830 flag during guard selection, leading to weaker anonymity and worse
15831 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
15834 o Minor features (geoip):
15835 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
15838 o Minor bugfixes (compilation):
15839 - When checking for net/pfvar.h, include netinet/in.h if possible.
15840 This fixes transparent proxy detection on OpenBSD. Fixes bug
15841 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
15842 - Fix a compilation warning with Clang 3.6: Do not check the
15843 presence of an address which can never be NULL. Fixes bug 17781.
15845 o Minor bugfixes (correctness):
15846 - When displaying an IPv6 exit policy, include the mask bits
15847 correctly even when the number is greater than 31. Fixes bug
15848 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
15849 - The wrong list was used when looking up expired intro points in a
15850 rend service object, causing what we think could be reachability
15851 issues for hidden services, and triggering a BUG log. Fixes bug
15852 16702; bugfix on 0.2.7.2-alpha.
15853 - Fix undefined behavior in the tor_cert_checksig function. Fixes
15854 bug 17722; bugfix on 0.2.7.2-alpha.
15857 Changes in version 0.2.7.5 - 2015-11-20
15858 The Tor 0.2.7 release series is dedicated to the memory of Tor user
15859 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
15860 tirelessly to advocate human rights regardless of national borders,
15861 and oppose the encroachments of mass surveillance. He opposed national
15862 exceptionalism, he brought clarity to legal and policy debates, he
15863 understood and predicted the impact of mass surveillance on the world,
15864 and he laid the groundwork for resisting it. While serving on the Tor
15865 Project's board of directors, he brought us his uncompromising focus
15866 on technical excellence in the service of humankind. Caspar was an
15867 inimitable force for good and a wonderful friend. He was kind,
15868 humorous, generous, gallant, and believed we should protect one
15869 another without exception. We honor him here for his ideals, his
15870 efforts, and his accomplishments. Please honor his memory with works
15871 that would make him proud.
15873 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
15875 The 0.2.7 series adds a more secure identity key type for relays,
15876 improves cryptography performance, resolves several longstanding
15877 hidden-service performance issues, improves controller support for
15878 hidden services, and includes small bugfixes and performance
15879 improvements throughout the program. This release series also includes
15880 more tests than before, and significant simplifications to which parts
15881 of Tor invoke which others.
15883 (This release contains no code changes since 0.2.7.4-rc.)
15886 Changes in version 0.2.7.4-rc - 2015-10-21
15887 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
15888 fixes some important memory leaks, and a scary-looking (but mostly
15889 harmless in practice) invalid-read bug. It also has a few small
15890 bugfixes, notably fixes for compilation and portability on different
15891 platforms. If no further significant bounds are found, the next
15892 release will the the official stable release.
15894 o Major bugfixes (security, correctness):
15895 - Fix an error that could cause us to read 4 bytes before the
15896 beginning of an openssl string. This bug could be used to cause
15897 Tor to crash on systems with unusual malloc implementations, or
15898 systems with unusual hardening installed. Fixes bug 17404; bugfix
15901 o Major bugfixes (correctness):
15902 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
15903 bug 17401; bugfix on 0.2.7.3-rc.
15905 o Major bugfixes (memory leaks):
15906 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
15907 17398; bugfix on 0.2.6.1-alpha.
15908 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
15909 17402; bugfix on 0.2.7.3-rc.
15910 - Fix a memory leak when reading an expired signing key from disk.
15911 Fixes bug 17403; bugfix on 0.2.7.2-rc.
15913 o Minor features (geoIP):
15914 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
15917 o Minor bugfixes (compilation):
15918 - Repair compilation with the most recent (unreleased, alpha)
15919 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
15920 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
15921 17251; bugfix on 0.2.7.2-alpha.
15922 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
15923 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
15925 o Minor bugfixes (portability):
15926 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
15927 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
15930 o Minor bugfixes (sandbox):
15931 - Add the "hidserv-stats" filename to our sandbox filter for the
15932 HiddenServiceStatistics option to work properly. Fixes bug 17354;
15933 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
15935 o Minor bugfixes (testing):
15936 - Add unit tests for get_interface_address* failure cases. Fixes bug
15937 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
15938 - Fix breakage when running 'make check' with BSD make. Fixes bug
15939 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
15940 - Make the get_ifaddrs_* unit tests more tolerant of different
15941 network configurations. (Don't assume every test box has an IPv4
15942 address, and don't assume every test box has a non-localhost
15943 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
15944 - Skip backtrace tests when backtrace support is not compiled in.
15945 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
15949 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
15950 - Note that HiddenServicePorts can take a unix domain socket. Closes
15954 Changes in version 0.2.7.3-rc - 2015-09-25
15955 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
15956 contains numerous usability fixes for Ed25519 keys, safeguards against
15957 several misconfiguration problems, significant simplifications to
15958 Tor's callgraph, and numerous bugfixes and small features.
15960 This is the most tested release of Tor to date. The unit tests cover
15961 39.40% of the code, and the integration tests (accessible with "make
15962 test-full-online", requiring stem and chutney and a network
15963 connection) raise the coverage to 64.49%.
15965 o Major features (security, hidden services):
15966 - Hidden services, if using the EntryNodes option, are required to
15967 use more than one EntryNode, in order to avoid a guard discovery
15968 attack. (This would only affect people who had configured hidden
15969 services and manually specified the EntryNodes option with a
15970 single entry-node. The impact was that it would be easy to
15971 remotely identify the guard node used by such a hidden service.
15972 See ticket for more information.) Fixes ticket 14917.
15974 o Major features (Ed25519 keys, keypinning):
15975 - The key-pinning option on directory authorities is now advisory-
15976 only by default. In a future version, or when the AuthDirPinKeys
15977 option is set, pins are enforced again. Disabling key-pinning
15978 seemed like a good idea so that we can survive the fallout of any
15979 usability problems associated with Ed25519 keys. Closes
15982 o Major features (Ed25519 performance):
15983 - Improve the speed of Ed25519 operations and Curve25519 keypair
15984 generation when built targeting 32 bit x86 platforms with SSE2
15985 available. Implements ticket 16535.
15986 - Improve the runtime speed of Ed25519 signature verification by
15987 using Ed25519-donna's batch verification support. Implements
15990 o Major features (performance testing):
15991 - The test-network.sh script now supports performance testing.
15992 Requires corresponding chutney performance testing changes. Patch
15993 by "teor". Closes ticket 14175.
15995 o Major features (relay, Ed25519):
15996 - Significant usability improvements for Ed25519 key management. Log
15997 messages are better, and the code can recover from far more
15998 failure conditions. Thanks to "s7r" for reporting and diagnosing
16000 - Add a new OfflineMasterKey option to tell Tor never to try loading
16001 or generating a secret Ed25519 identity key. You can use this in
16002 combination with tor --keygen to manage offline and/or encrypted
16003 Ed25519 keys. Implements ticket 16944.
16004 - Add a --newpass option to allow changing or removing the
16005 passphrase of an encrypted key with tor --keygen. Implements part
16007 - On receiving a HUP signal, check to see whether the Ed25519
16008 signing key has changed, and reload it if so. Closes ticket 16790.
16010 o Major bugfixes (relay, Ed25519):
16011 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
16012 0.2.7.2-alpha. Reported by "s7r".
16013 - Improve handling of expired signing keys with offline master keys.
16014 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
16016 o Minor features (client-side privacy):
16017 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
16018 lifespan when IsolateSOCKSAuth and streams with SOCKS
16019 authentication are attached to the circuit. This allows
16020 applications like TorBrowser to manage circuit lifetime on their
16021 own. Implements feature 15482.
16022 - When logging malformed hostnames from SOCKS5 requests, respect
16023 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
16025 o Minor features (compilation):
16026 - Give a warning as early as possible when trying to build with an
16027 unsupported OpenSSL version. Closes ticket 16901.
16028 - Fail during configure if we're trying to build against an OpenSSL
16029 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
16030 which started requiring ECC.
16032 o Minor features (geoip):
16033 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
16036 o Minor features (hidden services):
16037 - Relays need to have the Fast flag to get the HSDir flag. As this
16038 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
16039 drop. This change should make some attacks against the hidden
16040 service directory system harder. Fixes ticket 15963.
16041 - Turn on hidden service statistics collection by setting the torrc
16042 option HiddenServiceStatistics to "1" by default. (This keeps
16043 track only of the fraction of traffic used by hidden services, and
16044 the total number of hidden services in existence.) Closes
16046 - Client now uses an introduction point failure cache to know when
16047 to fetch or keep a descriptor in their cache. Previously, failures
16048 were recorded implicitly, but not explicitly remembered. Closes
16051 o Minor features (testing, authorities, documentation):
16052 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
16053 explicitly manage consensus flags in testing networks. Patch by
16054 "robgjansen", modified by "teor". Implements part of ticket 14882.
16056 o Minor bugfixes (security, exit policies):
16057 - ExitPolicyRejectPrivate now also rejects the relay's published
16058 IPv6 address (if any), and any publicly routable IPv4 or IPv6
16059 addresses on any local interfaces. ticket 17027. Patch by "teor".
16060 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
16062 o Minor bug fixes (torrc exit policies):
16063 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
16064 produce IPv6 wildcard addresses. Previously they would produce
16065 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
16066 of bug 16069; bugfix on 0.2.4.7-alpha.
16067 - When parsing torrc ExitPolicies, we now warn for a number of cases
16068 where the user's intent is likely to differ from Tor's actual
16069 behavior. These include: using an IPv4 address with an accept6 or
16070 reject6 line; using "private" on an accept6 or reject6 line; and
16071 including any ExitPolicy lines after accept *:* or reject *:*.
16072 Related to ticket 16069.
16073 - When parsing torrc ExitPolicies, we now issue an info-level
16074 message when expanding an "accept/reject *" line to include both
16075 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
16076 - In each instance above, usage advice is provided to avoid the
16077 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
16078 16069; bugfix on 0.2.4.7-alpha.
16080 o Minor bugfixes (authority):
16081 - Don't assign "HSDir" to a router if it isn't Valid and Running.
16082 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
16083 - Downgrade log messages about Ed25519 key issues if they are in old
16084 cached router descriptors. Fixes part of bug 16286; bugfix
16086 - When we find an Ed25519 key issue in a cached descriptor, stop
16087 saying the descriptor was just "uploaded". Fixes another part of
16088 bug 16286; bugfix on 0.2.7.2-alpha.
16090 o Minor bugfixes (control port):
16091 - Repair a warning and a spurious result when getting the maximum
16092 number of file descriptors from the controller. Fixes bug 16697;
16093 bugfix on 0.2.7.2-alpha.
16095 o Minor bugfixes (correctness):
16096 - When calling channel_free_list(), avoid calling smartlist_remove()
16097 while inside a FOREACH loop. This partially reverts commit
16098 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
16099 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
16101 o Minor bugfixes (documentation):
16102 - Advise users on how to configure separate IPv4 and IPv6 exit
16103 policies in the manpage and sample torrcs. Related to ticket 16069.
16104 - Fix the usage message of tor-resolve(1) so that it no longer lists
16105 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
16106 - Fix an error in the manual page and comments for
16107 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
16108 required "ORPort connectivity". While this is true, it is in no
16109 way unique to the HSDir flag. Of all the flags, only HSDirs need a
16110 DirPort configured in order for the authorities to assign that
16111 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
16114 o Minor bugfixes (Ed25519):
16115 - Fix a memory leak when reading router descriptors with expired
16116 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
16118 o Minor bugfixes (linux seccomp2 sandbox):
16119 - Allow bridge authorities to run correctly under the seccomp2
16120 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
16121 - Allow routers with ed25519 keys to run correctly under the
16122 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
16124 o Minor bugfixes (open file limit):
16125 - Fix set_max_file_descriptors() to set by default the max open file
16126 limit to the current limit when setrlimit() fails. Fixes bug
16127 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
16129 o Minor bugfixes (portability):
16130 - Try harder to normalize the exit status of the Tor process to the
16131 standard-provided range. Fixes bug 16975; bugfix on every version
16133 - Check correctly for Windows socket errors in the workqueue
16134 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
16135 - Fix the behavior of crypto_rand_time_range() when told to consider
16136 times before 1970. (These times were possible when running in a
16137 simulated network environment where time()'s output starts at
16138 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
16139 - Restore correct operation of TLS client-cipher detection on
16140 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
16142 o Minor bugfixes (relay):
16143 - Ensure that worker threads actually exit when a fatal error or
16144 shutdown is indicated. This fix doesn't currently affect the
16145 behavior of Tor, because Tor workers never indicates fatal error
16146 or shutdown except in the unit tests. Fixes bug 16868; bugfix
16148 - Unblock threads before releasing the work queue mutex to ensure
16149 predictable scheduling behavior. Fixes bug 16644; bugfix
16152 o Code simplification and refactoring:
16153 - Change the function that's called when we need to retry all
16154 downloads so that it only reschedules the downloads to happen
16155 immediately, rather than launching them all at once itself. This
16156 further simplifies Tor's callgraph.
16157 - Move some format-parsing functions out of crypto.c and
16158 crypto_curve25519.c into crypto_format.c and/or util_format.c.
16159 - Move the client-only parts of init_keys() into a separate
16160 function. Closes ticket 16763.
16161 - Simplify the microdesc_free() implementation so that it no longer
16162 appears (to code analysis tools) to potentially invoke a huge
16163 suite of other microdesc functions.
16164 - Simply the control graph further by deferring the inner body of
16165 directory_all_unreachable() into a callback. Closes ticket 16762.
16166 - Treat the loss of an owning controller as equivalent to a SIGTERM
16167 signal. This removes a tiny amount of duplicated code, and
16168 simplifies our callgraph. Closes ticket 16788.
16169 - When generating an event to send to the controller, we no longer
16170 put the event over the network immediately. Instead, we queue
16171 these events, and use a Libevent callback to deliver them. This
16172 change simplifies Tor's callgraph by reducing the number of
16173 functions from which all other Tor functions are reachable. Closes
16175 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
16176 that try to scan or compile every file on Unix won't decide that
16178 - Remove the unused "nulterminate" argument from buf_pullup().
16181 - Recommend a 40 GB example AccountingMax in torrc.sample rather
16182 than a 4 GB max. Closes ticket 16742.
16183 - Include the TUNING document in our source tarball. It is referred
16184 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
16188 - The internal pure-C tor-fw-helper tool is now removed from the Tor
16189 distribution, in favor of the pure-Go clone available from
16190 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
16191 used by the C tor-fw-helper are not, in our opinion, very
16192 confidence- inspiring in their secure-programming techniques.
16193 Closes ticket 13338.
16194 - Remove the code that would try to aggressively flush controller
16195 connections while writing to them. This code was introduced in
16196 0.1.2.7-alpha, in order to keep output buffers from exceeding
16197 their limits. But there is no longer a maximum output buffer size,
16198 and flushing data in this way caused some undesirable recursions
16199 in our call graph. Closes ticket 16480.
16202 - Make "bridges+hs" the default test network. This tests almost all
16203 tor functionality during make test-network, while allowing tests
16204 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
16205 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
16206 (chutney). Patches by "teor".
16207 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
16208 by-side in the same parent directory. Closes ticket 16903. Patch
16210 - Use environment variables rather than autoconf substitutions to
16211 send variables from the build system to the test scripts. This
16212 change should be easier to maintain, and cause 'make distcheck' to
16213 work better than before. Fixes bug 17148.
16214 - Add a new set of callgraph analysis scripts that use clang to
16215 produce a list of which Tor functions are reachable from which
16216 other Tor functions. We're planning to use these to help simplify
16217 our code structure by identifying illogical dependencies.
16218 - Add new 'test-full' and 'test-full-online' targets to run all
16219 tests, including integration tests with stem and chutney.
16220 - Make the test-workqueue test work on Windows by initializing the
16221 network before we begin.
16222 - New make target (make test-network-all) to run multiple applicable
16223 chutney test cases. Patch from Teor; closes 16953.
16224 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
16225 functions in dns.c. Implements a portion of ticket 16831.
16226 - When building Tor with testing coverage enabled, run Chutney tests
16227 (if any) using the 'tor-cov' coverage binary.
16228 - When running test-network or test-stem, check for the absence of
16229 stem/chutney before doing any build operations.
16232 Changes in version 0.2.7.2-alpha - 2015-07-27
16233 This, the second alpha in the Tor 0.2.7 series, has a number of new
16234 features, including a way to manually pick the number of introduction
16235 points for hidden services, and the much stronger Ed25519 signing key
16236 algorithm for regular Tor relays (including support for encrypted
16237 offline identity keys in the new algorithm).
16239 Support for Ed25519 on relays is currently limited to signing router
16240 descriptors; later alphas in this series will extend Ed25519 key
16241 support to more parts of the Tor protocol.
16243 o Major features (Ed25519 identity keys, Proposal 220):
16244 - All relays now maintain a stronger identity key, using the Ed25519
16245 elliptic curve signature format. This master key is designed so
16246 that it can be kept offline. Relays also generate an online
16247 signing key, and a set of other Ed25519 keys and certificates.
16248 These are all automatically regenerated and rotated as needed.
16249 Implements part of ticket 12498.
16250 - Directory authorities now vote on Ed25519 identity keys along with
16251 RSA1024 keys. Implements part of ticket 12498.
16252 - Directory authorities track which Ed25519 identity keys have been
16253 used with which RSA1024 identity keys, and do not allow them to
16254 vary freely. Implements part of ticket 12498.
16255 - Microdescriptors now include Ed25519 identity keys. Implements
16256 part of ticket 12498.
16257 - Add support for offline encrypted Ed25519 master keys. To use this
16258 feature on your tor relay, run "tor --keygen" to make a new master
16259 key (or to make a new signing key if you already have a master
16260 key). Closes ticket 13642.
16262 o Major features (Hidden services):
16263 - Add the torrc option HiddenServiceNumIntroductionPoints, to
16264 specify a fixed number of introduction points. Its maximum value
16265 is 10 and default is 3. Using this option can increase a hidden
16266 service's reliability under load, at the cost of making it more
16267 visible that the hidden service is facing extra load. Closes
16269 - Remove the adaptive algorithm for choosing the number of
16270 introduction points, which used to change the number of
16271 introduction points (poorly) depending on the number of
16272 connections the HS sees. Closes ticket 4862.
16274 o Major features (onion key cross-certification):
16275 - Relay descriptors now include signatures of their own identity
16276 keys, made using the TAP and ntor onion keys. These signatures
16277 allow relays to prove ownership of their own onion keys. Because
16278 of this change, microdescriptors will no longer need to include
16279 RSA identity keys. Implements proposal 228; closes ticket 12499.
16281 o Major features (performance):
16282 - Improve the runtime speed of Ed25519 operations by using the
16283 public-domain Ed25519-donna by Andrew M. ("floodyberry").
16284 Implements ticket 16467.
16285 - Improve the runtime speed of the ntor handshake by using an
16286 optimized curve25519 basepoint scalarmult implementation from the
16287 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
16288 ideas by Adam Langley. Implements ticket 9663.
16290 o Major bugfixes (client-side privacy, also in 0.2.6.9):
16291 - Properly separate out each SOCKSPort when applying stream
16292 isolation. The error occurred because each port's session group
16293 was being overwritten by a default value when the listener
16294 connection was initialized. Fixes bug 16247; bugfix on
16295 0.2.6.3-alpha. Patch by "jojelino".
16297 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
16298 - Stop refusing to store updated hidden service descriptors on a
16299 client. This reverts commit 9407040c59218 (which indeed fixed bug
16300 14219, but introduced a major hidden service reachability
16301 regression detailed in bug 16381). This is a temporary fix since
16302 we can live with the minor issue in bug 14219 (it just results in
16303 some load on the network) but the regression of 16381 is too much
16304 of a setback. First-round fix for bug 16381; bugfix
16307 o Major bugfixes (hidden services):
16308 - When cannibalizing a circuit for an introduction point, always
16309 extend to the chosen exit node (creating a 4 hop circuit).
16310 Previously Tor would use the current circuit exit node, which
16311 changed the original choice of introduction point, and could cause
16312 the hidden service to skip excluded introduction points or
16313 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
16316 o Major bugfixes (open file limit):
16317 - The open file limit wasn't checked before calling
16318 tor_accept_socket_nonblocking(), which would make Tor exceed the
16319 limit. Now, before opening a new socket, Tor validates the open
16320 file limit just before, and if the max has been reached, return an
16321 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
16323 o Major bugfixes (stability, also in 0.2.6.10):
16324 - Stop crashing with an assertion failure when parsing certain kinds
16325 of malformed or truncated microdescriptors. Fixes bug 16400;
16326 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
16327 by "cypherpunks_backup".
16328 - Stop random client-side assertion failures that could occur when
16329 connecting to a busy hidden service, or connecting to a hidden
16330 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
16333 o Minor features (directory authorities, security, also in 0.2.6.9):
16334 - The HSDir flag given by authorities now requires the Stable flag.
16335 For the current network, this results in going from 2887 to 2806
16336 HSDirs. Also, it makes it harder for an attacker to launch a sybil
16337 attack by raising the effort for a relay to become Stable to
16338 require at the very least 7 days, while maintaining the 96 hours
16339 uptime requirement for HSDir. Implements ticket 8243.
16341 o Minor features (client):
16342 - Relax the validation of hostnames in SOCKS5 requests, allowing the
16343 character '_' to appear, in order to cope with domains observed in
16344 the wild that are serving non-RFC compliant records. Resolves
16346 - Relax the validation done to hostnames in SOCKS5 requests, and
16347 allow a single trailing '.' to cope with clients that pass FQDNs
16348 using that syntax to explicitly indicate that the domain name is
16349 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
16350 - Add GroupWritable and WorldWritable options to unix-socket based
16351 SocksPort and ControlPort options. These options apply to a single
16352 socket, and override {Control,Socks}SocketsGroupWritable. Closes
16355 o Minor features (control protocol):
16356 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
16357 the control protocol. Resolves ticket 15358.
16359 o Minor features (directory authorities):
16360 - Directory authorities no longer vote against the "Fast", "Stable",
16361 and "HSDir" flags just because they were going to vote against
16362 "Running": if the consensus turns out to be that the router was
16363 running, then the authority's vote should count. Patch from Peter
16364 Retzlaff; closes issue 8712.
16366 o Minor features (geoip, also in 0.2.6.10):
16367 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
16368 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
16370 o Minor features (hidden services):
16371 - Add the new options "HiddenServiceMaxStreams" and
16372 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
16373 limit the maximum number of simultaneous streams per circuit, and
16374 optionally tear down the circuit when the limit is exceeded. Part
16377 o Minor features (portability):
16378 - Use C99 variadic macros when the compiler is not GCC. This avoids
16379 failing compilations on MSVC, and fixes a log-file-based race
16380 condition in our old workarounds. Original patch from Gisle Vanem.
16382 o Minor bugfixes (compilation, also in 0.2.6.9):
16383 - Build with --enable-systemd correctly when libsystemd is
16384 installed, but systemd is not. Fixes bug 16164; bugfix on
16385 0.2.6.3-alpha. Patch from Peter Palfrader.
16387 o Minor bugfixes (controller):
16388 - Add the descriptor ID in each HS_DESC control event. It was
16389 missing, but specified in control-spec.txt. Fixes bug 15881;
16390 bugfix on 0.2.5.2-alpha.
16392 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
16393 - Check for failures from crypto_early_init, and refuse to continue.
16394 A previous typo meant that we could keep going with an
16395 uninitialized crypto library, and would have OpenSSL initialize
16396 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
16397 when implementing ticket 4900. Patch by "teor".
16399 o Minor bugfixes (hidden services):
16400 - Fix a crash when reloading configuration while at least one
16401 configured and one ephemeral hidden service exists. Fixes bug
16402 16060; bugfix on 0.2.7.1-alpha.
16403 - Avoid crashing with a double-free bug when we create an ephemeral
16404 hidden service but adding it fails for some reason. Fixes bug
16405 16228; bugfix on 0.2.7.1-alpha.
16407 o Minor bugfixes (Linux seccomp2 sandbox):
16408 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
16409 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
16411 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
16412 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
16413 these when eventfd2() support is missing. Fixes bug 16363; bugfix
16414 on 0.2.6.3-alpha. Patch from "teor".
16416 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
16417 - Fix sandboxing to work when running as a relay, by allowing the
16418 renaming of secret_id_key, and allowing the eventfd2 and futex
16419 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
16421 - Allow systemd connections to work with the Linux seccomp2 sandbox
16422 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16425 o Minor bugfixes (relay):
16426 - Fix a rarely-encountered memory leak when failing to initialize
16427 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
16428 from "cypherpunks".
16430 o Minor bugfixes (systemd):
16431 - Fix an accidental formatting error that broke the systemd
16432 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
16433 - Tor's systemd unit file no longer contains extraneous spaces.
16434 These spaces would sometimes confuse tools like deb-systemd-
16435 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
16437 o Minor bugfixes (tests):
16438 - Use the configured Python executable when running test-stem-full.
16439 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
16441 o Minor bugfixes (tests, also in 0.2.6.9):
16442 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16443 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16445 o Minor bugfixes (threads, comments):
16446 - Always initialize return value in compute_desc_id in rendcommon.c
16447 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16448 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
16449 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16450 - Remove undefined directive-in-macro in test_util_writepid clang
16451 3.7 complains that using a preprocessor directive inside a macro
16452 invocation in test_util_writepid in test_util.c is undefined.
16453 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
16455 o Code simplification and refactoring:
16456 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
16457 to ensure they remain consistent and visible everywhere.
16458 - Remove some vestigial workarounds for the MSVC6 compiler. We
16459 haven't supported that in ages.
16460 - The link authentication code has been refactored for better
16461 testability and reliability. It now uses code generated with the
16462 "trunnel" binary encoding generator, to reduce the risk of bugs
16463 due to programmer error. Done as part of ticket 12498.
16466 - Include a specific and (hopefully) accurate documentation of the
16467 torrc file's meta-format in doc/torrc_format.txt. This is mainly
16468 of interest to people writing programs to parse or generate torrc
16469 files. This document is not a commitment to long-term
16470 compatibility; some aspects of the current format are a bit
16471 ridiculous. Closes ticket 2325.
16473 o Removed features:
16474 - Tor no longer supports copies of OpenSSL that are missing support
16475 for Elliptic Curve Cryptography. (We began using ECC when
16476 available in 0.2.4.8-alpha, for more safe and efficient key
16477 negotiation.) In particular, support for at least one of P256 or
16478 P224 is now required, with manual configuration needed if only
16479 P224 is available. Resolves ticket 16140.
16480 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
16481 on an operating system that has not upgraded to OpenSSL 1.0 or
16482 later, and you compile Tor from source, you will need to install a
16483 more recent OpenSSL to link Tor against.) These versions of
16484 OpenSSL are still supported by the OpenSSL, but the numerous
16485 cryptographic improvements in later OpenSSL releases makes them a
16486 clear choice. Resolves ticket 16034.
16487 - Remove the HidServDirectoryV2 option. Now all relays offer to
16488 store hidden service descriptors. Related to 16543.
16489 - Remove the VoteOnHidServDirectoriesV2 option, since all
16490 authorities have long set it to 1. Closes ticket 16543.
16493 - Document use of coverity, clang static analyzer, and clang dynamic
16494 undefined behavior and address sanitizers in doc/HACKING. Include
16495 detailed usage instructions in the blacklist. Patch by "teor".
16496 Closes ticket 15817.
16497 - The link authentication protocol code now has extensive tests.
16498 - The relay descriptor signature testing code now has
16500 - The test_workqueue program now runs faster, and is enabled by
16501 default as a part of "make check".
16502 - Now that OpenSSL has its own scrypt implementation, add an unit
16503 test that checks for interoperability between libscrypt_scrypt()
16504 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
16505 and rely on EVP_PBE_scrypt() whenever possible. Resolves
16509 Changes in version 0.2.6.10 - 2015-07-12
16510 Tor version 0.2.6.10 fixes some significant stability and hidden
16511 service client bugs, bulletproofs the cryptography init process, and
16512 fixes a bug when using the sandbox code with some older versions of
16513 Linux. Everyone running an older version, especially an older version
16514 of 0.2.6, should upgrade.
16516 o Major bugfixes (hidden service clients, stability):
16517 - Stop refusing to store updated hidden service descriptors on a
16518 client. This reverts commit 9407040c59218 (which indeed fixed bug
16519 14219, but introduced a major hidden service reachability
16520 regression detailed in bug 16381). This is a temporary fix since
16521 we can live with the minor issue in bug 14219 (it just results in
16522 some load on the network) but the regression of 16381 is too much
16523 of a setback. First-round fix for bug 16381; bugfix
16526 o Major bugfixes (stability):
16527 - Stop crashing with an assertion failure when parsing certain kinds
16528 of malformed or truncated microdescriptors. Fixes bug 16400;
16529 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
16530 by "cypherpunks_backup".
16531 - Stop random client-side assertion failures that could occur when
16532 connecting to a busy hidden service, or connecting to a hidden
16533 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
16536 o Minor features (geoip):
16537 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
16538 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
16540 o Minor bugfixes (crypto error-handling):
16541 - Check for failures from crypto_early_init, and refuse to continue.
16542 A previous typo meant that we could keep going with an
16543 uninitialized crypto library, and would have OpenSSL initialize
16544 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
16545 when implementing ticket 4900. Patch by "teor".
16547 o Minor bugfixes (Linux seccomp2 sandbox):
16548 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
16549 these when eventfd2() support is missing. Fixes bug 16363; bugfix
16550 on 0.2.6.3-alpha. Patch from "teor".
16553 Changes in version 0.2.6.9 - 2015-06-11
16554 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
16555 requirements for receiving an HSDir flag, and addresses some other small
16556 bugs in the systemd and sandbox code. Clients using circuit isolation
16557 should upgrade; all directory authorities should upgrade.
16559 o Major bugfixes (client-side privacy):
16560 - Properly separate out each SOCKSPort when applying stream
16561 isolation. The error occurred because each port's session group was
16562 being overwritten by a default value when the listener connection
16563 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
16566 o Minor feature (directory authorities, security):
16567 - The HSDir flag given by authorities now requires the Stable flag.
16568 For the current network, this results in going from 2887 to 2806
16569 HSDirs. Also, it makes it harder for an attacker to launch a sybil
16570 attack by raising the effort for a relay to become Stable which
16571 takes at the very least 7 days to do so and by keeping the 96
16572 hours uptime requirement for HSDir. Implements ticket 8243.
16574 o Minor bugfixes (compilation):
16575 - Build with --enable-systemd correctly when libsystemd is
16576 installed, but systemd is not. Fixes bug 16164; bugfix on
16577 0.2.6.3-alpha. Patch from Peter Palfrader.
16579 o Minor bugfixes (Linux seccomp2 sandbox):
16580 - Fix sandboxing to work when running as a relaymby renaming of
16581 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
16582 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
16583 - Allow systemd connections to work with the Linux seccomp2 sandbox
16584 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
16587 o Minor bugfixes (tests):
16588 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
16589 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
16592 Changes in version 0.2.6.8 - 2015-05-21
16593 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
16594 fixes an authority-side bug in assigning the HSDir flag. All directory
16595 authorities should upgrade.
16597 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
16598 - Revert commit that made directory authorities assign the HSDir
16599 flag to relays without a DirPort; this was bad because such relays
16600 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
16603 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
16604 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
16605 a client authorized hidden service. Fixes bug 15823; bugfix
16608 o Minor features (geoip):
16609 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
16610 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
16614 Changes in version 0.2.7.1-alpha - 2015-05-12
16615 Tor 0.2.7.1-alpha is the first alpha release in its series. It
16616 includes numerous small features and bugfixes against previous Tor
16617 versions, and numerous small infrastructure improvements. The most
16618 notable features are several new ways for controllers to interact with
16619 the hidden services subsystem.
16621 o New system requirements:
16622 - Tor no longer includes workarounds to support Libevent versions
16623 before 1.3e. Libevent 2.0 or later is recommended. Closes
16626 o Major features (controller):
16627 - Add the ADD_ONION and DEL_ONION commands that allow the creation
16628 and management of hidden services via the controller. Closes
16630 - New "GETINFO onions/current" and "GETINFO onions/detached"
16631 commands to get information about hidden services created via the
16632 controller. Part of ticket 6411.
16633 - New HSFETCH command to launch a request for a hidden service
16634 descriptor. Closes ticket 14847.
16635 - New HSPOST command to upload a hidden service descriptor. Closes
16636 ticket 3523. Patch by "DonnchaC".
16638 o Major bugfixes (hidden services):
16639 - Revert commit that made directory authorities assign the HSDir
16640 flag to relays without a DirPort; this was bad because such relays
16641 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
16644 o Minor features (clock-jump tolerance):
16645 - Recover better when our clock jumps back many hours, like might
16646 happen for Tails or Whonix users who start with a very wrong
16647 hardware clock, use Tor to discover a more accurate time, and then
16648 fix their clock. Resolves part of ticket 8766.
16650 o Minor features (command-line interface):
16651 - Make --hash-password imply --hush to prevent unnecessary noise.
16652 Closes ticket 15542. Patch from "cypherpunks".
16653 - Print a warning whenever we find a relative file path being used
16654 as torrc option. Resolves issue 14018.
16656 o Minor features (controller):
16657 - Add DirAuthority lines for default directory authorities to the
16658 output of the "GETINFO config/defaults" command if not already
16659 present. Implements ticket 14840.
16660 - Controllers can now use "GETINFO hs/client/desc/id/..." to
16661 retrieve items from the client's hidden service descriptor cache.
16662 Closes ticket 14845.
16663 - Implement a new controller command "GETINFO status/fresh-relay-
16664 descs" to fetch a descriptor/extrainfo pair that was generated on
16665 demand just for the controller's use. Implements ticket 14784.
16667 o Minor features (DoS-resistance):
16668 - Make it harder for attackers to overload hidden services with
16669 introductions, by blocking multiple introduction requests on the
16670 same circuit. Resolves ticket 15515.
16672 o Minor features (geoip):
16673 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
16674 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
16677 o Minor features (HS popularity countermeasure):
16678 - To avoid leaking HS popularity, don't cycle the introduction point
16679 when we've handled a fixed number of INTRODUCE2 cells but instead
16680 cycle it when a random number of introductions is reached, thus
16681 making it more difficult for an attacker to find out the amount of
16682 clients that have used the introduction point for a specific HS.
16683 Closes ticket 15745.
16685 o Minor features (logging):
16686 - Include the Tor version in all LD_BUG log messages, since people
16687 tend to cut and paste those into the bugtracker. Implements
16690 o Minor features (pluggable transports):
16691 - When launching managed pluggable transports on Linux systems,
16692 attempt to have the kernel deliver a SIGTERM on tor exit if the
16693 pluggable transport process is still running. Resolves
16695 - When launching managed pluggable transports, setup a valid open
16696 stdin in the child process that can be used to detect if tor has
16697 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
16698 can be used by implementations to detect this new behavior.
16699 Resolves ticket 15435.
16701 o Minor features (testing):
16702 - Add a test to verify that the compiler does not eliminate our
16703 memwipe() implementation. Closes ticket 15377.
16704 - Add make rule `check-changes` to verify the format of changes
16705 files. Closes ticket 15180.
16706 - Add unit tests for control_event_is_interesting(). Add a compile-
16707 time check that the number of events doesn't exceed the capacity
16708 of control_event_t.event_mask. Closes ticket 15431, checks for
16709 bugs similar to 13085. Patch by "teor".
16710 - Command-line argument tests moved to Stem. Resolves ticket 14806.
16711 - Integrate the ntor, backtrace, and zero-length keys tests into the
16712 automake test suite. Closes ticket 15344.
16713 - Remove assertions during builds to determine Tor's test coverage.
16714 We don't want to trigger these even in assertions, so including
16715 them artificially makes our branch coverage look worse than it is.
16716 This patch provides the new test-stem-full and coverage-html-full
16717 configure options. Implements ticket 15400.
16719 o Minor bugfixes (build):
16720 - Improve out-of-tree builds by making non-standard rules work and
16721 clean up additional files and directories. Fixes bug 15053; bugfix
16724 o Minor bugfixes (command-line interface):
16725 - When "--quiet" is provided along with "--validate-config", do not
16726 write anything to stdout on success. Fixes bug 14994; bugfix
16728 - When complaining about bad arguments to "--dump-config", use
16729 stderr, not stdout.
16731 o Minor bugfixes (configuration, unit tests):
16732 - Only add the default fallback directories when the DirAuthorities,
16733 AlternateDirAuthority, and FallbackDir directory config options
16734 are set to their defaults. The default fallback directory list is
16735 currently empty, this fix will only change tor's behavior when it
16736 has default fallback directories. Includes unit tests for
16737 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
16738 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
16740 o Minor bugfixes (correctness):
16741 - For correctness, avoid modifying a constant string in
16742 handle_control_postdescriptor. Fixes bug 15546; bugfix
16744 - Remove side-effects from tor_assert() calls. This was harmless,
16745 because we never disable assertions, but it is bad style and
16746 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
16749 o Minor bugfixes (hidden service):
16750 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
16751 a client authorized hidden service. Fixes bug 15823; bugfix
16753 - Remove an extraneous newline character from the end of hidden
16754 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
16756 o Minor bugfixes (interface):
16757 - Print usage information for --dump-config when it is used without
16758 an argument. Also, fix the error message to use different wording
16759 and add newline at the end. Fixes bug 15541; bugfix
16762 o Minor bugfixes (logs):
16763 - When building Tor under Clang, do not include an extra set of
16764 parentheses in log messages that include function names. Fixes bug
16765 15269; bugfix on every released version of Tor when compiled with
16766 recent enough Clang.
16768 o Minor bugfixes (network):
16769 - When attempting to use fallback technique for network interface
16770 lookup, disregard loopback and multicast addresses since they are
16771 unsuitable for public communications.
16773 o Minor bugfixes (statistics):
16774 - Disregard the ConnDirectionStatistics torrc options when Tor is
16775 not a relay since in that mode of operation no sensible data is
16776 being collected and because Tor might run into measurement hiccups
16777 when running as a client for some time, then becoming a relay.
16778 Fixes bug 15604; bugfix on 0.2.2.35.
16780 o Minor bugfixes (test networks):
16781 - When self-testing reachability, use ExtendAllowPrivateAddresses to
16782 determine if local/private addresses imply reachability. The
16783 previous fix used TestingTorNetwork, which implies
16784 ExtendAllowPrivateAddresses, but this excluded rare configurations
16785 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
16786 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
16787 issue discovered by CJ Ess.
16789 o Minor bugfixes (testing):
16790 - Check for matching value in server response in ntor_ref.py. Fixes
16791 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
16793 - Set the severity correctly when testing
16794 get_interface_addresses_ifaddrs() and
16795 get_interface_addresses_win32(), so that the tests fail gracefully
16796 instead of triggering an assertion. Fixes bug 15759; bugfix on
16797 0.2.6.3-alpha. Reported by Nicolas Derive.
16799 o Code simplification and refactoring:
16800 - Move the hacky fallback code out of get_interface_address6() into
16801 separate function and get it covered with unit-tests. Resolves
16803 - Refactor hidden service client-side cache lookup to intelligently
16804 report its various failure cases, and disentangle failure cases
16805 involving a lack of introduction points. Closes ticket 14391.
16806 - Use our own Base64 encoder instead of OpenSSL's, to allow more
16807 control over the output. Part of ticket 15652.
16810 - Improve the descriptions of statistics-related torrc options in
16811 the manpage to describe rationale and possible uses cases. Fixes
16813 - Improve the layout and formatting of ./configure --help messages.
16814 Closes ticket 15024. Patch from "cypherpunks".
16815 - Standardize on the term "server descriptor" in the manual page.
16816 Previously, we had used "router descriptor", "server descriptor",
16817 and "relay descriptor" interchangeably. Part of ticket 14987.
16820 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
16821 and always use the internal Base64 decoder. The internal decoder
16822 has been part of tor since 0.2.0.10-alpha, and no one should
16823 be using the OpenSSL one. Part of ticket 15652.
16824 - Remove the 'tor_strclear()' function; use memwipe() instead.
16825 Closes ticket 14922.
16827 o Removed features:
16828 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
16829 fingerprinting we now recommend pluggable transports; for forward-
16830 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
16831 - Remove the undocumented "--digests" command-line option. It
16832 complicated our build process, caused subtle build issues on
16833 multiple platforms, and is now redundant since we started
16834 including git version identifiers. Closes ticket 14742.
16835 - Tor no longer contains checks for ancient directory cache versions
16836 that didn't know about microdescriptors.
16837 - Tor no longer contains workarounds for stat files generated by
16838 super-old versions of Tor that didn't choose guards sensibly.
16841 Changes in version 0.2.4.27 - 2015-04-06
16842 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
16843 could be used by an attacker to crash hidden services, or crash clients
16844 visiting hidden services. Hidden services should upgrade as soon as
16845 possible; clients should upgrade whenever packages become available.
16847 This release also backports a simple improvement to make hidden
16848 services a bit less vulnerable to denial-of-service attacks.
16850 o Major bugfixes (security, hidden service):
16851 - Fix an issue that would allow a malicious client to trigger an
16852 assertion failure and halt a hidden service. Fixes bug 15600;
16853 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16854 - Fix a bug that could cause a client to crash with an assertion
16855 failure when parsing a malformed hidden service descriptor. Fixes
16856 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16858 o Minor features (DoS-resistance, hidden service):
16859 - Introduction points no longer allow multiple INTRODUCE1 cells to
16860 arrive on the same circuit. This should make it more expensive for
16861 attackers to overwhelm hidden services with introductions.
16862 Resolves ticket 15515.
16865 Changes in version 0.2.5.12 - 2015-04-06
16866 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
16867 could be used by an attacker to crash hidden services, or crash clients
16868 visiting hidden services. Hidden services should upgrade as soon as
16869 possible; clients should upgrade whenever packages become available.
16871 This release also backports a simple improvement to make hidden
16872 services a bit less vulnerable to denial-of-service attacks.
16874 o Major bugfixes (security, hidden service):
16875 - Fix an issue that would allow a malicious client to trigger an
16876 assertion failure and halt a hidden service. Fixes bug 15600;
16877 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16878 - Fix a bug that could cause a client to crash with an assertion
16879 failure when parsing a malformed hidden service descriptor. Fixes
16880 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16882 o Minor features (DoS-resistance, hidden service):
16883 - Introduction points no longer allow multiple INTRODUCE1 cells to
16884 arrive on the same circuit. This should make it more expensive for
16885 attackers to overwhelm hidden services with introductions.
16886 Resolves ticket 15515.
16889 Changes in version 0.2.6.7 - 2015-04-06
16890 Tor 0.2.6.7 fixes two security issues that could be used by an
16891 attacker to crash hidden services, or crash clients visiting hidden
16892 services. Hidden services should upgrade as soon as possible; clients
16893 should upgrade whenever packages become available.
16895 This release also contains two simple improvements to make hidden
16896 services a bit less vulnerable to denial-of-service attacks.
16898 o Major bugfixes (security, hidden service):
16899 - Fix an issue that would allow a malicious client to trigger an
16900 assertion failure and halt a hidden service. Fixes bug 15600;
16901 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
16902 - Fix a bug that could cause a client to crash with an assertion
16903 failure when parsing a malformed hidden service descriptor. Fixes
16904 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
16906 o Minor features (DoS-resistance, hidden service):
16907 - Introduction points no longer allow multiple INTRODUCE1 cells to
16908 arrive on the same circuit. This should make it more expensive for
16909 attackers to overwhelm hidden services with introductions.
16910 Resolves ticket 15515.
16911 - Decrease the amount of reattempts that a hidden service performs
16912 when its rendezvous circuits fail. This reduces the computational
16913 cost for running a hidden service under heavy load. Resolves
16917 Changes in version 0.2.6.6 - 2015-03-24
16918 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
16920 It adds numerous safety, security, correctness, and performance
16921 improvements. Client programs can be configured to use more kinds of
16922 sockets, AutomapHosts works better, the multithreading backend is
16923 improved, cell transmission is refactored, test coverage is much
16924 higher, more denial-of-service attacks are handled, guard selection is
16925 improved to handle long-term guards better, pluggable transports
16926 should work a bit better, and some annoying hidden service performance
16927 bugs should be addressed.
16929 o Minor bugfixes (portability):
16930 - Use the correct datatype in the SipHash-2-4 function to prevent
16931 compilers from assuming any sort of alignment. Fixes bug 15436;
16932 bugfix on 0.2.5.3-alpha.
16934 Changes in version 0.2.6.5-rc - 2015-03-18
16935 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
16936 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
16938 o Major bugfixes (client):
16939 - Avoid crashing when making certain configuration option changes on
16940 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
16943 o Major bugfixes (pluggable transports):
16944 - Initialize the extended OR Port authentication cookie before
16945 launching pluggable transports. This prevents a race condition
16946 that occurred when server-side pluggable transports would cache the
16947 authentication cookie before it has been (re)generated. Fixes bug
16948 15240; bugfix on 0.2.5.1-alpha.
16950 o Major bugfixes (portability):
16951 - Do not crash on startup when running on Solaris. Fixes a bug
16952 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
16955 o Minor features (heartbeat):
16956 - On relays, report how many connections we negotiated using each
16957 version of the Tor link protocols. This information will let us
16958 know if removing support for very old versions of the Tor
16959 protocols is harming the network. Closes ticket 15212.
16961 o Code simplification and refactoring:
16962 - Refactor main loop to extract the 'loop' part. This makes it
16963 easier to run Tor under Shadow. Closes ticket 15176.
16966 Changes in version 0.2.5.11 - 2015-03-17
16967 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
16969 It backports several bugfixes from the 0.2.6 branch, including a
16970 couple of medium-level security fixes for relays and exit nodes.
16971 It also updates the list of directory authorities.
16973 o Directory authority changes:
16974 - Remove turtles as a directory authority.
16975 - Add longclaw as a new (v3) directory authority. This implements
16976 ticket 13296. This keeps the directory authority count at 9.
16977 - The directory authority Faravahar has a new IP address. This
16978 closes ticket 14487.
16980 o Major bugfixes (crash, OSX, security):
16981 - Fix a remote denial-of-service opportunity caused by a bug in
16982 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
16985 o Major bugfixes (relay, stability, possible security):
16986 - Fix a bug that could lead to a relay crashing with an assertion
16987 failure if a buffer of exactly the wrong layout was passed to
16988 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
16989 0.2.0.10-alpha. Patch from 'cypherpunks'.
16990 - Do not assert if the 'data' pointer on a buffer is advanced to the
16991 very end of the buffer; log a BUG message instead. Only assert if
16992 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
16994 o Major bugfixes (exit node stability):
16995 - Fix an assertion failure that could occur under high DNS load.
16996 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
16997 diagnosed and fixed by "cypherpunks".
16999 o Major bugfixes (Linux seccomp2 sandbox):
17000 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
17001 crash during attempts to call wait4. Fixes bug 15088; bugfix on
17002 0.2.5.1-alpha. Patch from "sanic".
17004 o Minor features (controller):
17005 - New "GETINFO bw-event-cache" to get information about recent
17006 bandwidth events. Closes ticket 14128. Useful for controllers to
17007 get recent bandwidth history after the fix for ticket 13988.
17009 o Minor features (geoip):
17010 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17011 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17014 o Minor bugfixes (client, automapping):
17015 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
17016 no value follows the option. Fixes bug 14142; bugfix on
17017 0.2.4.7-alpha. Patch by "teor".
17018 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
17019 14195; bugfix on 0.1.0.1-rc.
17021 o Minor bugfixes (compilation):
17022 - Build without warnings with the stock OpenSSL srtp.h header, which
17023 has a duplicate declaration of SSL_get_selected_srtp_profile().
17024 Fixes bug 14220; this is OpenSSL's bug, not ours.
17026 o Minor bugfixes (directory authority):
17027 - Allow directory authorities to fetch more data from one another if
17028 they find themselves missing lots of votes. Previously, they had
17029 been bumping against the 10 MB queued data limit. Fixes bug 14261;
17030 bugfix on 0.1.2.5-alpha.
17031 - Enlarge the buffer to read bwauth generated files to avoid an
17032 issue when parsing the file in dirserv_read_measured_bandwidths().
17033 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
17035 o Minor bugfixes (statistics):
17036 - Increase period over which bandwidth observations are aggregated
17037 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
17039 o Minor bugfixes (preventative security, C safety):
17040 - When reading a hexadecimal, base-32, or base-64 encoded value from
17041 a string, always overwrite the whole output buffer. This prevents
17042 some bugs where we would look at (but fortunately, not reveal)
17043 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
17047 Changes in version 0.2.4.26 - 2015-03-17
17048 Tor 0.2.4.26 includes an updated list of directory authorities. It
17049 also backports a couple of stability and security bugfixes from 0.2.5
17052 o Directory authority changes:
17053 - Remove turtles as a directory authority.
17054 - Add longclaw as a new (v3) directory authority. This implements
17055 ticket 13296. This keeps the directory authority count at 9.
17056 - The directory authority Faravahar has a new IP address. This
17057 closes ticket 14487.
17059 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
17060 - Fix an assertion failure that could occur under high DNS load.
17061 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17062 diagnosed and fixed by "cypherpunks".
17064 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
17065 - Fix a bug that could lead to a relay crashing with an assertion
17066 failure if a buffer of exactly the wrong layout was passed to
17067 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17068 0.2.0.10-alpha. Patch from 'cypherpunks'.
17069 - Do not assert if the 'data' pointer on a buffer is advanced to the
17070 very end of the buffer; log a BUG message instead. Only assert if
17071 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17073 o Minor features (geoip):
17074 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17075 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17078 Changes in version 0.2.6.4-rc - 2015-03-09
17079 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
17080 attacker might be able to use in order to crash certain Tor
17081 directories. It also resolves some minor issues left over from, or
17082 introduced in, Tor 0.2.6.3-alpha or earlier.
17084 o Major bugfixes (crash, OSX, security):
17085 - Fix a remote denial-of-service opportunity caused by a bug in
17086 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
17089 o Major bugfixes (relay, stability, possible security):
17090 - Fix a bug that could lead to a relay crashing with an assertion
17091 failure if a buffer of exactly the wrong layout is passed to
17092 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
17093 0.2.0.10-alpha. Patch from "cypherpunks".
17094 - Do not assert if the 'data' pointer on a buffer is advanced to the
17095 very end of the buffer; log a BUG message instead. Only assert if
17096 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
17098 o Major bugfixes (FreeBSD IPFW transparent proxy):
17099 - Fix address detection with FreeBSD transparent proxies, when
17100 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
17103 o Major bugfixes (Linux seccomp2 sandbox):
17104 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
17105 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
17107 - Allow AF_UNIX hidden services to be used with the seccomp2
17108 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
17109 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
17110 crash during attempts to call wait4. Fixes bug 15088; bugfix on
17111 0.2.5.1-alpha. Patch from "sanic".
17113 o Minor features (controller):
17114 - Messages about problems in the bootstrap process now include
17115 information about the server we were trying to connect to when we
17116 noticed the problem. Closes ticket 15006.
17118 o Minor features (geoip):
17119 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
17120 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
17123 o Minor features (logs):
17124 - Quiet some log messages in the heartbeat and at startup. Closes
17127 o Minor bugfixes (certificate handling):
17128 - If an authority operator accidentally makes a signing certificate
17129 with a future publication time, do not discard its real signing
17130 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
17131 - Remove any old authority certificates that have been superseded
17132 for at least two days. Previously, we would keep superseded
17133 certificates until they expired, if they were published close in
17134 time to the certificate that superseded them. Fixes bug 11454;
17135 bugfix on 0.2.1.8-alpha.
17137 o Minor bugfixes (compilation):
17138 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
17140 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
17143 o Minor bugfixes (testing):
17144 - Fix endianness issues in unit test for resolve_my_address() to
17145 have it pass on big endian systems. Fixes bug 14980; bugfix on
17147 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
17148 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
17149 - When running the new 'make test-stem' target, use the configured
17150 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
17151 from "cypherpunks".
17152 - When running the zero-length-keys tests, do not use the default
17153 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
17156 o Directory authority IP change:
17157 - The directory authority Faravahar has a new IP address. This
17158 closes ticket 14487.
17161 - Remove some lingering dead code that once supported mempools.
17162 Mempools were disabled by default in 0.2.5, and removed entirely
17163 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
17167 Changes in version 0.2.6.3-alpha - 2015-02-19
17168 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
17169 the 0.2.6.x series. It introduces support for more kinds of sockets,
17170 makes it harder to accidentally run an exit, improves our
17171 multithreading backend, incorporates several fixes for the
17172 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
17174 If no major regressions or security holes are found in this version,
17175 the next version will be a release candidate.
17177 o Deprecated versions:
17178 - Tor relays older than 0.2.4.18-rc are no longer allowed to
17179 advertise themselves on the network. Closes ticket 13555.
17181 o Major features (security, unix domain sockets):
17182 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
17183 applications can reach Tor without having to create AF_INET or
17184 AF_INET6 sockets, meaning they can completely disable their
17185 ability to make non-Tor network connections. To create a socket of
17186 this type, use "SocksPort unix:/path/to/socket". Implements
17188 - Support mapping hidden service virtual ports to AF_UNIX sockets.
17189 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
17190 Implements ticket 11485.
17192 o Major features (changed defaults):
17193 - Prevent relay operators from unintentionally running exits: When a
17194 relay is configured as an exit node, we now warn the user unless
17195 the "ExitRelay" option is set to 1. We warn even more loudly if
17196 the relay is configured with the default exit policy, since this
17197 can indicate accidental misconfiguration. Setting "ExitRelay 0"
17198 stops Tor from running as an exit relay. Closes ticket 10067.
17200 o Major features (directory system):
17201 - When downloading server- or microdescriptors from a directory
17202 server, we no longer launch multiple simultaneous requests to the
17203 same server. This reduces load on the directory servers,
17204 especially when directory guards are in use. Closes ticket 9969.
17205 - When downloading server- or microdescriptors over a tunneled
17206 connection, do not limit the length of our requests to what the
17207 Squid proxy is willing to handle. Part of ticket 9969.
17208 - Authorities can now vote on the correct digests and latest
17209 versions for different software packages. This allows packages
17210 that include Tor to use the Tor authority system as a way to get
17211 notified of updates and their correct digests. Implements proposal
17212 227. Closes ticket 10395.
17214 o Major features (guards):
17215 - Introduce the Guardfraction feature to improves load balancing on
17216 guard nodes. Specifically, it aims to reduce the traffic gap that
17217 guard nodes experience when they first get the Guard flag. This is
17218 a required step if we want to increase the guard lifetime to 9
17219 months or greater. Closes ticket 9321.
17221 o Major features (performance):
17222 - Make the CPU worker implementation more efficient by avoiding the
17223 kernel and lengthening pipelines. The original implementation used
17224 sockets to transfer data from the main thread to the workers, and
17225 didn't allow any thread to be assigned more than a single piece of
17226 work at once. The new implementation avoids communications
17227 overhead by making requests in shared memory, avoiding kernel IO
17228 where possible, and keeping more requests in flight at once.
17229 Implements ticket 9682.
17231 o Major features (relay):
17232 - Raise the minimum acceptable configured bandwidth rate for bridges
17233 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
17234 20 KiB/sec.) Closes ticket 13822.
17236 o Major bugfixes (exit node stability):
17237 - Fix an assertion failure that could occur under high DNS load.
17238 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
17239 diagnosed and fixed by "cypherpunks".
17241 o Major bugfixes (mixed relay-client operation):
17242 - When running as a relay and client at the same time (not
17243 recommended), if we decide not to use a new guard because we want
17244 to retry older guards, only close the locally-originating circuits
17245 passing through that guard. Previously we would close all the
17246 circuits through that guard. Fixes bug 9819; bugfix on
17247 0.2.1.1-alpha. Reported by "skruffy".
17249 o Minor features (build):
17250 - New --disable-system-torrc compile-time option to prevent Tor from
17251 looking for the system-wide torrc or torrc-defaults files.
17252 Resolves ticket 13037.
17254 o Minor features (controller):
17255 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
17256 events so controllers can observe circuit isolation inputs. Closes
17258 - ControlPort now supports the unix:/path/to/socket syntax as an
17259 alternative to the ControlSocket option, for consistency with
17260 SocksPort and HiddenServicePort. Closes ticket 14451.
17261 - New "GETINFO bw-event-cache" to get information about recent
17262 bandwidth events. Closes ticket 14128. Useful for controllers to
17263 get recent bandwidth history after the fix for ticket 13988.
17265 o Minor features (Denial of service resistance):
17266 - Count the total number of bytes used storing hidden service
17267 descriptors against the value of MaxMemInQueues. If we're low on
17268 memory, and more than 20% of our memory is used holding hidden
17269 service descriptors, free them until no more than 10% of our
17270 memory holds hidden service descriptors. Free the least recently
17271 fetched descriptors first. Resolves ticket 13806.
17272 - When we have recently been under memory pressure (over 3/4 of
17273 MaxMemInQueues is allocated), then allocate smaller zlib objects
17274 for small requests. Closes ticket 11791.
17276 o Minor features (geoip):
17277 - Update geoip and geoip6 files to the January 7 2015 Maxmind
17278 GeoLite2 Country database.
17280 o Minor features (guard nodes):
17281 - Reduce the time delay before saving guard status to disk from 10
17282 minutes to 30 seconds (or from one hour to 10 minutes if
17283 AvoidDiskWrites is set). Closes ticket 12485.
17285 o Minor features (hidden service):
17286 - Make Sybil attacks against hidden services harder by changing the
17287 minimum time required to get the HSDir flag from 25 hours up to 96
17288 hours. Addresses ticket 14149.
17289 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
17290 services to disable the anti-scanning feature introduced in
17291 0.2.6.2-alpha. With this option not set, a connection to an
17292 unlisted port closes the circuit. With this option set, only a
17293 RELAY_DONE cell is sent. Closes ticket 14084.
17295 o Minor features (interface):
17296 - Implement "-f -" command-line option to read torrc configuration
17297 from standard input, if you don't want to store the torrc file in
17298 the file system. Implements feature 13865.
17300 o Minor features (logging):
17301 - Add a count of unique clients to the bridge heartbeat message.
17302 Resolves ticket 6852.
17303 - Suppress "router info incompatible with extra info" message when
17304 reading extrainfo documents from cache. (This message got loud
17305 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
17307 - Elevate hidden service authorized-client message from DEBUG to
17308 INFO. Closes ticket 14015.
17310 o Minor features (stability):
17311 - Add assertions in our hash-table iteration code to check for
17312 corrupted values that could cause infinite loops. Closes
17315 o Minor features (systemd):
17316 - Various improvements and modernizations in systemd hardening
17317 support. Closes ticket 13805. Patch from Craig Andrews.
17319 o Minor features (testing networks):
17320 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
17321 and the default on a testing network to 2 minutes. Drop the
17322 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
17323 keep the default on a testing network at 30 seconds. This reduces
17324 HS bootstrap time to around 25 seconds. Also, change the default
17325 time in test-network.sh to match. Closes ticket 13401. Patch
17327 - Create TestingDirAuthVoteHSDir to correspond to
17328 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
17329 HSDir flag for the listed relays regardless of uptime or ORPort
17330 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
17331 Partial implementation for ticket 14067. Patch by "teor".
17333 o Minor features (tor2web mode):
17334 - Introduce the config option Tor2webRendezvousPoints, which allows
17335 clients in Tor2webMode to select a specific Rendezvous Point to be
17336 used in HS circuits. This might allow better performance for
17337 Tor2Web nodes. Implements ticket 12844.
17339 o Minor bugfixes (client DNS):
17340 - Report the correct cached DNS expiration times on SOCKS port or in
17341 DNS replies. Previously, we would report everything as "never
17342 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
17343 - Avoid a small memory leak when we find a cached answer for a
17344 reverse DNS lookup in a client-side DNS cache. (Remember, client-
17345 side DNS caching is off by default, and is not recommended.) Fixes
17346 bug 14259; bugfix on 0.2.0.1-alpha.
17348 o Minor bugfixes (client, automapping):
17349 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
17350 no value follows the option. Fixes bug 14142; bugfix on
17351 0.2.4.7-alpha. Patch by "teor".
17352 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
17353 14195; bugfix on 0.1.0.1-rc.
17354 - Prevent changes to other options from removing the wildcard value
17355 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
17357 - Allow MapAddress and AutomapHostsOnResolve to work together when
17358 an address is mapped into another address type (like .onion) that
17359 must be automapped at resolve time. Fixes bug 7555; bugfix
17362 o Minor bugfixes (client, bridges):
17363 - When we are using bridges and we had a network connectivity
17364 problem, only retry connecting to our currently configured
17365 bridges, not all bridges we know about and remember using. Fixes
17366 bug 14216; bugfix on 0.2.2.17-alpha.
17368 o Minor bugfixes (client, IPv6):
17369 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
17370 flag is not set; and not because the NoIPv4Traffic flag was set.
17371 Previously we'd looked at the NoIPv4Traffic flag for both types of
17372 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
17374 o Minor bugfixes (compilation):
17375 - The address of an array in the middle of a structure will always
17376 be non-NULL. clang recognises this and complains. Disable the
17377 tautologous and redundant check to silence this warning. Fixes bug
17378 14001; bugfix on 0.2.1.2-alpha.
17379 - Avoid warnings when building with systemd 209 or later. Fixes bug
17380 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
17381 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
17382 Addresses ticket 14188.
17383 - Build without warnings with the stock OpenSSL srtp.h header, which
17384 has a duplicate declaration of SSL_get_selected_srtp_profile().
17385 Fixes bug 14220; this is OpenSSL's bug, not ours.
17386 - Do not compile any code related to Tor2Web mode when Tor2Web mode
17387 is not enabled at compile time. Previously, this code was included
17388 in a disabled state. See discussion on ticket 12844.
17389 - Remove the --disable-threads configure option again. It was
17390 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
17391 14819; bugfix on 0.2.6.2-alpha.
17393 o Minor bugfixes (controller):
17394 - Report "down" in response to the "GETINFO entry-guards" command
17395 when relays are down with an unreachable_since value. Previously,
17396 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
17397 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
17398 14116; bugfix on 0.2.2.9-alpha.
17399 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
17400 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
17402 o Minor bugfixes (directory authority):
17403 - Allow directory authorities to fetch more data from one another if
17404 they find themselves missing lots of votes. Previously, they had
17405 been bumping against the 10 MB queued data limit. Fixes bug 14261;
17406 bugfix on 0.1.2.5-alpha.
17407 - Do not attempt to download extrainfo documents which we will be
17408 unable to validate with a matching server descriptor. Fixes bug
17409 13762; bugfix on 0.2.0.1-alpha.
17410 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
17411 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
17412 - Enlarge the buffer to read bwauth generated files to avoid an
17413 issue when parsing the file in dirserv_read_measured_bandwidths().
17414 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
17416 o Minor bugfixes (file handling):
17417 - Stop failing when key files are zero-length. Instead, generate new
17418 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
17419 on all versions of Tor. Patch by "teor".
17420 - Stop generating a fresh .old RSA onion key file when the .old file
17421 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
17422 - Avoid overwriting .old key files with empty key files.
17423 - Skip loading zero-length extrainfo store, router store, stats,
17424 state, and key files.
17425 - Avoid crashing when trying to reload a torrc specified as a
17426 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
17429 o Minor bugfixes (hidden services):
17430 - Close the introduction circuit when we have no more usable intro
17431 points, instead of waiting for it to time out. This also ensures
17432 that no follow-up HS descriptor fetch is triggered when the
17433 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
17434 - When fetching a hidden service descriptor for a down service that
17435 was recently up, do not keep refetching until we try the same
17436 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
17437 - Successfully launch Tor with a nonexistent hidden service
17438 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
17439 14106; bugfix on 0.2.6.2-alpha.
17441 o Minor bugfixes (logging):
17442 - Avoid crashing when there are more log domains than entries in
17443 domain_list. Bugfix on 0.2.3.1-alpha.
17444 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
17446 - Don't log messages to stdout twice when starting up. Fixes bug
17447 13993; bugfix on 0.2.6.1-alpha.
17449 o Minor bugfixes (parsing):
17450 - Stop accepting milliseconds (or other junk) at the end of
17451 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
17452 - Support two-number and three-number version numbers correctly, in
17453 case we change the Tor versioning system in the future. Fixes bug
17454 13661; bugfix on 0.0.8pre1.
17456 o Minor bugfixes (path counting):
17457 - When deciding whether the consensus lists any exit nodes, count
17458 the number listed in the consensus, not the number we have
17459 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
17460 - When deciding whether we have any exit nodes, only examine
17461 ExitNodes when the ExitNodes option is actually set. Fixes part of
17462 bug 14918; bugfix on 0.2.6.2-alpha.
17463 - Get rid of redundant and possibly scary warnings that we are
17464 missing directory information while we bootstrap. Fixes part of
17465 bug 14918; bugfix on 0.2.6.2-alpha.
17467 o Minor bugfixes (portability):
17468 - Fix the ioctl()-based network interface lookup code so that it
17469 will work on systems that have variable-length struct ifreq, for
17471 - Fix scheduler compilation on targets where char is unsigned. Fixes
17472 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
17474 o Minor bugfixes (sandbox):
17475 - Allow glibc fatal errors to be sent to stderr before Tor exits.
17476 Previously, glibc would try to write them to /dev/tty, and the
17477 sandbox would trap the call and make Tor exit prematurely. Fixes
17478 bug 14759; bugfix on 0.2.5.1-alpha.
17480 o Minor bugfixes (shutdown):
17481 - When shutting down, always call event_del() on lingering read or
17482 write events before freeing them. Otherwise, we risk double-frees
17483 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
17486 o Minor bugfixes (small memory leaks):
17487 - Avoid leaking memory when using IPv6 virtual address mappings.
17488 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
17491 o Minor bugfixes (statistics):
17492 - Increase period over which bandwidth observations are aggregated
17493 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
17495 o Minor bugfixes (systemd support):
17496 - Fix detection and operation of systemd watchdog. Fixes part of bug
17497 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
17498 - Run correctly under systemd with the RunAsDaemon option set. Fixes
17499 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
17500 - Inform the systemd supervisor about more changes in the Tor
17501 process status. Implements part of ticket 14141. Patch from
17503 - Cause the "--disable-systemd" option to actually disable systemd
17504 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
17507 o Minor bugfixes (TLS):
17508 - Check more thoroughly throughout the TLS code for possible
17509 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
17511 o Minor bugfixes (transparent proxy):
17512 - Use getsockname, not getsockopt, to retrieve the address for a
17513 TPROXY-redirected connection. Fixes bug 13796; bugfix
17516 o Code simplification and refactoring:
17517 - Move fields related to isolating and configuring client ports into
17518 a shared structure. Previously, they were duplicated across
17519 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
17520 to copy them correctly had been the cause of at least one bug in
17521 the past. Closes ticket 8546.
17522 - Refactor the get_interface_addresses_raw() doom-function into
17523 multiple smaller and simpler subfunctions. Cover the resulting
17524 subfunctions with unit-tests. Fixes a significant portion of
17526 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
17527 only for version <= 0.2.2.24 which is now deprecated. Closes
17529 - Remove a test for a long-defunct broken version-one
17533 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
17534 for writing the OpenBSD-specific tips. Resolves ticket 13702.
17535 - Make the tor-resolve documentation match its help string and its
17536 options. Resolves part of ticket 14325.
17537 - Log a more useful error message from tor-resolve when failing to
17538 look up a hidden service address. Resolves part of ticket 14325.
17540 o Downgraded warnings:
17541 - Don't warn when we've attempted to contact a relay using the wrong
17542 ntor onion key. Closes ticket 9635.
17544 o Removed features:
17545 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
17546 longer silently accepted as an alias for "ExitNodes".
17547 - The --enable-mempool and --enable-buf-freelists options, which
17548 were originally created to work around bad malloc implementations,
17549 no longer exist. They were off-by-default in 0.2.5. Closes
17553 - Make the checkdir/perms test complete successfully even if the
17554 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
17555 - Test that tor does not fail when key files are zero-length. Check
17556 that tor generates new keys, and overwrites the empty key files.
17557 - Test that tor generates new keys when keys are missing
17558 (existing behavior).
17559 - Test that tor does not overwrite key files that already contain
17560 data (existing behavior). Tests bug 13111. Patch by "teor".
17561 - New "make test-stem" target to run stem integration tests.
17562 Requires that the "STEM_SOURCE_DIR" environment variable be set.
17563 Closes ticket 14107.
17564 - Make the test_cmdline_args.py script work correctly on Windows.
17565 Patch from Gisle Vanem.
17566 - Move the slower unit tests into a new "./src/test/test-slow"
17567 binary that can be run independently of the other tests. Closes
17569 - Avoid undefined behavior when sampling huge values from the
17570 Laplace distribution. This made unittests fail on Raspberry Pi.
17571 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
17574 Changes in version 0.2.6.2-alpha - 2014-12-31
17575 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
17576 It introduces a major new backend for deciding when to send cells on
17577 channels, which should lead down the road to big performance
17578 increases. It contains security and statistics features for better
17579 work on hidden services, and numerous bugfixes.
17581 This release contains many new unit tests, along with major
17582 performance improvements for running testing networks using Chutney.
17583 Thanks to a series of patches contributed by "teor", testing networks
17584 should now bootstrap in seconds, rather than minutes.
17586 o Major features (relay, infrastructure):
17587 - Complete revision of the code that relays use to decide which cell
17588 to send next. Formerly, we selected the best circuit to write on
17589 each channel, but we didn't select among channels in any
17590 sophisticated way. Now, we choose the best circuits globally from
17591 among those whose channels are ready to deliver traffic.
17593 This patch implements a new inter-cmux comparison API, a global
17594 high/low watermark mechanism and a global scheduler loop for
17595 transmission prioritization across all channels as well as among
17596 circuits on one channel. This schedule is currently tuned to
17597 (tolerantly) avoid making changes in network performance, but it
17598 should form the basis for major circuit performance increases in
17599 the future. Code by Andrea; tuning by Rob Jansen; implements
17602 o Major features (hidden services):
17603 - Make HS port scanning more difficult by immediately closing the
17604 circuit when a user attempts to connect to a nonexistent port.
17605 Closes ticket 13667.
17606 - Add a HiddenServiceStatistics option that allows Tor relays to
17607 gather and publish statistics about the overall size and volume of
17608 hidden service usage. Specifically, when this option is turned on,
17609 an HSDir will publish an approximate number of hidden services
17610 that have published descriptors to it the past 24 hours. Also, if
17611 a relay has acted as a hidden service rendezvous point, it will
17612 publish the approximate amount of rendezvous cells it has relayed
17613 the past 24 hours. The statistics themselves are obfuscated so
17614 that the exact values cannot be derived. For more details see
17615 proposal 238, "Better hidden service stats from Tor relays". This
17616 feature is currently disabled by default. Implements feature 13192.
17618 o Major bugfixes (client, automap):
17619 - Repair automapping with IPv6 addresses. This automapping should
17620 have worked previously, but one piece of debugging code that we
17621 inserted to detect a regression actually caused the regression to
17622 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
17623 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
17626 o Major bugfixes (hidden services):
17627 - When closing an introduction circuit that was opened in parallel
17628 with others, don't mark the introduction point as unreachable.
17629 Previously, the first successful connection to an introduction
17630 point would make the other introduction points get marked as
17631 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
17633 o Directory authority changes:
17634 - Remove turtles as a directory authority.
17635 - Add longclaw as a new (v3) directory authority. This implements
17636 ticket 13296. This keeps the directory authority count at 9.
17638 o Major removed features:
17639 - Tor clients no longer support connecting to hidden services
17640 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
17641 option has been removed. (There shouldn't be any hidden services
17642 running these versions on the network.) Closes ticket 7803.
17644 o Minor features (client):
17645 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
17646 is enabled, reject requests with IP addresses as hostnames.
17647 Resolves ticket 13315.
17649 o Minor features (controller):
17650 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
17651 write an unscheduled heartbeat message to the log. Implements
17654 o Minor features (geoip):
17655 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
17658 o Minor features (hidden services):
17659 - When re-enabling the network, don't try to build introduction
17660 circuits until we have successfully built a circuit. This makes
17661 hidden services come up faster when the network is re-enabled.
17662 Patch from "akwizgran". Closes ticket 13447.
17663 - When we fail to retrieve a hidden service descriptor, send the
17664 controller an "HS_DESC FAILED" controller event. Implements
17666 - New HiddenServiceDirGroupReadable option to cause hidden service
17667 directories and hostname files to be created group-readable. Patch
17668 from "anon", David Stainton, and "meejah". Closes ticket 11291.
17670 o Minor features (systemd):
17671 - Where supported, when running with systemd, report successful
17672 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
17673 - When running with systemd, support systemd watchdog messages. Part
17674 of ticket 11016. Patch by Michael Scherer.
17676 o Minor features (transparent proxy):
17677 - Update the transparent proxy option checks to allow for both ipfw
17678 and pf on OS X. Closes ticket 14002.
17679 - Use the correct option when using IPv6 with transparent proxy
17680 support on Linux. Resolves 13808. Patch by Francisco Blas
17683 o Minor bugfixes (preventative security, C safety):
17684 - When reading a hexadecimal, base-32, or base-64 encoded value from
17685 a string, always overwrite the whole output buffer. This prevents
17686 some bugs where we would look at (but fortunately, not reveal)
17687 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
17689 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
17690 just the part that's used. This makes it harder for data leak bugs
17691 to occur in the event of other programming failures. Resolves
17694 o Minor bugfixes (client, microdescriptors):
17695 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
17696 computing which microdescriptors to download. This keeps us from
17697 erroneous download behavior if two microdescriptor digests ever
17698 have the same first 160 bits. Fixes part of bug 13399; bugfix
17700 - Reset a router's status if its microdescriptor digest changes,
17701 even if the first 160 bits remain the same. Fixes part of bug
17702 13399; bugfix on 0.2.3.1-alpha.
17704 o Minor bugfixes (compilation):
17705 - Silence clang warnings under --enable-expensive-hardening,
17706 including implicit truncation of 64 bit values to 32 bit, const
17707 char assignment to self, tautological compare, and additional
17708 parentheses around equality tests. Fixes bug 13577; bugfix
17710 - Fix a clang warning about checking whether an address in the
17711 middle of a structure is NULL. Fixes bug 14001; bugfix
17714 o Minor bugfixes (hidden services):
17715 - Correctly send a controller event when we find that a rendezvous
17716 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
17717 - Pre-check directory permissions for new hidden-services to avoid
17718 at least one case of "Bug: Acting on config options left us in a
17719 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
17720 - When adding a new hidden service (for example, via SETCONF), Tor
17721 no longer congratulates the user for running a relay. Fixes bug
17722 13941; bugfix on 0.2.6.1-alpha.
17723 - When fetching hidden service descriptors, we now check not only
17724 for whether we got the hidden service we had in mind, but also
17725 whether we got the particular descriptors we wanted. This prevents
17726 a class of inefficient but annoying DoS attacks by hidden service
17727 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
17730 o Minor bugfixes (Linux seccomp2 sandbox):
17731 - Make transparent proxy support work along with the seccomp2
17732 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
17733 by Francisco Blas Izquierdo Riera.
17734 - Fix a memory leak in tor-resolve when running with the sandbox
17735 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
17737 o Minor bugfixes (logging):
17738 - Downgrade warnings about RSA signature failures to info log level.
17739 Emit a warning when an extra info document is found incompatible
17740 with a corresponding router descriptor. Fixes bug 9812; bugfix
17742 - Make connection_ap_handshake_attach_circuit() log the circuit ID
17743 correctly. Fixes bug 13701; bugfix on 0.0.6.
17745 o Minor bugfixes (misc):
17746 - Stop allowing invalid address patterns like "*/24" that contain
17747 both a wildcard address and a bit prefix length. This affects all
17748 our address-range parsing code. Fixes bug 7484; bugfix
17751 o Minor bugfixes (testing networks, fast startup):
17752 - Allow Tor to build circuits using a consensus with no exits. If
17753 the consensus has no exits (typical of a bootstrapping test
17754 network), allow Tor to build circuits once enough descriptors have
17755 been downloaded. This assists in bootstrapping a testing Tor
17756 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
17758 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
17759 header to directory servers. This allows us to obtain consensuses
17760 promptly when the consensus interval is very short. This assists
17761 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
17762 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
17763 - Stop assuming that private addresses are local when checking
17764 reachability in a TestingTorNetwork. Instead, when testing, assume
17765 all OR connections are remote. (This is necessary due to many test
17766 scenarios running all relays on localhost.) This assists in
17767 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
17768 0.1.0.1-rc. Patch by "teor".
17769 - Avoid building exit circuits from a consensus with no exits. Now
17770 thanks to our fix for 13718, we accept a no-exit network as not
17771 wholly lost, but we need to remember not to try to build exit
17772 circuits on it. Closes ticket 13814; patch by "teor".
17773 - Stop requiring exits to have non-zero bandwithcapacity in a
17774 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
17775 ignore exit bandwidthcapacity. This assists in bootstrapping a
17776 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
17777 on 0.2.0.3-alpha. Patch by "teor".
17778 - Add "internal" to some bootstrap statuses when no exits are
17779 available. If the consensus does not contain Exits, Tor will only
17780 build internal circuits. In this case, relevant statuses will
17781 contain the word "internal" as indicated in the Tor control-
17782 spec.txt. When bootstrap completes, Tor will be ready to build
17783 internal circuits. If a future consensus contains Exits, exit
17784 circuits may become available. Fixes part of bug 13718; bugfix on
17785 0.2.4.10-alpha. Patch by "teor".
17786 - Decrease minimum consensus interval to 10 seconds when
17787 TestingTorNetwork is set, or 5 seconds for the first consensus.
17788 Fix assumptions throughout the code that assume larger intervals.
17789 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
17791 - Avoid excluding guards from path building in minimal test
17792 networks, when we're in a test network and excluding guards would
17793 exclude all relays. This typically occurs in incredibly small tor
17794 networks, and those using "TestingAuthVoteGuard *". Fixes part of
17795 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
17797 o Code simplification and refactoring:
17798 - Stop using can_complete_circuits as a global variable; access it
17799 with a function instead.
17800 - Avoid using operators directly as macro arguments: this lets us
17801 apply coccinelle transformations to our codebase more directly.
17802 Closes ticket 13172.
17803 - Combine the functions used to parse ClientTransportPlugin and
17804 ServerTransportPlugin into a single function. Closes ticket 6456.
17805 - Add inline functions and convenience macros for inspecting channel
17806 state. Refactor the code to use convenience macros instead of
17807 checking channel state directly. Fixes issue 7356.
17808 - Document all members of was_router_added_t and rename
17809 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
17810 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
17811 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
17812 constant instead of hardcoded value. Fixes issue 13840.
17813 - Refactor our generic strmap and digestmap types into a single
17814 implementation, so that we can add a new digest256map
17818 - Document the bridge-authority-only 'networkstatus-bridges' file.
17819 Closes ticket 13713; patch from "tom".
17820 - Fix typo in PredictedPortsRelevanceTime option description in
17821 manpage. Resolves issue 13707.
17822 - Stop suggesting that users specify relays by nickname: it isn't a
17823 good idea. Also, properly cross-reference how to specify relays in
17824 all parts of manual documenting options that take a list of
17825 relays. Closes ticket 13381.
17826 - Clarify the HiddenServiceDir option description in manpage to make
17827 it clear that relative paths are taken with respect to the current
17828 working directory. Also clarify that this behavior is not
17829 guaranteed to remain indefinitely. Fixes issue 13913.
17832 - New tests for many parts of channel, relay, and circuitmux
17833 functionality. Code by Andrea; part of 9262.
17834 - New tests for parse_transport_line(). Part of ticket 6456.
17835 - In the unit tests, use chgrp() to change the group of the unit
17836 test temporary directory to the current user, so that the sticky
17837 bit doesn't interfere with tests that check directory groups.
17839 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
17843 Changes in version 0.2.6.1-alpha - 2014-10-30
17844 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
17845 includes numerous code cleanups and new tests, and fixes a large
17846 number of annoying bugs. Out-of-memory conditions are handled better
17847 than in 0.2.5, pluggable transports have improved proxy support, and
17848 clients now use optimistic data for contacting hidden services. Also,
17849 we are now more robust to changes in what we consider a parseable
17850 directory object, so that tightening restrictions does not have a risk
17851 of introducing infinite download loops.
17853 This is the first alpha release in a new series, so expect there to be
17854 bugs. Users who would rather test out a more stable branch should stay
17855 with 0.2.5.x for now.
17857 o New compiler and system requirements:
17858 - Tor 0.2.6.x requires that your compiler support more of the C99
17859 language standard than before. The 'configure' script now detects
17860 whether your compiler supports C99 mid-block declarations and
17861 designated initializers. If it does not, Tor will not compile.
17863 We may revisit this requirement if it turns out that a significant
17864 number of people need to build Tor with compilers that don't
17865 bother implementing a 15-year-old standard. Closes ticket 13233.
17866 - Tor no longer supports systems without threading support. When we
17867 began working on Tor, there were several systems that didn't have
17868 threads, or where the thread support wasn't able to run the
17869 threads of a single process on multiple CPUs. That no longer
17870 holds: every system where Tor needs to run well now has threading
17871 support. Resolves ticket 12439.
17873 o Removed platform support:
17874 - We no longer include special code to build on Windows CE; as far
17875 as we know, nobody has used Tor on Windows CE in a very long time.
17876 Closes ticket 11446.
17878 o Major features (bridges):
17879 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
17880 transports if they are configured via the "TOR_PT_PROXY"
17881 environment variable. Implements proposal 232. Resolves
17884 o Major features (client performance, hidden services):
17885 - Allow clients to use optimistic data when connecting to a hidden
17886 service, which should remove a round-trip from hidden service
17887 initialization. See proposal 181 for details. Implements
17890 o Major features (directory system):
17891 - Upon receiving an unparseable directory object, if its digest
17892 matches what we expected, then don't try to download it again.
17893 Previously, when we got a descriptor we didn't like, we would keep
17894 trying to download it over and over. Closes ticket 11243.
17896 o Major features (sample torrc):
17897 - Add a new, infrequently-changed "torrc.minimal". This file is
17898 similar to torrc.sample, but it will change as infrequently as
17899 possible, for the benefit of users whose systems prompt them for
17900 intervention whenever a default configuration file is changed.
17901 Making this change allows us to update torrc.sample to be a more
17902 generally useful "sample torrc".
17904 o Major bugfixes (directory authorities):
17905 - Do not assign the HSDir flag to relays if they are not Valid, or
17906 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
17908 o Major bugfixes (directory bandwidth performance):
17909 - Don't flush the zlib buffer aggressively when compressing
17910 directory information for clients. This should save about 7% of
17911 the bandwidth currently used for compressed descriptors and
17912 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
17914 o Minor features (security, memory wiping):
17915 - Ensure we securely wipe keys from memory after
17916 crypto_digest_get_digest and init_curve25519_keypair_from_file
17917 have finished using them. Resolves ticket 13477.
17919 o Minor features (security, out-of-memory handling):
17920 - When handling an out-of-memory condition, allocate less memory for
17921 temporary data structures. Fixes issue 10115.
17922 - When handling an out-of-memory condition, consider more types of
17923 buffers, including those on directory connections, and zlib
17924 buffers. Resolves ticket 11792.
17927 - When identity keypair is generated for first time, log a
17928 congratulatory message that links to the new relay lifecycle
17929 document. Implements feature 10427.
17931 o Minor features (client):
17932 - Clients are now willing to send optimistic data (before they
17933 receive a 'connected' cell) to relays of any version. (Relays
17934 without support for optimistic data are no longer supported on the
17935 Tor network.) Resolves ticket 13153.
17937 o Minor features (directory authorities):
17938 - Don't list relays with a bandwidth estimate of 0 in the consensus.
17939 Implements a feature proposed during discussion of bug 13000.
17940 - In tor-gencert, report an error if the user provides the same
17941 argument more than once.
17942 - If a directory authority can't find a best consensus method in the
17943 votes that it holds, it now falls back to its favorite consensus
17944 method. Previously, it fell back to method 1. Neither of these is
17945 likely to get enough signatures, but "fall back to favorite"
17946 doesn't require us to maintain support an obsolete consensus
17947 method. Implements part of proposal 215.
17949 o Minor features (logging):
17950 - On Unix-like systems, you can now use named pipes as the target of
17951 the Log option, and other options that try to append to files.
17952 Closes ticket 12061. Patch from "carlo von lynX".
17953 - When opening a log file at startup, send it every log message that
17954 we generated between startup and opening it. Previously, log
17955 messages that were generated before opening the log file were only
17956 logged to stdout. Closes ticket 6938.
17957 - Add a TruncateLogFile option to overwrite logs instead of
17958 appending to them. Closes ticket 5583.
17960 o Minor features (portability, Solaris):
17961 - Threads are no longer disabled by default on Solaris; we believe
17962 that the versions of Solaris with broken threading support are all
17963 obsolete by now. Resolves ticket 9495.
17965 o Minor features (relay):
17966 - Re-check our address after we detect a changed IP address from
17967 getsockname(). This ensures that the controller command "GETINFO
17968 address" will report the correct value. Resolves ticket 11582.
17970 - A new AccountingRule option lets Relays set whether they'd like
17971 AccountingMax to be applied separately to inbound and outbound
17972 traffic, or applied to the sum of inbound and outbound traffic.
17973 Resolves ticket 961. Patch by "chobe".
17975 o Minor features (testing networks):
17976 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
17977 the "Exit" flag regardless of their uptime, bandwidth, or exit
17978 policy. TestingTorNetwork must be set for this option to have any
17979 effect. Previously, authorities would take up to 35 minutes to
17980 give nodes the Exit flag in a test network. Partially implements
17983 o Minor features (validation):
17984 - Check all date/time values passed to tor_timegm and
17985 parse_rfc1123_time for validity, taking leap years into account.
17986 Improves HTTP header validation. Implemented with bug 13476.
17987 - In correct_tm(), limit the range of values returned by system
17988 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
17989 This means we don't have to deal with negative or too large dates,
17990 even if a clock is wrong. Otherwise we might fail to read a file
17991 written by us which includes such a date. Fixes bug 13476.
17993 o Minor bugfixes (bridge clients):
17994 - When configured to use a bridge without an identity digest (not
17995 recommended), avoid launching an extra channel to it when
17996 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
17998 o Minor bugfixes (bridges):
17999 - When DisableNetwork is set, do not launch pluggable transport
18000 plugins, and if any are running, terminate them. Fixes bug 13213;
18001 bugfix on 0.2.3.6-alpha.
18003 o Minor bugfixes (C correctness):
18004 - Fix several instances of possible integer overflow/underflow/NaN.
18005 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
18007 - In circuit_build_times_calculate_timeout() in circuitstats.c,
18008 avoid dividing by zero in the pareto calculations. This traps
18009 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
18011 - Fix an integer overflow in format_time_interval(). Fixes bug
18012 13393; bugfix on 0.2.0.10-alpha.
18013 - Set the correct day of year value when the system's localtime(_r)
18014 or gmtime(_r) functions fail to set struct tm. Not externally
18015 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
18016 - Avoid unlikely signed integer overflow in tor_timegm on systems
18017 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
18019 o Minor bugfixes (client):
18020 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
18021 BadExit flag are not considered worthy candidates. Fixes bug
18022 13066; bugfix on 0.1.2.3-alpha.
18023 - Use the consensus schedule for downloading consensuses, and not
18024 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
18025 - Handle unsupported or malformed SOCKS5 requests properly by
18026 responding with the appropriate error message before closing the
18027 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
18029 o Minor bugfixes (client, torrc):
18030 - Stop modifying the value of our DirReqStatistics torrc option just
18031 because we're not a bridge or relay. This bug was causing Tor
18032 Browser users to write "DirReqStatistics 0" in their torrc files
18033 as if they had chosen to change the config. Fixes bug 4244; bugfix
18035 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
18036 that our options have changed every time we SIGHUP. Fixes bug
18037 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
18039 o Minor bugfixes (controller):
18040 - Return an error when the second or later arguments of the
18041 "setevents" controller command are invalid events. Previously we
18042 would return success while silently skipping invalid events. Fixes
18043 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
18045 o Minor bugfixes (directory system):
18046 - Always believe that v3 directory authorities serve extra-info
18047 documents, whether they advertise "caches-extra-info" or not.
18048 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
18049 - When running as a v3 directory authority, advertise that you serve
18050 extra-info documents so that clients who want them can find them
18051 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
18052 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
18053 Previously, directories offering BRIDGE_DIRINFO and some other
18054 flag (i.e. microdescriptors or extrainfo) would be ignored when
18055 looking for bridges. Partially fixes bug 13163; bugfix
18058 o Minor bugfixes (networking):
18059 - Check for orconns and use connection_or_close_for_error() rather
18060 than connection_mark_for_close() directly in the getsockopt()
18061 failure case of connection_handle_write_impl(). Fixes bug 11302;
18062 bugfix on 0.2.4.4-alpha.
18064 o Minor bugfixes (relay):
18065 - When generating our family list, remove spaces from around the
18066 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
18067 - If our previous bandwidth estimate was 0 bytes, allow publishing a
18068 new relay descriptor immediately. Fixes bug 13000; bugfix
18071 o Minor bugfixes (testing networks):
18072 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
18073 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
18074 - Stop using the default authorities in networks which provide both
18075 AlternateDirAuthority and AlternateBridgeAuthority. Partially
18076 fixes bug 13163; bugfix on 0.2.0.13-alpha.
18078 o Minor bugfixes (testing):
18079 - Stop spawn test failures due to a race condition between the
18080 SIGCHLD handler updating the process status, and the test reading
18081 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
18083 o Minor bugfixes (testing, Windows):
18084 - Avoid passing an extra backslash when creating a temporary
18085 directory for running the unit tests on Windows. Fixes bug 12392;
18086 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
18088 o Minor bugfixes (windows):
18089 - Remove code to special-case handling of NTE_BAD_KEYSET when
18090 acquiring windows CryptoAPI context. This error can't actually
18091 occur for the parameters we're providing. Fixes bug 10816; bugfix
18094 o Minor bugfixes (zlib):
18095 - Avoid truncating a zlib stream when trying to finalize it with an
18096 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
18099 - Allow our configure script to build correctly with autoconf 2.62
18100 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
18101 - Improve the error message from ./configure to make it clear that
18102 when asciidoc has not been found, the user will have to either add
18103 --disable-asciidoc argument or install asciidoc. Resolves
18106 o Code simplification and refactoring:
18107 - Change the entry_is_live() function to take named bitfield
18108 elements instead of an unnamed list of booleans. Closes
18110 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
18111 Resolves ticket 12205.
18112 - Use calloc and reallocarray functions instead of multiply-
18113 then-malloc. This makes it less likely for us to fall victim to an
18114 integer overflow attack when allocating. Resolves ticket 12855.
18115 - Use the standard macro name SIZE_MAX, instead of our
18117 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
18118 functions which take them as arguments. Replace 0 with NO_DIRINFO
18119 in a function call for clarity. Seeks to prevent future issues
18121 - Avoid 4 null pointer errors under clang static analysis by using
18122 tor_assert() to prove that the pointers aren't null. Fixes
18124 - Rework the API of policies_parse_exit_policy() to use a bitmask to
18125 represent parsing options, instead of a confusing mess of
18126 booleans. Resolves ticket 8197.
18127 - Introduce a helper function to parse ExitPolicy in
18128 or_options_t structure.
18131 - Add a doc/TUNING document with tips for handling large numbers of
18132 TCP connections when running busy Tor relay. Update the warning
18133 message to point to this file when running out of sockets
18134 operating system is allowing to use simultaneously. Resolves
18137 o Removed features:
18138 - We no longer remind the user about configuration options that have
18139 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
18140 - Remove our old, non-weighted bandwidth-based node selection code.
18141 Previously, we used it as a fallback when we couldn't perform
18142 weighted bandwidth-based node selection. But that would only
18143 happen in the cases where we had no consensus, or when we had a
18144 consensus generated by buggy or ancient directory authorities. In
18145 either case, it's better to use the more modern, better maintained
18146 algorithm, with reasonable defaults for the weights. Closes
18148 - Remove the --disable-curve25519 configure option. Relays and
18149 clients now are required to support curve25519 and the
18151 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
18152 used to be deprecated synonyms for "StrictNodes", are now marked
18153 obsolete. Resolves ticket 12226.
18154 - Clients don't understand the BadDirectory flag in the consensus
18155 anymore, and ignore it.
18158 - Refactor the function that chooses guard nodes so that it can more
18159 easily be tested; write some tests for it.
18160 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
18161 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
18162 - Create unit tests for format_time_interval(). With bug 13393.
18163 - Add unit tests for tor_timegm signed overflow, tor_timegm and
18164 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
18165 tests (visible) fixes in bug 13476.
18166 - Add a "coverage-html" make target to generate HTML-visualized
18167 coverage results when building with --enable-coverage. (Requires
18168 lcov.) Patch from Kevin Murray.
18169 - Enable the backtrace handler (where supported) when running the
18171 - Revise all unit tests that used the legacy test_* macros to
18172 instead use the recommended tt_* macros. This patch was generated
18173 with coccinelle, to avoid manual errors. Closes ticket 13119.
18175 o Distribution (systemd):
18176 - systemd unit file: only allow tor to write to /var/lib/tor and
18177 /var/log/tor. The rest of the filesystem is accessible for reading
18178 only. Patch by intrigeri; resolves ticket 12751.
18179 - systemd unit file: ensure that the process and all its children
18180 can never gain new privileges. Patch by intrigeri; resolves
18182 - systemd unit file: set up /var/run/tor as writable for the Tor
18183 service. Patch by intrigeri; resolves ticket 13196.
18185 o Removed features (directory authorities):
18186 - Remove code that prevented authorities from listing Tor relays
18187 affected by CVE-2011-2769 as guards. These relays are already
18188 rejected altogether due to the minimum version requirement of
18189 0.2.3.16-alpha. Closes ticket 13152.
18190 - The "AuthDirRejectUnlisted" option no longer has any effect, as
18191 the fingerprints file (approved-routers) has been deprecated.
18192 - Directory authorities do not support being Naming dirauths anymore.
18193 The "NamingAuthoritativeDir" config option is now obsolete.
18194 - Directory authorities do not support giving out the BadDirectory
18196 - Directory authorities no longer advertise or support consensus
18197 methods 1 through 12 inclusive. These consensus methods were
18198 obsolete and/or insecure: maintaining the ability to support them
18199 served no good purpose. Implements part of proposal 215; closes
18202 o Testing (test-network.sh):
18203 - Stop using "echo -n", as some shells' built-in echo doesn't
18204 support "-n". Instead, use "/bin/echo -n". Partially fixes
18206 - Stop an apparent test-network hang when used with make -j2. Fixes
18208 - Add a --delay option to test-network.sh, which configures the
18209 delay before the chutney network tests for data transmission.
18210 Partially implements ticket 13161.
18213 Changes in version 0.2.5.10 - 2014-10-24
18214 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
18216 It adds several new security features, including improved
18217 denial-of-service resistance for relays, new compiler hardening
18218 options, and a system-call sandbox for hardened installations on Linux
18219 (requires seccomp2). The controller protocol has several new features,
18220 resolving IPv6 addresses should work better than before, and relays
18221 should be a little more CPU-efficient. We've added support for more
18222 OpenBSD and FreeBSD transparent proxy types. We've improved the build
18223 system and testing infrastructure to allow unit testing of more parts
18224 of the Tor codebase. Finally, we've addressed several nagging pluggable
18225 transport usability issues, and included numerous other small bugfixes
18226 and features mentioned below.
18228 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
18229 have accumulated many known flaws; everyone should upgrade.
18231 o Deprecated versions:
18232 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
18233 attention for some while.
18236 Changes in version 0.2.5.9-rc - 2014-10-20
18237 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
18238 series. It disables SSL3 in response to the recent "POODLE" attack
18239 (even though POODLE does not affect Tor). It also works around a crash
18240 bug caused by some operating systems' response to the "POODLE" attack
18241 (which does affect Tor). It also contains a few miscellaneous fixes.
18243 o Major security fixes:
18244 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18245 today support TLS 1.0 or later, so we can safely turn off support
18246 for this old (and insecure) protocol. Fixes bug 13426.
18248 o Major bugfixes (openssl bug workaround):
18249 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18250 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
18251 13471. This is a workaround for an OpenSSL bug.
18254 - Disable the sandbox name resolver cache when running tor-resolve:
18255 tor-resolve doesn't use the sandbox code, and turning it on was
18256 breaking attempts to do tor-resolve on a non-default server on
18257 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
18259 o Compilation fixes:
18260 - Build and run correctly on systems like OpenBSD-current that have
18261 patched OpenSSL to remove get_cipher_by_char and/or its
18262 implementations. Fixes issue 13325.
18264 o Downgraded warnings:
18265 - Downgrade the severity of the 'unexpected sendme cell from client'
18266 from 'warn' to 'protocol warning'. Closes ticket 8093.
18269 Changes in version 0.2.4.25 - 2014-10-20
18270 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
18271 (even though POODLE does not affect Tor). It also works around a crash
18272 bug caused by some operating systems' response to the "POODLE" attack
18273 (which does affect Tor).
18275 o Major security fixes (also in 0.2.5.9-rc):
18276 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
18277 today support TLS 1.0 or later, so we can safely turn off support
18278 for this old (and insecure) protocol. Fixes bug 13426.
18280 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
18281 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
18282 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
18283 13471. This is a workaround for an OpenSSL bug.
18286 Changes in version 0.2.5.8-rc - 2014-09-22
18287 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
18288 series. It fixes a bug that affects consistency and speed when
18289 connecting to hidden services, and it updates the location of one of
18290 the directory authorities.
18293 - Clients now send the correct address for their chosen rendezvous
18294 point when trying to access a hidden service. They used to send
18295 the wrong address, which would still work some of the time because
18296 they also sent the identity digest of the rendezvous point, and if
18297 the hidden service happened to try connecting to the rendezvous
18298 point from a relay that already had a connection open to it,
18299 the relay would reuse that connection. Now connections to hidden
18300 services should be more robust and faster. Also, this bug meant
18301 that clients were leaking to the hidden service whether they were
18302 on a little-endian (common) or big-endian (rare) system, which for
18303 some users might have reduced their anonymity. Fixes bug 13151;
18304 bugfix on 0.2.1.5-alpha.
18306 o Directory authority changes:
18307 - Change IP address for gabelmoo (v3 directory authority).
18310 Changes in version 0.2.4.24 - 2014-09-22
18311 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
18312 connecting to hidden services, and it updates the location of one of
18313 the directory authorities.
18316 - Clients now send the correct address for their chosen rendezvous
18317 point when trying to access a hidden service. They used to send
18318 the wrong address, which would still work some of the time because
18319 they also sent the identity digest of the rendezvous point, and if
18320 the hidden service happened to try connecting to the rendezvous
18321 point from a relay that already had a connection open to it,
18322 the relay would reuse that connection. Now connections to hidden
18323 services should be more robust and faster. Also, this bug meant
18324 that clients were leaking to the hidden service whether they were
18325 on a little-endian (common) or big-endian (rare) system, which for
18326 some users might have reduced their anonymity. Fixes bug 13151;
18327 bugfix on 0.2.1.5-alpha.
18329 o Directory authority changes:
18330 - Change IP address for gabelmoo (v3 directory authority).
18332 o Minor features (geoip):
18333 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18337 Changes in version 0.2.5.7-rc - 2014-09-11
18338 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
18339 release series, and some long-standing bugs related to ORPort reachability
18340 testing and failure to send CREATE cells. It is the first release
18341 candidate for the Tor 0.2.5.x series.
18343 o Major bugfixes (client, startup):
18344 - Start making circuits as soon as DisabledNetwork is turned off.
18345 When Tor started with DisabledNetwork set, it would correctly
18346 conclude that it shouldn't build circuits, but it would mistakenly
18347 cache this conclusion, and continue believing it even when
18348 DisableNetwork is set to 0. Fixes the bug introduced by the fix
18349 for bug 11200; bugfix on 0.2.5.4-alpha.
18350 - Resume expanding abbreviations for command-line options. The fix
18351 for bug 4647 accidentally removed our hack from bug 586 that
18352 rewrote HashedControlPassword to __HashedControlSessionPassword
18353 when it appears on the commandline (which allowed the user to set
18354 her own HashedControlPassword in the torrc file while the
18355 controller generates a fresh session password for each run). Fixes
18356 bug 12948; bugfix on 0.2.5.1-alpha.
18357 - Warn about attempts to run hidden services and relays in the same
18358 process: that's probably not a good idea. Closes ticket 12908.
18360 o Major bugfixes (relay):
18361 - Avoid queuing or sending destroy cells for circuit ID zero when we
18362 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
18363 Found and fixed by "cypherpunks".
18364 - Fix ORPort reachability detection on relays running behind a
18365 proxy, by correctly updating the "local" mark on the controlling
18366 channel when changing the address of an or_connection_t after the
18367 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
18369 o Minor features (bridge):
18370 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
18371 cookie file for the ExtORPort g+r by default.
18373 o Minor features (geoip):
18374 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
18377 o Minor bugfixes (logging):
18378 - Reduce the log severity of the "Pluggable transport proxy does not
18379 provide any needed transports and will not be launched." message,
18380 since Tor Browser includes several ClientTransportPlugin lines in
18381 its torrc-defaults file, leading every Tor Browser user who looks
18382 at her logs to see these notices and wonder if they're dangerous.
18383 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
18384 - Downgrade "Unexpected onionskin length after decryption" warning
18385 to a protocol-warn, since there's nothing relay operators can do
18386 about a client that sends them a malformed create cell. Resolves
18387 bug 12996; bugfix on 0.0.6rc1.
18388 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
18389 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
18390 - When logging information about an EXTEND2 or EXTENDED2 cell, log
18391 their names correctly. Fixes part of bug 12700; bugfix
18393 - When logging information about a relay cell whose command we don't
18394 recognize, log its command as an integer. Fixes part of bug 12700;
18395 bugfix on 0.2.1.10-alpha.
18396 - Escape all strings from the directory connection before logging
18397 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
18399 o Minor bugfixes (controller):
18400 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
18401 bug 12864; bugfix on 0.2.5.1-alpha.
18402 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
18403 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
18406 o Minor bugfixes (compilation):
18407 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
18408 bugfix on 0.2.5.5-alpha.
18409 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
18410 0.2.5.1-alpha. Patch from "NewEraCracker".
18411 - In routerlist_assert_ok(), don't take the address of a
18412 routerinfo's cache_info member unless that routerinfo is non-NULL.
18413 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
18414 - Fix a large number of false positive warnings from the clang
18415 analyzer static analysis tool. This should make real warnings
18416 easier for clang analyzer to find. Patch from "teor". Closes
18419 o Distribution (systemd):
18420 - Verify configuration file via ExecStartPre in the systemd unit
18421 file. Patch from intrigeri; resolves ticket 12730.
18422 - Explicitly disable RunAsDaemon in the systemd unit file. Our
18423 current systemd unit uses "Type = simple", so systemd does not
18424 expect tor to fork. If the user has "RunAsDaemon 1" in their
18425 torrc, then things won't work as expected. This is e.g. the case
18426 on Debian (and derivatives), since there we pass "--defaults-torrc
18427 /usr/share/tor/tor-service-defaults-torrc" (that contains
18428 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
18432 - Adjust the URLs in the README to refer to the new locations of
18433 several documents on the website. Fixes bug 12830. Patch from
18435 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
18439 Changes in version 0.2.5.6-alpha - 2014-07-28
18440 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
18441 risk from guard rotation, and fixes a variety of other issues to get
18442 us closer to a release candidate.
18444 o Major features (also in 0.2.4.23):
18445 - Make the number of entry guards configurable via a new
18446 NumEntryGuards consensus parameter, and the number of directory
18447 guards configurable via a new NumDirectoryGuards consensus
18448 parameter. Implements ticket 12688.
18450 o Major bugfixes (also in 0.2.4.23):
18451 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18452 implementation that caused incorrect results on 32-bit
18453 implementations when certain malformed inputs were used along with
18454 a small class of private ntor keys. This bug does not currently
18455 appear to allow an attacker to learn private keys or impersonate a
18456 Tor server, but it could provide a means to distinguish 32-bit Tor
18457 implementations from 64-bit Tor implementations. Fixes bug 12694;
18458 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18462 - Perform circuit cleanup operations even when circuit
18463 construction operations are disabled (because the network is
18464 disabled, or because there isn't enough directory information).
18465 Previously, when we were not building predictive circuits, we
18466 were not closing expired circuits either. Fixes bug 8387; bugfix on
18467 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
18468 became more strict about when we have "enough directory information
18469 to build circuits".
18472 - Authorities now assign the Guard flag to the fastest 25% of the
18473 network (it used to be the fastest 50%). Also raise the consensus
18474 weight that guarantees the Guard flag from 250 to 2000. For the
18475 current network, this results in about 1100 guards, down from 2500.
18476 This step paves the way for moving the number of entry guards
18477 down to 1 (proposal 236) while still providing reasonable expected
18478 performance for most users. Implements ticket 12690.
18479 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18481 - Slightly enhance the diagnostic message for bug 12184.
18483 o Minor bugfixes (also in 0.2.4.23):
18484 - Warn and drop the circuit if we receive an inbound 'relay early'
18485 cell. Those used to be normal to receive on hidden service circuits
18486 due to bug 1038, but the buggy Tor versions are long gone from
18487 the network so we can afford to resume watching for them. Resolves
18488 the rest of bug 1038; bugfix on 0.2.1.19.
18489 - Correct a confusing error message when trying to extend a circuit
18490 via the control protocol but we don't know a descriptor or
18491 microdescriptor for one of the specified relays. Fixes bug 12718;
18492 bugfix on 0.2.3.1-alpha.
18495 - Fix compilation when building with bufferevents enabled. (This
18496 configuration is still not expected to work, however.)
18497 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
18498 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
18500 - Compile correctly with builds and forks of OpenSSL (such as
18501 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
18502 0.2.1.1-alpha. Patch from "dhill".
18505 Changes in version 0.2.4.23 - 2014-07-28
18506 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
18507 guard rotation, and also backports several important fixes from the
18508 Tor 0.2.5 alpha release series.
18511 - Clients now look at the "usecreatefast" consensus parameter to
18512 decide whether to use CREATE_FAST or CREATE cells for the first hop
18513 of their circuit. This approach can improve security on connections
18514 where Tor's circuit handshake is stronger than the available TLS
18515 connection security levels, but the tradeoff is more computational
18516 load on guard relays. Implements proposal 221. Resolves ticket 9386.
18517 - Make the number of entry guards configurable via a new
18518 NumEntryGuards consensus parameter, and the number of directory
18519 guards configurable via a new NumDirectoryGuards consensus
18520 parameter. Implements ticket 12688.
18523 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
18524 implementation that caused incorrect results on 32-bit
18525 implementations when certain malformed inputs were used along with
18526 a small class of private ntor keys. This bug does not currently
18527 appear to allow an attacker to learn private keys or impersonate a
18528 Tor server, but it could provide a means to distinguish 32-bit Tor
18529 implementations from 64-bit Tor implementations. Fixes bug 12694;
18530 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
18534 - Warn and drop the circuit if we receive an inbound 'relay early'
18535 cell. Those used to be normal to receive on hidden service circuits
18536 due to bug 1038, but the buggy Tor versions are long gone from
18537 the network so we can afford to resume watching for them. Resolves
18538 the rest of bug 1038; bugfix on 0.2.1.19.
18539 - Correct a confusing error message when trying to extend a circuit
18540 via the control protocol but we don't know a descriptor or
18541 microdescriptor for one of the specified relays. Fixes bug 12718;
18542 bugfix on 0.2.3.1-alpha.
18543 - Avoid an illegal read from stack when initializing the TLS
18544 module using a version of OpenSSL without all of the ciphers
18545 used by the v2 link handshake. Fixes bug 12227; bugfix on
18546 0.2.4.8-alpha. Found by "starlight".
18549 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
18553 Changes in version 0.2.5.5-alpha - 2014-06-18
18554 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
18555 0.2.5.x release series, including a couple of DoS issues, some
18556 performance regressions, a large number of bugs affecting the Linux
18557 seccomp2 sandbox code, and various other bugfixes. It also adds
18558 diagnostic bugfixes for a few tricky issues that we're trying to
18561 o Major features (security, traffic analysis resistance):
18562 - Several major improvements to the algorithm used to decide when to
18563 close TLS connections. Previous versions of Tor closed connections
18564 at a fixed interval after the last time a non-padding cell was
18565 sent over the connection, regardless of the target of the
18566 connection. Now, we randomize the intervals by adding up to 50% of
18567 their base value, we measure the length of time since connection
18568 last had at least one circuit, and we allow connections to known
18569 ORs to remain open a little longer (15 minutes instead of 3
18570 minutes minimum). These changes should improve Tor's resistance
18571 against some kinds of traffic analysis, and lower some overhead
18572 from needlessly closed connections. Fixes ticket 6799.
18573 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
18575 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
18576 - Fix a memory leak that could occur if a microdescriptor parse
18577 fails during the tokenizing step. This bug could enable a memory
18578 exhaustion attack by directory servers. Fixes bug 11649; bugfix
18581 o Major bugfixes (security, directory authorities):
18582 - Directory authorities now include a digest of each relay's
18583 identity key as a part of its microdescriptor.
18585 This is a workaround for bug 11743 (reported by "cypherpunks"),
18586 where Tor clients do not support receiving multiple
18587 microdescriptors with the same SHA256 digest in the same
18588 consensus. When clients receive a consensus like this, they only
18589 use one of the relays. Without this fix, a hostile relay could
18590 selectively disable some client use of target relays by
18591 constructing a router descriptor with a different identity and the
18592 same microdescriptor parameters and getting the authorities to
18593 list it in a microdescriptor consensus. This fix prevents an
18594 attacker from causing a microdescriptor collision, because the
18595 router's identity is not forgeable.
18597 o Major bugfixes (relay):
18598 - Use a direct dirport connection when uploading non-anonymous
18599 descriptors to the directory authorities. Previously, relays would
18600 incorrectly use tunnel connections under a fairly wide variety of
18601 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
18602 - When a circuit accidentally has the same circuit ID for its
18603 forward and reverse direction, correctly detect the direction of
18604 cells using that circuit. Previously, this bug made roughly one
18605 circuit in a million non-functional. Fixes bug 12195; this is a
18606 bugfix on every version of Tor.
18608 o Major bugfixes (client, pluggable transports):
18609 - When managing pluggable transports, use OS notification facilities
18610 to learn if they have crashed, and don't attempt to kill any
18611 process that has already exited. Fixes bug 8746; bugfix
18614 o Minor features (diagnostic):
18615 - When logging a warning because of bug 7164, additionally check the
18616 hash table for consistency (as proposed on ticket 11737). This may
18617 help diagnose bug 7164.
18618 - When we log a heartbeat, log how many one-hop circuits we have
18619 that are at least 30 minutes old, and log status information about
18620 a few of them. This is an attempt to track down bug 8387.
18621 - When encountering an unexpected CR while writing text to a file on
18622 Windows, log the name of the file. Should help diagnosing
18624 - Give more specific warnings when a client notices that an onion
18625 handshake has failed. Fixes ticket 9635.
18626 - Add significant new logging code to attempt to diagnose bug 12184,
18627 where relays seem to run out of available circuit IDs.
18628 - Improve the diagnostic log message for bug 8387 even further to
18629 try to improve our odds of figuring out why one-hop directory
18630 circuits sometimes do not get closed.
18632 o Minor features (security, memory management):
18633 - Memory allocation tricks (mempools and buffer freelists) are now
18634 disabled by default. You can turn them back on with
18635 --enable-mempools and --enable-buf-freelists respectively. We're
18636 disabling these features because malloc performance is good enough
18637 on most platforms, and a similar feature in OpenSSL exacerbated
18638 exploitation of the Heartbleed attack. Resolves ticket 11476.
18640 o Minor features (security):
18641 - Apply the secure SipHash-2-4 function to the hash table mapping
18642 circuit IDs and channels to circuits. We missed this one when we
18643 were converting all the other hash functions to use SipHash back
18644 in 0.2.5.3-alpha. Resolves ticket 11750.
18646 o Minor features (build):
18647 - The configure script has a --disable-seccomp option to turn off
18648 support for libseccomp on systems that have it, in case it (or
18649 Tor's use of it) is broken. Resolves ticket 11628.
18651 o Minor features (other):
18652 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
18655 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
18656 - When running a hidden service, do not allow TunneledDirConns 0;
18657 this will keep the hidden service from running, and also
18658 make it publish its descriptors directly over HTTP. Fixes bug 10849;
18659 bugfix on 0.2.1.1-alpha.
18661 o Minor bugfixes (performance):
18662 - Avoid a bug where every successful connection made us recompute
18663 the flag telling us whether we have sufficient information to
18664 build circuits. Previously, we would forget our cached value
18665 whenever we successfully opened a channel (or marked a router as
18666 running or not running for any other reason), regardless of
18667 whether we had previously believed the router to be running. This
18668 forced us to run an expensive update operation far too often.
18669 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
18670 - Avoid using tor_memeq() for checking relay cell integrity. This
18671 removes a possible performance bottleneck. Fixes part of bug
18672 12169; bugfix on 0.2.1.31.
18674 o Minor bugfixes (compilation):
18675 - Fix compilation of test_status.c when building with MVSC. Bugfix
18676 on 0.2.5.4-alpha. Patch from Gisle Vanem.
18677 - Resolve GCC complaints on OpenBSD about discarding constness in
18678 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
18679 on 0.1.1.23. Patch from Dana Koch.
18680 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
18681 treatment of long and time_t as comparable types. Fixes part of
18682 bug 11633. Patch from Dana Koch.
18683 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
18684 11623; bugfix on 0.2.5.3-alpha.
18685 - When deciding whether to build the 64-bit curve25519
18686 implementation, detect platforms where we can compile 128-bit
18687 arithmetic but cannot link it. Fixes bug 11729; bugfix on
18688 0.2.4.8-alpha. Patch from "conradev".
18689 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
18690 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
18691 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
18694 o Minor bugfixes (Directory server):
18695 - When sending a compressed set of descriptors or microdescriptors,
18696 make sure to finalize the zlib stream. Previously, we would write
18697 all the compressed data, but if the last descriptor we wanted to
18698 send was missing or too old, we would not mark the stream as
18699 finished. This caused problems for decompression tools. Fixes bug
18700 11648; bugfix on 0.1.1.23.
18702 o Minor bugfixes (Linux seccomp sandbox):
18703 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
18704 11622; bugfix on 0.2.5.1-alpha.
18705 - Avoid crashing when re-opening listener ports with the seccomp
18706 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
18707 - Avoid crashing with the seccomp sandbox enabled along with
18708 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
18709 - When we receive a SIGHUP with the sandbox enabled, correctly
18710 support rotating our log files. Fixes bug 12032; bugfix
18712 - Avoid crash when running with sandboxing enabled and
18713 DirReqStatistics not disabled. Fixes bug 12035; bugfix
18715 - Fix a "BUG" warning when trying to write bridge-stats files with
18716 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
18718 - Prevent the sandbox from crashing on startup when run with the
18719 --enable-expensive-hardening configuration option. Fixes bug
18720 11477; bugfix on 0.2.5.4-alpha.
18721 - When running with DirPortFrontPage and sandboxing both enabled,
18722 reload the DirPortFrontPage correctly when restarting. Fixes bug
18723 12028; bugfix on 0.2.5.1-alpha.
18724 - Don't try to enable the sandbox when using the Tor binary to check
18725 its configuration, hash a passphrase, or so on. Doing so was
18726 crashing on startup for some users. Fixes bug 11609; bugfix
18728 - Avoid warnings when running with sandboxing and node statistics
18729 enabled at the same time. Fixes part of 12064; bugfix on
18730 0.2.5.1-alpha. Patch from Michael Wolf.
18731 - Avoid warnings when running with sandboxing enabled at the same
18732 time as cookie authentication, hidden services, or directory
18733 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
18734 - Do not allow options that require calls to exec to be enabled
18735 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
18736 bug 12043; bugfix on 0.2.5.1-alpha.
18737 - Handle failures in getpwnam()/getpwuid() when running with the
18738 User option set and the Linux syscall sandbox enabled. Fixes bug
18739 11946; bugfix on 0.2.5.1-alpha.
18740 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
18741 to avoid calling getaddrinfo() after installing the sandbox
18742 filters. Previously, it preloaded a cache with the IPv4 address
18743 for our hostname, and nothing else. Now, it loads the cache with
18744 every address that it used to initialize the Tor process. Fixes
18745 bug 11970; bugfix on 0.2.5.1-alpha.
18747 o Minor bugfixes (pluggable transports):
18748 - Enable the ExtORPortCookieAuthFile option, to allow changing the
18749 default location of the authentication token for the extended OR
18750 Port as used by sever-side pluggable transports. We had
18751 implemented this option before, but the code to make it settable
18752 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
18753 - Avoid another 60-second delay when starting Tor in a pluggable-
18754 transport-using configuration when we already have cached
18755 descriptors for our bridges. Fixes bug 11965; bugfix
18758 o Minor bugfixes (client):
18759 - Avoid "Tried to open a socket with DisableNetwork set" warnings
18760 when starting a client with bridges configured and DisableNetwork
18761 set. (Tor launcher starts Tor with DisableNetwork set the first
18762 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
18764 o Minor bugfixes (testing):
18765 - The Python parts of the test scripts now work on Python 3 as well
18766 as Python 2, so systems where '/usr/bin/python' is Python 3 will
18767 no longer have the tests break. Fixes bug 11608; bugfix
18769 - When looking for versions of python that we could run the tests
18770 with, check for "python2.7" and "python3.3"; previously we were
18771 only looking for "python", "python2", and "python3". Patch from
18772 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
18773 - Fix all valgrind warnings produced by the unit tests. There were
18774 over a thousand memory leak warnings previously, mostly produced
18775 by forgetting to free things in the unit test code. Fixes bug
18776 11618, bugfixes on many versions of Tor.
18778 o Minor bugfixes (tor-fw-helper):
18779 - Give a correct log message when tor-fw-helper fails to launch.
18780 (Previously, we would say something like "tor-fw-helper sent us a
18781 string we could not parse".) Fixes bug 9781; bugfix
18784 o Minor bugfixes (relay, threading):
18785 - Check return code on spawn_func() in cpuworker code, so that we
18786 don't think we've spawned a nonworking cpuworker and write junk to
18787 it forever. Fix related to bug 4345; bugfix on all released Tor
18788 versions. Found by "skruffy".
18789 - Use a pthread_attr to make sure that spawn_func() cannot return an
18790 error while at the same time launching a thread. Fix related to
18791 bug 4345; bugfix on all released Tor versions. Reported
18794 o Minor bugfixes (relay, oom prevention):
18795 - Correctly detect the total available system memory. We tried to do
18796 this in 0.2.5.4-alpha, but the code was set up to always return an
18797 error value, even on success. Fixes bug 11805; bugfix
18800 o Minor bugfixes (relay, other):
18801 - We now drop CREATE cells for already-existent circuit IDs and for
18802 zero-valued circuit IDs, regardless of other factors that might
18803 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
18805 - Avoid an illegal read from stack when initializing the TLS module
18806 using a version of OpenSSL without all of the ciphers used by the
18807 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
18809 - When rejecting DATA cells for stream_id zero, still count them
18810 against the circuit's deliver window so that we don't fail to send
18811 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
18813 o Minor bugfixes (logging):
18814 - Fix a misformatted log message about delayed directory fetches.
18815 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
18816 - Squelch a spurious LD_BUG message "No origin circuit for
18817 successful SOCKS stream" in certain hidden service failure cases;
18821 - Include a tor.service file in contrib/dist for use with systemd.
18822 Some distributions will be able to use this file unmodified;
18823 others will need to tweak it, or write their own. Patch from Jamie
18824 Nguyen; resolves ticket 8368.
18827 - Clean up several option names in the manpage to match their real
18828 names, add the missing documentation for a couple of testing and
18829 directory authority options, remove the documentation for a
18830 V2-directory fetching option that no longer exists. Resolves
18832 - Correct the documentation so that it lists the correct directory
18833 for the stats files. (They are in a subdirectory called "stats",
18835 - In the manpage, move more authority-only options into the
18836 directory authority section so that operators of regular directory
18837 caches don't get confused.
18840 - The contrib directory has been sorted and tidied. Before, it was
18841 an unsorted dumping ground for useful and not-so-useful things.
18842 Now, it is divided based on functionality, and the items which
18843 seemed to be nonfunctional or useless have been removed. Resolves
18844 ticket 8966; based on patches from "rl1987".
18847 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
18848 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
18849 - The TunnelDirConns and PreferTunnelledDirConns options no longer
18850 exist; tunneled directory connections have been available since
18851 0.1.2.5-alpha, and turning them off is not a good idea. This is a
18852 brute-force fix for 10849, where "TunnelDirConns 0" would break
18856 Changes in version 0.2.4.22 - 2014-05-16
18857 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
18858 alpha release series. These include blocking all authority signing
18859 keys that may have been affected by the OpenSSL "heartbleed" bug,
18860 choosing a far more secure set of TLS ciphersuites by default, closing
18861 a couple of memory leaks that could be used to run a target relay out
18862 of RAM, and several others.
18864 o Major features (security, backport from 0.2.5.4-alpha):
18865 - Block authority signing keys that were used on authorities
18866 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
18867 don't have any evidence that these keys _were_ compromised; we're
18868 doing this to be prudent.) Resolves ticket 11464.
18870 o Major bugfixes (security, OOM):
18871 - Fix a memory leak that could occur if a microdescriptor parse
18872 fails during the tokenizing step. This bug could enable a memory
18873 exhaustion attack by directory servers. Fixes bug 11649; bugfix
18876 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
18877 - The relay ciphersuite list is now generated automatically based on
18878 uniform criteria, and includes all OpenSSL ciphersuites with
18879 acceptable strength and forward secrecy. Previously, we had left
18880 some perfectly fine ciphersuites unsupported due to omission or
18881 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
18882 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
18883 - Relays now trust themselves to have a better view than clients of
18884 which TLS ciphersuites are better than others. (Thanks to bug
18885 11513, the relay list is now well-considered, whereas the client
18886 list has been chosen mainly for anti-fingerprinting purposes.)
18887 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
18888 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
18889 AES128. Resolves ticket 11528.
18890 - Clients now try to advertise the same list of ciphersuites as
18891 Firefox 28. This change enables selection of (fast) GCM
18892 ciphersuites, disables some strange old ciphers, and stops
18893 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
18894 Resolves ticket 11438.
18896 o Minor bugfixes (configuration, security):
18897 - When running a hidden service, do not allow TunneledDirConns 0:
18898 trying to set that option together with a hidden service would
18899 otherwise prevent the hidden service from running, and also make
18900 it publish its descriptors directly over HTTP. Fixes bug 10849;
18901 bugfix on 0.2.1.1-alpha.
18903 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
18904 - Avoid sending a garbage value to the controller when a circuit is
18905 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
18907 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
18908 - Stop leaking memory when we successfully resolve a PTR record.
18909 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
18911 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
18912 - Avoid 60-second delays in the bootstrapping process when Tor is
18913 launching for a second time while using bridges. Fixes bug 9229;
18914 bugfix on 0.2.0.3-alpha.
18916 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
18917 - Give the correct URL in the warning message when trying to run a
18918 relay on an ancient version of Windows. Fixes bug 9393.
18920 o Minor bugfixes (compilation):
18921 - Fix a compilation error when compiling with --disable-curve25519.
18922 Fixes bug 9700; bugfix on 0.2.4.17-rc.
18925 - Downgrade the warning severity for the the "md was still
18926 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
18927 for trying to diagnose this bug, and the current warning in
18928 earlier versions of tor achieves nothing useful. Addresses warning
18931 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
18932 - When we run out of usable circuit IDs on a channel, log only one
18933 warning for the whole channel, and describe how many circuits
18934 there were on the channel. Fixes part of ticket 11553.
18936 o Minor features (security, backport from 0.2.5.4-alpha):
18937 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
18938 leave the default at 8GBytes), to better support Raspberry Pi
18939 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
18941 o Documentation (backport from 0.2.5.4-alpha):
18942 - Correctly document that we search for a system torrc file before
18943 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
18947 Changes in version 0.2.5.4-alpha - 2014-04-25
18948 Tor 0.2.5.4-alpha includes several security and performance
18949 improvements for clients and relays, including blacklisting authority
18950 signing keys that were used while susceptible to the OpenSSL
18951 "heartbleed" bug, fixing two expensive functions on busy relays,
18952 improved TLS ciphersuite preference lists, support for run-time
18953 hardening on compilers that support AddressSanitizer, and more work on
18954 the Linux sandbox code.
18956 There are also several usability fixes for clients (especially clients
18957 that use bridges), two new TransPort protocols supported (one on
18958 OpenBSD, one on FreeBSD), and various other bugfixes.
18960 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
18961 have accumulated many known flaws; everyone should upgrade.
18963 o Major features (security):
18964 - If you don't specify MaxMemInQueues yourself, Tor now tries to
18965 pick a good value based on your total system memory. Previously,
18966 the default was always 8 GB. You can still override the default by
18967 setting MaxMemInQueues yourself. Resolves ticket 11396.
18968 - Block authority signing keys that were used on authorities
18969 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
18970 don't have any evidence that these keys _were_ compromised; we're
18971 doing this to be prudent.) Resolves ticket 11464.
18973 o Major features (relay performance):
18974 - Speed up server-side lookups of rendezvous and introduction point
18975 circuits by using hashtables instead of linear searches. These
18976 functions previously accounted between 3 and 7% of CPU usage on
18977 some busy relays. Resolves ticket 9841.
18978 - Avoid wasting CPU when extending a circuit over a channel that is
18979 nearly out of circuit IDs. Previously, we would do a linear scan
18980 over possible circuit IDs before finding one or deciding that we
18981 had exhausted our possibilities. Now, we try at most 64 random
18982 circuit IDs before deciding that we probably won't succeed. Fixes
18983 a possible root cause of ticket 11553.
18985 o Major features (seccomp2 sandbox, Linux only):
18986 - The seccomp2 sandbox can now run a test network for multiple hours
18987 without crashing. The sandbox is still experimental, and more bugs
18988 will probably turn up. To try it, enable "Sandbox 1" on a Linux
18989 host. Resolves ticket 11351.
18990 - Strengthen sandbox code: the sandbox can now test the arguments
18991 for rename(), and blocks _sysctl() entirely. Resolves another part
18993 - When the sandbox blocks a system call, it now tries to log a stack
18994 trace before exiting. Resolves ticket 11465.
18996 o Major bugfixes (TLS cipher selection):
18997 - The relay ciphersuite list is now generated automatically based on
18998 uniform criteria, and includes all OpenSSL ciphersuites with
18999 acceptable strength and forward secrecy. Previously, we had left
19000 some perfectly fine ciphersuites unsupported due to omission or
19001 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
19002 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
19003 - Relays now trust themselves to have a better view than clients of
19004 which TLS ciphersuites are better than others. (Thanks to bug
19005 11513, the relay list is now well-considered, whereas the client
19006 list has been chosen mainly for anti-fingerprinting purposes.)
19007 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
19008 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
19009 AES128. Resolves ticket 11528.
19010 - Clients now try to advertise the same list of ciphersuites as
19011 Firefox 28. This change enables selection of (fast) GCM
19012 ciphersuites, disables some strange old ciphers, and stops
19013 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
19014 Resolves ticket 11438.
19016 o Major bugfixes (bridge client):
19017 - Avoid 60-second delays in the bootstrapping process when Tor is
19018 launching for a second time while using bridges. Fixes bug 9229;
19019 bugfix on 0.2.0.3-alpha.
19021 o Minor features (transparent proxy, *BSD):
19022 - Support FreeBSD's ipfw firewall interface for TransPort ports on
19023 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
19024 10267; patch from "yurivict".
19025 - Support OpenBSD's divert-to rules with the pf firewall for
19026 transparent proxy ports. To enable it, set "TransProxyType
19027 pf-divert". This allows Tor to run a TransPort transparent proxy
19028 port on OpenBSD 4.4 or later without root privileges. See the
19029 pf.conf(5) manual page for information on configuring pf to use
19030 divert-to rules. Closes ticket 10896; patch from Dana Koch.
19032 o Minor features (security):
19033 - New --enable-expensive-hardening option to enable security
19034 hardening options that consume nontrivial amounts of CPU and
19035 memory. Right now, this includes AddressSanitizer and UbSan, which
19036 are supported in newer versions of GCC and Clang. Closes ticket
19039 o Minor features (log verbosity):
19040 - Demote the message that we give when a flushing connection times
19041 out for too long from NOTICE to INFO. It was usually meaningless.
19042 Resolves ticket 5286.
19043 - Don't log so many notice-level bootstrapping messages at startup
19044 about downloading descriptors. Previously, we'd log a notice
19045 whenever we learned about more routers. Now, we only log a notice
19046 at every 5% of progress. Fixes bug 9963.
19047 - Warn less verbosely when receiving a malformed
19048 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
19049 - When we run out of usable circuit IDs on a channel, log only one
19050 warning for the whole channel, and describe how many circuits
19051 there were on the channel. Fixes part of ticket 11553.
19053 o Minor features (relay):
19054 - If a circuit timed out for at least 3 minutes, check if we have a
19055 new external IP address, and publish a new descriptor with the new
19056 IP address if it changed. Resolves ticket 2454.
19058 o Minor features (controller):
19059 - Make the entire exit policy available from the control port via
19060 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
19062 - Because of the fix for ticket 11396, the real limit for memory
19063 usage may no longer match the configured MaxMemInQueues value. The
19064 real limit is now exposed via GETINFO limits/max-mem-in-queues.
19066 o Minor features (bridge client):
19067 - Report a more useful failure message when we can't connect to a
19068 bridge because we don't have the right pluggable transport
19069 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
19071 o Minor features (diagnostic):
19072 - Add more log messages to diagnose bug 7164, which causes
19073 intermittent "microdesc_free() called but md was still referenced"
19074 warnings. We now include more information, to figure out why we
19075 might be cleaning a microdescriptor for being too old if it's
19076 still referenced by a live node_t object.
19078 o Minor bugfixes (client, DNSPort):
19079 - When using DNSPort, try to respond to AAAA requests with AAAA
19080 answers. Previously, we hadn't looked at the request type when
19081 deciding which answer type to prefer. Fixes bug 10468; bugfix on
19083 - When receiving a DNS query for an unsupported record type, reply
19084 with no answer rather than with a NOTIMPL error. This behavior
19085 isn't correct either, but it will break fewer client programs, we
19086 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
19089 o Minor bugfixes (exit relay):
19090 - Stop leaking memory when we successfully resolve a PTR record.
19091 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
19093 o Minor bugfixes (bridge client):
19094 - Stop accepting bridge lines containing hostnames. Doing so would
19095 cause clients to perform DNS requests on the hostnames, which was
19096 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
19097 - Avoid a 60-second delay in the bootstrapping process when a Tor
19098 client with pluggable transports re-reads its configuration at
19099 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
19101 o Minor bugfixes (client, logging during bootstrap):
19102 - Warn only once if we start logging in an unsafe way. Previously,
19103 we complain as many times as we had problems. Fixes bug 9870;
19104 bugfix on 0.2.5.1-alpha.
19105 - Only report the first fatal bootstrap error on a given OR
19106 connection. This stops us from telling the controller bogus error
19107 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
19108 - Be more helpful when trying to run sandboxed on Linux without
19109 libseccomp. Instead of saying "Sandbox is not implemented on this
19110 platform", we now explain that we need to be built with
19111 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
19112 - Avoid generating spurious warnings when starting with
19113 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
19116 o Minor bugfixes (closing OR connections):
19117 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
19118 check if it's an or_connection_t and correctly call
19119 connection_or_close_for_error() rather than
19120 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
19122 - When closing all connections on setting DisableNetwork to 1, use
19123 connection_or_close_normally() rather than closing OR connections
19124 out from under the channel layer. Fixes bug 11306; bugfix on
19127 o Minor bugfixes (controller):
19128 - Avoid sending a garbage value to the controller when a circuit is
19129 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
19131 o Minor bugfixes (tor-fw-helper):
19132 - Allow tor-fw-helper to build again by adding src/ext to its
19133 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
19135 o Minor bugfixes (bridges):
19136 - Avoid potential crashes or bad behavior when launching a
19137 server-side managed proxy with ORPort or ExtORPort temporarily
19138 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
19140 o Minor bugfixes (platform-specific):
19141 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
19142 bug 11426; bugfix on 0.2.5.3-alpha.
19143 - When dumping a malformed directory object to disk, save it in
19144 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
19146 - Don't report failures from make_socket_reuseable() on incoming
19147 sockets on OSX: this can happen when incoming connections close
19148 early. Fixes bug 10081.
19150 o Minor bugfixes (trivial memory leaks):
19151 - Fix a small memory leak when signing a directory object. Fixes bug
19152 11275; bugfix on 0.2.4.13-alpha.
19153 - Free placeholder entries in our circuit table at exit; fixes a
19154 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
19155 - Don't re-initialize a second set of OpenSSL mutexes when starting
19156 up. Previously, we'd make one set of mutexes, and then immediately
19157 replace them with another. Fixes bug 11726; bugfix on
19159 - Resolve some memory leaks found by coverity in the unit tests, on
19160 exit in tor-gencert, and on a failure to compute digests for our
19161 own keys when generating a v3 networkstatus vote. These leaks
19162 should never have affected anyone in practice.
19164 o Minor bugfixes (hidden service):
19165 - Only retry attempts to connect to a chosen rendezvous point 8
19166 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
19168 o Minor bugfixes (misc code correctness):
19169 - Fix various instances of undefined behavior in channeltls.c,
19170 tor_memmem(), and eventdns.c that would cause us to construct
19171 pointers to memory outside an allocated object. (These invalid
19172 pointers were not accessed, but C does not even allow them to
19173 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
19174 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
19175 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
19176 fix some miscellaneous errors in our tests and codebase. Fixes bug
19177 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
19178 - Always check return values for unlink, munmap, UnmapViewOfFile;
19179 check strftime return values more often. In some cases all we can
19180 do is report a warning, but this may help prevent deeper bugs from
19181 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
19183 - Fix numerous warnings from the clang "scan-build" static analyzer.
19184 Some of these are programming style issues; some of them are false
19185 positives that indicated awkward code; some are undefined behavior
19186 cases related to constructing (but not using) invalid pointers;
19187 some are assumptions about API behavior; some are (harmlessly)
19188 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
19189 correct; and one or two are genuine bugs that weren't reachable
19190 from the rest of the program. Fixes bug 8793; bugfixes on many,
19194 - Build the torify.1 manpage again. Previously, we were only trying
19195 to build it when also building tor-fw-helper. That's why we didn't
19196 notice that we'd broken the ability to build it. Fixes bug 11321;
19197 bugfix on 0.2.5.1-alpha.
19198 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
19199 11061; bugfix on 0.2.4.7-alpha.
19200 - Correctly document that we search for a system torrc file before
19201 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
19203 - Resolve warnings from Doxygen.
19205 o Code simplifications and refactoring:
19206 - Remove is_internal_IP() function. Resolves ticket 4645.
19207 - Remove unused function circuit_dump_by_chan from circuitlist.c.
19208 Closes issue 9107; patch from "marek".
19209 - Change our use of the ENUM_BF macro to avoid declarations that
19212 o Deprecated versions:
19213 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
19214 attention for some while. Directory authorities no longer accept
19215 descriptors from relays running any version of Tor prior to Tor
19216 0.2.3.16-alpha. Resolves ticket 11149.
19219 - New macros in test.h to simplify writing mock-functions for unit
19220 tests. Part of ticket 11507. Patch from Dana Koch.
19221 - Complete tests for the status.c module. Resolves ticket 11507.
19222 Patch from Dana Koch.
19225 - Remove all code for the long unused v1 directory protocol.
19226 Resolves ticket 11070.
19229 Changes in version 0.2.5.3-alpha - 2014-03-22
19230 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
19231 two new anti-DoS features for Tor relays, resolves a bug that kept
19232 SOCKS5 support for IPv6 from working, fixes several annoying usability
19233 issues for bridge users, and removes more old code for unused
19236 The Tor 0.2.5.x release series is now in patch-freeze: no feature
19237 patches not already written will be considered for inclusion in 0.2.5.x.
19239 o Major features (relay security, DoS-resistance):
19240 - When deciding whether we have run out of memory and we need to
19241 close circuits, also consider memory allocated in buffers for
19242 streams attached to each circuit.
19244 This change, which extends an anti-DoS feature introduced in
19245 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
19246 better resist more memory-based DoS attacks than before. Since the
19247 MaxMemInCellQueues option now applies to all queues, it is renamed
19248 to MaxMemInQueues. This feature fixes bug 10169.
19249 - Avoid hash-flooding denial-of-service attacks by using the secure
19250 SipHash-2-4 hash function for our hashtables. Without this
19251 feature, an attacker could degrade performance of a targeted
19252 client or server by flooding their data structures with a large
19253 number of entries to be stored at the same hash table position,
19254 thereby slowing down the Tor instance. With this feature, hash
19255 table positions are derived from a randomized cryptographic key,
19256 and an attacker cannot predict which entries will collide. Closes
19258 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
19259 the default at 8GBytes), to better support Raspberry Pi users. Fixes
19260 bug 9686; bugfix on 0.2.4.14-alpha.
19262 o Minor features (bridges, pluggable transports):
19263 - Bridges now write the SHA1 digest of their identity key
19264 fingerprint (that is, a hash of a hash of their public key) to
19265 notice-level logs, and to a new hashed-fingerprint file. This
19266 information will help bridge operators look up their bridge in
19267 Globe and similar tools. Resolves ticket 10884.
19268 - Improve the message that Tor displays when running as a bridge
19269 using pluggable transports without an Extended ORPort listener.
19270 Also, log the message in the log file too. Resolves ticket 11043.
19272 o Minor features (other):
19273 - Add a new option, PredictedPortsRelevanceTime, to control how long
19274 after having received a request to connect to a given port Tor
19275 will try to keep circuits ready in anticipation of future requests
19276 for that port. Patch from "unixninja92"; implements ticket 9176.
19277 - Generate a warning if any ports are listed in the SocksPolicy,
19278 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
19279 AuthDirBadExit options. (These options only support address
19280 ranges.) Fixes part of ticket 11108.
19281 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
19284 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
19285 - Build without warnings under clang 3.4. (We have some macros that
19286 define static functions only some of which will get used later in
19287 the module. Starting with clang 3.4, these give a warning unless the
19288 unused attribute is set on them.) Resolves ticket 10904.
19289 - Fix build warnings about missing "a2x" comment when building the
19290 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
19291 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
19293 o Minor bugfixes (client):
19294 - Improve the log message when we can't connect to a hidden service
19295 because all of the hidden service directory nodes hosting its
19296 descriptor are excluded. Improves on our fix for bug 10722, which
19297 was a bugfix on 0.2.0.10-alpha.
19298 - Raise a control port warning when we fail to connect to all of
19299 our bridges. Previously, we didn't inform the controller, and
19300 the bootstrap process would stall. Fixes bug 11069; bugfix on
19302 - Exit immediately when a process-owning controller exits.
19303 Previously, tor relays would wait for a little while after their
19304 controller exited, as if they had gotten an INT signal -- but this
19305 was problematic, since there was no feedback for the user. To do a
19306 clean shutdown, controllers should send an INT signal and give Tor
19307 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
19308 - Stop attempting to connect to bridges before our pluggable
19309 transports are configured (harmless but resulted in some erroneous
19310 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
19311 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
19312 generating incorrect SOCKS5 responses, and confusing client
19313 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
19315 o Minor bugfixes (relays and bridges):
19316 - Avoid crashing on a malformed resolv.conf file when running a
19317 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
19318 - Non-exit relays no longer launch mock DNS requests to check for
19319 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
19320 non-exit relays stopped servicing DNS requests. Fixes bug 965;
19321 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
19322 - Bridges now report complete directory request statistics. Related
19323 to bug 5824; bugfix on 0.2.2.1-alpha.
19324 - Bridges now never collect statistics that were designed for
19325 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
19326 - Stop giving annoying warning messages when we decide not to launch
19327 a pluggable transport proxy that we don't need (because there are
19328 no bridges configured to use it). Resolves ticket 5018; bugfix
19330 - Give the correct URL in the warning message when trying to run a
19331 relay on an ancient version of Windows. Fixes bug 9393.
19333 o Minor bugfixes (backtrace support):
19334 - Support automatic backtraces on more platforms by using the
19335 "-fasynchronous-unwind-tables" compiler option. This option is
19336 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
19337 is on by default and table generation is not. This doesn't yet
19338 add Windows support; only Linux, OSX, and some BSDs are affected.
19339 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
19340 - Avoid strange behavior if two threads hit failed assertions at the
19341 same time and both try to log backtraces at once. (Previously, if
19342 this had happened, both threads would have stored their intermediate
19343 results in the same buffer, and generated junk outputs.) Reported by
19344 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
19345 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
19346 0.2.5.2-alpha; patch from Nick Hopper.
19348 o Minor bugfixes (unit tests):
19349 - Fix a small bug in the unit tests that might have made the tests
19350 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
19351 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
19354 - Remove all remaining code related to version-0 hidden service
19355 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
19356 the rest of bug 10841.
19359 - Document in the manpage that "KBytes" may also be written as
19360 "kilobytes" or "KB", that "Kbits" may also be written as
19361 "kilobits", and so forth. Closes ticket 9222.
19362 - Document that the ClientOnly config option overrides ORPort.
19363 Our old explanation made ClientOnly sound as though it did
19364 nothing at all. Resolves bug 9059.
19365 - Explain that SocksPolicy, DirPolicy, and similar options don't
19366 take port arguments. Fixes the other part of ticket 11108.
19367 - Fix a comment about the rend_server_descriptor_t.protocols field
19368 to more accurately describe its range. Also, make that field
19369 unsigned, to more accurately reflect its usage. Fixes bug 9099;
19370 bugfix on 0.2.1.5-alpha.
19371 - Fix the manpage's description of HiddenServiceAuthorizeClient:
19372 the maximum client name length is 16, not 19. Fixes bug 11118;
19373 bugfix on 0.2.1.6-alpha.
19375 o Code simplifications and refactoring:
19376 - Get rid of router->address, since in all cases it was just the
19377 string representation of router->addr. Resolves ticket 5528.
19379 o Test infrastructure:
19380 - Update to the latest version of tinytest.
19381 - Improve the tinytest implementation of string operation tests so
19382 that comparisons with NULL strings no longer crash the tests; they
19383 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
19386 Changes in version 0.2.4.21 - 2014-02-28
19387 Tor 0.2.4.21 further improves security against potential adversaries who
19388 find breaking 1024-bit crypto doable, and backports several stability
19389 and robustness patches from the 0.2.5 branch.
19391 o Major features (client security):
19392 - When we choose a path for a 3-hop circuit, make sure it contains
19393 at least one relay that supports the NTor circuit extension
19394 handshake. Otherwise, there is a chance that we're building
19395 a circuit that's worth attacking by an adversary who finds
19396 breaking 1024-bit crypto doable, and that chance changes the game
19397 theory. Implements ticket 9777.
19400 - Do not treat streams that fail with reason
19401 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
19402 since it could also indicate an ENETUNREACH connection error. Fixes
19403 part of bug 10777; bugfix on 0.2.4.8-alpha.
19405 o Code simplification and refactoring:
19406 - Remove data structures which were introduced to implement the
19407 CellStatistics option: they are now redundant with the new timestamp
19408 field in the regular packed_cell_t data structure, which we did
19409 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
19412 - Always clear OpenSSL bignums before freeing them -- even bignums
19413 that don't contain secrets. Resolves ticket 10793. Patch by
19415 - Build without warnings under clang 3.4. (We have some macros that
19416 define static functions only some of which will get used later in
19417 the module. Starting with clang 3.4, these give a warning unless the
19418 unused attribute is set on them.) Resolves ticket 10904.
19419 - Update geoip and geoip6 files to the February 7 2014 Maxmind
19420 GeoLite2 Country database.
19423 - Set the listen() backlog limit to the largest actually supported
19424 on the system, not to the value in a header file. Fixes bug 9716;
19425 bugfix on every released Tor.
19426 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
19427 exit node as a NOROUTE error, not an INTERNAL error, since they
19428 can apparently happen when trying to connect to the wrong sort
19429 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
19430 - Fix build warnings about missing "a2x" comment when building the
19431 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
19432 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
19433 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
19434 not entirely remove it from the connection lists. Fixes bug 9602;
19435 bugfix on 0.2.4.4-alpha.
19436 - Fix a segmentation fault in our benchmark code when running with
19437 Fedora's OpenSSL package, or any other OpenSSL that provides
19438 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
19439 - Turn "circuit handshake stats since last time" log messages into a
19440 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
19442 o Documentation fixes:
19443 - Document that all but one DirPort entry must have the NoAdvertise
19444 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
19447 Changes in version 0.2.5.2-alpha - 2014-02-13
19448 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
19449 like the "poor random number generation" fix and the "building too many
19450 circuits" fix. It also further improves security against potential
19451 adversaries who find breaking 1024-bit crypto doable, and launches
19452 pluggable transports on demand (which gets us closer to integrating
19453 pluggable transport support by default -- not to be confused with Tor
19454 bundles enabling pluggable transports and bridges by default).
19456 o Major features (client security):
19457 - When we choose a path for a 3-hop circuit, make sure it contains
19458 at least one relay that supports the NTor circuit extension
19459 handshake. Otherwise, there is a chance that we're building
19460 a circuit that's worth attacking by an adversary who finds
19461 breaking 1024-bit crypto doable, and that chance changes the game
19462 theory. Implements ticket 9777.
19463 - Clients now look at the "usecreatefast" consensus parameter to
19464 decide whether to use CREATE_FAST or CREATE cells for the first hop
19465 of their circuit. This approach can improve security on connections
19466 where Tor's circuit handshake is stronger than the available TLS
19467 connection security levels, but the tradeoff is more computational
19468 load on guard relays. Implements proposal 221. Resolves ticket 9386.
19470 o Major features (bridges):
19471 - Don't launch pluggable transport proxies if we don't have any
19472 bridges configured that would use them. Now we can list many
19473 pluggable transports, and Tor will dynamically start one when it
19474 hears a bridge address that needs it. Resolves ticket 5018.
19475 - The bridge directory authority now assigns status flags (Stable,
19476 Guard, etc) to bridges based on thresholds calculated over all
19477 Running bridges. Now bridgedb can finally make use of its features
19478 to e.g. include at least one Stable bridge in its answers. Fixes
19481 o Major features (other):
19482 - Extend ORCONN controller event to include an "ID" parameter,
19483 and add four new controller event types CONN_BW, CIRC_BW,
19484 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
19485 The new events are emitted in private Tor networks only, with the
19486 goal of being able to better track performance and load during
19487 full-network simulations. Implements proposal 218 and ticket 7359.
19488 - On some platforms (currently: recent OSX versions, glibc-based
19489 platforms that support the ELF format, and a few other
19490 Unix-like operating systems), Tor can now dump stack traces
19491 when a crash occurs or an assertion fails. By default, traces
19492 are dumped to stderr (if possible) and to any logs that are
19493 reporting errors. Implements ticket 9299.
19496 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
19497 not entirely remove it from the connection lists. Fixes bug 9602;
19498 bugfix on 0.2.4.4-alpha.
19499 - Do not treat streams that fail with reason
19500 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
19501 since it could also indicate an ENETUNREACH connection error. Fixes
19502 part of bug 10777; bugfix on 0.2.4.8-alpha.
19504 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
19505 - Do not allow OpenSSL engines to replace the PRNG, even when
19506 HardwareAccel is set. The only default builtin PRNG engine uses
19507 the Intel RDRAND instruction to replace the entire PRNG, and
19508 ignores all attempts to seed it with more entropy. That's
19509 cryptographically stupid: the right response to a new alleged
19510 entropy source is never to discard all previously used entropy
19511 sources. Fixes bug 10402; works around behavior introduced in
19512 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
19514 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
19515 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
19516 - Avoid launching spurious extra circuits when a stream is pending.
19517 This fixes a bug where any circuit that _wasn't_ unusable for new
19518 streams would be treated as if it were, causing extra circuits to
19519 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
19521 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19522 - No longer stop reading or writing on cpuworker connections when
19523 our rate limiting buckets go empty. Now we should handle circuit
19524 handshake requests more promptly. Resolves bug 9731.
19525 - Stop trying to bootstrap all our directory information from
19526 only our first guard. Discovered while fixing bug 9946; bugfix
19529 o Minor features (bridges, pluggable transports):
19530 - Add threshold cutoffs to the networkstatus document created by
19531 the Bridge Authority. Fixes bug 1117.
19532 - On Windows, spawn background processes using the CREATE_NO_WINDOW
19533 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
19534 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
19535 Vidalia set this option for us.) Implements ticket 10297.
19537 o Minor features (security):
19538 - Always clear OpenSSL bignums before freeing them -- even bignums
19539 that don't contain secrets. Resolves ticket 10793. Patch by
19542 o Minor features (config options and command line):
19543 - Add an --allow-missing-torrc commandline option that tells Tor to
19544 run even if the configuration file specified by -f is not available.
19545 Implements ticket 10060.
19546 - Add support for the TPROXY transparent proxying facility on Linux.
19547 See documentation for the new TransProxyType option for more
19548 details. Implementation by "thomo". Closes ticket 10582.
19550 o Minor features (controller):
19551 - Add a new "HS_DESC" controller event that reports activities
19552 related to hidden service descriptors. Resolves ticket 8510.
19553 - New "DROPGUARDS" controller command to forget all current entry
19554 guards. Not recommended for ordinary use, since replacing guards
19555 too frequently makes several attacks easier. Resolves ticket 9934;
19558 o Minor features (build):
19559 - Assume that a user using ./configure --host wants to cross-compile,
19560 and give an error if we cannot find a properly named
19561 tool-chain. Add a --disable-tool-name-check option to proceed
19562 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
19563 - If we run ./configure and the compiler recognizes -fstack-protector
19564 but the linker rejects it, warn the user about a potentially missing
19565 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
19567 o Minor features (testing):
19568 - If Python is installed, "make check" now runs extra tests beyond
19569 the unit test scripts.
19570 - When bootstrapping a test network, sometimes very few relays get
19571 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
19572 specify a set of relays which should be voted Guard regardless of
19573 their uptime or bandwidth. Addresses ticket 9206.
19575 o Minor features (log messages):
19576 - When ServerTransportPlugin is set on a bridge, Tor can write more
19577 useful statistics about bridge use in its extrainfo descriptors,
19578 but only if the Extended ORPort ("ExtORPort") is set too. Add a
19579 log message to inform the user in this case. Resolves ticket 9651.
19580 - When receiving a new controller connection, log the origin address.
19581 Resolves ticket 9698; patch from "sigpipe".
19582 - When logging OpenSSL engine status at startup, log the status of
19583 more engines. Fixes ticket 10043; patch from Joshua Datko.
19584 - Turn "circuit handshake stats since last time" log messages into a
19585 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
19587 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19588 - Improve the circuit queue out-of-memory handler. Previously, when
19589 we ran low on memory, we'd close whichever circuits had the most
19590 queued cells. Now, we close those that have the *oldest* queued
19591 cells, on the theory that those are most responsible for us
19592 running low on memory. Based on analysis from a forthcoming paper
19593 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
19594 - Generate bootstrapping status update events correctly when fetching
19595 microdescriptors. Fixes bug 9927.
19596 - Update to the October 2 2013 Maxmind GeoLite Country database.
19598 o Minor bugfixes (clients):
19599 - When closing a channel that has already been open, do not close
19600 pending circuits that were waiting to connect to the same relay.
19601 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
19604 o Minor bugfixes (relays):
19605 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
19606 exit node as a NOROUTE error, not an INTERNAL error, since they
19607 can apparently happen when trying to connect to the wrong sort
19608 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
19610 o Minor bugfixes (bridges):
19611 - Fix a bug where the first connection works to a bridge that uses a
19612 pluggable transport with client-side parameters, but we don't send
19613 the client-side parameters on subsequent connections. (We don't
19614 use any pluggable transports with client-side parameters yet,
19615 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
19616 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
19618 o Minor bugfixes (node selection):
19619 - If ExcludeNodes is set, consider non-excluded hidden service
19620 directory servers before excluded ones. Do not consider excluded
19621 hidden service directory servers at all if StrictNodes is
19622 set. (Previously, we would sometimes decide to connect to those
19623 servers, and then realize before we initiated a connection that
19624 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
19625 Reported by "mr-4".
19626 - If we set the ExitNodes option but it doesn't include any nodes
19627 that have the Exit flag, we would choose not to bootstrap. Now we
19628 bootstrap so long as ExitNodes includes nodes which can exit to
19629 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
19631 o Minor bugfixes (controller and command-line):
19632 - If changing a config option via "setconf" fails in a recoverable
19633 way, we used to nonetheless write our new control ports to the
19634 file described by the "ControlPortWriteToFile" option. Now we only
19635 write out that file if we successfully switch to the new config
19636 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
19637 - When a command-line option such as --version or --help that
19638 ordinarily implies --hush appears on the command line along with
19639 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
19640 only if it appeared later on the command line. Fixes bug 9578;
19641 bugfix on 0.2.5.1-alpha.
19643 o Minor bugfixes (code correctness):
19644 - Previously we used two temporary files when writing descriptors to
19645 disk; now we only use one. Fixes bug 1376.
19646 - Remove an erroneous (but impossible and thus harmless) pointer
19647 comparison that would have allowed compilers to skip a bounds
19648 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
19649 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
19650 - Fix an always-true assertion in pluggable transports code so it
19651 actually checks what it was trying to check. Fixes bug 10046;
19652 bugfix on 0.2.3.9-alpha. Found by "dcb".
19654 o Minor bugfixes (protocol correctness):
19655 - When receiving a VERSIONS cell with an odd number of bytes, close
19656 the connection immediately since the cell is malformed. Fixes bug
19657 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
19660 o Minor bugfixes (build):
19661 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
19662 turned off (that is, without support for v2 link handshakes). Fixes
19663 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
19664 - Fix compilation warnings and startup issues when running with
19665 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
19667 - Fix compilation on Solaris 9, which didn't like us having an
19668 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
19670 o Minor bugfixes (testing):
19671 - Fix a segmentation fault in our benchmark code when running with
19672 Fedora's OpenSSL package, or any other OpenSSL that provides
19673 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
19675 o Minor bugfixes (log messages):
19676 - Fix a bug where clients using bridges would report themselves
19677 as 50% bootstrapped even without a live consensus document.
19678 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
19679 - Suppress a warning where, if there's only one directory authority
19680 in the network, we would complain that votes and signatures cannot
19681 be uploaded to other directory authorities. Fixes bug 10842;
19682 bugfix on 0.2.2.26-beta.
19683 - Report bootstrapping progress correctly when we're downloading
19684 microdescriptors. We had updated our "do we have enough microdescs
19685 to begin building circuits?" logic most recently in 0.2.4.10-alpha
19686 (see bug 5956), but we left the bootstrap status event logic at
19687 "how far through getting 1/4 of them are we?" Fixes bug 9958;
19688 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
19690 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
19691 - Avoid a crash bug when starting with a corrupted microdescriptor
19692 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
19693 - If we fail to dump a previously cached microdescriptor to disk, avoid
19694 freeing duplicate data later on. Fixes bug 10423; bugfix on
19695 0.2.4.13-alpha. Spotted by "bobnomnom".
19697 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19698 - Correctly log long IPv6 exit policies, instead of truncating them
19699 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
19700 - Our default TLS ecdhe groups were backwards: we meant to be using
19701 P224 for relays (for performance win) and P256 for bridges (since
19702 it is more common in the wild). Instead we had it backwards. After
19703 reconsideration, we decided that the default should be P256 on all
19704 hosts, since its security is probably better, and since P224 is
19705 reportedly used quite little in the wild. Found by "skruffy" on
19706 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
19707 - Free directory authority certificate download statuses on exit
19708 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
19710 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19711 - If the guard we choose first doesn't answer, we would try the
19712 second guard, but once we connected to the second guard we would
19713 abandon it and retry the first one, slowing down bootstrapping.
19714 The fix is to treat all our initially chosen guards as acceptable
19715 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
19716 - Fix an assertion failure that would occur when disabling the
19717 ORPort setting on a running Tor process while accounting was
19718 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
19719 - When examining the list of network interfaces to find our address,
19720 do not consider non-running or disabled network interfaces. Fixes
19721 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
19722 - Avoid an off-by-one error when checking buffer boundaries when
19723 formatting the exit status of a pluggable transport helper.
19724 This is probably not an exploitable bug, but better safe than
19725 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
19728 o Removed code and features:
19729 - Clients now reject any directory authority certificates lacking
19730 a dir-key-crosscert element. These have been included since
19731 0.2.1.9-alpha, so there's no real reason for them to be optional
19732 any longer. Completes proposal 157. Resolves ticket 10162.
19733 - Remove all code that existed to support the v2 directory system,
19734 since there are no longer any v2 directory authorities. Resolves
19736 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
19737 options, which were used for designating authorities as "Hidden
19738 service authorities". There has been no use of hidden service
19739 authorities since 0.2.2.1-alpha, when we stopped uploading or
19740 downloading v0 hidden service descriptors. Fixes bug 10881; also
19741 part of a fix for bug 10841.
19743 o Code simplification and refactoring:
19744 - Remove some old fallback code designed to keep Tor clients working
19745 in a network with only two working relays. Elsewhere in the code we
19746 have long since stopped supporting such networks, so there wasn't
19747 much point in keeping it around. Addresses ticket 9926.
19748 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
19749 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
19750 - Remove data structures which were introduced to implement the
19751 CellStatistics option: they are now redundant with the addition
19752 of a timestamp to the regular packed_cell_t data structure, which
19753 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
19756 o Documentation (man page) fixes:
19757 - Update manpage to describe some of the files you can expect to
19758 find in Tor's DataDirectory. Addresses ticket 9839.
19759 - Document that all but one DirPort entry must have the NoAdvertise
19760 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
19762 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
19763 - Clarify the usage and risks of setting the ContactInfo torrc line
19764 for your relay or bridge. Resolves ticket 9854.
19765 - Add anchors to the manpage so we can link to the html version of
19766 the documentation for specific options. Resolves ticket 9866.
19767 - Replace remaining references to DirServer in man page and
19768 log entries. Resolves ticket 10124.
19771 - Make the "tor-gencert" tool used by directory authority operators
19772 create 2048-bit signing keys by default (rather than 1024-bit, since
19773 1024-bit is uncomfortably small these days). Addresses ticket 10324.
19776 Changes in version 0.2.4.20 - 2013-12-22
19777 Tor 0.2.4.20 fixes potentially poor random number generation for users
19778 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
19779 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
19780 and 4) have no state file in their DataDirectory (as would happen on
19781 first start). Users who generated relay or hidden service identity
19782 keys in such a situation should discard them and generate new ones.
19784 This release also fixes a logic error that caused Tor clients to build
19785 many more preemptive circuits than they actually need.
19788 - Do not allow OpenSSL engines to replace the PRNG, even when
19789 HardwareAccel is set. The only default builtin PRNG engine uses
19790 the Intel RDRAND instruction to replace the entire PRNG, and
19791 ignores all attempts to seed it with more entropy. That's
19792 cryptographically stupid: the right response to a new alleged
19793 entropy source is never to discard all previously used entropy
19794 sources. Fixes bug 10402; works around behavior introduced in
19795 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
19797 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
19798 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
19799 - Avoid launching spurious extra circuits when a stream is pending.
19800 This fixes a bug where any circuit that _wasn't_ unusable for new
19801 streams would be treated as if it were, causing extra circuits to
19802 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
19805 - Avoid a crash bug when starting with a corrupted microdescriptor
19806 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
19807 - If we fail to dump a previously cached microdescriptor to disk, avoid
19808 freeing duplicate data later on. Fixes bug 10423; bugfix on
19809 0.2.4.13-alpha. Spotted by "bobnomnom".
19812 Changes in version 0.2.4.19 - 2013-12-11
19813 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
19814 (1986-2013). Aaron worked on diverse projects including helping to guide
19815 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
19816 transparency to the U.S government's PACER documents, and contributing
19817 design and development for Tor and Tor2Web. Aaron was one of the latest
19818 martyrs in our collective fight for civil liberties and human rights,
19819 and his death is all the more painful because he was one of us.
19821 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
19822 a new circuit handshake and link encryption that use ECC to provide
19823 better security and efficiency; makes relays better manage circuit
19824 creation requests; uses "directory guards" to reduce client enumeration
19825 risks; makes bridges collect and report statistics about the pluggable
19826 transports they support; cleans up and improves our geoip database;
19827 gets much closer to IPv6 support for clients, bridges, and relays; makes
19828 directory authorities use measured bandwidths rather than advertised
19829 ones when computing flags and thresholds; disables client-side DNS
19830 caching to reduce tracking risks; and fixes a big bug in bridge
19831 reachability testing. This release introduces two new design
19832 abstractions in the code: a new "channel" abstraction between circuits
19833 and or_connections to allow for implementing alternate relay-to-relay
19834 transports, and a new "circuitmux" abstraction storing the queue of
19835 circuits for a channel. The release also includes many stability,
19836 security, and privacy fixes.
19839 Changes in version 0.2.4.18-rc - 2013-11-16
19840 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
19841 series. It takes a variety of fixes from the 0.2.5.x branch to improve
19842 stability, performance, and better handling of edge cases.
19845 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
19846 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
19847 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
19848 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
19849 them to solve bug 6033.)
19852 - No longer stop reading or writing on cpuworker connections when
19853 our rate limiting buckets go empty. Now we should handle circuit
19854 handshake requests more promptly. Resolves bug 9731.
19855 - If we are unable to save a microdescriptor to the journal, do not
19856 drop it from memory and then reattempt downloading it. Fixes bug
19857 9645; bugfix on 0.2.2.6-alpha.
19858 - Stop trying to bootstrap all our directory information from
19859 only our first guard. Discovered while fixing bug 9946; bugfix
19861 - The new channel code sometimes lost track of in-progress circuits,
19862 causing long-running clients to stop building new circuits. The
19863 fix is to always call circuit_n_chan_done(chan, 0) from
19864 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
19866 o Minor bugfixes (on 0.2.4.x):
19867 - Correctly log long IPv6 exit policies, instead of truncating them
19868 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
19869 - Our default TLS ecdhe groups were backwards: we meant to be using
19870 P224 for relays (for performance win) and P256 for bridges (since
19871 it is more common in the wild). Instead we had it backwards. After
19872 reconsideration, we decided that the default should be P256 on all
19873 hosts, since its security is probably better, and since P224 is
19874 reportedly used quite little in the wild. Found by "skruffy" on
19875 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
19876 - Free directory authority certificate download statuses on exit
19877 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
19879 o Minor bugfixes (on 0.2.3.x and earlier):
19880 - If the guard we choose first doesn't answer, we would try the
19881 second guard, but once we connected to the second guard we would
19882 abandon it and retry the first one, slowing down bootstrapping.
19883 The fix is to treat all our initially chosen guards as acceptable
19884 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
19885 - Fix an assertion failure that would occur when disabling the
19886 ORPort setting on a running Tor process while accounting was
19887 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
19888 - When examining the list of network interfaces to find our address,
19889 do not consider non-running or disabled network interfaces. Fixes
19890 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
19891 - Avoid an off-by-one error when checking buffer boundaries when
19892 formatting the exit status of a pluggable transport helper.
19893 This is probably not an exploitable bug, but better safe than
19894 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
19897 o Minor features (protecting client timestamps):
19898 - Clients no longer send timestamps in their NETINFO cells. These were
19899 not used for anything, and they provided one small way for clients
19900 to be distinguished from each other as they moved from network to
19901 network or behind NAT. Implements part of proposal 222.
19902 - Clients now round timestamps in INTRODUCE cells down to the nearest
19903 10 minutes. If a new Support022HiddenServices option is set to 0, or
19904 if it's set to "auto" and the feature is disabled in the consensus,
19905 the timestamp is sent as 0 instead. Implements part of proposal 222.
19906 - Stop sending timestamps in AUTHENTICATE cells. This is not such
19907 a big deal from a security point of view, but it achieves no actual
19908 good purpose, and isn't needed. Implements part of proposal 222.
19909 - Reduce down accuracy of timestamps in hidden service descriptors.
19910 Implements part of proposal 222.
19912 o Minor features (other):
19913 - Improve the circuit queue out-of-memory handler. Previously, when
19914 we ran low on memory, we'd close whichever circuits had the most
19915 queued cells. Now, we close those that have the *oldest* queued
19916 cells, on the theory that those are most responsible for us
19917 running low on memory. Based on analysis from a forthcoming paper
19918 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
19919 - Generate bootstrapping status update events correctly when fetching
19920 microdescriptors. Fixes bug 9927.
19921 - Update to the October 2 2013 Maxmind GeoLite Country database.
19923 o Documentation fixes:
19924 - Clarify the usage and risks of setting the ContactInfo torrc line
19925 for your relay or bridge. Resolves ticket 9854.
19926 - Add anchors to the manpage so we can link to the html version of
19927 the documentation for specific options. Resolves ticket 9866.
19928 - Replace remaining references to DirServer in man page and
19929 log entries. Resolves ticket 10124.
19932 Changes in version 0.2.5.1-alpha - 2013-10-02
19933 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
19934 on Linux, allows bridges that offer pluggable transports to report usage
19935 statistics, fixes many issues to make testing easier, and provides
19936 a pile of minor features and bugfixes that have been waiting for a
19937 release of the new branch.
19939 This is the first alpha release in a new series, so expect there to
19940 be bugs. Users who would rather test out a more stable branch should
19941 stay with 0.2.4.x for now.
19943 o Major features (security):
19944 - Use the seccomp2 syscall filtering facility on Linux to limit
19945 which system calls Tor can invoke. This is an experimental,
19946 Linux-only feature to provide defense-in-depth against unknown
19947 attacks. To try turning it on, set "Sandbox 1" in your torrc
19948 file. Please be ready to report bugs. We hope to add support
19949 for better sandboxing in the future, including more fine-grained
19950 filters, better division of responsibility, and support for more
19951 platforms. This work has been done by Cristian-Matei Toader for
19952 Google Summer of Code.
19953 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
19954 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
19955 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
19956 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
19957 them to solve bug 6033.)
19959 o Major features (other):
19960 - Add support for passing arguments to managed pluggable transport
19961 proxies. Implements ticket 3594.
19962 - Bridges now track GeoIP information and the number of their users
19963 even when pluggable transports are in use, and report usage
19964 statistics in their extra-info descriptors. Resolves tickets 4773
19966 - Make testing Tor networks bootstrap better: lower directory fetch
19967 retry schedules and maximum interval without directory requests,
19968 and raise maximum download tries. Implements ticket 6752.
19969 - Add make target 'test-network' to run tests on a Chutney network.
19970 Implements ticket 8530.
19971 - The ntor handshake is now on-by-default, no matter what the
19972 directory authorities recommend. Implements ticket 8561.
19975 - Instead of writing destroy cells directly to outgoing connection
19976 buffers, queue them and intersperse them with other outgoing cells.
19977 This can prevent a set of resource starvation conditions where too
19978 many pending destroy cells prevent data cells from actually getting
19979 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
19980 bugfix on 0.2.0.1-alpha.
19981 - If we are unable to save a microdescriptor to the journal, do not
19982 drop it from memory and then reattempt downloading it. Fixes bug
19983 9645; bugfix on 0.2.2.6-alpha.
19984 - The new channel code sometimes lost track of in-progress circuits,
19985 causing long-running clients to stop building new circuits. The
19986 fix is to always call circuit_n_chan_done(chan, 0) from
19987 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
19990 - Tor now builds each source file in two modes: a mode that avoids
19991 exposing identifiers needlessly, and another mode that exposes
19992 more identifiers for testing. This lets the compiler do better at
19993 optimizing the production code, while enabling us to take more
19994 radical measures to let the unit tests test things.
19995 - The production builds no longer include functions used only in
19996 the unit tests; all functions exposed from a module only for
19997 unit-testing are now static in production builds.
19998 - Add an --enable-coverage configuration option to make the unit
19999 tests (and a new src/or/tor-cov target) to build with gcov test
20003 - We now have rudimentary function mocking support that our unit
20004 tests can use to test functions in isolation. Function mocking
20005 lets the tests temporarily replace a function's dependencies with
20006 stub functions, so that the tests can check the function without
20007 invoking the other functions it calls.
20008 - Add more unit tests for the <circid,channel>->circuit map, and
20009 the destroy-cell-tracking code to fix bug 7912.
20010 - Unit tests for failing cases of the TAP onion handshake.
20011 - More unit tests for address-manipulation functions.
20013 o Minor features (protecting client timestamps):
20014 - Clients no longer send timestamps in their NETINFO cells. These were
20015 not used for anything, and they provided one small way for clients
20016 to be distinguished from each other as they moved from network to
20017 network or behind NAT. Implements part of proposal 222.
20018 - Clients now round timestamps in INTRODUCE cells down to the nearest
20019 10 minutes. If a new Support022HiddenServices option is set to 0, or
20020 if it's set to "auto" and the feature is disabled in the consensus,
20021 the timestamp is sent as 0 instead. Implements part of proposal 222.
20022 - Stop sending timestamps in AUTHENTICATE cells. This is not such
20023 a big deal from a security point of view, but it achieves no actual
20024 good purpose, and isn't needed. Implements part of proposal 222.
20025 - Reduce down accuracy of timestamps in hidden service descriptors.
20026 Implements part of proposal 222.
20028 o Minor features (config options):
20029 - Config (torrc) lines now handle fingerprints which are missing
20030 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
20031 - Support a --dump-config option to print some or all of the
20032 configured options. Mainly useful for debugging the command-line
20033 option parsing code. Helps resolve ticket 4647.
20034 - Raise awareness of safer logging: notify user of potentially
20035 unsafe config options, like logging more verbosely than severity
20036 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
20037 - Add a new configuration option TestingV3AuthVotingStartOffset
20038 that bootstraps a network faster by changing the timing for
20039 consensus votes. Addresses ticket 8532.
20040 - Add a new torrc option "ServerTransportOptions" that allows
20041 bridge operators to pass configuration parameters to their
20042 pluggable transports. Resolves ticket 8929.
20043 - The config (torrc) file now accepts bandwidth and space limits in
20044 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
20045 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
20048 o Minor features (build):
20049 - Add support for `--library-versions` flag. Implements ticket 6384.
20050 - Return the "unexpected sendme" warnings to a warn severity, but make
20051 them rate limited, to help diagnose ticket 8093.
20052 - Detect a missing asciidoc, and warn the user about it, during
20053 configure rather than at build time. Fixes issue 6506. Patch from
20056 o Minor features (other):
20057 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
20058 sockets in a single system call. Implements ticket 5129.
20059 - Log current accounting state (bytes sent and received + remaining
20060 time for the current accounting period) in the relay's heartbeat
20061 message. Implements ticket 5526; patch from Peter Retzlaff.
20062 - Implement the TRANSPORT_LAUNCHED control port event that
20063 notifies controllers about new launched pluggable
20064 transports. Resolves ticket 5609.
20065 - If we're using the pure-C 32-bit curve25519_donna implementation
20066 of curve25519, build it with the -fomit-frame-pointer option to
20067 make it go faster on register-starved hosts. This improves our
20068 handshake performance by about 6% on i386 hosts without nacl.
20069 Closes ticket 8109.
20070 - Update to the September 4 2013 Maxmind GeoLite Country database.
20073 - Set the listen() backlog limit to the largest actually supported
20074 on the system, not to the value in a header file. Fixes bug 9716;
20075 bugfix on every released Tor.
20076 - No longer accept malformed http headers when parsing urls from
20077 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
20078 bugfix on 0.0.6pre1.
20079 - In munge_extrainfo_into_routerinfo(), check the return value of
20080 memchr(). This would have been a serious issue if we ever passed
20081 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
20083 - On the chance that somebody manages to build Tor on a
20084 platform where time_t is unsigned, correct the way that
20085 microdesc_add_to_cache() handles negative time arguments.
20086 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
20087 - Reject relative control socket paths and emit a warning. Previously,
20088 single-component control socket paths would be rejected, but Tor
20089 would not log why it could not validate the config. Fixes bug 9258;
20090 bugfix on 0.2.3.16-alpha.
20092 o Minor bugfixes (command line):
20093 - Use a single command-line parser for parsing torrc options on the
20094 command line and for finding special command-line options to avoid
20095 inconsistent behavior for torrc option arguments that have the same
20096 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
20098 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
20099 9573; bugfix on 0.0.9pre5.
20101 o Minor fixes (build, auxiliary programs):
20102 - Stop preprocessing the "torify" script with autoconf, since
20103 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
20105 - The tor-fw-helper program now follows the standard convention and
20106 exits with status code "0" on success. Fixes bug 9030; bugfix on
20107 0.2.3.1-alpha. Patch by Arlo Breault.
20108 - Corrected ./configure advice for what openssl dev package you should
20109 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
20111 o Minor code improvements:
20112 - Remove constants and tests for PKCS1 padding; it's insecure and
20113 shouldn't be used for anything new. Fixes bug 8792; patch
20115 - Remove instances of strcpy() from the unit tests. They weren't
20116 hurting anything, since they were only in the unit tests, but it's
20117 embarrassing to have strcpy() in the code at all, and some analysis
20118 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
20119 0.2.3.8-alpha. Patch from Arlo Breault.
20121 o Removed features:
20122 - Remove migration code from when we renamed the "cached-routers"
20123 file to "cached-descriptors" back in 0.2.0.8-alpha. This
20124 incidentally resolves ticket 6502 by cleaning up the related code
20125 a bit. Patch from Akshay Hebbar.
20127 o Code simplification and refactoring:
20128 - Extract the common duplicated code for creating a subdirectory
20129 of the data directory and writing to a file in it. Fixes ticket
20130 4282; patch from Peter Retzlaff.
20131 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
20132 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
20133 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
20134 - Add a set of accessor functions for the circuit timeout data
20135 structure. Fixes ticket 6153; patch from "piet".
20136 - Clean up exit paths from connection_listener_new(). Closes ticket
20137 8789. Patch from Arlo Breault.
20138 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
20139 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
20140 - Use a doubly-linked list to implement the global circuit list.
20141 Resolves ticket 9108. Patch from Marek Majkowski.
20142 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
20145 Changes in version 0.2.4.17-rc - 2013-09-05
20146 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
20147 series. It adds an emergency step to help us tolerate the massive
20148 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
20149 circuit-level handshakes now effectively jump the queue compared to
20150 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
20151 big bug hindering bridge reachability tests.
20154 - Relays now process the new "NTor" circuit-level handshake requests
20155 with higher priority than the old "TAP" circuit-level handshake
20156 requests. We still process some TAP requests to not totally starve
20157 0.2.3 clients when NTor becomes popular. A new consensus parameter
20158 "NumNTorsPerTAP" lets us tune the balance later if we need to.
20159 Implements ticket 9574.
20162 - If the circuit build timeout logic is disabled (via the consensus,
20163 or because we are an authority), then don't build testing circuits.
20164 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
20165 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
20166 previously they did not, which prevented them from receiving
20167 successful connections from relays for self-test or bandwidth
20168 testing. Also, when a relay is extending a circuit to a bridge,
20169 it needs to send a NETINFO cell, even when the bridge hasn't sent
20170 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
20171 - If the time to download the next old-style networkstatus is in
20172 the future, do not decline to consider whether to download the
20173 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
20177 - Avoid double-closing the listener socket in our socketpair()
20178 replacement (used on Windows) in the case where the addresses on
20179 our opened sockets don't match what we expected. Fixes bug 9400;
20180 bugfix on 0.0.2pre7. Found by Coverity.
20182 o Minor fixes (config options):
20183 - Avoid overflows when the user sets MaxCircuitDirtiness to a
20184 ridiculously high value, by imposing a (ridiculously high) 30-day
20185 maximum on MaxCircuitDirtiness.
20186 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
20187 message is logged at notice, not at info.
20188 - Warn and fail if a server is configured not to advertise any
20189 ORPorts at all. (We need *something* to put in our descriptor,
20190 or we just won't work.)
20193 - Track how many "TAP" and "NTor" circuit handshake requests we get,
20194 and how many we complete, and log it every hour to help relay
20195 operators follow trends in network load. Addresses ticket 9658.
20196 - Update to the August 7 2013 Maxmind GeoLite Country database.
20199 Changes in version 0.2.4.16-rc - 2013-08-10
20200 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
20201 series. It fixes several crash bugs in the 0.2.4 branch.
20204 - Fix a bug in the voting algorithm that could yield incorrect results
20205 when a non-naming authority declared too many flags. Fixes bug 9200;
20206 bugfix on 0.2.0.3-alpha.
20207 - Fix an uninitialized read that could in some cases lead to a remote
20208 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
20209 Anybody running a hidden service on the experimental 0.2.4.x
20210 branch should upgrade. (This is, so far as we know, unrelated to
20212 - Avoid an assertion failure when processing DNS replies without the
20213 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
20214 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
20215 0.2.4.15-rc. Found by stem integration tests.
20218 - Fix an invalid memory read that occurred when a pluggable
20219 transport proxy failed its configuration protocol.
20220 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
20221 - When evaluating whether to use a connection that we haven't
20222 decided is canonical using a recent link protocol version,
20223 decide that it's canonical only if it used address _does_
20224 match the desired address. Fixes bug 9309; bugfix on
20225 0.2.4.4-alpha. Reported by skruffy.
20226 - Make the default behavior of NumDirectoryGuards be to track
20227 NumEntryGuards. Now a user who changes only NumEntryGuards will get
20228 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
20229 - Fix a spurious compilation warning with some older versions of
20230 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
20233 - Update to the July 3 2013 Maxmind GeoLite Country database.
20236 Changes in version 0.2.4.15-rc - 2013-07-01
20237 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
20238 series. It fixes a few smaller bugs, but generally appears stable.
20239 Please test it and let us know whether it is!
20242 - When receiving a new configuration file via the control port's
20243 LOADCONF command, do not treat the defaults file as absent.
20244 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
20247 - Issue a warning when running with the bufferevents backend enabled.
20248 It's still not stable, and people should know that they're likely
20249 to hit unexpected problems. Closes ticket 9147.
20252 Changes in version 0.2.4.14-alpha - 2013-06-18
20253 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
20254 present in 0.2.4.13-alpha.
20257 - When we have too much memory queued in circuits (according to a new
20258 MaxMemInCellQueues option), close the circuits consuming the most
20259 memory. This prevents us from running out of memory as a relay if
20260 circuits fill up faster than they can be drained. Fixes bug 9063;
20261 bugfix on the 54th commit of Tor. This bug is a further fix beyond
20262 bug 6252, whose fix was merged into 0.2.3.21-rc.
20264 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
20265 where we tried to solve this issue simply by imposing an upper limit
20266 on the number of queued cells for a single circuit. That approach
20267 proved to be problematic, since there are ways to provoke clients to
20268 send a number of cells in excess of any such reasonable limit. Fixes
20269 bug 9072; bugfix on 0.2.4.13-alpha.
20271 - Limit hidden service descriptors to at most ten introduction
20272 points, to slow one kind of guard enumeration. Fixes bug 9002;
20273 bugfix on 0.1.1.11-alpha.
20276 Changes in version 0.2.4.13-alpha - 2013-06-14
20277 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
20278 vulnerabilities, makes socks5 username/password circuit isolation
20279 actually actually work (this time for sure!), and cleans up a bunch
20280 of other issues in preparation for a release candidate.
20282 o Major bugfixes (robustness):
20283 - Close any circuit that has too many cells queued on it. Fixes
20284 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
20285 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
20286 - Prevent the get_freelists() function from running off the end of
20287 the list of freelists if it somehow gets an unrecognized
20288 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
20290 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
20291 when an exit connection with optimistic data succeeds immediately
20292 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
20294 - Fix a directory authority crash bug when building a consensus
20295 using an older consensus as its basis. Fixes bug 8833. Bugfix
20299 - Avoid a memory leak where we would leak a consensus body when we
20300 find that a consensus which we couldn't previously verify due to
20301 missing certificates is now verifiable. Fixes bug 8719; bugfix
20303 - We used to always request authority certificates by identity digest,
20304 meaning we'd get the newest one even when we wanted one with a
20305 different signing key. Then we would complain about being given
20306 a certificate we already had, and never get the one we really
20307 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
20308 resource to request the one we want. Fixes bug 5595; bugfix on
20310 - Follow the socks5 protocol when offering username/password
20311 authentication. The fix for bug 8117 exposed this bug, and it
20312 turns out real-world applications like Pidgin do care. Bugfix on
20313 0.2.3.2-alpha; fixes bug 8879.
20314 - Prevent failures on Windows Vista and later when rebuilding the
20315 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
20316 bugfix on 0.2.4.12-alpha.
20319 - Fix an impossible buffer overrun in the AES unit tests. Fixes
20320 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
20321 - If for some reason we fail to write a microdescriptor while
20322 rebuilding the cache, do not let the annotations from that
20323 microdescriptor linger in the cache file, and do not let the
20324 microdescriptor stay recorded as present in its old location.
20325 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
20326 - Fix a memory leak that would occur whenever a configuration
20327 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
20328 - Paste the description for PathBias parameters from the man
20329 page into or.h, so the code documents them too. Fixes bug 7982;
20330 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
20331 - Relays now treat a changed IPv6 ORPort as sufficient reason to
20332 publish an updated descriptor. Fixes bug 6026; bugfix on
20334 - When launching a resolve request on behalf of an AF_UNIX control
20335 socket, omit the address field of the new entry connection, used in
20336 subsequent controller events, rather than letting tor_dup_addr()
20337 set it to "<unknown address type>". Fixes bug 8639; bugfix on
20340 o Minor bugfixes (log messages):
20341 - Fix a scaling issue in the path bias accounting code that
20342 resulted in "Bug:" log messages from either
20343 pathbias_scale_close_rates() or pathbias_count_build_success().
20344 This represents a bugfix on a previous bugfix: the original fix
20345 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
20347 - Give a less useless error message when the user asks for an IPv4
20348 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
20352 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
20353 to tolerate bug 8093 for now.
20354 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
20355 in directory authority votes to describe whether they have enough
20356 measured bandwidths to ignore advertised (relay descriptor)
20357 bandwidth claims. Resolves ticket 8711.
20358 - Update to the June 5 2013 Maxmind GeoLite Country database.
20360 o Removed documentation:
20361 - Remove some of the older contents of doc/ as obsolete; move others
20362 to torspec.git. Fixes bug 8965.
20364 o Code simplification and refactoring:
20365 - Avoid using character buffers when constructing most directory
20366 objects: this approach was unwieldy and error-prone. Instead,
20367 build smartlists of strings, and concatenate them when done.
20370 Changes in version 0.2.4.12-alpha - 2013-04-18
20371 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
20372 process for lengthening the guard rotation period, makes directory
20373 authority opinions in the consensus a bit less gameable, makes socks5
20374 username/password circuit isolation actually work, and fixes a wide
20375 variety of other issues.
20378 - Raise the default time that a client keeps an entry guard from
20379 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
20380 2012 paper. (We would make it even longer, but we need better client
20381 load balancing first.) Also, make the guard lifetime controllable
20382 via a new GuardLifetime torrc option and a GuardLifetime consensus
20383 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
20384 - Directory authorities now prefer using measured bandwidths to
20385 advertised ones when computing flags and thresholds. Resolves
20387 - Directory authorities that have more than a threshold number
20388 of relays with measured bandwidths now treat relays with unmeasured
20389 bandwidths as having bandwidth 0. Resolves ticket 8435.
20391 o Major bugfixes (assert / resource use):
20392 - Avoid a bug where our response to TLS renegotiation under certain
20393 network conditions could lead to a busy-loop, with 100% CPU
20394 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
20395 - Avoid an assertion when we discover that we'd like to write a cell
20396 onto a closing connection: just discard the cell. Fixes another
20397 case of bug 7350; bugfix on 0.2.4.4-alpha.
20399 o Major bugfixes (client-side privacy):
20400 - When we mark a circuit as unusable for new circuits, have it
20401 continue to be unusable for new circuits even if MaxCircuitDirtiness
20402 is increased too much at the wrong time, or the system clock jumps
20403 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
20404 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
20405 which have resolved to internal addresses") is set, apply that
20406 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
20407 - When an exit relay rejects a stream with reason "exit policy", but
20408 we only know an exit policy summary (e.g. from the microdesc
20409 consensus) for it, do not mark the relay as useless for all exiting.
20410 Instead, mark just the circuit as unsuitable for that particular
20411 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
20412 - Allow applications to get proper stream isolation with
20413 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
20414 username/password authentication also offer "no authentication". Tor
20415 had previously preferred "no authentication", so the applications
20416 never actually sent Tor their auth details. Now Tor selects
20417 username/password authentication if it's offered. You can disable
20418 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
20419 bug 8117; bugfix on 0.2.3.3-alpha.
20421 o Major bugfixes (other):
20422 - When unable to find any working directory nodes to use as a
20423 directory guard, give up rather than adding the same non-working
20424 nodes to the directory guard list over and over. Fixes bug 8231;
20425 bugfix on 0.2.4.8-alpha.
20428 - Reject as invalid most directory objects containing a NUL.
20429 Belt-and-suspender fix for bug 8037.
20430 - In our testsuite, create temporary directories with a bit more
20431 entropy in their name to make name collisions less likely. Fixes
20433 - Add CACHED keyword to ADDRMAP events in the control protocol
20434 to indicate whether a DNS result will be cached or not. Resolves
20436 - Update to the April 3 2013 Maxmind GeoLite Country database.
20438 o Minor features (build):
20439 - Detect and reject attempts to build Tor with threading support
20440 when OpenSSL has been compiled without threading support.
20442 - Clarify that when autoconf is checking for nacl, it is checking
20443 specifically for nacl with a fast curve25519 implementation.
20445 - Warn if building on a platform with an unsigned time_t: there
20446 are too many places where Tor currently assumes that time_t can
20447 hold negative values. We'd like to fix them all, but probably
20450 o Minor bugfixes (build):
20451 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
20452 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
20453 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
20454 - Add the old src/or/micro-revision.i filename to CLEANFILES.
20455 On the off chance that somebody has one, it will go away as soon
20456 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
20457 - Build Tor correctly on 32-bit platforms where the compiler can build
20458 but not run code using the "uint128_t" construction. Fixes bug 8587;
20459 bugfix on 0.2.4.8-alpha.
20460 - Fix compilation warning with some versions of clang that would
20461 prefer the -Wswitch-enum compiler flag to warn about switch
20462 statements with missing enum values, even if those switch
20463 statements have a "default:" statement. Fixes bug 8598; bugfix
20466 o Minor bugfixes (protocol):
20467 - Fix the handling of a TRUNCATE cell when it arrives while the
20468 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
20469 - Fix a misframing issue when reading the version numbers in a
20470 VERSIONS cell. Previously we would recognize [00 01 00 02] as
20471 'version 1, version 2, and version 0x100', when it should have
20472 only included versions 1 and 2. Fixes bug 8059; bugfix on
20473 0.2.0.10-alpha. Reported pseudonymously.
20474 - Make the format and order of STREAM events for DNS lookups
20475 consistent among the various ways to launch DNS lookups. Fixes
20476 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
20477 - Correct our check for which versions of Tor support the EXTEND2
20478 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
20479 later, when support was really added in version 0.2.4.8-alpha.
20480 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
20482 o Minor bugfixes (other):
20483 - Correctly store microdescriptors and extrainfo descriptors with
20484 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
20485 Bug reported by "cypherpunks".
20486 - Increase the width of the field used to remember a connection's
20487 link protocol version to two bytes. Harmless for now, since the
20488 only currently recognized versions are one byte long. Reported
20489 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
20490 - If the state file's path bias counts are invalid (presumably from a
20491 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
20492 additional checks and log messages to the scaling of Path Bias
20493 counts, in case there still are remaining issues with scaling.
20494 Should help resolve bug 8235.
20495 - Eliminate several instances where we use "Nickname=ID" to refer to
20496 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
20497 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
20498 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
20500 o Minor bugfixes (syscalls):
20501 - Always check the return values of functions fcntl() and
20502 setsockopt(). We don't believe these are ever actually failing in
20503 practice, but better safe than sorry. Also, checking these return
20504 values should please analysis tools like Coverity. Patch from
20505 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
20506 - Use direct writes rather than stdio when building microdescriptor
20507 caches, in an attempt to mitigate bug 8031, or at least make it
20510 o Minor bugfixes (config):
20511 - When rejecting a configuration because we were unable to parse a
20512 quoted string, log an actual error message. Fixes bug 7950; bugfix
20514 - Behave correctly when the user disables LearnCircuitBuildTimeout
20515 but doesn't tell us what they would like the timeout to be. Fixes
20516 bug 6304; bugfix on 0.2.2.14-alpha.
20517 - When autodetecting the number of CPUs, use the number of available
20518 CPUs in preference to the number of configured CPUs. Inform the
20519 user if this reduces the number of available CPUs. Fixes bug 8002;
20520 bugfix on 0.2.3.1-alpha.
20521 - Make it an error when you set EntryNodes but disable UseGuardNodes,
20522 since it will (surprisingly to some users) ignore EntryNodes. Fixes
20523 bug 8180; bugfix on 0.2.3.11-alpha.
20524 - Allow TestingTorNetworks to override the 4096-byte minimum for
20525 the Fast threshold. Otherwise they can't bootstrap until they've
20526 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
20527 - Fix some logic errors when the user manually overrides the
20528 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
20531 o Minor bugfixes (log messages to help diagnose bugs):
20532 - If we fail to free a microdescriptor because of bug 7164, log
20533 the filename and line number from which we tried to free it.
20534 - Add another diagnostic to the heartbeat message: track and log
20535 overhead that TLS is adding to the data we write. If this is
20536 high, we are sending too little data to SSL_write at a time.
20537 Diagnostic for bug 7707.
20538 - Add more detail to a log message about relaxed timeouts, to help
20540 - Warn more aggressively when flushing microdescriptors to a
20541 microdescriptor cache fails, in an attempt to mitigate bug 8031,
20542 or at least make it more diagnosable.
20543 - Improve debugging output to help track down bug 8185 ("Bug:
20544 outgoing relay cell has n_chan==NULL. Dropping.")
20545 - Log the purpose of a path-bias testing circuit correctly.
20546 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
20548 o Minor bugfixes (0.2.4.x log messages that were too noisy):
20549 - Don't attempt to relax the timeout of already opened 1-hop circuits.
20550 They might never timeout. This should eliminate some/all cases of
20551 the relaxed timeout log message.
20552 - Use circuit creation time for network liveness evaluation. This
20553 should eliminate warning log messages about liveness caused
20554 by changes in timeout evaluation. Fixes bug 6572; bugfix on
20556 - Reduce a path bias length check from notice to info. The message
20557 is triggered when creating controller circuits. Fixes bug 8196;
20558 bugfix on 0.2.4.8-alpha.
20559 - Fix a path state issue that triggered a notice during relay startup.
20560 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
20561 - Reduce occurrences of warns about circuit purpose in
20562 connection_ap_expire_building(). Fixes bug 8477; bugfix on
20565 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
20566 - If we encounter a write failure on a SOCKS connection before we
20567 finish our SOCKS handshake, don't warn that we closed the
20568 connection before we could send a SOCKS reply. Fixes bug 8427;
20569 bugfix on 0.1.0.1-rc.
20570 - Correctly recognize that [::1] is a loopback address. Fixes
20571 bug 8377; bugfix on 0.2.1.3-alpha.
20572 - Fix a directory authority warn caused when we have a large amount
20573 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
20574 - Don't log inappropriate heartbeat messages when hibernating: a
20575 hibernating node is _expected_ to drop out of the consensus,
20576 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
20577 bugfix on 0.2.3.1-alpha.
20578 - Don't complain about bootstrapping problems while hibernating.
20579 These complaints reflect a general code problem, but not one
20580 with any problematic effects (no connections are actually
20581 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
20583 o Documentation fixes:
20584 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
20585 names match. Fixes bug 7768.
20586 - Make the torify manpage no longer refer to tsocks; torify hasn't
20587 supported tsocks since 0.2.3.14-alpha.
20588 - Make the tor manpage no longer reference tsocks.
20589 - Fix the GeoIPExcludeUnknown documentation to refer to
20590 ExcludeExitNodes rather than the currently nonexistent
20591 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
20594 - The tor-tsocks.conf is no longer distributed or installed. We
20595 recommend that tsocks users use torsocks instead. Resolves
20599 Changes in version 0.2.4.11-alpha - 2013-03-11
20600 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
20601 more robust, makes hidden service authentication work again, and
20602 resolves a DPI fingerprint for Tor's SSL transport.
20604 o Major features (directory authorities):
20605 - Directory authorities now support a new consensus method (17)
20606 where they cap the published bandwidth of servers for which
20607 insufficient bandwidth measurements exist. Fixes part of bug 2286.
20608 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
20609 serve any v2 directory information. Now we can test disabling the
20610 old deprecated v2 directory format, and see whether doing so has
20611 any effect on network load. Begins to fix bug 6783.
20612 - Directory authorities now include inside each vote a statement of
20613 the performance thresholds they used when assigning flags.
20614 Implements ticket 8151.
20616 o Major bugfixes (directory authorities):
20617 - Stop marking every relay as having been down for one hour every
20618 time we restart a directory authority. These artificial downtimes
20619 were messing with our Stable and Guard flag calculations. Fixes
20620 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
20622 o Major bugfixes (hidden services):
20623 - Allow hidden service authentication to succeed again. When we
20624 refactored the hidden service introduction code back
20625 in 0.2.4.1-alpha, we didn't update the code that checks
20626 whether authentication information is present, causing all
20627 authentication checks to return "false". Fix for bug 8207; bugfix
20628 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
20630 o Minor features (relays, bridges):
20631 - Make bridge relays check once a minute for whether their IP
20632 address has changed, rather than only every 15 minutes. Resolves
20633 bugs 1913 and 1992.
20634 - Refactor resolve_my_address() so it returns the method by which we
20635 decided our public IP address (explicitly configured, resolved from
20636 explicit hostname, guessed from interfaces, learned by gethostname).
20637 Now we can provide more helpful log messages when a relay guesses
20638 its IP address incorrectly (e.g. due to unexpected lines in
20639 /etc/hosts). Resolves ticket 2267.
20640 - Teach bridge-using clients to avoid 0.2.2 bridges when making
20641 microdescriptor-related dir requests, and only fall back to normal
20642 descriptors if none of their bridges can handle microdescriptors
20643 (as opposed to the fix in ticket 4013, which caused them to fall
20644 back to normal descriptors if *any* of their bridges preferred
20645 them). Resolves ticket 4994.
20646 - Randomize the lifetime of our SSL link certificate, so censors can't
20647 use the static value for filtering Tor flows. Resolves ticket 8443;
20648 related to ticket 4014 which was included in 0.2.2.33.
20649 - Support a new version of the link protocol that allows 4-byte circuit
20650 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
20651 a possible resource exhaustion issue. Closes ticket 7351; implements
20654 o Minor features (portability):
20655 - Tweak the curve25519-donna*.c implementations to tolerate systems
20656 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
20657 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
20658 the signs of types during autoconf. This is better than our old
20659 approach, which didn't work when cross-compiling.
20660 - Detect the sign of enum values, rather than assuming that MSC is the
20661 only compiler where enum types are all signed. Fixes bug 7727;
20662 bugfix on 0.2.4.10-alpha.
20664 o Minor features (other):
20665 - Say "KBytes" rather than "KB" in the man page (for various values
20666 of K), to further reduce confusion about whether Tor counts in
20667 units of memory or fractions of units of memory. Resolves ticket 7054.
20668 - Clear the high bit on curve25519 public keys before passing them to
20669 our backend, in case we ever wind up using a backend that doesn't do
20670 so itself. If we used such a backend, and *didn't* clear the high bit,
20671 we could wind up in a situation where users with such backends would
20672 be distinguishable from users without. Fixes bug 8121; bugfix on
20674 - Update to the March 6 2013 Maxmind GeoLite Country database.
20676 o Minor bugfixes (clients):
20677 - When we receive a RELAY_END cell with the reason DONE, or with no
20678 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
20679 status as "connection refused". Previously we reported these cases
20680 as success but then immediately closed the connection. Fixes bug
20681 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
20682 - Downgrade an assertion in connection_ap_expire_beginning to an
20683 LD_BUG message. The fix for bug 8024 should prevent this message
20684 from displaying, but just in case, a warn that we can diagnose
20685 is better than more assert crashes. Fixes bug 8065; bugfix on
20687 - Lower path use bias thresholds to .80 for notice and .60 for warn.
20688 Also make the rate limiting flags for the path use bias log messages
20689 independent from the original path bias flags. Fixes bug 8161;
20690 bugfix on 0.2.4.10-alpha.
20692 o Minor bugfixes (relays):
20693 - Stop trying to resolve our hostname so often (e.g. every time we
20694 think about doing a directory fetch). Now we reuse the cached
20695 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
20696 and 2410 (bugfix on 0.1.2.2-alpha).
20697 - Stop sending a stray "(null)" in some cases for the server status
20698 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
20700 - When choosing which stream on a formerly stalled circuit to wake
20701 first, make better use of the platform's weak RNG. Previously,
20702 we had been using the % ("modulo") operator to try to generate a
20703 1/N chance of picking each stream, but this behaves badly with
20704 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
20706 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
20707 Irix's random() only return 15 bits; Solaris's random() returns more
20708 bits but its RAND_MAX says it only returns 15, and so on. Motivated
20709 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
20711 o Minor bugfixes (directory authorities):
20712 - Directory authorities now use less space when formatting identical
20713 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
20716 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
20717 - Avoid leaking memory if we fail to compute a consensus signature
20718 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
20719 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
20721 - Fix a memory leak during safe-cookie controller authentication.
20722 Bugfix on 0.2.3.13-alpha.
20723 - Avoid memory leak of IPv6 policy content if we fail to format it into
20724 a router descriptor. Bugfix on 0.2.4.7-alpha.
20726 o Minor bugfixes (other code correctness issues):
20727 - Avoid a crash if we fail to generate an extrainfo descriptor.
20728 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
20729 this is CID 718634.
20730 - When detecting the largest possible file descriptor (in order to
20731 close all file descriptors when launching a new program), actually
20732 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
20733 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
20735 - Fix a copy-and-paste error when adding a missing A1 to a routerset
20736 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
20737 Bugfix on 0.2.4.10-alpha.
20738 - Fix an impossible-to-trigger integer overflow when estimating how
20739 long our onionskin queue would take. (This overflow would require us
20740 to accept 4 million onionskins before processing 100 of them.) Fixes
20741 bug 8210; bugfix on 0.2.4.10-alpha.
20743 o Code simplification and refactoring:
20744 - Add a wrapper function for the common "log a message with a
20748 Changes in version 0.2.4.10-alpha - 2013-02-04
20749 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
20750 certain attacks that flood the network with relays; changes the queue
20751 for circuit create requests from a sized-based limit to a time-based
20752 limit; resumes building with MSVC on Windows; and fixes a wide variety
20755 o Major bugfixes (directory authority):
20756 - When computing directory thresholds, ignore any rejected-as-sybil
20757 nodes during the computation so that they can't influence Fast,
20758 Guard, etc. (We should have done this for proposal 109.) Fixes
20760 - When marking a node as a likely sybil, reset its uptime metrics
20761 to zero, so that it cannot time towards getting marked as Guard,
20762 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
20766 - When a TLS write is partially successful but incomplete, remember
20767 that the flushed part has been flushed, and notice that bytes were
20768 actually written. Reported and fixed pseudonymously. Fixes bug
20769 7708; bugfix on Tor 0.1.0.5-rc.
20770 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
20771 ID: these could be used to create unexpected streams and circuits
20772 which would count as "present" to some parts of Tor but "absent"
20773 to others, leading to zombie circuits and streams or to a bandwidth
20774 denial-of-service. Fixes bug 7889; bugfix on every released version
20775 of Tor. Reported by "oftc_must_be_destroyed".
20776 - Rename all macros in our local copy of queue.h to begin with "TOR_".
20777 This change seems the only good way to permanently prevent conflicts
20778 with queue.h on various operating systems. Fixes bug 8107; bugfix
20781 o Major features (relay):
20782 - Instead of limiting the number of queued onionskins (aka circuit
20783 create requests) to a fixed, hard-to-configure number, we limit
20784 the size of the queue based on how many we expect to be able to
20785 process in a given amount of time. We estimate the time it will
20786 take to process an onionskin based on average processing time
20787 of previous onionskins. Closes ticket 7291. You'll never have to
20788 configure MaxOnionsPending again.
20790 o Major features (portability):
20791 - Resume building correctly with MSVC and Makefile.nmake. This patch
20792 resolves numerous bugs and fixes reported by ultramage, including
20793 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
20794 - Make the ntor and curve25519 code build correctly with MSVC.
20795 Fix on 0.2.4.8-alpha.
20798 - When directory authorities are computing thresholds for flags,
20799 never let the threshold for the Fast flag fall below 4096
20800 bytes. Also, do not consider nodes with extremely low bandwidths
20801 when deciding thresholds for various directory flags. This change
20802 should raise our threshold for Fast relays, possibly in turn
20803 improving overall network performance; see ticket 1854. Resolves
20805 - The Tor client now ignores sub-domain components of a .onion
20806 address. This change makes HTTP "virtual" hosting
20807 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
20808 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
20809 hosted on the same hidden service. Implements proposal 204.
20810 - We compute the overhead from passing onionskins back and forth to
20811 cpuworkers, and report it when dumping statistics in response to
20812 SIGUSR1. Supports ticket 7291.
20814 o Minor features (path selection):
20815 - When deciding whether we have enough descriptors to build circuits,
20816 instead of looking at raw relay counts, look at which fraction
20817 of (bandwidth-weighted) paths we're able to build. This approach
20818 keeps clients from building circuits if their paths are likely to
20819 stand out statistically. The default fraction of paths needed is
20820 taken from the consensus directory; you can override it with the
20821 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
20822 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
20823 and we have GeoIP information, also exclude all nodes with unknown
20824 countries "??" and "A1". This behavior is controlled by the
20825 new GeoIPExcludeUnknown option: you can make such nodes always
20826 excluded with "GeoIPExcludeUnknown 1", and disable the feature
20827 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
20828 gets you the default behavior. Implements feature 7706.
20829 - Path Use Bias: Perform separate accounting for successful circuit
20830 use. Keep separate statistics on stream attempt rates versus stream
20831 success rates for each guard. Provide configurable thresholds to
20832 determine when to emit log messages or disable use of guards that
20833 fail too many stream attempts. Resolves ticket 7802.
20835 o Minor features (log messages):
20836 - When learning a fingerprint for a bridge, log its corresponding
20837 transport type. Implements ticket 7896.
20838 - Improve the log message when "Bug/attack: unexpected sendme cell
20839 from client" occurs, to help us track bug 8093.
20842 - Remove a couple of extraneous semicolons that were upsetting the
20843 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
20844 bugfix on 0.2.2.1-alpha.
20845 - Remove a source of rounding error during path bias count scaling;
20846 don't count cannibalized circuits as used for path bias until we
20847 actually try to use them; and fix a circuit_package_relay_cell()
20848 warning message about n_chan==NULL. Fixes bug 7802.
20849 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
20850 actually link against nacl when we're configured to use it. Fixes
20851 bug 7972; bugfix on 0.2.4.8-alpha.
20852 - Compile correctly with the --disable-curve25519 option. Fixes
20853 bug 8153; bugfix on 0.2.4.8-alpha.
20855 o Build improvements:
20856 - Do not report status verbosely from autogen.sh unless the -v flag
20857 is specified. Fixes issue 4664. Patch from Onizuka.
20858 - Replace all calls to snprintf() outside of src/ext with
20859 tor_snprintf(). Also remove the #define to replace snprintf with
20860 _snprintf on Windows; they have different semantics, and all of
20861 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
20862 - Try to detect if we are ever building on a platform where
20863 memset(...,0,...) does not set the value of a double to 0.0. Such
20864 platforms are permitted by the C standard, though in practice
20865 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
20866 currently support them, but it's better to detect them and fail
20867 than to perform erroneously.
20869 o Removed features:
20870 - Stop exporting estimates of v2 and v3 directory traffic shares
20871 in extrainfo documents. They were unneeded and sometimes inaccurate.
20872 Also stop exporting any v2 directory request statistics. Resolves
20874 - Drop support for detecting and warning about versions of Libevent
20875 before 1.3e. Nothing reasonable ships with them any longer;
20876 warning the user about them shouldn't be needed. Resolves ticket
20879 o Code simplifications and refactoring:
20880 - Rename "isin" functions to "contains", for grammar. Resolves
20882 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
20883 with the natural logarithm function from the system libm. Resolves
20887 Changes in version 0.2.4.9-alpha - 2013-01-15
20888 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
20889 work more robustly.
20892 - Fix backward compatibility logic when receiving an embedded ntor
20893 handshake tunneled in a CREATE cell. This clears up the "Bug:
20894 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
20898 Changes in version 0.2.4.8-alpha - 2013-01-14
20899 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
20900 risks, adds a new stronger and faster circuit handshake, and offers
20901 stronger and faster link encryption when both sides support it.
20904 - Preliminary support for directory guards (proposal 207): when
20905 possible, clients now use their entry guards for non-anonymous
20906 directory requests. This can help prevent client enumeration. Note
20907 that this behavior only works when we have a usable consensus
20908 directory, and when options about what to download are more or less
20909 standard. In the future we should re-bootstrap from our guards,
20910 rather than re-bootstrapping from the preconfigured list of
20911 directory sources that ships with Tor. Resolves ticket 6526.
20912 - Tor relays and clients now support a better CREATE/EXTEND cell
20913 format, allowing the sender to specify multiple address, identity,
20914 and handshake types. Implements Robert Ransom's proposal 200;
20915 closes ticket 7199.
20917 o Major features (new circuit handshake):
20918 - Tor now supports a new circuit extension handshake designed by Ian
20919 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
20920 circuit extension handshake, later called "TAP", was a bit slow
20921 (especially on the relay side), had a fragile security proof, and
20922 used weaker keys than we'd now prefer. The new circuit handshake
20923 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
20924 function, making it significantly more secure than the older
20925 handshake, and significantly faster. Tor can use one of two built-in
20926 pure-C curve25519-donna implementations by Adam Langley, or it
20927 can link against the "nacl" library for a tuned version if present.
20929 The built-in version is very fast for 64-bit systems when building
20930 with GCC. The built-in 32-bit version is still faster than the
20931 old TAP protocol, but using libnacl is better on most such hosts.
20933 Clients don't currently use this protocol by default, since
20934 comparatively few clients support it so far. To try it, set
20935 UseNTorHandshake to 1.
20937 Implements proposal 216; closes ticket 7202.
20939 o Major features (better link encryption):
20940 - Relays can now enable the ECDHE TLS ciphersuites when available
20941 and appropriate. These ciphersuites let us negotiate forward-secure
20942 TLS secret keys more safely and more efficiently than with our
20943 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
20944 public relays prefer the (faster) P224 group, and bridges prefer
20945 the (more common) P256 group; you can override this with the
20948 Enabling these ciphers was a little tricky, since for a long time,
20949 clients had been claiming to support them without actually doing
20950 so, in order to foil fingerprinting. But with the client-side
20951 implementation of proposal 198 in 0.2.3.17-beta, clients can now
20952 match the ciphers from recent Firefox versions *and* list the
20953 ciphers they actually mean, so relays can believe such clients
20954 when they advertise ECDHE support in their TLS ClientHello messages.
20956 This feature requires clients running 0.2.3.17-beta or later,
20957 and requires both sides to be running OpenSSL 1.0.0 or later
20958 with ECC support. OpenSSL 1.0.1, with the compile-time option
20959 "enable-ec_nistp_64_gcc_128", is highly recommended.
20961 Implements the relay side of proposal 198; closes ticket 7200.
20964 - Avoid crashing when, as a relay without IPv6-exit support, a
20965 client insists on getting an IPv6 address or nothing. Fixes bug
20966 7814; bugfix on 0.2.4.7-alpha.
20969 - Improve circuit build timeout handling for hidden services.
20970 In particular: adjust build timeouts more accurately depending
20971 upon the number of hop-RTTs that a particular circuit type
20972 undergoes. Additionally, launch intro circuits in parallel
20973 if they timeout, and take the first one to reply as valid.
20974 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
20975 separate error codes; or at least, don't break for that reason.
20976 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
20977 - Update to the January 2 2013 Maxmind GeoLite Country database.
20979 o Minor features (testing):
20980 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
20981 (P-256) Diffie-Hellman handshakes to src/or/bench.
20982 - Add benchmark functions to test onion handshake performance.
20984 o Minor features (path bias detection):
20985 - Alter the Path Bias log messages to be more descriptive in terms
20986 of reporting timeouts and other statistics.
20987 - Create three levels of Path Bias log messages, as opposed to just
20988 two. These are configurable via consensus as well as via the torrc
20989 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
20990 The default values are 0.70, 0.50, and 0.30 respectively.
20991 - Separate the log message levels from the decision to drop guards,
20992 which also is available via torrc option PathBiasDropGuards.
20993 PathBiasDropGuards still defaults to 0 (off).
20994 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
20995 in combination with PathBiasExtremeRate.
20996 - Increase the default values for PathBiasScaleThreshold and
20997 PathBiasCircThreshold from (200, 20) to (300, 150).
20998 - Add in circuit usage accounting to path bias. If we try to use a
20999 built circuit but fail for any reason, it counts as path bias.
21000 Certain classes of circuits where the adversary gets to pick your
21001 destination node are exempt from this accounting. Usage accounting
21002 can be specifically disabled via consensus parameter or torrc.
21003 - Convert all internal path bias state to double-precision floating
21004 point, to avoid roundoff error and other issues.
21005 - Only record path bias information for circuits that have completed
21006 *two* hops. Assuming end-to-end tagging is the attack vector, this
21007 makes us more resilient to ambient circuit failure without any
21008 detection capability loss.
21010 o Minor bugfixes (log messages):
21011 - Rate-limit the "No circuits are opened. Relaxed timeout for a
21012 circuit with channel state open..." message to once per hour to
21013 keep it from filling the notice logs. Mitigates bug 7799 but does
21014 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
21015 - Avoid spurious warnings when configuring multiple client ports of
21016 which only some are nonlocal. Previously, we had claimed that some
21017 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
21020 o Code simplifications and refactoring:
21021 - Get rid of a couple of harmless clang warnings, where we compared
21022 enums to ints. These warnings are newly introduced in clang 3.2.
21023 - Split the onion.c file into separate modules for the onion queue
21024 and the different handshakes it supports.
21025 - Remove the marshalling/unmarshalling code for sending requests to
21026 cpuworkers over a socket, and instead just send structs. The
21027 recipient will always be the same Tor binary as the sender, so
21028 any encoding is overkill.
21031 Changes in version 0.2.4.7-alpha - 2012-12-24
21032 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
21033 directory mirrors for more robust bootstrapping; fixes more issues where
21034 clients with changing network conditions refuse to make any circuits;
21035 adds initial support for exiting to IPv6 addresses; resumes being able
21036 to update our GeoIP database, and includes the geoip6 file this time;
21037 turns off the client-side DNS cache by default due to privacy risks;
21038 and fixes a variety of other issues.
21040 o Major features (client resilience):
21041 - Add a new "FallbackDir" torrc option to use when we can't use
21042 a directory mirror from the consensus (either because we lack a
21043 consensus, or because they're all down). Currently, all authorities
21044 are fallbacks by default, and there are no other default fallbacks,
21045 but that will change. This option will allow us to give clients a
21046 longer list of servers to try to get a consensus from when first
21047 connecting to the Tor network, and thereby reduce load on the
21048 directory authorities. Implements proposal 206, "Preconfigured
21049 directory sources for bootstrapping". We also removed the old
21050 "FallbackNetworkstatus" option, since we never got it working well
21051 enough to use it. Closes bug 572.
21052 - If we have no circuits open, use a relaxed timeout (the
21053 95-percentile cutoff) until a circuit succeeds. This heuristic
21054 should allow Tor to succeed at building circuits even when the
21055 network connection drastically changes. Should help with bug 3443.
21057 o Major features (IPv6):
21058 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
21059 connectivity, then set the IPv6Exit flag to 1. Also make sure your
21060 exit policy reads as you would like: the address * applies to all
21061 address families, whereas *4 is IPv4 address only, and *6 is IPv6
21062 addresses only. On the client side, you'll need to wait until the
21063 authorities have upgraded, wait for enough exits to support IPv6,
21064 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
21065 ticket 5547, implements proposal 117 as revised in proposal 208.
21067 We DO NOT recommend that clients with actual anonymity needs start
21068 using IPv6 over Tor yet, since not enough exits support it yet.
21070 o Major features (geoip database):
21071 - Maxmind began labelling Tor relays as being in country "A1",
21072 which breaks by-country node selection inside Tor. Now we use a
21073 script to replace "A1" ("Anonymous Proxy") entries in our geoip
21074 file with real country codes. This script fixes about 90% of "A1"
21075 entries automatically and uses manual country code assignments to
21076 fix the remaining 10%. See src/config/README.geoip for details.
21077 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
21078 Country database, as modified above.
21080 o Major bugfixes (client-side DNS):
21081 - Turn off the client-side DNS cache by default. Updating and using
21082 the DNS cache is now configurable on a per-client-port
21083 level. SOCKSPort, DNSPort, etc lines may now contain
21084 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
21085 cache these types of DNS answers when we receive them from an
21086 exit node in response to an application request on this port, and
21087 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
21088 cached DNS answers of these types, we shouldn't use them. It's
21089 potentially risky to use cached DNS answers at the client, since
21090 doing so can indicate to one exit what answers we've gotten
21091 for DNS lookups in the past. With IPv6, this becomes especially
21092 problematic. Using cached DNS answers for requests on the same
21093 circuit would present less linkability risk, since all traffic
21094 on a circuit is already linkable, but it would also provide
21095 little performance benefit: the exit node caches DNS replies
21096 too. Implements a simplified version of Proposal 205. Implements
21099 o Major bugfixes (other):
21100 - Alter circuit build timeout measurement to start at the point
21101 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
21102 initialization). This should make our timeout measurements more
21103 uniform. Previously, we were sometimes including ORconn setup time
21104 in our circuit build time measurements. Should resolve bug 3443.
21105 - Fix an assertion that could trigger in hibernate_go_dormant() when
21106 closing an or_connection_t: call channel_mark_for_close() rather
21107 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
21109 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
21110 7655; bugfix on 0.2.4.6-alpha.
21113 - Add a new torrc option "ServerTransportListenAddr" to let bridge
21114 operators select the address where their pluggable transports will
21115 listen for connections. Resolves ticket 7013.
21116 - Allow an optional $ before the node identity digest in the
21117 controller command GETINFO ns/id/<identity>, for consistency with
21118 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
21119 - Log packaged cell fullness as part of the heartbeat message.
21120 Diagnosis to try to determine the extent of bug 7743.
21122 o Minor features (IPv6):
21123 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
21124 prefer to hand out virtual IPv6 addresses, since there are more of
21125 them and we can't run out. To override this behavior and make IPv4
21126 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
21127 or DNSPort you're using for resolving. Implements ticket 7571.
21128 - AutomapHostsOnResolve responses are now randomized, to avoid
21129 annoying situations where Tor is restarted and applications
21130 connect to the wrong addresses.
21131 - Never try more than 1000 times to pick a new virtual address when
21132 AutomapHostsOnResolve is set. That's good enough so long as we
21133 aren't close to handing out our entire virtual address space;
21134 if you're getting there, it's best to switch to IPv6 virtual
21138 - The ADDRMAP command can no longer generate an ill-formed error
21139 code on a failed MAPADDRESS. It now says "internal" rather than
21140 an English sentence fragment with spaces in the middle. Bugfix on
21141 Tor 0.2.0.19-alpha.
21142 - Fix log messages and comments to avoid saying "GMT" when we mean
21143 "UTC". Fixes bug 6113.
21144 - Compile on win64 using mingw64. Fixes bug 7260; patches from
21146 - Fix a crash when debugging unit tests on Windows: deallocate a
21147 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
21148 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
21151 - The DirServer option is now DirAuthority, for consistency with
21152 current naming patterns. You can still use the old DirServer form.
21154 o Code simplification and refactoring:
21155 - Move the client-side address-map/virtual-address/DNS-cache code
21156 out of connection_edge.c into a new addressmap.c module.
21157 - Remove unused code for parsing v1 directories and "running routers"
21158 documents. Fixes bug 6887.
21161 Changes in version 0.2.3.25 - 2012-11-19
21162 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
21163 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
21164 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
21165 programmer, and friend. Unstinting in his dedication to the cause of
21166 freedom, he inspired and helped many of us as we began our work on
21167 anonymity, and inspires us still. Please honor his memory by writing
21168 software to protect people's freedoms, and by helping others to do so.
21170 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
21171 significantly reduced directory overhead (via microdescriptors),
21172 enormous crypto performance improvements for fast relays on new
21173 enough hardware, a new v3 TLS handshake protocol that can better
21174 resist fingerprinting, support for protocol obfuscation plugins (aka
21175 pluggable transports), better scalability for hidden services, IPv6
21176 support for bridges, performance improvements like allowing clients
21177 to skip the first round-trip on the circuit ("optimistic data") and
21178 refilling token buckets more often, a new "stream isolation" design
21179 to isolate different applications on different circuits, and many
21180 stability, security, and privacy fixes.
21183 - Tor tries to wipe potentially sensitive data after using it, so
21184 that if some subsequent security failure exposes Tor's memory,
21185 the damage will be limited. But we had a bug where the compiler
21186 was eliminating these wipe operations when it decided that the
21187 memory was no longer visible to a (correctly running) program,
21188 hence defeating our attempt at defense in depth. We fix that
21189 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
21190 is unlikely to optimize away. Future versions of Tor may use
21191 a less ridiculously heavy approach for this. Fixes bug 7352.
21192 Reported in an article by Andrey Karpov.
21195 - Fix a harmless bug when opting against publishing a relay descriptor
21196 because DisableNetwork is set. Fixes bug 7464; bugfix on
21200 Changes in version 0.2.4.6-alpha - 2012-11-13
21201 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
21202 makes our defense-in-depth memory wiping more reliable, and begins to
21203 count IPv6 addresses in bridge statistics,
21206 - Fix an assertion failure that could occur when closing a connection
21207 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
21209 - Tor tries to wipe potentially sensitive data after using it, so
21210 that if some subsequent security failure exposes Tor's memory,
21211 the damage will be limited. But we had a bug where the compiler
21212 was eliminating these wipe operations when it decided that the
21213 memory was no longer visible to a (correctly running) program,
21214 hence defeating our attempt at defense in depth. We fix that
21215 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
21216 is unlikely to optimize away. Future versions of Tor may use
21217 a less ridiculously heavy approach for this. Fixes bug 7352.
21218 Reported in an article by Andrey Karpov.
21221 - Add GeoIP database for IPv6 addresses. The new config option
21223 - Bridge statistics now count bridge clients connecting over IPv6:
21224 bridge statistics files now list "bridge-ip-versions" and
21225 extra-info documents list "geoip6-db-digest". The control protocol
21226 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
21227 implementation by "shkoo", addressing ticket 5055.
21230 - Warn when we are binding low ports when hibernation is enabled;
21231 previously we had warned when we were _advertising_ low ports with
21232 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
21233 - Fix a harmless bug when opting against publishing a relay descriptor
21234 because DisableNetwork is set. Fixes bug 7464; bugfix on
21236 - Add warning message when a managed proxy dies during configuration.
21237 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
21238 - Fix a linking error when building tor-fw-helper without miniupnp.
21239 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
21240 - Check for closing an or_connection_t without going through correct
21241 channel functions; emit a warning and then call
21242 connection_or_close_for_error() so we don't assert as in bugs 7212
21244 - Compile correctly on compilers without C99 designated initializer
21245 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
21246 - Avoid a possible assert that can occur when channel_send_destroy() is
21247 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
21248 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
21249 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
21250 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
21251 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
21253 o Code simplification and refactoring:
21254 - Start using OpenBSD's implementation of queue.h, so that we don't
21255 need to hand-roll our own pointer and list structures whenever we
21256 need them. (We can't rely on a sys/queue.h, since some operating
21257 systems don't have them, and the ones that do have them don't all
21258 present the same extensions.)
21261 Changes in version 0.2.4.5-alpha - 2012-10-25
21262 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
21263 two important security vulnerabilities that could lead to remotely
21264 triggerable relay crashes, fix a major bug that was preventing clients
21265 from choosing suitable exit nodes, and refactor some of our code.
21267 o Major bugfixes (security, also in 0.2.3.24-rc):
21268 - Fix a group of remotely triggerable assertion failures related to
21269 incorrect link protocol negotiation. Found, diagnosed, and fixed
21270 by "some guy from France". Fix for CVE-2012-2250; bugfix on
21272 - Fix a denial of service attack by which any directory authority
21273 could crash all the others, or by which a single v2 directory
21274 authority could crash everybody downloading v2 directory
21275 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
21277 o Major bugfixes (also in 0.2.3.24-rc):
21278 - When parsing exit policy summaries from microdescriptors, we had
21279 previously been ignoring the last character in each one, so that
21280 "accept 80,443,8080" would be treated by clients as indicating
21281 a node that allows access to ports 80, 443, and 808. That would
21282 lead to clients attempting connections that could never work,
21283 and ignoring exit nodes that would support their connections. Now
21284 clients parse these exit policy summaries correctly. Fixes bug 7192;
21285 bugfix on 0.2.3.1-alpha.
21287 o Minor bugfixes (also in 0.2.3.24-rc):
21288 - Clients now consider the ClientRejectInternalAddresses config option
21289 when using a microdescriptor consensus stanza to decide whether
21290 an exit relay would allow exiting to an internal address. Fixes
21291 bug 7190; bugfix on 0.2.3.1-alpha.
21294 - Only disable TLS session ticket support when running as a TLS
21295 server. Now clients will blend better with regular Firefox
21296 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
21298 o Code simplification and refactoring:
21299 - Start using OpenBSD's implementation of queue.h (originally by
21301 - Move the entry node code from circuitbuild.c to its own file.
21302 - Move the circuit build timeout tracking code from circuitbuild.c
21306 Changes in version 0.2.3.24-rc - 2012-10-25
21307 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
21308 could lead to remotely triggerable relay crashes, and fixes
21309 a major bug that was preventing clients from choosing suitable exit
21312 o Major bugfixes (security):
21313 - Fix a group of remotely triggerable assertion failures related to
21314 incorrect link protocol negotiation. Found, diagnosed, and fixed
21315 by "some guy from France". Fix for CVE-2012-2250; bugfix on
21317 - Fix a denial of service attack by which any directory authority
21318 could crash all the others, or by which a single v2 directory
21319 authority could crash everybody downloading v2 directory
21320 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
21323 - When parsing exit policy summaries from microdescriptors, we had
21324 previously been ignoring the last character in each one, so that
21325 "accept 80,443,8080" would be treated by clients as indicating
21326 a node that allows access to ports 80, 443, and 808. That would
21327 lead to clients attempting connections that could never work,
21328 and ignoring exit nodes that would support their connections. Now
21329 clients parse these exit policy summaries correctly. Fixes bug 7192;
21330 bugfix on 0.2.3.1-alpha.
21333 - Clients now consider the ClientRejectInternalAddresses config option
21334 when using a microdescriptor consensus stanza to decide whether
21335 an exit relay would allow exiting to an internal address. Fixes
21336 bug 7190; bugfix on 0.2.3.1-alpha.
21339 Changes in version 0.2.4.4-alpha - 2012-10-20
21340 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
21341 vulnerability introduced by a change in OpenSSL, fixes a remotely
21342 triggerable assert, and adds new channel_t and circuitmux_t abstractions
21343 that will make it easier to test new connection transport and cell
21344 scheduling algorithms.
21346 o New directory authorities (also in 0.2.3.23-rc):
21347 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
21348 authority. Closes ticket 5749.
21350 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
21351 - Disable TLS session tickets. OpenSSL's implementation was giving
21352 our TLS session keys the lifetime of our TLS context objects, when
21353 perfect forward secrecy would want us to discard anything that
21354 could decrypt a link connection as soon as the link connection
21355 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
21356 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
21357 - Discard extraneous renegotiation attempts once the V3 link
21358 protocol has been initiated. Failure to do so left us open to
21359 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
21360 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
21362 o Internal abstraction features:
21363 - Introduce new channel_t abstraction between circuits and
21364 or_connection_t to allow for implementing alternate OR-to-OR
21365 transports. A channel_t is an abstract object which can either be a
21366 cell-bearing channel, which is responsible for authenticating and
21367 handshaking with the remote OR and transmitting cells to and from
21368 it, or a listening channel, which spawns new cell-bearing channels
21369 at the request of remote ORs. Implements part of ticket 6465.
21370 - Also new is the channel_tls_t subclass of channel_t, adapting it
21371 to the existing or_connection_t code. The V2/V3 protocol handshaking
21372 code which formerly resided in command.c has been moved below the
21373 channel_t abstraction layer and may be found in channeltls.c now.
21374 Implements the rest of ticket 6465.
21375 - Introduce new circuitmux_t storing the queue of circuits for
21376 a channel; this encapsulates and abstracts the queue logic and
21377 circuit selection policy, and allows the latter to be overridden
21378 easily by switching out a policy object. The existing EWMA behavior
21379 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
21381 o Required libraries:
21382 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
21383 strongly recommended.
21386 - Warn users who run hidden services on a Tor client with
21387 UseEntryGuards disabled that their hidden services will be
21388 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
21389 attack which motivated Tor to support entry guards in the first
21390 place). Resolves ticket 6889.
21391 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
21392 dhill. Resolves ticket 6982.
21393 - Option OutboundBindAddress can be specified multiple times and
21394 accepts IPv6 addresses. Resolves ticket 6876.
21396 o Minor bugfixes (also in 0.2.3.23-rc):
21397 - Don't serve or accept v2 hidden service descriptors over a
21398 relay's DirPort. It's never correct to do so, and disabling it
21399 might make it more annoying to exploit any bugs that turn up in the
21400 descriptor-parsing code. Fixes bug 7149.
21401 - Fix two cases in src/or/transports.c where we were calling
21402 fmt_addr() twice in a parameter list. Bug found by David
21403 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
21404 - Fix memory leaks whenever we logged any message about the "path
21405 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
21406 - When relays refuse a "create" cell because their queue of pending
21407 create cells is too big (typically because their cpu can't keep up
21408 with the arrival rate), send back reason "resource limit" rather
21409 than reason "internal", so network measurement scripts can get a
21410 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
21413 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
21414 - Free some more still-in-use memory at exit, to make hunting for
21415 memory leaks easier. Resolves bug 7029.
21416 - When a Tor client gets a "truncated" relay cell, the first byte of
21417 its payload specifies why the circuit was truncated. We were
21418 ignoring this 'reason' byte when tearing down the circuit, resulting
21419 in the controller not being told why the circuit closed. Now we
21420 pass the reason from the truncated cell to the controller. Bugfix
21421 on 0.1.2.3-alpha; fixes bug 7039.
21422 - Downgrade "Failed to hand off onionskin" messages to "debug"
21423 severity, since they're typically redundant with the "Your computer
21424 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
21425 - Make clients running with IPv6 bridges connect over IPv6 again,
21426 even without setting new config options ClientUseIPv6 and
21427 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
21428 - Use square brackets around IPv6 addresses in numerous places
21429 that needed them, including log messages, HTTPS CONNECT proxy
21430 requests, TransportProxy statefile entries, and pluggable transport
21431 extra-info lines. Fixes bug 7011; patch by David Fifield.
21433 o Code refactoring and cleanup:
21434 - Source files taken from other packages now reside in src/ext;
21435 previously they were scattered around the rest of Tor.
21436 - Avoid use of reserved identifiers in our C code. The C standard
21437 doesn't like us declaring anything that starts with an
21438 underscore, so let's knock it off before we get in trouble. Fix
21439 for bug 1031; bugfix on the first Tor commit.
21442 Changes in version 0.2.3.23-rc - 2012-10-20
21443 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
21444 vulnerability introduced by a change in OpenSSL, and fixes a variety
21445 of smaller bugs in preparation for the release.
21447 o New directory authorities:
21448 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
21449 authority. Closes ticket 5749.
21451 o Major bugfixes (security/privacy):
21452 - Disable TLS session tickets. OpenSSL's implementation was giving
21453 our TLS session keys the lifetime of our TLS context objects, when
21454 perfect forward secrecy would want us to discard anything that
21455 could decrypt a link connection as soon as the link connection
21456 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
21457 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
21458 - Discard extraneous renegotiation attempts once the V3 link
21459 protocol has been initiated. Failure to do so left us open to
21460 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
21461 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
21464 - Fix a possible crash bug when checking for deactivated circuits
21465 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
21466 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
21468 o Minor bugfixes (on 0.2.3.x):
21469 - Fix two cases in src/or/transports.c where we were calling
21470 fmt_addr() twice in a parameter list. Bug found by David
21471 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
21472 - Convert an assert in the pathbias code to a log message. The assert
21473 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
21474 bugfix on 0.2.3.17-beta.
21475 - Fix memory leaks whenever we logged any message about the "path
21476 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
21478 o Minor bugfixes (on 0.2.2.x and earlier):
21479 - Don't serve or accept v2 hidden service descriptors over a relay's
21480 DirPort. It's never correct to do so, and disabling it might
21481 make it more annoying to exploit any bugs that turn up in the
21482 descriptor-parsing code. Fixes bug 7149.
21483 - When relays refuse a "create" cell because their queue of pending
21484 create cells is too big (typically because their cpu can't keep up
21485 with the arrival rate), send back reason "resource limit" rather
21486 than reason "internal", so network measurement scripts can get a
21487 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
21488 - Correct file sizes when reading binary files on Cygwin, to avoid
21489 a bug where Tor would fail to read its state file. Fixes bug 6844;
21490 bugfix on 0.1.2.7-alpha.
21491 - Avoid undefined behavior when parsing the list of supported
21492 rendezvous/introduction protocols in a hidden service descriptor.
21493 Previously, Tor would have confused (as-yet-unused) protocol version
21494 numbers greater than 32 with lower ones on many platforms. Fixes
21495 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
21497 o Documentation fixes:
21498 - Clarify that hidden services are TCP only. Fixes bug 6024.
21501 Changes in version 0.2.4.3-alpha - 2012-09-22
21502 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
21503 assertion, resumes letting relays test reachability of their DirPort,
21504 and cleans up a bunch of smaller bugs.
21507 - Fix an assertion failure in tor_timegm() that could be triggered
21508 by a badly formatted directory object. Bug found by fuzzing with
21509 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21512 - Fix a possible crash bug when checking for deactivated circuits
21513 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
21514 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
21515 - Allow routers to detect that their own DirPorts are running. When
21516 we removed support for versions_supports_begindir, we also
21517 accidentally removed the mechanism we used to self-test our
21518 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
21519 bugfix on 0.2.4.2-alpha.
21521 o Security features:
21522 - Switch to a completely time-invariant approach for picking nodes
21523 weighted by bandwidth. Our old approach would run through the
21524 part of the loop after it had made its choice slightly slower
21525 than it ran through the part of the loop before it had made its
21526 choice. Addresses ticket 6538.
21527 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
21528 by tor2web clients allows hidden services to identify tor2web
21529 clients through their repeated selection of the same rendezvous
21530 and introduction point circuit endpoints (their guards). Resolves
21534 - Enable Tor to read configuration, state, and key information from
21535 a FIFO. Previously Tor would only read from files with a positive
21536 stat.st_size. Code from meejah; fixes bug 6044.
21539 - Correct file sizes when reading binary files on Cygwin, to avoid
21540 a bug where Tor would fail to read its state file. Fixes bug 6844;
21541 bugfix on 0.1.2.7-alpha.
21542 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
21543 bugfix on 0.2.0.3-alpha.
21544 - When complaining about a client port on a public address, log
21545 which address we're complaining about. Fixes bug 4020; bugfix on
21546 0.2.3.3-alpha. Patch by Tom Fitzhenry.
21547 - Convert an assert in the pathbias code to a log message. The assert
21548 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
21549 bugfix on 0.2.3.17-beta.
21550 - Our new buildsystem was overzealous about rebuilding manpages: it
21551 would rebuild them all whenever any one of them changed. Now our
21552 dependency checking should be correct. Fixes bug 6843; bugfix on
21554 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
21555 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
21556 - Correct log printout about which address family is preferred
21557 when connecting to a bridge with both an IPv4 and IPv6 OR port.
21558 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
21560 o Minor bugfixes (code cleanliness):
21561 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
21562 with large values. This situation was untriggered, but nevertheless
21563 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
21564 - Reject consensus votes with more than 64 known-flags. We aren't even
21565 close to that limit yet, and our code doesn't handle it correctly.
21566 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
21567 - Avoid undefined behavior when parsing the list of supported
21568 rendezvous/introduction protocols in a hidden service descriptor.
21569 Previously, Tor would have confused (as-yet-unused) protocol version
21570 numbers greater than 32 with lower ones on many platforms. Fixes
21571 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
21572 - Fix handling of rendezvous client authorization types over 8.
21573 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
21574 - Fix building with older versions of GCC (2.95, for one) that don't
21575 like preprocessor directives inside macro arguments. Found by
21576 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
21577 - Switch weighted node selection rule from using a list of doubles
21578 to using a list of int64_t. This change should make the process
21579 slightly easier to debug and maintain. Needed to finish ticket 6538.
21581 o Code simplification and refactoring:
21582 - Move the generic "config" code into a new file, and have "config.c"
21583 hold only torrc- and state-related code. Resolves ticket 6823.
21584 - Move the core of our "choose a weighted element at random" logic
21585 into its own function, and give it unit tests. Now the logic is
21586 testable, and a little less fragile too.
21587 - Removed the testing_since field of node_t, which hasn't been used
21588 for anything since 0.2.0.9-alpha.
21590 o Documentation fixes:
21591 - Clarify that hidden services are TCP only. Fixes bug 6024.
21592 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
21596 Changes in version 0.2.3.22-rc - 2012-09-11
21597 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
21601 - Fix an assertion failure in tor_timegm() that could be triggered
21602 by a badly formatted directory object. Bug found by fuzzing with
21603 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21606 - Avoid segfault when starting up having run with an extremely old
21607 version of Tor and parsing its state file. Fixes bug 6801; bugfix
21611 Changes in version 0.2.2.39 - 2012-09-11
21612 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
21616 - Fix an assertion failure in tor_timegm() that could be triggered
21617 by a badly formatted directory object. Bug found by fuzzing with
21618 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
21619 - Do not crash when comparing an address with port value 0 to an
21620 address policy. This bug could have been used to cause a remote
21621 assertion failure by or against directory authorities, or to
21622 allow some applications to crash clients. Fixes bug 6690; bugfix
21626 Changes in version 0.2.4.2-alpha - 2012-09-10
21627 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
21628 raises the default rate limiting even more, and makes the bootstrapping
21629 log messages less noisy.
21632 - Automatically forward the TCP ports of pluggable transport
21633 proxies using tor-fw-helper if PortForwarding is enabled. Implements
21637 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
21638 to 1GB/1GB. The previous defaults were intended to be "basically
21639 infinite", but it turns out they're now limiting our 100mbit+
21640 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
21641 last time we raised it).
21644 - Detect when we're running with a version of OpenSSL other than the
21645 one we compiled with. This has occasionally given people hard-to-
21647 - Log fewer lines at level "notice" about our OpenSSL and Libevent
21648 versions and capabilities when everything is going right. Resolves
21649 part of ticket 6736.
21650 - Directory authorities no long accept descriptors for any version of
21651 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
21652 These versions are insecure, unsupported, or both. Implements
21656 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
21657 to start with a triple-underscore so the controller won't touch it.
21658 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
21659 - Avoid segfault when starting up having run with an extremely old
21660 version of Tor and parsing its state file. Fixes bug 6801; bugfix
21662 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
21663 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
21664 - Don't follow the NULL pointer if microdescriptor generation fails.
21665 (This does not appear to be triggerable, but it's best to be safe.)
21666 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
21667 - Fix mis-declared dependencies on src/common/crypto.c and
21668 src/or/tor_main.c that could break out-of-tree builds under some
21669 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
21670 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
21671 6778; bugfix on 0.2.4.1-alpha.
21672 - Fix a harmless (in this case) build warning for implicitly
21673 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
21675 o Removed features:
21676 - Now that all versions before 0.2.2.x are disallowed, we no longer
21677 need to work around their missing features. Thus we can remove a
21678 bunch of compatibility code.
21680 o Code refactoring:
21681 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
21682 TCP ports to forward. In the past it only accepted two ports:
21683 the ORPort and the DirPort.
21686 Changes in version 0.2.4.1-alpha - 2012-09-05
21687 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
21688 bridgedb; lets relays use IPv6 addresses and directory authorities
21689 advertise them; and switches to a cleaner build interface.
21691 This is the first alpha release in a new series, so expect there to
21692 be bugs. Users who would rather test out a more stable branch should
21693 stay with 0.2.3.x for now.
21695 o Major features (bridges):
21696 - Bridges now report the pluggable transports they support to the
21697 bridge authority, so it can pass the supported transports on to
21698 bridgedb and/or eventually do reachability testing. Implements
21701 o Major features (IPv6):
21702 - Bridge authorities now accept IPv6 bridge addresses and include
21703 them in network status documents. Implements ticket 5534.
21704 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
21705 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
21706 to happen. Implements ticket 5535.
21707 - All kind of relays, not just bridges, can now advertise an IPv6
21708 OR port. Implements ticket 6362.
21709 - Directory authorities vote on IPv6 OR ports using the new consensus
21710 method 14. Implements ticket 6363.
21712 o Major features (build):
21713 - Switch to a nonrecursive Makefile structure. Now instead of each
21714 Makefile.am invoking other Makefile.am's, there is a master
21715 Makefile.am that includes the others. This change makes our build
21716 process slightly more maintainable, and improves parallelism for
21717 building with make -j. Original patch by Stewart Smith; various
21718 fixes by Jim Meyering.
21719 - Where available, we now use automake's "silent" make rules by
21720 default, so that warnings are easier to spot. You can get the old
21721 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
21723 o Minor features (code security and spec conformance):
21724 - Clear keys and key-derived material left on the stack in
21725 rendservice.c and rendclient.c. Check return value of
21726 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
21727 These fixes should make us more forward-secure against cold-boot
21728 attacks and the like. Fixes bug 2385.
21729 - Reject EXTEND cells sent to nonexistent streams. According to the
21730 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
21731 we were only checking for stream IDs that were currently in use.
21732 Found while hunting for more instances of bug 6271. Bugfix on
21733 0.0.2pre8, which introduced incremental circuit construction.
21735 o Minor features (streamlining);
21736 - No longer include the "opt" prefix when generating routerinfos
21737 or v2 directories: it has been needless since Tor 0.1.2. Closes
21739 - Remove some now-needless code that tried to aggressively flush
21740 OR connections as data was added to them. Since 0.2.0.1-alpha, our
21741 cell queue logic has saved us from the failure mode that this code
21742 was supposed to prevent. Removing this code will limit the number
21743 of baroque control flow paths through Tor's network logic. Reported
21744 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
21746 o Minor features (controller):
21747 - Add a "GETINFO signal/names" control port command. Implements
21749 - Provide default values for all options via "GETINFO config/defaults".
21750 Implements ticket 4971.
21752 o Minor features (IPv6):
21753 - New config option "AuthDirHasIPv6Connectivity 1" that directory
21754 authorities should set if they have IPv6 connectivity and want to
21755 do reachability tests for IPv6 relays. Implements feature 5974.
21756 - A relay with an IPv6 OR port now sends that address in NETINFO
21757 cells (in addition to its other address). Implements ticket 6364.
21759 o Minor features (log messages):
21760 - Omit the first heartbeat log message, because it never has anything
21761 useful to say, and it clutters up the bootstrapping messages.
21762 Resolves ticket 6758.
21763 - Don't log about reloading the microdescriptor cache at startup. Our
21764 bootstrap warnings are supposed to tell the user when there's a
21765 problem, and our bootstrap notices say when there isn't. Resolves
21766 ticket 6759; bugfix on 0.2.2.6-alpha.
21767 - Don't log "I learned some more directory information" when we're
21768 reading cached directory information. Reserve it for when new
21769 directory information arrives in response to a fetch. Resolves
21771 - Prevent rounding error in path bias counts when scaling
21772 them down, and use the correct scale factor default. Also demote
21773 some path bias related log messages down a level and make others
21774 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
21775 - We no longer warn so much when generating manpages from their
21778 o Code simplifications and refactoring:
21779 - Enhance our internal sscanf replacement so that we can eliminate
21780 the last remaining uses of the system sscanf. (Though those uses
21781 of sscanf were safe, sscanf itself is generally error prone, so
21782 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
21784 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
21785 - Move last_reachable and testing_since from routerinfo_t to node_t.
21786 Implements ticket 5529.
21787 - Add replaycache_t structure, functions and unit tests, then refactor
21788 rend_service_introduce() to be more clear to read, improve, debug,
21789 and test. Resolves bug 6177.
21790 - Finally remove support for malloc_good_size and malloc_usable_size.
21791 We had hoped that these functions would let us eke a little more
21792 memory out of our malloc implementation. Unfortunately, the only
21793 implementations that provided these functions are also ones that
21794 are already efficient about not overallocation: they never got us
21795 more than 7 or so bytes per allocation. Removing them saves us a
21796 little code complexity and a nontrivial amount of build complexity.
21798 o New requirements:
21799 - Tor maintainers now require Automake version 1.9 or later to build
21800 Tor from the Git repository. (Automake is not required when building
21801 from a source distribution.)
21804 Changes in version 0.2.3.21-rc - 2012-09-05
21805 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
21806 series. It fixes a trio of potential security bugs, fixes a bug where
21807 we were leaving some of the fast relays out of the microdescriptor
21808 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
21809 and cleans up other smaller issues.
21811 o Major bugfixes (security):
21812 - Tear down the circuit if we get an unexpected SENDME cell. Clients
21813 could use this trick to make their circuits receive cells faster
21814 than our flow control would have allowed, or to gum up the network,
21815 or possibly to do targeted memory denial-of-service attacks on
21816 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
21817 from July 2002, before the release of Tor 0.0.0. We had committed
21818 this patch previously, but we had to revert it because of bug 6271.
21819 Now that 6271 is fixed, this patch appears to work.
21820 - Reject any attempt to extend to an internal address. Without
21821 this fix, a router could be used to probe addresses on an internal
21822 network to see whether they were accepting connections. Fixes bug
21823 6710; bugfix on 0.0.8pre1.
21824 - Do not crash when comparing an address with port value 0 to an
21825 address policy. This bug could have been used to cause a remote
21826 assertion failure by or against directory authorities, or to
21827 allow some applications to crash clients. Fixes bug 6690; bugfix
21831 - Remove the upper bound on microdescriptor length. We were hitting
21832 the limit for routers with complex exit policies or family
21833 declarations, causing clients to not use them. Fixes the first
21834 piece of bug 6404; fix on 0.2.2.6-alpha.
21835 - Detect "ORPort 0" as meaning, uniformly, that we're not running
21836 as a relay. Previously, some of our code would treat the presence
21837 of any ORPort line as meaning that we should act like a relay,
21838 even though our new listener code would correctly not open any
21839 ORPorts for ORPort 0. Similar bugs in other Port options are also
21840 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
21843 - Avoid a pair of double-free and use-after-mark bugs that can
21844 occur with certain timings in canceled and re-received DNS
21845 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
21846 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
21847 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
21848 - Allow one-hop directory fetching circuits the full "circuit build
21849 timeout" period, rather than just half of it, before failing them
21850 and marking the relay down. This fix should help reduce cases where
21851 clients declare relays (or worse, bridges) unreachable because
21852 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
21853 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
21855 - Authorities no longer include any router in their microdescriptor
21856 consensuses for which they couldn't generate or agree on a
21857 microdescriptor. Fixes the second piece of bug 6404; fix on
21859 - Detect and reject attempts to specify both "FooPort" and
21860 "FooPort 0" in the same configuration domain. (It's still okay
21861 to have a FooPort in your configuration file, and use "FooPort 0"
21862 on the command line to disable it.) Fixes the second half of bug
21863 6507; bugfix on 0.2.3.3-alpha.
21864 - Make wildcarded addresses (that is, ones beginning with "*.") work
21865 when provided via the controller's MapAddress command. Previously,
21866 they were accepted, but we never actually noticed that they were
21867 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
21868 - Avoid crashing on a malformed state file where EntryGuardPathBias
21869 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
21870 - Add a (probably redundant) memory clear between iterations of
21871 the router status voting loop, to prevent future coding errors
21872 where data might leak between iterations of the loop. Resolves
21875 o Minor bugfixes (log messages):
21876 - Downgrade "set buildtimeout to low value" messages to "info"
21877 severity; they were never an actual problem, there was never
21878 anything reasonable to do about them, and they tended to spam logs
21879 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
21880 - Downgrade path-bias warning messages to "info". We'll try to get
21881 them working better in 0.2.4. Add internal circuit construction
21882 state to protect against the noisy warn message "Unexpectedly high
21883 circuit_successes". Also add some additional rate-limited notice
21884 messages to help determine the root cause of the warn. Fixes bug
21885 6475. Bugfix against 0.2.3.17-beta.
21886 - Move log message when unable to find a microdesc in a routerstatus
21887 entry to parse time. Previously we'd spam this warning every time
21888 we tried to figure out which microdescriptors to download. Fixes
21889 the third piece of bug 6404; fix on 0.2.3.18-rc.
21892 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
21893 change when the authority is deciding whether to accept a newly
21894 uploaded descriptor. Implements ticket 6423.
21895 - Add missing documentation for consensus and microdesc files.
21896 Resolves ticket 6732.
21899 Changes in version 0.2.2.38 - 2012-08-12
21900 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
21901 attack that could in theory leak path information.
21904 - Avoid an uninitialized memory read when reading a vote or consensus
21905 document that has an unrecognized flavor name. This read could
21906 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
21907 - Try to leak less information about what relays a client is
21908 choosing to a side-channel attacker. Previously, a Tor client would
21909 stop iterating through the list of available relays as soon as it
21910 had chosen one, thus finishing a little earlier when it picked
21911 a router earlier in the list. If an attacker can recover this
21912 timing information (nontrivial but not proven to be impossible),
21913 they could learn some coarse-grained information about which relays
21914 a client was picking (middle nodes in particular are likelier to
21915 be affected than exits). The timing attack might be mitigated by
21916 other factors (see bug 6537 for some discussion), but it's best
21917 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
21920 Changes in version 0.2.3.20-rc - 2012-08-05
21921 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
21922 series. It fixes a pair of code security bugs and a potential anonymity
21923 issue, updates our RPM spec files, and cleans up other smaller issues.
21926 - Avoid read-from-freed-memory and double-free bugs that could occur
21927 when a DNS request fails while launching it. Fixes bug 6480;
21928 bugfix on 0.2.0.1-alpha.
21929 - Avoid an uninitialized memory read when reading a vote or consensus
21930 document that has an unrecognized flavor name. This read could
21931 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
21932 - Try to leak less information about what relays a client is
21933 choosing to a side-channel attacker. Previously, a Tor client would
21934 stop iterating through the list of available relays as soon as it
21935 had chosen one, thus finishing a little earlier when it picked
21936 a router earlier in the list. If an attacker can recover this
21937 timing information (nontrivial but not proven to be impossible),
21938 they could learn some coarse-grained information about which relays
21939 a client was picking (middle nodes in particular are likelier to
21940 be affected than exits). The timing attack might be mitigated by
21941 other factors (see bug 6537 for some discussion), but it's best
21942 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
21945 - Try to make the warning when giving an obsolete SOCKSListenAddress
21946 a little more useful.
21947 - Terminate active server managed proxies if Tor stops being a
21948 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
21949 - Provide a better error message about possible OSX Asciidoc failure
21950 reasons. Fixes bug 6436.
21951 - Warn when Tor is configured to use accounting in a way that can
21952 link a hidden service to some other hidden service or public
21953 address. Resolves ticket 6490.
21956 - Check return value of fputs() when writing authority certificate
21957 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
21958 - Ignore ServerTransportPlugin lines when Tor is not configured as
21959 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
21960 - When disabling guards for having too high a proportion of failed
21961 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
21965 - Update our default RPM spec files to work with mock and rpmbuild
21966 on RHEL/Fedora. They have an updated set of dependencies and
21967 conflicts, a fix for an ancient typo when creating the "_tor"
21968 user, and better instructions. Thanks to Ondrej Mikle for the
21969 patch series. Fixes bug 6043.
21972 - Make it possible to set the TestingTorNetwork configuration
21973 option using AlternateDirAuthority and AlternateBridgeAuthority
21974 as an alternative to setting DirServer. Addresses ticket 6377.
21977 - Clarify the documentation for the Alternate*Authority options.
21979 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
21981 o Code simplification and refactoring:
21982 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
21983 10 lines. Also, don't nest them. Doing so in the past has
21984 led to hard-to-debug code. The new style is to use the
21985 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
21988 Changes in version 0.2.3.19-rc - 2012-07-06
21989 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
21990 series. It fixes the compile on Windows, reverts to a GeoIP database
21991 that isn't as broken, and fixes a flow control bug that has been around
21992 since the beginning of Tor.
21995 - Fix a bug handling SENDME cells on nonexistent streams that could
21996 result in bizarre window values. Report and patch contributed
21997 pseudonymously. Fixes part of bug 6271. This bug was introduced
21998 before the first Tor release, in svn commit r152.
21999 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
22000 June 2012 database, Maxmind marked many Tor relays as country "A1",
22001 which will cause risky behavior for clients that set EntryNodes
22002 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
22003 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
22004 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
22007 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
22008 bugfix on 0.2.1.10-alpha.
22011 Changes in version 0.2.3.18-rc - 2012-06-28
22012 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
22013 series. It fixes a few smaller bugs, but generally appears stable.
22014 Please test it and let us know whether it is!
22017 - Allow wildcarded mapaddress targets to be specified on the
22018 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
22019 - Make our linker option detection code more robust against linkers
22020 such as on FreeBSD 8, where a bad combination of options completes
22021 successfully but makes an unrunnable binary. Fixes bug 6173;
22022 bugfix on 0.2.3.17-beta.
22024 o Minor bugfixes (on 0.2.2.x and earlier):
22025 - Avoid a false positive in the util/threads unit test by increasing
22026 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
22027 - Replace "Sending publish request" log messages with "Launching
22028 upload", so that they no longer confusingly imply that we're
22029 sending something to a directory we might not even be connected
22030 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
22031 - Make sure to set *socket_error in all error cases in
22032 connection_connect(), so it can't produce a warning about
22033 errno being zero from errno_to_orconn_end_reason(). Bugfix on
22034 0.2.1.1-alpha; resolves ticket 6028.
22035 - Downgrade "Got a certificate, but we already have it" log messages
22036 from warning to info, except when we're a dirauth. Fixes bug 5238;
22037 bugfix on 0.2.1.7-alpha.
22038 - When checking for requested signatures on the latest consensus
22039 before serving it to a client, make sure to check the right
22040 consensus flavor. Bugfix on 0.2.2.6-alpha.
22041 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
22042 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
22044 o Minor bugfixes (on 0.2.3.x):
22045 - Make format_helper_exit_status() avoid unnecessary space padding
22046 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
22048 - Downgrade a message about cleaning the microdescriptor cache to
22049 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
22050 - Log a BUG message at severity INFO if we have a networkstatus with
22051 a missing entry for some microdescriptor. Continues on a patch
22053 - Improve the log message when a managed proxy fails to launch. Fixes
22054 bug 5099; bugfix on 0.2.3.6-alpha.
22055 - Don't do DNS lookups when parsing corrupted managed proxy protocol
22056 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
22057 - When formatting wildcarded address mappings for the controller,
22058 be sure to include "*." as appropriate. Partially fixes bug 6244;
22059 bugfix on 0.2.3.9-alpha.
22060 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
22061 Bugfix on 0.2.3.13-alpha.
22062 - Stop logging messages about running with circuit timeout learning
22063 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
22064 - Disable a spurious warning about reading on a marked and flushing
22065 connection. We shouldn't be doing that, but apparently we
22066 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
22067 - Fix a bug that stopped AllowDotExit from working on addresses
22068 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
22071 o Code simplification, refactoring, unit tests:
22072 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
22073 Libevent's notion of cached time when possible.
22074 - Remove duplicate code for invoking getrlimit() from control.c.
22075 - Add a unit test for the environment_variable_names_equal function.
22078 - Document the --defaults-torrc option, and the new (in 0.2.3)
22079 semantics for overriding, extending, and clearing lists of
22080 options. Closes bug 4748.
22083 Changes in version 0.2.3.17-beta - 2012-06-15
22084 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
22085 gets our TLS handshake back on track for being able to blend in with
22086 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
22087 with Vidalia, and otherwise continues to get us closer to a release
22091 - Enable gcc and ld hardening by default. Resolves ticket 5210.
22092 - Update TLS cipher list to match Firefox 8 and later. Resolves
22094 - Implement the client side of proposal 198: remove support for
22095 clients falsely claiming to support standard ciphersuites that
22096 they can actually provide. As of modern OpenSSL versions, it's not
22097 necessary to fake any standard ciphersuite, and doing so prevents
22098 us from using better ciphersuites in the future, since servers
22099 can't know whether an advertised ciphersuite is really supported or
22100 not. Some hosts -- notably, ones with very old versions of OpenSSL
22101 or where OpenSSL has been built with ECC disabled -- will stand
22102 out because of this change; TBB users should not be affected.
22105 - Change the default value for DynamicDHGroups (introduced in
22106 0.2.3.9-alpha) to 0. This feature can make Tor relays less
22107 identifiable by their use of the mod_ssl DH group, but at
22108 the cost of some usability (#4721) and bridge tracing (#6087)
22109 regressions. Resolves ticket 5598.
22110 - Send a CRLF at the end of each STATUS_* control protocol event. This
22111 bug tickled a bug in Vidalia which would make it freeze. Fixes
22112 bug 6094; bugfix on 0.2.3.16-alpha.
22115 - Disable writing on marked-for-close connections when they are
22116 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
22117 bug 5263; bugfix on 0.0.2pre13, where we first added a special
22118 case for flushing marked connections.
22119 - Detect SSL handshake even when the initial attempt to write the
22120 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
22121 - Change the AllowDotExit rules so they should actually work.
22122 We now enforce AllowDotExit only immediately after receiving an
22123 address via SOCKS or DNSPort: other sources are free to provide
22124 .exit addresses after the resolution occurs. Fixes bug 3940;
22125 bugfix on 0.2.2.1-alpha.
22126 - Fix a (harmless) integer overflow in cell statistics reported by
22127 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
22128 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
22129 right places and never depends on the consensus parameters or
22130 computes adaptive timeouts when it is disabled. Fixes bug 5049;
22131 bugfix on 0.2.2.14-alpha.
22132 - When building Tor on Windows with -DUNICODE (not default), ensure
22133 that error messages, filenames, and DNS server names are always
22134 NUL-terminated when we convert them to a single-byte encoding.
22135 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
22136 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
22137 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
22138 - Fix an edge case where TestingTorNetwork is set but the authorities
22139 and relays all have an uptime of zero, where the private Tor network
22140 could briefly lack support for hidden services. Fixes bug 3886;
22141 bugfix on 0.2.2.18-alpha.
22142 - Correct the manpage's descriptions for the default values of
22143 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
22145 - Fix the documentation for the --hush and --quiet command line
22146 options, which changed their behavior back in 0.2.3.3-alpha.
22147 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
22151 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
22152 more information to it, so that we can track it down in case it
22153 returns again. Mitigates bug 5235.
22154 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
22155 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
22156 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
22157 - Warn the user when HTTPProxy, but no other proxy type, is
22158 configured. This can cause surprising behavior: it doesn't send
22159 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
22160 directory traffic only. Resolves ticket 4663.
22161 - Issue a notice if a guard completes less than 40% of your circuits.
22162 Threshold is configurable by torrc option PathBiasNoticeRate and
22163 consensus parameter pb_noticepct. There is additional, off-by-
22164 default code to disable guards which fail too many circuits.
22165 Addresses ticket 5458.
22166 - Update to the June 6 2012 Maxmind GeoLite Country database.
22168 o Code simplifications and refactoring:
22169 - Remove validate_pluggable_transports_config(): its warning
22170 message is now handled by connection_or_connect().
22173 Changes in version 0.2.2.37 - 2012-06-06
22174 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
22175 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
22179 - Work around a bug in OpenSSL that broke renegotiation with TLS
22180 1.1 and TLS 1.2. Without this workaround, all attempts to speak
22181 the v2 Tor connection protocol when both sides were using OpenSSL
22182 1.0.1 would fail. Resolves ticket 6033.
22183 - When waiting for a client to renegotiate, don't allow it to add
22184 any bytes to the input buffer. This fixes a potential DoS issue.
22185 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
22186 - Fix an edge case where if we fetch or publish a hidden service
22187 descriptor, we might build a 4-hop circuit and then use that circuit
22188 for exiting afterwards -- even if the new last hop doesn't obey our
22189 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
22192 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
22193 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
22196 - Tell GCC and Clang to check for any errors in format strings passed
22197 to the tor_v*(print|scan)f functions.
22200 Changes in version 0.2.3.16-alpha - 2012-06-05
22201 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
22202 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
22203 currently). It also fixes a variety of smaller bugs and other cleanups
22204 that get us closer to a release candidate.
22206 o Major bugfixes (general):
22207 - Work around a bug in OpenSSL that broke renegotiation with TLS
22208 1.1 and TLS 1.2. Without this workaround, all attempts to speak
22209 the v2 Tor connection protocol when both sides were using OpenSSL
22210 1.0.1 would fail. Resolves ticket 6033.
22211 - When waiting for a client to renegotiate, don't allow it to add
22212 any bytes to the input buffer. This fixes a potential DoS issue.
22213 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
22214 - Pass correct OR address to managed proxies (like obfsproxy),
22215 even when ORListenAddress is used. Fixes bug 4865; bugfix on
22217 - The advertised platform of a router now includes only its operating
22218 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
22219 service pack level (for Windows) or its CPU architecture (for Unix).
22220 We also no longer include the "git-XYZ" tag in the version. Resolves
22223 o Major bugfixes (clients):
22224 - If we are unable to find any exit that supports our predicted ports,
22225 stop calling them predicted, so that we don't loop and build
22226 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
22227 which introduced predicted ports.
22228 - Fix an edge case where if we fetch or publish a hidden service
22229 descriptor, we might build a 4-hop circuit and then use that circuit
22230 for exiting afterwards -- even if the new last hop doesn't obey our
22231 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
22232 - Check at each new consensus whether our entry guards were picked
22233 long enough ago that we should rotate them. Previously, we only
22234 did this check at startup, which could lead to us holding a guard
22235 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
22236 - When fetching a bridge descriptor from a bridge authority,
22237 always do so anonymously, whether we have been able to open
22238 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
22239 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
22240 but we'll need to wait for bug 6010 before it's actually usable.
22242 o Major bugfixes (directory authorities):
22243 - When computing weight parameters, behave more robustly in the
22244 presence of a bad bwweightscale value. Previously, the authorities
22245 would crash if they agreed on a sufficiently broken weight_scale
22246 value: now, they use a reasonable default and carry on. Partial
22247 fix for 5786; bugfix on 0.2.2.17-alpha.
22248 - Check more thoroughly to prevent a rogue authority from
22249 double-voting on any consensus directory parameter. Previously,
22250 authorities would crash in this case if the total number of
22251 votes for any parameter exceeded the number of active voters,
22252 but would let it pass otherwise. Partial fix for bug 5786; bugfix
22256 - Rate-limit log messages when asked to connect anonymously to
22257 a private address. When these hit, they tended to hit fast and
22258 often. Also, don't bother trying to connect to addresses that we
22259 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
22260 reply makes us think we have been lied to, even when the address the
22261 client tried to connect to was "localhost." Resolves ticket 2822.
22262 - Allow packagers to insert an extra string in server descriptor
22263 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
22264 Resolves the rest of ticket 2988.
22265 - Raise the threshold of server descriptors needed (75%) and exit
22266 server descriptors needed (50%) before we will declare ourselves
22267 bootstrapped. This will make clients start building circuits a
22268 little later, but makes the initially constructed circuits less
22269 skewed and less in conflict with further directory fetches. Fixes
22271 - Close any connection that sends unrecognized junk before the
22272 handshake. Solves an issue noted in bug 4369.
22273 - Improve log messages about managed transports. Resolves ticket 5070.
22274 - Tag a bridge's descriptor as "never to be sent unencrypted".
22275 This shouldn't matter, since bridges don't open non-anonymous
22276 connections to the bridge authority and don't allow unencrypted
22277 directory connections from clients, but we might as well make
22278 sure. Closes bug 5139.
22279 - Expose our view of whether we have gone dormant to the controller,
22280 via a new "GETINFO dormant" value. Torbutton and other controllers
22281 can use this to avoid doing periodic requests through Tor while
22282 it's dormant (bug 4718). Fixes bug 5954.
22283 - Tell GCC and Clang to check for any errors in format strings passed
22284 to the tor_v*(print|scan)f functions.
22285 - Update to the May 1 2012 Maxmind GeoLite Country database.
22287 o Minor bugfixes (already included in 0.2.2.36):
22288 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
22289 Fixes bug 5346; bugfix on 0.0.8pre3.
22290 - Correct parsing of certain date types in parse_http_time().
22291 Without this patch, If-Modified-Since would behave
22292 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
22293 Esteban Manchado Velázques.
22294 - Make our number-parsing functions always treat too-large values
22295 as an error, even when those values exceed the width of the
22296 underlying type. Previously, if the caller provided these
22297 functions with minima or maxima set to the extreme values of the
22298 underlying integer type, these functions would return those
22299 values on overflow rather than treating overflow as an error.
22300 Fixes part of bug 5786; bugfix on 0.0.9.
22301 - If we hit the error case where routerlist_insert() replaces an
22302 existing (old) server descriptor, make sure to remove that
22303 server descriptor from the old_routers list. Fix related to bug
22304 1776. Bugfix on 0.2.2.18-alpha.
22305 - Clarify the behavior of MaxCircuitDirtiness with hidden service
22306 circuits. Fixes issue 5259.
22308 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
22309 - Prevent a null-pointer dereference when receiving a data cell
22310 for a nonexistent stream when the circuit in question has an
22311 empty deliver window. We don't believe this is triggerable,
22312 since we don't currently allow deliver windows to become empty,
22313 but the logic is tricky enough that it's better to make the code
22314 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
22315 - Fix a memory leak when trying to launch a DNS request when the
22316 network is disabled or the nameservers are unconfigurable. Fixes
22317 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
22318 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
22319 - Don't hold a Windows file handle open for every file mapping;
22320 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
22322 - Avoid O(n^2) performance characteristics when parsing a large
22323 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
22324 - Format more doubles with %f, not %lf. Patch from grarpamp to make
22325 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
22327 - Make our replacement implementation of strtok_r() compatible with
22328 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
22329 bugfix on 0.2.2.1-alpha.
22330 - Fix a NULL-pointer dereference on a badly formed
22331 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
22332 bugfix on 0.2.2.9-alpha.
22333 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
22334 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
22335 - Defensively refactor rend_mid_rendezvous() so that protocol
22336 violations and length checks happen in the beginning. Fixes
22338 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
22339 that IPv6 stuff will compile on MSVC, and compilation issues
22340 will be easier to track down. Fixes bug 5861.
22342 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
22343 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
22344 resource exhaustion, so that clients can adjust their load to
22345 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
22346 started using END_STREAM_REASON_RESOURCELIMIT.
22347 - Don't check for whether the address we're using for outbound
22348 connections has changed until after the outbound connection has
22349 completed. On Windows, getsockname() doesn't succeed until the
22350 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
22351 - If the configuration tries to set MyFamily on a bridge, refuse to
22352 do so, and warn about the security implications. Fixes bug 4657;
22353 bugfix on 0.2.0.3-alpha.
22354 - If the client fails to set a reasonable set of ciphersuites
22355 during its v2 handshake renegotiation, allow the renegotiation to
22356 continue nevertheless (i.e. send all the required certificates).
22357 Fixes bug 4591; bugfix on 0.2.0.20-rc.
22358 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
22359 option is set to 0 (which Vidalia version 0.2.16 now does when
22360 a SAVECONF attempt fails), perform other actions that SIGHUP
22361 usually causes (like reopening the logs). Fixes bug 5095; bugfix
22363 - If we fail to write a microdescriptor to the disk cache, do not
22364 continue replacing the old microdescriptor file. Fixes bug 2954;
22365 bugfix on 0.2.2.6-alpha.
22366 - Exit nodes don't need to fetch certificates for authorities that
22367 they don't recognize; only directory authorities, bridges,
22368 and caches need to do that. Fixes part of bug 2297; bugfix on
22370 - Correctly handle checking the permissions on the parent
22371 directory of a control socket in the root directory. Bug found
22372 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
22374 - When told to add a bridge with the same digest as a preexisting
22375 bridge but a different addr:port, change the addr:port as
22376 requested. Previously we would not notice the change. Fixes half
22377 of bug 5603; fix on 0.2.2.26-beta.
22378 - End AUTHCHALLENGE error messages (in the control protocol) with
22379 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
22381 o Minor bugfixes (on 0.2.3.x):
22382 - Turn an assertion (that the number of handshakes received as a
22383 server is not < 1) into a warning. Fixes bug 4873; bugfix on
22385 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
22386 we had reversed them when the answer was cached.) Fixes bug
22387 5723; bugfix on 0.2.3.1-alpha.
22388 - Work correctly on Linux systems with accept4 support advertised in
22389 their headers, but without accept4 support in the kernel. Fix
22390 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
22391 - When told to add a bridge with the same addr:port as a preexisting
22392 bridge but a different transport, change the transport as
22393 requested. Previously we would not notice the change. Fixes half
22394 of bug 5603; fix on 0.2.3.2-alpha.
22395 - Avoid a "double-reply" warning when replying to a SOCKS request
22396 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
22397 bugfix on 0.2.3.4-alpha.
22398 - Fix a bug where a bridge authority crashes if it has seen no
22399 directory requests when it's time to write statistics to disk.
22400 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
22402 - Don't try to open non-control listeners when DisableNetwork is set.
22403 Previously, we'd open all listeners, then immediately close them.
22404 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
22405 - Don't abort the managed proxy protocol if the managed proxy
22406 sends us an unrecognized line; ignore it instead. Fixes bug
22407 5910; bugfix on 0.2.3.9-alpha.
22408 - Fix a compile warning in crypto.c when compiling with clang 3.1.
22409 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
22410 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
22411 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
22412 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
22413 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
22414 - Resolve numerous small warnings and build issues with MSVC. Resolves
22417 o Documentation fixes:
22418 - Improve the manual's documentation for the NT Service command-line
22419 options. Addresses ticket 3964.
22420 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
22421 - Document the changes to the ORPort and DirPort options, and the
22422 fact that {OR/Dir}ListenAddress is now unnecessary (and
22423 therefore deprecated). Resolves ticket 5597.
22426 - Remove the torrc.bridge file: we don't use it for anything, and
22427 it had become badly desynchronized from torrc.sample. Resolves
22431 Changes in version 0.2.2.36 - 2012-05-24
22432 Tor 0.2.2.36 updates the addresses for two of the eight directory
22433 authorities, fixes some potential anonymity and security issues,
22434 and fixes several crash bugs.
22436 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
22437 known flaws, and nobody should be using them. You should upgrade. If
22438 you're using a Linux or BSD and its packages are obsolete, stop using
22439 those packages and upgrade anyway.
22441 o Directory authority changes:
22442 - Change IP address for maatuska (v3 directory authority).
22443 - Change IP address for ides (v3 directory authority), and rename
22447 - When building or running with any version of OpenSSL earlier
22448 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
22449 versions have a bug (CVE-2011-4576) in which their block cipher
22450 padding includes uninitialized data, potentially leaking sensitive
22451 information to any peer with whom they make a SSLv3 connection. Tor
22452 does not use SSL v3 by default, but a hostile client or server
22453 could force an SSLv3 connection in order to gain information that
22454 they shouldn't have been able to get. The best solution here is to
22455 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
22456 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
22457 to make sure that the bug can't happen.
22458 - Never use a bridge or a controller-supplied node as an exit, even
22459 if its exit policy allows it. Found by wanoskarnet. Fixes bug
22460 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
22461 and 0.2.0.3-alpha (for bridge-purpose descriptors).
22462 - Only build circuits if we have a sufficient threshold of the total
22463 descriptors that are marked in the consensus with the "Exit"
22464 flag. This mitigates an attack proposed by wanoskarnet, in which
22465 all of a client's bridges collude to restrict the exit nodes that
22466 the client knows about. Fixes bug 5343.
22467 - Provide controllers with a safer way to implement the cookie
22468 authentication mechanism. With the old method, if another locally
22469 running program could convince a controller that it was the Tor
22470 process, then that program could trick the controller into telling
22471 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
22472 authentication method uses a challenge-response approach to prevent
22473 this attack. Fixes bug 5185; implements proposal 193.
22476 - Avoid logging uninitialized data when unable to decode a hidden
22477 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
22478 - Avoid a client-side assertion failure when receiving an INTRODUCE2
22479 cell on a general purpose circuit. Fixes bug 5644; bugfix on
22481 - Fix builds when the path to sed, openssl, or sha1sum contains
22482 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
22484 - Correct our replacements for the timeradd() and timersub() functions
22485 on platforms that lack them (for example, Windows). The timersub()
22486 function is used when expiring circuits, while timeradd() is
22487 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
22488 bugfix on 0.2.2.24-alpha.
22489 - Fix the SOCKET_OK test that we use to tell when socket
22490 creation fails so that it works on Win64. Fixes part of bug 4533;
22491 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
22494 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
22495 Fixes bug 5346; bugfix on 0.0.8pre3.
22496 - Make our number-parsing functions always treat too-large values
22497 as an error, even when those values exceed the width of the
22498 underlying type. Previously, if the caller provided these
22499 functions with minima or maxima set to the extreme values of the
22500 underlying integer type, these functions would return those
22501 values on overflow rather than treating overflow as an error.
22502 Fixes part of bug 5786; bugfix on 0.0.9.
22503 - Older Linux kernels erroneously respond to strange nmap behavior
22504 by having accept() return successfully with a zero-length
22505 socket. When this happens, just close the connection. Previously,
22506 we would try harder to learn the remote address: but there was
22507 no such remote address to learn, and our method for trying to
22508 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
22509 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
22510 - Correct parsing of certain date types in parse_http_time().
22511 Without this patch, If-Modified-Since would behave
22512 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
22513 Esteban Manchado Velázques.
22514 - Change the BridgePassword feature (part of the "bridge community"
22515 design, which is not yet implemented) to use a time-independent
22516 comparison. The old behavior might have allowed an adversary
22517 to use timing to guess the BridgePassword value. Fixes bug 5543;
22518 bugfix on 0.2.0.14-alpha.
22519 - Detect and reject certain misformed escape sequences in
22520 configuration values. Previously, these values would cause us
22521 to crash if received in a torrc file or over an authenticated
22522 control port. Bug found by Esteban Manchado Velázquez, and
22523 independently by Robert Connolly from Matta Consulting who further
22524 noted that it allows a post-authentication heap overflow. Patch
22525 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
22526 bugfix on 0.2.0.16-alpha.
22527 - Fix a compile warning when using the --enable-openbsd-malloc
22528 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
22529 - During configure, detect when we're building with clang version
22530 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
22531 CFLAGS. clang doesn't support them yet.
22532 - When sending an HTTP/1.1 proxy request, include a Host header.
22533 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
22534 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
22535 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
22536 - If we hit the error case where routerlist_insert() replaces an
22537 existing (old) server descriptor, make sure to remove that
22538 server descriptor from the old_routers list. Fix related to bug
22539 1776. Bugfix on 0.2.2.18-alpha.
22541 o Minor bugfixes (documentation and log messages):
22542 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
22543 Fixes bug 4856; bugfix on Tor 0.0.6.
22544 - Update "ClientOnly" man page entry to explain that there isn't
22545 really any point to messing with it. Resolves ticket 5005.
22546 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
22547 directory authority option (introduced in Tor 0.2.2.34).
22548 - Downgrade the "We're missing a certificate" message from notice
22549 to info: people kept mistaking it for a real problem, whereas it
22550 is seldom the problem even when we are failing to bootstrap. Fixes
22551 bug 5067; bugfix on 0.2.0.10-alpha.
22552 - Correctly spell "connect" in a log message on failure to create a
22553 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
22554 - Clarify the behavior of MaxCircuitDirtiness with hidden service
22555 circuits. Fixes issue 5259.
22558 - Directory authorities now reject versions of Tor older than
22559 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
22560 inclusive. These versions accounted for only a small fraction of
22561 the Tor network, and have numerous known security issues. Resolves
22563 - Update to the May 1 2012 Maxmind GeoLite Country database.
22566 - When sending or relaying a RELAY_EARLY cell, we used to convert
22567 it to a RELAY cell if the connection was using the v1 link
22568 protocol. This was a workaround for older versions of Tor, which
22569 didn't handle RELAY_EARLY cells properly. Now that all supported
22570 versions can handle RELAY_EARLY cells, and now that we're enforcing
22571 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
22572 remove this workaround. Addresses bug 4786.
22575 Changes in version 0.2.3.15-alpha - 2012-04-30
22576 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
22577 the development branch build on Windows again.
22579 o Minor bugfixes (on 0.2.2.x and earlier):
22580 - Make sure that there are no unhandled pending TLS errors before
22581 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
22582 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
22583 Bugfix on 0.1.0.5-rc; fixes bug 4528.
22584 - Fix an assert that directory authorities could trigger on sighup
22585 during some configuration state transitions. We now don't treat
22586 it as a fatal error when the new descriptor we just generated in
22587 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
22588 - After we pick a directory mirror, we would refuse to use it if
22589 it's in our ExcludeExitNodes list, resulting in mysterious failures
22590 to bootstrap for people who just wanted to avoid exiting from
22591 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
22592 - When building with --enable-static-tor on OpenBSD, do not
22593 erroneously attempt to link -lrt. Fixes bug 5103.
22595 o Minor bugfixes (on 0.2.3.x):
22596 - When Tor is built with kernel headers from a recent (last few
22597 years) Linux kernel, do not fail to run on older (pre-2.6.28
22598 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
22599 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
22600 and 0.2.3.12-alpha.
22601 - Fix compilation with miniupnpc version 1.6; patch from
22602 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
22603 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
22604 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
22605 - Fix compilation on platforms without unistd.h, or where environ
22606 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
22609 - Directory authorities are now a little more lenient at accepting
22610 older router descriptors, or newer router descriptors that don't
22611 make big changes. This should help ameliorate past and future
22612 issues where routers think they have uploaded valid descriptors,
22613 but the authorities don't think so. Fix for ticket 2479.
22614 - Make the code that clients use to detect an address change be
22615 IPv6-aware, so that it won't fill clients' logs with error
22616 messages when trying to get the IPv4 address of an IPv6
22617 connection. Implements ticket 5537.
22619 o Removed features:
22620 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
22621 authorities needed to use it for a while to keep the network working
22622 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
22623 that was six months ago. As of now, it should no longer be needed
22627 Changes in version 0.2.3.14-alpha - 2012-04-23
22628 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
22629 candidate. It also dramatically speeds up AES: fast relays should
22630 consider switching to the newer OpenSSL library.
22632 o Directory authority changes:
22633 - Change IP address for ides (v3 directory authority), and rename
22637 - Avoid logging uninitialized data when unable to decode a hidden
22638 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
22639 - Avoid a client-side assertion failure when receiving an INTRODUCE2
22640 cell on a general purpose circuit. Fixes bug 5644; bugfix on
22642 - If authorities are unable to get a v2 consensus document from other
22643 directory authorities, they no longer fall back to fetching
22644 them from regular directory caches. Fixes bug 5635; bugfix on
22645 0.2.2.26-beta, where routers stopped downloading v2 consensus
22646 documents entirely.
22647 - When we start a Tor client with a normal consensus already cached,
22648 be willing to download a microdescriptor consensus. Fixes bug 4011;
22649 fix on 0.2.3.1-alpha.
22651 o Major features (performance):
22652 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
22653 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
22654 vectorized AES implementations as appropriate. These can be much,
22655 much faster than other AES implementations.
22657 o Minor bugfixes (0.2.2.x and earlier):
22658 - Don't launch more than 10 service-side introduction-point circuits
22659 for a hidden service in five minutes. Previously, we would consider
22660 launching more introduction-point circuits if at least one second
22661 had passed without any introduction-point circuits failing. Fixes
22662 bug 4607; bugfix on 0.0.7pre1.
22663 - Change the BridgePassword feature (part of the "bridge community"
22664 design, which is not yet implemented) to use a time-independent
22665 comparison. The old behavior might have allowed an adversary
22666 to use timing to guess the BridgePassword value. Fixes bug 5543;
22667 bugfix on 0.2.0.14-alpha.
22668 - Enforce correct return behavior of tor_vsscanf() when the '%%'
22669 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
22670 - When sending an HTTP/1.1 proxy request, include a Host header.
22671 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
22672 - Don't log that we have "decided to publish new relay descriptor"
22673 unless we are actually publishing a descriptor. Fixes bug 3942;
22674 bugfix on 0.2.2.28-beta.
22676 o Minor bugfixes (0.2.3.x):
22677 - Fix a bug where a bridge authority crashes (on a failed assert)
22678 if it has seen no directory requests when it's time to write
22679 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
22680 - Fix bug stomping on ORPort option NoListen and ignoring option
22681 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
22682 - In the testsuite, provide a large enough buffer in the tor_sscanf
22683 unit test. Otherwise we'd overrun that buffer and crash during
22684 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
22686 - Make sure we create the keys directory if it doesn't exist and we're
22687 about to store the dynamic Diffie-Hellman parameters. Fixes bug
22688 5572; bugfix on 0.2.3.13-alpha.
22689 - Fix a small memory leak when trying to decode incorrect base16
22690 authenticator during SAFECOOKIE authentication. Found by
22691 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
22694 - Add more information to a log statement that might help track down
22695 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
22696 non-IP address" messages (or any Bug messages, for that matter!),
22697 please let us know about it.
22698 - Relays now understand an IPv6 address when they get one from a
22699 directory server. Resolves ticket 4875.
22700 - Resolve IPv6 addresses in bridge and entry statistics to country
22701 code "??" which means we at least count them. Resolves ticket 5053;
22702 improves on 0.2.3.9-alpha.
22703 - Update to the April 3 2012 Maxmind GeoLite Country database.
22704 - Begin a doc/state-contents.txt file to explain the contents of
22705 the Tor state file. Fixes bug 2987.
22707 o Default torrc changes:
22708 - Stop listing "socksport 9050" in torrc.sample. We open a socks
22709 port on 9050 by default anyway, so this should not change anything
22711 - Stop mentioning the deprecated *ListenAddress options in
22712 torrc.sample. Fixes bug 5438.
22713 - Document unit of bandwidth related options in sample torrc.
22716 o Removed features:
22717 - The "torify" script no longer supports the "tsocks" socksifier
22718 tool, since tsocks doesn't support DNS and UDP right for Tor.
22719 Everyone should be using torsocks instead. Fixes bugs 3530 and
22720 5180. Based on a patch by "ugh".
22722 o Code refactoring:
22723 - Change the symmetric cipher interface so that creating and
22724 initializing a stream cipher are no longer separate functions.
22725 - Remove all internal support for unpadded RSA. We never used it, and
22726 it would be a bad idea to start.
22729 Changes in version 0.2.3.13-alpha - 2012-03-26
22730 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
22731 in managed pluggable transports, as well as providing other cleanups
22732 that get us closer to a release candidate.
22734 o Directory authority changes:
22735 - Change IP address for maatuska (v3 directory authority).
22738 - Provide controllers with a safer way to implement the cookie
22739 authentication mechanism. With the old method, if another locally
22740 running program could convince a controller that it was the Tor
22741 process, then that program could trick the controller into telling
22742 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
22743 authentication method uses a challenge-response approach to prevent
22744 this attack. Fixes bug 5185, implements proposal 193.
22745 - Never use a bridge or a controller-supplied node as an exit, even
22746 if its exit policy allows it. Found by wanoskarnet. Fixes bug
22747 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
22748 and 0.2.0.3-alpha (for bridge-purpose descriptors).
22749 - Only build circuits if we have a sufficient threshold of the total
22750 descriptors that are marked in the consensus with the "Exit"
22751 flag. This mitigates an attack proposed by wanoskarnet, in which
22752 all of a client's bridges collude to restrict the exit nodes that
22753 the client knows about. Fixes bug 5343.
22755 o Major bugfixes (on Tor 0.2.3.x):
22756 - Avoid an assert when managed proxies like obfsproxy are configured,
22757 and we receive HUP signals or setconf attempts too rapidly. This
22758 situation happens most commonly when Vidalia tries to attach to
22759 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
22760 bugfix on 0.2.3.6-alpha.
22761 - Fix a relay-side pluggable transports bug where managed proxies were
22762 unreachable from the Internet, because Tor asked them to bind on
22763 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
22764 - Stop discarding command-line arguments when TestingTorNetwork
22765 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
22766 0.2.3.9-alpha, where task 4552 added support for two layers of
22768 - Resume allowing the unit tests to run in gdb. This was accidentally
22769 made impossible when the DisableDebuggerAttachment option was
22770 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
22771 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
22772 0.2.3.11-alpha. Reported by Anthony G. Basile.
22774 o Minor bugfixes (on 0.2.2.x and earlier):
22775 - Ensure we don't cannibalize circuits that are longer than three hops
22776 already, so we don't end up making circuits with 5 or more
22777 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
22778 0.1.0.1-rc which introduced cannibalization.
22779 - Detect and reject certain misformed escape sequences in
22780 configuration values. Previously, these values would cause us
22781 to crash if received in a torrc file or over an authenticated
22782 control port. Bug found by Esteban Manchado Velázquez, and
22783 independently by Robert Connolly from Matta Consulting who further
22784 noted that it allows a post-authentication heap overflow. Patch
22785 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
22786 bugfix on 0.2.0.16-alpha.
22787 - Fix a compile warning when using the --enable-openbsd-malloc
22788 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
22789 - Directory caches no longer refuse to clean out descriptors because
22790 of missing v2 networkstatus documents, unless they're configured
22791 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
22792 0.2.2.26-beta. Patch by Daniel Bryg.
22793 - Update to the latest version of the tinytest unit testing framework.
22794 This includes a couple of bugfixes that can be relevant for
22795 running forked unit tests on Windows, and removes all reserved
22798 o Minor bugfixes (on 0.2.3.x):
22799 - On a failed pipe() call, don't leak file descriptors. Fixes bug
22800 4296; bugfix on 0.2.3.1-alpha.
22801 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
22802 until after we have received a CERTS cell. Fixes bug 4361; bugfix
22803 on 0.2.3.6-alpha. Patch by "frosty".
22804 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
22805 option, so that the IP stack doesn't decide to use it for IPv4
22806 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
22807 - Ensure that variables set in Tor's environment cannot override
22808 environment variables that Tor passes to a managed
22809 pluggable-transport proxy. Previously, Tor would pass every
22810 variable in its environment to managed proxies along with the new
22811 ones, in such a way that on many operating systems, the inherited
22812 environment variables would override those which Tor tried to
22813 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
22814 bugfix on 0.2.3.9-alpha for Windows.
22817 - A wide variety of new unit tests by Esteban Manchado Velázquez.
22818 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
22819 - Update to the March 6 2012 Maxmind GeoLite Country database.
22822 Changes in version 0.2.3.12-alpha - 2012-02-13
22823 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
22824 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
22825 when Tor is configured to use a pluggable transport like obfsproxy.
22828 - Fix builds when the path to sed, openssl, or sha1sum contains
22829 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
22831 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
22832 connections. This change should allow busy exit relays to stop
22833 running out of available sockets as quickly. Fixes bug 4950;
22834 bugfix on 0.2.2.26-beta.
22835 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
22836 would ask the bridge for microdescriptors, which are only supported
22837 in 0.2.3.x, and then fail to bootstrap when it didn't get the
22838 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
22839 - Properly set up obfsproxy's environment when in managed mode. The
22840 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
22841 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
22842 5076 and 5082; bugfix on 0.2.3.6-alpha.
22845 - Use the dead_strip option when building Tor on OS X. This reduces
22846 binary size by almost 19% when linking openssl and libevent
22847 statically, which we do for Tor Browser Bundle.
22848 - Fix broken URLs in the sample torrc file, and tell readers about
22849 the OutboundBindAddress, ExitPolicyRejectPrivate, and
22850 PublishServerDescriptor options. Addresses bug 4652.
22851 - Update to the February 7 2012 Maxmind GeoLite Country database.
22854 - Downgrade the "We're missing a certificate" message from notice
22855 to info: people kept mistaking it for a real problem, whereas it
22856 is seldom the problem even when we are failing to bootstrap. Fixes
22857 bug 5067; bugfix on 0.2.0.10-alpha.
22858 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
22859 managed pluggable transport server proxy's environment.
22860 Previously, we would put it there, even though Tor doesn't
22861 implement an 'extended server port' yet, and even though Tor
22862 almost certainly isn't listening at that address. For now, we set
22863 it to an empty string to avoid crashing older obfsproxies. Bugfix
22865 - Log the heartbeat message every HeartbeatPeriod seconds, not every
22866 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
22867 0.2.3.1-alpha. Bug reported by Scott Bennett.
22868 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
22869 bugfix on 0.2.3.11-alpha.
22870 - Update "ClientOnly" man page entry to explain that there isn't
22871 really any point to messing with it. Resolves ticket 5005.
22872 - Use the correct CVE number for CVE-2011-4576 in our comments and
22873 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
22876 o Code simplifications and refactoring:
22877 - Use the _WIN32 macro throughout our code to detect Windows.
22878 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
22882 Changes in version 0.2.3.11-alpha - 2012-01-22
22883 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
22884 the last step of the plan to limit maximum circuit length, includes
22885 a wide variety of hidden service performance and correctness fixes,
22886 works around an OpenSSL security flaw if your distro is too stubborn
22887 to upgrade, and fixes a bunch of smaller issues.
22890 - Now that Tor 0.2.0.x is completely deprecated, enable the final
22891 part of "Proposal 110: Avoiding infinite length circuits" by
22892 refusing all circuit-extend requests that do not use a relay_early
22893 cell. This change helps Tor resist a class of denial-of-service
22894 attacks by limiting the maximum circuit length.
22895 - Adjust the number of introduction points that a hidden service
22896 will try to maintain based on how long its introduction points
22897 remain in use and how many introductions they handle. Fixes
22899 - Try to use system facilities for enumerating local interface
22900 addresses, before falling back to our old approach (which was
22901 binding a UDP socket, and calling getsockname() on it). That
22902 approach was scaring OS X users whose draconian firewall
22903 software warned about binding to UDP sockets, regardless of
22904 whether packets were sent. Now we try to use getifaddrs(),
22905 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
22906 system supports. Resolves ticket 1827.
22908 o Major security workaround:
22909 - When building or running with any version of OpenSSL earlier
22910 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
22911 versions have a bug (CVE-2011-4576) in which their block cipher
22912 padding includes uninitialized data, potentially leaking sensitive
22913 information to any peer with whom they make a SSLv3 connection. Tor
22914 does not use SSL v3 by default, but a hostile client or server
22915 could force an SSLv3 connection in order to gain information that
22916 they shouldn't have been able to get. The best solution here is to
22917 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
22918 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
22919 to make sure that the bug can't happen.
22922 - Fix the SOCKET_OK test that we use to tell when socket
22923 creation fails so that it works on Win64. Fixes part of bug 4533;
22924 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
22925 - Correct our replacements for the timeradd() and timersub() functions
22926 on platforms that lack them (for example, Windows). The timersub()
22927 function is used when expiring circuits, while timeradd() is
22928 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
22929 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
22930 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
22931 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
22932 bug at runtime, not compile time, because some distributions hack
22933 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
22934 on 0.2.3.9-alpha. Found by Pascal.
22936 o Minor features (controller):
22937 - Use absolute path names when reporting the torrc filename in the
22938 control protocol, so a controller can more easily find the torrc
22939 file. Resolves bug 1101.
22940 - Extend the control protocol to report flags that control a circuit's
22941 path selection in CIRC events and in replies to 'GETINFO
22942 circuit-status'. Implements part of ticket 2411.
22943 - Extend the control protocol to report the hidden service address
22944 and current state of a hidden-service-related circuit in CIRC
22945 events and in replies to 'GETINFO circuit-status'. Implements part
22947 - When reporting the path to the cookie file to the controller,
22948 give an absolute path. Resolves ticket 4881.
22949 - Allow controllers to request an event notification whenever a
22950 circuit is cannibalized or its purpose is changed. Implements
22951 part of ticket 3457.
22952 - Include the creation time of a circuit in CIRC and CIRC2
22953 control-port events and the list produced by the 'GETINFO
22954 circuit-status' control-port command.
22956 o Minor features (directory authorities):
22957 - Directory authorities now reject versions of Tor older than
22958 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
22959 inclusive. These versions accounted for only a small fraction of
22960 the Tor network, and have numerous known security issues. Resolves
22962 - Authority operators can now vote for all relays in a given
22963 set of countries to be BadDir/BadExit/Invalid/Rejected.
22964 - Provide two consensus parameters (FastFlagMinThreshold and
22965 FastFlagMaxThreshold) to control the range of allowable bandwidths
22966 for the Fast directory flag. These allow authorities to run
22967 experiments on appropriate requirements for being a "Fast" node.
22968 The AuthDirFastGuarantee config value still applies. Implements
22970 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
22971 directory authority option (introduced in Tor 0.2.2.34).
22973 o Minor features (other):
22974 - Don't disable the DirPort when we cannot exceed our AccountingMax
22975 limit during this interval because the effective bandwidthrate is
22976 low enough. This is useful in a situation where AccountMax is only
22977 used as an additional safeguard or to provide statistics.
22978 - Prepend an informative header to generated dynamic_dh_params files.
22979 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
22980 EntryNodes will have no effect. Resolves issue 2571.
22981 - Log more useful messages when we fail to disable debugger
22983 - Log which authority we're missing votes from when we go to fetch
22984 them from the other auths.
22985 - Log (at debug level) whenever a circuit's purpose is changed.
22986 - Add missing documentation for the MaxClientCircuitsPending,
22987 UseMicrodescriptors, UserspaceIOCPBuffers, and
22988 _UseFilteringSSLBufferevents options, all introduced during
22989 the 0.2.3.x series.
22990 - Update to the January 3 2012 Maxmind GeoLite Country database.
22992 o Minor bugfixes (hidden services):
22993 - Don't close hidden service client circuits which have almost
22994 finished connecting to their destination when they reach
22995 the normal circuit-build timeout. Previously, we would close
22996 introduction circuits which are waiting for an acknowledgement
22997 from the introduction point, and rendezvous circuits which have
22998 been specified in an INTRODUCE1 cell sent to a hidden service,
22999 after the normal CBT. Now, we mark them as 'timed out', and launch
23000 another rendezvous attempt in parallel. This behavior change can
23001 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
23002 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
23003 - Don't close hidden-service-side rendezvous circuits when they
23004 reach the normal circuit-build timeout. This behavior change can
23005 be disabled using the new
23006 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
23007 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
23008 - Make sure we never mark the wrong rendezvous circuit as having
23009 had its introduction cell acknowledged by the introduction-point
23010 relay. Previously, when we received an INTRODUCE_ACK cell on a
23011 client-side hidden-service introduction circuit, we might have
23012 marked a rendezvous circuit other than the one we specified in
23013 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
23014 a warning message and interfered with the hidden service
23015 connection-establishment process. Fixes bug 4759; bugfix on
23016 0.2.3.3-alpha, when we added the stream-isolation feature which
23017 might cause Tor to open multiple rendezvous circuits for the same
23019 - Don't trigger an assertion failure when we mark a new client-side
23020 hidden-service introduction circuit for close during the process
23021 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
23024 o Minor bugfixes (log messages):
23025 - Correctly spell "connect" in a log message on failure to create a
23026 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
23028 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
23029 Fixes bug 4856; bugfix on Tor 0.0.6.
23030 - Fix the log message describing how we work around discovering
23031 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
23032 4837; bugfix on 0.2.2.9-alpha.
23033 - When logging about a disallowed .exit name, do not also call it
23034 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
23036 o Minor bugfixes (build fixes):
23037 - During configure, detect when we're building with clang version
23038 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
23039 CFLAGS. clang doesn't support them yet.
23040 - During configure, search for library containing cos function as
23041 libm lives in libcore on some platforms (BeOS/Haiku). Linking
23042 against libm was hard-coded before. Fixes the first part of bug
23043 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
23045 - Detect attempts to build Tor on (as yet hypothetical) versions
23046 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
23047 fix for bug 4533. Bugfix on 0.2.2.28-beta.
23048 - Preprocessor directives should not be put inside the arguments
23049 of a macro. This would break compilation with GCC releases prior
23050 to version 3.3. We would never recommend such an old GCC version,
23051 but it is apparently required for binary compatibility on some
23052 platforms (namely, certain builds of Haiku). Fixes the other part
23053 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
23056 o Minor bugfixes (other):
23057 - Older Linux kernels erroneously respond to strange nmap behavior
23058 by having accept() return successfully with a zero-length
23059 socket. When this happens, just close the connection. Previously,
23060 we would try harder to learn the remote address: but there was
23061 no such remote address to learn, and our method for trying to
23062 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
23063 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
23064 - Fix null-pointer access that could occur if TLS allocation failed.
23065 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
23066 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
23067 accidentally been reverted.
23068 - Fix our implementation of crypto_random_hostname() so it can't
23069 overflow on ridiculously large inputs. (No Tor version has ever
23070 provided this kind of bad inputs, but let's be correct in depth.)
23071 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
23072 - Find more places in the code that should have been testing for
23073 invalid sockets using the SOCKET_OK macro. Required for a fix
23074 for bug 4533. Bugfix on 0.2.2.28-beta.
23075 - Fix an assertion failure when, while running with bufferevents, a
23076 connection finishes connecting after it is marked for close, but
23077 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
23078 - test_util_spawn_background_ok() hardcoded the expected value
23079 for ENOENT to 2. This isn't portable as error numbers are
23080 platform specific, and particularly the hurd has ENOENT at
23081 0x40000002. Construct expected string at runtime, using the correct
23082 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
23083 - Reject attempts to disable DisableDebuggerAttachment while Tor is
23084 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
23085 - Use an appropriate-width type for sockets in tor-fw-helper on
23086 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
23089 - When sending or relaying a RELAY_EARLY cell, we used to convert
23090 it to a RELAY cell if the connection was using the v1 link
23091 protocol. This was a workaround for older versions of Tor, which
23092 didn't handle RELAY_EARLY cells properly. Now that all supported
23093 versions can handle RELAY_EARLY cells, and now that we're enforcing
23094 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
23095 remove this workaround. Addresses bug 4786.
23097 o Code simplifications and refactoring:
23098 - Use OpenSSL's built-in SSL_state_string_long() instead of our
23099 own homebrewed ssl_state_to_string() replacement. Patch from
23100 Emile Snyder. Fixes bug 4653.
23101 - Use macros to indicate OpenSSL versions, so we don't need to worry
23102 about accidental hexadecimal bit shifts.
23103 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
23105 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
23106 - Use the smartlist_add_asprintf() alias more consistently.
23107 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
23108 invalid value, rather than just -1.
23109 - Rename a handful of old identifiers, mostly related to crypto
23110 structures and crypto functions. By convention, our "create an
23111 object" functions are called "type_new()", our "free an object"
23112 functions are called "type_free()", and our types indicate that
23113 they are types only with a final "_t". But a handful of older
23114 types and functions broke these rules, with function names like
23115 "type_create" or "subsystem_op_type", or with type names like
23119 Changes in version 0.2.3.10-alpha - 2011-12-16
23120 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
23121 Tor's buffers code. Absolutely everybody should upgrade.
23123 The bug relied on an incorrect calculation when making data continuous
23124 in one of our IO buffers, if the first chunk of the buffer was
23125 misaligned by just the wrong amount. The miscalculation would allow an
23126 attacker to overflow a piece of heap-allocated memory. To mount this
23127 attack, the attacker would need to either open a SOCKS connection to
23128 Tor's SocksPort (usually restricted to localhost), or target a Tor
23129 instance configured to make its connections through a SOCKS proxy
23130 (which Tor does not do by default).
23132 Good security practice requires that all heap-overflow bugs should be
23133 presumed to be exploitable until proven otherwise, so we are treating
23134 this as a potential code execution attack. Please upgrade immediately!
23135 This bug does not affect bufferevents-based builds of Tor. Special
23136 thanks to "Vektor" for reporting this issue to us!
23138 This release also contains a few minor bugfixes for issues discovered
23142 - Fix a heap overflow bug that could occur when trying to pull
23143 data into the first chunk of a buffer, when that chunk had
23144 already had some data drained from it. Fixes CVE-2011-2778;
23145 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23148 - If we can't attach streams to a rendezvous circuit when we
23149 finish connecting to a hidden service, clear the rendezvous
23150 circuit's stream-isolation state and try to attach streams
23151 again. Previously, we cleared rendezvous circuits' isolation
23152 state either too early (if they were freshly built) or not at all
23153 (if they had been built earlier and were cannibalized). Bugfix on
23154 0.2.3.3-alpha; fixes bug 4655.
23155 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
23156 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
23157 - Fix an assertion failure when a relay with accounting enabled
23158 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
23161 - Update to the December 6 2011 Maxmind GeoLite Country database.
23164 Changes in version 0.2.2.35 - 2011-12-16
23165 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
23166 buffers code. Absolutely everybody should upgrade.
23168 The bug relied on an incorrect calculation when making data continuous
23169 in one of our IO buffers, if the first chunk of the buffer was
23170 misaligned by just the wrong amount. The miscalculation would allow an
23171 attacker to overflow a piece of heap-allocated memory. To mount this
23172 attack, the attacker would need to either open a SOCKS connection to
23173 Tor's SocksPort (usually restricted to localhost), or target a Tor
23174 instance configured to make its connections through a SOCKS proxy
23175 (which Tor does not do by default).
23177 Good security practice requires that all heap-overflow bugs should be
23178 presumed to be exploitable until proven otherwise, so we are treating
23179 this as a potential code execution attack. Please upgrade immediately!
23180 This bug does not affect bufferevents-based builds of Tor. Special
23181 thanks to "Vektor" for reporting this issue to us!
23183 Tor 0.2.2.35 also fixes several bugs in previous versions, including
23184 crash bugs for unusual configurations, and a long-term bug that
23185 would prevent Tor from starting on Windows machines with draconian
23188 With this release, we remind everyone that 0.2.0.x has reached its
23189 formal end-of-life. Those Tor versions have many known flaws, and
23190 nobody should be using them. You should upgrade -- ideally to the
23191 0.2.2.x series. If you're using a Linux or BSD and its packages are
23192 obsolete, stop using those packages and upgrade anyway.
23194 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
23195 longer receive support after some time in early 2012.
23198 - Fix a heap overflow bug that could occur when trying to pull
23199 data into the first chunk of a buffer, when that chunk had
23200 already had some data drained from it. Fixes CVE-2011-2778;
23201 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23202 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
23203 that it doesn't attempt to allocate a socketpair. This could cause
23204 some problems on Windows systems with overzealous firewalls. Fix for
23205 bug 4457; workaround for Libevent versions 2.0.1-alpha through
23207 - If we mark an OR connection for close based on a cell we process,
23208 don't process any further cells on it. We already avoid further
23209 reads on marked-for-close connections, but now we also discard the
23210 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
23211 which was the first version where we might mark a connection for
23212 close based on processing a cell on it.
23213 - Correctly sanity-check that we don't underflow on a memory
23214 allocation (and then assert) for hidden service introduction
23215 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23216 bugfix on 0.2.1.5-alpha.
23217 - Fix a memory leak when we check whether a hidden service
23218 descriptor has any usable introduction points left. Fixes bug
23219 4424. Bugfix on 0.2.2.25-alpha.
23220 - Don't crash when we're running as a relay and don't have a GeoIP
23221 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
23222 we've had in the 0.2.3.x branch already.
23223 - When running as a client, do not print a misleading (and plain
23224 wrong) log message that we're collecting "directory request"
23225 statistics: clients don't collect statistics. Also don't create a
23226 useless (because empty) stats file in the stats/ directory. Fixes
23227 bug 4353; bugfix on 0.2.2.34.
23230 - Detect failure to initialize Libevent. This fix provides better
23231 detection for future instances of bug 4457.
23232 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
23233 function. This was eating up hideously large amounts of time on some
23234 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
23235 - Resolve an integer overflow bug in smartlist_ensure_capacity().
23236 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
23238 - Don't warn about unused log_mutex in log.c when building with
23239 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
23240 0.1.0.6-rc which introduced --disable-threads.
23241 - When configuring, starting, or stopping an NT service, stop
23242 immediately after the service configuration attempt has succeeded
23243 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
23244 - When sending a NETINFO cell, include the original address
23245 received for the other side, not its canonical address. Found
23246 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
23247 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
23248 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
23249 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
23250 occurred when a client tried to fetch a descriptor for a bridge
23251 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
23252 - Backport fixes for a pair of compilation warnings on Windows.
23253 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
23254 - If we had ever tried to call tor_addr_to_str on an address of
23255 unknown type, we would have done a strdup on an uninitialized
23256 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
23257 Reported by "troll_un".
23258 - Correctly detect and handle transient lookup failures from
23259 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
23260 Reported by "troll_un".
23261 - Fix null-pointer access that could occur if TLS allocation failed.
23262 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
23263 - Use tor_socket_t type for listener argument to accept(). Fixes bug
23264 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
23267 - Add two new config options for directory authorities:
23268 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
23269 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
23270 that is always sufficient to satisfy the bandwidth requirement for
23271 the Guard flag. Now it will be easier for researchers to simulate
23272 Tor networks with different values. Resolves ticket 4484.
23273 - When Tor ignores a hidden service specified in its configuration,
23274 include the hidden service's directory in the warning message.
23275 Previously, we would only tell the user that some hidden service
23276 was ignored. Bugfix on 0.0.6; fixes bug 4426.
23277 - Update to the December 6 2011 Maxmind GeoLite Country database.
23279 o Packaging changes:
23280 - Make it easier to automate expert package builds on Windows,
23281 by removing an absolute path from makensis.exe command.
23284 Changes in version 0.2.1.32 - 2011-12-16
23285 Tor 0.2.1.32 backports important security and privacy fixes for
23286 oldstable. This release is intended only for package maintainers and
23287 others who cannot use the 0.2.2 stable series. All others should be
23288 using Tor 0.2.2.x or newer.
23290 The Tor 0.2.1.x series will reach formal end-of-life some time in
23291 early 2012; we will stop releasing patches for it then.
23293 o Major bugfixes (also included in 0.2.2.x):
23294 - Correctly sanity-check that we don't underflow on a memory
23295 allocation (and then assert) for hidden service introduction
23296 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23297 bugfix on 0.2.1.5-alpha.
23298 - Fix a heap overflow bug that could occur when trying to pull
23299 data into the first chunk of a buffer, when that chunk had
23300 already had some data drained from it. Fixes CVE-2011-2778;
23301 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
23304 - Update to the December 6 2011 Maxmind GeoLite Country database.
23307 Changes in version 0.2.3.9-alpha - 2011-12-08
23308 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
23309 a "DisableNetwork" security feature that bundles can use to avoid
23310 touching the network until bridges are configured, moves forward on
23311 the pluggable transport design, fixes a flaw in the hidden service
23312 design that unnecessarily prevented clients with wrong clocks from
23313 reaching hidden services, and fixes a wide variety of other issues.
23316 - Clients can now connect to private bridges over IPv6. Bridges
23317 still need at least one IPv4 address in order to connect to
23318 other relays. Note that we don't yet handle the case where the
23319 user has two bridge lines for the same bridge (one IPv4, one
23320 IPv6). Implements parts of proposal 186.
23321 - New "DisableNetwork" config option to prevent Tor from launching any
23322 connections or accepting any connections except on a control port.
23323 Bundles and controllers can set this option before letting Tor talk
23324 to the rest of the network, for example to prevent any connections
23325 to a non-bridge address. Packages like Orbot can also use this
23326 option to instruct Tor to save power when the network is off.
23327 - Clients and bridges can now be configured to use a separate
23328 "transport" proxy. This approach makes the censorship arms race
23329 easier by allowing bridges to use protocol obfuscation plugins. It
23330 implements the "managed proxy" part of proposal 180 (ticket 3472).
23331 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
23332 implementation. It makes AES_CTR about 7% faster than our old one
23333 (which was about 10% faster than the one OpenSSL used to provide).
23334 Resolves ticket 4526.
23335 - Add a "tor2web mode" for clients that want to connect to hidden
23336 services non-anonymously (and possibly more quickly). As a safety
23337 measure to try to keep users from turning this on without knowing
23338 what they are doing, tor2web mode must be explicitly enabled at
23339 compile time, and a copy of Tor compiled to run in tor2web mode
23340 cannot be used as a normal Tor client. Implements feature 2553.
23341 - Add experimental support for running on Windows with IOCP and no
23342 kernel-space socket buffers. This feature is controlled by a new
23343 "UserspaceIOCPBuffers" config option (off by default), which has
23344 no effect unless Tor has been built with support for bufferevents,
23345 is running on Windows, and has enabled IOCP. This may, in the long
23346 run, help solve or mitigate bug 98.
23347 - Use a more secure consensus parameter voting algorithm. Now at
23348 least three directory authorities or a majority of them must
23349 vote on a given parameter before it will be included in the
23350 consensus. Implements proposal 178.
23353 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
23354 They used to check that the timestamp was within 30 minutes
23355 of their system clock, so they could cap the size of their
23356 replay-detection cache, but that approach unnecessarily refused
23357 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
23358 the v3 intro-point protocol (the first one which sent a timestamp
23359 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
23360 - Only use the EVP interface when AES acceleration is enabled,
23361 to avoid a 5-7% performance regression. Resolves issue 4525;
23362 bugfix on 0.2.3.8-alpha.
23364 o Privacy/anonymity features (bridge detection):
23365 - Make bridge SSL certificates a bit more stealthy by using random
23366 serial numbers, in the same fashion as OpenSSL when generating
23367 self-signed certificates. Implements ticket 4584.
23368 - Introduce a new config option "DynamicDHGroups", enabled by
23369 default, which provides each bridge with a unique prime DH modulus
23370 to be used during SSL handshakes. This option attempts to help
23371 against censors who might use the Apache DH modulus as a static
23372 identifier for bridges. Addresses ticket 4548.
23374 o Minor features (new/different config options):
23375 - New configuration option "DisableDebuggerAttachment" (on by default)
23376 to prevent basic debugging attachment attempts by other processes.
23377 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
23378 - Allow MapAddress directives to specify matches against super-domains,
23379 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
23380 Implements issue 933.
23381 - Slightly change behavior of "list" options (that is, config
23382 options that can appear more than once) when they appear both in
23383 torrc and on the command line. Previously, the command-line options
23384 would be appended to the ones from torrc. Now, the command-line
23385 options override the torrc options entirely. This new behavior
23386 allows the user to override list options (like exit policies and
23387 ports to listen on) from the command line, rather than simply
23388 appending to the list.
23389 - You can get the old (appending) command-line behavior for "list"
23390 options by prefixing the option name with a "+".
23391 - You can remove all the values for a "list" option from the command
23392 line without adding any new ones by prefixing the option name
23394 - Add experimental support for a "defaults" torrc file to be parsed
23395 before the regular torrc. Torrc options override the defaults file's
23396 options in the same way that the command line overrides the torrc.
23397 The SAVECONF controller command saves only those options which
23398 differ between the current configuration and the defaults file. HUP
23399 reloads both files. (Note: This is an experimental feature; its
23400 behavior will probably be refined in future 0.2.3.x-alpha versions
23401 to better meet packagers' needs.) Implements task 4552.
23404 - Try to make the introductory warning message that Tor prints on
23405 startup more useful for actually finding help and information.
23406 Resolves ticket 2474.
23407 - Running "make version" now displays the version of Tor that
23408 we're about to build. Idea from katmagic; resolves issue 4400.
23409 - Expire old or over-used hidden service introduction points.
23410 Required by fix for bug 3460.
23411 - Move the replay-detection cache for the RSA-encrypted parts of
23412 INTRODUCE2 cells to the introduction point data structures.
23413 Previously, we would use one replay-detection cache per hidden
23414 service. Required by fix for bug 3460.
23415 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
23416 public key replay-detection cache from 60 minutes to 5 minutes. This
23417 replay-detection cache is now used only to detect multiple
23418 INTRODUCE2 cells specifying the same rendezvous point, so we can
23419 avoid launching multiple simultaneous attempts to connect to it.
23421 o Minor bugfixes (on Tor 0.2.2.x and earlier):
23422 - Resolve an integer overflow bug in smartlist_ensure_capacity().
23423 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
23425 - Fix a minor formatting issue in one of tor-gencert's error messages.
23427 - Prevent a false positive from the check-spaces script, by disabling
23428 the "whitespace between function name and (" check for functions
23430 - Fix a log message suggesting that people contact a non-existent
23431 email address. Fixes bug 3448.
23432 - Fix null-pointer access that could occur if TLS allocation failed.
23433 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
23434 - Report a real bootstrap problem to the controller on router
23435 identity mismatch. Previously we just said "foo", which probably
23436 made a lot of sense at the time. Fixes bug 4169; bugfix on
23438 - If we had ever tried to call tor_addr_to_str() on an address of
23439 unknown type, we would have done a strdup() on an uninitialized
23440 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
23441 Reported by "troll_un".
23442 - Correctly detect and handle transient lookup failures from
23443 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
23444 Reported by "troll_un".
23445 - Use tor_socket_t type for listener argument to accept(). Fixes bug
23446 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
23447 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
23448 bug 4532; found by "troll_un".
23450 o Minor bugfixes (on Tor 0.2.3.x):
23451 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
23453 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
23454 circuit for use as a hidden service client's rendezvous point.
23455 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
23456 with help from wanoskarnet.
23457 - Restore behavior of overriding SocksPort, ORPort, and similar
23458 options from the command line. Bugfix on 0.2.3.3-alpha.
23461 - Properly handle the case where the build-tree is not the same
23462 as the source tree when generating src/common/common_sha1.i,
23463 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
23464 bugfix on 0.2.0.1-alpha.
23466 o Code simplifications, cleanups, and refactorings:
23467 - Remove the pure attribute from all functions that used it
23468 previously. In many cases we assigned it incorrectly, because the
23469 functions might assert or call impure functions, and we don't have
23470 evidence that keeping the pure attribute is worthwhile. Implements
23471 changes suggested in ticket 4421.
23472 - Remove some dead code spotted by coverity. Fixes cid 432.
23473 Bugfix on 0.2.3.1-alpha, closes bug 4637.
23476 Changes in version 0.2.3.8-alpha - 2011-11-22
23477 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
23478 socketpair-related bug that has been bothering Windows users. It adds
23479 support to serve microdescriptors to controllers, so Vidalia's network
23480 map can resume listing relays (once Vidalia implements its side),
23481 and adds better support for hardware AES acceleration. Finally, it
23482 starts the process of adjusting the bandwidth cutoff for getting the
23483 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
23484 that tiny relays harm performance more than they help network capacity.
23487 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
23488 that it doesn't attempt to allocate a socketpair. This could cause
23489 some problems on Windows systems with overzealous firewalls. Fix for
23490 bug 4457; workaround for Libevent versions 2.0.1-alpha through
23492 - Correctly sanity-check that we don't underflow on a memory
23493 allocation (and then assert) for hidden service introduction
23494 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
23495 bugfix on 0.2.1.5-alpha.
23496 - Remove the artificially low cutoff of 20KB to guarantee the Fast
23497 flag. In the past few years the average relay speed has picked
23498 up, and while the "top 7/8 of the network get the Fast flag" and
23499 "all relays with 20KB or more of capacity get the Fast flag" rules
23500 used to have the same result, now the top 7/8 of the network has
23501 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
23502 - Fix a rare assertion failure when checking whether a v0 hidden
23503 service descriptor has any usable introduction points left, and
23504 we don't have enough information to build a circuit to the first
23505 intro point named in the descriptor. The HS client code in
23506 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
23507 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
23508 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
23509 - Make bridge authorities not crash when they are asked for their own
23510 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
23511 - When running as a client, do not print a misleading (and plain
23512 wrong) log message that we're collecting "directory request"
23513 statistics: clients don't collect statistics. Also don't create a
23514 useless (because empty) stats file in the stats/ directory. Fixes
23515 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
23518 - Allow Tor controllers like Vidalia to obtain the microdescriptor
23519 for a relay by identity digest or nickname. Previously,
23520 microdescriptors were only available by their own digests, so a
23521 controller would have to ask for and parse the whole microdescriptor
23522 consensus in order to look up a single relay's microdesc. Fixes
23523 bug 3832; bugfix on 0.2.3.1-alpha.
23524 - Use OpenSSL's EVP interface for AES encryption, so that all AES
23525 operations can use hardware acceleration (if present). Resolves
23528 o Minor bugfixes (on 0.2.2.x and earlier):
23529 - Detect failure to initialize Libevent. This fix provides better
23530 detection for future instances of bug 4457.
23531 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
23532 function. This was eating up hideously large amounts of time on some
23533 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
23534 - Don't warn about unused log_mutex in log.c when building with
23535 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
23536 0.1.0.6-rc which introduced --disable-threads.
23537 - Allow manual 'authenticate' commands to the controller interface
23538 from netcat (nc) as well as telnet. We were rejecting them because
23539 they didn't come with the expected whitespace at the end of the
23540 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
23541 - Fix some (not actually triggerable) buffer size checks in usage of
23542 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
23544 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
23545 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
23546 - When configuring, starting, or stopping an NT service, stop
23547 immediately after the service configuration attempt has succeeded
23548 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
23549 - When sending a NETINFO cell, include the original address
23550 received for the other side, not its canonical address. Found
23551 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
23552 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
23553 can pick them up when the tests aren't disabled. Bugfix on
23554 0.2.2.4-alpha which introduced tinytest.
23555 - Fix a memory leak when we check whether a hidden service
23556 descriptor has any usable introduction points left. Fixes bug
23557 4424. Bugfix on 0.2.2.25-alpha.
23558 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
23559 occurred when a client tried to fetch a descriptor for a bridge
23560 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
23562 o Minor bugfixes (on 0.2.3.x):
23563 - Make util unit tests build correctly with MSVC. Bugfix on
23564 0.2.3.3-alpha. Patch by Gisle Vanem.
23565 - Successfully detect AUTH_CHALLENGE cells with no recognized
23566 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
23567 Found by frosty_un.
23568 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
23569 it should still send a NETINFO cell to allow the connection to
23570 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
23572 - Log less loudly when we get an invalid authentication certificate
23573 from a source other than a directory authority: it's not unusual
23574 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
23576 - Tolerate servers with more clock skew in their authentication
23577 certificates than previously. Fixes bug 4371; bugfix on
23579 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
23580 on 0.2.3.4-alpha and 0.2.3.6-alpha.
23583 - Add two new config options for directory authorities:
23584 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
23585 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
23586 that is always sufficient to satisfy the bandwidth requirement for
23587 the Guard flag. Now it will be easier for researchers to simulate
23588 Tor networks with different values. Resolves ticket 4484.
23589 - When Tor ignores a hidden service specified in its configuration,
23590 include the hidden service's directory in the warning message.
23591 Previously, we would only tell the user that some hidden service
23592 was ignored. Bugfix on 0.0.6; fixes bug 4426.
23593 - When we fail to initialize Libevent, retry with IOCP disabled so we
23594 don't need to turn on multi-threading support in Libevent, which in
23595 turn requires a working socketpair(). This is a workaround for bug
23596 4457, which affects Libevent versions from 2.0.1-alpha through
23598 - Detect when we try to build on a platform that doesn't define
23599 AF_UNSPEC to 0. We don't work there, so refuse to compile.
23600 - Update to the November 1 2011 Maxmind GeoLite Country database.
23602 o Packaging changes:
23603 - Make it easier to automate expert package builds on Windows,
23604 by removing an absolute path from makensis.exe command.
23606 o Code simplifications and refactoring:
23607 - Remove some redundant #include directives throughout the code.
23608 Patch from Andrea Gelmini.
23609 - Unconditionally use OpenSSL's AES implementation instead of our
23610 old built-in one. OpenSSL's AES has been better for a while, and
23611 relatively few servers should still be on any version of OpenSSL
23612 that doesn't have good optimized assembly AES.
23613 - Use the name "CERTS" consistently to refer to the new cell type;
23614 we were calling it CERT in some places and CERTS in others.
23617 - Numerous new unit tests for functions in util.c and address.c by
23619 - The long-disabled benchmark tests are now split into their own
23620 ./src/test/bench binary.
23621 - The benchmark tests can now use more accurate timers than
23622 gettimeofday() when such timers are available.
23625 Changes in version 0.2.3.7-alpha - 2011-10-30
23626 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
23627 the new v3 handshake. It also resolves yet another bridge address
23631 - If we mark an OR connection for close based on a cell we process,
23632 don't process any further cells on it. We already avoid further
23633 reads on marked-for-close connections, but now we also discard the
23634 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
23635 which was the first version where we might mark a connection for
23636 close based on processing a cell on it.
23637 - Fix a double-free bug that would occur when we received an invalid
23638 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
23639 bugfix on 0.2.3.6-alpha.
23640 - Bridges no longer include their address in NETINFO cells on outgoing
23641 OR connections, to allow them to blend in better with clients.
23642 Removes another avenue for enumerating bridges. Reported by
23643 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
23644 cells were introduced.
23647 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
23648 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
23651 Changes in version 0.2.3.6-alpha - 2011-10-26
23652 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
23653 anonymity vulnerability where an attacker can deanonymize Tor
23654 users. Everybody should upgrade.
23656 This release also features support for a new v3 connection handshake
23657 protocol, and fixes to make hidden service connections more robust.
23660 - Implement a new handshake protocol (v3) for authenticating Tors to
23661 each other over TLS. It should be more resistant to fingerprinting
23662 than previous protocols, and should require less TLS hacking for
23663 future Tor implementations. Implements proposal 176.
23664 - Allow variable-length padding cells to disguise the length of
23665 Tor's TLS records. Implements part of proposal 184.
23667 o Privacy/anonymity fixes (clients):
23668 - Clients and bridges no longer send TLS certificate chains on
23669 outgoing OR connections. Previously, each client or bridge would
23670 use the same cert chain for all outgoing OR connections until
23671 its IP address changes, which allowed any relay that the client
23672 or bridge contacted to determine which entry guards it is using.
23673 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23674 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23675 no longer considers that connection as suitable for satisfying a
23676 circuit EXTEND request. Now relays can protect clients from the
23677 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23678 - Directory authorities no longer assign the Guard flag to relays
23679 that haven't upgraded to the above "refuse EXTEND requests
23680 to client connections" fix. Now directory authorities can
23681 protect clients from the CVE-2011-2768 issue even if neither
23682 the clients nor the relays have upgraded yet. There's a new
23683 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
23684 to let us transition smoothly, else tomorrow there would be no
23687 o Major bugfixes (hidden services):
23688 - Improve hidden service robustness: when an attempt to connect to
23689 a hidden service ends, be willing to refetch its hidden service
23690 descriptors from each of the HSDir relays responsible for them
23691 immediately. Previously, we would not consider refetching the
23692 service's descriptors from each HSDir for 15 minutes after the last
23693 fetch, which was inconvenient if the hidden service was not running
23694 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
23695 - When one of a hidden service's introduction points appears to be
23696 unreachable, stop trying it. Previously, we would keep trying
23697 to build circuits to the introduction point until we lost the
23698 descriptor, usually because the user gave up and restarted Tor.
23699 Partly fixes bug 3825.
23700 - Don't launch a useless circuit after failing to use one of a
23701 hidden service's introduction points. Previously, we would
23702 launch a new introduction circuit, but not set the hidden service
23703 which that circuit was intended to connect to, so it would never
23704 actually be used. A different piece of code would then create a
23705 new introduction circuit correctly. Bug reported by katmagic and
23706 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
23708 o Major bugfixes (other):
23709 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23710 that they initiated. Relays could distinguish incoming bridge
23711 connections from client connections, creating another avenue for
23712 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23713 Found by "frosty_un".
23714 - Don't update the AccountingSoftLimitHitAt state file entry whenever
23715 tor gets started. This prevents a wrong average bandwidth
23716 estimate, which would cause relays to always start a new accounting
23717 interval at the earliest possible moment. Fixes bug 2003; bugfix
23718 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
23719 immensely in tracking this bug down.
23720 - Fix a crash bug when changing node restrictions while a DNS lookup
23721 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
23724 o Minor bugfixes (on 0.2.2.x and earlier):
23725 - When a hidden service turns an extra service-side introduction
23726 circuit into a general-purpose circuit, free the rend_data and
23727 intro_key fields first, so we won't leak memory if the circuit
23728 is cannibalized for use as another service-side introduction
23729 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
23730 - Rephrase the log message emitted if the TestSocks check is
23731 successful. Patch from Fabian Keil; fixes bug 4094.
23732 - Bridges now skip DNS self-tests, to act a little more stealthily.
23733 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
23734 bridges. Patch by "warms0x".
23735 - Remove a confusing dollar sign from the example fingerprint in the
23736 man page, and also make the example fingerprint a valid one. Fixes
23737 bug 4309; bugfix on 0.2.1.3-alpha.
23738 - Fix internal bug-checking logic that was supposed to catch
23739 failures in digest generation so that it will fail more robustly
23740 if we ask for a nonexistent algorithm. Found by Coverity Scan.
23741 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
23742 - Report any failure in init_keys() calls launched because our
23743 IP address has changed. Spotted by Coverity Scan. Bugfix on
23744 0.1.1.4-alpha; fixes CID 484.
23746 o Minor bugfixes (on 0.2.3.x):
23747 - Fix a bug in configure.in that kept it from building a configure
23748 script with autoconf versions earlier than 2.61. Fixes bug 2430;
23749 bugfix on 0.2.3.1-alpha.
23750 - Don't warn users that they are exposing a client port to the
23751 Internet if they have specified an RFC1918 address. Previously,
23752 we would warn if the user had specified any non-loopback
23753 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
23754 - Fix memory leaks in the failing cases of the new SocksPort and
23755 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
23756 fixes coverity CIDs 485, 486, and 487.
23759 - When a hidden service's introduction point times out, consider
23760 trying it again during the next attempt to connect to the
23761 HS. Previously, we would not try it again unless a newly fetched
23762 descriptor contained it. Required by fixes for bugs 1297 and 3825.
23763 - The next version of Windows will be called Windows 8, and it has
23764 a major version of 6, minor version of 2. Correctly identify that
23765 version instead of calling it "Very recent version". Resolves
23766 ticket 4153; reported by funkstar.
23767 - The Bridge Authority now writes statistics on how many bridge
23768 descriptors it gave out in total, and how many unique descriptors
23769 it gave out. It also lists how often the most and least commonly
23770 fetched descriptors were given out, as well as the median and
23771 25th/75th percentile. Implements tickets 4200 and 4294.
23772 - Update to the October 4 2011 Maxmind GeoLite Country database.
23774 o Code simplifications and refactoring:
23775 - Remove some old code to remember statistics about which descriptors
23776 we've served as a directory mirror. The feature wasn't used and
23777 is outdated now that microdescriptors are around.
23778 - Rename Tor functions that turn strings into addresses, so that
23779 "parse" indicates that no hostname resolution occurs, and
23780 "lookup" indicates that hostname resolution may occur. This
23781 should help prevent mistakes in the future. Fixes bug 3512.
23784 Changes in version 0.2.2.34 - 2011-10-26
23785 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
23786 can deanonymize Tor users. Everybody should upgrade.
23788 The attack relies on four components: 1) Clients reuse their TLS cert
23789 when talking to different relays, so relays can recognize a user by
23790 the identity key in her cert. 2) An attacker who knows the client's
23791 identity key can probe each guard relay to see if that identity key
23792 is connected to that guard relay right now. 3) A variety of active
23793 attacks in the literature (starting from "Low-Cost Traffic Analysis
23794 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
23795 discover the guard relays that a Tor user visiting the website is using.
23796 4) Clients typically pick three guards at random, so the set of guards
23797 for a given user could well be a unique fingerprint for her. This
23798 release fixes components #1 and #2, which is enough to block the attack;
23799 the other two remain as open research problems. Special thanks to
23800 "frosty_un" for reporting the issue to us!
23802 Clients should upgrade so they are no longer recognizable by the TLS
23803 certs they present. Relays should upgrade so they no longer allow a
23804 remote attacker to probe them to test whether unpatched clients are
23805 currently connected to them.
23807 This release also fixes several vulnerabilities that allow an attacker
23808 to enumerate bridge relays. Some bridge enumeration attacks still
23809 remain; see for example proposal 188.
23811 o Privacy/anonymity fixes (clients):
23812 - Clients and bridges no longer send TLS certificate chains on
23813 outgoing OR connections. Previously, each client or bridge would
23814 use the same cert chain for all outgoing OR connections until
23815 its IP address changes, which allowed any relay that the client
23816 or bridge contacted to determine which entry guards it is using.
23817 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23818 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23819 no longer considers that connection as suitable for satisfying a
23820 circuit EXTEND request. Now relays can protect clients from the
23821 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23822 - Directory authorities no longer assign the Guard flag to relays
23823 that haven't upgraded to the above "refuse EXTEND requests
23824 to client connections" fix. Now directory authorities can
23825 protect clients from the CVE-2011-2768 issue even if neither
23826 the clients nor the relays have upgraded yet. There's a new
23827 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
23828 to let us transition smoothly, else tomorrow there would be no
23831 o Privacy/anonymity fixes (bridge enumeration):
23832 - Bridge relays now do their directory fetches inside Tor TLS
23833 connections, like all the other clients do, rather than connecting
23834 directly to the DirPort like public relays do. Removes another
23835 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
23836 - Bridges relays now build circuits for themselves in a more similar
23837 way to how clients build them. Removes another avenue for
23838 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
23839 when bridges were introduced.
23840 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23841 that they initiated. Relays could distinguish incoming bridge
23842 connections from client connections, creating another avenue for
23843 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23844 Found by "frosty_un".
23847 - Fix a crash bug when changing node restrictions while a DNS lookup
23848 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
23850 - Don't launch a useless circuit after failing to use one of a
23851 hidden service's introduction points. Previously, we would
23852 launch a new introduction circuit, but not set the hidden service
23853 which that circuit was intended to connect to, so it would never
23854 actually be used. A different piece of code would then create a
23855 new introduction circuit correctly. Bug reported by katmagic and
23856 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
23859 - Change an integer overflow check in the OpenBSD_Malloc code so
23860 that GCC is less likely to eliminate it as impossible. Patch
23861 from Mansour Moufid. Fixes bug 4059.
23862 - When a hidden service turns an extra service-side introduction
23863 circuit into a general-purpose circuit, free the rend_data and
23864 intro_key fields first, so we won't leak memory if the circuit
23865 is cannibalized for use as another service-side introduction
23866 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
23867 - Bridges now skip DNS self-tests, to act a little more stealthily.
23868 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
23869 bridges. Patch by "warms0x".
23870 - Fix internal bug-checking logic that was supposed to catch
23871 failures in digest generation so that it will fail more robustly
23872 if we ask for a nonexistent algorithm. Found by Coverity Scan.
23873 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
23874 - Report any failure in init_keys() calls launched because our
23875 IP address has changed. Spotted by Coverity Scan. Bugfix on
23876 0.1.1.4-alpha; fixes CID 484.
23878 o Minor bugfixes (log messages and documentation):
23879 - Remove a confusing dollar sign from the example fingerprint in the
23880 man page, and also make the example fingerprint a valid one. Fixes
23881 bug 4309; bugfix on 0.2.1.3-alpha.
23882 - The next version of Windows will be called Windows 8, and it has
23883 a major version of 6, minor version of 2. Correctly identify that
23884 version instead of calling it "Very recent version". Resolves
23885 ticket 4153; reported by funkstar.
23886 - Downgrade log messages about circuit timeout calibration from
23887 "notice" to "info": they don't require or suggest any human
23888 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
23889 bugfix on 0.2.2.14-alpha.
23892 - Turn on directory request statistics by default and include them in
23893 extra-info descriptors. Don't break if we have no GeoIP database.
23894 Backported from 0.2.3.1-alpha; implements ticket 3951.
23895 - Update to the October 4 2011 Maxmind GeoLite Country database.
23898 Changes in version 0.2.1.31 - 2011-10-26
23899 Tor 0.2.1.31 backports important security and privacy fixes for
23900 oldstable. This release is intended only for package maintainers and
23901 others who cannot use the 0.2.2 stable series. All others should be
23902 using Tor 0.2.2.x or newer.
23904 o Security fixes (also included in 0.2.2.x):
23905 - Replace all potentially sensitive memory comparison operations
23906 with versions whose runtime does not depend on the data being
23907 compared. This will help resist a class of attacks where an
23908 adversary can use variations in timing information to learn
23909 sensitive data. Fix for one case of bug 3122. (Safe memcmp
23910 implementation by Robert Ransom based partially on code by DJB.)
23911 - Fix an assert in parsing router descriptors containing IPv6
23912 addresses. This one took down the directory authorities when
23913 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
23915 o Privacy/anonymity fixes (also included in 0.2.2.x):
23916 - Clients and bridges no longer send TLS certificate chains on
23917 outgoing OR connections. Previously, each client or bridge would
23918 use the same cert chain for all outgoing OR connections until
23919 its IP address changes, which allowed any relay that the client
23920 or bridge contacted to determine which entry guards it is using.
23921 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
23922 - If a relay receives a CREATE_FAST cell on a TLS connection, it
23923 no longer considers that connection as suitable for satisfying a
23924 circuit EXTEND request. Now relays can protect clients from the
23925 CVE-2011-2768 issue even if the clients haven't upgraded yet.
23926 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
23927 that they initiated. Relays could distinguish incoming bridge
23928 connections from client connections, creating another avenue for
23929 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
23930 Found by "frosty_un".
23931 - When receiving a hidden service descriptor, check that it is for
23932 the hidden service we wanted. Previously, Tor would store any
23933 hidden service descriptors that a directory gave it, whether it
23934 wanted them or not. This wouldn't have let an attacker impersonate
23935 a hidden service, but it did let directories pre-seed a client
23936 with descriptors that it didn't want. Bugfix on 0.0.6.
23937 - Avoid linkability based on cached hidden service descriptors: forget
23938 all hidden service descriptors cached as a client when processing a
23939 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
23940 - Make the bridge directory authority refuse to answer directory
23941 requests for "all" descriptors. It used to include bridge
23942 descriptors in its answer, which was a major information leak.
23943 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
23944 - Don't attach new streams to old rendezvous circuits after SIGNAL
23945 NEWNYM. Previously, we would keep using an existing rendezvous
23946 circuit if it remained open (i.e. if it were kept open by a
23947 long-lived stream, or if a new stream were attached to it before
23948 Tor could notice that it was old and no longer in use). Bugfix on
23949 0.1.1.15-rc; fixes bug 3375.
23951 o Minor bugfixes (also included in 0.2.2.x):
23952 - When we restart our relay, we might get a successful connection
23953 from the outside before we've started our reachability tests,
23954 triggering a warning: "ORPort found reachable, but I have no
23955 routerinfo yet. Failing to inform controller of success." This
23956 bug was harmless unless Tor is running under a controller
23957 like Vidalia, in which case the controller would never get a
23958 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
23960 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
23961 enabled. Fixes bug 1526.
23962 - Remove undocumented option "-F" from tor-resolve: it hasn't done
23963 anything since 0.2.1.16-rc.
23964 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
23965 None of the cases where we did this before were wrong, but by making
23966 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
23967 - Fix a rare crash bug that could occur when a client was configured
23968 with a large number of bridges. Fixes bug 2629; bugfix on
23969 0.2.1.2-alpha. Bugfix by trac user "shitlei".
23970 - Correct the warning displayed when a rendezvous descriptor exceeds
23971 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
23973 - Fix an uncommon assertion failure when running with DNSPort under
23974 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
23975 - When warning about missing zlib development packages during compile,
23976 give the correct package names. Bugfix on 0.2.0.1-alpha.
23977 - Require that introduction point keys and onion keys have public
23978 exponent 65537. Bugfix on 0.2.0.10-alpha.
23979 - Do not crash when our configuration file becomes unreadable, for
23980 example due to a permissions change, between when we start up
23981 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
23983 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
23985 - Always NUL-terminate the sun_path field of a sockaddr_un before
23986 passing it to the kernel. (Not a security issue: kernels are
23987 smart enough to reject bad sockaddr_uns.) Found by Coverity;
23988 CID #428. Bugfix on Tor 0.2.0.3-alpha.
23989 - Don't stack-allocate the list of supplementary GIDs when we're
23990 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
23991 could take up to 256K, which is way too much stack. Found by
23992 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
23994 o Minor bugfixes (only in 0.2.1.x):
23995 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
23996 rely on them. Bugfix on 0.2.1.30.
23997 - Use git revisions instead of svn revisions when generating our
23998 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
24000 o Minor features (also included in 0.2.2.x):
24001 - Adjust the expiration time on our SSL session certificates to
24002 better match SSL certs seen in the wild. Resolves ticket 4014.
24003 - Allow nameservers with IPv6 address. Resolves bug 2574.
24004 - Update to the October 4 2011 Maxmind GeoLite Country database.
24007 Changes in version 0.2.3.5-alpha - 2011-09-28
24008 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
24009 bridge relays; fixes an assertion error that many users started hitting
24010 today; and adds the ability to refill token buckets more often than
24011 once per second, allowing significant performance improvements.
24014 - Bridge relays now do their directory fetches inside Tor TLS
24015 connections, like all the other clients do, rather than connecting
24016 directly to the DirPort like public relays do. Removes another
24017 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
24018 - Bridges relays now build circuits for themselves in a more similar
24019 way to how clients build them. Removes another avenue for
24020 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
24021 when bridges were introduced.
24024 - Fix an "Assertion md->held_by_node == 1 failed" error that could
24025 occur when the same microdescriptor was referenced by two node_t
24026 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
24028 o Major features (networking):
24029 - Add a new TokenBucketRefillInterval option to refill token buckets
24030 more frequently than once per second. This should improve network
24031 performance, alleviate queueing problems, and make traffic less
24032 bursty. Implements proposal 183; closes ticket 3630. Design by
24033 Florian Tschorsch and Björn Scheuermann; implementation by
24037 - Change an integer overflow check in the OpenBSD_Malloc code so
24038 that GCC is less likely to eliminate it as impossible. Patch
24039 from Mansour Moufid. Fixes bug 4059.
24041 o Minor bugfixes (usability):
24042 - Downgrade log messages about circuit timeout calibration from
24043 "notice" to "info": they don't require or suggest any human
24044 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
24045 bugfix on 0.2.2.14-alpha.
24047 o Minor features (diagnostics):
24048 - When the system call to create a listener socket fails, log the
24049 error message explaining why. This may help diagnose bug 4027.
24052 Changes in version 0.2.3.4-alpha - 2011-09-13
24053 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
24054 tweak to Tor's TLS handshake that makes relays and bridges that run
24055 this new version reachable from Iran again. It also fixes a few new
24056 bugs in 0.2.3.x, and teaches relays to recognize when they're not
24057 listed in the network consensus and republish.
24059 o Major bugfixes (also part of 0.2.2.33):
24060 - Avoid an assertion failure when reloading a configuration with
24061 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
24062 3923; bugfix on 0.2.2.25-alpha.
24064 o Minor features (security, also part of 0.2.2.33):
24065 - Check for replays of the public-key encrypted portion of an
24066 INTRODUCE1 cell, in addition to the current check for replays of
24067 the g^x value. This prevents a possible class of active attacks
24068 by an attacker who controls both an introduction point and a
24069 rendezvous point, and who uses the malleability of AES-CTR to
24070 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
24071 that these attacks are infeasible (requiring the attacker to send
24072 on the order of zettabytes of altered cells in a short interval),
24073 but we'd rather block them off in case there are any classes of
24074 this attack that we missed. Reported by Willem Pinckaers.
24076 o Minor features (also part of 0.2.2.33):
24077 - Adjust the expiration time on our SSL session certificates to
24078 better match SSL certs seen in the wild. Resolves ticket 4014.
24079 - Change the default required uptime for a relay to be accepted as
24080 a HSDir (hidden service directory) from 24 hours to 25 hours.
24081 Improves on 0.2.0.10-alpha; resolves ticket 2649.
24082 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
24083 authorities to abstain from voting on assignment of the HSDir
24084 consensus flag. Related to bug 2649.
24085 - Update to the September 6 2011 Maxmind GeoLite Country database.
24087 o Minor bugfixes (also part of 0.2.2.33):
24088 - Demote the 'replay detected' log message emitted when a hidden
24089 service receives the same Diffie-Hellman public key in two different
24090 INTRODUCE2 cells to info level. A normal Tor client can cause that
24091 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
24092 fixes part of bug 2442.
24093 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
24094 level. There is nothing that a hidden service's operator can do
24095 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
24097 - Clarify a log message specifying the characters permitted in
24098 HiddenServiceAuthorizeClient client names. Previously, the log
24099 message said that "[A-Za-z0-9+-_]" were permitted; that could have
24100 given the impression that every ASCII character between "+" and "_"
24101 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
24103 o Build fixes (also part of 0.2.2.33):
24104 - Clean up some code issues that prevented Tor from building on older
24105 BSDs. Fixes bug 3894; reported by "grarpamp".
24106 - Search for a platform-specific version of "ar" when cross-compiling.
24107 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
24110 - Fix a bug where the SocksPort option (for example) would get
24111 ignored and replaced by the default if a SocksListenAddress
24112 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
24116 - Relays now try regenerating and uploading their descriptor more
24117 frequently if they are not listed in the consensus, or if the
24118 version of their descriptor listed in the consensus is too
24119 old. This fix should prevent situations where a server declines
24120 to re-publish itself because it has done so too recently, even
24121 though the authorities decided not to list its recent-enough
24122 descriptor. Fix for bug 3327.
24125 - Relays now include a reason for regenerating their descriptors
24126 in an HTTP header when uploading to the authorities. This will
24127 make it easier to debug descriptor-upload issues in the future.
24128 - When starting as root and then changing our UID via the User
24129 control option, and we have a ControlSocket configured, make sure
24130 that the ControlSocket is owned by the same account that Tor will
24131 run under. Implements ticket 3421; fix by Jérémy Bobbio.
24134 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
24135 utility function used in the control-port code). This shouldn't
24136 ever happen unless Tor is completely out of memory, but if it did
24137 happen and Tor somehow recovered from it, Tor could have sent a log
24138 message to a control port in the middle of a reply to a controller
24139 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
24140 - Make 'FetchUselessDescriptors' cause all descriptor types and
24141 all consensus types (including microdescriptors) to get fetched.
24142 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
24144 o Code refactoring:
24145 - Make a new "entry connection" struct as an internal subtype of "edge
24146 connection", to simplify the code and make exit connections smaller.
24149 Changes in version 0.2.2.33 - 2011-09-13
24150 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
24151 TLS handshake that makes relays and bridges that run this new version
24152 reachable from Iran again.
24155 - Avoid an assertion failure when reloading a configuration with
24156 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
24157 3923; bugfix on 0.2.2.25-alpha.
24159 o Minor features (security):
24160 - Check for replays of the public-key encrypted portion of an
24161 INTRODUCE1 cell, in addition to the current check for replays of
24162 the g^x value. This prevents a possible class of active attacks
24163 by an attacker who controls both an introduction point and a
24164 rendezvous point, and who uses the malleability of AES-CTR to
24165 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
24166 that these attacks are infeasible (requiring the attacker to send
24167 on the order of zettabytes of altered cells in a short interval),
24168 but we'd rather block them off in case there are any classes of
24169 this attack that we missed. Reported by Willem Pinckaers.
24172 - Adjust the expiration time on our SSL session certificates to
24173 better match SSL certs seen in the wild. Resolves ticket 4014.
24174 - Change the default required uptime for a relay to be accepted as
24175 a HSDir (hidden service directory) from 24 hours to 25 hours.
24176 Improves on 0.2.0.10-alpha; resolves ticket 2649.
24177 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
24178 authorities to abstain from voting on assignment of the HSDir
24179 consensus flag. Related to bug 2649.
24180 - Update to the September 6 2011 Maxmind GeoLite Country database.
24182 o Minor bugfixes (documentation and log messages):
24183 - Correct the man page to explain that HashedControlPassword and
24184 CookieAuthentication can both be set, in which case either method
24185 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
24186 when we decided to allow these config options to both be set. Issue
24187 raised by bug 3898.
24188 - Demote the 'replay detected' log message emitted when a hidden
24189 service receives the same Diffie-Hellman public key in two different
24190 INTRODUCE2 cells to info level. A normal Tor client can cause that
24191 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
24192 fixes part of bug 2442.
24193 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
24194 level. There is nothing that a hidden service's operator can do
24195 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
24197 - Clarify a log message specifying the characters permitted in
24198 HiddenServiceAuthorizeClient client names. Previously, the log
24199 message said that "[A-Za-z0-9+-_]" were permitted; that could have
24200 given the impression that every ASCII character between "+" and "_"
24201 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
24204 - Provide a substitute implementation of lround() for MSVC, which
24205 apparently lacks it. Patch from Gisle Vanem.
24206 - Clean up some code issues that prevented Tor from building on older
24207 BSDs. Fixes bug 3894; reported by "grarpamp".
24208 - Search for a platform-specific version of "ar" when cross-compiling.
24209 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
24212 Changes in version 0.2.3.3-alpha - 2011-09-01
24213 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
24214 security, and provides client-side support for the microdescriptor
24215 and optimistic data features introduced earlier in the 0.2.3.x
24216 series. It also includes numerous critical bugfixes in the (optional)
24217 bufferevent-based networking backend.
24219 o Major features (stream isolation):
24220 - You can now configure Tor so that streams from different
24221 applications are isolated on different circuits, to prevent an
24222 attacker who sees your streams as they leave an exit node from
24223 linking your sessions to one another. To do this, choose some way
24224 to distinguish the applications: have them connect to different
24225 SocksPorts, or have one of them use SOCKS4 while the other uses
24226 SOCKS5, or have them pass different authentication strings to the
24227 SOCKS proxy. Then, use the new SocksPort syntax to configure the
24228 degree of isolation you need. This implements Proposal 171.
24229 - There's a new syntax for specifying multiple client ports (such as
24230 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
24231 multiple *Port entries with full addr:port syntax on each.
24232 The old *ListenAddress format is still supported, but you can't
24233 mix it with the new *Port syntax.
24235 o Major features (other):
24236 - Enable microdescriptor fetching by default for clients. This allows
24237 clients to download a much smaller amount of directory information.
24238 To disable it (and go back to the old-style consensus and
24239 descriptors), set "UseMicrodescriptors 0" in your torrc file.
24240 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
24241 "PortForwarding" config option), now supports Windows.
24242 - When using an exit relay running 0.2.3.x, clients can now
24243 "optimistically" send data before the exit relay reports that
24244 the stream has opened. This saves a round trip when starting
24245 connections where the client speaks first (such as web browsing).
24246 This behavior is controlled by a consensus parameter (currently
24247 disabled). To turn it on or off manually, use the "OptimisticData"
24248 torrc option. Implements proposal 181; code by Ian Goldberg.
24250 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
24251 - When using IOCP on Windows, we need to enable Libevent windows
24253 - The IOCP backend now works even when the user has not specified
24254 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
24255 Fixes part of bug 3752.
24256 - Correctly record the bytes we've read and written when using
24257 bufferevents, so that we can include them in our bandwidth history
24258 and advertised bandwidth. Fixes bug 3803.
24259 - Apply rate-limiting only at the bottom of a chain of filtering
24260 bufferevents. This prevents us from filling up internal read
24261 buffers and violating rate-limits when filtering bufferevents
24262 are enabled. Fixes part of bug 3804.
24263 - Add high-watermarks to the output buffers for filtered
24264 bufferevents. This prevents us from filling up internal write
24265 buffers and wasting CPU cycles when filtering bufferevents are
24266 enabled. Fixes part of bug 3804.
24267 - Correctly notice when data has been written from a bufferevent
24268 without flushing it completely. Fixes bug 3805.
24269 - Fix a bug where server-side tunneled bufferevent-based directory
24270 streams would get closed prematurely. Fixes bug 3814.
24271 - Fix a use-after-free error with per-connection rate-limiting
24272 buckets. Fixes bug 3888.
24274 o Major bugfixes (also part of 0.2.2.31-rc):
24275 - If we're configured to write our ControlPorts to disk, only write
24276 them after switching UID and creating the data directory. This way,
24277 we don't fail when starting up with a nonexistent DataDirectory
24278 and a ControlPortWriteToFile setting based on that directory. Fixes
24279 bug 3747; bugfix on Tor 0.2.2.26-beta.
24282 - Added a new CONF_CHANGED event so that controllers can be notified
24283 of any configuration changes made by other controllers, or by the
24284 user. Implements ticket 1692.
24285 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
24286 leak when using bufferevents, and lets Libevent worry about how to
24287 best copy data out of a buffer.
24288 - Replace files in stats/ rather than appending to them. Now that we
24289 include statistics in extra-info descriptors, it makes no sense to
24290 keep old statistics forever. Implements ticket 2930.
24292 o Minor features (build compatibility):
24293 - Limited, experimental support for building with nmake and MSVC.
24294 - Provide a substitute implementation of lround() for MSVC, which
24295 apparently lacks it. Patch from Gisle Vanem.
24297 o Minor features (also part of 0.2.2.31-rc):
24298 - Update to the August 2 2011 Maxmind GeoLite Country database.
24300 o Minor bugfixes (on 0.2.3.x-alpha):
24301 - Fix a spurious warning when parsing SOCKS requests with
24302 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
24303 - Get rid of a harmless warning that could happen on relays running
24304 with bufferevents. The warning was caused by someone doing an http
24305 request to a relay's orport. Also don't warn for a few related
24306 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
24308 o Minor bugfixes (on 2.2.x and earlier):
24309 - Correct the man page to explain that HashedControlPassword and
24310 CookieAuthentication can both be set, in which case either method
24311 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
24312 when we decided to allow these config options to both be set. Issue
24313 raised by bug 3898.
24314 - The "--quiet" and "--hush" options now apply not only to Tor's
24315 behavior before logs are configured, but also to Tor's behavior in
24316 the absence of configured logs. Fixes bug 3550; bugfix on
24319 o Minor bugfixes (also part of 0.2.2.31-rc):
24320 - Write several files in text mode, on OSes that distinguish text
24321 mode from binary mode (namely, Windows). These files are:
24322 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
24323 that collect those statistics; 'client_keys' and 'hostname' for
24324 hidden services that use authentication; and (in the tor-gencert
24325 utility) newly generated identity and signing keys. Previously,
24326 we wouldn't specify text mode or binary mode, leading to an
24327 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
24328 the DirRecordUsageByCountry option which would have triggered
24329 the assertion failure was added), although this assertion failure
24330 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
24331 - Selectively disable deprecation warnings on OS X because Lion
24332 started deprecating the shipped copy of openssl. Fixes bug 3643.
24333 - Remove an extra pair of quotation marks around the error
24334 message in control-port STATUS_GENERAL BUG events. Bugfix on
24335 0.1.2.6-alpha; fixes bug 3732.
24336 - When unable to format an address as a string, report its value
24337 as "???" rather than reusing the last formatted address. Bugfix
24340 o Code simplifications and refactoring:
24341 - Rewrite the listener-selection logic so that parsing which ports
24342 we want to listen on is now separate from binding to the ports
24346 - Building Tor with bufferevent support now requires Libevent
24347 2.0.13-stable or later. Previous versions of Libevent had bugs in
24348 SSL-related bufferevents and related issues that would make Tor
24349 work badly with bufferevents. Requiring 2.0.13-stable also allows
24350 Tor with bufferevents to take advantage of Libevent APIs
24351 introduced after 2.0.8-rc.
24354 Changes in version 0.2.2.32 - 2011-08-27
24355 The Tor 0.2.2 release series is dedicated to the memory of Andreas
24356 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
24357 a founder of the PETS community, a leader in our field, a mentor,
24358 and a friend. He left us with these words: "I had the possibility
24359 to contribute to this world that is not as it should be. I hope I
24360 could help in some areas to make the world a better place, and that
24361 I could also encourage other people to be engaged in improving the
24362 world. Please, stay engaged. This world needs you, your love, your
24363 initiative -- now I cannot be part of that anymore."
24365 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
24366 ready. More than two years in the making, this release features improved
24367 client performance and hidden service reliability, better compatibility
24368 for Android, correct behavior for bridges that listen on more than
24369 one address, more extensible and flexible directory object handling,
24370 better reporting of network statistics, improved code security, and
24371 many many other features and bugfixes.
24374 Changes in version 0.2.2.31-rc - 2011-08-17
24375 Tor 0.2.2.31-rc is the second and hopefully final release candidate
24376 for the Tor 0.2.2.x series.
24379 - Remove an extra pair of quotation marks around the error
24380 message in control-port STATUS_GENERAL BUG events. Bugfix on
24381 0.1.2.6-alpha; fixes bug 3732.
24382 - If we're configured to write our ControlPorts to disk, only write
24383 them after switching UID and creating the data directory. This way,
24384 we don't fail when starting up with a nonexistent DataDirectory
24385 and a ControlPortWriteToFile setting based on that directory. Fixes
24386 bug 3747; bugfix on Tor 0.2.2.26-beta.
24389 - Update to the August 2 2011 Maxmind GeoLite Country database.
24392 - Allow GETINFO fingerprint to return a fingerprint even when
24393 we have not yet built a router descriptor. Fixes bug 3577;
24394 bugfix on 0.2.0.1-alpha.
24395 - Write several files in text mode, on OSes that distinguish text
24396 mode from binary mode (namely, Windows). These files are:
24397 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
24398 that collect those statistics; 'client_keys' and 'hostname' for
24399 hidden services that use authentication; and (in the tor-gencert
24400 utility) newly generated identity and signing keys. Previously,
24401 we wouldn't specify text mode or binary mode, leading to an
24402 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
24403 the DirRecordUsageByCountry option which would have triggered
24404 the assertion failure was added), although this assertion failure
24405 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
24406 - Selectively disable deprecation warnings on OS X because Lion
24407 started deprecating the shipped copy of openssl. Fixes bug 3643.
24408 - When unable to format an address as a string, report its value
24409 as "???" rather than reusing the last formatted address. Bugfix
24413 Changes in version 0.2.3.2-alpha - 2011-07-18
24414 Tor 0.2.3.2-alpha introduces two new experimental features:
24415 microdescriptors and pluggable transports. It also continues cleaning
24416 up a variety of recently introduced features.
24419 - Clients can now use microdescriptors instead of regular descriptors
24420 to build circuits. Microdescriptors are authority-generated
24421 summaries of regular descriptors' contents, designed to change
24422 very rarely (see proposal 158 for details). This feature is
24423 designed to save bandwidth, especially for clients on slow internet
24424 connections. It's off by default for now, since nearly no caches
24425 support it, but it will be on-by-default for clients in a future
24426 version. You can use the UseMicrodescriptors option to turn it on.
24427 - Tor clients using bridges can now be configured to use a separate
24428 'transport' proxy for each bridge. This approach helps to resist
24429 censorship by allowing bridges to use protocol obfuscation
24430 plugins. It implements part of proposal 180. Implements ticket 2841.
24431 - While we're trying to bootstrap, record how many TLS connections
24432 fail in each state, and report which states saw the most failures
24433 in response to any bootstrap failures. This feature may speed up
24434 diagnosis of censorship events. Implements ticket 3116.
24436 o Major bugfixes (on 0.2.3.1-alpha):
24437 - When configuring a large set of nodes in EntryNodes (as with
24438 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
24439 random subset to be guards, and choose them in random
24440 order. Fixes bug 2798.
24441 - Tor could crash when remembering a consensus in a non-used consensus
24442 flavor without having a current consensus set. Fixes bug 3361.
24443 - Comparing an unknown address to a microdescriptor's shortened exit
24444 policy would always give a "rejected" result. Fixes bug 3599.
24445 - Using microdescriptors as a client no longer prevents Tor from
24446 uploading and downloading hidden service descriptors. Fixes
24450 - Allow nameservers with IPv6 address. Resolves bug 2574.
24451 - Accept attempts to include a password authenticator in the
24452 handshake, as supported by SOCKS5. This handles SOCKS clients that
24453 don't know how to omit a password when authenticating. Resolves
24455 - When configuring a large set of nodes in EntryNodes, and there are
24456 enough of them listed as Guard so that we don't need to consider
24457 the non-guard entries, prefer the ones listed with the Guard flag.
24458 - Check for and recover from inconsistency in the microdescriptor
24459 cache. This will make it harder for us to accidentally free a
24460 microdescriptor without removing it from the appropriate data
24461 structures. Fixes issue 3135; issue noted by "wanoskarnet".
24462 - Log SSL state transitions at log level DEBUG, log domain
24463 HANDSHAKE. This can be useful for debugging censorship events.
24464 Implements ticket 3264.
24465 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
24466 implements ticket 3439.
24468 o Minor bugfixes (on 0.2.3.1-alpha):
24469 - Do not free all general-purpose regular descriptors just
24470 because microdescriptor use is enabled. Fixes bug 3113.
24471 - Correctly link libevent_openssl when --enable-static-libevent
24472 is passed to configure. Fixes bug 3118.
24473 - Bridges should not complain during their heartbeat log messages that
24474 they are unlisted in the consensus: that's more or less the point
24475 of being a bridge. Fixes bug 3183.
24476 - Report a SIGNAL event to controllers when acting on a delayed
24477 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
24478 event to the controller if we acted on a SIGNAL NEWNYM command
24479 immediately, and otherwise not report a SIGNAL event for the
24480 command at all. Fixes bug 3349.
24481 - Fix a crash when handling the SIGNAL controller command or
24482 reporting ERR-level status events with bufferevents enabled. Found
24483 by Robert Ransom. Fixes bug 3367.
24484 - Always ship the tor-fw-helper manpage in our release tarballs.
24485 Fixes bug 3389. Reported by Stephen Walker.
24486 - Fix a class of double-mark-for-close bugs when bufferevents
24487 are enabled. Fixes bug 3403.
24488 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
24489 - Add SIGNAL to the list returned by the 'GETINFO events/names'
24490 control-port command. Fixes part of bug 3465.
24491 - Prevent using negative indices during unit test runs when read_all()
24492 fails. Spotted by coverity.
24493 - Fix a rare memory leak when checking the nodelist without it being
24494 present. Found by coverity.
24495 - Only try to download a microdescriptor-flavored consensus from
24496 a directory cache that provides them.
24498 o Minor bugfixes (on 0.2.2.x and earlier):
24499 - Assert that hidden-service-related operations are not performed
24500 using single-hop circuits. Previously, Tor would assert that
24501 client-side streams are not attached to single-hop circuits,
24502 but not that other sensitive operations on the client and service
24503 side are not performed using single-hop circuits. Fixes bug 3332;
24505 - Don't publish a new relay descriptor when we reload our onion key,
24506 unless the onion key has actually changed. Fixes bug 3263 and
24507 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
24508 - Allow GETINFO fingerprint to return a fingerprint even when
24509 we have not yet built a router descriptor. Fixes bug 3577;
24510 bugfix on 0.2.0.1-alpha.
24511 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
24512 on 0.2.2.4-alpha; fixes bug 3427.
24514 o Code simplification and refactoring:
24515 - Use tor_sscanf() in place of scanf() in more places through the
24516 code. This makes us a little more locale-independent, and
24517 should help shut up code-analysis tools that can't tell
24518 a safe sscanf string from a dangerous one.
24519 - Use tt_assert(), not tor_assert(), for checking for test failures.
24520 This makes the unit tests more able to go on in the event that
24522 - Split connection_about_to_close() into separate functions for each
24526 - On Windows, we now define the _WIN32_WINNT macros only if they
24527 are not already defined. This lets the person building Tor decide,
24528 if they want, to require a later version of Windows.
24531 Changes in version 0.2.2.30-rc - 2011-07-07
24532 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
24533 series. It fixes a few smaller bugs, but generally appears stable.
24534 Please test it and let us know whether it is!
24537 - Send a SUCCEEDED stream event to the controller when a reverse
24538 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
24539 discovered by katmagic.
24540 - Always NUL-terminate the sun_path field of a sockaddr_un before
24541 passing it to the kernel. (Not a security issue: kernels are
24542 smart enough to reject bad sockaddr_uns.) Found by Coverity;
24543 CID #428. Bugfix on Tor 0.2.0.3-alpha.
24544 - Don't stack-allocate the list of supplementary GIDs when we're
24545 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
24546 could take up to 256K, which is way too much stack. Found by
24547 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
24548 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
24549 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
24550 fixes part of bug 3465.
24551 - Fix a memory leak when receiving a descriptor for a hidden
24552 service we didn't ask for. Found by Coverity; CID #30. Bugfix
24556 - Update to the July 1 2011 Maxmind GeoLite Country database.
24559 Changes in version 0.2.2.29-beta - 2011-06-20
24560 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
24561 have bridge lines in their torrc but don't want to use them; gets
24562 us closer to having the control socket feature working on Debian;
24563 and fixes a variety of smaller bugs.
24566 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
24567 When we changed the default behavior to "use bridges if any
24568 are listed in the torrc", we surprised users who had bridges
24569 in their torrc files but who didn't actually want to use them.
24570 Partial resolution for bug 3354.
24573 - Don't attach new streams to old rendezvous circuits after SIGNAL
24574 NEWNYM. Previously, we would keep using an existing rendezvous
24575 circuit if it remained open (i.e. if it were kept open by a
24576 long-lived stream, or if a new stream were attached to it before
24577 Tor could notice that it was old and no longer in use). Bugfix on
24578 0.1.1.15-rc; fixes bug 3375.
24581 - Fix a bug when using ControlSocketsGroupWritable with User. The
24582 directory's group would be checked against the current group, not
24583 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
24584 bugfix on 0.2.2.26-beta.
24585 - Make connection_printf_to_buf()'s behavior sane. Its callers
24586 expect it to emit a CRLF iff the format string ends with CRLF;
24587 it actually emitted a CRLF iff (a) the format string ended with
24588 CRLF or (b) the resulting string was over 1023 characters long or
24589 (c) the format string did not end with CRLF *and* the resulting
24590 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
24591 fixes part of bug 3407.
24592 - Make send_control_event_impl()'s behavior sane. Its callers
24593 expect it to always emit a CRLF at the end of the string; it
24594 might have emitted extra control characters as well. Bugfix on
24595 0.1.1.9-alpha; fixes another part of bug 3407.
24596 - Make crypto_rand_int() check the value of its input correctly.
24597 Previously, it accepted values up to UINT_MAX, but could return a
24598 negative number if given a value above INT_MAX+1. Found by George
24599 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
24600 - Avoid a segfault when reading a malformed circuit build state
24601 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
24603 - When asked about a DNS record type we don't support via a
24604 client DNSPort, reply with NOTIMPL rather than an empty
24605 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
24606 - Fix a rare memory leak during stats writing. Found by coverity.
24609 - Update to the June 1 2011 Maxmind GeoLite Country database.
24611 o Code simplifications and refactoring:
24612 - Remove some dead code as indicated by coverity.
24613 - Remove a few dead assignments during router parsing. Found by
24615 - Add some forgotten return value checks during unit tests. Found
24617 - Don't use 1-bit wide signed bit fields. Found by coverity.
24620 Changes in version 0.2.2.28-beta - 2011-06-04
24621 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
24622 fixed a big bug in whether relays stay in the consensus consistently,
24623 we moved closer to handling bridges and hidden services correctly,
24624 and we started the process of better handling the dreaded "my Vidalia
24625 died, and now my Tor demands a password when I try to reconnect to it"
24629 - Don't decide to make a new descriptor when receiving a HUP signal.
24630 This bug has caused a lot of 0.2.2.x relays to disappear from the
24631 consensus periodically. Fixes the most common case of triggering
24632 bug 1810; bugfix on 0.2.2.7-alpha.
24633 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
24634 - Don't try to build descriptors if "ORPort auto" is set and we
24635 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
24637 - Resolve a crash that occurred when setting BridgeRelay to 1 with
24638 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
24639 - Apply circuit timeouts to opened hidden-service-related circuits
24640 based on the correct start time. Previously, we would apply the
24641 circuit build timeout based on time since the circuit's creation;
24642 it was supposed to be applied based on time since the circuit
24643 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
24644 - Use the same circuit timeout for client-side introduction
24645 circuits as for other four-hop circuits, rather than the timeout
24646 for single-hop directory-fetch circuits; the shorter timeout may
24647 have been appropriate with the static circuit build timeout in
24648 0.2.1.x and earlier, but caused many hidden service access attempts
24649 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
24650 on 0.2.2.2-alpha; fixes another part of bug 1297.
24651 - In ticket 2511 we fixed a case where you could use an unconfigured
24652 bridge if you had configured it as a bridge the last time you ran
24653 Tor. Now fix another edge case: if you had configured it as a bridge
24654 but then switched to a different bridge via the controller, you
24655 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
24659 - Add an __OwningControllerProcess configuration option and a
24660 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
24661 that when it exits, Tor will shut down. Implements feature 3049.
24662 - If "UseBridges 1" is set and no bridges are configured, Tor will
24663 now refuse to build any circuits until some bridges are set.
24664 If "UseBridges auto" is set, Tor will use bridges if they are
24665 configured and we are not running as a server, but otherwise will
24666 make circuits as usual. The new default is "auto". Patch by anonym,
24667 so the Tails LiveCD can stop automatically revealing you as a Tor
24671 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
24672 - Remove a trailing asterisk from "exit-policy/default" in the
24673 output of the control port command "GETINFO info/names". Bugfix
24675 - Use a wide type to hold sockets when built for 64-bit Windows builds.
24677 - Warn when the user configures two HiddenServiceDir lines that point
24678 to the same directory. Bugfix on 0.0.6 (the version introducing
24679 HiddenServiceDir); fixes bug 3289.
24680 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
24681 part of bug 2748; bugfix on 0.2.0.10-alpha.
24682 - Log malformed requests for rendezvous descriptors as protocol
24683 warnings, not warnings. Also, use a more informative log message
24684 in case someone sees it at log level warning without prior
24685 info-level messages. Fixes the other part of bug 2748; bugfix
24687 - Clear the table recording the time of the last request for each
24688 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
24689 Previously, we would clear our HS descriptor cache on SIGNAL
24690 NEWNYM, but if we had previously retrieved a descriptor (or tried
24691 to) from every directory responsible for it, we would refuse to
24692 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
24694 - Fix a log message that said "bits" while displaying a value in
24695 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
24697 - When checking for 1024-bit keys, check for 1024 bits, not 128
24698 bytes. This allows Tor to correctly discard keys of length 1017
24699 through 1023. Bugfix on 0.0.9pre5.
24702 - Relays now log the reason for publishing a new relay descriptor,
24703 so we have a better chance of hunting down instances of bug 1810.
24704 Resolves ticket 3252.
24705 - Revise most log messages that refer to nodes by nickname to
24706 instead use the "$key=nickname at address" format. This should be
24707 more useful, especially since nicknames are less and less likely
24708 to be unique. Resolves ticket 3045.
24709 - Log (at info level) when purging pieces of hidden-service-client
24710 state because of SIGNAL NEWNYM.
24713 - Remove undocumented option "-F" from tor-resolve: it hasn't done
24714 anything since 0.2.1.16-rc.
24717 Changes in version 0.2.2.27-beta - 2011-05-18
24718 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
24719 release, and also adds a few more general bugfixes.
24722 - Fix a crash bug when changing bridges in a running Tor process.
24723 Fixes bug 3213; bugfix on 0.2.2.26-beta.
24724 - When the controller configures a new bridge, don't wait 10 to 60
24725 seconds before trying to fetch its descriptor. Bugfix on
24726 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
24729 - Require that onion keys have exponent 65537 in microdescriptors too.
24730 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
24731 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
24732 Changed the limit to 512 characters by removing base64 newlines.
24733 Fixes bug 2752. Fix by Michael Yakubovich.
24734 - When a client starts or stops using bridges, never use a circuit
24735 that was built before the configuration change. This behavior could
24736 put at risk a user who uses bridges to ensure that her traffic
24737 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
24741 Changes in version 0.2.2.26-beta - 2011-05-17
24742 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
24743 also introduces a new "socksport auto" approach that should make it
24744 easier to run multiple Tors on the same system, and does a lot of
24745 cleanup to get us closer to a release candidate.
24747 o Security/privacy fixes:
24748 - Replace all potentially sensitive memory comparison operations
24749 with versions whose runtime does not depend on the data being
24750 compared. This will help resist a class of attacks where an
24751 adversary can use variations in timing information to learn
24752 sensitive data. Fix for one case of bug 3122. (Safe memcmp
24753 implementation by Robert Ransom based partially on code by DJB.)
24754 - When receiving a hidden service descriptor, check that it is for
24755 the hidden service we wanted. Previously, Tor would store any
24756 hidden service descriptors that a directory gave it, whether it
24757 wanted them or not. This wouldn't have let an attacker impersonate
24758 a hidden service, but it did let directories pre-seed a client
24759 with descriptors that it didn't want. Bugfix on 0.0.6.
24760 - On SIGHUP, do not clear out all TrackHostExits mappings, client
24761 DNS cache entries, and virtual address mappings: that's what
24762 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
24765 - The options SocksPort, ControlPort, and so on now all accept a
24766 value "auto" that opens a socket on an OS-selected port. A
24767 new ControlPortWriteToFile option tells Tor to write its
24768 actual control port or ports to a chosen file. If the option
24769 ControlPortFileGroupReadable is set, the file is created as
24770 group-readable. Now users can run two Tor clients on the same
24771 system without needing to manually mess with parameters. Resolves
24772 part of ticket 3076.
24773 - Set SO_REUSEADDR on all sockets, not just listeners. This should
24774 help busy exit nodes avoid running out of useable ports just
24775 because all the ports have been used in the near past. Resolves
24779 - New "GETINFO net/listeners/(type)" controller command to return
24780 a list of addresses and ports that are bound for listeners for a
24781 given connection type. This is useful when the user has configured
24782 "SocksPort auto" and the controller needs to know which port got
24783 chosen. Resolves another part of ticket 3076.
24784 - Add a new ControlSocketsGroupWritable configuration option: when
24785 it is turned on, ControlSockets are group-writeable by the default
24786 group of the current user. Patch by Jérémy Bobbio; implements
24788 - Tor now refuses to create a ControlSocket in a directory that is
24789 world-readable (or group-readable if ControlSocketsGroupWritable
24790 is 0). This is necessary because some operating systems do not
24791 enforce permissions on an AF_UNIX sockets. Permissions on the
24792 directory holding the socket, however, seems to work everywhere.
24793 - Rate-limit a warning about failures to download v2 networkstatus
24794 documents. Resolves part of bug 1352.
24795 - Backport code from 0.2.3.x that allows directory authorities to
24796 clean their microdescriptor caches. Needed to resolve bug 2230.
24797 - When an HTTPS proxy reports "403 Forbidden", we now explain
24798 what it means rather than calling it an unexpected status code.
24799 Closes bug 2503. Patch from Michael Yakubovich.
24800 - Update to the May 1 2011 Maxmind GeoLite Country database.
24803 - Authorities now clean their microdesc cache periodically and when
24804 reading from disk initially, not only when adding new descriptors.
24805 This prevents a bug where we could lose microdescriptors. Bugfix
24806 on 0.2.2.6-alpha. Fixes bug 2230.
24807 - Do not crash when our configuration file becomes unreadable, for
24808 example due to a permissions change, between when we start up
24809 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
24811 - Avoid a bug that would keep us from replacing a microdescriptor
24812 cache on Windows. (We would try to replace the file while still
24813 holding it open. That's fine on Unix, but Windows doesn't let us
24814 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
24815 - Add missing explanations for the authority-related torrc options
24816 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
24817 man page. Resolves issue 2379.
24818 - As an authority, do not upload our own vote or signature set to
24819 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
24820 it would get flagged as a duplicate. Resolves bug 3026.
24821 - Accept hidden service descriptors if we think we might be a hidden
24822 service directory, regardless of what our consensus says. This
24823 helps robustness, since clients and hidden services can sometimes
24824 have a more up-to-date view of the network consensus than we do,
24825 and if they think that the directory authorities list us a HSDir,
24826 we might actually be one. Related to bug 2732; bugfix on
24828 - When a controller changes TrackHostExits, remove mappings for
24829 hosts that should no longer have their exits tracked. Bugfix on
24831 - When a controller changes VirtualAddrNetwork, remove any mappings
24832 for hosts that were automapped to the old network. Bugfix on
24834 - When a controller changes one of the AutomapHosts* options, remove
24835 any mappings for hosts that should no longer be automapped. Bugfix
24837 - Do not reset the bridge descriptor download status every time we
24838 re-parse our configuration or get a configuration change. Fixes
24839 bug 3019; bugfix on 0.2.0.3-alpha.
24841 o Minor bugfixes (code cleanup):
24842 - When loading the microdesc journal, remember its current size.
24843 In 0.2.2, this helps prevent the microdesc journal from growing
24844 without limit on authorities (who are the only ones to use it in
24845 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
24846 Fix posted by "cypherpunks."
24847 - The microdesc journal is supposed to get rebuilt only if it is
24848 at least _half_ the length of the store, not _twice_ the length
24849 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
24850 - Fix a potential null-pointer dereference while computing a
24851 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
24853 - Avoid a possible null-pointer dereference when rebuilding the mdesc
24854 cache without actually having any descriptors to cache. Bugfix on
24855 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
24856 - If we fail to compute the identity digest of a v3 legacy keypair,
24857 warn, and don't use a buffer-full of junk instead. Bugfix on
24858 0.2.1.1-alpha; fixes bug 3106.
24859 - Resolve an untriggerable issue in smartlist_string_num_isin(),
24860 where if the function had ever in the future been used to check
24861 for the presence of a too-large number, it would have given an
24862 incorrect result. (Fortunately, we only used it for 16-bit
24863 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
24864 - Require that introduction point keys and onion handshake keys
24865 have a public exponent of 65537. Starts to fix bug 3207; bugfix
24868 o Removed features:
24869 - Caches no longer download and serve v2 networkstatus documents
24870 unless FetchV2Networkstatus flag is set: these documents haven't
24871 haven't been used by clients or relays since 0.2.0.x. Resolves
24875 Changes in version 0.2.3.1-alpha - 2011-05-05
24876 Tor 0.2.3.1-alpha adds some new experimental features, including support
24877 for an improved network IO backend, IOCP networking on Windows,
24878 microdescriptor caching, "fast-start" support for streams, and automatic
24879 home router configuration. There are also numerous internal improvements
24880 to try to make the code easier for developers to work with.
24882 This is the first alpha release in a new series, so expect there to be
24883 bugs. Users who would rather test out a more stable branch should
24884 stay with 0.2.2.x for now.
24887 - Tor can now optionally build with the "bufferevents" buffered IO
24888 backend provided by Libevent 2. To use this feature, make sure you
24889 have the latest possible version of Libevent, and pass the
24890 --enable-bufferevents flag to configure when building Tor from
24891 source. This feature will make our networking code more flexible,
24892 let us stack layers on each other, and let us use more efficient
24893 zero-copy transports where available.
24894 - As an experimental feature, Tor can use IOCP for networking on Windows.
24895 Once this code is tuned and optimized, it promises much better
24896 performance than the select-based backend we've used in the past. To
24897 try this feature, you must build Tor with Libevent 2, configure Tor
24898 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
24899 your torrc. There are known bugs here: only try this if you can help
24900 debug it as it breaks.
24901 - The EntryNodes option can now include country codes like {de} or IP
24902 addresses or network masks. Previously we had disallowed these options
24903 because we didn't have an efficient way to keep the list up to
24904 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
24905 - Exit nodes now accept and queue data on not-yet-connected streams.
24906 Previously, the client wasn't allowed to send data until the stream was
24907 connected, which slowed down all connections. This change will enable
24908 clients to perform a "fast-start" on streams and send data without
24909 having to wait for a confirmation that the stream has opened. (Patch
24910 from Ian Goldberg; implements the server side of Proposal 174.)
24911 - Tor now has initial support for automatic port mapping on the many
24912 home routers that support NAT-PMP or UPnP. (Not yet supported on
24913 Windows). To build the support code, you'll need to have libnatpnp
24914 library and/or the libminiupnpc library, and you'll need to enable the
24915 feature specifically by passing "--enable-upnp" and/or
24916 "--enable-natpnp" to configure. To turn it on, use the new
24917 PortForwarding option.
24918 - Caches now download, cache, and serve multiple "flavors" of the
24919 consensus, including a flavor that describes microdescriptors.
24920 - Caches now download, cache, and serve microdescriptors -- small
24921 summaries of router descriptors that are authenticated by all of the
24922 directory authorities. Once enough caches are running this code,
24923 clients will be able to save significant amounts of directory bandwidth
24924 by downloading microdescriptors instead of router descriptors.
24927 - Make logging resolution configurable with a new LogTimeGranularity
24928 option, and change the default from 1 millisecond to 1 second.
24929 Implements enhancement 1668.
24930 - We log which torrc file we're using on startup. Implements ticket
24932 - Ordinarily, Tor does not count traffic from private addresses (like
24933 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
24934 There is now a new option, CountPrivateBandwidth, to disable this
24935 behavior. Patch from Daniel Cagara.
24936 - New --enable-static-tor configure option for building Tor as
24937 statically as possible. Idea, general hackery and thoughts from
24938 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
24940 - If you set the NumCPUs option to 0, Tor will now try to detect how
24941 many CPUs you have. This is the new default behavior.
24942 - Turn on directory request statistics by default and include them in
24943 extra-info descriptors. Don't break if we have no GeoIP database.
24944 - Relays that set "ConnDirectionStatistics 1" write statistics on the
24945 bidirectional use of connections to disk every 24 hours.
24946 - Add a GeoIP file digest to the extra-info descriptor. Implements
24948 - The NodeFamily option -- which let you declare that you want to
24949 consider nodes to be part of a family whether they list themselves
24950 that way or not -- now allows IP address ranges and country codes.
24951 - Add a new 'Heartbeat' log message type to periodically log a message
24952 describing Tor's status at level Notice. This feature is meant for
24953 operators who log at notice, and want to make sure that their Tor
24954 server is still working. Implementation by George Kadianakis.
24956 o Minor bugfixes (on 0.2.2.25-alpha):
24957 - When loading the microdesc journal, remember its current size.
24958 In 0.2.2, this helps prevent the microdesc journal from growing
24959 without limit on authorities (who are the only ones to use it in
24960 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
24961 Fix posted by "cypherpunks."
24962 - The microdesc journal is supposed to get rebuilt only if it is
24963 at least _half_ the length of the store, not _twice_ the length
24964 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
24965 - If as an authority we fail to compute the identity digest of a v3
24966 legacy keypair, warn, and don't use a buffer-full of junk instead.
24967 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
24968 - Authorities now clean their microdesc cache periodically and when
24969 reading from disk initially, not only when adding new descriptors.
24970 This prevents a bug where we could lose microdescriptors. Bugfix
24973 o Minor features (controller):
24974 - Add a new SIGNAL event to the controller interface so that
24975 controllers can be notified when Tor handles a signal. Resolves
24976 issue 1955. Patch by John Brooks.
24977 - Add a new GETINFO option to get total bytes read and written. Patch
24978 from pipe, revised by atagar. Resolves ticket 2345.
24979 - Implement some GETINFO controller fields to provide information about
24980 the Tor process's pid, euid, username, and resource limits.
24983 - Our build system requires automake 1.6 or later to create the
24984 Makefile.in files. Previously, you could have used 1.4.
24985 This only affects developers and people building Tor from git;
24986 people who build Tor from the source distribution without changing
24987 the Makefile.am files should be fine.
24988 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
24989 so on. This is more robust against some of the failure modes
24990 associated with running the autotools pieces on their own.
24992 o Minor packaging issues:
24993 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
24994 already created. Patch from Andreas Stieger. Fixes bug 2573.
24996 o Code simplifications and refactoring:
24997 - A major revision to our internal node-selecting and listing logic.
24998 Tor already had at least two major ways to look at the question of
24999 "which Tor servers do we know about": a list of router descriptors,
25000 and a list of entries in the current consensus. With
25001 microdescriptors, we're adding a third. Having so many systems
25002 without an abstraction layer over them was hurting the codebase.
25003 Now, we have a new "node_t" abstraction that presents a consistent
25004 interface to a client's view of a Tor node, and holds (nearly) all
25005 of the mutable state formerly in routerinfo_t and routerstatus_t.
25006 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
25007 no longer link against Libevent: they never used it, but
25008 our library structure used to force them to link it.
25010 o Removed features:
25011 - Remove some old code to work around even older versions of Tor that
25012 used forked processes to handle DNS requests. Such versions of Tor
25013 are no longer in use as servers.
25015 o Documentation fixes:
25016 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
25017 - Add missing documentation for the authority-related torrc options
25018 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
25022 Changes in version 0.2.2.25-alpha - 2011-04-29
25023 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
25024 robust, routers no longer overreport their bandwidth, Win7 should crash
25025 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
25026 now prevents hidden service-related activity from being linkable. It
25027 provides more information to Vidalia so you can see if your bridge is
25028 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
25029 StrictNodes configuration options to make them more reliable, more
25030 understandable, and more regularly applied. If you use those options,
25031 please see the revised documentation for them in the manual page.
25034 - Relays were publishing grossly inflated bandwidth values because
25035 they were writing their state files wrong--now they write the
25036 correct value. Also, resume reading bandwidth history from the
25037 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
25038 - Improve hidden service robustness: When we find that we have
25039 extended a hidden service's introduction circuit to a relay not
25040 listed as an introduction point in the HS descriptor we currently
25041 have, retry with an introduction point from the current
25042 descriptor. Previously we would just give up. Fixes bugs 1024 and
25043 1930; bugfix on 0.2.0.10-alpha.
25044 - Clients now stop trying to use an exit node associated with a given
25045 destination by TrackHostExits if they fail to reach that exit node.
25046 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
25047 - Fix crash bug on platforms where gmtime and localtime can return
25048 NULL. Windows 7 users were running into this one. Fixes part of bug
25049 2077. Bugfix on all versions of Tor. Found by boboper.
25051 o Security and stability fixes:
25052 - Don't double-free a parsable, but invalid, microdescriptor, even if
25053 it is followed in the blob we're parsing by an unparsable
25054 microdescriptor. Fixes an issue reported in a comment on bug 2954.
25055 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
25056 - If the Nickname configuration option isn't given, Tor would pick a
25057 nickname based on the local hostname as the nickname for a relay.
25058 Because nicknames are not very important in today's Tor and the
25059 "Unnamed" nickname has been implemented, this is now problematic
25060 behavior: It leaks information about the hostname without being
25061 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
25062 introduced the Unnamed nickname. Reported by tagnaq.
25063 - Fix an uncommon assertion failure when running with DNSPort under
25064 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
25065 - Avoid linkability based on cached hidden service descriptors: forget
25066 all hidden service descriptors cached as a client when processing a
25067 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
25070 - Export GeoIP information on bridge usage to controllers even if we
25071 have not yet been running for 24 hours. Now Vidalia bridge operators
25072 can get more accurate and immediate feedback about their
25073 contributions to the network.
25075 o Major features and bugfixes (node selection):
25076 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
25077 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
25078 options. Previously, we had been ambiguous in describing what
25079 counted as an "exit" node, and what operations exactly "StrictNodes
25080 0" would permit. This created confusion when people saw nodes built
25081 through unexpected circuits, and made it hard to tell real bugs from
25082 surprises. Now the intended behavior is:
25083 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
25084 a node that delivers user traffic outside the Tor network.
25085 . "Entry", in the context of EntryNodes, means a node used as the
25086 first hop of a multihop circuit. It doesn't include direct
25087 connections to directory servers.
25088 . "ExcludeNodes" applies to all nodes.
25089 . "StrictNodes" changes the behavior of ExcludeNodes only. When
25090 StrictNodes is set, Tor should avoid all nodes listed in
25091 ExcludeNodes, even when it will make user requests fail. When
25092 StrictNodes is *not* set, then Tor should follow ExcludeNodes
25093 whenever it can, except when it must use an excluded node to
25094 perform self-tests, connect to a hidden service, provide a
25095 hidden service, fulfill a .exit request, upload directory
25096 information, or fetch directory information.
25097 Collectively, the changes to implement the behavior fix bug 1090.
25098 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
25099 a node is listed in both, it's treated as excluded.
25100 - ExcludeNodes now applies to directory nodes -- as a preference if
25101 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
25102 Don't exclude all the directory authorities and set StrictNodes to 1
25103 unless you really want your Tor to break.
25104 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
25105 - ExcludeExitNodes now overrides .exit requests.
25106 - We don't use bridges listed in ExcludeNodes.
25107 - When StrictNodes is 1:
25108 . We now apply ExcludeNodes to hidden service introduction points
25109 and to rendezvous points selected by hidden service users. This
25110 can make your hidden service less reliable: use it with caution!
25111 . If we have used ExcludeNodes on ourself, do not try relay
25112 reachability self-tests.
25113 . If we have excluded all the directory authorities, we will not
25114 even try to upload our descriptor if we're a relay.
25115 . Do not honor .exit requests to an excluded node.
25116 - Remove a misfeature that caused us to ignore the Fast/Stable flags
25117 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
25118 - When the set of permitted nodes changes, we now remove any mappings
25119 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
25121 - We never cannibalize a circuit that had excluded nodes on it, even
25122 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
25123 - Revert a change where we would be laxer about attaching streams to
25124 circuits than when building the circuits. This was meant to prevent
25125 a set of bugs where streams were never attachable, but our improved
25126 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
25127 - Keep track of how many times we launch a new circuit to handle a
25128 given stream. Too many launches could indicate an inconsistency
25129 between our "launch a circuit to handle this stream" logic and our
25130 "attach this stream to one of the available circuits" logic.
25131 - Improve log messages related to excluded nodes.
25134 - Fix a spurious warning when moving from a short month to a long
25135 month on relays with month-based BandwidthAccounting. Bugfix on
25136 0.2.2.17-alpha; fixes bug 3020.
25137 - When a client finds that an origin circuit has run out of 16-bit
25138 stream IDs, we now mark it as unusable for new streams. Previously,
25139 we would try to close the entire circuit. Bugfix on 0.0.6.
25140 - Add a forgotten cast that caused a compile warning on OS X 10.6.
25141 Bugfix on 0.2.2.24-alpha.
25142 - Be more careful about reporting the correct error from a failed
25143 connect() system call. Under some circumstances, it was possible to
25144 look at an incorrect value for errno when sending the end reason.
25145 Bugfix on 0.1.0.1-rc.
25146 - Correctly handle an "impossible" overflow cases in connection byte
25147 counting, where we write or read more than 4GB on an edge connection
25148 in a single second. Bugfix on 0.1.2.8-beta.
25149 - Correct the warning displayed when a rendezvous descriptor exceeds
25150 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
25152 - Clients and hidden services now use HSDir-flagged relays for hidden
25153 service descriptor downloads and uploads even if the relays have no
25154 DirPort set and the client has disabled TunnelDirConns. This will
25155 eventually allow us to give the HSDir flag to relays with no
25156 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
25157 - Downgrade "no current certificates known for authority" message from
25158 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
25159 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
25160 2917. Bugfix on 0.1.1.1-alpha.
25161 - Only limit the lengths of single HS descriptors, even when multiple
25162 HS descriptors are published to an HSDir relay in a single POST
25163 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
25164 - Write the current time into the LastWritten line in our state file,
25165 rather than the time from the previous write attempt. Also, stop
25166 trying to use a time of -1 in our log statements. Fixes bug 3039;
25167 bugfix on 0.2.2.14-alpha.
25168 - Be more consistent in our treatment of file system paths. "~" should
25169 get expanded to the user's home directory in the Log config option.
25170 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
25171 feature for the -f and --DataDirectory options.
25174 - Make sure every relay writes a state file at least every 12 hours.
25175 Previously, a relay could go for weeks without writing its state
25176 file, and on a crash could lose its bandwidth history, capacity
25177 estimates, client country statistics, and so on. Addresses bug 3012.
25178 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
25179 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
25180 clients are already deprecated because of security bugs.
25181 - Don't allow v0 hidden service authorities to act as clients.
25182 Required by fix for bug 3000.
25183 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
25184 by fix for bug 3000.
25185 - Ensure that no empty [dirreq-](read|write)-history lines are added
25186 to an extrainfo document. Implements ticket 2497.
25188 o Code simplification and refactoring:
25189 - Remove workaround code to handle directory responses from servers
25190 that had bug 539 (they would send HTTP status 503 responses _and_
25191 send a body too). Since only server versions before
25192 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
25193 keep the workaround in place.
25194 - Remove the old 'fuzzy time' logic. It was supposed to be used for
25195 handling calculations where we have a known amount of clock skew and
25196 an allowed amount of unknown skew. But we only used it in three
25197 places, and we never adjusted the known/unknown skew values. This is
25198 still something we might want to do someday, but if we do, we'll
25199 want to do it differently.
25200 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
25201 None of the cases where we did this before were wrong, but by making
25202 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
25203 - Use GetTempDir to find the proper temporary directory location on
25204 Windows when generating temporary files for the unit tests. Patch by
25208 Changes in version 0.2.2.24-alpha - 2011-04-08
25209 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
25210 prevented Tor clients from effectively using "multihomed" bridges,
25211 that is, bridges that listen on multiple ports or IP addresses so users
25212 can continue to use some of their addresses even if others get blocked.
25215 - Fix a bug where bridge users who configure the non-canonical
25216 address of a bridge automatically switch to its canonical
25217 address. If a bridge listens at more than one address, it should be
25218 able to advertise those addresses independently and any non-blocked
25219 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
25221 - If you configured Tor to use bridge A, and then quit and
25222 configured Tor to use bridge B instead, it would happily continue
25223 to use bridge A if it's still reachable. While this behavior is
25224 a feature if your goal is connectivity, in some scenarios it's a
25225 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
25226 - Directory authorities now use data collected from their own
25227 uptime observations when choosing whether to assign the HSDir flag
25228 to relays, instead of trusting the uptime value the relay reports in
25229 its descriptor. This change helps prevent an attack where a small
25230 set of nodes with frequently-changing identity keys can blackhole
25231 a hidden service. (Only authorities need upgrade; others will be
25232 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
25235 - When we restart our relay, we might get a successful connection
25236 from the outside before we've started our reachability tests,
25237 triggering a warning: "ORPort found reachable, but I have no
25238 routerinfo yet. Failing to inform controller of success." This
25239 bug was harmless unless Tor is running under a controller
25240 like Vidalia, in which case the controller would never get a
25241 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
25243 - Make directory authorities more accurate at recording when
25244 relays that have failed several reachability tests became
25245 unreachable, so we can provide more accuracy at assigning Stable,
25246 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
25247 - Fix an issue that prevented static linking of libevent on
25248 some platforms (notably Linux). Fixes bug 2698; bugfix on
25249 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
25250 the --with-static-libevent configure option).
25251 - We now ask the other side of a stream (the client or the exit)
25252 for more data on that stream when the amount of queued data on
25253 that stream dips low enough. Previously, we wouldn't ask the
25254 other side for more data until either it sent us more data (which
25255 it wasn't supposed to do if it had exhausted its window!) or we
25256 had completely flushed all our queued data. This flow control fix
25257 should improve throughput. Fixes bug 2756; bugfix on the earliest
25258 released versions of Tor (svn commit r152).
25259 - Avoid a double-mark-for-free warning when failing to attach a
25260 transparent proxy connection. (We thought we had fixed this in
25261 0.2.2.23-alpha, but it turns out our fix was checking the wrong
25262 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
25263 bug) and 0.2.2.23-alpha (the incorrect fix).
25264 - When warning about missing zlib development packages during compile,
25265 give the correct package names. Bugfix on 0.2.0.1-alpha.
25268 - Directory authorities now log the source of a rejected POSTed v3
25269 networkstatus vote.
25270 - Make compilation with clang possible when using
25271 --enable-gcc-warnings by removing two warning options that clang
25272 hasn't implemented yet and by fixing a few warnings. Implements
25274 - When expiring circuits, use microsecond timers rather than
25275 one-second timers. This can avoid an unpleasant situation where a
25276 circuit is launched near the end of one second and expired right
25277 near the beginning of the next, and prevent fluctuations in circuit
25279 - Use computed circuit-build timeouts to decide when to launch
25280 parallel introduction circuits for hidden services. (Previously,
25281 we would retry after 15 seconds.)
25282 - Update to the April 1 2011 Maxmind GeoLite Country database.
25285 - Create the /var/run/tor directory on startup on OpenSUSE if it is
25286 not already created. Patch from Andreas Stieger. Fixes bug 2573.
25288 o Documentation changes:
25289 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
25290 - Resolve all doxygen warnings except those for missing documentation.
25292 - Add doxygen documentation for more functions, fields, and types.
25295 Changes in version 0.2.2.23-alpha - 2011-03-08
25296 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
25297 they restart they don't lose their bandwidth capacity estimate. This
25298 release also fixes a diverse set of user-facing bugs, ranging from
25299 relays overrunning their rate limiting to clients falsely warning about
25300 clock skew to bridge descriptor leaks by our bridge directory authority.
25303 - Stop sending a CLOCK_SKEW controller status event whenever
25304 we fetch directory information from a relay that has a wrong clock.
25305 Instead, only inform the controller when it's a trusted authority
25306 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
25307 the rest of bug 1074.
25308 - Fix an assert in parsing router descriptors containing IPv6
25309 addresses. This one took down the directory authorities when
25310 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
25311 - Make the bridge directory authority refuse to answer directory
25312 requests for "all" descriptors. It used to include bridge
25313 descriptors in its answer, which was a major information leak.
25314 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
25315 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
25316 Tor would ignore their RelayBandwidthBurst setting,
25317 potentially using more bandwidth than expected. Bugfix on
25318 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
25319 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
25320 hidserv" in her torrc. The 'hidserv' argument never controlled
25321 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
25324 - Relays now save observed peak bandwidth throughput rates to their
25325 state file (along with total usage, which was already saved)
25326 so that they can determine their correct estimated bandwidth on
25327 restart. Resolves bug 1863, where Tor relays would reset their
25328 estimated bandwidth to 0 after restarting.
25329 - Directory authorities now take changes in router IP address and
25330 ORPort into account when determining router stability. Previously,
25331 if a router changed its IP or ORPort, the authorities would not
25332 treat it as having any downtime for the purposes of stability
25333 calculation, whereas clients would experience downtime since the
25334 change could take a while to propagate to them. Resolves issue 1035.
25335 - Enable Address Space Layout Randomization (ASLR) and Data Execution
25336 Prevention (DEP) by default on Windows to make it harder for
25337 attackers to exploit vulnerabilities. Patch from John Brooks.
25339 o Minor bugfixes (on 0.2.1.x and earlier):
25340 - Fix a rare crash bug that could occur when a client was configured
25341 with a large number of bridges. Fixes bug 2629; bugfix on
25342 0.2.1.2-alpha. Bugfix by trac user "shitlei".
25343 - Avoid a double mark-for-free warning when failing to attach a
25344 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
25346 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
25347 found by "cypherpunks". This bug was introduced before the first
25348 Tor release, in svn commit r110.
25349 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
25350 don't mention them in the manpage. Fixes bug 2450; issue
25351 spotted by keb and G-Lo.
25352 - Fix a bug in bandwidth history state parsing that could have been
25353 triggered if a future version of Tor ever changed the timing
25354 granularity at which bandwidth history is measured. Bugfix on
25355 Tor 0.1.1.11-alpha.
25356 - When a relay decides that its DNS is too broken for it to serve
25357 as an exit server, it advertised itself as a non-exit, but
25358 continued to act as an exit. This could create accidental
25359 partitioning opportunities for users. Instead, if a relay is
25360 going to advertise reject *:* as its exit policy, it should
25361 really act with exit policy "reject *:*". Fixes bug 2366.
25362 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
25363 - In the special case where you configure a public exit relay as your
25364 bridge, Tor would be willing to use that exit relay as the last
25365 hop in your circuit as well. Now we fail that circuit instead.
25366 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
25367 - Fix a bug with our locking implementation on Windows that couldn't
25368 correctly detect when a file was already locked. Fixes bug 2504,
25369 bugfix on 0.2.1.6-alpha.
25370 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
25371 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
25373 - Set target port in get_interface_address6() correctly. Bugfix
25374 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
25375 - Directory authorities are now more robust to hops back in time
25376 when calculating router stability. Previously, if a run of uptime
25377 or downtime appeared to be negative, the calculation could give
25378 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
25380 - Fix an assert that got triggered when using the TestingTorNetwork
25381 configuration option and then issuing a GETINFO config-text control
25382 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
25384 o Minor bugfixes (on 0.2.2.x):
25385 - Clients should not weight BadExit nodes as Exits in their node
25386 selection. Similarly, directory authorities should not count BadExit
25387 bandwidth as Exit bandwidth when computing bandwidth-weights.
25388 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
25389 - Correctly clear our dir_read/dir_write history when there is an
25390 error parsing any bw history value from the state file. Bugfix on
25391 Tor 0.2.2.15-alpha.
25392 - Resolve a bug in verifying signatures of directory objects
25393 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
25394 Fixes bug 2409. Found by "piebeer".
25395 - Bridge authorities no longer crash on SIGHUP when they try to
25396 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
25400 - Log less aggressively about circuit timeout changes, and improve
25401 some other circuit timeout messages. Resolves bug 2004.
25402 - Log a little more clearly about the times at which we're no longer
25403 accepting new connections. Resolves bug 2181.
25404 - Reject attempts at the client side to open connections to private
25405 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
25406 a randomly chosen exit node. Attempts to do so are always
25407 ill-defined, generally prevented by exit policies, and usually
25408 in error. This will also help to detect loops in transparent
25409 proxy configurations. You can disable this feature by setting
25410 "ClientRejectInternalAddresses 0" in your torrc.
25411 - Always treat failure to allocate an RSA key as an unrecoverable
25413 - Update to the March 1 2011 Maxmind GeoLite Country database.
25415 o Minor features (log subsystem):
25416 - Add documentation for configuring logging at different severities in
25417 different log domains. We've had this feature since 0.2.1.1-alpha,
25418 but for some reason it never made it into the manpage. Fixes
25420 - Make it simpler to specify "All log domains except for A and B".
25421 Previously you needed to say "[*,~A,~B]". Now you can just say
25423 - Add a "LogMessageDomains 1" option to include the domains of log
25424 messages along with the messages. Without this, there's no way
25425 to use log domains without reading the source or doing a lot
25428 o Packaging changes:
25429 - Stop shipping the Tor specs files and development proposal documents
25430 in the tarball. They are now in a separate git repository at
25431 git://git.torproject.org/torspec.git
25434 Changes in version 0.2.1.30 - 2011-02-23
25435 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
25436 change is a slight tweak to Tor's TLS handshake that makes relays
25437 and bridges that run this new version reachable from Iran again.
25438 We don't expect this tweak will win the arms race long-term, but it
25439 buys us time until we roll out a better solution.
25442 - Stop sending a CLOCK_SKEW controller status event whenever
25443 we fetch directory information from a relay that has a wrong clock.
25444 Instead, only inform the controller when it's a trusted authority
25445 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
25446 the rest of bug 1074.
25447 - Fix a bounds-checking error that could allow an attacker to
25448 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
25449 Found by "piebeer".
25450 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
25451 Tor would ignore their RelayBandwidthBurst setting,
25452 potentially using more bandwidth than expected. Bugfix on
25453 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
25454 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
25455 hidserv" in her torrc. The 'hidserv' argument never controlled
25456 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
25459 - Adjust our TLS Diffie-Hellman parameters to match those used by
25461 - Update to the February 1 2011 Maxmind GeoLite Country database.
25464 - Check for and reject overly long directory certificates and
25465 directory tokens before they have a chance to hit any assertions.
25466 Bugfix on 0.2.1.28. Found by "doorss".
25467 - Bring the logic that gathers routerinfos and assesses the
25468 acceptability of circuits into line. This prevents a Tor OP from
25469 getting locked in a cycle of choosing its local OR as an exit for a
25470 path (due to a .exit request) and then rejecting the circuit because
25471 its OR is not listed yet. It also prevents Tor clients from using an
25472 OR running in the same instance as an exit (due to a .exit request)
25473 if the OR does not meet the same requirements expected of an OR
25474 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
25476 o Packaging changes:
25477 - Stop shipping the Tor specs files and development proposal documents
25478 in the tarball. They are now in a separate git repository at
25479 git://git.torproject.org/torspec.git
25480 - Do not include Git version tags as though they are SVN tags when
25481 generating a tarball from inside a repository that has switched
25482 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
25485 Changes in version 0.2.2.22-alpha - 2011-01-25
25486 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
25487 main other change is a slight tweak to Tor's TLS handshake that makes
25488 relays and bridges that run this new version reachable from Iran again.
25489 We don't expect this tweak will win the arms race long-term, but it
25490 will buy us a bit more time until we roll out a better solution.
25493 - Fix a bounds-checking error that could allow an attacker to
25494 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
25495 Found by "piebeer".
25496 - Don't assert when changing from bridge to relay or vice versa
25497 via the controller. The assert happened because we didn't properly
25498 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
25499 bug 2433. Reported by bastik.
25502 - Adjust our TLS Diffie-Hellman parameters to match those used by
25504 - Provide a log message stating which geoip file we're parsing
25505 instead of just stating that we're parsing the geoip file.
25506 Implements ticket 2432.
25509 - Check for and reject overly long directory certificates and
25510 directory tokens before they have a chance to hit any assertions.
25511 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
25514 Changes in version 0.2.2.21-alpha - 2011-01-15
25515 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
25516 continues our recent code security audit work. The main fix resolves
25517 a remote heap overflow vulnerability that can allow remote code
25518 execution (CVE-2011-0427). Other fixes address a variety of assert
25519 and crash bugs, most of which we think are hard to exploit remotely.
25521 o Major bugfixes (security), also included in 0.2.1.29:
25522 - Fix a heap overflow bug where an adversary could cause heap
25523 corruption. This bug probably allows remote code execution
25524 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
25526 - Prevent a denial-of-service attack by disallowing any
25527 zlib-compressed data whose compression factor is implausibly
25528 high. Fixes part of bug 2324; reported by "doorss".
25529 - Zero out a few more keys in memory before freeing them. Fixes
25530 bug 2384 and part of bug 2385. These key instances found by
25531 "cypherpunks", based on Andrew Case's report about being able
25532 to find sensitive data in Tor's memory space if you have enough
25533 permissions. Bugfix on 0.0.2pre9.
25535 o Major bugfixes (crashes), also included in 0.2.1.29:
25536 - Prevent calls to Libevent from inside Libevent log handlers.
25537 This had potential to cause a nasty set of crashes, especially
25538 if running Libevent with debug logging enabled, and running
25539 Tor with a controller watching for low-severity log messages.
25540 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
25541 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
25542 underflow errors there too. Fixes the other part of bug 2324.
25543 - Fix a bug where we would assert if we ever had a
25544 cached-descriptors.new file (or another file read directly into
25545 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
25546 on 0.2.1.25. Found by doorss.
25547 - Fix some potential asserts and parsing issues with grossly
25548 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
25551 o Minor bugfixes (other), also included in 0.2.1.29:
25552 - Fix a bug with handling misformed replies to reverse DNS lookup
25553 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
25554 bug reported by doorss.
25555 - Fix compilation on mingw when a pthreads compatibility library
25556 has been installed. (We don't want to use it, so we shouldn't
25557 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
25558 - Fix a bug where we would declare that we had run out of virtual
25559 addresses when the address space was only half-exhausted. Bugfix
25561 - Correctly handle the case where AutomapHostsOnResolve is set but
25562 no virtual addresses are available. Fixes bug 2328; bugfix on
25563 0.1.2.1-alpha. Bug found by doorss.
25564 - Correctly handle wrapping around when we run out of virtual
25565 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
25567 o Minor features, also included in 0.2.1.29:
25568 - Update to the January 1 2011 Maxmind GeoLite Country database.
25569 - Introduce output size checks on all of our decryption functions.
25571 o Build changes, also included in 0.2.1.29:
25572 - Tor does not build packages correctly with Automake 1.6 and earlier;
25573 added a check to Makefile.am to make sure that we're building with
25574 Automake 1.7 or later.
25575 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
25576 because we built it with a too-old version of automake. Thus that
25577 release broke ./configure --enable-openbsd-malloc, which is popular
25578 among really fast exit relays on Linux.
25580 o Major bugfixes, new in 0.2.2.21-alpha:
25581 - Prevent crash/heap corruption when the cbtnummodes consensus
25582 parameter is set to 0 or large values. Fixes bug 2317; bugfix
25585 o Major features, new in 0.2.2.21-alpha:
25586 - Introduce minimum/maximum values that clients will believe
25587 from the consensus. Now we'll have a better chance to avoid crashes
25588 or worse when a consensus param has a weird value.
25590 o Minor features, new in 0.2.2.21-alpha:
25591 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
25592 used on bridges, and it makes bridge scanning somewhat easier.
25593 - If writing the state file to disk fails, wait up to an hour before
25594 retrying again, rather than trying again each second. Fixes bug
25595 2346; bugfix on Tor 0.1.1.3-alpha.
25596 - Make Libevent log messages get delivered to controllers later,
25597 and not from inside the Libevent log handler. This prevents unsafe
25598 reentrant Libevent calls while still letting the log messages
25600 - Detect platforms that brokenly use a signed size_t, and refuse to
25601 build there. Found and analyzed by doorss and rransom.
25602 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
25605 o Minor bugfixes, new in 0.2.2.21-alpha:
25606 - Handle SOCKS messages longer than 128 bytes long correctly, rather
25607 than waiting forever for them to finish. Fixes bug 2330; bugfix
25608 on 0.2.0.16-alpha. Found by doorss.
25609 - Add assertions to check for overflow in arguments to
25610 base32_encode() and base32_decode(); fix a signed-unsigned
25611 comparison there too. These bugs are not actually reachable in Tor,
25612 but it's good to prevent future errors too. Found by doorss.
25613 - Correctly detect failures to create DNS requests when using Libevent
25614 versions before v2. (Before Libevent 2, we used our own evdns
25615 implementation. Its return values for Libevent's evdns_resolve_*()
25616 functions are not consistent with those from Libevent.) Fixes bug
25617 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
25619 o Documentation, new in 0.2.2.21-alpha:
25620 - Document the default socks host and port (127.0.0.1:9050) for
25624 Changes in version 0.2.1.29 - 2011-01-15
25625 Tor 0.2.1.29 continues our recent code security audit work. The main
25626 fix resolves a remote heap overflow vulnerability that can allow remote
25627 code execution. Other fixes address a variety of assert and crash bugs,
25628 most of which we think are hard to exploit remotely.
25630 o Major bugfixes (security):
25631 - Fix a heap overflow bug where an adversary could cause heap
25632 corruption. This bug probably allows remote code execution
25633 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
25635 - Prevent a denial-of-service attack by disallowing any
25636 zlib-compressed data whose compression factor is implausibly
25637 high. Fixes part of bug 2324; reported by "doorss".
25638 - Zero out a few more keys in memory before freeing them. Fixes
25639 bug 2384 and part of bug 2385. These key instances found by
25640 "cypherpunks", based on Andrew Case's report about being able
25641 to find sensitive data in Tor's memory space if you have enough
25642 permissions. Bugfix on 0.0.2pre9.
25644 o Major bugfixes (crashes):
25645 - Prevent calls to Libevent from inside Libevent log handlers.
25646 This had potential to cause a nasty set of crashes, especially
25647 if running Libevent with debug logging enabled, and running
25648 Tor with a controller watching for low-severity log messages.
25649 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
25650 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
25651 underflow errors there too. Fixes the other part of bug 2324.
25652 - Fix a bug where we would assert if we ever had a
25653 cached-descriptors.new file (or another file read directly into
25654 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
25655 on 0.2.1.25. Found by doorss.
25656 - Fix some potential asserts and parsing issues with grossly
25657 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
25660 o Minor bugfixes (other):
25661 - Fix a bug with handling misformed replies to reverse DNS lookup
25662 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
25663 bug reported by doorss.
25664 - Fix compilation on mingw when a pthreads compatibility library
25665 has been installed. (We don't want to use it, so we shouldn't
25666 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
25667 - Fix a bug where we would declare that we had run out of virtual
25668 addresses when the address space was only half-exhausted. Bugfix
25670 - Correctly handle the case where AutomapHostsOnResolve is set but
25671 no virtual addresses are available. Fixes bug 2328; bugfix on
25672 0.1.2.1-alpha. Bug found by doorss.
25673 - Correctly handle wrapping around to when we run out of virtual
25674 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
25675 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
25676 because we built it with a too-old version of automake. Thus that
25677 release broke ./configure --enable-openbsd-malloc, which is popular
25678 among really fast exit relays on Linux.
25681 - Update to the January 1 2011 Maxmind GeoLite Country database.
25682 - Introduce output size checks on all of our decryption functions.
25685 - Tor does not build packages correctly with Automake 1.6 and earlier;
25686 added a check to Makefile.am to make sure that we're building with
25687 Automake 1.7 or later.
25690 Changes in version 0.2.2.20-alpha - 2010-12-17
25691 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
25692 exploitable bugs. We also fix a variety of other significant bugs,
25693 change the IP address for one of our directory authorities, and update
25694 the minimum version that Tor relays must run to join the network.
25697 - Fix a remotely exploitable bug that could be used to crash instances
25698 of Tor remotely by overflowing on the heap. Remote-code execution
25699 hasn't been confirmed, but can't be ruled out. Everyone should
25700 upgrade. Bugfix on the 0.1.1 series and later.
25701 - Fix a bug that could break accounting on 64-bit systems with large
25702 time_t values, making them hibernate for impossibly long intervals.
25703 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
25704 - Fix a logic error in directory_fetches_from_authorities() that
25705 would cause all _non_-exits refusing single-hop-like circuits
25706 to fetch from authorities, when we wanted to have _exits_ fetch
25707 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
25709 - Fix a stream fairness bug that would cause newer streams on a given
25710 circuit to get preference when reading bytes from the origin or
25711 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
25712 introduced before the first Tor release, in svn revision r152.
25714 o Directory authority changes:
25715 - Change IP address and ports for gabelmoo (v3 directory authority).
25718 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
25719 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
25720 - Fix an off-by-one error in calculating some controller command
25721 argument lengths. Fortunately, this mistake is harmless since
25722 the controller code does redundant NUL termination too. Found by
25723 boboper. Bugfix on 0.1.1.1-alpha.
25724 - Do not dereference NULL if a bridge fails to build its
25725 extra-info descriptor. Found by an anonymous commenter on
25726 Trac. Bugfix on 0.2.2.19-alpha.
25729 - Update to the December 1 2010 Maxmind GeoLite Country database.
25730 - Directory authorities now reject relays running any versions of
25731 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
25732 known bugs that keep RELAY_EARLY cells from working on rendezvous
25733 circuits. Followup to fix for bug 2081.
25734 - Directory authorities now reject relays running any version of Tor
25735 older than 0.2.0.26-rc. That version is the earliest that fetches
25736 current directory information correctly. Fixes bug 2156.
25737 - Report only the top 10 ports in exit-port stats in order not to
25738 exceed the maximum extra-info descriptor length of 50 KB. Implements
25742 Changes in version 0.2.1.28 - 2010-12-17
25743 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
25744 exploitable bugs. We also took this opportunity to change the IP address
25745 for one of our directory authorities, and to update the geoip database
25749 - Fix a remotely exploitable bug that could be used to crash instances
25750 of Tor remotely by overflowing on the heap. Remote-code execution
25751 hasn't been confirmed, but can't be ruled out. Everyone should
25752 upgrade. Bugfix on the 0.1.1 series and later.
25754 o Directory authority changes:
25755 - Change IP address and ports for gabelmoo (v3 directory authority).
25758 - Update to the December 1 2010 Maxmind GeoLite Country database.
25761 Changes in version 0.2.1.27 - 2010-11-23
25762 Yet another OpenSSL security patch broke its compatibility with Tor:
25763 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
25764 also took this opportunity to fix several crash bugs, integrate a new
25765 directory authority, and update the bundled GeoIP database.
25768 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
25769 No longer set the tlsext_host_name extension on server SSL objects;
25770 but continue to set it on client SSL objects. Our goal in setting
25771 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
25772 bugfix on 0.2.1.1-alpha.
25773 - Do not log messages to the controller while shrinking buffer
25774 freelists. Doing so would sometimes make the controller connection
25775 try to allocate a buffer chunk, which would mess up the internals
25776 of the freelist and cause an assertion failure. Fixes bug 1125;
25777 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
25778 - Learn our external IP address when we're a relay or bridge, even if
25779 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
25780 where we introduced bridge relays that don't need to publish to
25781 be useful. Fixes bug 2050.
25782 - Do even more to reject (and not just ignore) annotations on
25783 router descriptors received anywhere but from the cache. Previously
25784 we would ignore such annotations at first, but cache them to disk
25785 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
25786 - When you're using bridges and your network goes away and your
25787 bridges get marked as down, recover when you attempt a new socks
25788 connection (if the network is back), rather than waiting up to an
25789 hour to try fetching new descriptors for your bridges. Bugfix on
25790 0.2.0.3-alpha; fixes bug 1981.
25793 - Move to the November 2010 Maxmind GeoLite country db (rather
25794 than the June 2009 ip-to-country GeoIP db) for our statistics that
25795 count how many users relays are seeing from each country. Now we'll
25796 have more accurate data, especially for many African countries.
25798 o New directory authorities:
25799 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
25803 - Fix an assertion failure that could occur in directory caches or
25804 bridge users when using a very short voting interval on a testing
25805 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
25807 - Enforce multiplicity rules when parsing annotations. Bugfix on
25808 0.2.0.8-alpha. Found by piebeer.
25809 - Allow handshaking OR connections to take a full KeepalivePeriod
25810 seconds to handshake. Previously, we would close them after
25811 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
25812 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
25814 - When building with --enable-gcc-warnings on OpenBSD, disable
25815 warnings in system headers. This makes --enable-gcc-warnings
25816 pass on OpenBSD 4.8.
25819 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
25820 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
25821 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
25822 Servers can start sending this code when enough clients recognize
25823 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
25824 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
25825 Patch from mingw-san.
25828 - Remove the old debian/ directory from the main Tor distribution.
25829 The official Tor-for-debian git repository lives at the URL
25830 https://git.torproject.org/debian/tor.git
25831 - Stop shipping the old doc/website/ directory in the tarball. We
25832 changed the website format in late 2010, and what we shipped in
25833 0.2.1.26 really wasn't that useful anyway.
25836 Changes in version 0.2.2.19-alpha - 2010-11-22
25837 Yet another OpenSSL security patch broke its compatibility with Tor:
25838 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
25841 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
25842 No longer set the tlsext_host_name extension on server SSL objects;
25843 but continue to set it on client SSL objects. Our goal in setting
25844 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
25845 bugfix on 0.2.1.1-alpha.
25848 - Try harder not to exceed the maximum length of 50 KB when writing
25849 statistics to extra-info descriptors. This bug was triggered by very
25850 fast relays reporting exit-port, entry, and dirreq statistics.
25851 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
25852 - Publish a router descriptor even if generating an extra-info
25853 descriptor fails. Previously we would not publish a router
25854 descriptor without an extra-info descriptor; this can cause fast
25855 exit relays collecting exit-port statistics to drop from the
25856 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
25859 Changes in version 0.2.2.18-alpha - 2010-11-16
25860 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
25861 us lately, makes unpublished bridge relays able to detect their IP
25862 address, and fixes a wide variety of other bugs to get us much closer
25863 to a stable release.
25866 - Do even more to reject (and not just ignore) annotations on
25867 router descriptors received anywhere but from the cache. Previously
25868 we would ignore such annotations at first, but cache them to disk
25869 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
25870 - Do not log messages to the controller while shrinking buffer
25871 freelists. Doing so would sometimes make the controller connection
25872 try to allocate a buffer chunk, which would mess up the internals
25873 of the freelist and cause an assertion failure. Fixes bug 1125;
25874 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
25875 - Learn our external IP address when we're a relay or bridge, even if
25876 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
25877 where we introduced bridge relays that don't need to publish to
25878 be useful. Fixes bug 2050.
25879 - Maintain separate TLS contexts and certificates for incoming and
25880 outgoing connections in bridge relays. Previously we would use the
25881 same TLS contexts and certs for incoming and outgoing connections.
25882 Bugfix on 0.2.0.3-alpha; addresses bug 988.
25883 - Maintain separate identity keys for incoming and outgoing TLS
25884 contexts in bridge relays. Previously we would use the same
25885 identity keys for incoming and outgoing TLS contexts. Bugfix on
25886 0.2.0.3-alpha; addresses the other half of bug 988.
25887 - Avoid an assertion failure when we as an authority receive a
25888 duplicate upload of a router descriptor that we already have,
25889 but which we previously considered an obsolete descriptor.
25890 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
25891 - Avoid a crash bug triggered by looking at a dangling pointer while
25892 setting the network status consensus. Found by Robert Ransom.
25893 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
25894 - Fix a logic error where servers that _didn't_ act as exits would
25895 try to keep their server lists more aggressively up to date than
25896 exits, when it was supposed to be the other way around. Bugfix
25899 o Minor bugfixes (on Tor 0.2.1.x and earlier):
25900 - When we're trying to guess whether we know our IP address as
25901 a relay, we would log various ways that we failed to guess
25902 our address, but never log that we ended up guessing it
25903 successfully. Now add a log line to help confused and anxious
25904 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
25905 - Bring the logic that gathers routerinfos and assesses the
25906 acceptability of circuits into line. This prevents a Tor OP from
25907 getting locked in a cycle of choosing its local OR as an exit for a
25908 path (due to a .exit request) and then rejecting the circuit because
25909 its OR is not listed yet. It also prevents Tor clients from using an
25910 OR running in the same instance as an exit (due to a .exit request)
25911 if the OR does not meet the same requirements expected of an OR
25912 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
25913 - Correctly describe errors that occur when generating a TLS object.
25914 Previously we would attribute them to a failure while generating a
25915 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
25917 - Enforce multiplicity rules when parsing annotations. Bugfix on
25918 0.2.0.8-alpha. Found by piebeer.
25919 - Fix warnings that newer versions of autoconf produced during
25920 ./autogen.sh. These warnings appear to be harmless in our case,
25921 but they were extremely verbose. Fixes bug 2020.
25923 o Minor bugfixes (on Tor 0.2.2.x):
25924 - Enable protection of small arrays whenever we build with gcc
25925 hardening features, not only when also building with warnings
25926 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
25929 - Make hidden services work better in private Tor networks by not
25930 requiring any uptime to join the hidden service descriptor
25931 DHT. Implements ticket 2088.
25932 - Rate-limit the "your application is giving Tor only an IP address"
25933 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
25934 - When AllowSingleHopExits is set, print a warning to explain to the
25935 relay operator why most clients are avoiding her relay.
25936 - Update to the November 1 2010 Maxmind GeoLite Country database.
25938 o Code simplifications and refactoring:
25939 - When we fixed bug 1038 we had to put in a restriction not to send
25940 RELAY_EARLY cells on rend circuits. This was necessary as long
25941 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
25942 active. Now remove this obsolete check. Resolves bug 2081.
25943 - Some options used different conventions for uppercasing of acronyms
25944 when comparing manpage and source. Fix those in favor of the
25945 manpage, as it makes sense to capitalize acronyms.
25946 - Remove the torrc.complete file. It hasn't been kept up to date
25947 and users will have better luck checking out the manpage.
25948 - Remove the obsolete "NoPublish" option; it has been flagged
25949 as obsolete and has produced a warning since 0.1.1.18-rc.
25950 - Remove everything related to building the expert bundle for OS X.
25951 It has confused many users, doesn't work right on OS X 10.6,
25952 and is hard to get rid of once installed. Resolves bug 1274.
25955 Changes in version 0.2.2.17-alpha - 2010-09-30
25956 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
25957 to use one-hop circuits (which can put the exit relays at higher risk,
25958 plus unbalance the network); fixes a big bug in bandwidth accounting
25959 for relays that want to limit their monthly bandwidth use; fixes a
25960 big pile of bugs in how clients tolerate temporary network failure;
25961 and makes our adaptive circuit build timeout feature (which improves
25962 client performance if your network is fast while not breaking things
25963 if your network is slow) better handle bad networks.
25966 - Exit relays now try harder to block exit attempts from unknown
25967 relays, to make it harder for people to use them as one-hop proxies
25968 a la tortunnel. Controlled by the refuseunknownexits consensus
25969 parameter (currently enabled), or you can override it on your
25970 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
25972 o Major bugfixes (0.2.1.x and earlier):
25973 - Fix a bug in bandwidth accounting that could make us use twice
25974 the intended bandwidth when our interval start changes due to
25975 daylight saving time. Now we tolerate skew in stored vs computed
25976 interval starts: if the start of the period changes by no more than
25977 50% of the period's duration, we remember bytes that we transferred
25978 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
25979 - Always search the Windows system directory for system DLLs, and
25980 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
25981 - When you're using bridges and your network goes away and your
25982 bridges get marked as down, recover when you attempt a new socks
25983 connection (if the network is back), rather than waiting up to an
25984 hour to try fetching new descriptors for your bridges. Bugfix on
25985 0.2.0.3-alpha; fixes bug 1981.
25987 o Major bugfixes (on 0.2.2.x):
25988 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
25990 - Fix a segfault that could happen when operating a bridge relay with
25991 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
25992 - The consensus bandwidth-weights (used by clients to choose fast
25993 relays) entered an unexpected edge case in September where
25994 Exits were much scarcer than Guards, resulting in bad weight
25995 recommendations. Now we compute them using new constraints that
25996 should succeed in all cases. Also alter directory authorities to
25997 not include the bandwidth-weights line if they fail to produce
25998 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
25999 - When weighting bridges during path selection, we used to trust
26000 the bandwidths they provided in their descriptor, only capping them
26001 at 10MB/s. This turned out to be problematic for two reasons:
26002 Bridges could claim to handle a lot more traffic then they
26003 actually would, thus making more clients pick them and have a
26004 pretty effective DoS attack. The other issue is that new bridges
26005 that might not have a good estimate for their bw capacity yet
26006 would not get used at all unless no other bridges are available
26007 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
26009 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
26010 - Ignore cannibalized circuits when recording circuit build times.
26011 This should provide for a minor performance improvement for hidden
26012 service users using 0.2.2.14-alpha, and should remove two spurious
26013 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
26014 - Simplify the logic that causes us to decide if the network is
26015 unavailable for purposes of recording circuit build times. If we
26016 receive no cells whatsoever for the entire duration of a circuit's
26017 full measured lifetime, the network is probably down. Also ignore
26018 one-hop directory fetching circuit timeouts when calculating our
26019 circuit build times. These changes should hopefully reduce the
26020 cases where we see ridiculous circuit build timeouts for people
26021 with spotty wireless connections. Fixes part of bug 1772; bugfix
26023 - Prevent the circuit build timeout from becoming larger than
26024 the maximum build time we have ever seen. Also, prevent the time
26025 period for measurement circuits from becoming larger than twice that
26026 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
26029 - When we run out of directory information such that we can't build
26030 circuits, but then get enough that we can build circuits, log when
26031 we actually construct a circuit, so the user has a better chance of
26032 knowing what's going on. Fixes bug 1362.
26033 - Be more generous with how much bandwidth we'd use up (with
26034 accounting enabled) before entering "soft hibernation". Previously,
26035 we'd refuse new connections and circuits once we'd used up 95% of
26036 our allotment. Now, we use up 95% of our allotment, AND make sure
26037 that we have no more than 500MB (or 3 hours of expected traffic,
26038 whichever is lower) remaining before we enter soft hibernation.
26039 - If we've configured EntryNodes and our network goes away and/or all
26040 our entrynodes get marked down, optimistically retry them all when
26041 a new socks application request appears. Fixes bug 1882.
26042 - Add some more defensive programming for architectures that can't
26043 handle unaligned integer accesses. We don't know of any actual bugs
26044 right now, but that's the best time to fix them. Fixes bug 1943.
26045 - Support line continuations in the torrc config file. If a line
26046 ends with a single backslash character, the newline is ignored, and
26047 the configuration value is treated as continuing on the next line.
26050 o Minor bugfixes (on 0.2.1.x and earlier):
26051 - For bandwidth accounting, calculate our expected bandwidth rate
26052 based on the time during which we were active and not in
26053 soft-hibernation during the last interval. Previously, we were
26054 also considering the time spent in soft-hibernation. If this
26055 was a long time, we would wind up underestimating our bandwidth
26056 by a lot, and skewing our wakeup time towards the start of the
26057 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
26059 o Minor bugfixes (on 0.2.2.x):
26060 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
26061 which were disabled by the circuit build timeout changes in
26062 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
26063 - Make sure we don't warn about missing bandwidth weights when
26064 choosing bridges or other relays not in the consensus. Bugfix on
26065 0.2.2.10-alpha; fixes bug 1805.
26066 - In our logs, do not double-report signatures from unrecognized
26067 authorities both as "from unknown authority" and "not
26068 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
26071 Changes in version 0.2.2.16-alpha - 2010-09-17
26072 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
26073 evident at exit relays), and also continues to resolve all the little
26074 bugs that have been filling up trac lately.
26076 o Major bugfixes (stream-level fairness):
26077 - When receiving a circuit-level SENDME for a blocked circuit, try
26078 to package cells fairly from all the streams that had previously
26079 been blocked on that circuit. Previously, we had started with the
26080 oldest stream, and allowed each stream to potentially exhaust
26081 the circuit's package window. This gave older streams on any
26082 given circuit priority over newer ones. Fixes bug 1937. Detected
26083 originally by Camilo Viecco. This bug was introduced before the
26084 first Tor release, in svn commit r152: it is the new winner of
26085 the longest-lived bug prize.
26086 - When the exit relay got a circuit-level sendme cell, it started
26087 reading on the exit streams, even if had 500 cells queued in the
26088 circuit queue already, so the circuit queue just grew and grew in
26089 some cases. We fix this by not re-enabling reading on receipt of a
26090 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
26091 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
26093 - Newly created streams were allowed to read cells onto circuits,
26094 even if the circuit's cell queue was blocked and waiting to drain.
26095 This created potential unfairness, as older streams would be
26096 blocked, but newer streams would gladly fill the queue completely.
26097 We add code to detect this situation and prevent any stream from
26098 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
26102 - Update to the September 1 2010 Maxmind GeoLite Country database.
26103 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
26104 not. This would lead to a cookie that is still not group readable.
26105 Closes bug 1843. Suggested by katmagic.
26106 - When logging a rate-limited warning, we now mention how many messages
26107 got suppressed since the last warning.
26108 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
26109 do individual connection-level rate limiting of clients. The torrc
26110 config options with the same names trump the consensus params, if
26111 both are present. Replaces the old "bwconnrate" and "bwconnburst"
26112 consensus params which were broken from 0.2.2.7-alpha through
26113 0.2.2.14-alpha. Closes bug 1947.
26114 - When a router changes IP address or port, authorities now launch
26115 a new reachability test for it. Implements ticket 1899.
26116 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
26117 2 no signature, 4 required" messages about consensus signatures
26118 easier to read, and make sure they get logged at the same severity
26119 as the messages explaining which keys are which. Fixes bug 1290.
26120 - Don't warn when we have a consensus that we can't verify because
26121 of missing certificates, unless those certificates are ones
26122 that we have been trying and failing to download. Fixes bug 1145.
26123 - If you configure your bridge with a known identity fingerprint,
26124 and the bridge authority is unreachable (as it is in at least
26125 one country now), fall back to directly requesting the descriptor
26126 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
26128 - When building with --enable-gcc-warnings on OpenBSD, disable
26129 warnings in system headers. This makes --enable-gcc-warnings
26130 pass on OpenBSD 4.8.
26132 o Minor bugfixes (on 0.2.1.x and earlier):
26133 - Authorities will now attempt to download consensuses if their
26134 own efforts to make a live consensus have failed. This change
26135 means authorities that restart will fetch a valid consensus, and
26136 it means authorities that didn't agree with the current consensus
26137 will still fetch and serve it if it has enough signatures. Bugfix
26138 on 0.2.0.9-alpha; fixes bug 1300.
26139 - Ensure DNS requests launched by "RESOLVE" commands from the
26140 controller respect the __LeaveStreamsUnattached setconf options. The
26141 same goes for requests launched via DNSPort or transparent
26142 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
26143 - Allow handshaking OR connections to take a full KeepalivePeriod
26144 seconds to handshake. Previously, we would close them after
26145 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
26146 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
26148 - Rate-limit "Failed to hand off onionskin" warnings.
26149 - Never relay a cell for a circuit we have already destroyed.
26150 Between marking a circuit as closeable and finally closing it,
26151 it may have been possible for a few queued cells to get relayed,
26152 even though they would have been immediately dropped by the next
26153 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
26154 - Never queue a cell for a circuit that's already been marked
26156 - Never vote for a server as "Running" if we have a descriptor for
26157 it claiming to be hibernating, and that descriptor was published
26158 more recently than our last contact with the server. Bugfix on
26159 0.2.0.3-alpha; fixes bug 911.
26160 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
26163 o Minor bugfixes (on 0.2.2.x):
26164 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
26165 down if a directory fetch fails and you've configured either
26166 bridges or EntryNodes. The intent was to mark the relay as down
26167 _unless_ you're using bridges or EntryNodes, since if you are
26168 then you could quickly run out of entry points.
26169 - Fix the Windows directory-listing code. A bug introduced in
26170 0.2.2.14-alpha could make Windows directory servers forget to load
26171 some of their cached v2 networkstatus files.
26172 - Really allow clients to use relays as bridges. Fixes bug 1776;
26173 bugfix on 0.2.2.15-alpha.
26174 - Demote a warn to info that happens when the CellStatistics option
26175 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
26176 Reported by Moritz Bartl.
26177 - On Windows, build correctly either with or without Unicode support.
26178 This is necessary so that Tor can support fringe platforms like
26179 Windows 98 (which has no Unicode), or Windows CE (which has no
26180 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
26183 - Add a unit test for cross-platform directory-listing code.
26186 Changes in version 0.2.2.15-alpha - 2010-08-18
26187 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
26188 fixes a variety of other bugs that were preventing performance
26189 experiments from moving forward, fixes several bothersome memory leaks,
26190 and generally closes a lot of smaller bugs that have been filling up
26194 - Stop assigning the HSDir flag to relays that disable their
26195 DirPort (and thus will refuse to answer directory requests). This
26196 fix should dramatically improve the reachability of hidden services:
26197 hidden services and hidden service clients pick six HSDir relays
26198 to store and retrieve the hidden service descriptor, and currently
26199 about half of the HSDir relays will refuse to work. Bugfix on
26200 0.2.0.10-alpha; fixes part of bug 1693.
26201 - The PerConnBWRate and Burst config options, along with the
26202 bwconnrate and bwconnburst consensus params, initialized each conn's
26203 token bucket values only when the connection is established. Now we
26204 update them if the config options change, and update them every time
26205 we get a new consensus. Otherwise we can encounter an ugly edge
26206 case where we initialize an OR conn to client-level bandwidth,
26207 but then later the relay joins the consensus and we leave it
26208 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
26209 - Fix a regression that caused Tor to rebind its ports if it receives
26210 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
26213 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
26214 should give us approximately 40-50% more Guard-flagged nodes,
26215 improving the anonymity the Tor network can provide and also
26216 decreasing the dropoff in throughput that relays experience when
26217 they first get the Guard flag.
26218 - Allow enabling or disabling the *Statistics config options while
26222 - Update to the August 1 2010 Maxmind GeoLite Country database.
26223 - Have the controller interface give a more useful message than
26224 "Internal Error" in response to failed GETINFO requests.
26225 - Warn when the same option is provided more than once in a torrc
26226 file, on the command line, or in a single SETCONF statement, and
26227 the option is one that only accepts a single line. Closes bug 1384.
26228 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
26229 Patch from mingw-san.
26230 - Add support for the country code "{??}" in torrc options like
26231 ExcludeNodes, to indicate all routers of unknown country. Closes
26233 - Relays report the number of bytes spent on answering directory
26234 requests in extra-info descriptors similar to {read,write}-history.
26235 Implements enhancement 1790.
26237 o Minor bugfixes (on 0.2.1.x and earlier):
26238 - Complain if PublishServerDescriptor is given multiple arguments that
26239 include 0 or 1. This configuration will be rejected in the future.
26240 Bugfix on 0.2.0.1-alpha; closes bug 1107.
26241 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
26242 Bugfix on 0.2.0.13-alpha; closes bug 928.
26243 - Change "Application request when we're believed to be offline."
26244 notice to "Application request when we haven't used client
26245 functionality lately.", to clarify that it's not an error. Bugfix
26246 on 0.0.9.3; fixes bug 1222.
26247 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
26248 would return "551 Internal error" rather than "552 Unrecognized key
26249 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
26250 - Users can't configure a regular relay to be their bridge. It didn't
26251 work because when Tor fetched the bridge descriptor, it found
26252 that it already had it, and didn't realize that the purpose of the
26253 descriptor had changed. Now we replace routers with a purpose other
26254 than bridge with bridge descriptors when fetching them. Bugfix on
26255 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
26256 refetch the descriptor with router purpose 'general', disabling
26258 - Fix a rare bug in rend_fn unit tests: we would fail a test when
26259 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
26260 on 0.2.0.10-alpha; fixes bug 1808.
26261 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
26262 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
26263 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
26264 Servers can start sending this code when enough clients recognize
26265 it. Also update the spec to reflect this new reason. Bugfix on
26266 0.1.0.1-rc; fixes part of bug 1793.
26267 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
26268 when we switch from being a public relay to a bridge. Otherwise
26269 there will still be clients that see the relay in their consensus,
26270 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
26272 - Instead of giving an assertion failure on an internal mismatch
26273 on estimated freelist size, just log a BUG warning and try later.
26274 Mitigates but does not fix bug 1125.
26275 - Fix an assertion failure that could occur in caches or bridge users
26276 when using a very short voting interval on a testing network.
26277 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
26279 o Minor bugfixes (on 0.2.2.x):
26280 - Alter directory authorities to always consider Exit-flagged nodes
26281 as potential Guard nodes in their votes. The actual decision to
26282 use Exits as Guards is done in the consensus bandwidth weights.
26283 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
26284 - When the controller is reporting the purpose of circuits that
26285 didn't finish building before the circuit build timeout, it was
26286 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
26287 - Our libevent version parsing code couldn't handle versions like
26288 1.4.14b-stable and incorrectly warned the user about using an
26289 old and broken version of libevent. Treat 1.4.14b-stable like
26290 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
26292 - Don't use substitution references like $(VAR:MOD) when
26293 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
26294 '$(:x)' to 'x' rather than the empty string. This bites us in
26295 doc/ when configured with --disable-asciidoc. Bugfix on
26296 0.2.2.9-alpha; fixes bug 1773.
26297 - Remove a spurious hidden service server-side log notice about
26298 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
26300 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
26302 - Correctly report written bytes on linked connections. Found while
26303 implementing 1790. Bugfix on 0.2.2.4-alpha.
26304 - Fix three memory leaks: one in circuit_build_times_parse_state(),
26305 one in dirvote_add_signatures_to_pending_consensus(), and one every
26306 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
26307 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
26309 o Code simplifications and refactoring:
26310 - Take a first step towards making or.h smaller by splitting out
26311 function definitions for all source files in src/or/. Leave
26312 structures and defines in or.h for now.
26313 - Remove a bunch of unused function declarations as well as a block of
26314 #if 0'd code from the unit tests. Closes bug 1824.
26315 - New unit tests for exit-port history statistics; refactored exit
26316 statistics code to be more easily tested.
26317 - Remove the old debian/ directory from the main Tor distribution.
26318 The official Tor-for-debian git repository lives at the URL
26319 https://git.torproject.org/debian/tor.git
26322 Changes in version 0.2.2.14-alpha - 2010-07-12
26323 Tor 0.2.2.14-alpha greatly improves client-side handling of
26324 circuit build timeouts, which are used to estimate speed and improve
26325 performance. We also move to a much better GeoIP database, port Tor to
26326 Windows CE, introduce new compile flags that improve code security,
26327 add an eighth v3 directory authority, and address a lot of more
26331 - Tor directory authorities no longer crash when started with a
26332 cached-microdesc-consensus file in their data directory. Bugfix
26333 on 0.2.2.6-alpha; fixes bug 1532.
26334 - Treat an unset $HOME like an empty $HOME rather than triggering an
26335 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
26336 - Ignore negative and large circuit build timeout values that can
26337 happen during a suspend or hibernate. These values caused various
26338 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
26339 - Alter calculation of Pareto distribution parameter 'Xm' for
26340 Circuit Build Timeout learning to use the weighted average of the
26341 top N=3 modes (because we have three entry guards). Considering
26342 multiple modes should improve the timeout calculation in some cases,
26343 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
26345 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
26346 right censored distribution model. This approach improves over the
26347 synthetic timeout generation approach that was producing insanely
26348 high timeout values. Now we calculate build timeouts using truncated
26349 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
26350 - Do not close circuits that are under construction when they reach
26351 the circuit build timeout. Instead, leave them building (but do not
26352 use them) for up until the time corresponding to the 95th percentile
26353 on the Pareto CDF or 60 seconds, whichever is greater. This is done
26354 to provide better data for the new Pareto model. This percentile
26355 can be controlled by the consensus.
26358 - Move to the June 2010 Maxmind GeoLite country db (rather than the
26359 June 2009 ip-to-country GeoIP db) for our statistics that count
26360 how many users relays are seeing from each country. Now we have
26361 more accurate data for many African countries.
26362 - Port Tor to build and run correctly on Windows CE systems, using
26363 the wcecompat library. Contributed by Valerio Lupi.
26364 - New "--enable-gcc-hardening" ./configure flag (off by default)
26365 to turn on gcc compile time hardening options. It ensures
26366 that signed ints have defined behavior (-fwrapv), enables
26367 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
26368 with canaries (-fstack-protector-all), turns on ASLR protection if
26369 supported by the kernel (-fPIE, -pie), and adds additional security
26370 related warnings. Verified to work on Mac OS X and Debian Lenny.
26371 - New "--enable-linker-hardening" ./configure flag (off by default)
26372 to turn on ELF specific hardening features (relro, now). This does
26373 not work with Mac OS X or any other non-ELF binary format.
26375 o New directory authorities:
26376 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
26380 - New config option "WarnUnsafeSocks 0" disables the warning that
26381 occurs whenever Tor receives a socks handshake using a version of
26382 the socks protocol that can only provide an IP address (rather
26383 than a hostname). Setups that do DNS locally over Tor are fine,
26384 and we shouldn't spam the logs in that case.
26385 - Convert the HACKING file to asciidoc, and add a few new sections
26386 to it, explaining how we use Git, how we make changelogs, and
26387 what should go in a patch.
26388 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
26389 event, to give information on the current rate of circuit timeouts
26390 over our stored history.
26391 - Add ability to disable circuit build time learning via consensus
26392 parameter and via a LearnCircuitBuildTimeout config option. Also
26393 automatically disable circuit build time calculation if we are
26394 either a AuthoritativeDirectory, or if we fail to write our state
26395 file. Fixes bug 1296.
26396 - More gracefully handle corrupt state files, removing asserts
26397 in favor of saving a backup and resetting state.
26398 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
26402 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
26404 - When a2x fails, mention that the user could disable manpages instead
26405 of trying to fix their asciidoc installation.
26406 - Where available, use Libevent 2.0's periodic timers so that our
26407 once-per-second cleanup code gets called even more closely to
26408 once per second than it would otherwise. Fixes bug 943.
26409 - If you run a bridge that listens on multiple IP addresses, and
26410 some user configures a bridge address that uses a different IP
26411 address than your bridge writes in its router descriptor, and the
26412 user doesn't specify an identity key, their Tor would discard the
26413 descriptor because "it isn't one of our configured bridges", and
26414 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
26415 Bugfix on 0.2.0.3-alpha.
26416 - If OpenSSL fails to make a duplicate of a private or public key, log
26417 an error message and try to exit cleanly. May help with debugging
26418 if bug 1209 ever remanifests.
26419 - Save a couple bytes in memory allocation every time we escape
26420 certain characters in a string. Patch from Florian Zumbiehl.
26421 - Make it explicit that we don't cannibalize one-hop circuits. This
26422 happens in the wild, but doesn't turn out to be a problem because
26423 we fortunately don't use those circuits. Many thanks to outofwords
26424 for the initial analysis and to swissknife who confirmed that
26425 two-hop circuits are actually created.
26426 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
26427 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
26428 - Eliminate a case where a circuit build time warning was displayed
26429 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
26432 Changes in version 0.2.1.26 - 2010-05-02
26433 Tor 0.2.1.26 addresses the recent connection and memory overload
26434 problems we've been seeing on relays, especially relays with their
26435 DirPort open. If your relay has been crashing, or you turned it off
26436 because it used too many resources, give this release a try.
26438 This release also fixes yet another instance of broken OpenSSL libraries
26439 that was causing some relays to drop out of the consensus.
26442 - Teach relays to defend themselves from connection overload. Relays
26443 now close idle circuits early if it looks like they were intended
26444 for directory fetches. Relays are also more aggressive about closing
26445 TLS connections that have no circuits on them. Such circuits are
26446 unlikely to be re-used, and tens of thousands of them were piling
26447 up at the fast relays, causing the relays to run out of sockets
26448 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
26449 their directory fetches over TLS).
26450 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
26451 that claim to be earlier than 0.9.8m, but which have in reality
26452 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
26453 behavior. Possible fix for some cases of bug 1346.
26454 - Directory mirrors were fetching relay descriptors only from v2
26455 directory authorities, rather than v3 authorities like they should.
26456 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
26457 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
26460 - Finally get rid of the deprecated and now harmful notion of "clique
26461 mode", where directory authorities maintain TLS connections to
26465 - In the util/threads test, no longer free the test_mutex before all
26466 worker threads have finished. Bugfix on 0.2.1.6-alpha.
26467 - The master thread could starve the worker threads quite badly on
26468 certain systems, causing them to run only partially in the allowed
26469 window. This resulted in test failures. Now the master thread sleeps
26470 occasionally for a few microseconds while the two worker-threads
26471 compete for the mutex. Bugfix on 0.2.0.1-alpha.
26474 Changes in version 0.2.2.13-alpha - 2010-04-24
26475 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
26476 problems we've been seeing on relays, especially relays with their
26477 DirPort open. If your relay has been crashing, or you turned it off
26478 because it used too many resources, give this release a try.
26481 - Teach relays to defend themselves from connection overload. Relays
26482 now close idle circuits early if it looks like they were intended
26483 for directory fetches. Relays are also more aggressive about closing
26484 TLS connections that have no circuits on them. Such circuits are
26485 unlikely to be re-used, and tens of thousands of them were piling
26486 up at the fast relays, causing the relays to run out of sockets
26487 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
26488 their directory fetches over TLS).
26491 - Finally get rid of the deprecated and now harmful notion of "clique
26492 mode", where directory authorities maintain TLS connections to
26494 - Directory authorities now do an immediate reachability check as soon
26495 as they hear about a new relay. This change should slightly reduce
26496 the time between setting up a relay and getting listed as running
26497 in the consensus. It should also improve the time between setting
26498 up a bridge and seeing use by bridge users.
26499 - Directory authorities no longer launch a TLS connection to every
26500 relay as they startup. Now that we have 2k+ descriptors cached,
26501 the resulting network hiccup is becoming a burden. Besides,
26502 authorities already avoid voting about Running for the first half
26503 hour of their uptime.
26506 Changes in version 0.2.2.12-alpha - 2010-04-20
26507 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
26508 handle and vote on descriptors. It was causing relays to drop out of
26512 - Many relays have been falling out of the consensus lately because
26513 not enough authorities know about their descriptor for them to get
26514 a majority of votes. When we deprecated the v2 directory protocol,
26515 we got rid of the only way that v3 authorities can hear from each
26516 other about other descriptors. Now authorities examine every v3
26517 vote for new descriptors, and fetch them from that authority. Bugfix
26519 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
26520 and a warning in or.h related to bandwidth_weight_rule_t that
26521 prevented clean compile on OS X. Fixes bug 1363; bugfix on
26523 - Fix a segfault on relays when DirReqStatistics is enabled
26524 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
26528 - Demote a confusing TLS warning that relay operators might get when
26529 someone tries to talk to their OrPort. It is neither the operator's
26530 fault nor can they do anything about it. Fixes bug 1364; bugfix
26534 Changes in version 0.2.2.11-alpha - 2010-04-15
26535 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
26536 libraries that was causing some relays to drop out of the consensus.
26539 - Directory mirrors were fetching relay descriptors only from v2
26540 directory authorities, rather than v3 authorities like they should.
26541 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
26542 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
26543 - Fix a parsing error that made every possible value of
26544 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
26545 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
26546 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
26547 about the option without breaking older ones.
26548 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
26549 that claim to be earlier than 0.9.8m, but which have in reality
26550 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
26551 behavior. Possible fix for some cases of bug 1346.
26554 - Experiment with a more aggressive approach to preventing clients
26555 from making one-hop exit streams. Exit relays who want to try it
26556 out can set "RefuseUnknownExits 1" in their torrc, and then look
26557 for "Attempt by %s to open a stream" log messages. Let us know
26559 - Add support for statically linking zlib by specifying
26560 --enable-static-zlib, to go with our support for statically linking
26561 openssl and libevent. Resolves bug 1358.
26564 - Fix a segfault that happens whenever a Tor client that is using
26565 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
26567 - When we cleaned up the contrib/tor-exit-notice.html file, we left
26568 out the first line. Fixes bug 1295.
26569 - When building the manpage from a tarball, we required asciidoc, but
26570 the asciidoc -> roff/html conversion was already done for the
26571 tarball. Make 'make' complain only when we need asciidoc (either
26572 because we're compiling directly from git, or because we altered
26573 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
26574 - When none of the directory authorities vote on any params, Tor
26575 segfaulted when trying to make the consensus from the votes. We
26576 didn't trigger the bug in practice, because authorities do include
26577 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
26580 - In the util/threads test, no longer free the test_mutex before all
26581 worker threads have finished. Bugfix on 0.2.1.6-alpha.
26582 - The master thread could starve the worker threads quite badly on
26583 certain systems, causing them to run only partially in the allowed
26584 window. This resulted in test failures. Now the master thread sleeps
26585 occasionally for a few microseconds while the two worker-threads
26586 compete for the mutex. Bugfix on 0.2.0.1-alpha.
26589 Changes in version 0.2.2.10-alpha - 2010-03-07
26590 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
26591 could prevent relays from guessing their IP address correctly. It also
26592 starts the groundwork for another client-side performance boost, since
26593 currently we're not making efficient use of relays that have both the
26594 Guard flag and the Exit flag.
26597 - Fix a regression from our patch for bug 1244 that caused relays
26598 to guess their IP address incorrectly if they didn't set Address
26599 in their torrc and/or their address fails to resolve. Bugfix on
26600 0.2.2.9-alpha; fixes bug 1269.
26602 o Major features (performance):
26603 - Directory authorities now compute consensus weightings that instruct
26604 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
26605 and no flag. Clients that use these weightings will distribute
26606 network load more evenly across these different relay types. The
26607 weightings are in the consensus so we can change them globally in
26608 the future. Extra thanks to "outofwords" for finding some nasty
26609 security bugs in the first implementation of this feature.
26611 o Minor features (performance):
26612 - Always perform router selections using weighted relay bandwidth,
26613 even if we don't need a high capacity circuit at the time. Non-fast
26614 circuits now only differ from fast ones in that they can use relays
26615 not marked with the Fast flag. This "feature" could turn out to
26616 be a horrible bug; we should investigate more before it goes into
26620 - Allow disabling building of the manpages. Skipping the manpage
26621 speeds up the build considerably.
26623 o Minor bugfixes (on 0.2.2.x):
26624 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
26625 Bugfix on 0.2.2.9-alpha.
26626 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
26627 config option. Bugfix on 0.2.2.7-alpha.
26628 - Ship the asciidoc-helper file in the tarball, so that people can
26629 build from source if they want to, and touching the .1.txt files
26630 doesn't break the build. Bugfix on 0.2.2.9-alpha.
26632 o Minor bugfixes (on 0.2.1.x or earlier):
26633 - Fix a dereference-then-NULL-check sequence when publishing
26634 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
26636 - Fix another dereference-then-NULL-check sequence. Bugfix on
26637 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
26638 - Make sure we treat potentially not NUL-terminated strings correctly.
26639 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
26641 o Code simplifications and refactoring:
26642 - Fix some urls in the exit notice file and make it XHTML1.1 strict
26643 compliant. Based on a patch from Christian Kujau.
26644 - Don't use sed in asciidoc-helper anymore.
26645 - Make the build process fail if asciidoc cannot be found and
26646 building with asciidoc isn't disabled.
26649 Changes in version 0.2.2.9-alpha - 2010-02-22
26650 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
26651 location of a directory authority, and cleans up a bunch of small bugs.
26653 o Directory authority changes:
26654 - Change IP address for dannenberg (v3 directory authority), and
26655 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
26656 service directory authority) from the list.
26659 - Make Tor work again on the latest OS X: when deciding whether to
26660 use strange flags to turn TLS renegotiation on, detect the OpenSSL
26661 version at run-time, not compile time. We need to do this because
26662 Apple doesn't update its dev-tools headers when it updates its
26663 libraries in a security patch.
26664 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
26665 that could happen on 32-bit platforms with 64-bit time_t. Also fix
26666 a memory leak when requesting a hidden service descriptor we've
26667 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
26669 - Authorities could be tricked into giving out the Exit flag to relays
26670 that didn't allow exiting to any ports. This bug could screw
26671 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
26672 1238. Bug discovered by Martin Kowalczyk.
26673 - When freeing a session key, zero it out completely. We only zeroed
26674 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
26675 patched by ekir. Fixes bug 1254.
26678 - Fix static compilation by listing the openssl libraries in the right
26679 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
26680 - Resume handling .exit hostnames in a special way: originally we
26681 stripped the .exit part and used the requested exit relay. In
26682 0.2.2.1-alpha we stopped treating them in any special way, meaning
26683 if you use a .exit address then Tor will pass it on to the exit
26684 relay. Now we reject the .exit stream outright, since that behavior
26685 might be more expected by the user. Found and diagnosed by Scott
26686 Bennett and Downie on or-talk.
26687 - Don't spam the controller with events when we have no file
26688 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
26689 for log messages was already solved from bug 748.)
26690 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
26692 - Make the DNSPort option work with libevent 2.x. Don't alter the
26693 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
26694 - Emit a GUARD DROPPED controller event for a case we missed.
26695 - Make more fields in the controller protocol case-insensitive, since
26696 control-spec.txt said they were.
26697 - Refactor resolve_my_address() to not use gethostbyname() anymore.
26698 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
26699 - Fix a spec conformance issue: the network-status-version token
26700 must be the first token in a v3 consensus or vote. Discovered by
26701 parakeep. Bugfix on 0.2.0.3-alpha.
26703 o Code simplifications and refactoring:
26704 - Generate our manpage and HTML documentation using Asciidoc. This
26705 change should make it easier to maintain the documentation, and
26706 produce nicer HTML.
26707 - Remove the --enable-iphone option. According to reports from Marco
26708 Bonetti, Tor builds fine without any special tweaking on recent
26709 iPhone SDK versions.
26710 - Removed some unnecessary files from the source distribution. The
26711 AUTHORS file has now been merged into the people page on the
26712 website. The roadmaps and design doc can now be found in the
26713 projects directory in svn.
26714 - Enabled various circuit build timeout constants to be controlled
26715 by consensus parameters. Also set better defaults for these
26716 parameters based on experimentation on broadband and simulated
26717 high latency links.
26720 - The 'EXTENDCIRCUIT' control port command can now be used with
26721 a circ id of 0 and no path. This feature will cause Tor to build
26722 a new 'fast' general purpose circuit using its own path selection
26724 - Added a BUILDTIMEOUT_SET controller event to describe changes
26725 to the circuit build timeout.
26726 - Future-proof the controller protocol a bit by ignoring keyword
26727 arguments we do not recognize.
26728 - Expand homedirs passed to tor-checkkey. This should silence a
26729 coverity complaint about passing a user-supplied string into
26730 open() without checking it.
26733 Changes in version 0.2.1.25 - 2010-03-16
26734 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
26735 prevent relays from guessing their IP address correctly. It also fixes
26736 several minor potential security bugs.
26739 - Fix a regression from our patch for bug 1244 that caused relays
26740 to guess their IP address incorrectly if they didn't set Address
26741 in their torrc and/or their address fails to resolve. Bugfix on
26742 0.2.1.23; fixes bug 1269.
26743 - When freeing a session key, zero it out completely. We only zeroed
26744 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
26745 patched by ekir. Fixes bug 1254.
26748 - Fix a dereference-then-NULL-check sequence when publishing
26749 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
26751 - Fix another dereference-then-NULL-check sequence. Bugfix on
26752 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
26753 - Make sure we treat potentially not NUL-terminated strings correctly.
26754 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
26758 Changes in version 0.2.1.24 - 2010-02-21
26759 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
26763 - Work correctly out-of-the-box with even more vendor-patched versions
26764 of OpenSSL. In particular, make it so Debian and OS X don't need
26765 customized patches to run/build.
26768 Changes in version 0.2.1.23 - 2010-02-13
26769 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
26770 again on the latest OS X, and updates the location of a directory
26773 o Major bugfixes (performance):
26774 - We were selecting our guards uniformly at random, and then weighting
26775 which of our guards we'd use uniformly at random. This imbalance
26776 meant that Tor clients were severely limited on throughput (and
26777 probably latency too) by the first hop in their circuit. Now we
26778 select guards weighted by currently advertised bandwidth. We also
26779 automatically discard guards picked using the old algorithm. Fixes
26780 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
26783 - Make Tor work again on the latest OS X: when deciding whether to
26784 use strange flags to turn TLS renegotiation on, detect the OpenSSL
26785 version at run-time, not compile time. We need to do this because
26786 Apple doesn't update its dev-tools headers when it updates its
26787 libraries in a security patch.
26788 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
26789 that could happen on 32-bit platforms with 64-bit time_t. Also fix
26790 a memory leak when requesting a hidden service descriptor we've
26791 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
26794 o Directory authority changes:
26795 - Change IP address for dannenberg (v3 directory authority), and
26796 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
26797 service directory authority) from the list.
26800 - Refactor resolve_my_address() to not use gethostbyname() anymore.
26801 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
26804 - Avoid a mad rush at the beginning of each month when each client
26805 rotates half of its guards. Instead we spread the rotation out
26806 throughout the month, but we still avoid leaving a precise timestamp
26807 in the state file about when we first picked the guard. Improves
26808 over the behavior introduced in 0.1.2.17.
26811 Changes in version 0.2.2.8-alpha - 2010-01-26
26812 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
26813 causing bridge relays to disappear. If you're running a bridge,
26817 - Fix a memory corruption bug on bridges that occurred during the
26818 inclusion of stats data in extra-info descriptors. Also fix the
26819 interface for geoip_get_bridge_stats* to prevent similar bugs in
26820 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
26821 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
26824 - Ignore OutboundBindAddress when connecting to localhost.
26825 Connections to localhost need to come _from_ localhost, or else
26826 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
26830 Changes in version 0.2.2.7-alpha - 2010-01-19
26831 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
26832 as laying the groundwork for further relay-side performance fixes. It
26833 also starts cleaning up client behavior with respect to the EntryNodes,
26834 ExitNodes, and StrictNodes config options.
26836 This release also rotates two directory authority keys, due to a
26837 security breach of some of the Torproject servers.
26839 o Directory authority changes:
26840 - Rotate keys (both v3 identity and relay identity) for moria1
26843 o Major features (performance):
26844 - We were selecting our guards uniformly at random, and then weighting
26845 which of our guards we'd use uniformly at random. This imbalance
26846 meant that Tor clients were severely limited on throughput (and
26847 probably latency too) by the first hop in their circuit. Now we
26848 select guards weighted by currently advertised bandwidth. We also
26849 automatically discard guards picked using the old algorithm. Fixes
26850 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
26851 - When choosing which cells to relay first, relays can now favor
26852 circuits that have been quiet recently, to provide lower latency
26853 for low-volume circuits. By default, relays enable or disable this
26854 feature based on a setting in the consensus. You can override
26855 this default by using the new "CircuitPriorityHalflife" config
26856 option. Design and code by Ian Goldberg, Can Tang, and Chris
26858 - Add separate per-conn write limiting to go with the per-conn read
26859 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
26860 but never per-conn write limits.
26861 - New consensus params "bwconnrate" and "bwconnburst" to let us
26862 rate-limit client connections as they enter the network. It's
26863 controlled in the consensus so we can turn it on and off for
26864 experiments. It's starting out off. Based on proposal 163.
26866 o Major features (relay selection options):
26867 - Switch to a StrictNodes config option, rather than the previous
26868 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
26869 "StrictExcludeNodes" option.
26870 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
26871 change during a config reload, mark and discard all our origin
26872 circuits. This fix should address edge cases where we change the
26873 config options and but then choose a circuit that we created before
26875 - If EntryNodes or ExitNodes are set, be more willing to use an
26876 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
26878 - Make EntryNodes config option much more aggressive even when
26879 StrictNodes is not set. Before it would prepend your requested
26880 entrynodes to your list of guard nodes, but feel free to use others
26881 after that. Now it chooses only from your EntryNodes if any of
26882 those are available, and only falls back to others if a) they're
26883 all down and b) StrictNodes is not set.
26884 - Now we refresh your entry guards from EntryNodes at each consensus
26885 fetch -- rather than just at startup and then they slowly rot as
26886 the network changes.
26889 - Stop bridge directory authorities from answering dbg-stability.txt
26890 directory queries, which would let people fetch a list of all
26891 bridge identities they track. Bugfix on 0.2.1.6-alpha.
26894 - Log a notice when we get a new control connection. Now it's easier
26895 for security-conscious users to recognize when a local application
26896 is knocking on their controller door. Suggested by bug 1196.
26897 - New config option "CircuitStreamTimeout" to override our internal
26898 timeout schedule for how many seconds until we detach a stream from
26899 a circuit and try a new circuit. If your network is particularly
26900 slow, you might want to set this to a number like 60.
26901 - New controller command "getinfo config-text". It returns the
26902 contents that Tor would write if you send it a SAVECONF command,
26903 so the controller can write the file to disk itself.
26904 - New options for SafeLogging to allow scrubbing only log messages
26905 generated while acting as a relay.
26906 - Ship the bridges spec file in the tarball too.
26907 - Avoid a mad rush at the beginning of each month when each client
26908 rotates half of its guards. Instead we spread the rotation out
26909 throughout the month, but we still avoid leaving a precise timestamp
26910 in the state file about when we first picked the guard. Improves
26911 over the behavior introduced in 0.1.2.17.
26913 o Minor bugfixes (compiling):
26914 - Fix compilation on OS X 10.3, which has a stub mlockall() but
26915 hides it. Bugfix on 0.2.2.6-alpha.
26916 - Fix compilation on Solaris by removing support for the
26917 DisableAllSwap config option. Solaris doesn't have an rlimit for
26918 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
26921 o Minor bugfixes (crashes):
26922 - Do not segfault when writing buffer stats when we haven't observed
26923 a single circuit to report about. Found by Fabian Lanze. Bugfix on
26925 - If we're in the pathological case where there's no exit bandwidth
26926 but there is non-exit bandwidth, or no guard bandwidth but there
26927 is non-guard bandwidth, don't crash during path selection. Bugfix
26929 - Fix an impossible-to-actually-trigger buffer overflow in relay
26930 descriptor generation. Bugfix on 0.1.0.15.
26932 o Minor bugfixes (privacy):
26933 - Fix an instance where a Tor directory mirror might accidentally
26934 log the IP address of a misbehaving Tor client. Bugfix on
26936 - Don't list Windows capabilities in relay descriptors. We never made
26937 use of them, and maybe it's a bad idea to publish them. Bugfix
26940 o Minor bugfixes (other):
26941 - Resolve an edge case in path weighting that could make us misweight
26942 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
26943 - Fix statistics on client numbers by country as seen by bridges that
26944 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
26945 intervals instead of variable 12-to-48-hour intervals.
26946 - After we free an internal connection structure, overwrite it
26947 with a different memory value than we use for overwriting a freed
26948 internal circuit structure. Should help with debugging. Suggested
26950 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
26953 o Removed features:
26954 - Remove the HSAuthorityRecordStats option that version 0 hidden
26955 service authorities could have used to track statistics of overall
26956 hidden service usage.
26959 Changes in version 0.2.1.22 - 2010-01-19
26960 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
26961 authorities -- it would tell you its whole history of bridge descriptors
26962 if you make the right directory request. This stable update also
26963 rotates two of the seven v3 directory authority keys and locations.
26965 o Directory authority changes:
26966 - Rotate keys (both v3 identity and relay identity) for moria1
26970 - Stop bridge directory authorities from answering dbg-stability.txt
26971 directory queries, which would let people fetch a list of all
26972 bridge identities they track. Bugfix on 0.2.1.6-alpha.
26975 Changes in version 0.2.1.21 - 2009-12-21
26976 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
26977 library. If you use Tor on Linux / Unix and you're getting SSL
26978 renegotiation errors, upgrading should help. We also recommend an
26979 upgrade if you're an exit relay.
26982 - Work around a security feature in OpenSSL 0.9.8l that prevents our
26983 handshake from working unless we explicitly tell OpenSSL that we
26984 are using SSL renegotiation safely. We are, of course, but OpenSSL
26985 0.9.8l won't work unless we say we are.
26986 - Avoid crashing if the client is trying to upload many bytes and the
26987 circuit gets torn down at the same time, or if the flip side
26988 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
26991 - Do not refuse to learn about authority certs and v2 networkstatus
26992 documents that are older than the latest consensus. This bug might
26993 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
26994 Spotted and fixed by xmux.
26995 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
26996 trigger platform-specific option misparsing case found by Coverity
26998 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
26999 trigger assert. Fixes bug 1173.
27002 Changes in version 0.2.2.6-alpha - 2009-11-19
27003 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
27004 support for the new lower-footprint "microdescriptor" directory design,
27005 future-proofing our consensus format against new hash functions or
27006 other changes, and an Android port. It also makes Tor compatible with
27007 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
27010 - Directory authorities can now create, vote on, and serve multiple
27011 parallel formats of directory data as part of their voting process.
27012 Partially implements Proposal 162: "Publish the consensus in
27014 - Directory authorities can now agree on and publish small summaries
27015 of router information that clients can use in place of regular
27016 server descriptors. This transition will eventually allow clients
27017 to use far less bandwidth for downloading information about the
27018 network. Begins the implementation of Proposal 158: "Clients
27019 download consensus + microdescriptors".
27020 - The directory voting system is now extensible to use multiple hash
27021 algorithms for signatures and resource selection. Newer formats
27022 are signed with SHA256, with a possibility for moving to a better
27023 hash algorithm in the future.
27024 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
27025 current and future memory pages via mlockall(). On supported
27026 platforms (modern Linux and probably BSD but not Windows or OS X),
27027 this should effectively disable any and all attempts to page out
27028 memory. This option requires that you start your Tor as root --
27029 if you use DisableAllSwap, please consider using the User option
27030 to properly reduce the privileges of your Tor.
27031 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
27032 to help Tor build correctly for Android phones.
27035 - Work around a security feature in OpenSSL 0.9.8l that prevents our
27036 handshake from working unless we explicitly tell OpenSSL that we
27037 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
27038 won't work unless we say we are.
27041 - Fix a crash bug when trying to initialize the evdns module in
27042 Libevent 2. Bugfix on 0.2.1.16-rc.
27043 - Stop logging at severity 'warn' when some other Tor client tries
27044 to establish a circuit with us using weak DH keys. It's a protocol
27045 violation, but that doesn't mean ordinary users need to hear about
27046 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
27047 - Do not refuse to learn about authority certs and v2 networkstatus
27048 documents that are older than the latest consensus. This bug might
27049 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
27050 Spotted and fixed by xmux.
27051 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
27052 - If all authorities restart at once right before a consensus vote,
27053 nobody will vote about "Running", and clients will get a consensus
27054 with no usable relays. Instead, authorities refuse to build a
27055 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
27056 - If your relay can't keep up with the number of incoming create
27057 cells, it would log one warning per failure into your logs. Limit
27058 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
27059 - Bridges now use "reject *:*" as their default exit policy. Bugfix
27060 on 0.2.0.3-alpha; fixes bug 1113.
27061 - Fix a memory leak on directory authorities during voting that was
27062 introduced in 0.2.2.1-alpha. Found via valgrind.
27065 Changes in version 0.2.1.20 - 2009-10-15
27066 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
27067 services at once, prepares for more performance improvements, and
27068 fixes a bunch of smaller bugs.
27070 The Windows and OS X bundles also include a more recent Vidalia,
27071 and switch from Privoxy to Polipo.
27073 The OS X installers are now drag and drop. It's best to un-install
27074 Tor/Vidalia and then install this new bundle, rather than upgrade. If
27075 you want to upgrade, you'll need to update the paths for Tor and Polipo
27076 in the Vidalia Settings window.
27079 - Send circuit or stream sendme cells when our window has decreased
27080 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
27081 by Karsten when testing the "reduce circuit window" performance
27082 patch. Bugfix on the 54th commit on Tor -- from July 2002,
27083 before the release of Tor 0.0.0. This is the new winner of the
27085 - Fix a remotely triggerable memory leak when a consensus document
27086 contains more than one signature from the same voter. Bugfix on
27088 - Avoid segfault in rare cases when finishing an introduction circuit
27089 as a client and finding out that we don't have an introduction key
27090 for it. Fixes bug 1073. Reported by Aaron Swartz.
27093 - Tor now reads the "circwindow" parameter out of the consensus,
27094 and uses that value for its circuit package window rather than the
27095 default of 1000 cells. Begins the implementation of proposal 168.
27097 o New directory authorities:
27098 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
27100 - Move moria1 and tonga to alternate IP addresses.
27103 - Fix a signed/unsigned compile warning in 0.2.1.19.
27104 - Fix possible segmentation fault on directory authorities. Bugfix on
27106 - Fix an extremely rare infinite recursion bug that could occur if
27107 we tried to log a message after shutting down the log subsystem.
27108 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
27109 - Fix an obscure bug where hidden services on 64-bit big-endian
27110 systems might mis-read the timestamp in v3 introduce cells, and
27111 refuse to connect back to the client. Discovered by "rotor".
27112 Bugfix on 0.2.1.6-alpha.
27113 - We were triggering a CLOCK_SKEW controller status event whenever
27114 we connect via the v2 connection protocol to any relay that has
27115 a wrong clock. Instead, we should only inform the controller when
27116 it's a trusted authority that claims our clock is wrong. Bugfix
27117 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
27118 - We were telling the controller about CHECKING_REACHABILITY and
27119 REACHABILITY_FAILED status events whenever we launch a testing
27120 circuit or notice that one has failed. Instead, only tell the
27121 controller when we want to inform the user of overall success or
27122 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
27124 - Don't warn when we're using a circuit that ends with a node
27125 excluded in ExcludeExitNodes, but the circuit is not used to access
27126 the outside world. This should help fix bug 1090. Bugfix on
27128 - Work around a small memory leak in some versions of OpenSSL that
27129 stopped the memory used by the hostname TLS extension from being
27133 - Add a "getinfo status/accepted-server-descriptor" controller
27134 command, which is the recommended way for controllers to learn
27135 whether our server descriptor has been successfully received by at
27136 least on directory authority. Un-recommend good-server-descriptor
27137 getinfo and status events until we have a better design for them.
27140 Changes in version 0.2.2.5-alpha - 2009-10-11
27141 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
27144 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
27146 o Directory authorities:
27147 - Temporarily (just for this release) move dizum to an alternate
27151 Changes in version 0.2.2.4-alpha - 2009-10-10
27152 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
27153 introduces a new unit test framework, shifts directry authority
27154 addresses around to reduce the impact from recent blocking events,
27155 and fixes a few smaller bugs.
27158 - Fix several more asserts in the circuit_build_times code, for
27159 example one that causes Tor to fail to start once we have
27160 accumulated 5000 build times in the state file. Bugfixes on
27161 0.2.2.2-alpha; fixes bug 1108.
27163 o New directory authorities:
27164 - Move moria1 and Tonga to alternate IP addresses.
27167 - Log SSL state transitions at debug level during handshake, and
27168 include SSL states in error messages. This may help debug future
27169 SSL handshake issues.
27170 - Add a new "Handshake" log domain for activities that happen
27171 during the TLS handshake.
27172 - Revert to the "June 3 2009" ip-to-country file. The September one
27173 seems to have removed most US IP addresses.
27174 - Directory authorities now reject Tor relays with versions less than
27175 0.1.2.14. This step cuts out four relays from the current network,
27176 none of which are very big.
27179 - Fix a couple of smaller issues with gathering statistics. Bugfixes
27181 - Fix two memory leaks in the error case of
27182 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
27183 - Don't count one-hop circuits when we're estimating how long it
27184 takes circuits to build on average. Otherwise we'll set our circuit
27185 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
27186 - Directory authorities no longer change their opinion of, or vote on,
27187 whether a router is Running, unless they have themselves been
27188 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
27191 o Code simplifications and refactoring:
27192 - Revise our unit tests to use the "tinytest" framework, so we
27193 can run tests in their own processes, have smarter setup/teardown
27194 code, and so on. The unit test code has moved to its own
27195 subdirectory, and has been split into multiple modules.
27198 Changes in version 0.2.2.3-alpha - 2009-09-23
27199 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
27202 - Fix an overzealous assert in our new circuit build timeout code.
27203 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
27206 - If the networkstatus consensus tells us that we should use a
27207 negative circuit package window, ignore it. Otherwise we'll
27208 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
27211 Changes in version 0.2.2.2-alpha - 2009-09-21
27212 Tor 0.2.2.2-alpha introduces our latest performance improvement for
27213 clients: Tor tracks the average time it takes to build a circuit, and
27214 avoids using circuits that take too long to build. For fast connections,
27215 this feature can cut your expected latency in half. For slow or flaky
27216 connections, it could ruin your Tor experience. Let us know if it does!
27219 - Tor now tracks how long it takes to build client-side circuits
27220 over time, and adapts its timeout to local network performance.
27221 Since a circuit that takes a long time to build will also provide
27222 bad performance, we get significant latency improvements by
27223 discarding the slowest 20% of circuits. Specifically, Tor creates
27224 circuits more aggressively than usual until it has enough data
27225 points for a good timeout estimate. Implements proposal 151.
27226 We are especially looking for reports (good and bad) from users with
27227 both EDGE and broadband connections that can move from broadband
27228 to EDGE and find out if the build-time data in the .tor/state gets
27229 reset without loss of Tor usability. You should also see a notice
27230 log message telling you that Tor has reset its timeout.
27231 - Directory authorities can now vote on arbitrary integer values as
27232 part of the consensus process. This is designed to help set
27233 network-wide parameters. Implements proposal 167.
27234 - Tor now reads the "circwindow" parameter out of the consensus,
27235 and uses that value for its circuit package window rather than the
27236 default of 1000 cells. Begins the implementation of proposal 168.
27239 - Fix a remotely triggerable memory leak when a consensus document
27240 contains more than one signature from the same voter. Bugfix on
27244 - Fix an extremely rare infinite recursion bug that could occur if
27245 we tried to log a message after shutting down the log subsystem.
27246 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
27247 - Fix parsing for memory or time units given without a space between
27248 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
27249 - A networkstatus vote must contain exactly one signature. Spec
27250 conformance issue. Bugfix on 0.2.0.3-alpha.
27251 - Fix an obscure bug where hidden services on 64-bit big-endian
27252 systems might mis-read the timestamp in v3 introduce cells, and
27253 refuse to connect back to the client. Discovered by "rotor".
27254 Bugfix on 0.2.1.6-alpha.
27255 - We were triggering a CLOCK_SKEW controller status event whenever
27256 we connect via the v2 connection protocol to any relay that has
27257 a wrong clock. Instead, we should only inform the controller when
27258 it's a trusted authority that claims our clock is wrong. Bugfix
27259 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
27260 - We were telling the controller about CHECKING_REACHABILITY and
27261 REACHABILITY_FAILED status events whenever we launch a testing
27262 circuit or notice that one has failed. Instead, only tell the
27263 controller when we want to inform the user of overall success or
27264 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
27266 - Don't warn when we're using a circuit that ends with a node
27267 excluded in ExcludeExitNodes, but the circuit is not used to access
27268 the outside world. This should help fix bug 1090, but more problems
27269 remain. Bugfix on 0.2.1.6-alpha.
27270 - Work around a small memory leak in some versions of OpenSSL that
27271 stopped the memory used by the hostname TLS extension from being
27273 - Make our 'torify' script more portable; if we have only one of
27274 'torsocks' or 'tsocks' installed, don't complain to the user;
27275 and explain our warning about tsocks better.
27278 - Add a "getinfo status/accepted-server-descriptor" controller
27279 command, which is the recommended way for controllers to learn
27280 whether our server descriptor has been successfully received by at
27281 least on directory authority. Un-recommend good-server-descriptor
27282 getinfo and status events until we have a better design for them.
27283 - Update to the "September 4 2009" ip-to-country file.
27286 Changes in version 0.2.2.1-alpha - 2009-08-26
27287 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
27288 Tor clients to bootstrap on networks where only port 80 is reachable,
27289 makes it more straightforward to support hardware crypto accelerators,
27290 and starts the groundwork for gathering stats safely at relays.
27293 - Start the process of disabling ".exit" address notation, since it
27294 can be used for a variety of esoteric application-level attacks
27295 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
27298 o New directory authorities:
27299 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
27303 - New AccelName and AccelDir options add support for dynamic OpenSSL
27304 hardware crypto acceleration engines.
27305 - Tor now supports tunneling all of its outgoing connections over
27306 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
27307 configuration options. Code by Christopher Davis.
27310 - Send circuit or stream sendme cells when our window has decreased
27311 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
27312 by Karsten when testing the "reduce circuit window" performance
27313 patch. Bugfix on the 54th commit on Tor -- from July 2002,
27314 before the release of Tor 0.0.0. This is the new winner of the
27317 o New options for gathering stats safely:
27318 - Directory mirrors that set "DirReqStatistics 1" write statistics
27319 about directory requests to disk every 24 hours. As compared to the
27320 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
27321 1) stats are written to disk exactly every 24 hours; 2) estimated
27322 shares of v2 and v3 requests are determined as mean values, not at
27323 the end of a measurement period; 3) unresolved requests are listed
27324 with country code '??'; 4) directories also measure download times.
27325 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
27326 number of exit streams and transferred bytes per port to disk every
27328 - Relays that set "CellStatistics 1" write statistics on how long
27329 cells spend in their circuit queues to disk every 24 hours.
27330 - Entry nodes that set "EntryStatistics 1" write statistics on the
27331 rough number and origins of connecting clients to disk every 24
27333 - Relays that write any of the above statistics to disk and set
27334 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
27335 their extra-info documents.
27338 - New --digests command-line switch to output the digests of the
27339 source files Tor was built with.
27340 - The "torify" script now uses torsocks where available.
27341 - The memarea code now uses a sentinel value at the end of each area
27342 to make sure nothing writes beyond the end of an area. This might
27343 help debug some conceivable causes of bug 930.
27344 - Time and memory units in the configuration file can now be set to
27345 fractional units. For example, "2.5 GB" is now a valid value for
27347 - Certain Tor clients (such as those behind check.torproject.org) may
27348 want to fetch the consensus in an extra early manner. To enable this
27349 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
27350 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
27351 as only certain clients who must have this information sooner should
27353 - Instead of adding the svn revision to the Tor version string, report
27354 the git commit (when we're building from a git checkout).
27357 - If any of the v3 certs we download are unparseable, we should
27358 actually notice the failure so we don't retry indefinitely. Bugfix
27359 on 0.2.0.x; reported by "rotator".
27360 - If the cached cert file is unparseable, warn but don't exit.
27361 - Fix possible segmentation fault on directory authorities. Bugfix on
27363 - When Tor fails to parse a descriptor of any kind, dump it to disk.
27364 Might help diagnosing bug 1051.
27366 o Deprecated and removed features:
27367 - The controller no longer accepts the old obsolete "addr-mappings/"
27368 or "unregistered-servers-" GETINFO values.
27369 - Hidden services no longer publish version 0 descriptors, and clients
27370 do not request or use version 0 descriptors. However, the old hidden
27371 service authorities still accept and serve version 0 descriptors
27372 when contacted by older hidden services/clients.
27373 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
27374 always on; using them is necessary for correct forward-compatible
27376 - Remove support for .noconnect style addresses. Nobody was using
27377 them, and they provided another avenue for detecting Tor users
27378 via application-level web tricks.
27380 o Packaging changes:
27381 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
27382 installer bundles. See
27383 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
27384 for details of what's new in Vidalia 0.2.3.
27385 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
27386 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
27387 configuration file, rather than the old Privoxy.
27388 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
27389 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
27390 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
27391 better compatibility with OS X 10.6, aka Snow Leopard.
27392 - OS X Vidalia Bundle: The multi-package installer is now replaced
27393 by a simple drag and drop to the /Applications folder. This change
27394 occurred with the upgrade to Vidalia 0.2.3.
27397 Changes in version 0.2.1.19 - 2009-07-28
27398 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
27399 services on Tor 0.2.1.3-alpha through 0.2.1.18.
27402 - Make accessing hidden services on 0.2.1.x work right again.
27403 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
27404 part of patch provided by "optimist".
27407 - When a relay/bridge is writing out its identity key fingerprint to
27408 the "fingerprint" file and to its logs, write it without spaces. Now
27409 it will look like the fingerprints in our bridges documentation,
27410 and confuse fewer users.
27413 - Relays no longer publish a new server descriptor if they change
27414 their MaxAdvertisedBandwidth config option but it doesn't end up
27415 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
27416 fixes bug 1026. Patch from Sebastian.
27417 - Avoid leaking memory every time we get a create cell but we have
27418 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
27419 fixes bug 1034. Reported by BarkerJr.
27422 Changes in version 0.2.1.18 - 2009-07-24
27423 Tor 0.2.1.18 lays the foundations for performance improvements,
27424 adds status events to help users diagnose bootstrap problems, adds
27425 optional authentication/authorization for hidden services, fixes a
27426 variety of potential anonymity problems, and includes a huge pile of
27427 other features and bug fixes.
27430 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
27433 Changes in version 0.2.1.17-rc - 2009-07-07
27434 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
27435 candidate for the 0.2.1.x series. It lays the groundwork for further
27436 client performance improvements, and also fixes a big bug with directory
27437 authorities that were causing them to assign Guard and Stable flags
27440 The Windows bundles also finally include the geoip database that we
27441 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
27442 should actually install Torbutton rather than giving you a cryptic
27443 failure message (oops).
27446 - Clients now use the bandwidth values in the consensus, rather than
27447 the bandwidth values in each relay descriptor. This approach opens
27448 the door to more accurate bandwidth estimates once the directory
27449 authorities start doing active measurements. Implements more of
27453 - When Tor clients restart after 1-5 days, they discard all their
27454 cached descriptors as too old, but they still use the cached
27455 consensus document. This approach is good for robustness, but
27456 bad for performance: since they don't know any bandwidths, they
27457 end up choosing at random rather than weighting their choice by
27458 speed. Fixed by the above feature of putting bandwidths in the
27459 consensus. Bugfix on 0.2.0.x.
27460 - Directory authorities were neglecting to mark relays down in their
27461 internal histories if the relays fall off the routerlist without
27462 ever being found unreachable. So there were relays in the histories
27463 that haven't been seen for eight months, and are listed as being
27464 up for eight months. This wreaked havoc on the "median wfu"
27465 and "median mtbf" calculations, in turn making Guard and Stable
27466 flags very wrong, hurting network performance. Fixes bugs 696 and
27467 969. Bugfix on 0.2.0.6-alpha.
27470 - Serve the DirPortFrontPage page even when we have been approaching
27471 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
27472 - The control port would close the connection before flushing long
27473 replies, such as the network consensus, if a QUIT command was issued
27474 before the reply had completed. Now, the control port flushes all
27475 pending replies before closing the connection. Also fixed a spurious
27476 warning when a QUIT command is issued after a malformed or rejected
27477 AUTHENTICATE command, but before the connection was closed. Patch
27478 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
27479 - When we can't find an intro key for a v2 hidden service descriptor,
27480 fall back to the v0 hidden service descriptor and log a bug message.
27481 Workaround for bug 1024.
27482 - Fix a log message that did not respect the SafeLogging option.
27486 - If we're a relay and we change our IP address, be more verbose
27487 about the reason that made us change. Should help track down
27488 further bugs for relays on dynamic IP addresses.
27491 Changes in version 0.2.0.35 - 2009-06-24
27493 - Avoid crashing in the presence of certain malformed descriptors.
27494 Found by lark, and by automated fuzzing.
27495 - Fix an edge case where a malicious exit relay could convince a
27496 controller that the client's DNS question resolves to an internal IP
27497 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
27500 - Finally fix the bug where dynamic-IP relays disappear when their
27501 IP address changes: directory mirrors were mistakenly telling
27502 them their old address if they asked via begin_dir, so they
27503 never got an accurate answer about their new address, so they
27504 just vanished after a day. For belt-and-suspenders, relays that
27505 don't set Address in their config now avoid using begin_dir for
27506 all direct connections. Should fix bugs 827, 883, and 900.
27507 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
27508 that would occur on some exit nodes when DNS failures and timeouts
27509 occurred in certain patterns. Fix for bug 957.
27512 - When starting with a cache over a few days old, do not leak
27513 memory for the obsolete router descriptors in it. Bugfix on
27514 0.2.0.33; fixes bug 672.
27515 - Hidden service clients didn't use a cached service descriptor that
27516 was older than 15 minutes, but wouldn't fetch a new one either,
27517 because there was already one in the cache. Now, fetch a v2
27518 descriptor unless the same descriptor was added to the cache within
27519 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
27522 Changes in version 0.2.1.16-rc - 2009-06-20
27523 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
27524 a bunch of minor bugs.
27527 - Fix an edge case where a malicious exit relay could convince a
27528 controller that the client's DNS question resolves to an internal IP
27529 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
27531 o Major performance improvements (on 0.2.0.x):
27532 - Disable and refactor some debugging checks that forced a linear scan
27533 over the whole server-side DNS cache. These accounted for over 50%
27534 of CPU time on a relatively busy exit node's gprof profile. Found
27536 - Disable some debugging checks that appeared in exit node profile
27540 - Update to the "June 3 2009" ip-to-country file.
27541 - Do not have tor-resolve automatically refuse all .onion addresses;
27542 if AutomapHostsOnResolve is set in your torrc, this will work fine.
27544 o Minor bugfixes (on 0.2.0.x):
27545 - Log correct error messages for DNS-related network errors on
27547 - Fix a race condition that could cause crashes or memory corruption
27548 when running as a server with a controller listening for log
27550 - Avoid crashing when we have a policy specified in a DirPolicy or
27551 SocksPolicy or ReachableAddresses option with ports set on it,
27552 and we re-load the policy. May fix bug 996.
27553 - Hidden service clients didn't use a cached service descriptor that
27554 was older than 15 minutes, but wouldn't fetch a new one either,
27555 because there was already one in the cache. Now, fetch a v2
27556 descriptor unless the same descriptor was added to the cache within
27557 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
27559 o Minor bugfixes (on 0.2.1.x):
27560 - Don't warn users about low port and hibernation mix when they
27561 provide a *ListenAddress directive to fix that. Bugfix on
27563 - When switching back and forth between bridge mode, do not start
27564 gathering GeoIP data until two hours have passed.
27565 - Do not complain that the user has requested an excluded node as
27566 an exit when the node is not really an exit. This could happen
27567 because the circuit was for testing, or an introduction point.
27571 Changes in version 0.2.1.15-rc - 2009-05-25
27572 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
27573 series. It fixes a major bug on fast exit relays, as well as a variety
27574 of more minor bugs.
27576 o Major bugfixes (on 0.2.0.x):
27577 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
27578 that would occur on some exit nodes when DNS failures and timeouts
27579 occurred in certain patterns. Fix for bug 957.
27581 o Minor bugfixes (on 0.2.0.x):
27582 - Actually return -1 in the error case for read_bandwidth_usage().
27583 Harmless bug, since we currently don't care about the return value
27584 anywhere. Bugfix on 0.2.0.9-alpha.
27585 - Provide a more useful log message if bug 977 (related to buffer
27586 freelists) ever reappears, and do not crash right away.
27587 - Fix an assertion failure on 64-bit platforms when we allocated
27588 memory right up to the end of a memarea, then realigned the memory
27589 one step beyond the end. Fixes a possible cause of bug 930.
27590 - Protect the count of open sockets with a mutex, so we can't
27591 corrupt it when two threads are closing or opening sockets at once.
27592 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
27593 - Don't allow a bridge to publish its router descriptor to a
27594 non-bridge directory authority. Fixes part of bug 932.
27595 - When we change to or from being a bridge, reset our counts of
27596 client usage by country. Fixes bug 932.
27597 - Fix a bug that made stream bandwidth get misreported to the
27599 - Stop using malloc_usable_size() to use more area than we had
27600 actually allocated: it was safe, but made valgrind really unhappy.
27601 - Fix a memory leak when v3 directory authorities load their keys
27602 and cert from disk. Bugfix on 0.2.0.1-alpha.
27604 o Minor bugfixes (on 0.2.1.x):
27605 - Fix use of freed memory when deciding to mark a non-addable
27606 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
27609 Changes in version 0.2.1.14-rc - 2009-04-12
27610 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
27611 series. It begins fixing some major performance problems, and also
27612 finally addresses the bug that was causing relays on dynamic IP
27613 addresses to fall out of the directory.
27616 - Clients replace entry guards that were chosen more than a few months
27617 ago. This change should significantly improve client performance,
27618 especially once more people upgrade, since relays that have been
27619 a guard for a long time are currently overloaded.
27621 o Major bugfixes (on 0.2.0):
27622 - Finally fix the bug where dynamic-IP relays disappear when their
27623 IP address changes: directory mirrors were mistakenly telling
27624 them their old address if they asked via begin_dir, so they
27625 never got an accurate answer about their new address, so they
27626 just vanished after a day. For belt-and-suspenders, relays that
27627 don't set Address in their config now avoid using begin_dir for
27628 all direct connections. Should fix bugs 827, 883, and 900.
27629 - Relays were falling out of the networkstatus consensus for
27630 part of a day if they changed their local config but the
27631 authorities discarded their new descriptor as "not sufficiently
27632 different". Now directory authorities accept a descriptor as changed
27633 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
27634 patch by Sebastian.
27635 - Avoid crashing in the presence of certain malformed descriptors.
27636 Found by lark, and by automated fuzzing.
27639 - When generating circuit events with verbose nicknames for
27640 controllers, try harder to look up nicknames for routers on a
27641 circuit. (Previously, we would look in the router descriptors we had
27642 for nicknames, but not in the consensus.) Partial fix for bug 941.
27643 - If the bridge config line doesn't specify a port, assume 443.
27644 This makes bridge lines a bit smaller and easier for users to
27646 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
27647 bytes (aka 20KB/s), to match our documentation. Also update
27648 directory authorities so they always assign the Fast flag to relays
27649 with 20KB/s of capacity. Now people running relays won't suddenly
27650 find themselves not seeing any use, if the network gets faster
27652 - Update to the "April 3 2009" ip-to-country file.
27655 - Avoid trying to print raw memory to the logs when we decide to
27656 give up on downloading a given relay descriptor. Bugfix on
27658 - In tor-resolve, when the Tor client to use is specified by
27659 <hostname>:<port>, actually use the specified port rather than
27660 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
27661 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
27662 - When starting with a cache over a few days old, do not leak
27663 memory for the obsolete router descriptors in it. Bugfix on
27665 - Avoid double-free on list of successfully uploaded hidden
27666 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
27667 - Change memarea_strndup() implementation to work even when
27668 duplicating a string at the end of a page. This bug was
27669 harmless for now, but could have meant crashes later. Fix by
27670 lark. Bugfix on 0.2.1.1-alpha.
27671 - Limit uploaded directory documents to be 16M rather than 500K.
27672 The directory authorities were refusing v3 consensus votes from
27673 other authorities, since the votes are now 504K. Fixes bug 959;
27674 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
27675 - Directory authorities should never send a 503 "busy" response to
27676 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
27680 Changes in version 0.2.1.13-alpha - 2009-03-09
27681 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
27682 cleanups. We're finally getting close to a release candidate.
27685 - Correctly update the list of which countries we exclude as
27686 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
27687 lark. Bugfix on 0.2.1.6-alpha.
27689 o Minor bugfixes (on 0.2.0.x and earlier):
27690 - Automatically detect MacOSX versions earlier than 10.4.0, and
27691 disable kqueue from inside Tor when running with these versions.
27692 We previously did this from the startup script, but that was no
27693 help to people who didn't use the startup script. Resolves bug 863.
27694 - When we had picked an exit node for a connection, but marked it as
27695 "optional", and it turned out we had no onion key for the exit,
27696 stop wanting that exit and try again. This situation may not
27697 be possible now, but will probably become feasible with proposal
27698 158. Spotted by rovv. Fixes another case of bug 752.
27699 - Clients no longer cache certificates for authorities they do not
27700 recognize. Bugfix on 0.2.0.9-alpha.
27701 - When we can't transmit a DNS request due to a network error, retry
27702 it after a while, and eventually transmit a failing response to
27703 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
27704 - If the controller claimed responsibility for a stream, but that
27705 stream never finished making its connection, it would live
27706 forever in circuit_wait state. Now we close it after SocksTimeout
27707 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
27708 - Drop begin cells to a hidden service if they come from the middle
27709 of a circuit. Patch from lark.
27710 - When we erroneously receive two EXTEND cells for the same circuit
27711 ID on the same connection, drop the second. Patch from lark.
27712 - Fix a crash that occurs on exit nodes when a nameserver request
27713 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
27714 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
27716 - Do not assume that a stack-allocated character array will be
27717 64-bit aligned on platforms that demand that uint64_t access is
27718 aligned. Possible fix for bug 604.
27719 - Parse dates and IPv4 addresses in a locale- and libc-independent
27720 manner, to avoid platform-dependent behavior on malformed input.
27721 - Build correctly when configured to build outside the main source
27722 path. Patch from Michael Gold.
27723 - We were already rejecting relay begin cells with destination port
27724 of 0. Now also reject extend cells with destination port or address
27725 of 0. Suggested by lark.
27727 o Minor bugfixes (on 0.2.1.x):
27728 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
27729 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
27730 - If we're an exit node, scrub the IP address to which we are exiting
27731 in the logs. Bugfix on 0.2.1.8-alpha.
27734 - On Linux, use the prctl call to re-enable core dumps when the user
27736 - New controller event NEWCONSENSUS that lists the networkstatus
27737 lines for every recommended relay. Now controllers like Torflow
27738 can keep up-to-date on which relays they should be using.
27739 - Update to the "February 26 2009" ip-to-country file.
27742 Changes in version 0.2.0.34 - 2009-02-08
27743 Tor 0.2.0.34 features several more security-related fixes. You should
27744 upgrade, especially if you run an exit relay (remote crash) or a
27745 directory authority (remote infinite loop), or you're on an older
27746 (pre-XP) or not-recently-patched Windows (remote exploit).
27748 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
27749 have many known flaws, and nobody should be using them. You should
27750 upgrade. If you're using a Linux or BSD and its packages are obsolete,
27751 stop using those packages and upgrade anyway.
27754 - Fix an infinite-loop bug on handling corrupt votes under certain
27755 circumstances. Bugfix on 0.2.0.8-alpha.
27756 - Fix a temporary DoS vulnerability that could be performed by
27757 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
27758 - Avoid a potential crash on exit nodes when processing malformed
27759 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
27760 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
27761 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
27764 - Fix compilation on systems where time_t is a 64-bit integer.
27765 Patch from Matthias Drochner.
27766 - Don't consider expiring already-closed client connections. Fixes
27767 bug 893. Bugfix on 0.0.2pre20.
27770 Changes in version 0.2.1.12-alpha - 2009-02-08
27771 Tor 0.2.1.12-alpha features several more security-related fixes. You
27772 should upgrade, especially if you run an exit relay (remote crash) or
27773 a directory authority (remote infinite loop), or you're on an older
27774 (pre-XP) or not-recently-patched Windows (remote exploit). It also
27775 includes a big pile of minor bugfixes and cleanups.
27778 - Fix an infinite-loop bug on handling corrupt votes under certain
27779 circumstances. Bugfix on 0.2.0.8-alpha.
27780 - Fix a temporary DoS vulnerability that could be performed by
27781 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
27782 - Avoid a potential crash on exit nodes when processing malformed
27783 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
27786 - Let controllers actually ask for the "clients_seen" event for
27787 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
27788 reported by Matt Edman.
27789 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
27791 - Fix a bug in address parsing that was preventing bridges or hidden
27792 service targets from being at IPv6 addresses.
27793 - Solve a bug that kept hardware crypto acceleration from getting
27794 enabled when accounting was turned on. Fixes bug 907. Bugfix on
27796 - Remove a bash-ism from configure.in to build properly on non-Linux
27797 platforms. Bugfix on 0.2.1.1-alpha.
27798 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
27799 headers. Bugfix on 0.2.0.10-alpha.
27800 - Don't consider expiring already-closed client connections. Fixes
27801 bug 893. Bugfix on 0.0.2pre20.
27802 - Fix another interesting corner-case of bug 891 spotted by rovv:
27803 Previously, if two hosts had different amounts of clock drift, and
27804 one of them created a new connection with just the wrong timing,
27805 the other might decide to deprecate the new connection erroneously.
27806 Bugfix on 0.1.1.13-alpha.
27807 - Resolve a very rare crash bug that could occur when the user forced
27808 a nameserver reconfiguration during the middle of a nameserver
27809 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
27810 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
27811 Bugfix on 0.2.1.7-alpha.
27812 - If we're using bridges and our network goes away, be more willing
27813 to forgive our bridges and try again when we get an application
27814 request. Bugfix on 0.2.0.x.
27817 - Support platforms where time_t is 64 bits long. (Congratulations,
27818 NetBSD!) Patch from Matthias Drochner.
27819 - Add a 'getinfo status/clients-seen' controller command, in case
27820 controllers want to hear clients_seen events but connect late.
27823 - Disable GCC's strict alias optimization by default, to avoid the
27824 likelihood of its introducing subtle bugs whenever our code violates
27825 the letter of C99's alias rules.
27828 Changes in version 0.2.0.33 - 2009-01-21
27829 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
27830 useful to users. It also finally fixes a bug where a relay or client
27831 that's been off for many days would take a long time to bootstrap.
27833 This update also fixes an important security-related bug reported by
27834 Ilja van Sprundel. You should upgrade. (We'll send out more details
27835 about the bug once people have had some time to upgrade.)
27838 - Fix a heap-corruption bug that may be remotely triggerable on
27839 some platforms. Reported by Ilja van Sprundel.
27842 - When a stream at an exit relay is in state "resolving" or
27843 "connecting" and it receives an "end" relay cell, the exit relay
27844 would silently ignore the end cell and not close the stream. If
27845 the client never closes the circuit, then the exit relay never
27846 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
27847 reported by "wood".
27848 - When sending CREATED cells back for a given circuit, use a 64-bit
27849 connection ID to find the right connection, rather than an addr:port
27850 combination. Now that we can have multiple OR connections between
27851 the same ORs, it is no longer possible to use addr:port to uniquely
27852 identify a connection.
27853 - Bridge relays that had DirPort set to 0 would stop fetching
27854 descriptors shortly after startup, and then briefly resume
27855 after a new bandwidth test and/or after publishing a new bridge
27856 descriptor. Bridge users that try to bootstrap from them would
27857 get a recent networkstatus but would get descriptors from up to
27858 18 hours earlier, meaning most of the descriptors were obsolete
27859 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
27860 - Prevent bridge relays from serving their 'extrainfo' document
27861 to anybody who asks, now that extrainfo docs include potentially
27862 sensitive aggregated client geoip summaries. Bugfix on
27864 - If the cached networkstatus consensus is more than five days old,
27865 discard it rather than trying to use it. In theory it could be
27866 useful because it lists alternate directory mirrors, but in practice
27867 it just means we spend many minutes trying directory mirrors that
27868 are long gone from the network. Also discard router descriptors as
27869 we load them if they are more than five days old, since the onion
27870 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
27873 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
27874 could make gcc generate non-functional binary search code. Bugfix
27876 - Build correctly on platforms without socklen_t.
27877 - Compile without warnings on solaris.
27878 - Avoid potential crash on internal error during signature collection.
27879 Fixes bug 864. Patch from rovv.
27880 - Correct handling of possible malformed authority signing key
27881 certificates with internal signature types. Fixes bug 880.
27882 Bugfix on 0.2.0.3-alpha.
27883 - Fix a hard-to-trigger resource leak when logging credential status.
27885 - When we can't initialize DNS because the network is down, do not
27886 automatically stop Tor from starting. Instead, we retry failed
27887 dns_init() every 10 minutes, and change the exit policy to reject
27888 *:* until one succeeds. Fixes bug 691.
27889 - Use 64 bits instead of 32 bits for connection identifiers used with
27890 the controller protocol, to greatly reduce risk of identifier reuse.
27891 - When we're choosing an exit node for a circuit, and we have
27892 no pending streams, choose a good general exit rather than one that
27893 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
27894 - Fix another case of assuming, when a specific exit is requested,
27895 that we know more than the user about what hosts it allows.
27896 Fixes one case of bug 752. Patch from rovv.
27897 - Clip the MaxCircuitDirtiness config option to a minimum of 10
27898 seconds. Warn the user if lower values are given in the
27899 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
27900 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
27901 user if lower values are given in the configuration. Bugfix on
27902 0.1.1.17-rc. Patch by Sebastian.
27903 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
27904 the cache because we already had a v0 descriptor with the same ID.
27905 Bugfix on 0.2.0.18-alpha.
27906 - Fix a race condition when freeing keys shared between main thread
27907 and CPU workers that could result in a memory leak. Bugfix on
27908 0.1.0.1-rc. Fixes bug 889.
27909 - Send a valid END cell back when a client tries to connect to a
27910 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
27911 840. Patch from rovv.
27912 - Check which hops rendezvous stream cells are associated with to
27913 prevent possible guess-the-streamid injection attacks from
27914 intermediate hops. Fixes another case of bug 446. Based on patch
27916 - If a broken client asks a non-exit router to connect somewhere,
27917 do not even do the DNS lookup before rejecting the connection.
27918 Fixes another case of bug 619. Patch from rovv.
27919 - When a relay gets a create cell it can't decrypt (e.g. because it's
27920 using the wrong onion key), we were dropping it and letting the
27921 client time out. Now actually answer with a destroy cell. Fixes
27922 bug 904. Bugfix on 0.0.2pre8.
27924 o Minor bugfixes (hidden services):
27925 - Do not throw away existing introduction points on SIGHUP. Bugfix on
27926 0.0.6pre1. Patch by Karsten. Fixes bug 874.
27929 - Report the case where all signatures in a detached set are rejected
27930 differently than the case where there is an error handling the
27932 - When we realize that another process has modified our cached
27933 descriptors, print out a more useful error message rather than
27934 triggering an assertion. Fixes bug 885. Patch from Karsten.
27935 - Implement the 0x20 hack to better resist DNS poisoning: set the
27936 case on outgoing DNS requests randomly, and reject responses that do
27937 not match the case correctly. This logic can be disabled with the
27938 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
27939 of servers that do not reliably preserve case in replies. See
27940 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
27942 - Check DNS replies for more matching fields to better resist DNS
27944 - Never use OpenSSL compression: it wastes RAM and CPU trying to
27945 compress cells, which are basically all encrypted, compressed, or
27949 Changes in version 0.2.1.11-alpha - 2009-01-20
27950 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
27951 week it will take a long time to bootstrap again" bug. It also fixes
27952 an important security-related bug reported by Ilja van Sprundel. You
27953 should upgrade. (We'll send out more details about the bug once people
27954 have had some time to upgrade.)
27957 - Fix a heap-corruption bug that may be remotely triggerable on
27958 some platforms. Reported by Ilja van Sprundel.
27961 - Discard router descriptors as we load them if they are more than
27962 five days old. Otherwise if Tor is off for a long time and then
27963 starts with cached descriptors, it will try to use the onion
27964 keys in those obsolete descriptors when building circuits. Bugfix
27965 on 0.2.0.x. Fixes bug 887.
27968 - Try to make sure that the version of Libevent we're running with
27969 is binary-compatible with the one we built with. May address bug
27971 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
27972 for bug 905. Bugfix on 0.2.1.7-alpha.
27973 - Add a new --enable-local-appdata configuration switch to change
27974 the default location of the datadir on win32 from APPDATA to
27975 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
27976 entirely. Patch from coderman.
27979 - Make outbound DNS packets respect the OutboundBindAddress setting.
27980 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
27981 - When our circuit fails at the first hop (e.g. we get a destroy
27982 cell back), avoid using that OR connection anymore, and also
27983 tell all the one-hop directory requests waiting for it that they
27984 should fail. Bugfix on 0.2.1.3-alpha.
27985 - In the torify(1) manpage, mention that tsocks will leak your
27989 Changes in version 0.2.1.10-alpha - 2009-01-06
27990 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
27991 would make the bridge relay not so useful if it had DirPort set to 0,
27992 and one that could let an attacker learn a little bit of information
27993 about the bridge's users), and a bug that would cause your Tor relay
27994 to ignore a circuit create request it can't decrypt (rather than reply
27995 with an error). It also fixes a wide variety of other bugs.
27998 - If the cached networkstatus consensus is more than five days old,
27999 discard it rather than trying to use it. In theory it could
28000 be useful because it lists alternate directory mirrors, but in
28001 practice it just means we spend many minutes trying directory
28002 mirrors that are long gone from the network. Helps bug 887 a bit;
28004 - Bridge relays that had DirPort set to 0 would stop fetching
28005 descriptors shortly after startup, and then briefly resume
28006 after a new bandwidth test and/or after publishing a new bridge
28007 descriptor. Bridge users that try to bootstrap from them would
28008 get a recent networkstatus but would get descriptors from up to
28009 18 hours earlier, meaning most of the descriptors were obsolete
28010 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
28011 - Prevent bridge relays from serving their 'extrainfo' document
28012 to anybody who asks, now that extrainfo docs include potentially
28013 sensitive aggregated client geoip summaries. Bugfix on
28017 - New controller event "clients_seen" to report a geoip-based summary
28018 of which countries we've seen clients from recently. Now controllers
28019 like Vidalia can show bridge operators that they're actually making
28021 - Build correctly against versions of OpenSSL 0.9.8 or later built
28022 without support for deprecated functions.
28023 - Update to the "December 19 2008" ip-to-country file.
28025 o Minor bugfixes (on 0.2.0.x):
28026 - Authorities now vote for the Stable flag for any router whose
28027 weighted MTBF is at least 5 days, regardless of the mean MTBF.
28028 - Do not remove routers as too old if we do not have any consensus
28029 document. Bugfix on 0.2.0.7-alpha.
28030 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
28031 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
28032 - When an exit relay resolves a stream address to a local IP address,
28033 do not just keep retrying that same exit relay over and
28034 over. Instead, just close the stream. Addresses bug 872. Bugfix
28035 on 0.2.0.32. Patch from rovv.
28036 - If a hidden service sends us an END cell, do not consider
28037 retrying the connection; just close it. Patch from rovv.
28038 - When we made bridge authorities stop serving bridge descriptors over
28039 unencrypted links, we also broke DirPort reachability testing for
28040 bridges. So bridges with a non-zero DirPort were printing spurious
28041 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
28042 - When a relay gets a create cell it can't decrypt (e.g. because it's
28043 using the wrong onion key), we were dropping it and letting the
28044 client time out. Now actually answer with a destroy cell. Fixes
28045 bug 904. Bugfix on 0.0.2pre8.
28046 - Squeeze 2-5% out of client performance (according to oprofile) by
28047 improving the implementation of some policy-manipulation functions.
28049 o Minor bugfixes (on 0.2.1.x):
28050 - Make get_interface_address() function work properly again; stop
28051 guessing the wrong parts of our address as our address.
28052 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
28053 send on that circuit. Otherwise we might violate the proposal-110
28054 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
28056 - When we're sending non-EXTEND cells to the first hop in a circuit,
28057 for example to use an encrypted directory connection, we don't need
28058 to use RELAY_EARLY cells: the first hop knows what kind of cell
28059 it is, and nobody else can even see the cell type. Conserving
28060 RELAY_EARLY cells makes it easier to cannibalize circuits like
28062 - Stop logging nameserver addresses in reverse order.
28063 - If we are retrying a directory download slowly over and over, do
28064 not automatically give up after the 254th failure. Bugfix on
28066 - Resume reporting accurate "stream end" reasons to the local control
28067 port. They were lost in the changes for Proposal 148. Bugfix on
28070 o Deprecated and removed features:
28071 - The old "tor --version --version" command, which would print out
28072 the subversion "Id" of most of the source files, is now removed. It
28073 turned out to be less useful than we'd expected, and harder to
28076 o Code simplifications and refactoring:
28077 - Change our header file guard macros to be less likely to conflict
28078 with system headers. Adam Langley noticed that we were conflicting
28079 with log.h on Android.
28080 - Tool-assisted documentation cleanup. Nearly every function or
28081 static variable in Tor should have its own documentation now.
28084 Changes in version 0.2.1.9-alpha - 2008-12-25
28085 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
28087 o New directory authorities:
28088 - gabelmoo (the authority run by Karsten Loesing) now has a new
28092 - Never use a connection with a mismatched address to extend a
28093 circuit, unless that connection is canonical. A canonical
28094 connection is one whose address is authenticated by the router's
28095 identity key, either in a NETINFO cell or in a router descriptor.
28096 - Avoid a possible memory corruption bug when receiving hidden service
28097 descriptors. Bugfix on 0.2.1.6-alpha.
28100 - Fix a logic error that would automatically reject all but the first
28101 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
28102 part of bug 813/868. Bug spotted by coderman.
28103 - When a stream at an exit relay is in state "resolving" or
28104 "connecting" and it receives an "end" relay cell, the exit relay
28105 would silently ignore the end cell and not close the stream. If
28106 the client never closes the circuit, then the exit relay never
28107 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
28108 reported by "wood".
28109 - When we can't initialize DNS because the network is down, do not
28110 automatically stop Tor from starting. Instead, retry failed
28111 dns_init() every 10 minutes, and change the exit policy to reject
28112 *:* until one succeeds. Fixes bug 691.
28115 - Give a better error message when an overzealous init script says
28116 "sudo -u username tor --user username". Makes Bug 882 easier for
28118 - When a directory authority gives us a new guess for our IP address,
28119 log which authority we used. Hopefully this will help us debug
28120 the recent complaints about bad IP address guesses.
28121 - Detect svn revision properly when we're using git-svn.
28122 - Try not to open more than one descriptor-downloading connection
28123 to an authority at once. This should reduce load on directory
28124 authorities. Fixes bug 366.
28125 - Add cross-certification to newly generated certificates, so that
28126 a signing key is enough information to look up a certificate.
28127 Partial implementation of proposal 157.
28128 - Start serving certificates by <identity digest, signing key digest>
28129 pairs. Partial implementation of proposal 157.
28130 - Clients now never report any stream end reason except 'MISC'.
28131 Implements proposal 148.
28132 - On platforms with a maximum syslog string length, truncate syslog
28133 messages to that length ourselves, rather than relying on the
28134 system to do it for us.
28135 - Optimize out calls to time(NULL) that occur for every IO operation,
28136 or for every cell. On systems where time() is a slow syscall,
28137 this fix will be slightly helpful.
28138 - Exit servers can now answer resolve requests for ip6.arpa addresses.
28139 - When we download a descriptor that we then immediately (as
28140 a directory authority) reject, do not retry downloading it right
28141 away. Should save some bandwidth on authorities. Fix for bug
28142 888. Patch by Sebastian Hahn.
28143 - When a download gets us zero good descriptors, do not notify
28144 Tor that new directory information has arrived.
28145 - Avoid some nasty corner cases in the logic for marking connections
28146 as too old or obsolete or noncanonical for circuits. Partial
28149 o Minor features (controller):
28150 - New CONSENSUS_ARRIVED event to note when a new consensus has
28151 been fetched and validated.
28152 - When we realize that another process has modified our cached
28153 descriptors file, print out a more useful error message rather
28154 than triggering an assertion. Fixes bug 885. Patch from Karsten.
28155 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
28156 controllers to prevent SIGHUP from reloading the
28157 configuration. Fixes bug 856.
28160 - Resume using the correct "REASON=" stream when telling the
28161 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
28162 - When a canonical connection appears later in our internal list
28163 than a noncanonical one for a given OR ID, always use the
28164 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
28166 - Clip the MaxCircuitDirtiness config option to a minimum of 10
28167 seconds. Warn the user if lower values are given in the
28168 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
28169 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
28170 user if lower values are given in the configuration. Bugfix on
28171 0.1.1.17-rc. Patch by Sebastian.
28172 - Fix a race condition when freeing keys shared between main thread
28173 and CPU workers that could result in a memory leak. Bugfix on
28174 0.1.0.1-rc. Fixes bug 889.
28176 o Minor bugfixes (hidden services):
28177 - Do not throw away existing introduction points on SIGHUP (bugfix on
28178 0.0.6pre1); also, do not stall hidden services because we're
28179 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
28180 by John Brooks. Patch by Karsten. Fixes bug 874.
28181 - Fix a memory leak when we decline to add a v2 rendezvous
28182 descriptor to the cache because we already had a v0 descriptor
28183 with the same ID. Bugfix on 0.2.0.18-alpha.
28185 o Deprecated and removed features:
28186 - RedirectExits has been removed. It was deprecated since
28188 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
28189 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
28190 - Cell pools are now always enabled; --disable-cell-pools is ignored.
28192 o Code simplifications and refactoring:
28193 - Rename the confusing or_is_obsolete field to the more appropriate
28194 is_bad_for_new_circs, and move it to or_connection_t where it
28196 - Move edge-only flags from connection_t to edge_connection_t: not
28197 only is this better coding, but on machines of plausible alignment,
28198 it should save 4-8 bytes per connection_t. "Every little bit helps."
28199 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
28200 for consistency; keep old option working for backward compatibility.
28201 - Simplify the code for finding connections to use for a circuit.
28204 Changes in version 0.2.1.8-alpha - 2008-12-08
28205 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
28206 builds better on unusual platforms like Solaris and old OS X, and
28207 fixes a variety of other issues.
28210 - New DirPortFrontPage option that takes an html file and publishes
28211 it as "/" on the DirPort. Now relay operators can provide a
28212 disclaimer without needing to set up a separate webserver. There's
28213 a sample disclaimer in contrib/tor-exit-notice.html.
28216 - When the client is choosing entry guards, now it selects at most
28217 one guard from a given relay family. Otherwise we could end up with
28218 all of our entry points into the network run by the same operator.
28219 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
28222 - Fix a DOS opportunity during the voting signature collection process
28223 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
28224 - Fix a possible segfault when establishing an exit connection. Bugfix
28228 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
28230 - Made Tor a little less aggressive about deleting expired
28231 certificates. Partial fix for bug 854.
28232 - Stop doing unaligned memory access that generated bus errors on
28233 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
28234 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
28235 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
28236 - Make USR2 log-level switch take effect immediately. Bugfix on
28238 - If one win32 nameserver fails to get added, continue adding the
28239 rest, and don't automatically fail.
28240 - Use fcntl() for locking when flock() is not available. Should fix
28241 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
28242 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
28243 could make gcc generate non-functional binary search code. Bugfix
28245 - Build correctly on platforms without socklen_t.
28246 - Avoid potential crash on internal error during signature collection.
28247 Fixes bug 864. Patch from rovv.
28248 - Do not use C's stdio library for writing to log files. This will
28249 improve logging performance by a minute amount, and will stop
28250 leaking fds when our disk is full. Fixes bug 861.
28251 - Stop erroneous use of O_APPEND in cases where we did not in fact
28252 want to re-seek to the end of a file before every last write().
28253 - Correct handling of possible malformed authority signing key
28254 certificates with internal signature types. Fixes bug 880. Bugfix
28256 - Fix a hard-to-trigger resource leak when logging credential status.
28260 - Directory mirrors no longer fetch the v1 directory or
28261 running-routers files. They are obsolete, and nobody asks for them
28262 anymore. This is the first step to making v1 authorities obsolete.
28264 o Minor features (controller):
28265 - Return circuit purposes in response to GETINFO circuit-status. Fixes
28269 Changes in version 0.2.0.32 - 2008-11-20
28270 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
28271 packages (and maybe other packages) noticed by Theo de Raadt, fixes
28272 a smaller security flaw that might allow an attacker to access local
28273 services, further improves hidden service performance, and fixes a
28274 variety of other issues.
28277 - The "User" and "Group" config options did not clear the
28278 supplementary group entries for the Tor process. The "User" option
28279 is now more robust, and we now set the groups to the specified
28280 user's primary group. The "Group" option is now ignored. For more
28281 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
28282 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
28283 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
28284 - The "ClientDNSRejectInternalAddresses" config option wasn't being
28285 consistently obeyed: if an exit relay refuses a stream because its
28286 exit policy doesn't allow it, we would remember what IP address
28287 the relay said the destination address resolves to, even if it's
28288 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
28291 - Fix a DOS opportunity during the voting signature collection process
28292 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
28294 o Major bugfixes (hidden services):
28295 - When fetching v0 and v2 rendezvous service descriptors in parallel,
28296 we were failing the whole hidden service request when the v0
28297 descriptor fetch fails, even if the v2 fetch is still pending and
28298 might succeed. Similarly, if the last v2 fetch fails, we were
28299 failing the whole hidden service request even if a v0 fetch is
28300 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
28301 - When extending a circuit to a hidden service directory to upload a
28302 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
28303 requests failed, because the router descriptor has not been
28304 downloaded yet. In these cases, do not attempt to upload the
28305 rendezvous descriptor, but wait until the router descriptor is
28306 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
28307 descriptor from a hidden service directory for which the router
28308 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
28312 - Fix several infrequent memory leaks spotted by Coverity.
28313 - When testing for libevent functions, set the LDFLAGS variable
28314 correctly. Found by Riastradh.
28315 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
28316 bootstrapping with tunneled directory connections. Bugfix on
28317 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
28318 - When asked to connect to A.B.exit:80, if we don't know the IP for A
28319 and we know that server B rejects most-but-not all connections to
28320 port 80, we would previously reject the connection. Now, we assume
28321 the user knows what they were asking for. Fixes bug 752. Bugfix
28322 on 0.0.9rc5. Diagnosed by BarkerJr.
28323 - If we overrun our per-second write limits a little, count this as
28324 having used up our write allocation for the second, and choke
28325 outgoing directory writes. Previously, we had only counted this when
28326 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
28327 Bugfix on 0.2.0.x (??).
28328 - Remove the old v2 directory authority 'lefkada' from the default
28329 list. It has been gone for many months.
28330 - Stop doing unaligned memory access that generated bus errors on
28331 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
28332 - Make USR2 log-level switch take effect immediately. Bugfix on
28335 o Minor bugfixes (controller):
28336 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
28337 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
28340 Changes in version 0.2.1.7-alpha - 2008-11-08
28341 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
28342 packages (and maybe other packages) noticed by Theo de Raadt, fixes
28343 a smaller security flaw that might allow an attacker to access local
28344 services, adds better defense against DNS poisoning attacks on exit
28345 relays, further improves hidden service performance, and fixes a
28346 variety of other issues.
28349 - The "ClientDNSRejectInternalAddresses" config option wasn't being
28350 consistently obeyed: if an exit relay refuses a stream because its
28351 exit policy doesn't allow it, we would remember what IP address
28352 the relay said the destination address resolves to, even if it's
28353 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
28354 - The "User" and "Group" config options did not clear the
28355 supplementary group entries for the Tor process. The "User" option
28356 is now more robust, and we now set the groups to the specified
28357 user's primary group. The "Group" option is now ignored. For more
28358 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
28359 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
28360 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
28361 - Do not use or believe expired v3 authority certificates. Patch
28362 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
28365 - Now NodeFamily and MyFamily config options allow spaces in
28366 identity fingerprints, so it's easier to paste them in.
28367 Suggested by Lucky Green.
28368 - Implement the 0x20 hack to better resist DNS poisoning: set the
28369 case on outgoing DNS requests randomly, and reject responses that do
28370 not match the case correctly. This logic can be disabled with the
28371 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
28372 of servers that do not reliably preserve case in replies. See
28373 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
28375 - Preserve case in replies to DNSPort requests in order to support
28376 the 0x20 hack for resisting DNS poisoning attacks.
28378 o Hidden service performance improvements:
28379 - When the client launches an introduction circuit, retry with a
28380 new circuit after 30 seconds rather than 60 seconds.
28381 - Launch a second client-side introduction circuit in parallel
28382 after a delay of 15 seconds (based on work by Christian Wilms).
28383 - Hidden services start out building five intro circuits rather
28384 than three, and when the first three finish they publish a service
28385 descriptor using those. Now we publish our service descriptor much
28386 faster after restart.
28389 - Minor fix in the warning messages when you're having problems
28390 bootstrapping; also, be more forgiving of bootstrap problems when
28391 we're still making incremental progress on a given bootstrap phase.
28392 - When we're choosing an exit node for a circuit, and we have
28393 no pending streams, choose a good general exit rather than one that
28394 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
28395 - Send a valid END cell back when a client tries to connect to a
28396 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
28397 840. Patch from rovv.
28398 - If a broken client asks a non-exit router to connect somewhere,
28399 do not even do the DNS lookup before rejecting the connection.
28400 Fixes another case of bug 619. Patch from rovv.
28401 - Fix another case of assuming, when a specific exit is requested,
28402 that we know more than the user about what hosts it allows.
28403 Fixes another case of bug 752. Patch from rovv.
28404 - Check which hops rendezvous stream cells are associated with to
28405 prevent possible guess-the-streamid injection attacks from
28406 intermediate hops. Fixes another case of bug 446. Based on patch
28408 - Avoid using a negative right-shift when comparing 32-bit
28409 addresses. Possible fix for bug 845 and bug 811.
28410 - Make the assert_circuit_ok() function work correctly on circuits that
28411 have already been marked for close.
28412 - Fix read-off-the-end-of-string error in unit tests when decoding
28413 introduction points.
28414 - Fix uninitialized size field for memory area allocation: may improve
28415 memory performance during directory parsing.
28416 - Treat duplicate certificate fetches as failures, so that we do
28417 not try to re-fetch an expired certificate over and over and over.
28418 - Do not say we're fetching a certificate when we'll in fact skip it
28419 because of a pending download.
28422 Changes in version 0.2.1.6-alpha - 2008-09-30
28423 Tor 0.2.1.6-alpha further improves performance and robustness of
28424 hidden services, starts work on supporting per-country relay selection,
28425 and fixes a variety of smaller issues.
28428 - Implement proposal 121: make it possible to build hidden services
28429 that only certain clients are allowed to connect to. This is
28430 enforced at several points, so that unauthorized clients are unable
28431 to send INTRODUCE cells to the service, or even (depending on the
28432 type of authentication) to learn introduction points. This feature
28433 raises the bar for certain kinds of active attacks against hidden
28434 services. Code by Karsten Loesing.
28435 - Relays now store and serve v2 hidden service descriptors by default,
28436 i.e., the new default value for HidServDirectoryV2 is 1. This is
28437 the last step in proposal 114, which aims to make hidden service
28438 lookups more reliable.
28439 - Start work to allow node restrictions to include country codes. The
28440 syntax to exclude nodes in a country with country code XX is
28441 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
28442 refinement to decide what config options should take priority if
28443 you ask to both use a particular node and exclude it.
28444 - Allow ExitNodes list to include IP ranges and country codes, just
28445 like the Exclude*Nodes lists. Patch from Robert Hogan.
28448 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
28449 Tor to fail to start if you had it configured to use a bridge
28450 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
28451 - When extending a circuit to a hidden service directory to upload a
28452 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
28453 requests failed, because the router descriptor had not been
28454 downloaded yet. In these cases, we now wait until the router
28455 descriptor is downloaded, and then retry. Likewise, clients
28456 now skip over a hidden service directory if they don't yet have
28457 its router descriptor, rather than futilely requesting it and
28458 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
28460 - When fetching v0 and v2 rendezvous service descriptors in parallel,
28461 we were failing the whole hidden service request when the v0
28462 descriptor fetch fails, even if the v2 fetch is still pending and
28463 might succeed. Similarly, if the last v2 fetch fails, we were
28464 failing the whole hidden service request even if a v0 fetch is
28465 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
28466 - DNS replies need to have names matching their requests, but
28467 these names should be in the questions section, not necessarily
28468 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
28471 - Update to the "September 1 2008" ip-to-country file.
28472 - Allow ports 465 and 587 in the default exit policy again. We had
28473 rejected them in 0.1.0.15, because back in 2005 they were commonly
28474 misconfigured and ended up as spam targets. We hear they are better
28475 locked down these days.
28476 - Use a lockfile to make sure that two Tor processes are not
28477 simultaneously running with the same datadir.
28478 - Serve the latest v3 networkstatus consensus via the control
28479 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
28480 - Better logging about stability/reliability calculations on directory
28482 - Drop the requirement to have an open dir port for storing and
28483 serving v2 hidden service descriptors.
28484 - Directory authorities now serve a /tor/dbg-stability.txt URL to
28485 help debug WFU and MTBF calculations.
28486 - Implement most of Proposal 152: allow specialized servers to permit
28487 single-hop circuits, and clients to use those servers to build
28488 single-hop circuits when using a specialized controller. Patch
28489 from Josh Albrecht. Resolves feature request 768.
28490 - Add a -p option to tor-resolve for specifying the SOCKS port: some
28491 people find host:port too confusing.
28492 - Make TrackHostExit mappings expire a while after their last use, not
28493 after their creation. Patch from Robert Hogan.
28494 - Provide circuit purposes along with circuit events to the controller.
28497 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
28499 - Fixed some memory leaks -- some quite frequent, some almost
28500 impossible to trigger -- based on results from Coverity.
28501 - When testing for libevent functions, set the LDFLAGS variable
28502 correctly. Found by Riastradh.
28503 - Fix an assertion bug in parsing policy-related options; possible fix
28505 - Catch and report a few more bootstrapping failure cases when Tor
28506 fails to establish a TCP connection. Cleanup on 0.2.1.x.
28507 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
28508 bootstrapping with tunneled directory connections. Bugfix on
28509 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
28510 - When asked to connect to A.B.exit:80, if we don't know the IP for A
28511 and we know that server B rejects most-but-not all connections to
28512 port 80, we would previously reject the connection. Now, we assume
28513 the user knows what they were asking for. Fixes bug 752. Bugfix
28514 on 0.0.9rc5. Diagnosed by BarkerJr.
28515 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
28516 service directories if they have no advertised dir port. Bugfix
28518 - If we overrun our per-second write limits a little, count this as
28519 having used up our write allocation for the second, and choke
28520 outgoing directory writes. Previously, we had only counted this when
28521 we had met our limits precisely. Fixes bug 824. Patch by rovv.
28522 Bugfix on 0.2.0.x (??).
28523 - Avoid a "0 divided by 0" calculation when calculating router uptime
28524 at directory authorities. Bugfix on 0.2.0.8-alpha.
28525 - Make DNS resolved controller events into "CLOSED", not
28526 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
28528 - Fix a bug where an unreachable relay would establish enough
28529 reachability testing circuits to do a bandwidth test -- if
28530 we already have a connection to the middle hop of the testing
28531 circuit, then it could establish the last hop by using the existing
28532 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
28533 circuits no longer use entry guards in 0.2.1.3-alpha.
28534 - If we have correct permissions on $datadir, we complain to stdout
28535 and fail to start. But dangerous permissions on
28536 $datadir/cached-status/ would cause us to open a log and complain
28537 there. Now complain to stdout and fail to start in both cases. Fixes
28538 bug 820, reported by seeess.
28539 - Remove the old v2 directory authority 'lefkada' from the default
28540 list. It has been gone for many months.
28542 o Code simplifications and refactoring:
28543 - Revise the connection_new functions so that a more typesafe variant
28544 exists. This will work better with Coverity, and let us find any
28545 actual mistakes we're making here.
28546 - Refactor unit testing logic so that dmalloc can be used sensibly
28547 with unit tests to check for memory leaks.
28548 - Move all hidden-service related fields from connection and circuit
28549 structure to substructures: this way they won't eat so much memory.
28552 Changes in version 0.2.0.31 - 2008-09-03
28553 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
28554 a big bug we're seeing where in rare cases traffic from one Tor stream
28555 gets mixed into another stream, and fixes a variety of smaller issues.
28558 - Make sure that two circuits can never exist on the same connection
28559 with the same circuit ID, even if one is marked for close. This
28560 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
28561 - Relays now reject risky extend cells: if the extend cell includes
28562 a digest of all zeroes, or asks to extend back to the relay that
28563 sent the extend cell, tear down the circuit. Ideas suggested
28565 - If not enough of our entry guards are available so we add a new
28566 one, we might use the new one even if it overlapped with the
28567 current circuit's exit relay (or its family). Anonymity bugfix
28568 pointed out by rovv.
28571 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
28572 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
28573 - Correctly detect the presence of the linux/netfilter_ipv4.h header
28574 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
28575 - Pick size of default geoip filename string correctly on windows.
28576 Fixes bug 806. Bugfix on 0.2.0.30.
28577 - Make the autoconf script accept the obsolete --with-ssl-dir
28578 option as an alias for the actually-working --with-openssl-dir
28579 option. Fix the help documentation to recommend --with-openssl-dir.
28580 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
28581 - When using the TransPort option on OpenBSD, and using the User
28582 option to change UID and drop privileges, make sure to open
28583 /dev/pf before dropping privileges. Fixes bug 782. Patch from
28584 Christopher Davis. Bugfix on 0.1.2.1-alpha.
28585 - Try to attach connections immediately upon receiving a RENDEZVOUS2
28586 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
28587 on the client side when connecting to a hidden service. Bugfix
28588 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
28589 - When closing an application-side connection because its circuit is
28590 getting torn down, generate the stream event correctly. Bugfix on
28591 0.1.2.x. Anonymous patch.
28594 Changes in version 0.2.1.5-alpha - 2008-08-31
28595 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
28596 in a lot of the infrastructure for adding authorization to hidden
28597 services, lays the groundwork for having clients read their load
28598 balancing information out of the networkstatus consensus rather than
28599 the individual router descriptors, addresses two potential anonymity
28600 issues, and fixes a variety of smaller issues.
28603 - Convert many internal address representations to optionally hold
28605 - Generate and accept IPv6 addresses in many protocol elements.
28606 - Make resolver code handle nameservers located at ipv6 addresses.
28607 - Begin implementation of proposal 121 ("Client authorization for
28608 hidden services"): configure hidden services with client
28609 authorization, publish descriptors for them, and configure
28610 authorization data for hidden services at clients. The next
28611 step is to actually access hidden services that perform client
28613 - More progress toward proposal 141: Network status consensus
28614 documents and votes now contain bandwidth information for each
28615 router and a summary of that router's exit policy. Eventually this
28616 will be used by clients so that they do not have to download every
28617 known descriptor before building circuits.
28619 o Major bugfixes (on 0.2.0.x and before):
28620 - When sending CREATED cells back for a given circuit, use a 64-bit
28621 connection ID to find the right connection, rather than an addr:port
28622 combination. Now that we can have multiple OR connections between
28623 the same ORs, it is no longer possible to use addr:port to uniquely
28624 identify a connection.
28625 - Relays now reject risky extend cells: if the extend cell includes
28626 a digest of all zeroes, or asks to extend back to the relay that
28627 sent the extend cell, tear down the circuit. Ideas suggested
28629 - If not enough of our entry guards are available so we add a new
28630 one, we might use the new one even if it overlapped with the
28631 current circuit's exit relay (or its family). Anonymity bugfix
28632 pointed out by rovv.
28635 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
28636 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
28637 - When using the TransPort option on OpenBSD, and using the User
28638 option to change UID and drop privileges, make sure to open /dev/pf
28639 before dropping privileges. Fixes bug 782. Patch from Christopher
28640 Davis. Bugfix on 0.1.2.1-alpha.
28641 - Correctly detect the presence of the linux/netfilter_ipv4.h header
28642 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
28643 - Add a missing safe_str() call for a debug log message.
28644 - Use 64 bits instead of 32 bits for connection identifiers used with
28645 the controller protocol, to greatly reduce risk of identifier reuse.
28646 - Make the autoconf script accept the obsolete --with-ssl-dir
28647 option as an alias for the actually-working --with-openssl-dir
28648 option. Fix the help documentation to recommend --with-openssl-dir.
28649 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
28652 - Rate-limit too-many-sockets messages: when they happen, they happen
28653 a lot. Resolves bug 748.
28654 - Resist DNS poisoning a little better by making sure that names in
28655 answer sections match.
28656 - Print the SOCKS5 error message string as well as the error code
28657 when a tor-resolve request fails. Patch from Jacob.
28660 Changes in version 0.2.1.4-alpha - 2008-08-04
28661 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
28664 - The address part of exit policies was not correctly written
28665 to router descriptors. This generated router descriptors that failed
28666 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
28668 - Tor triggered a false assert when extending a circuit to a relay
28669 but we already have a connection open to that relay. Noticed by
28670 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
28673 - Fix a hidden service logging bug: in some edge cases, the router
28674 descriptor of a previously picked introduction point becomes
28675 obsolete and we need to give up on it rather than continually
28676 complaining that it has become obsolete. Observed by xiando. Bugfix
28679 o Removed features:
28680 - Take out the TestVia config option, since it was a workaround for
28681 a bug that was fixed in Tor 0.1.1.21.
28684 Changes in version 0.2.1.3-alpha - 2008-08-03
28685 Tor 0.2.1.3-alpha implements most of the pieces to prevent
28686 infinite-length circuit attacks (see proposal 110); fixes a bug that
28687 might cause exit relays to corrupt streams they send back; allows
28688 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
28689 ExcludeExitNodes config options; and fixes a big pile of bugs.
28691 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
28692 - Send a bootstrap problem "warn" event on the first problem if the
28693 reason is NO_ROUTE (that is, our network is down).
28696 - Implement most of proposal 110: The first K cells to be sent
28697 along a circuit are marked as special "early" cells; only K "early"
28698 cells will be allowed. Once this code is universal, we can block
28699 certain kinds of DOS attack by requiring that EXTEND commands must
28700 be sent using an "early" cell.
28703 - Try to attach connections immediately upon receiving a RENDEZVOUS2
28704 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
28705 on the client side when connecting to a hidden service. Bugfix
28706 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
28707 - Ensure that two circuits can never exist on the same connection
28708 with the same circuit ID, even if one is marked for close. This
28709 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
28712 - When relays do their initial bandwidth measurement, don't limit
28713 to just our entry guards for the test circuits. Otherwise we tend
28714 to have multiple test circuits going through a single entry guard,
28715 which makes our bandwidth test less accurate. Fixes part of bug 654;
28716 patch contributed by Josh Albrecht.
28717 - Add an ExcludeExitNodes option so users can list a set of nodes
28718 that should be be excluded from the exit node position, but
28719 allowed elsewhere. Implements proposal 151.
28720 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
28721 ExcludeNodes and ExcludeExitNodes lists.
28722 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
28723 be more efficient. Formerly it was quadratic in the number of
28724 servers; now it should be linear. Fixes bug 509.
28725 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
28726 and n_conn_id_digest fields into a separate structure that's
28727 only needed when the circuit has not yet attached to an n_conn.
28730 - Change the contrib/tor.logrotate script so it makes the new
28731 logs as "_tor:_tor" rather than the default, which is generally
28732 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
28733 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
28734 warnings (occasionally), but it can also cause the compiler to
28735 eliminate error-checking code. Suggested by Peter Gutmann.
28736 - When a hidden service is giving up on an introduction point candidate
28737 that was not included in the last published rendezvous descriptor,
28738 don't reschedule publication of the next descriptor. Fixes bug 763.
28740 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
28741 HiddenServiceExcludeNodes as obsolete: they never worked properly,
28742 and nobody claims to be using them. Fixes bug 754. Bugfix on
28743 0.1.0.1-rc. Patch from Christian Wilms.
28744 - Fix a small alignment and memory-wasting bug on buffer chunks.
28747 o Minor bugfixes (controller):
28748 - When closing an application-side connection because its circuit
28749 is getting torn down, generate the stream event correctly.
28750 Bugfix on 0.1.2.x. Anonymous patch.
28752 o Removed features:
28753 - Remove all backward-compatibility code to support relays running
28754 versions of Tor so old that they no longer work at all on the
28758 Changes in version 0.2.0.30 - 2008-07-15
28760 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
28761 warnings (occasionally), but it can also cause the compiler to
28762 eliminate error-checking code. Suggested by Peter Gutmann.
28765 Changes in version 0.2.0.29-rc - 2008-07-08
28766 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
28767 hidden-service performance bugs, and fixes a bunch of smaller bugs.
28770 - If you have more than one bridge but don't know their keys,
28771 you would only launch a request for the descriptor of the first one
28772 on your list. (Tor considered launching requests for the others, but
28773 found that it already had a connection on the way for $0000...0000
28774 so it didn't open another.) Bugfix on 0.2.0.x.
28775 - If you have more than one bridge but don't know their keys, and the
28776 connection to one of the bridges failed, you would cancel all
28777 pending bridge connections. (After all, they all have the same
28778 digest.) Bugfix on 0.2.0.x.
28779 - When a hidden service was trying to establish an introduction point,
28780 and Tor had built circuits preemptively for such purposes, we
28781 were ignoring all the preemptive circuits and launching a new one
28782 instead. Bugfix on 0.2.0.14-alpha.
28783 - When a hidden service was trying to establish an introduction point,
28784 and Tor *did* manage to reuse one of the preemptively built
28785 circuits, it didn't correctly remember which one it used,
28786 so it asked for another one soon after, until there were no
28787 more preemptive circuits, at which point it launched one from
28788 scratch. Bugfix on 0.0.9.x.
28789 - Make directory servers include the X-Your-Address-Is: http header in
28790 their responses even for begin_dir conns. Now clients who only
28791 ever use begin_dir connections still have a way to learn their IP
28792 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
28795 - Fix a macro/CPP interaction that was confusing some compilers:
28796 some GCCs don't like #if/#endif pairs inside macro arguments.
28798 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
28799 Fixes bug 704; fix from Steven Murdoch.
28800 - When opening /dev/null in finish_daemonize(), do not pass the
28801 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
28802 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
28803 - Correctly detect transparent proxy support on Linux hosts that
28804 require in.h to be included before netfilter_ipv4.h. Patch
28806 - Disallow session resumption attempts during the renegotiation
28807 stage of the v2 handshake protocol. Clients should never be trying
28808 session resumption at this point, but apparently some did, in
28809 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
28810 found by Geoff Goodell.
28813 Changes in version 0.2.1.2-alpha - 2008-06-20
28814 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
28815 make it easier to set up your own private Tor network; fixes several
28816 big bugs with using more than one bridge relay; fixes a big bug with
28817 offering hidden services quickly after Tor starts; and uses a better
28818 API for reporting potential bootstrapping problems to the controller.
28821 - New TestingTorNetwork config option to allow adjustment of
28822 previously constant values that, while reasonable, could slow
28823 bootstrapping. Implements proposal 135. Patch from Karsten.
28826 - If you have more than one bridge but don't know their digests,
28827 you would only learn a request for the descriptor of the first one
28828 on your list. (Tor considered launching requests for the others, but
28829 found that it already had a connection on the way for $0000...0000
28830 so it didn't open another.) Bugfix on 0.2.0.x.
28831 - If you have more than one bridge but don't know their digests,
28832 and the connection to one of the bridges failed, you would cancel
28833 all pending bridge connections. (After all, they all have the
28834 same digest.) Bugfix on 0.2.0.x.
28835 - When establishing a hidden service, introduction points that
28836 originate from cannibalized circuits are completely ignored and not
28837 included in rendezvous service descriptors. This might be another
28838 reason for delay in making a hidden service available. Bugfix
28839 from long ago (0.0.9.x?)
28842 - Allow OpenSSL to use dynamic locks if it wants.
28843 - When building a consensus, do not include routers that are down.
28844 This will cut down 30% to 40% on consensus size. Implements
28846 - In directory authorities' approved-routers files, allow
28847 fingerprints with or without space.
28848 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
28849 controller can query our current bootstrap state in case it attaches
28850 partway through and wants to catch up.
28851 - Send an initial "Starting" bootstrap status event, so we have a
28852 state to start out in.
28855 - Asking for a conditional consensus at .../consensus/<fingerprints>
28856 would crash a dirserver if it did not already have a
28857 consensus. Bugfix on 0.2.1.1-alpha.
28858 - Clean up some macro/CPP interactions: some GCC versions don't like
28859 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
28862 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
28863 - Directory authorities shouldn't complain about bootstrapping
28864 problems just because they do a lot of reachability testing and
28865 some of the connection attempts fail.
28866 - Start sending "count" and "recommendation" key/value pairs in
28867 bootstrap problem status events, so the controller can hear about
28868 problems even before Tor decides they're worth reporting for sure.
28869 - If you're using bridges, generate "bootstrap problem" warnings
28870 as soon as you run out of working bridges, rather than waiting
28871 for ten failures -- which will never happen if you have less than
28873 - If we close our OR connection because there's been a circuit
28874 pending on it for too long, we were telling our bootstrap status
28875 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
28878 Changes in version 0.2.1.1-alpha - 2008-06-13
28879 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
28880 were making the Tor process bloat especially on Linux; makes our TLS
28881 handshake blend in better; sends "bootstrap phase" status events to
28882 the controller, so it can keep the user informed of progress (and
28883 problems) fetching directory information and establishing circuits;
28884 and adds a variety of smaller features.
28887 - More work on making our TLS handshake blend in: modify the list
28888 of ciphers advertised by OpenSSL in client mode to even more
28889 closely resemble a common web browser. We cheat a little so that
28890 we can advertise ciphers that the locally installed OpenSSL doesn't
28892 - Start sending "bootstrap phase" status events to the controller,
28893 so it can keep the user informed of progress fetching directory
28894 information and establishing circuits. Also inform the controller
28895 if we think we're stuck at a particular bootstrap phase. Implements
28897 - Resume using OpenSSL's RAND_poll() for better (and more portable)
28898 cross-platform entropy collection again. We used to use it, then
28899 stopped using it because of a bug that could crash systems that
28900 called RAND_poll when they had a lot of fds open. It looks like the
28901 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
28902 at startup, and to call RAND_poll() when we reseed later only if
28903 we have a non-buggy OpenSSL version.
28906 - When we choose to abandon a new entry guard because we think our
28907 older ones might be better, close any circuits pending on that
28908 new entry guard connection. This fix should make us recover much
28909 faster when our network is down and then comes back. Bugfix on
28910 0.1.2.8-beta; found by lodger.
28912 o Memory fixes and improvements:
28913 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
28914 to avoid unused RAM in buffer chunks and memory pools.
28915 - Speed up parsing and cut down on memory fragmentation by using
28916 stack-style allocations for parsing directory objects. Previously,
28917 this accounted for over 40% of allocations from within Tor's code
28918 on a typical directory cache.
28919 - Use a Bloom filter rather than a digest-based set to track which
28920 descriptors we need to keep around when we're cleaning out old
28921 router descriptors. This speeds up the computation significantly,
28922 and may reduce fragmentation.
28923 - Reduce the default smartlist size from 32 to 16; it turns out that
28924 most smartlists hold around 8-12 elements tops.
28925 - Make dumpstats() log the fullness and size of openssl-internal
28927 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
28928 patch to their OpenSSL, turn it on to save memory on servers. This
28929 patch will (with any luck) get included in a mainline distribution
28931 - Never use OpenSSL compression: it wastes RAM and CPU trying to
28932 compress cells, which are basically all encrypted, compressed,
28936 - Stop reloading the router list from disk for no reason when we
28937 run out of reachable directory mirrors. Once upon a time reloading
28938 it would set the 'is_running' flag back to 1 for them. It hasn't
28939 done that for a long time.
28940 - In very rare situations new hidden service descriptors were
28941 published earlier than 30 seconds after the last change to the
28942 service. (We currently think that a hidden service descriptor
28943 that's been stable for 30 seconds is worth publishing.)
28946 - Allow separate log levels to be configured for different logging
28947 domains. For example, this allows one to log all notices, warnings,
28948 or errors, plus all memory management messages of level debug or
28949 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
28950 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
28951 and stop using a warning that had become unfixably verbose under
28953 - New --hush command-line option similar to --quiet. While --quiet
28954 disables all logging to the console on startup, --hush limits the
28955 output to messages of warning and error severity.
28956 - Servers support a new URL scheme for consensus downloads that
28957 allows the client to specify which authorities are trusted.
28958 The server then only sends the consensus if the client will trust
28959 it. Otherwise a 404 error is sent back. Clients use this
28960 new scheme when the server supports it (meaning it's running
28961 0.2.1.1-alpha or later). Implements proposal 134.
28962 - New configure/torrc options (--enable-geoip-stats,
28963 DirRecordUsageByCountry) to record how many IPs we've served
28964 directory info to in each country code, how many status documents
28965 total we've sent to each country code, and what share of the total
28966 directory requests we should expect to see.
28967 - Use the TLS1 hostname extension to more closely resemble browser
28969 - Lots of new unit tests.
28970 - Add a macro to implement the common pattern of iterating through
28971 two parallel lists in lockstep.
28974 Changes in version 0.2.0.28-rc - 2008-06-13
28975 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
28976 performance bug, and fixes a bunch of smaller bugs.
28979 - Fix a bug where, when we were choosing the 'end stream reason' to
28980 put in our relay end cell that we send to the exit relay, Tor
28981 clients on Windows were sometimes sending the wrong 'reason'. The
28982 anonymity problem is that exit relays may be able to guess whether
28983 the client is running Windows, thus helping partition the anonymity
28984 set. Down the road we should stop sending reasons to exit relays,
28985 or otherwise prevent future versions of this bug.
28988 - While setting up a hidden service, some valid introduction circuits
28989 were overlooked and abandoned. This might be the reason for
28990 the long delay in making a hidden service available. Bugfix on
28994 - Update to the "June 9 2008" ip-to-country file.
28995 - Run 'make test' as part of 'make dist', so we stop releasing so
28996 many development snapshots that fail their unit tests.
28999 - When we're checking if we have enough dir info for each relay
29000 to begin establishing circuits, make sure that we actually have
29001 the descriptor listed in the consensus, not just any descriptor.
29003 - Bridge relays no longer print "xx=0" in their extrainfo document
29004 for every single country code in the geoip db. Bugfix on
29006 - Only warn when we fail to load the geoip file if we were planning to
29007 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
29008 - If we change our MaxAdvertisedBandwidth and then reload torrc,
29009 Tor won't realize it should publish a new relay descriptor. Fixes
29010 bug 688, reported by mfr. Bugfix on 0.1.2.x.
29011 - When we haven't had any application requests lately, don't bother
29012 logging that we have expired a bunch of descriptors. Bugfix
29014 - Make relay cells written on a connection count as non-padding when
29015 tracking how long a connection has been in use. Bugfix on
29016 0.2.0.1-alpha. Spotted by lodger.
29017 - Fix unit tests in 0.2.0.27-rc.
29018 - Fix compile on Windows.
29021 Changes in version 0.2.0.27-rc - 2008-06-03
29022 Tor 0.2.0.27-rc adds a few features we left out of the earlier
29023 release candidates. In particular, we now include an IP-to-country
29024 GeoIP database, so controllers can easily look up what country a
29025 given relay is in, and so bridge relays can give us some sanitized
29026 summaries about which countries are making use of bridges. (See proposal
29027 126-geoip-fetching.txt for details.)
29030 - Include an IP-to-country GeoIP file in the tarball, so bridge
29031 relays can report sanitized summaries of the usage they're seeing.
29034 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
29035 Robert Hogan. Fixes the first part of bug 681.
29036 - Make bridge authorities never serve extrainfo docs.
29037 - Add support to detect Libevent versions in the 1.4.x series
29039 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
29040 - Include a new contrib/tor-exit-notice.html file that exit relay
29041 operators can put on their website to help reduce abuse queries.
29044 - When tunneling an encrypted directory connection, and its first
29045 circuit fails, do not leave it unattached and ask the controller
29046 to deal. Fixes the second part of bug 681.
29047 - Make bridge authorities correctly expire old extrainfo documents
29051 Changes in version 0.2.0.26-rc - 2008-05-13
29052 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
29053 in Debian's OpenSSL packages. All users running any 0.2.0.x version
29054 should upgrade, whether they're running Debian or not.
29056 o Major security fixes:
29057 - Use new V3 directory authority keys on the tor26, gabelmoo, and
29058 moria1 V3 directory authorities. The old keys were generated with
29059 a vulnerable version of Debian's OpenSSL package, and must be
29060 considered compromised. Other authorities' keys were not generated
29061 with an affected version of OpenSSL.
29064 - List authority signatures as "unrecognized" based on DirServer
29065 lines, not on cert cache. Bugfix on 0.2.0.x.
29068 - Add a new V3AuthUseLegacyKey option to make it easier for
29069 authorities to change their identity keys if they have to.
29072 Changes in version 0.2.0.25-rc - 2008-04-23
29073 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
29076 - Remember to initialize threading before initializing logging.
29077 Otherwise, many BSD-family implementations will crash hard on
29078 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
29081 - Authorities correctly free policies on bad servers on
29082 exit. Fixes bug 672. Bugfix on 0.2.0.x.
29085 Changes in version 0.2.0.24-rc - 2008-04-22
29086 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
29087 v3 directory authority, makes relays with dynamic IP addresses and no
29088 DirPort notice more quickly when their IP address changes, fixes a few
29089 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
29091 o New directory authorities:
29092 - Take lefkada out of the list of v3 directory authorities, since
29093 it has been down for months.
29094 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
29098 - Detect address changes more quickly on non-directory mirror
29099 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
29101 o Minor features (security):
29102 - Reject requests for reverse-dns lookup of names that are in
29103 a private address space. Patch from lodger.
29104 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
29107 o Minor bugfixes (crashes):
29108 - Avoid a rare assert that can trigger when Tor doesn't have much
29109 directory information yet and it tries to fetch a v2 hidden
29110 service descriptor. Fixes bug 651, reported by nwf.
29111 - Initialize log mutex before initializing dmalloc. Otherwise,
29112 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
29113 - Use recursive pthread mutexes in order to avoid deadlock when
29114 logging debug-level messages to a controller. Bug spotted by nwf,
29115 bugfix on 0.2.0.16-alpha.
29117 o Minor bugfixes (resource management):
29118 - Keep address policies from leaking memory: start their refcount
29119 at 1, not 2. Bugfix on 0.2.0.16-alpha.
29120 - Free authority certificates on exit, so they don't look like memory
29121 leaks. Bugfix on 0.2.0.19-alpha.
29122 - Free static hashtables for policy maps and for TLS connections on
29123 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
29124 - Avoid allocating extra space when computing consensuses on 64-bit
29125 platforms. Bug spotted by aakova.
29127 o Minor bugfixes (misc):
29128 - Do not read the configuration file when we've only been told to
29129 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
29130 based on patch from Sebastian Hahn.
29131 - Exit relays that are used as a client can now reach themselves
29132 using the .exit notation, rather than just launching an infinite
29133 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
29134 - When attempting to open a logfile fails, tell us why.
29135 - Fix a dumb bug that was preventing us from knowing that we should
29136 preemptively build circuits to handle expected directory requests.
29137 Fixes bug 660. Bugfix on 0.1.2.x.
29138 - Warn less verbosely about clock skew from netinfo cells from
29139 untrusted sources. Fixes bug 663.
29140 - Make controller stream events for DNS requests more consistent,
29141 by adding "new stream" events for DNS requests, and removing
29142 spurious "stream closed" events" for cached reverse resolves.
29143 Patch from mwenge. Fixes bug 646.
29144 - Correctly notify one-hop connections when a circuit build has
29145 failed. Possible fix for bug 669. Found by lodger.
29148 Changes in version 0.2.0.23-rc - 2008-03-24
29149 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
29150 makes bootstrapping faster if the first directory mirror you contact
29151 is down. The bundles also include the new Vidalia 0.1.2 release.
29154 - When a tunneled directory request is made to a directory server
29155 that's down, notice after 30 seconds rather than 120 seconds. Also,
29156 fail any begindir streams that are pending on it, so they can
29157 retry elsewhere. This was causing multi-minute delays on bootstrap.
29160 Changes in version 0.2.0.22-rc - 2008-03-18
29161 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
29162 enables encrypted directory connections by default for non-relays, fixes
29163 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
29164 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
29167 - Enable encrypted directory connections by default for non-relays,
29168 so censor tools that block Tor directory connections based on their
29169 plaintext patterns will no longer work. This means Tor works in
29170 certain censored countries by default again.
29173 - Make sure servers always request certificates from clients during
29174 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
29175 - Do not enter a CPU-eating loop when a connection is closed in
29176 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
29177 diagnosed by lodger; bugfix on 0.2.0.20-rc.
29178 - Fix assertion failure that could occur when a blocked circuit
29179 became unblocked, and it had pending client DNS requests. Bugfix
29180 on 0.2.0.1-alpha. Fixes bug 632.
29182 o Minor bugfixes (on 0.1.2.x):
29183 - Generate "STATUS_SERVER" events rather than misspelled
29184 "STATUS_SEVER" events. Caught by mwenge.
29185 - When counting the number of bytes written on a TLS connection,
29186 look at the BIO actually used for writing to the network, not
29187 at the BIO used (sometimes) to buffer data for the network.
29188 Looking at different BIOs could result in write counts on the
29189 order of ULONG_MAX. Fixes bug 614.
29190 - On Windows, correctly detect errors when listing the contents of
29191 a directory. Fix from lodger.
29193 o Minor bugfixes (on 0.2.0.x):
29194 - Downgrade "sslv3 alert handshake failure" message to INFO.
29195 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
29196 left BandwidthRate and BandwidthBurst at the default, we would be
29197 silently limited by those defaults. Now raise them to match the
29198 RelayBandwidth* values.
29199 - Fix the SVK version detection logic to work correctly on a branch.
29200 - Make --enable-openbsd-malloc work correctly on Linux with alpha
29201 CPUs. Fixes bug 625.
29202 - Logging functions now check that the passed severity is sane.
29203 - Use proper log levels in the testsuite call of
29204 get_interface_address6().
29205 - When using a nonstandard malloc, do not use the platform values for
29206 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
29207 - Make the openbsd malloc code use 8k pages on alpha CPUs and
29209 - Detect mismatched page sizes when using --enable-openbsd-malloc.
29210 - Avoid double-marked-for-close warning when certain kinds of invalid
29211 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
29212 for bug 617. Bugfix on 0.2.0.1-alpha.
29213 - Make sure that the "NULL-means-reject *:*" convention is followed by
29214 all the policy manipulation functions, avoiding some possible crash
29215 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
29216 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
29217 actually works, and doesn't warn about every single reverse lookup.
29218 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
29221 - Only log guard node status when guard node status has changed.
29222 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
29223 make "INFO" 75% less verbose.
29226 Changes in version 0.2.0.21-rc - 2008-03-02
29227 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
29228 makes Tor work well with Vidalia again, fixes a rare assert bug,
29229 and fixes a pair of more minor bugs. The bundles also include Vidalia
29230 0.1.0 and Torbutton 1.1.16.
29233 - The control port should declare that it requires password auth
29234 when HashedControlSessionPassword is set too. Patch from Matt Edman;
29235 bugfix on 0.2.0.20-rc. Fixes bug 615.
29236 - Downgrade assert in connection_buckets_decrement() to a log message.
29237 This may help us solve bug 614, and in any case will make its
29238 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
29239 - We were sometimes miscounting the number of bytes read from the
29240 network, causing our rate limiting to not be followed exactly.
29241 Bugfix on 0.2.0.16-alpha. Reported by lodger.
29244 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
29245 OpenSSL versions should have been working fine. Diagnosis and patch
29246 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
29247 Bugfix on 0.2.0.20-rc.
29250 Changes in version 0.2.0.20-rc - 2008-02-24
29251 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
29252 makes more progress towards normalizing Tor's TLS handshake, makes
29253 hidden services work better again, helps relays bootstrap if they don't
29254 know their IP address, adds optional support for linking in openbsd's
29255 allocator or tcmalloc, allows really fast relays to scale past 15000
29256 sockets, and fixes a bunch of minor bugs reported by Veracode.
29259 - Enable the revised TLS handshake based on the one designed by
29260 Steven Murdoch in proposal 124, as revised in proposal 130. It
29261 includes version negotiation for OR connections as described in
29262 proposal 105. The new handshake is meant to be harder for censors
29263 to fingerprint, and it adds the ability to detect certain kinds of
29264 man-in-the-middle traffic analysis attacks. The version negotiation
29265 feature will allow us to improve Tor's link protocol more safely
29267 - Choose which bridge to use proportional to its advertised bandwidth,
29268 rather than uniformly at random. This should speed up Tor for
29269 bridge users. Also do this for people who set StrictEntryNodes.
29270 - When a TrackHostExits-chosen exit fails too many times in a row,
29271 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
29274 - Resolved problems with (re-)fetching hidden service descriptors.
29275 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
29276 and 0.2.0.19-alpha.
29277 - If we only ever used Tor for hidden service lookups or posts, we
29278 would stop building circuits and start refusing connections after
29279 24 hours, since we falsely believed that Tor was dormant. Reported
29280 by nwf; bugfix on 0.1.2.x.
29281 - Servers that don't know their own IP address should go to the
29282 authorities for their first directory fetch, even if their DirPort
29283 is off or if they don't know they're reachable yet. This will help
29284 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
29285 - When counting the number of open sockets, count not only the number
29286 of sockets we have received from the socket() call, but also
29287 the number we've gotten from accept() and socketpair(). This bug
29288 made us fail to count all sockets that we were using for incoming
29289 connections. Bugfix on 0.2.0.x.
29290 - Fix code used to find strings within buffers, when those strings
29291 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
29292 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
29293 - Add a new __HashedControlSessionPassword option for controllers
29294 to use for one-off session password hashes that shouldn't get
29295 saved to disk by SAVECONF --- Vidalia users were accumulating a
29296 pile of HashedControlPassword lines in their torrc files, one for
29297 each time they had restarted Tor and then clicked Save. Make Tor
29298 automatically convert "HashedControlPassword" to this new option but
29299 only when it's given on the command line. Partial fix for bug 586.
29301 o Minor features (performance):
29302 - Tune parameters for cell pool allocation to minimize amount of
29304 - Add OpenBSD malloc code from phk as an optional malloc
29305 replacement on Linux: some glibc libraries do very poorly
29306 with Tor's memory allocation patterns. Pass
29307 --enable-openbsd-malloc to get the replacement malloc code.
29308 - Add a --with-tcmalloc option to the configure script to link
29309 against tcmalloc (if present). Does not yet search for
29310 non-system include paths.
29311 - Stop imposing an arbitrary maximum on the number of file descriptors
29312 used for busy servers. Bug reported by Olaf Selke; patch from
29315 o Minor features (other):
29316 - When SafeLogging is disabled, log addresses along with all TLS
29318 - When building with --enable-gcc-warnings, check for whether Apple's
29319 warning "-Wshorten-64-to-32" is available.
29320 - Add a --passphrase-fd argument to the tor-gencert command for
29323 o Minor bugfixes (memory leaks and code problems):
29324 - We were leaking a file descriptor if Tor started with a zero-length
29325 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
29326 - Detect size overflow in zlib code. Reported by Justin Ferguson and
29328 - We were comparing the raw BridgePassword entry with a base64'ed
29329 version of it, when handling a "/tor/networkstatus-bridges"
29330 directory request. Now compare correctly. Noticed by Veracode.
29331 - Recover from bad tracked-since value in MTBF-history file.
29332 Should fix bug 537.
29333 - Alter the code that tries to recover from unhandled write
29334 errors, to not try to flush onto a socket that's given us
29335 unhandled errors. Bugfix on 0.1.2.x.
29336 - Make Unix controlsockets work correctly on OpenBSD. Patch from
29337 tup. Bugfix on 0.2.0.3-alpha.
29339 o Minor bugfixes (other):
29340 - If we have an extra-info document for our server, always make
29341 it available on the control port, even if we haven't gotten
29342 a copy of it from an authority yet. Patch from mwenge.
29343 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
29344 - Directory mirrors no longer include a guess at the client's IP
29345 address if the connection appears to be coming from the same /24
29346 network; it was producing too many wrong guesses.
29347 - Make the new hidden service code respect the SafeLogging setting.
29348 Bugfix on 0.2.0.x. Patch from Karsten.
29349 - When starting as an authority, do not overwrite all certificates
29350 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
29351 - If we're trying to flush the last bytes on a connection (for
29352 example, when answering a directory request), reset the
29353 time-to-give-up timeout every time we manage to write something
29354 on the socket. Bugfix on 0.1.2.x.
29355 - Change the behavior of "getinfo status/good-server-descriptor"
29356 so it doesn't return failure when any authority disappears.
29357 - Even though the man page said that "TrackHostExits ." should
29358 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
29359 - Report TLS "zero return" case as a "clean close" and "IO error"
29360 as a "close". Stop calling closes "unexpected closes": existing
29361 Tors don't use SSL_close(), so having a connection close without
29362 the TLS shutdown handshake is hardly unexpected.
29363 - Send NAMESERVER_STATUS messages for a single failed nameserver
29366 o Code simplifications and refactoring:
29367 - Remove the tor_strpartition function: its logic was confused,
29368 and it was only used for one thing that could be implemented far
29372 Changes in version 0.2.0.19-alpha - 2008-02-09
29373 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
29374 handshake, makes path selection for relays more secure and IP address
29375 guessing more robust, and generally fixes a lot of bugs in preparation
29376 for calling the 0.2.0 branch stable.
29379 - Do not include recognizeable strings in the commonname part of
29380 Tor's x509 certificates.
29383 - If we're a relay, avoid picking ourselves as an introduction point,
29384 a rendezvous point, or as the final hop for internal circuits. Bug
29385 reported by taranis and lodger. Bugfix on 0.1.2.x.
29386 - Patch from "Andrew S. Lists" to catch when we contact a directory
29387 mirror at IP address X and he says we look like we're coming from
29388 IP address X. Bugfix on 0.1.2.x.
29390 o Minor features (security):
29391 - Be more paranoid about overwriting sensitive memory on free(),
29392 as a defensive programming tactic to ensure forward secrecy.
29394 o Minor features (directory authority):
29395 - Actually validate the options passed to AuthDirReject,
29396 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
29397 - Reject router descriptors with out-of-range bandwidthcapacity or
29398 bandwidthburst values.
29400 o Minor features (controller):
29401 - Reject controller commands over 1MB in length. This keeps rogue
29402 processes from running us out of memory.
29404 o Minor features (misc):
29405 - Give more descriptive well-formedness errors for out-of-range
29406 hidden service descriptor/protocol versions.
29407 - Make memory debugging information describe more about history
29408 of cell allocation, so we can help reduce our memory use.
29410 o Deprecated features (controller):
29411 - The status/version/num-versioning and status/version/num-concurring
29412 GETINFO options are no longer useful in the v3 directory protocol:
29413 treat them as deprecated, and warn when they're used.
29416 - When our consensus networkstatus has been expired for a while, stop
29417 being willing to build circuits using it. Fixes bug 401. Bugfix
29419 - Directory caches now fetch certificates from all authorities
29420 listed in a networkstatus consensus, even when they do not
29421 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
29422 - When connecting to a bridge without specifying its key, insert
29423 the connection into the identity-to-connection map as soon as
29424 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
29425 - Detect versions of OS X where malloc_good_size() is present in the
29426 library but never actually declared. Resolves bug 587. Bugfix
29428 - Stop incorrectly truncating zlib responses to directory authority
29429 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
29430 - Stop recommending that every server operator send mail to tor-ops.
29431 Resolves bug 597. Bugfix on 0.1.2.x.
29432 - Don't trigger an assert if we start a directory authority with a
29433 private IP address (like 127.0.0.1).
29434 - Avoid possible failures when generating a directory with routers
29435 with over-long versions strings, or too many flags set. Bugfix
29437 - If an attempt to launch a DNS resolve request over the control
29438 port fails because we have overrun the limit on the number of
29439 connections, tell the controller that the request has failed.
29440 - Avoid using too little bandwidth when our clock skips a few
29441 seconds. Bugfix on 0.1.2.x.
29442 - Fix shell error when warning about missing packages in configure
29443 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
29444 - Do not become confused when receiving a spurious VERSIONS-like
29445 cell from a confused v1 client. Bugfix on 0.2.0.x.
29446 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
29447 introduction points for a hidden service have failed. Patch from
29448 Karsten Loesing. Bugfix on 0.2.0.x.
29450 o Code simplifications and refactoring:
29451 - Remove some needless generality from cpuworker code, for improved
29453 - Stop overloading the circuit_t.onionskin field for both "onionskin
29454 from a CREATE cell that we are waiting for a cpuworker to be
29455 assigned" and "onionskin from an EXTEND cell that we are going to
29456 send to an OR as soon as we are connected". Might help with bug 600.
29457 - Add an in-place version of aes_crypt() so that we can avoid doing a
29458 needless memcpy() call on each cell payload.
29461 Changes in version 0.2.0.18-alpha - 2008-01-25
29462 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
29463 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
29464 that can warn or reject connections to ports generally associated with
29465 vulnerable-plaintext protocols.
29467 o New directory authorities:
29468 - Set up dannenberg (run by CCC) as the sixth v3 directory
29472 - Fix a major memory leak when attempting to use the v2 TLS
29473 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
29474 - We accidentally enabled the under-development v2 TLS handshake
29475 code, which was causing log entries like "TLS error while
29476 renegotiating handshake". Disable it again. Resolves bug 590.
29477 - We were computing the wrong Content-Length: header for directory
29478 responses that need to be compressed on the fly, causing clients
29479 asking for those items to always fail. Bugfix on 0.2.0.x; partially
29483 - Avoid going directly to the directory authorities even if you're a
29484 relay, if you haven't found yourself reachable yet or if you've
29485 decided not to advertise your dirport yet. Addresses bug 556.
29486 - If we've gone 12 hours since our last bandwidth check, and we
29487 estimate we have less than 50KB bandwidth capacity but we could
29488 handle more, do another bandwidth test.
29489 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
29490 Tor can warn and/or refuse connections to ports commonly used with
29491 vulnerable-plaintext protocols. Currently we warn on ports 23,
29492 109, 110, and 143, but we don't reject any.
29495 - When we setconf ClientOnly to 1, close any current OR and Dir
29496 listeners. Reported by mwenge.
29497 - When we get a consensus that's been signed by more people than
29498 we expect, don't log about it; it's not a big deal. Reported
29502 - Don't answer "/tor/networkstatus-bridges" directory requests if
29503 the request isn't encrypted.
29504 - Make "ClientOnly 1" config option disable directory ports too.
29505 - Patches from Karsten Loesing to make v2 hidden services more
29506 robust: work even when there aren't enough HSDir relays available;
29507 retry when a v2 rend desc fetch fails; but don't retry if we
29508 already have a usable v0 rend desc.
29511 Changes in version 0.2.0.17-alpha - 2008-01-17
29512 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
29515 - Make the tor-gencert man page get included correctly in the tarball.
29518 Changes in version 0.2.0.16-alpha - 2008-01-17
29519 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
29520 Loesing, and generally cleans up a lot of features and minor bugs.
29522 o New directory authorities:
29523 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
29526 o Major performance improvements:
29527 - Switch our old ring buffer implementation for one more like that
29528 used by free Unix kernels. The wasted space in a buffer with 1mb
29529 of data will now be more like 8k than 1mb. The new implementation
29530 also avoids realloc();realloc(); patterns that can contribute to
29531 memory fragmentation.
29534 - Configuration files now accept C-style strings as values. This
29535 helps encode characters not allowed in the current configuration
29536 file format, such as newline or #. Addresses bug 557.
29537 - Although we fixed bug 539 (where servers would send HTTP status 503
29538 responses _and_ send a body too), there are still servers out
29539 there that haven't upgraded. Therefore, make clients parse such
29540 bodies when they receive them.
29541 - When we're not serving v2 directory information, there is no reason
29542 to actually keep any around. Remove the obsolete files and directory
29543 on startup if they are very old and we aren't going to serve them.
29545 o Minor performance improvements:
29546 - Reference-count and share copies of address policy entries; only 5%
29547 of them were actually distinct.
29548 - Never walk through the list of logs if we know that no log is
29549 interested in a given message.
29552 - When an authority has not signed a consensus, do not try to
29553 download a nonexistent "certificate with key 00000000". Bugfix
29554 on 0.2.0.x. Fixes bug 569.
29555 - Fix a rare assert error when we're closing one of our threads:
29556 use a mutex to protect the list of logs, so we never write to the
29557 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
29558 bug 575, which is kind of the revenge of bug 222.
29559 - Patch from Karsten Loesing to complain less at both the client
29560 and the relay when a relay used to have the HSDir flag but doesn't
29561 anymore, and we try to upload a hidden service descriptor.
29562 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
29564 - Do not try to download missing certificates until we have tried
29565 to check our fallback consensus. Fixes bug 583.
29566 - Make bridges round reported GeoIP stats info up to the nearest
29567 estimate, not down. Now we can distinguish between "0 people from
29568 this country" and "1 person from this country".
29569 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
29570 - Avoid possible segfault if key generation fails in
29571 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
29572 - Avoid segfault in the case where a badly behaved v2 versioning
29573 directory sends a signed networkstatus with missing client-versions.
29575 - Avoid segfaults on certain complex invocations of
29576 router_get_by_hexdigest(). Bugfix on 0.1.2.
29577 - Correct bad index on array access in parse_http_time(). Bugfix
29579 - Fix possible bug in vote generation when server versions are present
29580 but client versions are not.
29581 - Fix rare bug on REDIRECTSTREAM control command when called with no
29582 port set: it could erroneously report an error when none had
29584 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
29585 compressing large objects and find ourselves with more than 4k
29586 left over. Bugfix on 0.2.0.
29587 - Fix a small memory leak when setting up a hidden service.
29588 - Fix a few memory leaks that could in theory happen under bizarre
29590 - Fix an assert if we post a general-purpose descriptor via the
29591 control port but that descriptor isn't mentioned in our current
29592 network consensus. Bug reported by Jon McLachlan; bugfix on
29595 o Minor features (controller):
29596 - Get NS events working again. Patch from tup.
29597 - The GETCONF command now escapes and quotes configuration values
29598 that don't otherwise fit into the torrc file.
29599 - The SETCONF command now handles quoted values correctly.
29601 o Minor features (directory authorities):
29602 - New configuration options to override default maximum number of
29603 servers allowed on a single IP address. This is important for
29604 running a test network on a single host.
29605 - Actually implement the -s option to tor-gencert.
29606 - Add a manual page for tor-gencert.
29608 o Minor features (bridges):
29609 - Bridge authorities no longer serve bridge descriptors over
29610 unencrypted connections.
29612 o Minor features (other):
29613 - Add hidden services and DNSPorts to the list of things that make
29614 Tor accept that it has running ports. Change starting Tor with no
29615 ports from a fatal error to a warning; we might change it back if
29616 this turns out to confuse anybody. Fixes bug 579.
29619 Changes in version 0.1.2.19 - 2008-01-17
29620 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
29621 exit policy a little bit more conservative so it's safer to run an
29622 exit relay on a home system, and fixes a variety of smaller issues.
29625 - Exit policies now reject connections that are addressed to a
29626 relay's public (external) IP address too, unless
29627 ExitPolicyRejectPrivate is turned off. We do this because too
29628 many relays are running nearby to services that trust them based
29629 on network address.
29632 - When the clock jumps forward a lot, do not allow the bandwidth
29633 buckets to become negative. Fixes bug 544.
29634 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
29635 on every successful resolve. Reported by Mike Perry.
29636 - Purge old entries from the "rephist" database and the hidden
29637 service descriptor database even when DirPort is zero.
29638 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
29639 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
29640 crashing or mis-answering these requests.
29641 - When we decide to send a 503 response to a request for servers, do
29642 not then also send the server descriptors: this defeats the whole
29643 purpose. Fixes bug 539.
29646 - Changing the ExitPolicyRejectPrivate setting should cause us to
29647 rebuild our server descriptor.
29648 - Fix handling of hex nicknames when answering controller requests for
29649 networkstatus by name, or when deciding whether to warn about
29650 unknown routers in a config option. (Patch from mwenge.)
29651 - Fix a couple of hard-to-trigger autoconf problems that could result
29652 in really weird results on platforms whose sys/types.h files define
29653 nonstandard integer types.
29654 - Don't try to create the datadir when running --verify-config or
29655 --hash-password. Resolves bug 540.
29656 - If we were having problems getting a particular descriptor from the
29657 directory caches, and then we learned about a new descriptor for
29658 that router, we weren't resetting our failure count. Reported
29660 - Although we fixed bug 539 (where servers would send HTTP status 503
29661 responses _and_ send a body too), there are still servers out there
29662 that haven't upgraded. Therefore, make clients parse such bodies
29663 when they receive them.
29664 - Run correctly on systems where rlim_t is larger than unsigned long.
29665 This includes some 64-bit systems.
29666 - Run correctly on platforms (like some versions of OS X 10.5) where
29667 the real limit for number of open files is OPEN_FILES, not rlim_max
29668 from getrlimit(RLIMIT_NOFILES).
29669 - Avoid a spurious free on base64 failure.
29670 - Avoid segfaults on certain complex invocations of
29671 router_get_by_hexdigest().
29672 - Fix rare bug on REDIRECTSTREAM control command when called with no
29673 port set: it could erroneously report an error when none had
29677 Changes in version 0.2.0.15-alpha - 2007-12-25
29678 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
29679 features added in 0.2.0.13-alpha.
29682 - Fix several remotely triggerable asserts based on DirPort requests
29683 for a v2 or v3 networkstatus object before we were prepared. This
29684 was particularly bad for 0.2.0.13 and later bridge relays, who
29685 would never have a v2 networkstatus and would thus always crash
29686 when used. Bugfixes on 0.2.0.x.
29687 - Estimate the v3 networkstatus size more accurately, rather than
29688 estimating it at zero bytes and giving it artificially high priority
29689 compared to other directory requests. Bugfix on 0.2.0.x.
29692 - Fix configure.in logic for cross-compilation.
29693 - When we load a bridge descriptor from the cache, and it was
29694 previously unreachable, mark it as retriable so we won't just
29695 ignore it. Also, try fetching a new copy immediately. Bugfixes
29697 - The bridge GeoIP stats were counting other relays, for example
29698 self-reachability and authority-reachability tests.
29701 - Support compilation to target iPhone; patch from cjacker huang.
29702 To build for iPhone, pass the --enable-iphone option to configure.
29705 Changes in version 0.2.0.14-alpha - 2007-12-23
29707 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
29708 without a datadirectory from a previous Tor install. Reported
29710 - Fix a crash when we fetch a descriptor that turns out to be
29711 unexpected (it used to be in our networkstatus when we started
29712 fetching it, but it isn't in our current networkstatus), and we
29713 aren't using bridges. Bugfix on 0.2.0.x.
29714 - Fix a crash when accessing hidden services: it would work the first
29715 time you use a given introduction point for your service, but
29716 on subsequent requests we'd be using garbage memory. Fixed by
29717 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
29718 - Fix a crash when we load a bridge descriptor from disk but we don't
29719 currently have a Bridge line for it in our torrc. Bugfix on
29723 - If bridge authorities set BridgePassword, they will serve a
29724 snapshot of known bridge routerstatuses from their DirPort to
29725 anybody who knows that password. Unset by default.
29728 - Make the unit tests build again.
29729 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
29730 - Make PublishServerDescriptor default to 1, so the default doesn't
29731 have to change as we invent new directory protocol versions.
29732 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
29733 be included unless sys/time.h is already included. Fixes
29734 bug 553. Bugfix on 0.2.0.x.
29735 - If we receive a general-purpose descriptor and then receive an
29736 identical bridge-purpose descriptor soon after, don't discard
29737 the next one as a duplicate.
29740 - If BridgeRelay is set to 1, then the default for
29741 PublishServerDescriptor is now "bridge" rather than "v2,v3".
29742 - If the user sets RelayBandwidthRate but doesn't set
29743 RelayBandwidthBurst, then make them equal rather than erroring out.
29746 Changes in version 0.2.0.13-alpha - 2007-12-21
29747 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
29748 Goodell, fixes many more bugs, and adds a lot of infrastructure for
29751 o New directory authorities:
29752 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
29756 - Only update guard status (usable / not usable) once we have
29757 enough directory information. This was causing us to always pick
29758 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
29759 causing us to discard all our guards on startup if we hadn't been
29760 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
29761 - Purge old entries from the "rephist" database and the hidden
29762 service descriptor databases even when DirPort is zero. Bugfix
29764 - We were ignoring our RelayBandwidthRate for the first 30 seconds
29765 after opening a circuit -- even a relayed circuit. Bugfix on
29767 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
29768 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
29769 crashing or mis-answering these types of requests.
29770 - Relays were publishing their server descriptor to v1 and v2
29771 directory authorities, but they didn't try publishing to v3-only
29772 authorities. Fix this; and also stop publishing to v1 authorities.
29774 - When we were reading router descriptors from cache, we were ignoring
29775 the annotations -- so for example we were reading in bridge-purpose
29776 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
29777 - When we decided to send a 503 response to a request for servers, we
29778 were then also sending the server descriptors: this defeats the
29779 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
29782 - Bridge relays now behave like clients with respect to time
29783 intervals for downloading new consensus documents -- otherwise they
29784 stand out. Bridge users now wait until the end of the interval,
29785 so their bridge relay will be sure to have a new consensus document.
29786 - Three new config options (AlternateDirAuthority,
29787 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
29788 user selectively replace the default directory authorities by type,
29789 rather than the all-or-nothing replacement that DirServer offers.
29790 - Tor can now be configured to read a GeoIP file from disk in one
29791 of two formats. This can be used by controllers to map IP addresses
29792 to countries. Eventually, it may support exit-by-country.
29793 - When possible, bridge relays remember which countries users
29794 are coming from, and report aggregate information in their
29795 extra-info documents, so that the bridge authorities can learn
29796 where Tor is blocked.
29797 - Bridge directory authorities now do reachability testing on the
29798 bridges they know. They provide router status summaries to the
29799 controller via "getinfo ns/purpose/bridge", and also dump summaries
29800 to a file periodically.
29801 - Stop fetching directory info so aggressively if your DirPort is
29802 on but your ORPort is off; stop fetching v2 dir info entirely.
29803 You can override these choices with the new FetchDirInfoEarly
29807 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
29808 consensus documents when there are too many relays at a single
29809 IP address. Now clear it in v2 network status documents too, and
29810 also clear it in routerinfo_t when the relay is no longer listed
29811 in the relevant networkstatus document.
29812 - Don't crash if we get an unexpected value for the
29813 PublishServerDescriptor config option. Reported by Matt Edman;
29814 bugfix on 0.2.0.9-alpha.
29815 - Our new v2 hidden service descriptor format allows descriptors
29816 that have no introduction points. But Tor crashed when we tried
29817 to build a descriptor with no intro points (and it would have
29818 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
29819 by Karsten Loesing.
29820 - Fix building with dmalloc 5.5.2 with glibc.
29821 - Reject uploaded descriptors and extrainfo documents if they're
29822 huge. Otherwise we'll cache them all over the network and it'll
29823 clog everything up. Reported by Aljosha Judmayer.
29824 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
29825 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
29826 - When the DANGEROUS_VERSION controller status event told us we're
29827 running an obsolete version, it used the string "OLD" to describe
29828 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
29829 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
29830 - If we can't expand our list of entry guards (e.g. because we're
29831 using bridges or we have StrictEntryNodes set), don't mark relays
29832 down when they fail a directory request. Otherwise we're too quick
29833 to mark all our entry points down. Bugfix on 0.1.2.x.
29834 - Fix handling of hex nicknames when answering controller requests for
29835 networkstatus by name, or when deciding whether to warn about unknown
29836 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
29837 - Fix a couple of hard-to-trigger autoconf problems that could result
29838 in really weird results on platforms whose sys/types.h files define
29839 nonstandard integer types. Bugfix on 0.1.2.x.
29840 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
29841 - Don't crash on name lookup when we have no current consensus. Fixes
29842 bug 538; bugfix on 0.2.0.x.
29843 - Only Tors that want to mirror the v2 directory info should
29844 create the "cached-status" directory in their datadir. (All Tors
29845 used to create it.) Bugfix on 0.2.0.9-alpha.
29846 - Directory authorities should only automatically download Extra Info
29847 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
29850 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
29851 consumers. (We already do this on HUP.)
29852 - Authorities and caches fetch the v2 networkstatus documents
29853 less often, now that v3 is encouraged.
29854 - Add a new config option BridgeRelay that specifies you want to
29855 be a bridge relay. Right now the only difference is that it makes
29856 you answer begin_dir requests, and it makes you cache dir info,
29857 even if your DirPort isn't on.
29858 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
29859 ask about source, timestamp of arrival, purpose, etc. We need
29860 something like this to help Vidalia not do GeoIP lookups on bridge
29862 - Allow multiple HashedControlPassword config lines, to support
29863 multiple controller passwords.
29864 - Authorities now decide whether they're authoritative for a given
29865 router based on the router's purpose.
29866 - New config options AuthDirBadDir and AuthDirListBadDirs for
29867 authorities to mark certain relays as "bad directories" in the
29868 networkstatus documents. Also supports the "!baddir" directive in
29869 the approved-routers file.
29872 Changes in version 0.2.0.12-alpha - 2007-11-16
29873 This twelfth development snapshot fixes some more build problems as
29874 well as a few minor bugs.
29877 - Make it build on OpenBSD again. Patch from tup.
29878 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
29879 package-building for Red Hat, OS X, etc.
29881 o Minor bugfixes (on 0.1.2.x):
29882 - Changing the ExitPolicyRejectPrivate setting should cause us to
29883 rebuild our server descriptor.
29885 o Minor bugfixes (on 0.2.0.x):
29886 - When we're lacking a consensus, don't try to perform rendezvous
29887 operations. Reported by Karsten Loesing.
29888 - Fix a small memory leak whenever we decide against using a
29889 newly picked entry guard. Reported by Mike Perry.
29890 - When authorities detected more than two relays running on the same
29891 IP address, they were clearing all the status flags but forgetting
29892 to clear the "hsdir" flag. So clients were being told that a
29893 given relay was the right choice for a v2 hsdir lookup, yet they
29894 never had its descriptor because it was marked as 'not running'
29896 - If we're trying to fetch a bridge descriptor and there's no way
29897 the bridge authority could help us (for example, we don't know
29898 a digest, or there is no bridge authority), don't be so eager to
29899 fall back to asking the bridge authority.
29900 - If we're using bridges or have strictentrynodes set, and our
29901 chosen exit is in the same family as all our bridges/entry guards,
29902 then be flexible about families.
29905 - When we negotiate a v2 link-layer connection (not yet implemented),
29906 accept RELAY_EARLY cells and turn them into RELAY cells if we've
29907 negotiated a v1 connection for their next step. Initial code for
29911 Changes in version 0.2.0.11-alpha - 2007-11-12
29912 This eleventh development snapshot fixes some build problems with
29913 the previous snapshot. It also includes a more secure-by-default exit
29914 policy for relays, fixes an enormous memory leak for exit relays, and
29915 fixes another bug where servers were falling out of the directory list.
29918 - Exit policies now reject connections that are addressed to a
29919 relay's public (external) IP address too, unless
29920 ExitPolicyRejectPrivate is turned off. We do this because too
29921 many relays are running nearby to services that trust them based
29922 on network address. Bugfix on 0.1.2.x.
29925 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
29926 on every successful resolve. Reported by Mike Perry; bugfix
29928 - On authorities, never downgrade to old router descriptors simply
29929 because they're listed in the consensus. This created a catch-22
29930 where we wouldn't list a new descriptor because there was an
29931 old one in the consensus, and we couldn't get the new one in the
29932 consensus because we wouldn't list it. Possible fix for bug 548.
29933 Also, this might cause bug 543 to appear on authorities; if so,
29934 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
29936 o Packaging fixes on 0.2.0.10-alpha:
29937 - We were including instructions about what to do with the
29938 src/config/fallback-consensus file, but we weren't actually
29939 including it in the tarball. Disable all of that for now.
29942 - Allow people to say PreferTunnelledDirConns rather than
29943 PreferTunneledDirConns, for those alternate-spellers out there.
29946 - Don't reevaluate all the information from our consensus document
29947 just because we've downloaded a v2 networkstatus that we intend
29948 to cache. Fixes bug 545; bugfix on 0.2.0.x.
29951 Changes in version 0.2.0.10-alpha - 2007-11-10
29952 This tenth development snapshot adds a third v3 directory authority
29953 run by Mike Perry, adds most of Karsten Loesing's new hidden service
29954 descriptor format, fixes a bad crash bug and new bridge bugs introduced
29955 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
29956 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
29957 addresses many more minor issues.
29959 o New directory authorities:
29960 - Set up ides (run by Mike Perry) as the third v3 directory authority.
29963 - Allow tunnelled directory connections to ask for an encrypted
29964 "begin_dir" connection or an anonymized "uses a full Tor circuit"
29965 connection independently. Now we can make anonymized begin_dir
29966 connections for (e.g.) more secure hidden service posting and
29968 - More progress on proposal 114: code from Karsten Loesing to
29969 implement new hidden service descriptor format.
29970 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
29971 accommodate the growing number of servers that use the default
29972 and are reaching it.
29973 - Directory authorities use a new formula for selecting which nodes
29974 to advertise as Guards: they must be in the top 7/8 in terms of
29975 how long we have known about them, and above the median of those
29976 nodes in terms of weighted fractional uptime.
29977 - Make "not enough dir info yet" warnings describe *why* Tor feels
29978 it doesn't have enough directory info yet.
29981 - Stop servers from crashing if they set a Family option (or
29982 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
29984 - Make bridge users work again -- the move to v3 directories in
29985 0.2.0.9-alpha had introduced a number of bugs that made bridges
29986 no longer work for clients.
29987 - When the clock jumps forward a lot, do not allow the bandwidth
29988 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
29990 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
29991 - When the consensus lists a router descriptor that we previously were
29992 mirroring, but that we considered non-canonical, reload the
29993 descriptor as canonical. This fixes bug 543 where Tor servers
29994 would start complaining after a few days that they don't have
29995 enough directory information to build a circuit.
29996 - Consider replacing the current consensus when certificates arrive
29997 that make the pending consensus valid. Previously, we were only
29998 considering replacement when the new certs _didn't_ help.
29999 - Fix an assert error on startup if we didn't already have the
30000 consensus and certs cached in our datadirectory: we were caching
30001 the consensus in consensus_waiting_for_certs but then free'ing it
30003 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
30004 Request) if we need more v3 certs but we've already got pending
30005 requests for all of them.
30006 - Correctly back off from failing certificate downloads. Fixes
30008 - Authorities don't vote on the Running flag if they have been running
30009 for less than 30 minutes themselves. Fixes bug 547, where a newly
30010 started authority would vote that everyone was down.
30012 o New requirements:
30013 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
30014 it, it had no AES, and it hasn't seen any security patches since
30018 - Clients now hold circuitless TLS connections open for 1.5 times
30019 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
30020 rebuild a new circuit over them within that timeframe. Previously,
30021 they held them open only for KeepalivePeriod (5 minutes).
30022 - Use "If-Modified-Since" to avoid retrieving consensus
30023 networkstatuses that we already have.
30024 - When we have no consensus, check FallbackNetworkstatusFile (defaults
30025 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
30026 we start knowing some directory caches.
30027 - When we receive a consensus from the future, warn about skew.
30028 - Improve skew reporting: try to give the user a better log message
30029 about how skewed they are, and how much this matters.
30030 - When we have a certificate for an authority, believe that
30031 certificate's claims about the authority's IP address.
30032 - New --quiet command-line option to suppress the default console log.
30033 Good in combination with --hash-password.
30034 - Authorities send back an X-Descriptor-Not-New header in response to
30035 an accepted-but-discarded descriptor upload. Partially implements
30037 - Make the log message for "tls error. breaking." more useful.
30038 - Better log messages about certificate downloads, to attempt to
30039 track down the second incarnation of bug 546.
30041 o Minor features (bridges):
30042 - If bridge users set UpdateBridgesFromAuthority, but the digest
30043 they ask for is a 404 from the bridge authority, they now fall
30044 back to trying the bridge directly.
30045 - Bridges now use begin_dir to publish their server descriptor to
30046 the bridge authority, even when they haven't set TunnelDirConns.
30048 o Minor features (controller):
30049 - When reporting clock skew, and we know that the clock is _at least
30050 as skewed_ as some value, but we don't know the actual value,
30051 report the value as a "minimum skew."
30054 - Update linux-tor-prio.sh script to allow QoS based on the uid of
30055 the Tor process. Patch from Marco Bonetti with tweaks from Mike
30059 - Refuse to start if both ORPort and UseBridges are set. Bugfix
30060 on 0.2.0.x, suggested by Matt Edman.
30061 - Don't stop fetching descriptors when FetchUselessDescriptors is
30062 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
30063 reported by tup and ioerror.
30064 - Better log message on vote from unknown authority.
30065 - Don't log "Launching 0 request for 0 router" message.
30067 o Minor bugfixes (memory leaks):
30068 - Stop leaking memory every time we parse a v3 certificate. Bugfix
30070 - Stop leaking memory every time we load a v3 certificate. Bugfix
30071 on 0.2.0.1-alpha. Fixes bug 536.
30072 - Stop leaking a cached networkstatus on exit. Bugfix on
30074 - Stop leaking voter information every time we free a consensus.
30075 Bugfix on 0.2.0.3-alpha.
30076 - Stop leaking signed data every time we check a voter signature.
30077 Bugfix on 0.2.0.3-alpha.
30078 - Stop leaking a signature every time we fail to parse a consensus or
30079 a vote. Bugfix on 0.2.0.3-alpha.
30080 - Stop leaking v2_download_status_map on shutdown. Bugfix on
30082 - Stop leaking conn->nickname every time we make a connection to a
30083 Tor relay without knowing its expected identity digest (e.g. when
30084 using bridges). Bugfix on 0.2.0.3-alpha.
30086 - Minor bugfixes (portability):
30087 - Run correctly on platforms where rlim_t is larger than unsigned
30088 long, and/or where the real limit for number of open files is
30089 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
30090 particular, these may be needed for OS X 10.5.
30093 Changes in version 0.1.2.18 - 2007-10-28
30094 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
30095 hidden service introduction that were causing huge delays, and a big
30096 bug that was causing some servers to disappear from the network status
30097 lists for a few hours each day.
30099 o Major bugfixes (crashes):
30100 - If a connection is shut down abruptly because of something that
30101 happened inside connection_flushed_some(), do not call
30102 connection_finished_flushing(). Should fix bug 451:
30103 "connection_stop_writing: Assertion conn->write_event failed"
30104 Bugfix on 0.1.2.7-alpha.
30105 - Fix possible segfaults in functions called from
30106 rend_process_relay_cell().
30108 o Major bugfixes (hidden services):
30109 - Hidden services were choosing introduction points uniquely by
30110 hexdigest, but when constructing the hidden service descriptor
30111 they merely wrote the (potentially ambiguous) nickname.
30112 - Clients now use the v2 intro format for hidden service
30113 connections: they specify their chosen rendezvous point by identity
30114 digest rather than by (potentially ambiguous) nickname. These
30115 changes could speed up hidden service connections dramatically.
30117 o Major bugfixes (other):
30118 - Stop publishing a new server descriptor just because we get a
30119 HUP signal. This led (in a roundabout way) to some servers getting
30120 dropped from the networkstatus lists for a few hours each day.
30121 - When looking for a circuit to cannibalize, consider family as well
30122 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
30123 circuit cannibalization).
30124 - When a router wasn't listed in a new networkstatus, we were leaving
30125 the flags for that router alone -- meaning it remained Named,
30126 Running, etc -- even though absence from the networkstatus means
30127 that it shouldn't be considered to exist at all anymore. Now we
30128 clear all the flags for routers that fall out of the networkstatus
30129 consensus. Fixes bug 529.
30132 - Don't try to access (or alter) the state file when running
30133 --list-fingerprint or --verify-config or --hash-password. Resolves
30135 - When generating information telling us how to extend to a given
30136 router, do not try to include the nickname if it is
30137 absent. Resolves bug 467.
30138 - Fix a user-triggerable segfault in expand_filename(). (There isn't
30139 a way to trigger this remotely.)
30140 - When sending a status event to the controller telling it that an
30141 OR address is reachable, set the port correctly. (Previously we
30142 were reporting the dir port.)
30143 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
30144 command. Bugfix on 0.1.2.17.
30145 - When loading bandwidth history, do not believe any information in
30146 the future. Fixes bug 434.
30147 - When loading entry guard information, do not believe any information
30149 - When we have our clock set far in the future and generate an
30150 onion key, then re-set our clock to be correct, we should not stop
30151 the onion key from getting rotated.
30152 - On some platforms, accept() can return a broken address. Detect
30153 this more quietly, and deal accordingly. Fixes bug 483.
30154 - It's not actually an error to find a non-pending entry in the DNS
30155 cache when canceling a pending resolve. Don't log unless stuff
30156 is fishy. Resolves bug 463.
30157 - Don't reset trusted dir server list when we set a configuration
30158 option. Patch from Robert Hogan.
30159 - Don't try to create the datadir when running --verify-config or
30160 --hash-password. Resolves bug 540.
30163 Changes in version 0.2.0.9-alpha - 2007-10-24
30164 This ninth development snapshot switches clients to the new v3 directory
30165 system; allows servers to be listed in the network status even when they
30166 have the same nickname as a registered server; and fixes many other
30167 bugs including a big one that was causing some servers to disappear
30168 from the network status lists for a few hours each day.
30170 o Major features (directory system):
30171 - Clients now download v3 consensus networkstatus documents instead
30172 of v2 networkstatus documents. Clients and caches now base their
30173 opinions about routers on these consensus documents. Clients only
30174 download router descriptors listed in the consensus.
30175 - Authorities now list servers who have the same nickname as
30176 a different named server, but list them with a new flag,
30177 "Unnamed". Now we can list servers that happen to pick the same
30178 nickname as a server that registered two years ago and then
30179 disappeared. Partially implements proposal 122.
30180 - If the consensus lists a router as "Unnamed", the name is assigned
30181 to a different router: do not identify the router by that name.
30182 Partially implements proposal 122.
30183 - Authorities can now come to a consensus on which method to use to
30184 compute the consensus. This gives us forward compatibility.
30187 - Stop publishing a new server descriptor just because we HUP or
30188 when we find our DirPort to be reachable but won't actually publish
30189 it. New descriptors without any real changes are dropped by the
30190 authorities, and can screw up our "publish every 18 hours" schedule.
30192 - When a router wasn't listed in a new networkstatus, we were leaving
30193 the flags for that router alone -- meaning it remained Named,
30194 Running, etc -- even though absence from the networkstatus means
30195 that it shouldn't be considered to exist at all anymore. Now we
30196 clear all the flags for routers that fall out of the networkstatus
30197 consensus. Fixes bug 529; bugfix on 0.1.2.x.
30198 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
30199 extrainfo documents and then discard them immediately for not
30200 matching the latest router. Bugfix on 0.2.0.1-alpha.
30202 o Minor features (v3 directory protocol):
30203 - Allow tor-gencert to generate a new certificate without replacing
30205 - Allow certificates to include an address.
30206 - When we change our directory-cache settings, reschedule all voting
30207 and download operations.
30208 - Reattempt certificate downloads immediately on failure, as long as
30209 we haven't failed a threshold number of times yet.
30210 - Delay retrying consensus downloads while we're downloading
30211 certificates to verify the one we just got. Also, count getting a
30212 consensus that we already have (or one that isn't valid) as a failure,
30213 and count failing to get the certificates after 20 minutes as a
30215 - Build circuits and download descriptors even if our consensus is a
30216 little expired. (This feature will go away once authorities are
30219 o Minor features (router descriptor cache):
30220 - If we find a cached-routers file that's been sitting around for more
30221 than 28 days unmodified, then most likely it's a leftover from
30222 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
30224 - When we (as a cache) download a descriptor because it was listed
30225 in a consensus, remember when the consensus was supposed to expire,
30226 and don't expire the descriptor until then.
30228 o Minor features (performance):
30229 - Call routerlist_remove_old_routers() much less often. This should
30230 speed startup, especially on directory caches.
30231 - Don't try to launch new descriptor downloads quite so often when we
30232 already have enough directory information to build circuits.
30233 - Base64 decoding was actually showing up on our profile when parsing
30234 the initial descriptor file; switch to an in-process all-at-once
30235 implementation that's about 3.5x times faster than calling out to
30238 o Minor features (compilation):
30239 - Detect non-ASCII platforms (if any still exist) and refuse to
30240 build there: some of our code assumes that 'A' is 65 and so on.
30242 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
30243 - Make the "next period" votes into "current period" votes immediately
30244 after publishing the consensus; avoid a heisenbug that made them
30245 stick around indefinitely.
30246 - When we discard a vote as a duplicate, do not report this as
30248 - Treat missing v3 keys or certificates as an error when running as a
30249 v3 directory authority.
30250 - When we're configured to be a v3 authority, but we're only listed
30251 as a non-v3 authority in our DirServer line for ourself, correct
30253 - If an authority doesn't have a qualified hostname, just put
30254 its address in the vote. This fixes the problem where we referred to
30255 "moria on moria:9031."
30256 - Distinguish between detached signatures for the wrong period, and
30257 detached signatures for a divergent vote.
30258 - Fix a small memory leak when computing a consensus.
30259 - When there's no consensus, we were forming a vote every 30
30260 minutes, but writing the "valid-after" line in our vote based
30261 on our configured V3AuthVotingInterval: so unless the intervals
30262 matched up, we immediately rejected our own vote because it didn't
30263 start at the voting interval that caused us to construct a vote.
30265 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
30266 - Delete unverified-consensus when the real consensus is set.
30267 - Consider retrying a consensus networkstatus fetch immediately
30268 after one fails: don't wait 60 seconds to notice.
30269 - When fetching a consensus as a cache, wait until a newer consensus
30270 should exist before trying to replace the current one.
30271 - Use a more forgiving schedule for retrying failed consensus
30272 downloads than for other types.
30274 o Minor bugfixes (other directory issues):
30275 - Correct the implementation of "download votes by digest." Bugfix on
30277 - Authorities no longer send back "400 you're unreachable please fix
30278 it" errors to Tor servers that aren't online all the time. We're
30279 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
30281 o Minor bugfixes (controller):
30282 - Don't reset trusted dir server list when we set a configuration
30283 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
30284 - Respond to INT and TERM SIGNAL commands before we execute the
30285 signal, in case the signal shuts us down. We had a patch in
30286 0.1.2.1-alpha that tried to do this by queueing the response on
30287 the connection's buffer before shutting down, but that really
30288 isn't the same thing at all. Bug located by Matt Edman.
30290 o Minor bugfixes (misc):
30291 - Correctly check for bad options to the "PublishServerDescriptor"
30292 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
30293 - Stop leaking memory on failing case of base32_decode, and make
30294 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
30295 - Don't try to download extrainfo documents when we're trying to
30296 fetch enough directory info to build a circuit: having enough
30297 info should get priority. Bugfix on 0.2.0.x.
30298 - Don't complain that "your server has not managed to confirm that its
30299 ports are reachable" if we haven't been able to build any circuits
30300 yet. Bug found by spending four hours without a v3 consensus. Bugfix
30302 - Detect the reason for failing to mmap a descriptor file we just
30303 wrote, and give a more useful log message. Fixes bug 533. Bugfix
30306 o Code simplifications and refactoring:
30307 - Remove support for the old bw_accounting file: we've been storing
30308 bandwidth accounting information in the state file since
30309 0.1.2.5-alpha. This may result in bandwidth accounting errors
30310 if you try to upgrade from 0.1.1.x or earlier, or if you try to
30311 downgrade to 0.1.1.x or earlier.
30312 - New convenience code to locate a file within the DataDirectory.
30313 - Move non-authority functionality out of dirvote.c.
30314 - Refactor the arguments for router_pick_{directory_|trusteddir}server
30315 so that they all take the same named flags.
30318 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
30319 Unix users an easy way to script their Tor process (e.g. by
30320 adjusting bandwidth based on the time of the day).
30323 Changes in version 0.2.0.8-alpha - 2007-10-12
30324 This eighth development snapshot fixes a crash bug that's been bothering
30325 us since February 2007, lets bridge authorities store a list of bridge
30326 descriptors they've seen, gets v3 directory voting closer to working,
30327 starts caching v3 directory consensus documents on directory mirrors,
30328 and fixes a variety of smaller issues including some minor memory leaks.
30330 o Major features (router descriptor cache):
30331 - Store routers in a file called cached-descriptors instead of in
30332 cached-routers. Initialize cached-descriptors from cached-routers
30333 if the old format is around. The new format allows us to store
30334 annotations along with descriptors.
30335 - Use annotations to record the time we received each descriptor, its
30336 source, and its purpose.
30337 - Disable the SETROUTERPURPOSE controller command: it is now
30339 - Controllers should now specify cache=no or cache=yes when using
30340 the +POSTDESCRIPTOR command.
30341 - Bridge authorities now write bridge descriptors to disk, meaning
30342 we can export them to other programs and begin distributing them
30345 o Major features (directory authorities):
30346 - When a v3 authority is missing votes or signatures, it now tries
30348 - Directory authorities track weighted fractional uptime as well as
30349 weighted mean-time-between failures. WFU is suitable for deciding
30350 whether a node is "usually up", while MTBF is suitable for deciding
30351 whether a node is "likely to stay up." We need both, because
30352 "usually up" is a good requirement for guards, while "likely to
30353 stay up" is a good requirement for long-lived connections.
30355 o Major features (v3 directory system):
30356 - Caches now download v3 network status documents as needed,
30357 and download the descriptors listed in them.
30358 - All hosts now attempt to download and keep fresh v3 authority
30359 certificates, and re-attempt after failures.
30360 - More internal-consistency checks for vote parsing.
30362 o Major bugfixes (crashes):
30363 - If a connection is shut down abruptly because of something that
30364 happened inside connection_flushed_some(), do not call
30365 connection_finished_flushing(). Should fix bug 451. Bugfix on
30368 o Major bugfixes (performance):
30369 - Fix really bad O(n^2) performance when parsing a long list of
30370 routers: Instead of searching the entire list for an "extra-info "
30371 string which usually wasn't there, once for every routerinfo
30372 we read, just scan lines forward until we find one we like.
30374 - When we add data to a write buffer in response to the data on that
30375 write buffer getting low because of a flush, do not consider the
30376 newly added data as a candidate for immediate flushing, but rather
30377 make it wait until the next round of writing. Otherwise, we flush
30378 and refill recursively, and a single greedy TLS connection can
30379 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
30381 o Minor features (v3 authority system):
30382 - Add more ways for tools to download the votes that lead to the
30384 - Send a 503 when low on bandwidth and a vote, consensus, or
30385 certificate is requested.
30386 - If-modified-since is now implemented properly for all kinds of
30387 certificate requests.
30389 o Minor bugfixes (network statuses):
30390 - Tweak the implementation of proposal 109 slightly: allow at most
30391 two Tor servers on the same IP address, except if it's the location
30392 of a directory authority, in which case allow five. Bugfix on
30395 o Minor bugfixes (controller):
30396 - When sending a status event to the controller telling it that an
30397 OR address is reachable, set the port correctly. (Previously we
30398 were reporting the dir port.) Bugfix on 0.1.2.x.
30400 o Minor bugfixes (v3 directory system):
30401 - Fix logic to look up a cert by its signing key digest. Bugfix on
30403 - Only change the reply to a vote to "OK" if it's not already
30404 set. This gets rid of annoying "400 OK" log messages, which may
30405 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
30406 - When we get a valid consensus, recompute the voting schedule.
30407 - Base the valid-after time of a vote on the consensus voting
30408 schedule, not on our preferred schedule.
30409 - Make the return values and messages from signature uploads and
30410 downloads more sensible.
30411 - Fix a memory leak when serving votes and consensus documents, and
30412 another when serving certificates.
30414 o Minor bugfixes (performance):
30415 - Use a slightly simpler string hashing algorithm (copying Python's
30416 instead of Java's) and optimize our digest hashing algorithm to take
30417 advantage of 64-bit platforms and to remove some possibly-costly
30419 - Fix a minor memory leak whenever we parse guards from our state
30420 file. Bugfix on 0.2.0.7-alpha.
30421 - Fix a minor memory leak whenever we write out a file. Bugfix on
30423 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
30424 command. Bugfix on 0.2.0.5-alpha.
30426 o Minor bugfixes (portability):
30427 - On some platforms, accept() can return a broken address. Detect
30428 this more quietly, and deal accordingly. Fixes bug 483.
30429 - Stop calling tor_strlower() on uninitialized memory in some cases.
30430 Bugfix in 0.2.0.7-alpha.
30432 o Minor bugfixes (usability):
30433 - Treat some 403 responses from directory servers as INFO rather than
30434 WARN-severity events.
30435 - It's not actually an error to find a non-pending entry in the DNS
30436 cache when canceling a pending resolve. Don't log unless stuff is
30437 fishy. Resolves bug 463.
30439 o Minor bugfixes (anonymity):
30440 - Never report that we've used more bandwidth than we're willing to
30441 relay: it leaks how much non-relay traffic we're using. Resolves
30443 - When looking for a circuit to cannibalize, consider family as well
30444 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
30445 circuit cannibalization).
30447 o Code simplifications and refactoring:
30448 - Make a bunch of functions static. Remove some dead code.
30449 - Pull out about a third of the really big routerlist.c; put it in a
30450 new module, networkstatus.c.
30451 - Merge the extra fields in local_routerstatus_t back into
30452 routerstatus_t: we used to need one routerstatus_t for each
30453 authority's opinion, plus a local_routerstatus_t for the locally
30454 computed consensus opinion. To save space, we put the locally
30455 modified fields into local_routerstatus_t, and only the common
30456 stuff into routerstatus_t. But once v3 directories are in use,
30457 clients and caches will no longer need to hold authority opinions;
30458 thus, the rationale for keeping the types separate is now gone.
30459 - Make the code used to reschedule and reattempt downloads more
30461 - Turn all 'Are we a directory server/mirror?' logic into a call to
30463 - Remove the code to generate the oldest (v1) directory format.
30464 The code has been disabled since 0.2.0.5-alpha.
30467 Changes in version 0.2.0.7-alpha - 2007-09-21
30468 This seventh development snapshot makes bridges work again, makes bridge
30469 authorities work for the first time, fixes two huge performance flaws
30470 in hidden services, and fixes a variety of minor issues.
30472 o New directory authorities:
30473 - Set up moria1 and tor26 as the first v3 directory authorities. See
30474 doc/spec/dir-spec.txt for details on the new directory design.
30476 o Major bugfixes (crashes):
30477 - Fix possible segfaults in functions called from
30478 rend_process_relay_cell(). Bugfix on 0.1.2.x.
30480 o Major bugfixes (bridges):
30481 - Fix a bug that made servers send a "404 Not found" in response to
30482 attempts to fetch their server descriptor. This caused Tor servers
30483 to take many minutes to establish reachability for their DirPort,
30484 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
30485 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
30486 users configure that and specify a bridge with an identity
30487 fingerprint, now they will lookup the bridge descriptor at the
30488 default bridge authority via a one-hop tunnel, but once circuits
30489 are established they will switch to a three-hop tunnel for later
30490 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
30492 o Major bugfixes (hidden services):
30493 - Hidden services were choosing introduction points uniquely by
30494 hexdigest, but when constructing the hidden service descriptor
30495 they merely wrote the (potentially ambiguous) nickname.
30496 - Clients now use the v2 intro format for hidden service
30497 connections: they specify their chosen rendezvous point by identity
30498 digest rather than by (potentially ambiguous) nickname. Both
30499 are bugfixes on 0.1.2.x, and they could speed up hidden service
30500 connections dramatically. Thanks to Karsten Loesing.
30502 o Minor features (security):
30503 - As a client, do not believe any server that tells us that an
30504 address maps to an internal address space.
30505 - Make it possible to enable HashedControlPassword and
30506 CookieAuthentication at the same time.
30508 o Minor features (guard nodes):
30509 - Tag every guard node in our state file with the version that
30510 we believe added it, or with our own version if we add it. This way,
30511 if a user temporarily runs an old version of Tor and then switches
30512 back to a new one, she doesn't automatically lose her guards.
30514 o Minor features (speed):
30515 - When implementing AES counter mode, update only the portions of the
30516 counter buffer that need to change, and don't keep separate
30517 network-order and host-order counters when they are the same (i.e.,
30518 on big-endian hosts.)
30520 o Minor features (controller):
30521 - Accept LF instead of CRLF on controller, since some software has a
30522 hard time generating real Internet newlines.
30523 - Add GETINFO values for the server status events
30524 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
30527 o Removed features:
30528 - Routers no longer include bandwidth-history lines in their
30529 descriptors; this information is already available in extra-info
30530 documents, and including it in router descriptors took up 60%
30531 (!) of compressed router descriptor downloads. Completes
30532 implementation of proposal 104.
30533 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
30534 and TorControl.py, as they use the old v0 controller protocol,
30535 and are obsoleted by TorFlow anyway.
30536 - Drop support for v1 rendezvous descriptors, since we never used
30537 them anyway, and the code has probably rotted by now. Based on
30538 patch from Karsten Loesing.
30539 - On OSX, stop warning the user that kqueue support in libevent is
30540 "experimental", since it seems to have worked fine for ages.
30543 - When generating information telling us how to extend to a given
30544 router, do not try to include the nickname if it is absent. Fixes
30545 bug 467. Bugfix on 0.2.0.3-alpha.
30546 - Fix a user-triggerable (but not remotely-triggerable) segfault
30547 in expand_filename(). Bugfix on 0.1.2.x.
30548 - Fix a memory leak when freeing incomplete requests from DNSPort.
30549 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
30550 - Don't try to access (or alter) the state file when running
30551 --list-fingerprint or --verify-config or --hash-password. (Resolves
30552 bug 499.) Bugfix on 0.1.2.x.
30553 - Servers used to decline to publish their DirPort if their
30554 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
30555 were below a threshold. Now they only look at BandwidthRate and
30556 RelayBandwidthRate. Bugfix on 0.1.2.x.
30557 - Remove an optimization in the AES counter-mode code that assumed
30558 that the counter never exceeded 2^68. When the counter can be set
30559 arbitrarily as an IV (as it is by Karsten's new hidden services
30560 code), this assumption no longer holds. Bugfix on 0.1.2.x.
30561 - Resume listing "AUTHORITY" flag for authorities in network status.
30562 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
30564 o Code simplifications and refactoring:
30565 - Revamp file-writing logic so we don't need to have the entire
30566 contents of a file in memory at once before we write to disk. Tor,
30568 - Turn "descriptor store" into a full-fledged type.
30569 - Move all NT services code into a separate source file.
30570 - Unify all code that computes medians, percentile elements, etc.
30571 - Get rid of a needless malloc when parsing address policies.
30574 Changes in version 0.1.2.17 - 2007-08-30
30575 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
30576 X bundles. Vidalia 0.0.14 makes authentication required for the
30577 ControlPort in the default configuration, which addresses important
30578 security risks. Everybody who uses Vidalia (or another controller)
30581 In addition, this Tor update fixes major load balancing problems with
30582 path selection, which should speed things up a lot once many people
30585 o Major bugfixes (security):
30586 - We removed support for the old (v0) control protocol. It has been
30587 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
30588 become more of a headache than it's worth.
30590 o Major bugfixes (load balancing):
30591 - When choosing nodes for non-guard positions, weight guards
30592 proportionally less, since they already have enough load. Patch
30594 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
30595 will allow fast Tor servers to get more attention.
30596 - When we're upgrading from an old Tor version, forget our current
30597 guards and pick new ones according to the new weightings. These
30598 three load balancing patches could raise effective network capacity
30599 by a factor of four. Thanks to Mike Perry for measurements.
30601 o Major bugfixes (stream expiration):
30602 - Expire not-yet-successful application streams in all cases if
30603 they've been around longer than SocksTimeout. Right now there are
30604 some cases where the stream will live forever, demanding a new
30605 circuit every 15 seconds. Fixes bug 454; reported by lodger.
30607 o Minor features (controller):
30608 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
30609 is valid before any authentication has been received. It tells
30610 a controller what kind of authentication is expected, and what
30611 protocol is spoken. Implements proposal 119.
30613 o Minor bugfixes (performance):
30614 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
30615 greatly speeding up loading cached-routers from disk on startup.
30616 - Disable sentinel-based debugging for buffer code: we squashed all
30617 the bugs that this was supposed to detect a long time ago, and now
30618 its only effect is to change our buffer sizes from nice powers of
30619 two (which platform mallocs tend to like) to values slightly over
30620 powers of two (which make some platform mallocs sad).
30622 o Minor bugfixes (misc):
30623 - If exit bandwidth ever exceeds one third of total bandwidth, then
30624 use the correct formula to weight exit nodes when choosing paths.
30625 Based on patch from Mike Perry.
30626 - Choose perfectly fairly among routers when choosing by bandwidth and
30627 weighting by fraction of bandwidth provided by exits. Previously, we
30628 would choose with only approximate fairness, and correct ourselves
30629 if we ran off the end of the list.
30630 - If we require CookieAuthentication but we fail to write the
30631 cookie file, we would warn but not exit, and end up in a state
30632 where no controller could authenticate. Now we exit.
30633 - If we require CookieAuthentication, stop generating a new cookie
30634 every time we change any piece of our config.
30635 - Refuse to start with certain directory authority keys, and
30636 encourage people using them to stop.
30637 - Terminate multi-line control events properly. Original patch
30639 - Fix a minor memory leak when we fail to find enough suitable
30640 servers to choose a circuit.
30641 - Stop leaking part of the descriptor when we run into a particularly
30642 unparseable piece of it.
30645 Changes in version 0.2.0.6-alpha - 2007-08-26
30646 This sixth development snapshot features a new Vidalia version in the
30647 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
30648 the ControlPort in the default configuration, which addresses important
30651 In addition, this snapshot fixes major load balancing problems
30652 with path selection, which should speed things up a lot once many
30653 people have upgraded. The directory authorities also use a new
30654 mean-time-between-failure approach to tracking which servers are stable,
30655 rather than just looking at the most recent uptime.
30657 o New directory authorities:
30658 - Set up Tonga as the default bridge directory authority.
30661 - Directory authorities now track servers by weighted
30662 mean-times-between-failures. When we have 4 or more days of data,
30663 use measured MTBF rather than declared uptime to decide whether
30664 to call a router Stable. Implements proposal 108.
30666 o Major bugfixes (load balancing):
30667 - When choosing nodes for non-guard positions, weight guards
30668 proportionally less, since they already have enough load. Patch
30670 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
30671 will allow fast Tor servers to get more attention.
30672 - When we're upgrading from an old Tor version, forget our current
30673 guards and pick new ones according to the new weightings. These
30674 three load balancing patches could raise effective network capacity
30675 by a factor of four. Thanks to Mike Perry for measurements.
30677 o Major bugfixes (descriptor parsing):
30678 - Handle unexpected whitespace better in malformed descriptors. Bug
30679 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
30682 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
30683 GETINFO for Torstat to use until it can switch to using extrainfos.
30684 - Optionally (if built with -DEXPORTMALLINFO) export the output
30685 of mallinfo via http, as tor/mallinfo.txt. Only accessible
30689 - Do not intermix bridge routers with controller-added
30690 routers. (Bugfix on 0.2.0.x)
30691 - Do not fail with an assert when accept() returns an unexpected
30692 address family. Addresses but does not wholly fix bug 483. (Bugfix
30694 - Let directory authorities startup even when they can't generate
30695 a descriptor immediately, e.g. because they don't know their
30697 - Stop putting the authentication cookie in a file called "0"
30698 in your working directory if you don't specify anything for the
30699 new CookieAuthFile option. Reported by Matt Edman.
30700 - Make it possible to read the PROTOCOLINFO response in a way that
30701 conforms to our control-spec. Reported by Matt Edman.
30702 - Fix a minor memory leak when we fail to find enough suitable
30703 servers to choose a circuit. Bugfix on 0.1.2.x.
30704 - Stop leaking part of the descriptor when we run into a particularly
30705 unparseable piece of it. Bugfix on 0.1.2.x.
30706 - Unmap the extrainfo cache file on exit.
30709 Changes in version 0.2.0.5-alpha - 2007-08-19
30710 This fifth development snapshot fixes compilation on Windows again;
30711 fixes an obnoxious client-side bug that slowed things down and put
30712 extra load on the network; gets us closer to using the v3 directory
30713 voting scheme; makes it easier for Tor controllers to use cookie-based
30714 authentication; and fixes a variety of other bugs.
30716 o Removed features:
30717 - Version 1 directories are no longer generated in full. Instead,
30718 authorities generate and serve "stub" v1 directories that list
30719 no servers. This will stop Tor versions 0.1.0.x and earlier from
30720 working, but (for security reasons) nobody should be running those
30723 o Major bugfixes (compilation, 0.2.0.x):
30724 - Try to fix Win32 compilation again: improve checking for IPv6 types.
30725 - Try to fix MSVC compilation: build correctly on platforms that do
30726 not define s6_addr16 or s6_addr32.
30727 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
30730 o Major bugfixes (stream expiration):
30731 - Expire not-yet-successful application streams in all cases if
30732 they've been around longer than SocksTimeout. Right now there are
30733 some cases where the stream will live forever, demanding a new
30734 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
30735 reported by lodger.
30737 o Minor features (directory servers):
30738 - When somebody requests a list of statuses or servers, and we have
30739 none of those, return a 404 rather than an empty 200.
30741 o Minor features (directory voting):
30742 - Store v3 consensus status consensuses on disk, and reload them
30745 o Minor features (security):
30746 - Warn about unsafe ControlPort configurations.
30747 - Refuse to start with certain directory authority keys, and
30748 encourage people using them to stop.
30750 o Minor features (controller):
30751 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
30752 is valid before any authentication has been received. It tells
30753 a controller what kind of authentication is expected, and what
30754 protocol is spoken. Implements proposal 119.
30755 - New config option CookieAuthFile to choose a new location for the
30756 cookie authentication file, and config option
30757 CookieAuthFileGroupReadable to make it group-readable.
30759 o Minor features (unit testing):
30760 - Add command-line arguments to unit-test executable so that we can
30761 invoke any chosen test from the command line rather than having
30762 to run the whole test suite at once; and so that we can turn on
30763 logging for the unit tests.
30765 o Minor bugfixes (on 0.1.2.x):
30766 - If we require CookieAuthentication but we fail to write the
30767 cookie file, we would warn but not exit, and end up in a state
30768 where no controller could authenticate. Now we exit.
30769 - If we require CookieAuthentication, stop generating a new cookie
30770 every time we change any piece of our config.
30771 - When loading bandwidth history, do not believe any information in
30772 the future. Fixes bug 434.
30773 - When loading entry guard information, do not believe any information
30775 - When we have our clock set far in the future and generate an
30776 onion key, then re-set our clock to be correct, we should not stop
30777 the onion key from getting rotated.
30778 - Clean up torrc sample config file.
30779 - Do not automatically run configure from autogen.sh. This
30780 non-standard behavior tended to annoy people who have built other
30783 o Minor bugfixes (on 0.2.0.x):
30784 - Fix a bug with AutomapHostsOnResolve that would always cause
30785 the second request to fail. Bug reported by Kate. Bugfix on
30787 - Fix a bug in ADDRMAP controller replies that would sometimes
30788 try to print a NULL. Patch from tup.
30789 - Read v3 directory authority keys from the right location.
30790 - Numerous bugfixes to directory voting code.
30793 Changes in version 0.1.2.16 - 2007-08-01
30794 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
30795 remote attacker in certain situations to rewrite the user's torrc
30796 configuration file. This can completely compromise anonymity of users
30797 in most configurations, including those running the Vidalia bundles,
30798 TorK, etc. Or worse.
30800 o Major security fixes:
30801 - Close immediately after missing authentication on control port;
30802 do not allow multiple authentication attempts.
30805 Changes in version 0.2.0.4-alpha - 2007-08-01
30806 This fourth development snapshot fixes a critical security vulnerability
30807 for most users, specifically those running Vidalia, TorK, etc. Everybody
30808 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
30810 o Major security fixes:
30811 - Close immediately after missing authentication on control port;
30812 do not allow multiple authentication attempts.
30814 o Major bugfixes (compilation):
30815 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
30818 o Minor features (performance):
30819 - Be even more aggressive about releasing RAM from small
30820 empty buffers. Thanks to our free-list code, this shouldn't be too
30821 performance-intensive.
30822 - Disable sentinel-based debugging for buffer code: we squashed all
30823 the bugs that this was supposed to detect a long time ago, and
30824 now its only effect is to change our buffer sizes from nice
30825 powers of two (which platform mallocs tend to like) to values
30826 slightly over powers of two (which make some platform mallocs sad).
30827 - Log malloc statistics from mallinfo() on platforms where it
30831 Changes in version 0.2.0.3-alpha - 2007-07-29
30832 This third development snapshot introduces new experimental
30833 blocking-resistance features and a preliminary version of the v3
30834 directory voting design, and includes many other smaller features
30838 - The first pieces of our "bridge" design for blocking-resistance
30839 are implemented. People can run bridge directory authorities;
30840 people can run bridges; and people can configure their Tor clients
30841 with a set of bridges to use as the first hop into the Tor network.
30842 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
30844 - Create listener connections before we setuid to the configured
30845 User and Group. Now non-Windows users can choose port values
30846 under 1024, start Tor as root, and have Tor bind those ports
30847 before it changes to another UID. (Windows users could already
30849 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
30850 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
30851 on "vserver" accounts. (Patch from coderman.)
30852 - Be even more aggressive about separating local traffic from relayed
30853 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
30855 o Major features (experimental):
30856 - First cut of code for "v3 dir voting": directory authorities will
30857 vote on a common network status document rather than each publishing
30858 their own opinion. This code needs more testing and more corner-case
30859 handling before it's ready for use.
30862 - Directory authorities now call routers Fast if their bandwidth is
30863 at least 100KB/s, and consider their bandwidth adequate to be a
30864 Guard if it is at least 250KB/s, no matter the medians. This fix
30865 complements proposal 107. [Bugfix on 0.1.2.x]
30866 - Directory authorities now never mark more than 3 servers per IP as
30867 Valid and Running. (Implements proposal 109, by Kevin Bauer and
30869 - Minor change to organizationName and commonName generation
30870 procedures in TLS certificates during Tor handshakes, to invalidate
30871 some earlier censorware approaches. This is not a long-term
30872 solution, but applying it will give us a bit of time to look into
30873 the epidemiology of countermeasures as they spread.
30875 o Major bugfixes (directory):
30876 - Rewrite directory tokenization code to never run off the end of
30877 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
30879 o Minor features (controller):
30880 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
30881 match requests to applications. (Patch from Robert Hogan.)
30882 - Report address and port correctly on connections to DNSPort. (Patch
30883 from Robert Hogan.)
30884 - Add a RESOLVE command to launch hostname lookups. (Original patch
30885 from Robert Hogan.)
30886 - Add GETINFO status/enough-dir-info to let controllers tell whether
30887 Tor has downloaded sufficient directory information. (Patch
30889 - You can now use the ControlSocket option to tell Tor to listen for
30890 controller connections on Unix domain sockets on systems that
30891 support them. (Patch from Peter Palfrader.)
30892 - STREAM NEW events are generated for DNSPort requests and for
30893 tunneled directory connections. (Patch from Robert Hogan.)
30894 - New "GETINFO address-mappings/*" command to get address mappings
30895 with expiry information. "addr-mappings/*" is now deprecated.
30898 o Minor features (misc):
30899 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
30901 - The tor-gencert tool for v3 directory authorities now creates all
30902 files as readable to the file creator only, and write-protects
30903 the authority identity key.
30904 - When dumping memory usage, list bytes used in buffer memory
30906 - When running with dmalloc, dump more stats on hup and on exit.
30907 - Directory authorities now fail quickly and (relatively) harmlessly
30908 if they generate a network status document that is somehow
30911 o Traffic load balancing improvements:
30912 - If exit bandwidth ever exceeds one third of total bandwidth, then
30913 use the correct formula to weight exit nodes when choosing paths.
30914 (Based on patch from Mike Perry.)
30915 - Choose perfectly fairly among routers when choosing by bandwidth and
30916 weighting by fraction of bandwidth provided by exits. Previously, we
30917 would choose with only approximate fairness, and correct ourselves
30918 if we ran off the end of the list. [Bugfix on 0.1.2.x]
30920 o Performance improvements:
30921 - Be more aggressive with freeing buffer RAM or putting it on the
30923 - Use Critical Sections rather than Mutexes for synchronizing threads
30924 on win32; Mutexes are heavier-weight, and designed for synchronizing
30927 o Deprecated and removed features:
30928 - RedirectExits is now deprecated.
30929 - Stop allowing address masks that do not correspond to bit prefixes.
30930 We have warned about these for a really long time; now it's time
30931 to reject them. (Patch from croup.)
30933 o Minor bugfixes (directory):
30934 - Fix another crash bug related to extra-info caching. (Bug found by
30935 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
30936 - Directories no longer return a "304 not modified" when they don't
30937 have the networkstatus the client asked for. Also fix a memory
30938 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
30939 - We had accidentally labelled 0.1.2.x directory servers as not
30940 suitable for begin_dir requests, and had labelled no directory
30941 servers as suitable for uploading extra-info documents. [Bugfix
30944 o Minor bugfixes (dns):
30945 - Fix a crash when DNSPort is set more than once. (Patch from Robert
30946 Hogan.) [Bugfix on 0.2.0.2-alpha]
30947 - Add DNSPort connections to the global connection list, so that we
30948 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
30950 - Fix a dangling reference that could lead to a crash when DNSPort is
30951 changed or closed (Patch from Robert Hogan.) [Bugfix on
30954 o Minor bugfixes (controller):
30955 - Provide DNS expiry times in GMT, not in local time. For backward
30956 compatibility, ADDRMAP events only provide GMT expiry in an extended
30957 field. "GETINFO address-mappings" always does the right thing.
30958 - Use CRLF line endings properly in NS events.
30959 - Terminate multi-line control events properly. (Original patch
30960 from tup.) [Bugfix on 0.1.2.x-alpha]
30961 - Do not include spaces in SOURCE_ADDR fields in STREAM
30962 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
30965 Changes in version 0.1.2.15 - 2007-07-17
30966 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
30967 problems, fixes compilation on BSD, and fixes a variety of other
30968 bugs. Everybody should upgrade.
30970 o Major bugfixes (compilation):
30971 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
30973 o Major bugfixes (crashes):
30974 - Try even harder not to dereference the first character after
30975 an mmap(). Reported by lodger.
30976 - Fix a crash bug in directory authorities when we re-number the
30977 routerlist while inserting a new router.
30978 - When the cached-routers file is an even multiple of the page size,
30979 don't run off the end and crash. (Fixes bug 455; based on idea
30981 - Fix eventdns.c behavior on Solaris: It is critical to include
30982 orconfig.h _before_ sys/types.h, so that we can get the expected
30983 definition of _FILE_OFFSET_BITS.
30985 o Major bugfixes (security):
30986 - Fix a possible buffer overrun when using BSD natd support. Bug
30988 - When sending destroy cells from a circuit's origin, don't include
30989 the reason for tearing down the circuit. The spec says we didn't,
30990 and now we actually don't. Reported by lodger.
30991 - Keep streamids from different exits on a circuit separate. This
30992 bug may have allowed other routers on a given circuit to inject
30993 cells into streams. Reported by lodger; fixes bug 446.
30994 - If there's a never-before-connected-to guard node in our list,
30995 never choose any guards past it. This way we don't expand our
30996 guard list unless we need to.
30998 o Minor bugfixes (guard nodes):
30999 - Weight guard selection by bandwidth, so that low-bandwidth nodes
31000 don't get overused as guards.
31002 o Minor bugfixes (directory):
31003 - Correctly count the number of authorities that recommend each
31004 version. Previously, we were under-counting by 1.
31005 - Fix a potential crash bug when we load many server descriptors at
31006 once and some of them make others of them obsolete. Fixes bug 458.
31008 o Minor bugfixes (hidden services):
31009 - Stop tearing down the whole circuit when the user asks for a
31010 connection to a port that the hidden service didn't configure.
31013 o Minor bugfixes (misc):
31014 - On Windows, we were preventing other processes from reading
31015 cached-routers while Tor was running. Reported by janbar.
31016 - Fix a possible (but very unlikely) bug in picking routers by
31017 bandwidth. Add a log message to confirm that it is in fact
31018 unlikely. Patch from lodger.
31019 - Backport a couple of memory leak fixes.
31020 - Backport miscellaneous cosmetic bugfixes.
31023 Changes in version 0.2.0.2-alpha - 2007-06-02
31024 o Major bugfixes on 0.2.0.1-alpha:
31025 - Fix an assertion failure related to servers without extra-info digests.
31026 Resolves bugs 441 and 442.
31028 o Minor features (directory):
31029 - Support "If-Modified-Since" when answering HTTP requests for
31030 directories, running-routers documents, and network-status documents.
31031 (There's no need to support it for router descriptors, since those
31032 are downloaded by descriptor digest.)
31034 o Minor build issues:
31035 - Clear up some MIPSPro compiler warnings.
31036 - When building from a tarball on a machine that happens to have SVK
31037 installed, report the micro-revision as whatever version existed
31038 in the tarball, not as "x".
31041 Changes in version 0.2.0.1-alpha - 2007-06-01
31042 This early development snapshot provides new features for people running
31043 Tor as both a client and a server (check out the new RelayBandwidth
31044 config options); lets Tor run as a DNS proxy; and generally moves us
31045 forward on a lot of fronts.
31047 o Major features, server usability:
31048 - New config options RelayBandwidthRate and RelayBandwidthBurst:
31049 a separate set of token buckets for relayed traffic. Right now
31050 relayed traffic is defined as answers to directory requests, and
31051 OR connections that don't have any local circuits on them.
31053 o Major features, client usability:
31054 - A client-side DNS proxy feature to replace the need for
31055 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
31056 for DNS requests on port 9999, use the Tor network to resolve them
31057 anonymously, and send the reply back like a regular DNS server.
31058 The code still only implements a subset of DNS.
31059 - Make PreferTunneledDirConns and TunnelDirConns work even when
31060 we have no cached directory info. This means Tor clients can now
31061 do all of their connections protected by TLS.
31063 o Major features, performance and efficiency:
31064 - Directory authorities accept and serve "extra info" documents for
31065 routers. These documents contain fields from router descriptors
31066 that aren't usually needed, and that use a lot of excess
31067 bandwidth. Once these fields are removed from router descriptors,
31068 the bandwidth savings should be about 60%. [Partially implements
31070 - Servers upload extra-info documents to any authority that accepts
31071 them. Authorities (and caches that have been configured to download
31072 extra-info documents) download them as needed. [Partially implements
31074 - Change the way that Tor buffers data that it is waiting to write.
31075 Instead of queueing data cells in an enormous ring buffer for each
31076 client->OR or OR->OR connection, we now queue cells on a separate
31077 queue for each circuit. This lets us use less slack memory, and
31078 will eventually let us be smarter about prioritizing different kinds
31080 - Use memory pools to allocate cells with better speed and memory
31081 efficiency, especially on platforms where malloc() is inefficient.
31082 - Stop reading on edge connections when their corresponding circuit
31083 buffers are full; start again as the circuits empty out.
31085 o Major features, other:
31086 - Add an HSAuthorityRecordStats option that hidden service authorities
31087 can use to track statistics of overall hidden service usage without
31088 logging information that would be very useful to an attacker.
31089 - Start work implementing multi-level keys for directory authorities:
31090 Add a standalone tool to generate key certificates. (Proposal 103.)
31093 - Directory authorities now call routers Stable if they have an
31094 uptime of at least 30 days, even if that's not the median uptime
31095 in the network. Implements proposal 107, suggested by Kevin Bauer
31098 o Minor fixes (resource management):
31099 - Count the number of open sockets separately from the number
31100 of active connection_t objects. This will let us avoid underusing
31101 our allocated connection limit.
31102 - We no longer use socket pairs to link an edge connection to an
31103 anonymous directory connection or a DirPort test connection.
31104 Instead, we track the link internally and transfer the data
31105 in-process. This saves two sockets per "linked" connection (at the
31106 client and at the server), and avoids the nasty Windows socketpair()
31108 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
31109 for every single inactive connection_t. Free items from the
31110 4k/16k-buffer free lists when they haven't been used for a while.
31112 o Minor features (build):
31113 - Make autoconf search for libevent, openssl, and zlib consistently.
31114 - Update deprecated macros in configure.in.
31115 - When warning about missing headers, tell the user to let us
31116 know if the compile succeeds anyway, so we can downgrade the
31118 - Include the current subversion revision as part of the version
31119 string: either fetch it directly if we're in an SVN checkout, do
31120 some magic to guess it if we're in an SVK checkout, or use
31121 the last-detected version if we're building from a .tar.gz.
31122 Use this version consistently in log messages.
31124 o Minor features (logging):
31125 - Always prepend "Bug: " to any log message about a bug.
31126 - Put a platform string (e.g. "Linux i686") in the startup log
31127 message, so when people paste just their logs, we know if it's
31128 OpenBSD or Windows or what.
31129 - When logging memory usage, break down memory used in buffers by
31132 o Minor features (directory system):
31133 - New config option V2AuthoritativeDirectory that all directory
31134 authorities should set. This will let future authorities choose
31135 not to serve V2 directory information.
31136 - Directory authorities allow multiple router descriptors and/or extra
31137 info documents to be uploaded in a single go. This will make
31138 implementing proposal 104 simpler.
31140 o Minor features (controller):
31141 - Add a new config option __DisablePredictedCircuits designed for
31142 use by the controller, when we don't want Tor to build any circuits
31144 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
31145 so we can exit from the middle of the circuit.
31146 - Implement "getinfo status/circuit-established".
31147 - Implement "getinfo status/version/..." so a controller can tell
31148 whether the current version is recommended, and whether any versions
31149 are good, and how many authorities agree. (Patch from shibz.)
31151 o Minor features (hidden services):
31152 - Allow multiple HiddenServicePort directives with the same virtual
31153 port; when they occur, the user is sent round-robin to one
31154 of the target ports chosen at random. Partially fixes bug 393 by
31155 adding limited ad-hoc round-robining.
31157 o Minor features (other):
31159 - Add a new AutomapHostsOnResolve option: when it is enabled, any
31160 resolve request for hosts matching a given pattern causes Tor to
31161 generate an internal virtual address mapping for that host. This
31162 allows DNSPort to work sensibly with hidden service users. By
31163 default, .exit and .onion addresses are remapped; the list of
31164 patterns can be reconfigured with AutomapHostsSuffixes.
31165 - Add an "-F" option to tor-resolve to force a resolve for a .onion
31166 address. Thanks to the AutomapHostsOnResolve option, this is no
31167 longer a completely silly thing to do.
31168 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
31169 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
31170 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
31171 minus 1 byte: the actual maximum declared bandwidth.
31173 o Removed features:
31174 - Removed support for the old binary "version 0" controller protocol.
31175 This has been deprecated since 0.1.1, and warnings have been issued
31176 since 0.1.2. When we encounter a v0 control message, we now send
31177 back an error and close the connection.
31178 - Remove the old "dns worker" server DNS code: it hasn't been default
31179 since 0.1.2.2-alpha, and all the servers seem to be using the new
31182 o Minor bugfixes (portability):
31183 - Even though Windows is equally happy with / and \ as path separators,
31184 try to use \ consistently on Windows and / consistently on Unix: it
31185 makes the log messages nicer.
31186 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
31187 - Read resolv.conf files correctly on platforms where read() returns
31188 partial results on small file reads.
31190 o Minor bugfixes (directory):
31191 - Correctly enforce that elements of directory objects do not appear
31192 more often than they are allowed to appear.
31193 - When we are reporting the DirServer line we just parsed, we were
31194 logging the second stanza of the key fingerprint, not the first.
31196 o Minor bugfixes (logging):
31197 - When we hit an EOF on a log (probably because we're shutting down),
31198 don't try to remove the log from the list: just mark it as
31199 unusable. (Bulletproofs against bug 222.)
31201 o Minor bugfixes (other):
31202 - In the exitlist script, only consider the most recently published
31203 server descriptor for each server. Also, when the user requests
31204 a list of servers that _reject_ connections to a given address,
31205 explicitly exclude the IPs that also have servers that accept
31206 connections to that address. (Resolves bug 405.)
31207 - Stop allowing hibernating servers to be "stable" or "fast".
31208 - On Windows, we were preventing other processes from reading
31209 cached-routers while Tor was running. (Reported by janbar)
31210 - Make the NodeFamilies config option work. (Reported by
31211 lodger -- it has never actually worked, even though we added it
31213 - Check return values from pthread_mutex functions.
31214 - Don't save non-general-purpose router descriptors to the disk cache,
31215 because we have no way of remembering what their purpose was when
31217 - Add even more asserts to hunt down bug 417.
31218 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
31219 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
31220 Add a log message to confirm that it is in fact unlikely.
31222 o Minor bugfixes (controller):
31223 - Make 'getinfo fingerprint' return a 551 error if we're not a
31224 server, so we match what the control spec claims we do. Reported
31226 - Fix a typo in an error message when extendcircuit fails that
31227 caused us to not follow the \r\n-based delimiter protocol. Reported
31230 o Code simplifications and refactoring:
31231 - Stop passing around circuit_t and crypt_path_t pointers that are
31232 implicit in other procedure arguments.
31233 - Drop the old code to choke directory connections when the
31234 corresponding OR connections got full: thanks to the cell queue
31235 feature, OR conns don't get full any more.
31236 - Make dns_resolve() handle attaching connections to circuits
31237 properly, so the caller doesn't have to.
31238 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
31239 - Keep the connection array as a dynamic smartlist_t, rather than as
31240 a fixed-sized array. This is important, as the number of connections
31241 is becoming increasingly decoupled from the number of sockets.
31244 Changes in version 0.1.2.14 - 2007-05-25
31245 Tor 0.1.2.14 changes the addresses of two directory authorities (this
31246 change especially affects those who serve or use hidden services),
31247 and fixes several other crash- and security-related bugs.
31249 o Directory authority changes:
31250 - Two directory authorities (moria1 and moria2) just moved to new
31251 IP addresses. This change will particularly affect those who serve
31252 or use hidden services.
31254 o Major bugfixes (crashes):
31255 - If a directory server runs out of space in the connection table
31256 as it's processing a begin_dir request, it will free the exit stream
31257 but leave it attached to the circuit, leading to unpredictable
31258 behavior. (Reported by seeess, fixes bug 425.)
31259 - Fix a bug in dirserv_remove_invalid() that would cause authorities
31260 to corrupt memory under some really unlikely scenarios.
31261 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
31262 - Avoid segfaults when reading from mmaped descriptor file. (Reported
31265 o Major bugfixes (security):
31266 - When choosing an entry guard for a circuit, avoid using guards
31267 that are in the same family as the chosen exit -- not just guards
31268 that are exactly the chosen exit. (Reported by lodger.)
31270 o Major bugfixes (resource management):
31271 - If a directory authority is down, skip it when deciding where to get
31272 networkstatus objects or descriptors. Otherwise we keep asking
31273 every 10 seconds forever. Fixes bug 384.
31274 - Count it as a failure if we fetch a valid network-status but we
31275 don't want to keep it. Otherwise we'll keep fetching it and keep
31276 not wanting to keep it. Fixes part of bug 422.
31277 - If all of our dirservers have given us bad or no networkstatuses
31278 lately, then stop hammering them once per minute even when we
31279 think they're failed. Fixes another part of bug 422.
31282 - Actually set the purpose correctly for descriptors inserted with
31283 purpose=controller.
31284 - When we have k non-v2 authorities in our DirServer config,
31285 we ignored the last k authorities in the list when updating our
31287 - Correctly back-off from requesting router descriptors that we are
31288 having a hard time downloading.
31289 - Read resolv.conf files correctly on platforms where read() returns
31290 partial results on small file reads.
31291 - Don't rebuild the entire router store every time we get 32K of
31292 routers: rebuild it when the journal gets very large, or when
31293 the gaps in the store get very large.
31296 - When routers publish SVN revisions in their router descriptors,
31297 authorities now include those versions correctly in networkstatus
31299 - Warn when using a version of libevent before 1.3b to run a server on
31300 OSX or BSD: these versions interact badly with userspace threads.
31303 Changes in version 0.1.2.13 - 2007-04-24
31304 This release features some major anonymity fixes, such as safer path
31305 selection; better client performance; faster bootstrapping, better
31306 address detection, and better DNS support for servers; write limiting as
31307 well as read limiting to make servers easier to run; and a huge pile of
31308 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
31310 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
31311 of the Freenode IRC network, remembering his patience and vision for
31312 free speech on the Internet.
31315 - Fix a memory leak when we ask for "all" networkstatuses and we
31316 get one we don't recognize.
31317 - Add more asserts to hunt down bug 417.
31318 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
31321 Changes in version 0.1.2.12-rc - 2007-03-16
31323 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
31324 directory information requested inside Tor connections (i.e. via
31325 begin_dir cells). It only triggered when the same connection was
31326 serving other data at the same time. Reported by seeess.
31329 - When creating a circuit via the controller, send a 'launched'
31330 event when we're done, so we follow the spec better.
31333 Changes in version 0.1.2.11-rc - 2007-03-15
31334 o Minor bugfixes (controller), reported by daejees:
31335 - Correct the control spec to match how the code actually responds
31336 to 'getinfo addr-mappings/*'.
31337 - The control spec described a GUARDS event, but the code
31338 implemented a GUARD event. Standardize on GUARD, but let people
31339 ask for GUARDS too.
31342 Changes in version 0.1.2.10-rc - 2007-03-07
31343 o Major bugfixes (Windows):
31344 - Do not load the NT services library functions (which may not exist)
31345 just to detect if we're a service trying to shut down. Now we run
31346 on Win98 and friends again.
31348 o Minor bugfixes (other):
31349 - Clarify a couple of log messages.
31350 - Fix a misleading socks5 error number.
31353 Changes in version 0.1.2.9-rc - 2007-03-02
31354 o Major bugfixes (Windows):
31355 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
31356 of the usual GCC "%llu". This prevents a bug when saving 64-bit
31357 int configuration values: the high-order 32 bits would get
31358 truncated. In particular, we were being bitten by the default
31359 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
31360 and maybe also bug 397.)
31362 o Minor bugfixes (performance):
31363 - Use OpenSSL's AES implementation on platforms where it's faster.
31364 This could save us as much as 10% CPU usage.
31366 o Minor bugfixes (server):
31367 - Do not rotate onion key immediately after setting it for the first
31370 o Minor bugfixes (directory authorities):
31371 - Stop calling servers that have been hibernating for a long time
31372 "stable". Also, stop letting hibernating or obsolete servers affect
31373 uptime and bandwidth cutoffs.
31374 - Stop listing hibernating servers in the v1 directory.
31376 o Minor bugfixes (hidden services):
31377 - Upload hidden service descriptors slightly less often, to reduce
31378 load on authorities.
31380 o Minor bugfixes (other):
31381 - Fix an assert that could trigger if a controller quickly set then
31382 cleared EntryNodes. Bug found by Udo van den Heuvel.
31383 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
31385 - Fix a potential race condition in the rpm installer. Found by
31387 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
31388 of 2 as indicating that the server is completely bad; it sometimes
31389 means that the server is just bad for the request in question. (may fix
31390 the last of bug 326.)
31391 - Disable encrypted directory connections when we don't have a server
31392 descriptor for the destination. We'll get this working again in
31396 Changes in version 0.1.2.8-beta - 2007-02-26
31397 o Major bugfixes (crashes):
31398 - Stop crashing when the controller asks us to resetconf more than
31399 one config option at once. (Vidalia 0.0.11 does this.)
31400 - Fix a crash that happened on Win98 when we're given command-line
31401 arguments: don't try to load NT service functions from advapi32.dll
31402 except when we need them. (Bug introduced in 0.1.2.7-alpha;
31404 - Fix a longstanding obscure crash bug that could occur when
31405 we run out of DNS worker processes. (Resolves bug 390.)
31407 o Major bugfixes (hidden services):
31408 - Correctly detect whether hidden service descriptor downloads are
31409 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
31411 o Major bugfixes (accounting):
31412 - When we start during an accounting interval before it's time to wake
31413 up, remember to wake up at the correct time. (May fix bug 342.)
31415 o Minor bugfixes (controller):
31416 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
31417 clear the corresponding on_circuit variable, and remember later
31418 that we don't need to send a redundant CLOSED event. Resolves part
31420 - Report events where a resolve succeeded or where we got a socks
31421 protocol error correctly, rather than calling both of them
31423 - Change reported stream target addresses to IP consistently when
31424 we finally get the IP from an exit node.
31425 - Send log messages to the controller even if they happen to be very
31428 o Minor bugfixes (other):
31429 - Display correct results when reporting which versions are
31430 recommended, and how recommended they are. (Resolves bug 383.)
31431 - Improve our estimates for directory bandwidth to be less random:
31432 guess that an unrecognized directory will have the average bandwidth
31433 from all known directories, not that it will have the average
31434 bandwidth from those directories earlier than it on the list.
31435 - If we start a server with ClientOnly 1, then set ClientOnly to 0
31436 and hup, stop triggering an assert based on an empty onion_key.
31437 - On platforms with no working mmap() equivalent, don't warn the
31438 user when cached-routers doesn't exist.
31439 - Warn the user when mmap() [or its equivalent] fails for some reason
31440 other than file-not-found.
31441 - Don't warn the user when cached-routers.new doesn't exist: that's
31442 perfectly fine when starting up for the first time.
31443 - When EntryNodes are configured, rebuild the guard list to contain,
31444 in order: the EntryNodes that were guards before; the rest of the
31445 EntryNodes; the nodes that were guards before.
31446 - Mask out all signals in sub-threads; only the libevent signal
31447 handler should be processing them. This should prevent some crashes
31448 on some machines using pthreads. (Patch from coderman.)
31449 - Fix switched arguments on memset in the implementation of
31450 tor_munmap() for systems with no mmap() call.
31451 - When Tor receives a router descriptor that it asked for, but
31452 no longer wants (because it has received fresh networkstatuses
31453 in the meantime), do not warn the user. Cache the descriptor if
31454 we're a cache; drop it if we aren't.
31455 - Make earlier entry guards _really_ get retried when the network
31457 - On a malformed DNS reply, always give an error to the corresponding
31459 - Build with recent libevents on platforms that do not define the
31460 nonstandard types "u_int8_t" and friends.
31462 o Minor features (controller):
31463 - Warn the user when an application uses the obsolete binary v0
31464 control protocol. We're planning to remove support for it during
31465 the next development series, so it's good to give people some
31467 - Add STREAM_BW events to report per-entry-stream bandwidth
31468 use. (Patch from Robert Hogan.)
31469 - Rate-limit SIGNEWNYM signals in response to controllers that
31470 impolitely generate them for every single stream. (Patch from
31471 mwenge; closes bug 394.)
31472 - Make REMAP stream events have a SOURCE (cache or exit), and
31473 make them generated in every case where we get a successful
31474 connected or resolved cell.
31476 o Minor bugfixes (performance):
31477 - Call router_have_min_dir_info half as often. (This is showing up in
31478 some profiles, but not others.)
31479 - When using GCC, make log_debug never get called at all, and its
31480 arguments never get evaluated, when no debug logs are configured.
31481 (This is showing up in some profiles, but not others.)
31484 - Remove some never-implemented options. Mark PathlenCoinWeight as
31486 - Implement proposal 106: Stop requiring clients to have well-formed
31487 certificates; stop checking nicknames in certificates. (Clients
31488 have certificates so that they can look like Tor servers, but in
31489 the future we might want to allow them to look like regular TLS
31490 clients instead. Nicknames in certificates serve no purpose other
31491 than making our protocol easier to recognize on the wire.)
31492 - Revise messages on handshake failure again to be even more clear about
31493 which are incoming connections and which are outgoing.
31494 - Discard any v1 directory info that's over 1 month old (for
31495 directories) or over 1 week old (for running-routers lists).
31496 - Do not warn when individual nodes in the configuration's EntryNodes,
31497 ExitNodes, etc are down: warn only when all possible nodes
31498 are down. (Fixes bug 348.)
31499 - Always remove expired routers and networkstatus docs before checking
31500 whether we have enough information to build circuits. (Fixes
31502 - Put a lower-bound on MaxAdvertisedBandwidth.
31505 Changes in version 0.1.2.7-alpha - 2007-02-06
31506 o Major bugfixes (rate limiting):
31507 - Servers decline directory requests much more aggressively when
31508 they're low on bandwidth. Otherwise they end up queueing more and
31509 more directory responses, which can't be good for latency.
31510 - But never refuse directory requests from local addresses.
31511 - Fix a memory leak when sending a 503 response for a networkstatus
31513 - Be willing to read or write on local connections (e.g. controller
31514 connections) even when the global rate limiting buckets are empty.
31515 - If our system clock jumps back in time, don't publish a negative
31516 uptime in the descriptor. Also, don't let the global rate limiting
31517 buckets go absurdly negative.
31518 - Flush local controller connection buffers periodically as we're
31519 writing to them, so we avoid queueing 4+ megabytes of data before
31522 o Major bugfixes (NT services):
31523 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
31524 command-line flag so that admins can override the default by saying
31525 "tor --service install --user "SomeUser"". This will not affect
31526 existing installed services. Also, warn the user that the service
31527 will look for its configuration file in the service user's
31528 %appdata% directory. (We can't do the 'hardwire the user's appdata
31529 directory' trick any more, since we may not have read access to that
31532 o Major bugfixes (other):
31533 - Previously, we would cache up to 16 old networkstatus documents
31534 indefinitely, if they came from nontrusted authorities. Now we
31535 discard them if they are more than 10 days old.
31536 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
31538 - Detect and reject malformed DNS responses containing circular
31540 - If exits are rare enough that we're not marking exits as guards,
31541 ignore exit bandwidth when we're deciding the required bandwidth
31543 - When we're handling a directory connection tunneled over Tor,
31544 don't fill up internal memory buffers with all the data we want
31545 to tunnel; instead, only add it if the OR connection that will
31546 eventually receive it has some room for it. (This can lead to
31547 slowdowns in tunneled dir connections; a better solution will have
31548 to wait for 0.2.0.)
31550 o Minor bugfixes (dns):
31551 - Add some defensive programming to eventdns.c in an attempt to catch
31552 possible memory-stomping bugs.
31553 - Detect and reject DNS replies containing IPv4 or IPv6 records with
31554 an incorrect number of bytes. (Previously, we would ignore the
31556 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
31557 in the correct order, and doesn't crash.
31558 - Free memory held in recently-completed DNS lookup attempts on exit.
31559 This was not a memory leak, but may have been hiding memory leaks.
31560 - Handle TTL values correctly on reverse DNS lookups.
31561 - Treat failure to parse resolv.conf as an error.
31563 o Minor bugfixes (other):
31564 - Fix crash with "tor --list-fingerprint" (reported by seeess).
31565 - When computing clock skew from directory HTTP headers, consider what
31566 time it was when we finished asking for the directory, not what
31568 - Expire socks connections if they spend too long waiting for the
31569 handshake to finish. Previously we would let them sit around for
31570 days, if the connecting application didn't close them either.
31571 - And if the socks handshake hasn't started, don't send a
31572 "DNS resolve socks failed" handshake reply; just close it.
31573 - Stop using C functions that OpenBSD's linker doesn't like.
31574 - Don't launch requests for descriptors unless we have networkstatuses
31575 from at least half of the authorities. This delays the first
31576 download slightly under pathological circumstances, but can prevent
31577 us from downloading a bunch of descriptors we don't need.
31578 - Do not log IPs with TLS failures for incoming TLS
31579 connections. (Fixes bug 382.)
31580 - If the user asks to use invalid exit nodes, be willing to use
31582 - Stop using the reserved ac_cv namespace in our configure script.
31583 - Call stat() slightly less often; use fstat() when possible.
31584 - Refactor the way we handle pending circuits when an OR connection
31585 completes or fails, in an attempt to fix a rare crash bug.
31586 - Only rewrite a conn's address based on X-Forwarded-For: headers
31587 if it's a parseable public IP address; and stop adding extra quotes
31588 to the resulting address.
31591 - Weight directory requests by advertised bandwidth. Now we can
31592 let servers enable write limiting but still allow most clients to
31593 succeed at their directory requests. (We still ignore weights when
31594 choosing a directory authority; I hope this is a feature.)
31597 - Create a new file ReleaseNotes which was the old ChangeLog. The
31598 new ChangeLog file now includes the summaries for all development
31600 - Check for addresses with invalid characters at the exit as well
31601 as at the client, and warn less verbosely when they fail. You can
31602 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
31603 - Adapt a patch from goodell to let the contrib/exitlist script
31604 take arguments rather than require direct editing.
31605 - Inform the server operator when we decide not to advertise a
31606 DirPort due to AccountingMax enabled or a low BandwidthRate. It
31607 was confusing Zax, so now we're hopefully more helpful.
31608 - Bring us one step closer to being able to establish an encrypted
31609 directory tunnel without knowing a descriptor first. Still not
31610 ready yet. As part of the change, now assume we can use a
31611 create_fast cell if we don't know anything about a router.
31612 - Allow exit nodes to use nameservers running on ports other than 53.
31613 - Servers now cache reverse DNS replies.
31614 - Add an --ignore-missing-torrc command-line option so that we can
31615 get the "use sensible defaults if the configuration file doesn't
31616 exist" behavior even when specifying a torrc location on the command
31619 o Minor features (controller):
31620 - Track reasons for OR connection failure; make these reasons
31621 available via the controller interface. (Patch from Mike Perry.)
31622 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
31623 can learn when clients are sending malformed hostnames to Tor.
31624 - Clean up documentation for controller status events.
31625 - Add a REMAP status to stream events to note that a stream's
31626 address has changed because of a cached address or a MapAddress
31630 Changes in version 0.1.2.6-alpha - 2007-01-09
31632 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
31633 connection handles more than 4 gigs in either direction, we crash.
31634 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
31635 advertised exit node, somebody might try to exit from us when
31636 we're bootstrapping and before we've built our descriptor yet.
31637 Refuse the connection rather than crashing.
31640 - Warn if we (as a server) find that we've resolved an address that we
31641 weren't planning to resolve.
31642 - Warn that using select() on any libevent version before 1.1 will be
31643 unnecessarily slow (even for select()).
31644 - Flush ERR-level controller status events just like we currently
31645 flush ERR-level log events, so that a Tor shutdown doesn't prevent
31646 the controller from learning about current events.
31648 o Minor features (more controller status events):
31649 - Implement EXTERNAL_ADDRESS server status event so controllers can
31650 learn when our address changes.
31651 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
31652 can learn when directories reject our descriptor.
31653 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
31654 can learn when a client application is speaking a non-socks protocol
31656 - Implement DANGEROUS_SOCKS client status event so controllers
31657 can learn when a client application is leaking DNS addresses.
31658 - Implement BUG general status event so controllers can learn when
31659 Tor is unhappy about its internal invariants.
31660 - Implement CLOCK_SKEW general status event so controllers can learn
31661 when Tor thinks the system clock is set incorrectly.
31662 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
31663 server status events so controllers can learn when their descriptors
31664 are accepted by a directory.
31665 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
31666 server status events so controllers can learn about Tor's progress in
31667 deciding whether it's reachable from the outside.
31668 - Implement BAD_LIBEVENT general status event so controllers can learn
31669 when we have a version/method combination in libevent that needs to
31671 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
31672 and DNS_USELESS server status events so controllers can learn
31673 about changes to DNS server status.
31675 o Minor features (directory):
31676 - Authorities no longer recommend exits as guards if this would shift
31677 too much load to the exit nodes.
31680 Changes in version 0.1.2.5-alpha - 2007-01-06
31682 - Enable write limiting as well as read limiting. Now we sacrifice
31683 capacity if we're pushing out lots of directory traffic, rather
31684 than overrunning the user's intended bandwidth limits.
31685 - Include TLS overhead when counting bandwidth usage; previously, we
31686 would count only the bytes sent over TLS, but not the bytes used
31688 - Support running the Tor service with a torrc not in the same
31689 directory as tor.exe and default to using the torrc located in
31690 the %appdata%\Tor\ of the user who installed the service. Patch
31692 - Servers now check for the case when common DNS requests are going to
31693 wildcarded addresses (i.e. all getting the same answer), and change
31694 their exit policy to reject *:* if it's happening.
31695 - Implement BEGIN_DIR cells, so we can connect to the directory
31696 server via TLS to do encrypted directory requests rather than
31697 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
31698 config options if you like.
31700 o Minor features (config and docs):
31701 - Start using the state file to store bandwidth accounting data:
31702 the bw_accounting file is now obsolete. We'll keep generating it
31703 for a while for people who are still using 0.1.2.4-alpha.
31704 - Try to batch changes to the state file so that we do as few
31705 disk writes as possible while still storing important things in
31707 - The state file and the bw_accounting file get saved less often when
31708 the AvoidDiskWrites config option is set.
31709 - Make PIDFile work on Windows (untested).
31710 - Add internal descriptions for a bunch of configuration options:
31711 accessible via controller interface and in comments in saved
31713 - Reject *:563 (NNTPS) in the default exit policy. We already reject
31714 NNTP by default, so this seems like a sensible addition.
31715 - Clients now reject hostnames with invalid characters. This should
31716 avoid some inadvertent info leaks. Add an option
31717 AllowNonRFC953Hostnames to disable this behavior, in case somebody
31718 is running a private network with hosts called @, !, and #.
31719 - Add a maintainer script to tell us which options are missing
31720 documentation: "make check-docs".
31721 - Add a new address-spec.txt document to describe our special-case
31722 addresses: .exit, .onion, and .noconnnect.
31724 o Minor features (DNS):
31725 - Ongoing work on eventdns infrastructure: now it has dns server
31726 and ipv6 support. One day Tor will make use of it.
31727 - Add client-side caching for reverse DNS lookups.
31728 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
31729 - When we change nameservers or IP addresses, reset and re-launch
31730 our tests for DNS hijacking.
31732 o Minor features (directory):
31733 - Authorities now specify server versions in networkstatus. This adds
31734 about 2% to the size of compressed networkstatus docs, and allows
31735 clients to tell which servers support BEGIN_DIR and which don't.
31736 The implementation is forward-compatible with a proposed future
31737 protocol version scheme not tied to Tor versions.
31738 - DirServer configuration lines now have an orport= option so
31739 clients can open encrypted tunnels to the authorities without
31740 having downloaded their descriptors yet. Enabled for moria1,
31741 moria2, tor26, and lefkada now in the default configuration.
31742 - Directory servers are more willing to send a 503 "busy" if they
31743 are near their write limit, especially for v1 directory requests.
31744 Now they can use their limited bandwidth for actual Tor traffic.
31745 - Clients track responses with status 503 from dirservers. After a
31746 dirserver has given us a 503, we try not to use it until an hour has
31747 gone by, or until we have no dirservers that haven't given us a 503.
31748 - When we get a 503 from a directory, and we're not a server, we don't
31749 count the failure against the total number of failures allowed
31750 for the thing we're trying to download.
31751 - Report X-Your-Address-Is correctly from tunneled directory
31752 connections; don't report X-Your-Address-Is when it's an internal
31753 address; and never believe reported remote addresses when they're
31755 - Protect against an unlikely DoS attack on directory servers.
31756 - Add a BadDirectory flag to network status docs so that authorities
31757 can (eventually) tell clients about caches they believe to be
31760 o Minor features (controller):
31761 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
31762 - Reimplement GETINFO so that info/names stays in sync with the
31764 - Implement "GETINFO fingerprint".
31765 - Implement "SETEVENTS GUARD" so controllers can get updates on
31766 entry guard status as it changes.
31768 o Minor features (clean up obsolete pieces):
31769 - Remove some options that have been deprecated since at least
31770 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
31771 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
31772 to set log options.
31773 - We no longer look for identity and onion keys in "identity.key" and
31774 "onion.key" -- these were replaced by secret_id_key and
31775 secret_onion_key in 0.0.8pre1.
31776 - We no longer require unrecognized directory entries to be
31779 o Major bugfixes (security):
31780 - Stop sending the HttpProxyAuthenticator string to directory
31781 servers when directory connections are tunnelled through Tor.
31782 - Clients no longer store bandwidth history in the state file.
31783 - Do not log introduction points for hidden services if SafeLogging
31785 - When generating bandwidth history, round down to the nearest
31786 1k. When storing accounting data, round up to the nearest 1k.
31787 - When we're running as a server, remember when we last rotated onion
31788 keys, so that we will rotate keys once they're a week old even if
31789 we never stay up for a week ourselves.
31791 o Major bugfixes (other):
31792 - Fix a longstanding bug in eventdns that prevented the count of
31793 timed-out resolves from ever being reset. This bug caused us to
31794 give up on a nameserver the third time it timed out, and try it
31795 10 seconds later... and to give up on it every time it timed out
31797 - Take out the '5 second' timeout from the connection retry
31798 schedule. Now the first connect attempt will wait a full 10
31799 seconds before switching to a new circuit. Perhaps this will help
31800 a lot. Based on observations from Mike Perry.
31801 - Fix a bug on the Windows implementation of tor_mmap_file() that
31802 would prevent the cached-routers file from ever loading. Reported
31806 - Fix an assert failure when a directory authority sets
31807 AuthDirRejectUnlisted and then receives a descriptor from an
31808 unlisted router. Reported by seeess.
31809 - Avoid a double-free when parsing malformed DirServer lines.
31810 - Fix a bug when a BSD-style PF socket is first used. Patch from
31812 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
31813 to resolve an address at a given exit node even when they ask for
31815 - Servers no longer ever list themselves in their "family" line,
31816 even if configured to do so. This makes it easier to configure
31817 family lists conveniently.
31818 - When running as a server, don't fall back to 127.0.0.1 when no
31819 nameservers are configured in /etc/resolv.conf; instead, make the
31820 user fix resolv.conf or specify nameservers explicitly. (Resolves
31822 - Stop accepting certain malformed ports in configured exit policies.
31823 - Don't re-write the fingerprint file every restart, unless it has
31825 - Stop warning when a single nameserver fails: only warn when _all_ of
31826 our nameservers have failed. Also, when we only have one nameserver,
31827 raise the threshold for deciding that the nameserver is dead.
31828 - Directory authorities now only decide that routers are reachable
31829 if their identity keys are as expected.
31830 - When the user uses bad syntax in the Log config line, stop
31831 suggesting other bad syntax as a replacement.
31832 - Correctly detect ipv6 DNS capability on OpenBSD.
31834 o Minor bugfixes (controller):
31835 - Report the circuit number correctly in STREAM CLOSED events. Bug
31836 reported by Mike Perry.
31837 - Do not report bizarre values for results of accounting GETINFOs
31838 when the last second's write or read exceeds the allotted bandwidth.
31839 - Report "unrecognized key" rather than an empty string when the
31840 controller tries to fetch a networkstatus that doesn't exist.
31843 Changes in version 0.1.1.26 - 2006-12-14
31844 o Security bugfixes:
31845 - Stop sending the HttpProxyAuthenticator string to directory
31846 servers when directory connections are tunnelled through Tor.
31847 - Clients no longer store bandwidth history in the state file.
31848 - Do not log introduction points for hidden services if SafeLogging
31852 - Fix an assert failure when a directory authority sets
31853 AuthDirRejectUnlisted and then receives a descriptor from an
31854 unlisted router (reported by seeess).
31857 Changes in version 0.1.2.4-alpha - 2006-12-03
31859 - Add support for using natd; this allows FreeBSDs earlier than
31860 5.1.2 to have ipfw send connections through Tor without using
31861 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
31864 - Make all connections to addresses of the form ".noconnect"
31865 immediately get closed. This lets application/controller combos
31866 successfully test whether they're talking to the same Tor by
31867 watching for STREAM events.
31868 - Make cross.sh cross-compilation script work even when autogen.sh
31869 hasn't been run. (Patch from Michael Mohr.)
31870 - Statistics dumped by -USR2 now include a breakdown of public key
31871 operations, for profiling.
31874 - Fix a major leak when directory authorities parse their
31875 approved-routers list, a minor memory leak when we fail to pick
31876 an exit node, and a few rare leaks on errors.
31877 - Handle TransPort connections even when the server sends data before
31878 the client sends data. Previously, the connection would just hang
31879 until the client sent data. (Patch from tup based on patch from
31881 - Avoid assert failure when our cached-routers file is empty on
31885 - Don't log spurious warnings when we see a circuit close reason we
31886 don't recognize; it's probably just from a newer version of Tor.
31887 - Have directory authorities allow larger amounts of drift in uptime
31888 without replacing the server descriptor: previously, a server that
31889 restarted every 30 minutes could have 48 "interesting" descriptors
31891 - Start linking to the Tor specification and Tor reference manual
31892 correctly in the Windows installer.
31893 - Add Vidalia to the OS X uninstaller script, so when we uninstall
31894 Tor/Privoxy we also uninstall Vidalia.
31895 - Resume building on Irix64, and fix a lot of warnings from its
31896 MIPSpro C compiler.
31897 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
31898 when we're running as a client.
31901 Changes in version 0.1.1.25 - 2006-11-04
31903 - When a client asks us to resolve (rather than connect to)
31904 an address, and we have a cached answer, give them the cached
31905 answer. Previously, we would give them no answer at all.
31906 - We were building exactly the wrong circuits when we predict
31907 hidden service requirements, meaning Tor would have to build all
31908 its circuits on demand.
31909 - If none of our live entry guards have a high uptime, but we
31910 require a guard with a high uptime, try adding a new guard before
31911 we give up on the requirement. This patch should make long-lived
31912 connections more stable on average.
31913 - When testing reachability of our DirPort, don't launch new
31914 tests when there's already one in progress -- unreachable
31915 servers were stacking up dozens of testing streams.
31917 o Security bugfixes:
31918 - When the user sends a NEWNYM signal, clear the client-side DNS
31919 cache too. Otherwise we continue to act on previous information.
31922 - Avoid a memory corruption bug when creating a hash table for
31924 - Avoid possibility of controller-triggered crash when misusing
31925 certain commands from a v0 controller on platforms that do not
31926 handle printf("%s",NULL) gracefully.
31927 - Avoid infinite loop on unexpected controller input.
31928 - Don't log spurious warnings when we see a circuit close reason we
31929 don't recognize; it's probably just from a newer version of Tor.
31930 - Add Vidalia to the OS X uninstaller script, so when we uninstall
31931 Tor/Privoxy we also uninstall Vidalia.
31934 Changes in version 0.1.2.3-alpha - 2006-10-29
31936 - Prepare for servers to publish descriptors less often: never
31937 discard a descriptor simply for being too old until either it is
31938 recommended by no authorities, or until we get a better one for
31939 the same router. Make caches consider retaining old recommended
31940 routers for even longer.
31941 - If most authorities set a BadExit flag for a server, clients
31942 don't think of it as a general-purpose exit. Clients only consider
31943 authorities that advertise themselves as listing bad exits.
31944 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
31945 headers for content, so that we can work better in the presence of
31946 caching HTTP proxies.
31947 - Allow authorities to list nodes as bad exits by fingerprint or by
31950 o Minor features, controller:
31951 - Add a REASON field to CIRC events; for backward compatibility, this
31952 field is sent only to controllers that have enabled the extended
31953 event format. Also, add additional reason codes to explain why
31954 a given circuit has been destroyed or truncated. (Patches from
31956 - Add a REMOTE_REASON field to extended CIRC events to tell the
31957 controller about why a remote OR told us to close a circuit.
31958 - Stream events also now have REASON and REMOTE_REASON fields,
31959 working much like those for circuit events.
31960 - There's now a GETINFO ns/... field so that controllers can ask Tor
31961 about the current status of a router.
31962 - A new event type "NS" to inform a controller when our opinion of
31963 a router's status has changed.
31964 - Add a GETINFO events/names and GETINFO features/names so controllers
31965 can tell which events and features are supported.
31966 - A new CLEARDNSCACHE signal to allow controllers to clear the
31967 client-side DNS cache without expiring circuits.
31969 o Security bugfixes:
31970 - When the user sends a NEWNYM signal, clear the client-side DNS
31971 cache too. Otherwise we continue to act on previous information.
31974 - Avoid sending junk to controllers or segfaulting when a controller
31975 uses EVENT_NEW_DESC with verbose nicknames.
31976 - Stop triggering asserts if the controller tries to extend hidden
31977 service circuits (reported by mwenge).
31978 - Avoid infinite loop on unexpected controller input.
31979 - When the controller does a "GETINFO network-status", tell it
31980 about even those routers whose descriptors are very old, and use
31981 long nicknames where appropriate.
31982 - Change NT service functions to be loaded on demand. This lets us
31983 build with MinGW without breaking Tor for Windows 98 users.
31984 - Do DirPort reachability tests less often, since a single test
31985 chews through many circuits before giving up.
31986 - In the hidden service example in torrc.sample, stop recommending
31987 esoteric and discouraged hidden service options.
31988 - When stopping an NT service, wait up to 10 sec for it to actually
31989 stop. Patch from Matt Edman; resolves bug 295.
31990 - Fix handling of verbose nicknames with ORCONN controller events:
31991 make them show up exactly when requested, rather than exactly when
31993 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
31994 printing a duplicate "$" in the keys we send (reported by mwenge).
31995 - Correctly set maximum connection limit on Cygwin. (This time
31997 - Try to detect Windows correctly when cross-compiling.
31998 - Detect the size of the routers file correctly even if it is
31999 corrupted (on systems without mmap) or not page-aligned (on systems
32000 with mmap). This bug was harmless.
32001 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
32002 to open a stream fails; now we do in more cases. This should
32003 make clients able to find a good exit faster in some cases, since
32004 unhandleable requests will now get an error rather than timing out.
32005 - Resolve two memory leaks when rebuilding the on-disk router cache
32006 (reported by fookoowa).
32007 - Clean up minor code warnings suggested by the MIPSpro C compiler,
32008 and reported by some Centos users.
32009 - Controller signals now work on non-Unix platforms that don't define
32010 SIGUSR1 and SIGUSR2 the way we expect.
32011 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
32012 values before failing, and always enables eventdns.
32013 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
32014 Try to fix this in configure.in by checking for most functions
32015 before we check for libevent.
32018 Changes in version 0.1.2.2-alpha - 2006-10-07
32020 - Make our async eventdns library on-by-default for Tor servers,
32021 and plan to deprecate the separate dnsworker threads.
32022 - Add server-side support for "reverse" DNS lookups (using PTR
32023 records so clients can determine the canonical hostname for a given
32024 IPv4 address). Only supported by servers using eventdns; servers
32025 now announce in their descriptors whether they support eventdns.
32026 - Specify and implement client-side SOCKS5 interface for reverse DNS
32027 lookups (see doc/socks-extensions.txt).
32028 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
32029 connect to directory servers through Tor. Previously, clients needed
32030 to find Tor exits to make private connections to directory servers.
32031 - Avoid choosing Exit nodes for entry or middle hops when the
32032 total bandwidth available from non-Exit nodes is much higher than
32033 the total bandwidth available from Exit nodes.
32034 - Workaround for name servers (like Earthlink's) that hijack failing
32035 DNS requests and replace the no-such-server answer with a "helpful"
32036 redirect to an advertising-driven search portal. Also work around
32037 DNS hijackers who "helpfully" decline to hijack known-invalid
32038 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
32039 lets you turn it off.
32040 - Send out a burst of long-range padding cells once we've established
32041 that we're reachable. Spread them over 4 circuits, so hopefully
32042 a few will be fast. This exercises our bandwidth and bootstraps
32043 us into the directory more quickly.
32045 o New/improved config options:
32046 - Add new config option "ResolvConf" to let the server operator
32047 choose an alternate resolve.conf file when using eventdns.
32048 - Add an "EnforceDistinctSubnets" option to control our "exclude
32049 servers on the same /16" behavior. It's still on by default; this
32050 is mostly for people who want to operate private test networks with
32051 all the machines on the same subnet.
32052 - If one of our entry guards is on the ExcludeNodes list, or the
32053 directory authorities don't think it's a good guard, treat it as
32054 if it were unlisted: stop using it as a guard, and throw it off
32055 the guards list if it stays that way for a long time.
32056 - Allow directory authorities to be marked separately as authorities
32057 for the v1 directory protocol, the v2 directory protocol, and
32058 as hidden service directories, to make it easier to retire old
32059 authorities. V1 authorities should set "HSAuthoritativeDir 1"
32060 to continue being hidden service authorities too.
32061 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
32063 o Minor features, controller:
32064 - Fix CIRC controller events so that controllers can learn the
32065 identity digests of non-Named servers used in circuit paths.
32066 - Let controllers ask for more useful identifiers for servers. Instead
32067 of learning identity digests for un-Named servers and nicknames
32068 for Named servers, the new identifiers include digest, nickname,
32069 and indication of Named status. Off by default; see control-spec.txt
32070 for more information.
32071 - Add a "getinfo address" controller command so it can display Tor's
32072 best guess to the user.
32073 - New controller event to alert the controller when our server
32074 descriptor has changed.
32075 - Give more meaningful errors on controller authentication failure.
32077 o Minor features, other:
32078 - When asked to resolve a hostname, don't use non-exit servers unless
32079 requested to do so. This allows servers with broken DNS to be
32080 useful to the network.
32081 - Divide eventdns log messages into warn and info messages.
32082 - Reserve the nickname "Unnamed" for routers that can't pick
32083 a hostname: any router can call itself Unnamed; directory
32084 authorities will never allocate Unnamed to any particular router;
32085 clients won't believe that any router is the canonical Unnamed.
32086 - Only include function names in log messages for info/debug messages.
32087 For notice/warn/err, the content of the message should be clear on
32088 its own, and printing the function name only confuses users.
32089 - Avoid some false positives during reachability testing: don't try
32090 to test via a server that's on the same /24 as us.
32091 - If we fail to build a circuit to an intended enclave, and it's
32092 not mandatory that we use that enclave, stop wanting it.
32093 - When eventdns is enabled, allow multithreaded builds on NetBSD and
32094 OpenBSD. (We had previously disabled threads on these platforms
32095 because they didn't have working thread-safe resolver functions.)
32097 o Major bugfixes, anonymity/security:
32098 - If a client asked for a server by name, and there's a named server
32099 in our network-status but we don't have its descriptor yet, we
32100 could return an unnamed server instead.
32101 - Fix NetBSD bug that could allow someone to force uninitialized RAM
32102 to be sent to a server's DNS resolver. This only affects NetBSD
32103 and other platforms that do not bounds-check tolower().
32104 - Reject (most) attempts to use Tor circuits with length one. (If
32105 many people start using Tor as a one-hop proxy, exit nodes become
32106 a more attractive target for compromise.)
32107 - Just because your DirPort is open doesn't mean people should be
32108 able to remotely teach you about hidden service descriptors. Now
32109 only accept rendezvous posts if you've got HSAuthoritativeDir set.
32111 o Major bugfixes, other:
32112 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
32113 - When a client asks the server to resolve (not connect to)
32114 an address, and it has a cached answer, give them the cached answer.
32115 Previously, the server would give them no answer at all.
32116 - Allow really slow clients to not hang up five minutes into their
32117 directory downloads (suggested by Adam J. Richter).
32118 - We were building exactly the wrong circuits when we anticipated
32119 hidden service requirements, meaning Tor would have to build all
32120 its circuits on demand.
32121 - Avoid crashing when we mmap a router cache file of size 0.
32122 - When testing reachability of our DirPort, don't launch new
32123 tests when there's already one in progress -- unreachable
32124 servers were stacking up dozens of testing streams.
32126 o Minor bugfixes, correctness:
32127 - If we're a directory mirror and we ask for "all" network status
32128 documents, we would discard status documents from authorities
32129 we don't recognize.
32130 - Avoid a memory corruption bug when creating a hash table for
32132 - Avoid controller-triggered crash when misusing certain commands
32133 from a v0 controller on platforms that do not handle
32134 printf("%s",NULL) gracefully.
32135 - Don't crash when a controller sends a third argument to an
32136 "extendcircuit" request.
32137 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
32138 response; fix error code when "getinfo dir/status/" fails.
32139 - Avoid crash when telling controller stream-status and a stream
32141 - Patch from Adam Langley to fix assert() in eventdns.c.
32142 - Fix a debug log message in eventdns to say "X resolved to Y"
32143 instead of "X resolved to X".
32144 - Make eventdns give strings for DNS errors, not just error numbers.
32145 - Track unreachable entry guards correctly: don't conflate
32146 'unreachable by us right now' with 'listed as down by the directory
32147 authorities'. With the old code, if a guard was unreachable by
32148 us but listed as running, it would clog our guard list forever.
32149 - Behave correctly in case we ever have a network with more than
32150 2GB/s total advertised capacity.
32151 - Make TrackExitHosts case-insensitive, and fix the behavior of
32152 ".suffix" TrackExitHosts items to avoid matching in the middle of
32154 - Finally fix the openssl warnings from newer gccs that believe that
32155 ignoring a return value is okay, but casting a return value and
32156 then ignoring it is a sign of madness.
32157 - Prevent the contrib/exitlist script from printing the same
32158 result more than once.
32159 - Patch from Steve Hildrey: Generate network status correctly on
32160 non-versioning dirservers.
32161 - Don't listen to the X-Your-Address-Is hint if you did the lookup
32162 via Tor; otherwise you'll think you're the exit node's IP address.
32164 o Minor bugfixes, performance:
32165 - Two small performance improvements on parsing descriptors.
32166 - Major performance improvement on inserting descriptors: change
32167 algorithm from O(n^2) to O(n).
32168 - Make the common memory allocation path faster on machines where
32169 malloc(0) returns a pointer.
32170 - Start remembering X-Your-Address-Is directory hints even if you're
32171 a client, so you can become a server more smoothly.
32172 - Avoid duplicate entries on MyFamily line in server descriptor.
32174 o Packaging, features:
32175 - Remove architecture from OS X builds. The official builds are
32176 now universal binaries.
32177 - The Debian package now uses --verify-config when (re)starting,
32178 to distinguish configuration errors from other errors.
32179 - Update RPMs to require libevent 1.1b.
32181 o Packaging, bugfixes:
32182 - Patches so Tor builds with MinGW on Windows.
32183 - Patches so Tor might run on Cygwin again.
32184 - Resume building on non-gcc compilers and ancient gcc. Resume
32185 building with the -O0 compile flag. Resume building cleanly on
32187 - Run correctly on OS X platforms with case-sensitive filesystems.
32188 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
32189 - Add autoconf checks so Tor can build on Solaris x86 again.
32192 - Documented (and renamed) ServerDNSSearchDomains and
32193 ServerDNSResolvConfFile options.
32194 - Be clearer that the *ListenAddress directives can be repeated
32198 Changes in version 0.1.1.24 - 2006-09-29
32200 - Allow really slow clients to not hang up five minutes into their
32201 directory downloads (suggested by Adam J. Richter).
32202 - Fix major performance regression from 0.1.0.x: instead of checking
32203 whether we have enough directory information every time we want to
32204 do something, only check when the directory information has changed.
32205 This should improve client CPU usage by 25-50%.
32206 - Don't crash if, after a server has been running for a while,
32207 it can't resolve its hostname.
32210 - Allow Tor to start when RunAsDaemon is set but no logs are set.
32211 - Don't crash when the controller receives a third argument to an
32212 "extendcircuit" request.
32213 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
32214 response; fix error code when "getinfo dir/status/" fails.
32215 - Fix configure.in to not produce broken configure files with
32216 more recent versions of autoconf. Thanks to Clint for his auto*
32218 - Fix security bug on NetBSD that could allow someone to force
32219 uninitialized RAM to be sent to a server's DNS resolver. This
32220 only affects NetBSD and other platforms that do not bounds-check
32222 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
32223 methods: these are known to be buggy.
32224 - If we're a directory mirror and we ask for "all" network status
32225 documents, we would discard status documents from authorities
32226 we don't recognize.
32229 Changes in version 0.1.2.1-alpha - 2006-08-27
32231 - Add "eventdns" async dns library from Adam Langley, tweaked to
32232 build on OSX and Windows. Only enabled if you pass the
32233 --enable-eventdns argument to configure.
32234 - Allow servers with no hostname or IP address to learn their
32235 IP address by asking the directory authorities. This code only
32236 kicks in when you would normally have exited with a "no address"
32237 error. Nothing's authenticated, so use with care.
32238 - Rather than waiting a fixed amount of time between retrying
32239 application connections, we wait only 5 seconds for the first,
32240 10 seconds for the second, and 15 seconds for each retry after
32241 that. Hopefully this will improve the expected user experience.
32242 - Patch from Tup to add support for transparent AP connections:
32243 this basically bundles the functionality of trans-proxy-tor
32244 into the Tor mainline. Now hosts with compliant pf/netfilter
32245 implementations can redirect TCP connections straight to Tor
32246 without diverting through SOCKS. Needs docs.
32247 - Busy directory servers save lots of memory by spooling server
32248 descriptors, v1 directories, and v2 networkstatus docs to buffers
32249 as needed rather than en masse. Also mmap the cached-routers
32250 files, so we don't need to keep the whole thing in memory too.
32251 - Automatically avoid picking more than one node from the same
32252 /16 network when constructing a circuit.
32253 - Revise and clean up the torrc.sample that we ship with; add
32254 a section for BandwidthRate and BandwidthBurst.
32257 - Split circuit_t into origin_circuit_t and or_circuit_t, and
32258 split connection_t into edge, or, dir, control, and base structs.
32259 These will save quite a bit of memory on busy servers, and they'll
32260 also help us track down bugs in the code and bugs in the spec.
32261 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
32262 or later. Log when we are doing this, so we can diagnose it when
32263 it fails. (Also, recommend libevent 1.1b for kqueue and
32264 win32 methods; deprecate libevent 1.0b harder; make libevent
32265 recommendation system saner.)
32266 - Start being able to build universal binaries on OS X (thanks
32268 - Export the default exit policy via the control port, so controllers
32269 don't need to guess what it is / will be later.
32270 - Add a man page entry for ProtocolWarnings.
32271 - Add TestVia config option to the man page.
32272 - Remove even more protocol-related warnings from Tor server logs,
32273 such as bad TLS handshakes and malformed begin cells.
32274 - Stop fetching descriptors if you're not a dir mirror and you
32275 haven't tried to establish any circuits lately. [This currently
32276 causes some dangerous behavior, because when you start up again
32277 you'll use your ancient server descriptors.]
32278 - New DirPort behavior: if you have your dirport set, you download
32279 descriptors aggressively like a directory mirror, whether or not
32280 your ORPort is set.
32281 - Get rid of the router_retry_connections notion. Now routers
32282 no longer try to rebuild long-term connections to directory
32283 authorities, and directory authorities no longer try to rebuild
32284 long-term connections to all servers. We still don't hang up
32285 connections in these two cases though -- we need to look at it
32286 more carefully to avoid flapping, and we likely need to wait til
32287 0.1.1.x is obsolete.
32288 - Drop compatibility with obsolete Tors that permit create cells
32289 to have the wrong circ_id_type.
32290 - Re-enable per-connection rate limiting. Get rid of the "OP
32291 bandwidth" concept. Lay groundwork for "bandwidth classes" --
32292 separate global buckets that apply depending on what sort of conn
32294 - Start publishing one minute or so after we find our ORPort
32295 to be reachable. This will help reduce the number of descriptors
32296 we have for ourselves floating around, since it's quite likely
32297 other things (e.g. DirPort) will change during that minute too.
32298 - Fork the v1 directory protocol into its own spec document,
32299 and mark dir-spec.txt as the currently correct (v2) spec.
32302 - When we find our DirPort to be reachable, publish a new descriptor
32303 so we'll tell the world (reported by pnx).
32304 - Publish a new descriptor after we hup/reload. This is important
32305 if our config has changed such that we'll want to start advertising
32306 our DirPort now, etc.
32307 - Allow Tor to start when RunAsDaemon is set but no logs are set.
32308 - When we have a state file we cannot parse, tell the user and
32309 move it aside. Now we avoid situations where the user starts
32310 Tor in 1904, Tor writes a state file with that timestamp in it,
32311 the user fixes her clock, and Tor refuses to start.
32312 - Fix configure.in to not produce broken configure files with
32313 more recent versions of autoconf. Thanks to Clint for his auto*
32315 - "tor --verify-config" now exits with -1(255) or 0 depending on
32316 whether the config options are bad or good.
32317 - Resolve bug 321 when using dnsworkers: append a period to every
32318 address we resolve at the exit node, so that we do not accidentally
32319 pick up local addresses, and so that failing searches are retried
32320 in the resolver search domains. (This is already solved for
32321 eventdns.) (This breaks Blossom servers for now.)
32322 - If we are using an exit enclave and we can't connect, e.g. because
32323 its webserver is misconfigured to not listen on localhost, then
32324 back off and try connecting from somewhere else before we fail.
32327 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
32328 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
32329 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
32330 when the IP address is mapped through MapAddress to a hostname.
32331 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
32332 useless IPv6 DNS resolves.
32333 - Patch suggested by Karsten Loesing: respond to SIGNAL command
32334 before we execute the signal, in case the signal shuts us down.
32335 - Clean up AllowInvalidNodes man page entry.
32336 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
32337 - Add more asserts to track down an assert error on a windows Tor
32338 server with connection_add being called with socket == -1.
32339 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
32340 - Fix misleading log messages: an entry guard that is "unlisted",
32341 as well as not known to be "down" (because we've never heard
32342 of it), is not therefore "up".
32343 - Remove code to special-case "-cvs" ending, since it has not
32344 actually mattered since 0.0.9.
32345 - Make our socks5 handling more robust to broken socks clients:
32346 throw out everything waiting on the buffer in between socks
32347 handshake phases, since they can't possibly (so the theory
32348 goes) have predicted what we plan to respond to them.
32351 Changes in version 0.1.1.23 - 2006-07-30
32353 - Fast Tor servers, especially exit nodes, were triggering asserts
32354 due to a bug in handling the list of pending DNS resolves. Some
32355 bugs still remain here; we're hunting them.
32356 - Entry guards could crash clients by sending unexpected input.
32357 - More fixes on reachability testing: if you find yourself reachable,
32358 then don't ever make any client requests (so you stop predicting
32359 circuits), then hup or have your clock jump, then later your IP
32360 changes, you won't think circuits are working, so you won't try to
32361 test reachability, so you won't publish.
32364 - Avoid a crash if the controller does a resetconf firewallports
32365 and then a setconf fascistfirewall=1.
32366 - Avoid an integer underflow when the dir authority decides whether
32367 a router is stable: we might wrongly label it stable, and compute
32368 a slightly wrong median stability, when a descriptor is published
32370 - Fix a place where we might trigger an assert if we can't build our
32371 own server descriptor yet.
32374 Changes in version 0.1.1.22 - 2006-07-05
32376 - Fix a big bug that was causing servers to not find themselves
32377 reachable if they changed IP addresses. Since only 0.1.1.22+
32378 servers can do reachability testing correctly, now we automatically
32379 make sure to test via one of these.
32380 - Fix to allow clients and mirrors to learn directory info from
32381 descriptor downloads that get cut off partway through.
32382 - Directory authorities had a bug in deciding if a newly published
32383 descriptor was novel enough to make everybody want a copy -- a few
32384 servers seem to be publishing new descriptors many times a minute.
32386 - Fix a rare bug that was causing some servers to complain about
32387 "closing wedged cpuworkers" and skip some circuit create requests.
32388 - Make the Exit flag in directory status documents actually work.
32391 Changes in version 0.1.1.21 - 2006-06-10
32392 o Crash and assert fixes from 0.1.1.20:
32393 - Fix a rare crash on Tor servers that have enabled hibernation.
32394 - Fix a seg fault on startup for Tor networks that use only one
32395 directory authority.
32396 - Fix an assert from a race condition that occurs on Tor servers
32397 while exiting, where various threads are trying to log that they're
32398 exiting, and delete the logs, at the same time.
32399 - Make our unit tests pass again on certain obscure platforms.
32402 - Add support for building SUSE RPM packages.
32403 - Speed up initial bootstrapping for clients: if we are making our
32404 first ever connection to any entry guard, then don't mark it down
32406 - When only one Tor server in the network is labelled as a guard,
32407 and we've already picked him, we would cycle endlessly picking him
32408 again, being unhappy about it, etc. Now we specifically exclude
32409 current guards when picking a new guard.
32410 - Servers send create cells more reliably after the TLS connection
32411 is established: we were sometimes forgetting to send half of them
32412 when we had more than one pending.
32413 - If we get a create cell that asks us to extend somewhere, but the
32414 Tor server there doesn't match the expected digest, we now send
32415 a destroy cell back, rather than silently doing nothing.
32416 - Make options->RedirectExit work again.
32417 - Make cookie authentication for the controller work again.
32418 - Stop being picky about unusual characters in the arguments to
32419 mapaddress. It's none of our business.
32420 - Add a new config option "TestVia" that lets you specify preferred
32421 middle hops to use for test circuits. Perhaps this will let me
32422 debug the reachability problems better.
32424 o Log / documentation fixes:
32425 - If we're a server and some peer has a broken TLS certificate, don't
32426 log about it unless ProtocolWarnings is set, i.e., we want to hear
32427 about protocol violations by others.
32428 - Fix spelling of VirtualAddrNetwork in man page.
32429 - Add a better explanation at the top of the autogenerated torrc file
32430 about what happened to our old torrc.
32433 Changes in version 0.1.1.20 - 2006-05-23
32435 - Downgrade a log severity where servers complain that they're
32437 - Avoid a compile warning on FreeBSD.
32438 - Remove string size limit on NEWDESC messages; solve bug 291.
32439 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
32440 more thoroughly when we're running on windows.
32443 Changes in version 0.1.1.19-rc - 2006-05-03
32445 - Regenerate our local descriptor if it's dirty and we try to use
32446 it locally (e.g. if it changes during reachability detection).
32447 - If we setconf our ORPort to 0, we continued to listen on the
32448 old ORPort and receive connections.
32449 - Avoid a second warning about machine/limits.h on Debian
32451 - Be willing to add our own routerinfo into the routerlist.
32452 Now authorities will include themselves in their directories
32453 and network-statuses.
32454 - Stop trying to upload rendezvous descriptors to every
32455 directory authority: only try the v1 authorities.
32456 - Servers no longer complain when they think they're not
32457 registered with the directory authorities. There were too many
32459 - Backport dist-rpm changes so rpms can be built without errors.
32462 - Implement an option, VirtualAddrMask, to set which addresses
32463 get handed out in response to mapaddress requests. This works
32464 around a bug in tsocks where 127.0.0.0/8 is never socksified.
32467 Changes in version 0.1.1.18-rc - 2006-04-10
32469 - Work harder to download live network-statuses from all the
32470 directory authorities we know about. Improve the threshold
32471 decision logic so we're more robust to edge cases.
32472 - When fetching rendezvous descriptors, we were willing to ask
32473 v2 authorities too, which would always return 404.
32476 - Stop listing down or invalid nodes in the v1 directory. This will
32477 reduce its bulk by about 1/3, and reduce load on directory
32479 - When deciding whether a router is Fast or Guard-worthy, consider
32480 his advertised BandwidthRate and not just the BandwidthCapacity.
32481 - No longer ship INSTALL and README files -- they are useless now.
32482 - Force rpmbuild to behave and honor target_cpu.
32483 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
32484 - Start to include translated versions of the tor-doc-*.html
32485 files, along with the screenshots. Still needs more work.
32486 - Start sending back 512 and 451 errors if mapaddress fails,
32487 rather than not sending anything back at all.
32488 - When we fail to bind or listen on an incoming or outgoing
32489 socket, we should close it before failing. otherwise we just
32490 leak it. (thanks to weasel for finding.)
32491 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
32492 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
32493 - Make NoPublish (even though deprecated) work again.
32494 - Fix a minor security flaw where a versioning auth dirserver
32495 could list a recommended version many times in a row to make
32496 clients more convinced that it's recommended.
32497 - Fix crash bug if there are two unregistered servers running
32498 with the same nickname, one of them is down, and you ask for
32499 them by nickname in your EntryNodes or ExitNodes. Also, try
32500 to pick the one that's running rather than an arbitrary one.
32501 - Fix an infinite loop we could hit if we go offline for too long.
32502 - Complain when we hit WSAENOBUFS on recv() or write() too.
32503 Perhaps this will help us hunt the bug.
32504 - If you're not a versioning dirserver, don't put the string
32505 "client-versions \nserver-versions \n" in your network-status.
32506 - Lower the minimum required number of file descriptors to 1000,
32507 so we can have some overhead for Valgrind on Linux, where the
32508 default ulimit -n is 1024.
32511 - Add tor.dizum.com as the fifth authoritative directory server.
32512 - Add a new config option FetchUselessDescriptors, off by default,
32513 for when you plan to run "exitlist" on your client and you want
32514 to know about even the non-running descriptors.
32517 Changes in version 0.1.1.17-rc - 2006-03-28
32519 - Clients and servers since 0.1.1.10-alpha have been expiring
32520 connections whenever they are idle for 5 minutes and they *do*
32521 have circuits on them. Oops. With this new version, clients will
32522 discard their previous entry guard choices and avoid choosing
32523 entry guards running these flawed versions.
32524 - Fix memory leak when uncompressing concatenated zlib streams. This
32525 was causing substantial leaks over time on Tor servers.
32526 - The v1 directory was including servers as much as 48 hours old,
32527 because that's how the new routerlist->routers works. Now only
32528 include them if they're 20 hours old or less.
32531 - Resume building on irix64, netbsd 2.0, etc.
32532 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
32534 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
32535 and it is confusing some users.
32536 - Mirrors stop caching the v1 directory so often.
32537 - Make the max number of old descriptors that a cache will hold
32538 rise with the number of directory authorities, so we can scale.
32539 - Change our win32 uname() hack to be more forgiving about what
32540 win32 versions it thinks it's found.
32543 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
32545 - When the controller's *setconf commands fail, collect an error
32546 message in a string and hand it back to the controller.
32547 - Make the v2 dir's "Fast" flag based on relative capacity, just
32548 like "Stable" is based on median uptime. Name everything in the
32549 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
32550 - Log server fingerprint on startup, so new server operators don't
32551 have to go hunting around their filesystem for it.
32552 - Return a robots.txt on our dirport to discourage google indexing.
32553 - Let the controller ask for GETINFO dir/status/foo so it can ask
32554 directly rather than connecting to the dir port. Only works when
32555 dirport is set for now.
32557 o New config options rather than constants in the code:
32558 - SocksTimeout: How long do we let a socks connection wait
32559 unattached before we fail it?
32560 - CircuitBuildTimeout: Cull non-open circuits that were born
32561 at least this many seconds ago.
32562 - CircuitIdleTimeout: Cull open clean circuits that were born
32563 at least this many seconds ago.
32566 Changes in version 0.1.1.16-rc - 2006-03-18
32567 o Bugfixes on 0.1.1.15-rc:
32568 - Fix assert when the controller asks to attachstream a connect-wait
32569 or resolve-wait stream.
32570 - Now do address rewriting when the controller asks us to attach
32571 to a particular circuit too. This will let Blossom specify
32572 "moria2.exit" without having to learn what moria2's IP address is.
32573 - Make the "tor --verify-config" command-line work again, so people
32574 can automatically check if their torrc will parse.
32575 - Authoritative dirservers no longer require an open connection from
32576 a server to consider him "reachable". We need this change because
32577 when we add new auth dirservers, old servers won't know not to
32579 - Let Tor build on Sun CC again.
32580 - Fix an off-by-one buffer size in dirserv.c that magically never
32581 hit our three authorities but broke sjmurdoch's own tor network.
32582 - If we as a directory mirror don't know of any v1 directory
32583 authorities, then don't try to cache any v1 directories.
32584 - Stop warning about unknown servers in our family when they are
32585 given as hex digests.
32586 - Stop complaining as quickly to the server operator that he
32587 hasn't registered his nickname/key binding.
32588 - Various cleanups so we can add new V2 Auth Dirservers.
32589 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
32590 reflect the updated flags in our v2 dir protocol.
32591 - Resume allowing non-printable characters for exit streams (both
32592 for connecting and for resolving). Now we tolerate applications
32593 that don't follow the RFCs. But continue to block malformed names
32596 o Bugfixes on 0.1.0.x:
32597 - Fix assert bug in close_logs(): when we close and delete logs,
32598 remove them all from the global "logfiles" list.
32599 - Fix minor integer overflow in calculating when we expect to use up
32600 our bandwidth allocation before hibernating.
32601 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
32602 there are multiple SSLs installed with different versions.
32603 - When we try to be a server and Address is not explicitly set and
32604 our hostname resolves to a private IP address, try to use an
32605 interface address if it has a public address. Now Windows machines
32606 that think of themselves as localhost can work by default.
32609 - Let the controller ask for GETINFO dir/server/foo so it can ask
32610 directly rather than connecting to the dir port.
32611 - Let the controller tell us about certain router descriptors
32612 that it doesn't want Tor to use in circuits. Implement
32613 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
32614 - New config option SafeSocks to reject all application connections
32615 using unsafe socks protocols. Defaults to off.
32618 Changes in version 0.1.1.15-rc - 2006-03-11
32619 o Bugfixes and cleanups:
32620 - When we're printing strings from the network, don't try to print
32621 non-printable characters. This protects us against shell escape
32622 sequence exploits, and also against attacks to fool humans into
32623 misreading their logs.
32624 - Fix a bug where Tor would fail to establish any connections if you
32625 left it off for 24 hours and then started it: we were happy with
32626 the obsolete network statuses, but they all referred to router
32627 descriptors that were too old to fetch, so we ended up with no
32628 valid router descriptors.
32629 - Fix a seg fault in the controller's "getinfo orconn-status"
32630 command while listing status on incoming handshaking connections.
32631 Introduce a status name "NEW" for these connections.
32632 - If we get a linelist or linelist_s config option from the torrc
32633 (e.g. ExitPolicy) and it has no value, warn and skip rather than
32634 silently resetting it to its default.
32635 - Don't abandon entry guards until they've been down or gone for
32637 - Cleaner and quieter log messages.
32640 - New controller signal NEWNYM that makes new application requests
32641 use clean circuits.
32642 - Add a new circuit purpose 'controller' to let the controller ask
32643 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
32644 controller command to let you specify the purpose if you're
32645 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
32646 command to let you change a circuit's purpose after it's been
32648 - Accept "private:*" in routerdesc exit policies; not generated yet
32649 because older Tors do not understand it.
32650 - Add BSD-style contributed startup script "rc.subr" from Peter
32654 Changes in version 0.1.1.14-alpha - 2006-02-20
32655 o Bugfixes on 0.1.1.x:
32656 - Don't die if we ask for a stdout or stderr log (even implicitly)
32657 and we're set to RunAsDaemon -- just warn.
32658 - We still had a few bugs in the OR connection rotation code that
32659 caused directory servers to slowly aggregate connections to other
32660 fast Tor servers. This time for sure!
32661 - Make log entries on Win32 include the name of the function again.
32662 - We were treating a pair of exit policies if they were equal even
32663 if one said accept and the other said reject -- causing us to
32664 not always publish a new descriptor since we thought nothing
32666 - Retry pending server downloads as well as pending networkstatus
32667 downloads when we unexpectedly get a socks request.
32668 - We were ignoring the IS_FAST flag in the directory status,
32669 meaning we were willing to pick trivial-bandwidth nodes for "fast"
32671 - If the controller's SAVECONF command fails (e.g. due to file
32672 permissions), let the controller know that it failed.
32675 - If we're trying to be a Tor server and running Windows 95/98/ME
32676 as a server, explain that we'll likely crash.
32677 - When we're a server, a client asks for an old-style directory,
32678 and our write bucket is empty, don't give it to him. This way
32679 small servers can continue to serve the directory *sometimes*,
32680 without getting overloaded.
32681 - Compress exit policies even more -- look for duplicate lines
32683 - Clients now honor the "guard" flag in the router status when
32684 picking entry guards, rather than looking at is_fast or is_stable.
32685 - Retain unrecognized lines in $DATADIR/state file, so that we can
32686 be forward-compatible.
32687 - Generate 18.0.0.0/8 address policy format in descs when we can;
32688 warn when the mask is not reducible to a bit-prefix.
32689 - Let the user set ControlListenAddress in the torrc. This can be
32690 dangerous, but there are some cases (like a secured LAN) where it
32692 - Split ReachableAddresses into ReachableDirAddresses and
32693 ReachableORAddresses, so we can restrict Dir conns to port 80
32694 and OR conns to port 443.
32695 - Now we can target arch and OS in rpm builds (contributed by
32696 Phobos). Also make the resulting dist-rpm filename match the
32698 - New config options to help controllers: FetchServerDescriptors
32699 and FetchHidServDescriptors for whether to fetch server
32700 info and hidserv info or let the controller do it, and
32701 PublishServerDescriptor and PublishHidServDescriptors.
32702 - Also let the controller set the __AllDirActionsPrivate config
32703 option if you want all directory fetches/publishes to happen via
32704 Tor (it assumes your controller bootstraps your circuits).
32707 Changes in version 0.1.0.17 - 2006-02-17
32708 o Crash bugfixes on 0.1.0.x:
32709 - When servers with a non-zero DirPort came out of hibernation,
32710 sometimes they would trigger an assert.
32712 o Other important bugfixes:
32713 - On platforms that don't have getrlimit (like Windows), we were
32714 artificially constraining ourselves to a max of 1024
32715 connections. Now just assume that we can handle as many as 15000
32716 connections. Hopefully this won't cause other problems.
32718 o Backported features:
32719 - When we're a server, a client asks for an old-style directory,
32720 and our write bucket is empty, don't give it to him. This way
32721 small servers can continue to serve the directory *sometimes*,
32722 without getting overloaded.
32723 - Whenever you get a 503 in response to a directory fetch, try
32724 once more. This will become important once servers start sending
32725 503's whenever they feel busy.
32726 - Fetch a new directory every 120 minutes, not every 40 minutes.
32727 Now that we have hundreds of thousands of users running the old
32728 directory algorithm, it's starting to hurt a lot.
32729 - Bump up the period for forcing a hidden service descriptor upload
32730 from 20 minutes to 1 hour.
32733 Changes in version 0.1.1.13-alpha - 2006-02-09
32734 o Crashes in 0.1.1.x:
32735 - When you tried to setconf ORPort via the controller, Tor would
32736 crash. So people using TorCP to become a server were sad.
32737 - Solve (I hope) the stack-smashing bug that we were seeing on fast
32738 servers. The problem appears to be something do with OpenSSL's
32739 random number generation, or how we call it, or something. Let me
32740 know if the crashes continue.
32741 - Turn crypto hardware acceleration off by default, until we find
32742 somebody smart who can test it for us. (It appears to produce
32743 seg faults in at least some cases.)
32744 - Fix a rare assert error when we've tried all intro points for
32745 a hidden service and we try fetching the service descriptor again:
32746 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
32749 - Fix a major load balance bug: we were round-robining in 16 KB
32750 chunks, and servers with bandwidthrate of 20 KB, while downloading
32751 a 600 KB directory, would starve their other connections. Now we
32752 try to be a bit more fair.
32753 - Dir authorities and mirrors were never expiring the newest
32754 descriptor for each server, causing memory and directory bloat.
32755 - Fix memory-bloating and connection-bloating bug on servers: We
32756 were never closing any connection that had ever had a circuit on
32757 it, because we were checking conn->n_circuits == 0, yet we had a
32758 bug that let it go negative.
32759 - Make Tor work using squid as your http proxy again -- squid
32760 returns an error if you ask for a URL that's too long, and it uses
32761 a really generic error message. Plus, many people are behind a
32762 transparent squid so they don't even realize it.
32763 - On platforms that don't have getrlimit (like Windows), we were
32764 artificially constraining ourselves to a max of 1024
32765 connections. Now just assume that we can handle as many as 15000
32766 connections. Hopefully this won't cause other problems.
32767 - Add a new config option ExitPolicyRejectPrivate which defaults to
32768 1. This means all exit policies will begin with rejecting private
32769 addresses, unless the server operator explicitly turns it off.
32772 - Clients no longer download descriptors for non-running
32774 - Before we add new directory authorities, we should make it
32775 clear that only v1 authorities should receive/publish hidden
32776 service descriptors.
32779 - As soon as we've fetched some more directory info, immediately
32780 try to download more server descriptors. This way we don't have
32781 a 10 second pause during initial bootstrapping.
32782 - Remove even more loud log messages that the server operator can't
32784 - When we're running an obsolete or un-recommended version, make
32785 the log message more clear about what the problem is and what
32786 versions *are* still recommended.
32787 - Provide a more useful warn message when our onion queue gets full:
32788 the CPU is too slow or the exit policy is too liberal.
32789 - Don't warn when we receive a 503 from a dirserver/cache -- this
32790 will pave the way for them being able to refuse if they're busy.
32791 - When we fail to bind a listener, try to provide a more useful
32792 log message: e.g., "Is Tor already running?"
32793 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
32794 Goldberg can prove things about our handshake protocol more
32796 - MaxConn has been obsolete for a while now. Document the ConnLimit
32797 config option, which is a *minimum* number of file descriptors
32798 that must be available else Tor refuses to start.
32799 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
32800 if you log to syslog and want something other than LOG_DAEMON.
32801 - Make dirservers generate a separate "guard" flag to mean,
32802 "would make a good entry guard". Make clients parse it and vote
32803 on it. Not used by clients yet.
32804 - Implement --with-libevent-dir option to ./configure. Also, improve
32805 search techniques to find libevent, and use those for openssl too.
32806 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
32807 - Only start testing reachability once we've established a
32808 circuit. This will make startup on dirservers less noisy.
32809 - Don't try to upload hidden service descriptors until we have
32810 established a circuit.
32811 - Fix the controller's "attachstream 0" command to treat conn like
32812 it just connected, doing address remapping, handling .exit and
32813 .onion idioms, and so on. Now we're more uniform in making sure
32814 that the controller hears about new and closing connections.
32817 Changes in version 0.1.1.12-alpha - 2006-01-11
32818 o Bugfixes on 0.1.1.x:
32819 - The fix to close duplicate server connections was closing all
32820 Tor client connections if they didn't establish a circuit
32821 quickly enough. Oops.
32822 - Fix minor memory issue (double-free) that happened on exit.
32824 o Bugfixes on 0.1.0.x:
32825 - Tor didn't warn when it failed to open a log file.
32828 Changes in version 0.1.1.11-alpha - 2006-01-10
32829 o Crashes in 0.1.1.x:
32830 - Include all the assert/crash fixes from 0.1.0.16.
32831 - If you start Tor and then quit very quickly, there were some
32832 races that tried to free things that weren't allocated yet.
32833 - Fix a rare memory stomp if you're running hidden services.
32834 - Fix segfault when specifying DirServer in config without nickname.
32835 - Fix a seg fault when you finish connecting to a server but at
32836 that moment you dump his server descriptor.
32837 - Extendcircuit and Attachstream controller commands would
32838 assert/crash if you don't give them enough arguments.
32839 - Fix an assert error when we're out of space in the connection_list
32840 and we try to post a hidden service descriptor (reported by weasel).
32841 - If you specify a relative torrc path and you set RunAsDaemon in
32842 your torrc, then it chdir()'s to the new directory. If you HUP,
32843 it tries to load the new torrc location, fails, and exits.
32844 The fix: no longer allow a relative path to torrc using -f.
32847 - Implement "entry guards": automatically choose a handful of entry
32848 nodes and stick with them for all circuits. Only pick new guards
32849 when the ones you have are unsuitable, and if the old guards
32850 become suitable again, switch back. This will increase security
32851 dramatically against certain end-point attacks. The EntryNodes
32852 config option now provides some hints about which entry guards you
32853 want to use most; and StrictEntryNodes means to only use those.
32854 - New directory logic: download by descriptor digest, not by
32855 fingerprint. Caches try to download all listed digests from
32856 authorities; clients try to download "best" digests from caches.
32857 This avoids partitioning and isolating attacks better.
32858 - Make the "stable" router flag in network-status be the median of
32859 the uptimes of running valid servers, and make clients pay
32860 attention to the network-status flags. Thus the cutoff adapts
32861 to the stability of the network as a whole, making IRC, IM, etc
32862 connections more reliable.
32865 - Tor servers with dynamic IP addresses were needing to wait 18
32866 hours before they could start doing reachability testing using
32867 the new IP address and ports. This is because they were using
32868 the internal descriptor to learn what to test, yet they were only
32869 rebuilding the descriptor once they decided they were reachable.
32870 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
32871 to download certain server descriptors, throw them away, and then
32872 fetch them again after 30 minutes. Now mirrors throw away these
32873 server descriptors so clients can't get them.
32874 - We were leaving duplicate connections to other ORs open for a week,
32875 rather than closing them once we detect a duplicate. This only
32876 really affected authdirservers, but it affected them a lot.
32877 - Spread the authdirservers' reachability testing over the entire
32878 testing interval, so we don't try to do 500 TLS's at once every
32882 - If the network is down, and we try to connect to a conn because
32883 we have a circuit in mind, and we timeout (30 seconds) because the
32884 network never answers, we were expiring the circuit, but we weren't
32885 obsoleting the connection or telling the entry_guards functions.
32886 - Some Tor servers process billions of cells per day. These statistics
32887 need to be uint64_t's.
32888 - Check for integer overflows in more places, when adding elements
32889 to smartlists. This could possibly prevent a buffer overflow
32890 on malicious huge inputs. I don't see any, but I haven't looked
32892 - ReachableAddresses kept growing new "reject *:*" lines on every
32894 - When you "setconf log" via the controller, it should remove all
32895 logs. We were automatically adding back in a "log notice stdout".
32896 - Newly bootstrapped Tor networks couldn't establish hidden service
32897 circuits until they had nodes with high uptime. Be more tolerant.
32898 - We were marking servers down when they could not answer every piece
32899 of the directory request we sent them. This was far too harsh.
32900 - Fix the torify (tsocks) config file to not use Tor for localhost
32902 - Directory authorities now go to the proper authority when asking for
32903 a networkstatus, even when they want a compressed one.
32904 - Fix a harmless bug that was causing Tor servers to log
32905 "Got an end because of misc error, but we're not an AP. Closing."
32906 - Authorities were treating their own descriptor changes as cosmetic,
32907 meaning the descriptor available in the network-status and the
32908 descriptor that clients downloaded were different.
32909 - The OS X installer was adding a symlink for tor_resolve but
32910 the binary was called tor-resolve (reported by Thomas Hardly).
32911 - Workaround a problem with some http proxies where they refuse GET
32912 requests that specify "Content-Length: 0" (reported by Adrian).
32913 - Fix wrong log message when you add a "HiddenServiceNodes" config
32914 line without any HiddenServiceDir line (reported by Chris Thomas).
32917 - Write the TorVersion into the state file so we have a prayer of
32918 keeping forward and backward compatibility.
32919 - Revive the FascistFirewall config option rather than eliminating it:
32920 now it's a synonym for ReachableAddresses *:80,*:443.
32921 - Clients choose directory servers from the network status lists,
32922 not from their internal list of router descriptors. Now they can
32923 go to caches directly rather than needing to go to authorities
32925 - Directory authorities ignore router descriptors that have only
32926 cosmetic differences: do this for 0.1.0.x servers now too.
32927 - Add a new flag to network-status indicating whether the server
32928 can answer v2 directory requests too.
32929 - Authdirs now stop whining so loudly about bad descriptors that
32930 they fetch from other dirservers. So when there's a log complaint,
32931 it's for sure from a freshly uploaded descriptor.
32932 - Reduce memory requirements in our structs by changing the order
32934 - There used to be two ways to specify your listening ports in a
32935 server descriptor: on the "router" line and with a separate "ports"
32936 line. Remove support for the "ports" line.
32937 - New config option "AuthDirRejectUnlisted" for auth dirservers as
32938 a panic button: if we get flooded with unusable servers we can
32939 revert to only listing servers in the approved-routers file.
32940 - Auth dir servers can now mark a fingerprint as "!reject" or
32941 "!invalid" in the approved-routers file (as its nickname), to
32942 refuse descriptors outright or include them but marked as invalid.
32943 - Servers store bandwidth history across restarts/crashes.
32944 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
32945 get a better idea of why their circuits failed. Not used yet.
32946 - Directory mirrors now cache up to 16 unrecognized network-status
32947 docs. Now we can add new authdirservers and they'll be cached too.
32948 - When picking a random directory, prefer non-authorities if any
32950 - New controller option "getinfo desc/all-recent" to fetch the
32951 latest server descriptor for every router that Tor knows about.
32954 Changes in version 0.1.0.16 - 2006-01-02
32955 o Crash bugfixes on 0.1.0.x:
32956 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
32957 corrupting the heap, losing FDs, or crashing when we need to resize
32958 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
32959 - It turns out sparc64 platforms crash on unaligned memory access
32960 too -- so detect and avoid this.
32961 - Handle truncated compressed data correctly (by detecting it and
32963 - Fix possible-but-unlikely free(NULL) in control.c.
32964 - When we were closing connections, there was a rare case that
32965 stomped on memory, triggering seg faults and asserts.
32966 - Avoid potential infinite recursion when building a descriptor. (We
32967 don't know that it ever happened, but better to fix it anyway.)
32968 - We were neglecting to unlink marked circuits from soon-to-close OR
32969 connections, which caused some rare scribbling on freed memory.
32970 - Fix a memory stomping race bug when closing the joining point of two
32971 rendezvous circuits.
32972 - Fix an assert in time parsing found by Steven Murdoch.
32974 o Other bugfixes on 0.1.0.x:
32975 - When we're doing reachability testing, provide more useful log
32976 messages so the operator knows what to expect.
32977 - Do not check whether DirPort is reachable when we are suppressing
32978 advertising it because of hibernation.
32979 - When building with -static or on Solaris, we sometimes needed -ldl.
32980 - When we're deciding whether a stream has enough circuits around
32981 that can handle it, count the freshly dirty ones and not the ones
32982 that are so dirty they won't be able to handle it.
32983 - When we're expiring old circuits, we had a logic error that caused
32984 us to close new rendezvous circuits rather than old ones.
32985 - Give a more helpful log message when you try to change ORPort via
32986 the controller: you should upgrade Tor if you want that to work.
32987 - We were failing to parse Tor versions that start with "Tor ".
32988 - Tolerate faulty streams better: when a stream fails for reason
32989 exitpolicy, stop assuming that the router is lying about his exit
32990 policy. When a stream fails for reason misc, allow it to retry just
32991 as if it was resolvefailed. When a stream has failed three times,
32992 reset its failure count so we can try again and get all three tries.
32995 Changes in version 0.1.1.10-alpha - 2005-12-11
32996 o Correctness bugfixes on 0.1.0.x:
32997 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
32998 corrupting the heap, losing FDs, or crashing when we need to resize
32999 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
33000 - Stop doing the complex voodoo overkill checking for insecure
33001 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
33002 - When we were closing connections, there was a rare case that
33003 stomped on memory, triggering seg faults and asserts.
33004 - We were neglecting to unlink marked circuits from soon-to-close OR
33005 connections, which caused some rare scribbling on freed memory.
33006 - When we're deciding whether a stream has enough circuits around
33007 that can handle it, count the freshly dirty ones and not the ones
33008 that are so dirty they won't be able to handle it.
33009 - Recover better from TCP connections to Tor servers that are
33010 broken but don't tell you (it happens!); and rotate TLS
33011 connections once a week.
33012 - When we're expiring old circuits, we had a logic error that caused
33013 us to close new rendezvous circuits rather than old ones.
33014 - Fix a scary-looking but apparently harmless bug where circuits
33015 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
33016 servers, and never switch to state CIRCUIT_STATE_OPEN.
33017 - When building with -static or on Solaris, we sometimes needed to
33019 - Give a useful message when people run Tor as the wrong user,
33020 rather than telling them to start chowning random directories.
33021 - We were failing to inform the controller about new .onion streams.
33023 o Security bugfixes on 0.1.0.x:
33024 - Refuse server descriptors if the fingerprint line doesn't match
33025 the included identity key. Tor doesn't care, but other apps (and
33026 humans) might actually be trusting the fingerprint line.
33027 - We used to kill the circuit when we receive a relay command we
33028 don't recognize. Now we just drop it.
33029 - Start obeying our firewall options more rigorously:
33030 . If we can't get to a dirserver directly, try going via Tor.
33031 . Don't ever try to connect (as a client) to a place our
33032 firewall options forbid.
33033 . If we specify a proxy and also firewall options, obey the
33034 firewall options even when we're using the proxy: some proxies
33035 can only proxy to certain destinations.
33036 - Fix a bug found by Lasse Overlier: when we were making internal
33037 circuits (intended to be cannibalized later for rendezvous and
33038 introduction circuits), we were picking them so that they had
33039 useful exit nodes. There was no need for this, and it actually
33040 aids some statistical attacks.
33041 - Start treating internal circuits and exit circuits separately.
33042 It's important to keep them separate because internal circuits
33043 have their last hops picked like middle hops, rather than like
33044 exit hops. So exiting on them will break the user's expectations.
33046 o Bugfixes on 0.1.1.x:
33047 - Take out the mis-feature where we tried to detect IP address
33048 flapping for people with DynDNS, and chose not to upload a new
33049 server descriptor sometimes.
33050 - Try to be compatible with OpenSSL 0.9.6 again.
33051 - Log fix: when the controller is logging about .onion addresses,
33052 sometimes it didn't include the ".onion" part of the address.
33053 - Don't try to modify options->DirServers internally -- if the
33054 user didn't specify any, just add the default ones directly to
33055 the trusted dirserver list. This fixes a bug where people running
33056 controllers would use SETCONF on some totally unrelated config
33057 option, and Tor would start yelling at them about changing their
33059 - Let the controller's redirectstream command specify a port, in
33060 case the controller wants to change that too.
33061 - When we requested a pile of server descriptors, we sometimes
33062 accidentally launched a duplicate request for the first one.
33063 - Bugfix for trackhostexits: write down the fingerprint of the
33064 chosen exit, not its nickname, because the chosen exit might not
33066 - When parsing foo.exit, if foo is unknown, and we are leaving
33067 circuits unattached, set the chosen_exit field and leave the
33068 address empty. This matters because controllers got confused
33070 - Directory authorities no longer try to download server
33071 descriptors that they know they will reject.
33073 o Features and updates:
33074 - Replace balanced trees with hash tables: this should make stuff
33075 significantly faster.
33076 - Resume using the AES counter-mode implementation that we ship,
33077 rather than OpenSSL's. Ours is significantly faster.
33078 - Many other CPU and memory improvements.
33079 - Add a new config option FastFirstHopPK (on by default) so clients
33080 do a trivial crypto handshake for their first hop, since TLS has
33081 already taken care of confidentiality and authentication.
33082 - Add a new config option TestSocks so people can see if their
33083 applications are using socks4, socks4a, socks5-with-ip, or
33084 socks5-with-hostname. This way they don't have to keep mucking
33085 with tcpdump and wondering if something got cached somewhere.
33086 - Warn when listening on a public address for socks. I suspect a
33087 lot of people are setting themselves up as open socks proxies,
33088 and they have no idea that jerks on the Internet are using them,
33089 since they simply proxy the traffic into the Tor network.
33090 - Add "private:*" as an alias in configuration for policies. Now
33091 you can simplify your exit policy rather than needing to list
33092 every single internal or nonroutable network space.
33093 - Add a new controller event type that allows controllers to get
33094 all server descriptors that were uploaded to a router in its role
33095 as authoritative dirserver.
33096 - Start shipping socks-extensions.txt, tor-doc-unix.html,
33097 tor-doc-server.html, and stylesheet.css in the tarball.
33098 - Stop shipping tor-doc.html in the tarball.
33101 Changes in version 0.1.1.9-alpha - 2005-11-15
33102 o Usability improvements:
33103 - Start calling it FooListenAddress rather than FooBindAddress,
33104 since few of our users know what it means to bind an address
33106 - Reduce clutter in server logs. We're going to try to make
33107 them actually usable now. New config option ProtocolWarnings that
33108 lets you hear about how _other Tors_ are breaking the protocol. Off
33110 - Divide log messages into logging domains. Once we put some sort
33111 of interface on this, it will let people looking at more verbose
33112 log levels specify the topics they want to hear more about.
33113 - Make directory servers return better http 404 error messages
33114 instead of a generic "Servers unavailable".
33115 - Check for even more Windows version flags when writing the platform
33116 string in server descriptors, and note any we don't recognize.
33117 - Clean up more of the OpenSSL memory when exiting, so we can detect
33118 memory leaks better.
33119 - Make directory authorities be non-versioning, non-naming by
33120 default. Now we can add new directory servers without requiring
33121 their operators to pay close attention.
33122 - When logging via syslog, include the pid whenever we provide
33123 a log entry. Suggested by Todd Fries.
33125 o Performance improvements:
33126 - Directory servers now silently throw away new descriptors that
33127 haven't changed much if the timestamps are similar. We do this to
33128 tolerate older Tor servers that upload a new descriptor every 15
33129 minutes. (It seemed like a good idea at the time.)
33130 - Inline bottleneck smartlist functions; use fast versions by default.
33131 - Add a "Map from digest to void*" abstraction digestmap_t so we
33132 can do less hex encoding/decoding. Use it in router_get_by_digest()
33133 to resolve a performance bottleneck.
33134 - Allow tor_gzip_uncompress to extract as much as possible from
33135 truncated compressed data. Try to extract as many
33136 descriptors as possible from truncated http responses (when
33137 DIR_PURPOSE_FETCH_ROUTERDESC).
33138 - Make circ->onionskin a pointer, not a static array. moria2 was using
33139 125000 circuit_t's after it had been up for a few weeks, which
33140 translates to 20+ megs of wasted space.
33141 - The private half of our EDH handshake keys are now chosen out
33142 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
33144 o Security improvements:
33145 - Start making directory caches retain old routerinfos, so soon
33146 clients can start asking by digest of descriptor rather than by
33147 fingerprint of server.
33148 - Add half our entropy from RAND_poll in OpenSSL. This knows how
33149 to use egd (if present), openbsd weirdness (if present), vms/os2
33150 weirdness (if we ever port there), and more in the future.
33152 o Bugfixes on 0.1.0.x:
33153 - Do round-robin writes of at most 16 kB per write. This might be
33154 more fair on loaded Tor servers, and it might resolve our Windows
33155 crash bug. It might also slow things down.
33156 - Our TLS handshakes were generating a single public/private
33157 keypair for the TLS context, rather than making a new one for
33158 each new connections. Oops. (But we were still rotating them
33159 periodically, so it's not so bad.)
33160 - When we were cannibalizing a circuit with a particular exit
33161 node in mind, we weren't checking to see if that exit node was
33162 already present earlier in the circuit. Oops.
33163 - When a Tor server's IP changes (e.g. from a dyndns address),
33164 upload a new descriptor so clients will learn too.
33165 - Really busy servers were keeping enough circuits open on stable
33166 connections that they were wrapping around the circuit_id
33167 space. (It's only two bytes.) This exposed a bug where we would
33168 feel free to reuse a circuit_id even if it still exists but has
33169 been marked for close. Try to fix this bug. Some bug remains.
33170 - If we would close a stream early (e.g. it asks for a .exit that
33171 we know would refuse it) but the LeaveStreamsUnattached config
33172 option is set by the controller, then don't close it.
33174 o Bugfixes on 0.1.1.8-alpha:
33175 - Fix a big pile of memory leaks, some of them serious.
33176 - Do not try to download a routerdesc if we would immediately reject
33178 - Resume inserting a newline between all router descriptors when
33179 generating (old style) signed directories, since our spec says
33181 - When providing content-type application/octet-stream for
33182 server descriptors using .z, we were leaving out the
33183 content-encoding header. Oops. (Everything tolerated this just
33184 fine, but that doesn't mean we need to be part of the problem.)
33185 - Fix a potential seg fault in getconf and getinfo using version 1
33186 of the controller protocol.
33187 - Avoid crash: do not check whether DirPort is reachable when we
33188 are suppressing it because of hibernation.
33189 - Make --hash-password not crash on exit.
33192 Changes in version 0.1.1.8-alpha - 2005-10-07
33193 o New features (major):
33194 - Clients don't download or use the directory anymore. Now they
33195 download and use network-statuses from the trusted dirservers,
33196 and fetch individual server descriptors as needed from mirrors.
33197 See dir-spec.txt for all the gory details.
33198 - Be more conservative about whether to advertise our DirPort.
33199 The main change is to not advertise if we're running at capacity
33200 and either a) we could hibernate or b) our capacity is low and
33201 we're using a default DirPort.
33202 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
33204 o New features (minor):
33205 - Try to be smart about when to retry network-status and
33206 server-descriptor fetches. Still needs some tuning.
33207 - Stop parsing, storing, or using running-routers output (but
33208 mirrors still cache and serve it).
33209 - Consider a threshold of versioning dirservers (dirservers who have
33210 an opinion about which Tor versions are still recommended) before
33211 deciding whether to warn the user that he's obsolete.
33212 - Dirservers can now reject/invalidate by key and IP, with the
33213 config options "AuthDirInvalid" and "AuthDirReject". This is
33214 useful since currently we automatically list servers as running
33215 and usable even if we know they're jerks.
33216 - Provide dire warnings to any users who set DirServer; move it out
33217 of torrc.sample and into torrc.complete.
33218 - Add MyFamily to torrc.sample in the server section.
33219 - Add nicknames to the DirServer line, so we can refer to them
33220 without requiring all our users to memorize their IP addresses.
33221 - When we get an EOF or a timeout on a directory connection, note
33222 how many bytes of serverdesc we are dropping. This will help
33223 us determine whether it is smart to parse incomplete serverdesc
33225 - Add a new function to "change pseudonyms" -- that is, to stop
33226 using any currently-dirty circuits for new streams, so we don't
33227 link new actions to old actions. Currently it's only called on
33228 HUP (or SIGNAL RELOAD).
33229 - On sighup, if UseHelperNodes changed to 1, use new circuits.
33230 - Start using RAND_bytes rather than RAND_pseudo_bytes from
33231 OpenSSL. Also, reseed our entropy every hour, not just at
33232 startup. And entropy in 512-bit chunks, not 160-bit chunks.
33234 o Fixes on 0.1.1.7-alpha:
33235 - Nobody ever implemented EVENT_ADDRMAP for control protocol
33236 version 0, so don't let version 0 controllers ask for it.
33237 - If you requested something with too many newlines via the
33238 v1 controller protocol, you could crash tor.
33239 - Fix a number of memory leaks, including some pretty serious ones.
33240 - Re-enable DirPort testing again, so Tor servers will be willing
33241 to advertise their DirPort if it's reachable.
33242 - On TLS handshake, only check the other router's nickname against
33243 its expected nickname if is_named is set.
33245 o Fixes forward-ported from 0.1.0.15:
33246 - Don't crash when we don't have any spare file descriptors and we
33247 try to spawn a dns or cpu worker.
33248 - Make the numbers in read-history and write-history into uint64s,
33249 so they don't overflow and publish negatives in the descriptor.
33251 o Fixes on 0.1.0.x:
33252 - For the OS X package's modified privoxy config file, comment
33253 out the "logfile" line so we don't log everything passed
33255 - We were whining about using socks4 or socks5-with-local-lookup
33256 even when it's an IP in the "virtual" range we designed exactly
33258 - We were leaking some memory every time the client changes IPs.
33259 - Never call free() on tor_malloc()d memory. This will help us
33260 use dmalloc to detect memory leaks.
33261 - Check for named servers when looking them up by nickname;
33262 warn when we'recalling a non-named server by its nickname;
33263 don't warn twice about the same name.
33264 - Try to list MyFamily elements by key, not by nickname, and warn
33265 if we've not heard of the server.
33266 - Make windows platform detection (uname equivalent) smarter.
33267 - It turns out sparc64 doesn't like unaligned access either.
33270 Changes in version 0.1.0.15 - 2005-09-23
33271 o Bugfixes on 0.1.0.x:
33272 - Reject ports 465 and 587 (spam targets) in default exit policy.
33273 - Don't crash when we don't have any spare file descriptors and we
33274 try to spawn a dns or cpu worker.
33275 - Get rid of IgnoreVersion undocumented config option, and make us
33276 only warn, never exit, when we're running an obsolete version.
33277 - Don't try to print a null string when your server finds itself to
33278 be unreachable and the Address config option is empty.
33279 - Make the numbers in read-history and write-history into uint64s,
33280 so they don't overflow and publish negatives in the descriptor.
33281 - Fix a minor memory leak in smartlist_string_remove().
33282 - We were only allowing ourselves to upload a server descriptor at
33283 most every 20 minutes, even if it changed earlier than that.
33284 - Clean up log entries that pointed to old URLs.
33287 Changes in version 0.1.1.7-alpha - 2005-09-14
33288 o Fixes on 0.1.1.6-alpha:
33289 - Exit servers were crashing when people asked them to make a
33290 connection to an address not in their exit policy.
33291 - Looking up a non-existent stream for a v1 control connection would
33293 - Fix a seg fault if we ask a dirserver for a descriptor by
33294 fingerprint but he doesn't know about him.
33295 - SETCONF was appending items to linelists, not clearing them.
33296 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
33297 out and refuse the setconf if it would fail.
33298 - Downgrade the dirserver log messages when whining about
33302 - Add Peter Palfrader's check-tor script to tor/contrib/
33303 It lets you easily check whether a given server (referenced by
33304 nickname) is reachable by you.
33305 - Numerous changes to move towards client-side v2 directories. Not
33308 o Fixes on 0.1.0.x:
33309 - If the user gave tor an odd number of command-line arguments,
33310 we were silently ignoring the last one. Now we complain and fail.
33311 [This wins the oldest-bug prize -- this bug has been present since
33312 November 2002, as released in Tor 0.0.0.]
33313 - Do not use unaligned memory access on alpha, mips, or mipsel.
33314 It *works*, but is very slow, so we treat them as if it doesn't.
33315 - Retry directory requests if we fail to get an answer we like
33316 from a given dirserver (we were retrying before, but only if
33317 we fail to connect).
33318 - When writing the RecommendedVersions line, sort them first.
33319 - When the client asked for a rendezvous port that the hidden
33320 service didn't want to provide, we were sending an IP address
33321 back along with the end cell. Fortunately, it was zero. But stop
33323 - Correct "your server is reachable" log entries to indicate that
33324 it was self-testing that told us so.
33327 Changes in version 0.1.1.6-alpha - 2005-09-09
33328 o Fixes on 0.1.1.5-alpha:
33329 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
33330 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
33331 - Fix bug with tor_memmem finding a match at the end of the string.
33332 - Make unit tests run without segfaulting.
33333 - Resolve some solaris x86 compile warnings.
33334 - Handle duplicate lines in approved-routers files without warning.
33335 - Fix bug where as soon as a server refused any requests due to his
33336 exit policy (e.g. when we ask for localhost and he tells us that's
33337 127.0.0.1 and he won't do it), we decided he wasn't obeying his
33338 exit policy using him for any exits.
33339 - Only do openssl hardware accelerator stuff if openssl version is
33342 o New controller features/fixes:
33343 - Add a "RESETCONF" command so you can set config options like
33344 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
33345 a config option in the torrc with no value, then it clears it
33346 entirely (rather than setting it to its default).
33347 - Add a "GETINFO config-file" to tell us where torrc is.
33348 - Avoid sending blank lines when GETINFO replies should be empty.
33349 - Add a QUIT command for the controller (for using it manually).
33350 - Fix a bug in SAVECONF that was adding default dirservers and
33351 other redundant entries to the torrc file.
33353 o Start on the new directory design:
33354 - Generate, publish, cache, serve new network-status format.
33355 - Publish individual descriptors (by fingerprint, by "all", and by
33357 - Publish client and server recommended versions separately.
33358 - Allow tor_gzip_uncompress() to handle multiple concatenated
33359 compressed strings. Serve compressed groups of router
33360 descriptors. The compression logic here could be more
33362 - Distinguish v1 authorities (all currently trusted directories)
33363 from v2 authorities (all trusted directories).
33364 - Change DirServers config line to note which dirs are v1 authorities.
33365 - Add configuration option "V1AuthoritativeDirectory 1" which
33366 moria1, moria2, and tor26 should set.
33367 - Remove option when getting directory cache to see whether they
33368 support running-routers; they all do now. Replace it with one
33369 to see whether caches support v2 stuff.
33372 - Dirservers now do their own external reachability testing of each
33373 Tor server, and only list them as running if they've been found to
33374 be reachable. We also send back warnings to the server's logs if
33375 it uploads a descriptor that we already believe is unreachable.
33376 - Implement exit enclaves: if we know an IP address for the
33377 destination, and there's a running Tor server at that address
33378 which allows exit to the destination, then extend the circuit to
33379 that exit first. This provides end-to-end encryption and end-to-end
33380 authentication. Also, if the user wants a .exit address or enclave,
33381 use 4 hops rather than 3, and cannibalize a general circ for it
33383 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
33384 controller. Also, rotate dns and cpu workers if the controller
33385 changes options that will affect them; and initialize the dns
33386 worker cache tree whether or not we start out as a server.
33387 - Only upload a new server descriptor when options change, 18
33388 hours have passed, uptime is reset, or bandwidth changes a lot.
33389 - Check [X-]Forwarded-For headers in HTTP requests when generating
33390 log messages. This lets people run dirservers (and caches) behind
33391 Apache but still know which IP addresses are causing warnings.
33393 o Config option changes:
33394 - Replace (Fascist)Firewall* config options with a new
33395 ReachableAddresses option that understands address policies.
33396 For example, "ReachableAddresses *:80,*:443"
33397 - Get rid of IgnoreVersion undocumented config option, and make us
33398 only warn, never exit, when we're running an obsolete version.
33399 - Make MonthlyAccountingStart config option truly obsolete now.
33401 o Fixes on 0.1.0.x:
33402 - Reject ports 465 and 587 in the default exit policy, since
33403 people have started using them for spam too.
33404 - It turns out we couldn't bootstrap a network since we added
33405 reachability detection in 0.1.0.1-rc. Good thing the Tor network
33406 has never gone down. Add an AssumeReachable config option to let
33407 servers and dirservers bootstrap. When we're trying to build a
33408 high-uptime or high-bandwidth circuit but there aren't enough
33409 suitable servers, try being less picky rather than simply failing.
33410 - Our logic to decide if the OR we connected to was the right guy
33411 was brittle and maybe open to a mitm for unverified routers.
33412 - We weren't cannibalizing circuits correctly for
33413 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
33414 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
33415 build those from scratch. This should make hidden services faster.
33416 - Predict required circuits better, with an eye toward making hidden
33417 services faster on the service end.
33418 - Retry streams if the exit node sends back a 'misc' failure. This
33419 should result in fewer random failures. Also, after failing
33420 from resolve failed or misc, reset the num failures, so we give
33421 it a fair shake next time we try.
33422 - Clean up the rendezvous warn log msgs, and downgrade some to info.
33423 - Reduce severity on logs about dns worker spawning and culling.
33424 - When we're shutting down and we do something like try to post a
33425 server descriptor or rendezvous descriptor, don't complain that
33426 we seem to be unreachable. Of course we are, we're shutting down.
33427 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
33428 We don't use them yet, but maybe one day our DNS resolver will be
33429 able to discover them.
33430 - Make ContactInfo mandatory for authoritative directory servers.
33431 - Require server descriptors to list IPv4 addresses -- hostnames
33432 are no longer allowed. This also fixes some potential security
33433 problems with people providing hostnames as their address and then
33434 preferentially resolving them to partition users.
33435 - Change log line for unreachability to explicitly suggest /etc/hosts
33436 as the culprit. Also make it clearer what IP address and ports we're
33437 testing for reachability.
33438 - Put quotes around user-supplied strings when logging so users are
33439 more likely to realize if they add bad characters (like quotes)
33441 - Let auth dir servers start without specifying an Address config
33443 - Make unit tests (and other invocations that aren't the real Tor)
33444 run without launching listeners, creating subdirectories, and so on.
33447 Changes in version 0.1.1.5-alpha - 2005-08-08
33448 o Bugfixes included in 0.1.0.14.
33450 o Bugfixes on 0.1.0.x:
33451 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
33452 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
33453 it would silently using ignore the 6668.
33456 Changes in version 0.1.0.14 - 2005-08-08
33457 o Bugfixes on 0.1.0.x:
33458 - Fix the other half of the bug with crypto handshakes
33460 - Fix an assert trigger if you send a 'signal term' via the
33461 controller when it's listening for 'event info' messages.
33464 Changes in version 0.1.1.4-alpha - 2005-08-04
33465 o Bugfixes included in 0.1.0.13.
33468 - Improve tor_gettimeofday() granularity on windows.
33469 - Make clients regenerate their keys when their IP address changes.
33470 - Implement some more GETINFO goodness: expose helper nodes, config
33471 options, getinfo keys.
33474 Changes in version 0.1.0.13 - 2005-08-04
33475 o Bugfixes on 0.1.0.x:
33476 - Fix a critical bug in the security of our crypto handshakes.
33477 - Fix a size_t underflow in smartlist_join_strings2() that made
33478 it do bad things when you hand it an empty smartlist.
33479 - Fix Windows installer to ship Tor license (thanks to Aphex for
33480 pointing out this oversight) and put a link to the doc directory
33482 - Explicitly set no-unaligned-access for sparc: it turns out the
33483 new gcc's let you compile broken code, but that doesn't make it
33487 Changes in version 0.1.1.3-alpha - 2005-07-23
33488 o Bugfixes on 0.1.1.2-alpha:
33489 - Fix a bug in handling the controller's "post descriptor"
33491 - Fix several bugs in handling the controller's "extend circuit"
33493 - Fix a bug in handling the controller's "stream status" event.
33494 - Fix an assert failure if we have a controller listening for
33495 circuit events and we go offline.
33496 - Re-allow hidden service descriptors to publish 0 intro points.
33497 - Fix a crash when generating your hidden service descriptor if
33498 you don't have enough intro points already.
33500 o New features on 0.1.1.2-alpha:
33501 - New controller function "getinfo accounting", to ask how
33502 many bytes we've used in this time period.
33503 - Experimental support for helper nodes: a lot of the risk from
33504 a small static adversary comes because users pick new random
33505 nodes every time they rebuild a circuit. Now users will try to
33506 stick to the same small set of entry nodes if they can. Not
33507 enabled by default yet.
33509 o Bugfixes on 0.1.0.12:
33510 - If you're an auth dir server, always publish your dirport,
33511 even if you haven't yet found yourself to be reachable.
33512 - Fix a size_t underflow in smartlist_join_strings2() that made
33513 it do bad things when you hand it an empty smartlist.
33516 Changes in version 0.1.0.12 - 2005-07-18
33517 o New directory servers:
33518 - tor26 has changed IP address.
33520 o Bugfixes on 0.1.0.x:
33521 - Fix a possible double-free in tor_gzip_uncompress().
33522 - When --disable-threads is set, do not search for or link against
33523 pthreads libraries.
33524 - Don't trigger an assert if an authoritative directory server
33525 claims its dirport is 0.
33526 - Fix bug with removing Tor as an NT service: some people were
33527 getting "The service did not return an error." Thanks to Matt
33531 Changes in version 0.1.1.2-alpha - 2005-07-15
33532 o New directory servers:
33533 - tor26 has changed IP address.
33535 o Bugfixes on 0.1.0.x, crashes/leaks:
33536 - Port the servers-not-obeying-their-exit-policies fix from
33538 - Fix an fd leak in start_daemon().
33539 - On Windows, you can't always reopen a port right after you've
33540 closed it. So change retry_listeners() to only close and re-open
33541 ports that have changed.
33542 - Fix a possible double-free in tor_gzip_uncompress().
33544 o Bugfixes on 0.1.0.x, usability:
33545 - When tor_socketpair() fails in Windows, give a reasonable
33546 Windows-style errno back.
33547 - Let people type "tor --install" as well as "tor -install" when
33549 want to make it an NT service.
33550 - NT service patch from Matt Edman to improve error messages.
33551 - When the controller asks for a config option with an abbreviated
33552 name, give the full name in our response.
33553 - Correct the man page entry on TrackHostExitsExpire.
33554 - Looks like we were never delivering deflated (i.e. compressed)
33555 running-routers lists, even when asked. Oops.
33556 - When --disable-threads is set, do not search for or link against
33557 pthreads libraries.
33559 o Bugfixes on 0.1.1.x:
33560 - Fix a seg fault with autodetecting which controller version is
33564 - New hidden service descriptor format: put a version in it, and
33565 let people specify introduction/rendezvous points that aren't
33566 in "the directory" (which is subjective anyway).
33567 - Allow the DEBUG controller event to work again. Mark certain log
33568 entries as "don't tell this to controllers", so we avoid cycles.
33571 Changes in version 0.1.0.11 - 2005-06-30
33572 o Bugfixes on 0.1.0.x:
33573 - Fix major security bug: servers were disregarding their
33574 exit policies if clients behaved unexpectedly.
33575 - Make OS X init script check for missing argument, so we don't
33576 confuse users who invoke it incorrectly.
33577 - Fix a seg fault in "tor --hash-password foo".
33578 - The MAPADDRESS control command was broken.
33581 Changes in version 0.1.1.1-alpha - 2005-06-29
33583 - Make OS X init script check for missing argument, so we don't
33584 confuse users who invoke it incorrectly.
33585 - Fix a seg fault in "tor --hash-password foo".
33586 - Fix a possible way to DoS dirservers.
33587 - When we complain that your exit policy implicitly allows local or
33588 private address spaces, name them explicitly so operators can
33590 - Make the log message less scary when all the dirservers are
33591 temporarily unreachable.
33592 - We were printing the number of idle dns workers incorrectly when
33596 - Revised controller protocol (version 1) that uses ascii rather
33597 than binary. Add supporting libraries in python and java so you
33598 can use the controller from your applications without caring how
33599 our protocol works.
33600 - Spiffy new support for crypto hardware accelerators. Can somebody
33604 Changes in version 0.0.9.10 - 2005-06-16
33605 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
33606 - Refuse relay cells that claim to have a length larger than the
33607 maximum allowed. This prevents a potential attack that could read
33608 arbitrary memory (e.g. keys) from an exit server's process
33612 Changes in version 0.1.0.10 - 2005-06-14
33613 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
33614 libevent before 1.1a.
33617 Changes in version 0.1.0.9-rc - 2005-06-09
33619 - Reset buf->highwater every time buf_shrink() is called, not just on
33620 a successful shrink. This was causing significant memory bloat.
33621 - Fix buffer overflow when checking hashed passwords.
33622 - Security fix: if seeding the RNG on Win32 fails, quit.
33623 - Allow seeding the RNG on Win32 even when you're not running as
33625 - Disable threading on Solaris too. Something is wonky with it,
33626 cpuworkers, and reentrant libs.
33627 - Reenable the part of the code that tries to flush as soon as an
33628 OR outbuf has a full TLS record available. Perhaps this will make
33629 OR outbufs not grow as huge except in rare cases, thus saving lots
33630 of CPU time plus memory.
33631 - Reject malformed .onion addresses rather then passing them on as
33632 normal web requests.
33633 - Adapt patch from Adam Langley: fix possible memory leak in
33634 tor_lookup_hostname().
33635 - Initialize libevent later in the startup process, so the logs are
33636 already established by the time we start logging libevent warns.
33637 - Use correct errno on win32 if libevent fails.
33638 - Check and warn about known-bad/slow libevent versions.
33639 - Pay more attention to the ClientOnly config option.
33640 - Have torctl.in/tor.sh.in check for location of su binary (needed
33642 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
33643 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
33644 HttpProxyAuthenticator
33645 - Stop warning about sigpipes in the logs. We're going to
33646 pretend that getting these occasionally is normal and fine.
33647 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
33649 installer screens; and don't put stuff into StartupItems unless
33650 the user asks you to.
33651 - Require servers that use the default dirservers to have public IP
33652 addresses. We have too many servers that are configured with private
33653 IPs and their admins never notice the log entries complaining that
33654 their descriptors are being rejected.
33655 - Add OSX uninstall instructions. An actual uninstall script will
33659 Changes in version 0.1.0.8-rc - 2005-05-23
33661 - It turns out that kqueue on OS X 10.3.9 was causing kernel
33662 panics. Disable kqueue on all OS X Tors.
33663 - Fix RPM: remove duplicate line accidentally added to the rpm
33665 - Disable threads on openbsd too, since its gethostaddr is not
33667 - Tolerate libevent 0.8 since it still works, even though it's
33669 - Enable building on Red Hat 9.0 again.
33670 - Allow the middle hop of the testing circuit to be running any
33671 version, now that most of them have the bugfix to let them connect
33672 to unknown servers. This will allow reachability testing to work
33673 even when 0.0.9.7-0.0.9.9 become obsolete.
33674 - Handle relay cells with rh.length too large. This prevents
33675 a potential attack that could read arbitrary memory (maybe even
33676 keys) from the exit server's process.
33677 - We screwed up the dirport reachability testing when we don't yet
33678 have a cached version of the directory. Hopefully now fixed.
33679 - Clean up router_load_single_router() (used by the controller),
33680 so it doesn't seg fault on error.
33681 - Fix a minor memory leak when somebody establishes an introduction
33682 point at your Tor server.
33683 - If a socks connection ends because read fails, don't warn that
33684 you're not sending a socks reply back.
33687 - Add HttpProxyAuthenticator config option too, that works like
33688 the HttpsProxyAuthenticator config option.
33689 - Encode hashed controller passwords in hex instead of base64,
33690 to make it easier to write controllers.
33693 Changes in version 0.1.0.7-rc - 2005-05-17
33695 - Fix a bug in the OS X package installer that prevented it from
33696 installing on Tiger.
33697 - Fix a script bug in the OS X package installer that made it
33698 complain during installation.
33699 - Find libevent even if it's hiding in /usr/local/ and your
33700 CFLAGS and LDFLAGS don't tell you to look there.
33701 - Be able to link with libevent as a shared library (the default
33702 after 1.0d), even if it's hiding in /usr/local/lib and even
33703 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
33704 assuming you're running gcc. Otherwise fail and give a useful
33706 - Fix a bug in the RPM packager: set home directory for _tor to
33707 something more reasonable when first installing.
33708 - Free a minor amount of memory that is still reachable on exit.
33711 Changes in version 0.1.0.6-rc - 2005-05-14
33713 - Implement --disable-threads configure option. Disable threads on
33714 netbsd by default, because it appears to have no reentrant resolver
33716 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
33717 release (1.1) detects and disables kqueue if it's broken.
33718 - Append default exit policy before checking for implicit internal
33719 addresses. Now we don't log a bunch of complaints on startup
33720 when using the default exit policy.
33721 - Some people were putting "Address " in their torrc, and they had
33722 a buggy resolver that resolved " " to 0.0.0.0. Oops.
33723 - If DataDir is ~/.tor, and that expands to /.tor, then default to
33724 LOCALSTATEDIR/tor instead.
33725 - Fix fragmented-message bug in TorControl.py.
33726 - Resolve a minor bug which would prevent unreachable dirports
33727 from getting suppressed in the published descriptor.
33728 - When the controller gave us a new descriptor, we weren't resolving
33729 it immediately, so Tor would think its address was 0.0.0.0 until
33730 we fetched a new directory.
33731 - Fix an uppercase/lowercase case error in suppressing a bogus
33732 libevent warning on some Linuxes.
33735 - Begin scrubbing sensitive strings from logs by default. Turn off
33736 the config option SafeLogging if you need to do debugging.
33737 - Switch to a new buffer management algorithm, which tries to avoid
33738 reallocing and copying quite as much. In first tests it looks like
33739 it uses *more* memory on average, but less cpu.
33740 - First cut at support for "create-fast" cells. Clients can use
33741 these when extending to their first hop, since the TLS already
33742 provides forward secrecy and authentication. Not enabled on
33744 - When dirservers refuse a router descriptor, we now log its
33745 contactinfo, platform, and the poster's IP address.
33746 - Call tor_free_all instead of connections_free_all after forking, to
33747 save memory on systems that need to fork.
33748 - Whine at you if you're a server and you don't set your contactinfo.
33749 - Implement --verify-config command-line option to check if your torrc
33750 is valid without actually launching Tor.
33751 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
33752 rather than just rejecting it.
33755 Changes in version 0.1.0.5-rc - 2005-04-27
33757 - Stop trying to print a null pointer if an OR conn fails because
33758 we didn't like its cert.
33760 - Switch our internal buffers implementation to use a ring buffer,
33761 to hopefully improve performance for fast servers a lot.
33762 - Add HttpsProxyAuthenticator support (basic auth only), based
33763 on patch from Adam Langley.
33764 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
33765 the fast servers that have been joining lately.
33766 - Give hidden service accesses extra time on the first attempt,
33767 since 60 seconds is often only barely enough. This might improve
33769 - Improve performance for dirservers: stop re-parsing the whole
33770 directory every time you regenerate it.
33771 - Add more debugging info to help us find the weird dns freebsd
33772 pthreads bug; cleaner debug messages to help track future issues.
33775 Changes in version 0.0.9.9 - 2005-04-23
33776 o Bugfixes on 0.0.9.x:
33777 - If unofficial Tor clients connect and send weird TLS certs, our
33778 Tor server triggers an assert. This release contains a minimal
33779 backport from the broader fix that we put into 0.1.0.4-rc.
33782 Changes in version 0.1.0.4-rc - 2005-04-23
33784 - If unofficial Tor clients connect and send weird TLS certs, our
33785 Tor server triggers an assert. Stop asserting, and start handling
33786 TLS errors better in other situations too.
33787 - When the controller asks us to tell it about all the debug-level
33788 logs, it turns out we were generating debug-level logs while
33789 telling it about them, which turns into a bad loop. Now keep
33790 track of whether you're sending a debug log to the controller,
33791 and don't log when you are.
33792 - Fix the "postdescriptor" feature of the controller interface: on
33793 non-complete success, only say "done" once.
33795 - Clients are now willing to load balance over up to 2mB, not 1mB,
33796 of advertised bandwidth capacity.
33797 - Add a NoPublish config option, so you can be a server (e.g. for
33798 testing running Tor servers in other Tor networks) without
33799 publishing your descriptor to the primary dirservers.
33802 Changes in version 0.1.0.3-rc - 2005-04-08
33803 o Improvements on 0.1.0.2-rc:
33804 - Client now retries when streams end early for 'hibernating' or
33805 'resource limit' reasons, rather than failing them.
33806 - More automated handling for dirserver operators:
33807 - Automatically approve nodes running 0.1.0.2-rc or later,
33808 now that the the reachability detection stuff is working.
33809 - Now we allow two unverified servers with the same nickname
33810 but different keys. But if a nickname is verified, only that
33811 nickname+key are allowed.
33812 - If you're an authdirserver connecting to an address:port,
33813 and it's not the OR you were expecting, forget about that
33814 descriptor. If he *was* the one you were expecting, then forget
33815 about all other descriptors for that address:port.
33816 - Allow servers to publish descriptors from 12 hours in the future.
33817 Corollary: only whine about clock skew from the dirserver if
33818 he's a trusted dirserver (since now even verified servers could
33819 have quite wrong clocks).
33820 - Adjust maximum skew and age for rendezvous descriptors: let skew
33821 be 48 hours rather than 90 minutes.
33822 - Efficiency improvements:
33823 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
33824 it much faster to look up a circuit for each relay cell.
33825 - Remove most calls to assert_all_pending_dns_resolves_ok(),
33826 since they're eating our cpu on exit nodes.
33827 - Stop wasting time doing a case insensitive comparison for every
33828 dns name every time we do any lookup. Canonicalize the names to
33829 lowercase and be done with it.
33830 - Start sending 'truncated' cells back rather than destroy cells,
33831 if the circuit closes in front of you. This means we won't have
33832 to abandon partially built circuits.
33833 - Only warn once per nickname from add_nickname_list_to_smartlist
33834 per failure, so an entrynode or exitnode choice that's down won't
33836 - Put a note in the torrc about abuse potential with the default
33838 - Revise control spec and implementation to allow all log messages to
33839 be sent to controller with their severities intact (suggested by
33840 Matt Edman). Update TorControl to handle new log event types.
33841 - Provide better explanation messages when controller's POSTDESCRIPTOR
33843 - Stop putting nodename in the Platform string in server descriptors.
33844 It doesn't actually help, and it is confusing/upsetting some people.
33846 o Bugfixes on 0.1.0.2-rc:
33847 - We were printing the host mask wrong in exit policies in server
33848 descriptors. This isn't a critical bug though, since we were still
33849 obeying the exit policy internally.
33850 - Fix Tor when compiled with libevent but without pthreads: move
33851 connection_unregister() from _connection_free() to
33853 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
33854 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
33855 when we look through the connection array, we'll find any of the
33856 cpu/dnsworkers. This is no good.
33858 o Bugfixes on 0.0.9.8:
33859 - Fix possible bug on threading platforms (e.g. win32) which was
33860 leaking a file descriptor whenever a cpuworker or dnsworker died.
33861 - When using preferred entry or exit nodes, ignore whether the
33862 circuit wants uptime or capacity. They asked for the nodes, they
33864 - chdir() to your datadirectory at the *end* of the daemonize process,
33865 not the beginning. This was a problem because the first time you
33866 run tor, if your datadir isn't there, and you have runasdaemon set
33867 to 1, it will try to chdir to it before it tries to create it. Oops.
33868 - Handle changed router status correctly when dirserver reloads
33869 fingerprint file. We used to be dropping all unverified descriptors
33870 right then. The bug was hidden because we would immediately
33871 fetch a directory from another dirserver, which would include the
33872 descriptors we just dropped.
33873 - When we're connecting to an OR and he's got a different nickname/key
33874 than we were expecting, only complain loudly if we're an OP or a
33875 dirserver. Complaining loudly to the OR admins just confuses them.
33876 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
33877 artificially capped at 500kB.
33880 Changes in version 0.0.9.8 - 2005-04-07
33881 o Bugfixes on 0.0.9.x:
33882 - We have a bug that I haven't found yet. Sometimes, very rarely,
33883 cpuworkers get stuck in the 'busy' state, even though the cpuworker
33884 thinks of itself as idle. This meant that no new circuits ever got
33885 established. Here's a workaround to kill any cpuworker that's been
33886 busy for more than 100 seconds.
33889 Changes in version 0.1.0.2-rc - 2005-04-01
33890 o Bugfixes on 0.1.0.1-rc:
33891 - Fixes on reachability detection:
33892 - Don't check for reachability while hibernating.
33893 - If ORPort is reachable but DirPort isn't, still publish the
33894 descriptor, but zero out DirPort until it's found reachable.
33895 - When building testing circs for ORPort testing, use only
33896 high-bandwidth nodes, so fewer circuits fail.
33897 - Complain about unreachable ORPort separately from unreachable
33898 DirPort, so the user knows what's going on.
33899 - Make sure we only conclude ORPort reachability if we didn't
33900 initiate the conn. Otherwise we could falsely conclude that
33901 we're reachable just because we connected to the guy earlier
33902 and he used that same pipe to extend to us.
33903 - Authdirservers shouldn't do ORPort reachability detection,
33904 since they're in clique mode, so it will be rare to find a
33905 server not already connected to them.
33906 - When building testing circuits, always pick middle hops running
33907 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
33908 bug. (This is a kludge; it will go away when 0.0.9.x becomes
33910 - When we decide we're reachable, actually publish our descriptor
33912 - Fix bug in redirectstream in the controller.
33913 - Fix the state descriptor strings so logs don't claim edge streams
33914 are in a different state than they actually are.
33915 - Use recent libevent features when possible (this only really affects
33916 win32 and osx right now, because the new libevent with these
33917 features hasn't been released yet). Add code to suppress spurious
33919 - Prevent possible segfault in connection_close_unattached_ap().
33920 - Fix newlines on torrc in win32.
33921 - Improve error msgs when tor-resolve fails.
33923 o Improvements on 0.0.9.x:
33924 - New experimental script tor/contrib/ExerciseServer.py (needs more
33925 work) that uses the controller interface to build circuits and
33926 fetch pages over them. This will help us bootstrap servers that
33927 have lots of capacity but haven't noticed it yet.
33928 - New experimental script tor/contrib/PathDemo.py (needs more work)
33929 that uses the controller interface to let you choose whole paths
33931 "<hostname>.<path,separated by dots>.<length of path>.path"
33932 - When we've connected to an OR and handshaked but didn't like
33933 the result, we were closing the conn without sending destroy
33934 cells back for pending circuits. Now send those destroys.
33937 Changes in version 0.0.9.7 - 2005-04-01
33938 o Bugfixes on 0.0.9.x:
33939 - Fix another race crash bug (thanks to Glenn Fink for reporting).
33940 - Compare identity to identity, not to nickname, when extending to
33941 a router not already in the directory. This was preventing us from
33942 extending to unknown routers. Oops.
33943 - Make sure to create OS X Tor user in <500 range, so we aren't
33944 creating actual system users.
33945 - Note where connection-that-hasn't-sent-end was marked, and fix
33946 a few really loud instances of this harmless bug (it's fixed more
33950 Changes in version 0.1.0.1-rc - 2005-03-28
33952 - Add reachability testing. Your Tor server will automatically try
33953 to see if its ORPort and DirPort are reachable from the outside,
33954 and it won't upload its descriptor until it decides they are.
33955 - Handle unavailable hidden services better. Handle slow or busy
33956 hidden services better.
33957 - Add support for CONNECTing through https proxies, with "HttpsProxy"
33959 - New exit policy: accept most low-numbered ports, rather than
33960 rejecting most low-numbered ports.
33961 - More Tor controller support (still experimental). See
33962 http://tor.eff.org/doc/control-spec.txt for all the new features,
33963 including signals to emulate unix signals from any platform;
33964 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
33965 closestream; closecircuit; etc.
33966 - Make nt services work and start on startup on win32 (based on
33967 patch by Matt Edman).
33968 - Add a new AddressMap config directive to rewrite incoming socks
33969 addresses. This lets you, for example, declare an implicit
33970 required exit node for certain sites.
33971 - Add a new TrackHostExits config directive to trigger addressmaps
33972 for certain incoming socks addresses -- for sites that break when
33973 your exit keeps changing (based on patch by Mike Perry).
33974 - Redo the client-side dns cache so it's just an addressmap too.
33975 - Notice when our IP changes, and reset stats/uptime/reachability.
33976 - When an application is using socks5, give him the whole variety of
33977 potential socks5 responses (connect refused, host unreachable, etc),
33978 rather than just "success" or "failure".
33979 - A more sane version numbering system. See
33980 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
33981 - New contributed script "exitlist": a simple python script to
33982 parse directories and find Tor nodes that exit to listed
33984 - New contributed script "privoxy-tor-toggle" to toggle whether
33985 Privoxy uses Tor. Seems to be configured for Debian by default.
33986 - Report HTTP reasons to client when getting a response from directory
33987 servers -- so you can actually know what went wrong.
33988 - New config option MaxAdvertisedBandwidth which lets you advertise
33989 a low bandwidthrate (to not attract as many circuits) while still
33990 allowing a higher bandwidthrate in reality.
33992 o Robustness/stability fixes:
33993 - Make Tor use Niels Provos's libevent instead of its current
33994 poll-but-sometimes-select mess. This will let us use faster async
33995 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
33997 - pthread support now too. This was forced because when we forked,
33998 we ended up wasting a lot of duplicate ram over time. Also switch
33999 to foo_r versions of some library calls to allow reentry and
34001 - Better handling for heterogeneous / unreliable nodes:
34002 - Annotate circuits w/ whether they aim to contain high uptime nodes
34003 and/or high capacity nodes. When building circuits, choose
34005 - This means that every single node in an intro rend circuit,
34006 not just the last one, will have a minimum uptime.
34007 - New config option LongLivedPorts to indicate application streams
34008 that will want high uptime circuits.
34009 - Servers reset uptime when a dir fetch entirely fails. This
34010 hopefully reflects stability of the server's network connectivity.
34011 - If somebody starts his tor server in Jan 2004 and then fixes his
34012 clock, don't make his published uptime be a year.
34013 - Reset published uptime when you wake up from hibernation.
34014 - Introduce a notion of 'internal' circs, which are chosen without
34015 regard to the exit policy of the last hop. Intro and rendezvous
34016 circs must be internal circs, to avoid leaking information. Resolve
34017 and connect streams can use internal circs if they want.
34018 - New circuit pooling algorithm: make sure to have enough circs around
34019 to satisfy any predicted ports, and also make sure to have 2 internal
34020 circs around if we've required internal circs lately (and with high
34021 uptime if we've seen that lately too).
34022 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
34023 which describes how often we retry making new circuits if current
34024 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
34025 how long we're willing to make use of an already-dirty circuit.
34026 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
34027 circ as necessary, if there are any completed ones lying around
34028 when we try to launch one.
34029 - Make hidden services try to establish a rendezvous for 30 seconds,
34030 rather than for n (where n=3) attempts to build a circuit.
34031 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
34032 "ShutdownWaitLength".
34033 - Try to be more zealous about calling connection_edge_end when
34034 things go bad with edge conns in connection.c.
34035 - Revise tor-spec to add more/better stream end reasons.
34036 - Revise all calls to connection_edge_end to avoid sending "misc",
34037 and to take errno into account where possible.
34040 - Fix a race condition that can trigger an assert, when we have a
34041 pending create cell and an OR connection fails right then.
34042 - Fix several double-mark-for-close bugs, e.g. where we were finding
34043 a conn for a cell even if that conn is already marked for close.
34044 - Make sequence of log messages when starting on win32 with no config
34045 file more reasonable.
34046 - When choosing an exit node for a new non-internal circ, don't take
34047 into account whether it'll be useful for any pending x.onion
34048 addresses -- it won't.
34049 - Turn addr_policy_compare from a tristate to a quadstate; this should
34050 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
34051 for google.com" problem.
34052 - Make "platform" string in descriptor more accurate for Win32 servers,
34053 so it's not just "unknown platform".
34054 - Fix an edge case in parsing config options (thanks weasel).
34055 If they say "--" on the commandline, it's not an option.
34056 - Reject odd-looking addresses at the client (e.g. addresses that
34057 contain a colon), rather than having the server drop them because
34059 - tor-resolve requests were ignoring .exit if there was a working circuit
34060 they could use instead.
34061 - REUSEADDR on normal platforms means you can rebind to the port
34062 right after somebody else has let it go. But REUSEADDR on win32
34063 means to let you bind to the port _even when somebody else
34064 already has it bound_! So, don't do that on Win32.
34065 - Change version parsing logic: a version is "obsolete" if it is not
34066 recommended and (1) there is a newer recommended version in the
34067 same series, or (2) there are no recommended versions in the same
34068 series, but there are some recommended versions in a newer series.
34069 A version is "new" if it is newer than any recommended version in
34071 - Stop most cases of hanging up on a socks connection without sending
34075 - Require BandwidthRate to be at least 20kB/s for servers.
34076 - When a dirserver causes you to give a warn, mention which dirserver
34078 - New config option DirAllowPrivateAddresses for authdirservers.
34079 Now by default they refuse router descriptors that have non-IP or
34080 private-IP addresses.
34081 - Stop publishing socksport in the directory, since it's not
34082 actually meant to be public. For compatibility, publish a 0 there
34084 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
34085 smart" value, that is low for servers and high for clients.
34086 - If our clock jumps forward by 100 seconds or more, assume something
34087 has gone wrong with our network and abandon all not-yet-used circs.
34088 - Warn when exit policy implicitly allows local addresses.
34089 - If we get an incredibly skewed timestamp from a dirserver mirror
34090 that isn't a verified OR, don't warn -- it's probably him that's
34092 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
34093 cookies to disk and doesn't log each web request to disk. (Thanks
34094 to Brett Carrington for pointing this out.)
34095 - When a client asks us for a dir mirror and we don't have one,
34096 launch an attempt to get a fresh one.
34097 - If we're hibernating and we get a SIGINT, exit immediately.
34098 - Add --with-dmalloc ./configure option, to track memory leaks.
34099 - And try to free all memory on closing, so we can detect what
34101 - Cache local dns resolves correctly even when they're .exit
34103 - Give a better warning when some other server advertises an
34104 ORPort that is actually an apache running ssl.
34105 - Add "opt hibernating 1" to server descriptor to make it clearer
34106 whether the server is hibernating.
34109 Changes in version 0.0.9.6 - 2005-03-24
34110 o Bugfixes on 0.0.9.x (crashes and asserts):
34111 - Add new end stream reasons to maintenance branch. Fix bug where
34112 reason (8) could trigger an assert. Prevent bug from recurring.
34113 - Apparently win32 stat wants paths to not end with a slash.
34114 - Fix assert triggers in assert_cpath_layer_ok(), where we were
34115 blowing away the circuit that conn->cpath_layer points to, then
34116 checking to see if the circ is well-formed. Backport check to make
34117 sure we dont use the cpath on a closed connection.
34118 - Prevent circuit_resume_edge_reading_helper() from trying to package
34119 inbufs for marked-for-close streams.
34120 - Don't crash on hup if your options->address has become unresolvable.
34121 - Some systems (like OS X) sometimes accept() a connection and tell
34122 you the remote host is 0.0.0.0:0. If this happens, due to some
34123 other mis-features, we get confused; so refuse the conn for now.
34125 o Bugfixes on 0.0.9.x (other):
34126 - Fix harmless but scary "Unrecognized content encoding" warn message.
34127 - Add new stream error reason: TORPROTOCOL reason means "you are not
34128 speaking a version of Tor I understand; say bye-bye to your stream."
34129 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
34130 into the future, now that we are more tolerant of skew. This
34131 resolves a bug where a Tor server would refuse to cache a directory
34132 because all the directories it gets are too far in the future;
34133 yet the Tor server never logs any complaints about clock skew.
34134 - Mac packaging magic: make man pages useable, and do not overwrite
34135 existing torrc files.
34136 - Make OS X log happily to /var/log/tor/tor.log
34139 Changes in version 0.0.9.5 - 2005-02-22
34140 o Bugfixes on 0.0.9.x:
34141 - Fix an assert race at exit nodes when resolve requests fail.
34142 - Stop picking unverified dir mirrors--it only leads to misery.
34143 - Patch from Matt Edman to make NT services work better. Service
34144 support is still not compiled into the executable by default.
34145 - Patch from Dmitri Bely so the Tor service runs better under
34146 the win32 SYSTEM account.
34147 - Make tor-resolve actually work (?) on Win32.
34148 - Fix a sign bug when getrlimit claims to have 4+ billion
34149 file descriptors available.
34150 - Stop refusing to start when bandwidthburst == bandwidthrate.
34151 - When create cells have been on the onion queue more than five
34152 seconds, just send back a destroy and take them off the list.
34155 Changes in version 0.0.9.4 - 2005-02-03
34156 o Bugfixes on 0.0.9:
34157 - Fix an assert bug that took down most of our servers: when
34158 a server claims to have 1 GB of bandwidthburst, don't
34160 - Don't crash as badly if we have spawned the max allowed number
34161 of dnsworkers, or we're out of file descriptors.
34162 - Block more file-sharing ports in the default exit policy.
34163 - MaxConn is now automatically set to the hard limit of max
34164 file descriptors we're allowed (ulimit -n), minus a few for
34166 - Give a clearer message when servers need to raise their
34167 ulimit -n when they start running out of file descriptors.
34168 - SGI Compatibility patches from Jan Schaumann.
34169 - Tolerate a corrupt cached directory better.
34170 - When a dirserver hasn't approved your server, list which one.
34171 - Go into soft hibernation after 95% of the bandwidth is used,
34172 not 99%. This is especially important for daily hibernators who
34173 have a small accounting max. Hopefully it will result in fewer
34174 cut connections when the hard hibernation starts.
34175 - Load-balance better when using servers that claim more than
34176 800kB/s of capacity.
34177 - Make NT services work (experimental, only used if compiled in).
34180 Changes in version 0.0.9.3 - 2005-01-21
34181 o Bugfixes on 0.0.9:
34182 - Backport the cpu use fixes from main branch, so busy servers won't
34183 need as much processor time.
34184 - Work better when we go offline and then come back, or when we
34185 run Tor at boot before the network is up. We do this by
34186 optimistically trying to fetch a new directory whenever an
34187 application request comes in and we think we're offline -- the
34188 human is hopefully a good measure of when the network is back.
34189 - Backport some minimal hidserv bugfixes: keep rend circuits open as
34190 long as you keep using them; actually publish hidserv descriptors
34191 shortly after they change, rather than waiting 20-40 minutes.
34192 - Enable Mac startup script by default.
34193 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
34194 - When you update AllowUnverifiedNodes or FirewallPorts via the
34195 controller's setconf feature, we were always appending, never
34197 - When you update HiddenServiceDir via setconf, it was screwing up
34198 the order of reading the lines, making it fail.
34199 - Do not rewrite a cached directory back to the cache; otherwise we
34200 will think it is recent and not fetch a newer one on startup.
34201 - Workaround for webservers that lie about Content-Encoding: Tor
34202 now tries to autodetect compressed directories and compression
34203 itself. This lets us Proxypass dir fetches through apache.
34206 Changes in version 0.0.9.2 - 2005-01-04
34207 o Bugfixes on 0.0.9 (crashes and asserts):
34208 - Fix an assert on startup when the disk is full and you're logging
34210 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
34211 style address, then we'd crash.
34212 - Fix an assert trigger when the running-routers string we get from
34213 a dirserver is broken.
34214 - Make worker threads start and run on win32. Now win32 servers
34216 - Bandaid (not actually fix, but now it doesn't crash) an assert
34217 where the dns worker dies mysteriously and the main Tor process
34218 doesn't remember anything about the address it was resolving.
34220 o Bugfixes on 0.0.9 (Win32):
34221 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
34222 name out of the warning/assert messages.
34223 - Fix a superficial "unhandled error on read" bug on win32.
34224 - The win32 installer no longer requires a click-through for our
34225 license, since our Free Software license grants rights but does not
34227 - Win32: When connecting to a dirserver fails, try another one
34228 immediately. (This was already working for non-win32 Tors.)
34229 - Stop trying to parse $HOME on win32 when hunting for default
34231 - Make tor-resolve.c work on win32 by calling network_init().
34233 o Bugfixes on 0.0.9 (other):
34234 - Make 0.0.9.x build on Solaris again.
34235 - Due to a fencepost error, we were blowing away the \n when reporting
34236 confvalue items in the controller. So asking for multiple config
34237 values at once couldn't work.
34238 - When listing circuits that are pending on an opening OR connection,
34239 if we're an OR we were listing circuits that *end* at us as
34240 being pending on every listener, dns/cpu worker, etc. Stop that.
34241 - Dirservers were failing to create 'running-routers' or 'directory'
34242 strings if we had more than some threshold of routers. Fix them so
34243 they can handle any number of routers.
34244 - Fix a superficial "Duplicate mark for close" bug.
34245 - Stop checking for clock skew for OR connections, even for servers.
34246 - Fix a fencepost error that was chopping off the last letter of any
34247 nickname that is the maximum allowed nickname length.
34248 - Update URLs in log messages so they point to the new website.
34249 - Fix a potential problem in mangling server private keys while
34250 writing to disk (not triggered yet, as far as we know).
34251 - Include the licenses for other free software we include in Tor,
34252 now that we're shipping binary distributions more regularly.
34255 Changes in version 0.0.9.1 - 2004-12-15
34256 o Bugfixes on 0.0.9:
34257 - Make hibernation actually work.
34258 - Make HashedControlPassword config option work.
34259 - When we're reporting event circuit status to a controller,
34260 don't use the stream status code.
34263 Changes in version 0.0.9 - 2004-12-12
34265 - Clean up manpage and torrc.sample file.
34266 - Clean up severities and text of log warnings.
34268 - Make servers trigger an assert when they enter hibernation.
34271 Changes in version 0.0.9rc7 - 2004-12-08
34272 o Bugfixes on 0.0.9rc:
34273 - Fix a stack-trashing crash when an exit node begins hibernating.
34274 - Avoid looking at unallocated memory while considering which
34275 ports we need to build circuits to cover.
34276 - Stop a sigpipe: when an 'end' cell races with eof from the app,
34277 we shouldn't hold-open-until-flush if the eof arrived first.
34278 - Fix a bug with init_cookie_authentication() in the controller.
34279 - When recommending new-format log lines, if the upper bound is
34280 LOG_ERR, leave it implicit.
34282 o Bugfixes on 0.0.8.1:
34283 - Fix a whole slew of memory leaks.
34284 - Fix isspace() and friends so they still make Solaris happy
34285 but also so they don't trigger asserts on win32.
34286 - Fix parse_iso_time on platforms without strptime (eg win32).
34287 - win32: tolerate extra "readable" events better.
34288 - win32: when being multithreaded, leave parent fdarray open.
34289 - Make unit tests work on win32.
34292 Changes in version 0.0.9rc6 - 2004-12-06
34293 o Bugfixes on 0.0.9pre:
34294 - Clean up some more integer underflow opportunities (not exploitable
34296 - While hibernating, hup should not regrow our listeners.
34297 - Send an end to the streams we close when we hibernate, rather
34298 than just chopping them off.
34299 - React to eof immediately on non-open edge connections.
34301 o Bugfixes on 0.0.8.1:
34302 - Calculate timeout for waiting for a connected cell from the time
34303 we sent the begin cell, not from the time the stream started. If
34304 it took a long time to establish the circuit, we would time out
34305 right after sending the begin cell.
34306 - Fix router_compare_addr_to_addr_policy: it was not treating a port
34307 of * as always matching, so we were picking reject *:* nodes as
34308 exit nodes too. Oops.
34311 - New circuit building strategy: keep a list of ports that we've
34312 used in the past 6 hours, and always try to have 2 circuits open
34313 or on the way that will handle each such port. Seed us with port
34314 80 so web users won't complain that Tor is "slow to start up".
34315 - Make kill -USR1 dump more useful stats about circuits.
34316 - When warning about retrying or giving up, print the address, so
34317 the user knows which one it's talking about.
34318 - If you haven't used a clean circuit in an hour, throw it away,
34319 just to be on the safe side. (This means after 6 hours a totally
34320 unused Tor client will have no circuits open.)
34323 Changes in version 0.0.9rc5 - 2004-12-01
34324 o Bugfixes on 0.0.8.1:
34325 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
34326 - Let resolve conns retry/expire also, rather than sticking around
34328 - If we are using select, make sure we stay within FD_SETSIZE.
34330 o Bugfixes on 0.0.9pre:
34331 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
34332 but doesn't seem to be currently; thanks to Ilja van Sprundel for
34334 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
34335 instead. Impose minima and maxima for all *Period options; impose
34336 even tighter maxima for fetching if we are a caching dirserver.
34337 Clip rather than rejecting.
34338 - Fetch cached running-routers from servers that serve it (that is,
34339 authdirservers and servers running 0.0.9rc5-cvs or later.)
34342 - Accept *:706 (silc) in default exit policy.
34343 - Implement new versioning format for post 0.1.
34344 - Support "foo.nickname.exit" addresses, to let Alice request the
34345 address "foo" as viewed by exit node "nickname". Based on a patch
34347 - Make tor --version --version dump the cvs Id of every file.
34350 Changes in version 0.0.9rc4 - 2004-11-28
34351 o Bugfixes on 0.0.8.1:
34352 - Make windows sockets actually non-blocking (oops), and handle
34353 win32 socket errors better.
34355 o Bugfixes on 0.0.9rc1:
34356 - Actually catch the -USR2 signal.
34359 Changes in version 0.0.9rc3 - 2004-11-25
34360 o Bugfixes on 0.0.8.1:
34361 - Flush the log file descriptor after we print "Tor opening log file",
34362 so we don't see those messages days later.
34364 o Bugfixes on 0.0.9rc1:
34365 - Make tor-resolve work again.
34366 - Avoid infinite loop in tor-resolve if tor hangs up on it.
34367 - Fix an assert trigger for clients/servers handling resolves.
34370 Changes in version 0.0.9rc2 - 2004-11-24
34371 o Bugfixes on 0.0.9rc1:
34372 - I broke socks5 support while fixing the eof bug.
34373 - Allow unitless bandwidths and intervals; they default to bytes
34375 - New servers don't start out hibernating; they are active until
34376 they run out of bytes, so they have a better estimate of how
34377 long it takes, and so their operators can know they're working.
34380 Changes in version 0.0.9rc1 - 2004-11-23
34381 o Bugfixes on 0.0.8.1:
34382 - Finally fix a bug that's been plaguing us for a year:
34383 With high load, circuit package window was reaching 0. Whenever
34384 we got a circuit-level sendme, we were reading a lot on each
34385 socket, but only writing out a bit. So we would eventually reach
34386 eof. This would be noticed and acted on even when there were still
34387 bytes sitting in the inbuf.
34388 - When poll() is interrupted, we shouldn't believe the revents values.
34390 o Bugfixes on 0.0.9pre6:
34391 - Fix hibernate bug that caused pre6 to be broken.
34392 - Don't keep rephist info for routers that haven't had activity for
34393 24 hours. (This matters now that clients have keys, since we track
34395 - Never call close_temp_logs while validating log options.
34396 - Fix backslash-escaping on tor.sh.in and torctl.in.
34399 - Implement weekly/monthly/daily accounting: now you specify your
34400 hibernation properties by
34401 AccountingMax N bytes|KB|MB|GB|TB
34402 AccountingStart day|week|month [day] HH:MM
34403 Defaults to "month 1 0:00".
34404 - Let bandwidth and interval config options be specified as 5 bytes,
34405 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
34406 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
34407 get back to normal.)
34408 - If your requested entry or exit node has advertised bandwidth 0,
34410 - Be more greedy about filling up relay cells -- we try reading again
34411 once we've processed the stuff we read, in case enough has arrived
34412 to fill the last cell completely.
34413 - Apply NT service patch from Osamu Fujino. Still needs more work.
34416 Changes in version 0.0.9pre6 - 2004-11-15
34417 o Bugfixes on 0.0.8.1:
34418 - Fix assert failure on malformed socks4a requests.
34419 - Use identity comparison, not nickname comparison, to choose which
34420 half of circuit-ID-space each side gets to use. This is needed
34421 because sometimes we think of a router as a nickname, and sometimes
34422 as a hex ID, and we can't predict what the other side will do.
34423 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
34424 write() call will fail and we handle it there.
34425 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
34426 and smartlist_len, which are two major profiling offenders.
34428 o Bugfixes on 0.0.9pre5:
34429 - Fix a bug in read_all that was corrupting config files on windows.
34430 - When we're raising the max number of open file descriptors to
34431 'unlimited', don't log that we just raised it to '-1'.
34432 - Include event code with events, as required by control-spec.txt.
34433 - Don't give a fingerprint when clients do --list-fingerprint:
34434 it's misleading, because it will never be the same again.
34435 - Stop using strlcpy in tor_strndup, since it was slowing us
34437 - Remove warn on startup about missing cached-directory file.
34438 - Make kill -USR1 work again.
34439 - Hibernate if we start tor during the "wait for wakeup-time" phase
34440 of an accounting interval. Log our hibernation plans better.
34441 - Authoritative dirservers now also cache their directory, so they
34442 have it on start-up.
34445 - Fetch running-routers; cache running-routers; compress
34446 running-routers; serve compressed running-routers.z
34447 - Add NSI installer script contributed by J Doe.
34448 - Commit VC6 and VC7 workspace/project files.
34449 - Commit a tor.spec for making RPM files, with help from jbash.
34450 - Add contrib/torctl.in contributed by Glenn Fink.
34451 - Implement the control-spec's SAVECONF command, to write your
34452 configuration to torrc.
34453 - Get cookie authentication for the controller closer to working.
34454 - Include control-spec.txt in the tarball.
34455 - When set_conf changes our server descriptor, upload a new copy.
34456 But don't upload it too often if there are frequent changes.
34457 - Document authentication config in man page, and document signals
34459 - Clean up confusing parts of man page and torrc.sample.
34460 - Make expand_filename handle ~ and ~username.
34461 - Use autoconf to enable largefile support where necessary. Use
34462 ftello where available, since ftell can fail at 2GB.
34463 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
34464 log more informatively.
34465 - Give a slightly more useful output for "tor -h".
34466 - Refuse application socks connections to port 0.
34467 - Check clock skew for verified servers, but allow unverified
34468 servers and clients to have any clock skew.
34469 - Break DirFetchPostPeriod into:
34470 - DirFetchPeriod for fetching full directory,
34471 - StatusFetchPeriod for fetching running-routers,
34472 - DirPostPeriod for posting server descriptor,
34473 - RendPostPeriod for posting hidden service descriptors.
34474 - Make sure the hidden service descriptors are at a random offset
34475 from each other, to hinder linkability.
34478 Changes in version 0.0.9pre5 - 2004-11-09
34479 o Bugfixes on 0.0.9pre4:
34480 - Fix a seg fault in unit tests (doesn't affect main program).
34481 - Fix an assert bug where a hidden service provider would fail if
34482 the first hop of his rendezvous circuit was down.
34483 - Hidden service operators now correctly handle version 1 style
34484 INTRODUCE1 cells (nobody generates them still, so not a critical
34486 - If do_hup fails, actually notice.
34487 - Handle more errnos from accept() without closing the listener.
34488 Some OpenBSD machines were closing their listeners because
34489 they ran out of file descriptors.
34490 - Send resolve cells to exit routers that are running a new
34491 enough version of the resolve code to work right.
34492 - Better handling of winsock includes on non-MSV win32 compilers.
34493 - Some people had wrapped their tor client/server in a script
34494 that would restart it whenever it died. This did not play well
34495 with our "shut down if your version is obsolete" code. Now people
34496 don't fetch a new directory if their local cached version is
34498 - Make our autogen.sh work on ksh as well as bash.
34501 - Hibernation: New config option "AccountingMaxKB" lets you
34502 set how many KBytes per month you want to allow your server to
34503 consume. Rather than spreading those bytes out evenly over the
34504 month, we instead hibernate for some of the month and pop up
34505 at a deterministic time, work until the bytes are consumed, then
34506 hibernate again. Config option "MonthlyAccountingStart" lets you
34507 specify which day of the month your billing cycle starts on.
34508 - Control interface: a separate program can now talk to your
34509 client/server over a socket, and get/set config options, receive
34510 notifications of circuits and streams starting/finishing/dying,
34511 bandwidth used, etc. The next step is to get some GUIs working.
34512 Let us know if you want to help out. See doc/control-spec.txt .
34513 - Ship a contrib/tor-control.py as an example script to interact
34514 with the control port.
34515 - "tor --hash-password zzyxz" will output a salted password for
34516 use in authenticating to the control interface.
34517 - New log format in config:
34518 "Log minsev[-maxsev] stdout|stderr|syslog" or
34519 "Log minsev[-maxsev] file /var/foo"
34522 - DirPolicy config option, to let people reject incoming addresses
34523 from their dirserver.
34524 - "tor --list-fingerprint" will list your identity key fingerprint
34526 - Add "pass" target for RedirectExit, to make it easier to break
34527 out of a sequence of RedirectExit rules.
34528 - Clients now generate a TLS cert too, in preparation for having
34529 them act more like real nodes.
34530 - Ship src/win32/ in the tarball, so people can use it to build.
34531 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
34533 - New "router-status" line in directory, to better bind each verified
34534 nickname to its identity key.
34535 - Deprecate unofficial config option abbreviations, and abbreviations
34536 not on the command line.
34537 - Add a pure-C tor-resolve implementation.
34538 - Use getrlimit and friends to ensure we can reach MaxConn (currently
34539 1024) file descriptors.
34541 o Code security improvements, inspired by Ilja:
34542 - Replace sprintf with snprintf. (I think they were all safe, but
34544 - Replace strcpy/strncpy with strlcpy in more places.
34545 - Avoid strcat; use snprintf or strlcat instead.
34546 - snprintf wrapper with consistent (though not C99) overflow behavior.
34549 Changes in version 0.0.9pre4 - 2004-10-17
34550 o Bugfixes on 0.0.9pre3:
34551 - If the server doesn't specify an exit policy, use the real default
34552 exit policy, not reject *:*.
34553 - Ignore fascistfirewall when uploading/downloading hidden service
34554 descriptors, since we go through Tor for those; and when using
34555 an HttpProxy, since we assume it can reach them all.
34556 - When looking for an authoritative dirserver, use only the ones
34557 configured at boot. Don't bother looking in the directory.
34558 - The rest of the fix for get_default_conf_file() on older win32.
34559 - Make 'Routerfile' config option obsolete.
34562 - New 'MyFamily nick1,...' config option for a server to
34563 specify other servers that shouldn't be used in the same circuit
34564 with it. Only believed if nick1 also specifies us.
34565 - New 'NodeFamily nick1,nick2,...' config option for a client to
34566 specify nodes that it doesn't want to use in the same circuit.
34567 - New 'Redirectexit pattern address:port' config option for a
34568 server to redirect exit connections, e.g. to a local squid.
34571 Changes in version 0.0.9pre3 - 2004-10-13
34572 o Bugfixes on 0.0.8.1:
34573 - Better torrc example lines for dirbindaddress and orbindaddress.
34574 - Improved bounds checking on parsed ints (e.g. config options and
34575 the ones we find in directories.)
34576 - Better handling of size_t vs int, so we're more robust on 64
34578 - Fix the rest of the bug where a newly started OR would appear
34579 as unverified even after we've added his fingerprint and hupped
34581 - Fix a bug from 0.0.7: when read() failed on a stream, we would
34582 close it without sending back an end. So 'connection refused'
34583 would simply be ignored and the user would get no response.
34585 o Bugfixes on 0.0.9pre2:
34586 - Serving the cached-on-disk directory to people is bad. We now
34587 provide no directory until we've fetched a fresh one.
34588 - Workaround for bug on windows where cached-directories get crlf
34590 - Make get_default_conf_file() work on older windows too.
34591 - If we write a *:* exit policy line in the descriptor, don't write
34592 any more exit policy lines.
34595 - Use only 0.0.9pre1 and later servers for resolve cells.
34596 - Make the dirservers file obsolete.
34597 - Include a dir-signing-key token in directories to tell the
34598 parsing entity which key is being used to sign.
34599 - Remove the built-in bulky default dirservers string.
34600 - New config option "Dirserver %s:%d [fingerprint]", which can be
34601 repeated as many times as needed. If no dirservers specified,
34602 default to moria1,moria2,tor26.
34603 - Make moria2 advertise a dirport of 80, so people behind firewalls
34604 will be able to get a directory.
34605 - Http proxy support
34606 - Dirservers translate requests for http://%s:%d/x to /x
34607 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
34608 be routed through this host.
34609 - Clients ask for /tor/x rather than /x for new enough dirservers.
34610 This way we can one day coexist peacefully with apache.
34611 - Clients specify a "Host: %s%d" http header, to be compatible
34612 with more proxies, and so running squid on an exit node can work.
34615 Changes in version 0.0.8.1 - 2004-10-13
34617 - Fix a seg fault that can be triggered remotely for Tor
34618 clients/servers with an open dirport.
34619 - Fix a rare assert trigger, where routerinfos for entries in
34620 our cpath would expire while we're building the path.
34621 - Fix a bug in OutboundBindAddress so it (hopefully) works.
34622 - Fix a rare seg fault for people running hidden services on
34623 intermittent connections.
34624 - Fix a bug in parsing opt keywords with objects.
34625 - Fix a stale pointer assert bug when a stream detaches and
34627 - Fix a string format vulnerability (probably not exploitable)
34628 in reporting stats locally.
34629 - Fix an assert trigger: sometimes launching circuits can fail
34630 immediately, e.g. because too many circuits have failed recently.
34631 - Fix a compile warning on 64 bit platforms.
34634 Changes in version 0.0.9pre2 - 2004-10-03
34636 - Make fetching a cached directory work for 64-bit platforms too.
34637 - Make zlib.h a required header, not an optional header.
34640 Changes in version 0.0.9pre1 - 2004-10-01
34642 - Stop using separate defaults for no-config-file and
34643 empty-config-file. Now you have to explicitly turn off SocksPort,
34644 if you don't want it open.
34645 - Fix a bug in OutboundBindAddress so it (hopefully) works.
34646 - Improve man page to mention more of the 0.0.8 features.
34647 - Fix a rare seg fault for people running hidden services on
34648 intermittent connections.
34649 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
34651 - Fix more dns related bugs: send back resolve_failed and end cells
34652 more reliably when the resolve fails, rather than closing the
34653 circuit and then trying to send the cell. Also attach dummy resolve
34654 connections to a circuit *before* calling dns_resolve(), to fix
34655 a bug where cached answers would never be sent in RESOLVED cells.
34656 - When we run out of disk space, or other log writing error, don't
34657 crash. Just stop logging to that log and continue.
34658 - We were starting to daemonize before we opened our logs, so if
34659 there were any problems opening logs, we would complain to stderr,
34660 which wouldn't work, and then mysteriously exit.
34661 - Fix a rare bug where sometimes a verified OR would connect to us
34662 before he'd uploaded his descriptor, which would cause us to
34663 assign conn->nickname as though he's unverified. Now we look through
34664 the fingerprint list to see if he's there.
34665 - Fix a rare assert trigger, where routerinfos for entries in
34666 our cpath would expire while we're building the path.
34669 - Clients can ask dirservers for /dir.z to get a compressed version
34670 of the directory. Only works for servers running 0.0.9, of course.
34671 - Make clients cache directories and use them to seed their router
34672 lists at startup. This means clients have a datadir again.
34673 - Configuration infrastructure support for warning on obsolete
34675 - Respond to content-encoding headers by trying to uncompress as
34677 - Reply with a deflated directory when a client asks for "dir.z".
34678 We could use allow-encodings instead, but allow-encodings isn't
34679 specified in HTTP 1.0.
34680 - Raise the max dns workers from 50 to 100.
34681 - Discourage people from setting their dirfetchpostperiod more often
34682 than once per minute.
34683 - Protect dirservers from overzealous descriptor uploading -- wait
34684 10 seconds after directory gets dirty, before regenerating.
34687 Changes in version 0.0.8 - 2004-08-25
34688 o Port it to SunOS 5.9 / Athena
34691 Changes in version 0.0.8rc2 - 2004-08-20
34692 o Make it compile on cygwin again.
34693 o When picking unverified routers, skip those with low uptime and/or
34694 low bandwidth, depending on what properties you care about.
34697 Changes in version 0.0.8rc1 - 2004-08-18
34698 o Changes from 0.0.7.3:
34700 - Fix assert triggers: if the other side returns an address 0.0.0.0,
34701 don't put it into the client dns cache.
34702 - If a begin failed due to exit policy, but we believe the IP address
34703 should have been allowed, switch that router to exitpolicy reject *:*
34704 until we get our next directory.
34706 - Clients choose nodes proportional to advertised bandwidth.
34707 - Avoid using nodes with low uptime as introduction points.
34708 - Handle servers with dynamic IP addresses: don't replace
34709 options->Address with the resolved one at startup, and
34710 detect our address right before we make a routerinfo each time.
34711 - 'FascistFirewall' option to pick dirservers and ORs on specific
34712 ports; plus 'FirewallPorts' config option to tell FascistFirewall
34713 which ports are open. (Defaults to 80,443)
34714 - Be more aggressive about trying to make circuits when the network
34715 has changed (e.g. when you unsuspend your laptop).
34716 - Check for time skew on http headers; report date in response to
34718 - If the entrynode config line has only one node, don't pick it as
34720 - Add strict{entry|exit}nodes config options. If set to 1, then
34721 we refuse to build circuits that don't include the specified entry
34723 - OutboundBindAddress config option, to bind to a specific
34724 IP address for outgoing connect()s.
34725 - End truncated log entries (e.g. directories) with "[truncated]".
34727 o Patches to 0.0.8preX:
34729 - Patches to compile and run on win32 again (maybe)?
34730 - Fix crash when looking for ~/.torrc with no $HOME set.
34731 - Fix a race bug in the unit tests.
34732 - Handle verified/unverified name collisions better when new
34733 routerinfo's arrive in a directory.
34734 - Sometimes routers were getting entered into the stats before
34735 we'd assigned their identity_digest. Oops.
34736 - Only pick and establish intro points after we've gotten a
34739 - AllowUnverifiedNodes config option to let circuits choose no-name
34740 routers in entry,middle,exit,introduction,rendezvous positions.
34741 Allow middle and rendezvous positions by default.
34742 - Add a man page for tor-resolve.
34745 Changes in version 0.0.7.3 - 2004-08-12
34746 o Stop dnsworkers from triggering an assert failure when you
34747 ask them to resolve the host "".
34750 Changes in version 0.0.8pre3 - 2004-08-09
34751 o Changes from 0.0.7.2:
34752 - Allow multiple ORs with same nickname in routerlist -- now when
34753 people give us one identity key for a nickname, then later
34754 another, we don't constantly complain until the first expires.
34755 - Remember used bandwidth (both in and out), and publish 15-minute
34756 snapshots for the past day into our descriptor.
34757 - You can now fetch $DIRURL/running-routers to get just the
34758 running-routers line, not the whole descriptor list. (But
34759 clients don't use this yet.)
34760 - When people mistakenly use Tor as an http proxy, point them
34761 at the tor-doc.html rather than the INSTALL.
34762 - Remove our mostly unused -- and broken -- hex_encode()
34763 function. Use base16_encode() instead. (Thanks to Timo Lindfors
34764 for pointing out this bug.)
34765 - Rotate onion keys every 12 hours, not every 2 hours, so we have
34766 fewer problems with people using the wrong key.
34767 - Change the default exit policy to reject the default edonkey,
34768 kazaa, gnutella ports.
34769 - Add replace_file() to util.[ch] to handle win32's rename().
34771 o Changes from 0.0.8preX:
34772 - Fix two bugs in saving onion keys to disk when rotating, so
34773 hopefully we'll get fewer people using old onion keys.
34774 - Fix an assert error that was making SocksPolicy not work.
34775 - Be willing to expire routers that have an open dirport -- it's
34776 just the authoritative dirservers we want to not forget.
34777 - Reject tor-resolve requests for .onion addresses early, so we
34778 don't build a whole rendezvous circuit and then fail.
34779 - When you're warning a server that he's unverified, don't cry
34780 wolf unpredictably.
34781 - Fix a race condition: don't try to extend onto a connection
34782 that's still handshaking.
34783 - For servers in clique mode, require the conn to be open before
34784 you'll choose it for your path.
34785 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
34786 end relay cell, etc.
34787 - Measure bandwidth capacity over the last 24 hours, not just 12
34788 - Bugfix: authoritative dirservers were making and signing a new
34789 directory for each client, rather than reusing the cached one.
34792 Changes in version 0.0.8pre2 - 2004-08-04
34793 o Changes from 0.0.7.2:
34795 - Check directory signature _before_ you decide whether you're
34796 you're running an obsolete version and should exit.
34797 - Check directory signature _before_ you parse the running-routers
34798 list to decide who's running or verified.
34799 - Bugfixes and features:
34800 - Check return value of fclose while writing to disk, so we don't
34801 end up with broken files when servers run out of disk space.
34802 - Log a warning if the user uses an unsafe socks variant, so people
34803 are more likely to learn about privoxy or socat.
34804 - Dirservers now include RFC1123-style dates in the HTTP headers,
34805 which one day we will use to better detect clock skew.
34807 o Changes from 0.0.8pre1:
34808 - Make it compile without warnings again on win32.
34809 - Log a warning if you're running an unverified server, to let you
34810 know you might want to get it verified.
34811 - Only pick a default nickname if you plan to be a server.
34814 Changes in version 0.0.8pre1 - 2004-07-23
34816 - Made our unit tests compile again on OpenBSD 3.5, and tor
34817 itself compile again on OpenBSD on a sparc64.
34818 - We were neglecting milliseconds when logging on win32, so
34819 everything appeared to happen at the beginning of each second.
34821 o Protocol changes:
34822 - 'Extend' relay cell payloads now include the digest of the
34823 intended next hop's identity key. Now we can verify that we're
34824 extending to the right router, and also extend to routers we
34825 hadn't heard of before.
34828 - Tor nodes can now act as relays (with an advertised ORPort)
34829 without being manually verified by the dirserver operators.
34830 - Uploaded descriptors of unverified routers are now accepted
34831 by the dirservers, and included in the directory.
34832 - Verified routers are listed by nickname in the running-routers
34833 list; unverified routers are listed as "$<fingerprint>".
34834 - We now use hash-of-identity-key in most places rather than
34835 nickname or addr:port, for improved security/flexibility.
34836 - To avoid Sybil attacks, paths still use only verified servers.
34837 But now we have a chance to play around with hybrid approaches.
34838 - Nodes track bandwidth usage to estimate capacity (not used yet).
34839 - ClientOnly option for nodes that never want to become servers.
34840 - Directory caching.
34841 - "AuthoritativeDir 1" option for the official dirservers.
34842 - Now other nodes (clients and servers) will cache the latest
34843 directory they've pulled down.
34844 - They can enable their DirPort to serve it to others.
34845 - Clients will pull down a directory from any node with an open
34846 DirPort, and check the signature/timestamp correctly.
34847 - Authoritative dirservers now fetch directories from other
34848 authdirservers, to stay better synced.
34849 - Running-routers list tells who's down also, along with noting
34850 if they're verified (listed by nickname) or unverified (listed
34852 - Allow dirservers to serve running-router list separately.
34853 This isn't used yet.
34854 - ORs connect-on-demand to other ORs
34855 - If you get an extend cell to an OR you're not connected to,
34856 connect, handshake, and forward the create cell.
34857 - The authoritative dirservers stay connected to everybody,
34858 and everybody stays connected to 0.0.7 servers, but otherwise
34859 clients/servers expire unused connections after 5 minutes.
34860 - When servers get a sigint, they delay 30 seconds (refusing new
34861 connections) then exit. A second sigint causes immediate exit.
34862 - File and name management:
34863 - Look for .torrc if no CONFDIR "torrc" is found.
34864 - If no datadir is defined, then choose, make, and secure ~/.tor
34866 - If torrc not found, exitpolicy reject *:*.
34867 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
34868 - If no nickname is defined, derive default from hostname.
34869 - Rename secret key files, e.g. identity.key -> secret_id_key,
34870 to discourage people from mailing their identity key to tor-ops.
34871 - Refuse to build a circuit before the directory has arrived --
34872 it won't work anyway, since you won't know the right onion keys
34874 - Try other dirservers immediately if the one you try is down. This
34875 should tolerate down dirservers better now.
34876 - Parse tor version numbers so we can do an is-newer-than check
34877 rather than an is-in-the-list check.
34878 - New socks command 'resolve', to let us shim gethostbyname()
34880 - A 'tor_resolve' script to access the socks resolve functionality.
34881 - A new socks-extensions.txt doc file to describe our
34882 interpretation and extensions to the socks protocols.
34883 - Add a ContactInfo option, which gets published in descriptor.
34884 - Publish OR uptime in descriptor (and thus in directory) too.
34885 - Write tor version at the top of each log file
34886 - New docs in the tarball:
34888 - Document that you should proxy your SSL traffic too.
34891 Changes in version 0.0.7.2 - 2004-07-07
34892 o A better fix for the 0.0.0.0 problem, that will hopefully
34893 eliminate the remaining related assertion failures.
34896 Changes in version 0.0.7.1 - 2004-07-04
34897 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
34898 since internally we use 0.0.0.0 to signify "not yet resolved".
34901 Changes in version 0.0.7 - 2004-06-07
34902 o Updated the man page to reflect the new features.
34905 Changes in version 0.0.7rc2 - 2004-06-06
34906 o Changes from 0.0.7rc1:
34907 - Make it build on Win32 again.
34908 o Changes from 0.0.6.2:
34909 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
34913 Changes in version 0.0.7rc1 - 2004-06-02
34915 - On sighup, we were adding another log without removing the first
34916 one. So log messages would get duplicated n times for n sighups.
34917 - Several cases of using a connection after we'd freed it. The
34918 problem was that connections that are pending resolve are in both
34919 the pending_resolve tree, and also the circuit's resolving_streams
34920 list. When you want to remove one, you must remove it from both.
34921 - Fix a double-mark-for-close where an end cell arrived for a
34922 resolving stream, and then the resolve failed.
34923 - Check directory signatures based on name of signer, not on whom
34924 we got the directory from. This will let us cache directories more
34927 - Crank up some of our constants to handle more users.
34930 Changes in version 0.0.7pre1 - 2004-06-02
34931 o Fixes for crashes and other obnoxious bugs:
34932 - Fix an epipe bug: sometimes when directory connections failed
34933 to connect, we would give them a chance to flush before closing
34935 - When we detached from a circuit because of resolvefailed, we
34936 would immediately try the same circuit twice more, and then
34937 give up on the resolve thinking we'd tried three different
34939 - Limit the number of intro circuits we'll attempt to build for a
34940 hidden service per 15-minute period.
34941 - Check recommended-software string *early*, before actually parsing
34942 the directory. Thus we can detect an obsolete version and exit,
34943 even if the new directory format doesn't parse.
34944 o Fixes for security bugs:
34945 - Remember which nodes are dirservers when you startup, and if a
34946 random OR enables his dirport, don't automatically assume he's
34947 a trusted dirserver.
34949 - Directory connections were asking the wrong poll socket to
34950 start writing, and not asking themselves to start writing.
34951 - When we detached from a circuit because we sent a begin but
34952 didn't get a connected, we would use it again the first time;
34953 but after that we would correctly switch to a different one.
34954 - Stop warning when the first onion decrypt attempt fails; they
34955 will sometimes legitimately fail now that we rotate keys.
34956 - Override unaligned-access-ok check when $host_cpu is ia64 or
34957 arm. Apparently they allow it but the kernel whines.
34958 - Dirservers try to reconnect periodically too, in case connections
34960 - Fix some memory leaks in directory servers.
34961 - Allow backslash in Win32 filenames.
34962 - Made Tor build complain-free on FreeBSD, hopefully without
34963 breaking other BSD builds. We'll see.
34965 - Doxygen markup on all functions and global variables.
34966 - Make directory functions update routerlist, not replace it. So
34967 now directory disagreements are not so critical a problem.
34968 - Remove the upper limit on number of descriptors in a dirserver's
34969 directory (not that we were anywhere close).
34970 - Allow multiple logfiles at different severity ranges.
34971 - Allow *BindAddress to specify ":port" rather than setting *Port
34972 separately. Allow multiple instances of each BindAddress config
34973 option, so you can bind to multiple interfaces if you want.
34974 - Allow multiple exit policy lines, which are processed in order.
34975 Now we don't need that huge line with all the commas in it.
34976 - Enable accept/reject policies on SOCKS connections, so you can bind
34977 to 0.0.0.0 but still control who can use your OP.
34980 Changes in version 0.0.6.2 - 2004-05-16
34981 o Our integrity-checking digest was checking only the most recent cell,
34982 not the previous cells like we'd thought.
34983 Thanks to Stefan Mark for finding the flaw!
34986 Changes in version 0.0.6.1 - 2004-05-06
34987 o Fix two bugs in our AES counter-mode implementation (this affected
34988 onion-level stream encryption, but not TLS-level). It turns
34989 out we were doing something much more akin to a 16-character
34990 polyalphabetic cipher. Oops.
34991 Thanks to Stefan Mark for finding the flaw!
34992 o Retire moria3 as a directory server, and add tor26 as a directory
34996 Changes in version 0.0.6 - 2004-05-02
34997 [version bump only]
35000 Changes in version 0.0.6rc4 - 2004-05-01
35001 o Update the built-in dirservers list to use the new directory format
35002 o Fix a rare seg fault: if a node offering a hidden service attempts
35003 to build a circuit to Alice's rendezvous point and fails before it
35004 reaches the last hop, it retries with a different circuit, but
35006 o Handle windows socket errors correctly.
35009 Changes in version 0.0.6rc3 - 2004-04-28
35010 o Don't expire non-general excess circuits (if we had enough
35011 circuits open, we were expiring rendezvous circuits -- even
35012 when they had a stream attached. oops.)
35013 o Fetch randomness from /dev/urandom better (not via fopen/fread)
35014 o Better debugging for tls errors
35015 o Some versions of openssl have an SSL_pending function that erroneously
35016 returns bytes when there is a non-application record pending.
35017 o Set Content-Type on the directory and hidserv descriptor.
35018 o Remove IVs from cipher code, since AES-ctr has none.
35019 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
35020 o We were using an array of length zero in a few places.
35021 o win32's gethostbyname can't resolve an IP to an IP.
35022 o win32's close can't close a socket.
35025 Changes in version 0.0.6rc2 - 2004-04-26
35026 o Fix a bug where we were closing tls connections intermittently.
35027 It turns out openssl keeps its errors around -- so if an error
35028 happens, and you don't ask about it, and then another openssl
35029 operation happens and succeeds, and you ask if there was an error,
35030 it tells you about the first error. Fun fun.
35031 o Fix a bug that's been lurking since 27 may 03 (!)
35032 When passing back a destroy cell, we would use the wrong circ id.
35033 'Mostly harmless', but still worth fixing.
35034 o Since we don't support truncateds much, don't bother sending them;
35035 just close the circ.
35036 o check for <machine/limits.h> so we build on NetBSD again (I hope).
35037 o don't crash if a conn that sent a begin has suddenly lost its circuit
35038 (this was quite rare).
35041 Changes in version 0.0.6rc1 - 2004-04-25
35042 o We now rotate link (tls context) keys and onion keys.
35043 o CREATE cells now include oaep padding, so you can tell
35044 if you decrypted them correctly.
35045 o Add bandwidthburst to server descriptor.
35046 o Directories now say which dirserver signed them.
35047 o Use a tor_assert macro that logs failed assertions too.
35050 Changes in version 0.0.6pre5 - 2004-04-18
35051 o changes from 0.0.6pre4:
35052 - make tor build on broken freebsd 5.2 installs
35053 - fix a failed assert when you try an intro point, get a nack, and try
35054 a second one and it works.
35055 - when alice uses a port that the hidden service doesn't accept,
35056 it now sends back an end cell (denied by exit policy). otherwise
35057 alice would just have to wait to time out.
35058 - fix another rare bug: when we had tried all the intro
35059 points for a hidden service, we fetched the descriptor
35060 again, but we left our introcirc thinking it had already
35061 sent an intro, so it kept waiting for a response...
35062 - bugfix: when you sleep your hidden-service laptop, as soon
35063 as it wakes up it tries to upload a service descriptor, but
35064 socketpair fails for some reason (localhost not up yet?).
35065 now we simply give up on that upload, and we'll try again later.
35066 i'd still like to find the bug though.
35067 - if an intro circ waiting for an ack dies before getting one, then
35069 - we were reusing stale service descriptors and refetching usable
35073 Changes in version 0.0.6pre4 - 2004-04-14
35074 o changes from 0.0.6pre3:
35075 - when bob fails to connect to the rendezvous point, and his
35076 circ didn't fail because of the rendezvous point itself, then
35077 he retries a couple of times
35078 - we expire introduction and rendezvous circs more thoroughly
35079 (sometimes they were hanging around forever)
35080 - we expire unattached rendezvous streams that have been around
35081 too long (they were sticking around forever).
35082 - fix a measly fencepost error that was crashing everybody with
35086 Changes in version 0.0.6pre3 - 2004-04-14
35087 o changes from 0.0.6pre2:
35088 - make hup work again
35089 - fix some memory leaks for dirservers
35090 - allow more skew in rendezvous descriptor timestamps, to help
35091 handle people like blanu who don't know what time it is
35092 - normal circs are 3 hops, but some rend/intro circs are 4, if
35093 the initiator doesn't get to choose the last hop
35094 - send acks for introductions, so alice can know whether to try
35096 - bob publishes intro points more correctly
35097 o changes from 0.0.5:
35098 - fix an assert trigger that's been plaguing us since the days
35099 of 0.0.2prexx (thanks weasel!)
35100 - retry stream correctly when we fail to connect because of
35101 exit-policy-reject (should try another) or can't-resolve-address
35102 (also should try another, because dns on random internet servers
35104 - when we hup a dirserver and we've *removed* a server from the
35105 approved-routers list, now we remove that server from the
35106 in-memory directories too
35109 Changes in version 0.0.6pre2 - 2004-04-08
35110 o We fixed our base32 implementation. Now it works on all architectures.
35113 Changes in version 0.0.6pre1 - 2004-04-08
35115 - Hidden services and rendezvous points are implemented. Go to
35116 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
35117 hidden services. (This only works via a socks4a proxy such as
35118 Privoxy, and currently it's quite slow.)
35121 Changes in version 0.0.5 - 2004-03-30
35122 [version bump only]
35125 Changes in version 0.0.5rc3 - 2004-03-29
35126 o Install torrc as torrc.sample -- we no longer clobber your
35128 o Re-enable recommendedversion checking (we broke it in rc2, oops)
35129 o Add in a 'notice' log level for things the operator should hear
35130 but that aren't warnings
35133 Changes in version 0.0.5rc2 - 2004-03-29
35134 o Hold socks connection open until reply is flushed (if possible)
35135 o Make exit nodes resolve IPs to IPs immediately, rather than asking
35136 the dns farm to do it.
35137 o Fix c99 aliasing warnings in rephist.c
35138 o Don't include server descriptors that are older than 24 hours in the
35140 o Give socks 'reject' replies their whole 15s to attempt to flush,
35141 rather than seeing the 60s timeout and assuming the flush had failed.
35142 o Clean automake droppings from the cvs repository
35145 Changes in version 0.0.5rc1 - 2004-03-28
35146 o Fix mangled-state bug in directory fetching (was causing sigpipes).
35147 o Only build circuits after we've fetched the directory: clients were
35148 using only the directory servers before they'd fetched a directory.
35149 This also means longer startup time; so it goes.
35150 o Fix an assert trigger where an OP would fail to handshake, and we'd
35151 expect it to have a nickname.
35152 o Work around a tsocks bug: do a socks reject when AP connection dies
35153 early, else tsocks goes into an infinite loop.
35156 Changes in version 0.0.4 - 2004-03-26
35157 o When connecting to a dirserver or OR and the network is down,
35161 Changes in version 0.0.3 - 2004-03-26
35162 o Warn and fail if server chose a nickname with illegal characters
35163 o Port to Solaris and Sparc:
35164 - include missing header fcntl.h
35165 - have autoconf find -lsocket -lnsl automatically
35166 - deal with hardware word alignment
35167 - make uname() work (solaris has a different return convention)
35168 - switch from using signal() to sigaction()
35169 o Preliminary work on reputation system:
35170 - Keep statistics on success/fail of connect attempts; they're published
35171 by kill -USR1 currently.
35172 - Add a RunTesting option to try to learn link state by creating test
35173 circuits, even when SocksPort is off.
35174 - Remove unused open circuits when there are too many.
35177 Changes in version 0.0.2 - 2004-03-19
35178 - Include strlcpy and strlcat for safer string ops
35179 - define INADDR_NONE so we compile (but still not run) on solaris
35182 Changes in version 0.0.2pre27 - 2004-03-14
35184 - Allow internal tor networks (we were rejecting internal IPs,
35185 now we allow them if they're set explicitly).
35186 - And fix a few endian issues.
35189 Changes in version 0.0.2pre26 - 2004-03-14
35191 - If a stream times out after 15s without a connected cell, don't
35192 try that circuit again: try a new one.
35193 - Retry streams at most 4 times. Then give up.
35194 - When a dirserver gets a descriptor from an unknown router, it
35195 logs its fingerprint (so the dirserver operator can choose to
35196 accept it even without mail from the server operator).
35197 - Inform unapproved servers when we reject their descriptors.
35198 - Make tor build on Windows again. It works as a client, who knows
35200 - Clearer instructions in the torrc for how to set up a server.
35201 - Be more efficient about reading fd's when our global token bucket
35202 (used for rate limiting) becomes empty.
35204 - Stop asserting that computers always go forward in time. It's
35206 - When we sent a cell (e.g. destroy) and then marked an OR connection
35207 expired, we might close it before finishing a flush if the other
35208 side isn't reading right then.
35209 - Don't allow dirservers to start if they haven't defined
35210 RecommendedVersions
35211 - We were caching transient dns failures. Oops.
35212 - Prevent servers from publishing an internal IP as their address.
35213 - Address a strcat vulnerability in circuit.c
35216 Changes in version 0.0.2pre25 - 2004-03-04
35218 - Put the OR's IP in its router descriptor, not its fqdn. That way
35219 we'll stop being stalled by gethostbyname for nodes with flaky dns,
35222 - If the user typed in an address that didn't resolve, the server
35226 Changes in version 0.0.2pre24 - 2004-03-03
35228 - Fix an assertion failure in dns.c, where we were trying to dequeue
35229 a pending dns resolve even if it wasn't pending
35230 - Fix a spurious socks5 warning about still trying to write after the
35231 connection is finished.
35232 - Hold certain marked_for_close connections open until they're finished
35233 flushing, rather than losing bytes by closing them too early.
35234 - Correctly report the reason for ending a stream
35235 - Remove some duplicate calls to connection_mark_for_close
35236 - Put switch_id and start_daemon earlier in the boot sequence, so it
35237 will actually try to chdir() to options.DataDirectory
35238 - Make 'make test' exit(1) if a test fails; fix some unit tests
35239 - Make tor fail when you use a config option it doesn't know about,
35240 rather than warn and continue.
35241 - Make --version work
35242 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
35245 Changes in version 0.0.2pre23 - 2004-02-29
35247 - Print a statement when the first circ is finished, so the user
35248 knows it's working.
35249 - If a relay cell is unrecognized at the end of the circuit,
35250 send back a destroy. (So attacks to mutate cells are more
35252 - New config option 'excludenodes' to avoid certain nodes for circuits.
35253 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
35254 so you can collect coredumps there.
35256 - Fix a bug in tls flushing where sometimes data got wedged and
35257 didn't flush until more data got sent. Hopefully this bug was
35258 a big factor in the random delays we were seeing.
35259 - Make 'connected' cells include the resolved IP, so the client
35260 dns cache actually gets populated.
35261 - Disallow changing from ORPort=0 to ORPort>0 on hup.
35262 - When we time-out on a stream and detach from the circuit, send an
35263 end cell down it first.
35264 - Only warn about an unknown router (in exitnodes, entrynodes,
35265 excludenodes) after we've fetched a directory.
35268 Changes in version 0.0.2pre22 - 2004-02-26
35270 - Servers publish less revealing uname information in descriptors.
35271 - More memory tracking and assertions, to crash more usefully when
35273 - If the default torrc isn't there, just use some default defaults.
35274 Plus provide an internal dirservers file if they don't have one.
35275 - When the user tries to use Tor as an http proxy, give them an http
35276 501 failure explaining that we're a socks proxy.
35277 - Dump a new router.desc on hup, to help confused people who change
35278 their exit policies and then wonder why router.desc doesn't reflect
35280 - Clean up the generic tor.sh init script that we ship with.
35282 - If the exit stream is pending on the resolve, and a destroy arrives,
35283 then the stream wasn't getting removed from the pending list. I
35284 think this was the one causing recent server crashes.
35285 - Use a more robust poll on OSX 10.3, since their poll is flaky.
35286 - When it couldn't resolve any dirservers, it was useless from then on.
35287 Now it reloads the RouterFile (or default dirservers) if it has no
35289 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
35290 many users don't even *have* a /usr/local/sbin/.
35293 Changes in version 0.0.2pre21 - 2004-02-18
35295 - There's a ChangeLog file that actually reflects the changelog.
35296 - There's a 'torify' wrapper script, with an accompanying
35297 tor-tsocks.conf, that simplifies the process of using tsocks for
35298 tor. It even has a man page.
35299 - The tor binary gets installed to sbin rather than bin now.
35300 - Retry streams where the connected cell hasn't arrived in 15 seconds
35301 - Clean up exit policy handling -- get the default out of the torrc,
35302 so we can update it without forcing each server operator to fix
35304 - Allow imaps and pop3s in default exit policy
35306 - Prevent picking middleman nodes as the last node in the circuit
35309 Changes in version 0.0.2pre20 - 2004-01-30
35311 - We now have a deb package, and it's in debian unstable. Go to
35312 it, apt-getters. :)
35313 - I've split the TotalBandwidth option into BandwidthRate (how many
35314 bytes per second you want to allow, long-term) and
35315 BandwidthBurst (how many bytes you will allow at once before the cap
35316 kicks in). This better token bucket approach lets you, say, set
35317 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
35318 performance while not exceeding your monthly bandwidth quota.
35319 - Push out a tls record's worth of data once you've got it, rather
35320 than waiting until you've read everything waiting to be read. This
35321 may improve performance by pipelining better. We'll see.
35322 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
35323 from failed circuits (if they haven't been connected yet) and attach
35325 - Expire old streams that haven't managed to connect. Some day we'll
35326 have them reattach to new circuits instead.
35329 - Fix several memory leaks that were causing servers to become bloated
35331 - Fix a few very rare assert triggers. A few more remain.
35332 - Setuid to User _before_ complaining about running as root.
35335 Changes in version 0.0.2pre19 - 2004-01-07
35337 - Fix deadlock condition in dns farm. We were telling a child to die by
35338 closing the parent's file descriptor to him. But newer children were
35339 inheriting the open file descriptor from the parent, and since they
35340 weren't closing it, the socket never closed, so the child never read
35341 eof, so he never knew to exit. Similarly, dns workers were holding
35342 open other sockets, leading to all sorts of chaos.
35343 - New cleaner daemon() code for forking and backgrounding.
35344 - If you log to a file, it now prints an entry at the top of the
35345 logfile so you know it's working.
35346 - The onionskin challenge length was 30 bytes longer than necessary.
35347 - Started to patch up the spec so it's not quite so out of date.
35350 Changes in version 0.0.2pre18 - 2004-01-02
35352 - Fix endian issues with the 'integrity' field in the relay header.
35353 - Fix a potential bug where connections in state
35354 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
35357 Changes in version 0.0.2pre17 - 2003-12-30
35359 - Made --debuglogfile (or any second log file, actually) work.
35360 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
35361 adversary could force us into an infinite loop.
35364 - Each onionskin handshake now includes a hash of the computed key,
35365 to prove the server's identity and help perfect forward secrecy.
35366 - Changed cell size from 256 to 512 bytes (working toward compatibility
35368 - Changed cell length to 2 bytes, and moved it to the relay header.
35369 - Implemented end-to-end integrity checking for the payloads of
35371 - Separated streamid from 'recognized' (otherwise circuits will get
35372 messed up when we try to have streams exit from the middle). We
35373 use the integrity-checking to confirm that a cell is addressed to
35375 - Randomize the initial circid and streamid values, so an adversary who
35376 breaks into a node can't learn how many circuits or streams have
35380 Changes in version 0.0.2pre16 - 2003-12-14
35382 - Fixed a bug that made HUP trigger an assert
35383 - Fixed a bug where a circuit that immediately failed wasn't being
35384 counted as a failed circuit in counting retries.
35387 - Now we close the circuit when we get a truncated cell: otherwise we're
35388 open to an anonymity attack where a bad node in the path truncates
35389 the circuit and then we open streams at him.
35390 - Add port ranges to exit policies
35391 - Add a conservative default exit policy
35392 - Warn if you're running tor as root
35393 - on HUP, retry OR connections and close/rebind listeners
35394 - options.EntryNodes: try these nodes first when picking the first node
35395 - options.ExitNodes: if your best choices happen to include any of
35396 your preferred exit nodes, you choose among just those preferred
35398 - options.ExcludedNodes: nodes that are never picked in path building
35401 Changes in version 0.0.2pre15 - 2003-12-03
35402 o Robustness and bugfixes:
35403 - Sometimes clients would cache incorrect DNS resolves, which would
35404 really screw things up.
35405 - An OP that goes offline would slowly leak all its sockets and stop
35407 - A wide variety of bugfixes in exit node selection, exit policy
35408 handling, and processing pending streams when a new circuit is
35410 - Pick nodes for a path only from those the directory says are up
35411 - Choose randomly from all running dirservers, not always the first one
35412 - Increase allowed http header size for directory fetch.
35413 - Stop writing to stderr (if we're daemonized it will be closed).
35414 - Enable -g always, so cores will be more useful to me.
35415 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
35418 - Wrote a man page. It lists commonly used options.
35421 - Change default loglevel to warn.
35422 - Make PidFile default to null rather than littering in your CWD.
35423 - OnionRouter config option is now obsolete. Instead it just checks
35425 - Moved to a single unified torrc file for both clients and servers.
35428 Changes in version 0.0.2pre14 - 2003-11-29
35429 o Robustness and bugfixes:
35430 - Force the admin to make the DataDirectory himself
35431 - to get ownership/permissions right
35432 - so clients no longer make a DataDirectory and then never use it
35433 - fix bug where a client who was offline for 45 minutes would never
35434 pull down a directory again
35435 - fix (or at least hide really well) the dns assert bug that was
35436 causing server crashes
35437 - warnings and improved robustness wrt clockskew for certs
35438 - use the native daemon(3) to daemonize, when available
35439 - exit if bind() fails
35440 - exit if neither socksport nor orport is defined
35441 - include our own tor_timegm (Win32 doesn't have its own)
35442 - bugfix for win32 with lots of connections
35443 - fix minor bias in PRNG
35444 - make dirserver more robust to corrupt cached directory
35447 - Wrote the design document (woo)
35449 o Circuit building and exit policies:
35450 - Circuits no longer try to use nodes that the directory has told them
35452 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
35453 bitcounts (18.0.0.0/8).
35454 - Make AP connections standby for a circuit if no suitable circuit
35455 exists, rather than failing
35456 - Circuits choose exit node based on addr/port, exit policies, and
35457 which AP connections are standing by
35458 - Bump min pathlen from 2 to 3
35459 - Relay end cells have a payload to describe why the stream ended.
35460 - If the stream failed because of exit policy, try again with a new
35462 - Clients have a dns cache to remember resolved addresses.
35463 - Notice more quickly when we have no working circuits
35466 - APPort is now called SocksPort
35467 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
35469 - RecommendedVersions is now a config variable rather than
35470 hardcoded (for dirservers)
35471 - Reloads config on HUP
35472 - Usage info on -h or --help
35473 - If you set User and Group config vars, it'll setu/gid to them.
35476 Changes in version 0.0.2pre13 - 2003-10-19
35477 o General stability:
35478 - SSL_write no longer fails when it returns WANTWRITE and the number
35479 of bytes in the buf has changed by the next SSL_write call.
35480 - Fix segfault fetching directory when network is down
35481 - Fix a variety of minor memory leaks
35482 - Dirservers reload the fingerprints file on HUP, so I don't have
35483 to take down the network when I approve a new router
35484 - Default server config file has explicit Address line to specify fqdn
35487 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
35488 - Make listener connections not ever alloc bufs
35490 o Autoconf improvements:
35491 - don't clobber an external CFLAGS in ./configure
35492 - Make install now works
35493 - create var/lib/tor on make install
35494 - autocreate a tor.sh initscript to help distribs
35495 - autocreate the torrc and sample-server-torrc with correct paths
35497 o Log files and Daemonizing now work:
35498 - If --DebugLogFile is specified, log to it at -l debug
35499 - If --LogFile is specified, use it instead of commandline
35500 - If --RunAsDaemon is set, tor forks and backgrounds on startup