1 Changes in version 0.3.5.11 - 2020-07-09
2 Tor 0.3.5.11 backports fixes from later tor releases, including several
3 usability, portability, and reliability fixes.
5 This release also fixes TROVE-2020-001, a medium-severity denial of
6 service vulnerability affecting all versions of Tor when compiled with
7 the NSS encryption library. (This is not the default configuration.)
8 Using this vulnerability, an attacker could cause an affected Tor
9 instance to crash remotely. This issue is also tracked as CVE-2020-
10 15572. Anybody running a version of Tor built with the NSS library
11 should upgrade to 0.3.5.11, 0.4.2.8, 0.4.3.6, or 0.4.4.2-alpha
14 o Major bugfixes (NSS, security, backport from 0.4.4.2-alpha):
15 - Fix a crash due to an out-of-bound memory access when Tor is
16 compiled with NSS support. Fixes bug 33119; bugfix on
17 0.3.5.1-alpha. This issue is also tracked as TROVE-2020-001
20 o Major bugfixes (DoS defenses, bridges, pluggable transport, backport from 0.4.3.4-rc):
21 - Fix a bug that was preventing DoS defenses from running on bridges
22 with a pluggable transport. Previously, the DoS subsystem was not
23 given the transport name of the client connection, thus failed to
24 find the GeoIP cache entry for that client address. Fixes bug
25 33491; bugfix on 0.3.3.2-alpha.
27 o Minor features (testing, backport from 0.4.3.4-rc):
28 - The unit tests now support a "TOR_SKIP_TESTCASES" environment
29 variable to specify a list of space-separated test cases that
30 should not be executed. We will use this to disable certain tests
31 that are failing on Appveyor because of mismatched OpenSSL
32 libraries. Part of ticket 33643.
34 o Minor bugfix (CI, Windows, backport from 0.4.4.2-alpha):
35 - Use the correct 64-bit printf format when compiling with MINGW on
36 Appveyor. Fixes bug 40026; bugfix on 0.3.5.5-alpha.
38 o Minor bugfix (relay, configuration, backport from 0.4.3.3-alpha):
39 - Warn if the ContactInfo field is not set, and tell the relay
40 operator that not having a ContactInfo field set might cause their
41 relay to get rejected in the future. Fixes bug 33361; bugfix
44 o Minor bugfixes (client performance, backport from 0.4.4.1-alpha):
45 - Resume use of preemptively-built circuits when UseEntryGuards is set
46 to 0. We accidentally disabled this feature with that config
47 setting, leading to slower load times. Fixes bug 34303; bugfix
50 o Minor bugfixes (compiler compatibility, backport from 0.4.3.5):
51 - Avoid compiler warnings from Clang 10 related to the use of GCC-
52 style "/* falls through */" comments. Both Clang and GCC allow
53 __attribute__((fallthrough)) instead, so that's what we're using
54 now. Fixes bug 34078; bugfix on 0.3.1.3-alpha.
56 o Minor bugfixes (compiler warnings, backport from 0.4.4.2-alpha):
57 - Fix a compiler warning on platforms with 32-bit time_t values.
58 Fixes bug 40028; bugfix on 0.3.2.8-rc.
60 o Minor bugfixes (embedded Tor, backport from 0.4.3.1-alpha):
61 - When starting Tor any time after the first time in a process,
62 register the thread in which it is running as the main thread.
63 Previously, we only did this on Windows, which could lead to bugs
64 like 23081 on non-Windows platforms. Fixes bug 32884; bugfix
67 o Minor bugfixes (key portability, backport from 0.4.3.4-rc):
68 - When reading PEM-encoded key data, tolerate CRLF line-endings even
69 if we are not running on Windows. Previously, non-Windows hosts
70 would reject these line-endings in certain positions, making
71 certain key files hard to move from one host to another. Fixes bug
72 33032; bugfix on 0.3.5.1-alpha.
74 o Minor bugfixes (logging, backport from 0.4.4.2-alpha):
75 - Downgrade a noisy log message that could occur naturally when
76 receiving an extrainfo document that we no longer want. Fixes bug
77 16016; bugfix on 0.2.6.3-alpha.
79 o Minor bugfixes (onion service v3, client, backport from 0.4.3.3-alpha):
80 - Remove a BUG() warning that would cause a stack trace if an onion
81 service descriptor was freed while we were waiting for a
82 rendezvous circuit to complete. Fixes bug 28992; bugfix
85 o Testing (CI, backport from 0.4.3.4-rc):
86 - In our Appveyor Windows CI, copy required DLLs to test and app
87 directories, before running tor's tests. This ensures that tor.exe
88 and test*.exe use the correct version of each DLL. This fix is not
89 required, but we hope it will avoid DLL search issues in future.
90 Fixes bug 33673; bugfix on 0.3.4.2-alpha.
91 - On Appveyor, skip the crypto/openssl_version test, which is
92 failing because of a mismatched library installation. Fix
96 Changes in version 0.3.5.10 - 2020-03-18
97 Tor 0.3.5.10 backports many fixes from later Tor releases, including a
98 fix for TROVE-2020-002, a major denial-of-service vulnerability that
99 affected all released Tor instances since 0.2.1.5-alpha. Using this
100 vulnerability, an attacker could cause Tor instances to consume a huge
101 amount of CPU, disrupting their operations for several seconds or
102 minutes. This attack could be launched by anybody against a relay, or
103 by a directory cache against any client that had connected to it. The
104 attacker could launch this attack as much as they wanted, thereby
105 disrupting service or creating patterns that could aid in traffic
106 analysis. This issue was found by OSS-Fuzz, and is also tracked
109 We do not have reason to believe that this attack is currently being
110 exploited in the wild, but nonetheless we advise everyone to upgrade
111 as soon as packages are available.
113 o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
114 - Fix a denial-of-service bug that could be used by anyone to
115 consume a bunch of CPU on any Tor relay or authority, or by
116 directories to consume a bunch of CPU on clients or hidden
117 services. Because of the potential for CPU consumption to
118 introduce observable timing patterns, we are treating this as a
119 high-severity security issue. Fixes bug 33119; bugfix on
120 0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
121 as TROVE-2020-002 and CVE-2020-10592.
123 o Major bugfixes (linux seccomp sandbox, backport from 0.4.3.1-alpha):
124 - Correct how we use libseccomp. Particularly, stop assuming that
125 rules are applied in a particular order or that more rules are
126 processed after the first match. Neither is the case! In
127 libseccomp <2.4.0 this lead to some rules having no effect.
128 libseccomp 2.4.0 changed how rules are generated, leading to a
129 different ordering, which in turn led to a fatal crash during
130 startup. Fixes bug 29819; bugfix on 0.2.5.1-alpha. Patch by
133 o Minor features (continuous integration, backport from 0.4.3.2-alpha):
134 - Stop allowing failures on the Travis CI stem tests job. It looks
135 like all the stem hangs we were seeing before are now fixed.
138 o Minor bugfixes (bridges, backport from 0.4.3.1-alpha):
139 - Lowercase the configured value of BridgeDistribution before adding
140 it to the descriptor. Fixes bug 32753; bugfix on 0.3.2.3-alpha.
142 o Minor bugfixes (crash, backport from 0.4.2.4-rc):
143 - When running Tor with an option like --verify-config or
144 --dump-config that does not start the event loop, avoid crashing
145 if we try to exit early because of an error. Fixes bug 32407;
146 bugfix on 0.3.3.1-alpha.
148 o Minor bugfixes (logging, backport from 0.4.3.2-alpha):
149 - If we encounter a bug when flushing a buffer to a TLS connection,
150 only log the bug once per invocation of the Tor process.
151 Previously we would log with every occurrence, which could cause
152 us to run out of disk space. Fixes bug 33093; bugfix
155 o Minor bugfixes (onion services v3, backport from 0.4.3.3-alpha):
156 - Fix an assertion failure that could result from a corrupted
157 ADD_ONION control port command. Found by Saibato. Fixes bug 33137;
158 bugfix on 0.3.3.1-alpha. This issue is also tracked
161 o Minor bugfixes (rust, build, backport from 0.4.3.2-alpha):
162 - Fix a syntax warning given by newer versions of Rust that was
163 creating problems for our continuous integration. Fixes bug 33212;
164 bugfix on 0.3.5.1-alpha.
166 o Testing (backport from 0.4.3.1-alpha):
167 - Re-enable the Travis CI macOS Chutney build, but don't let it
168 prevent the Travis job from finishing. (The Travis macOS jobs are
169 slow, so we don't want to have it delay the whole CI process.)
171 - Turn off Tor's Sandbox in Chutney jobs, and run those jobs on
172 Ubuntu Bionic. Turning off the Sandbox is a work-around, until we
173 fix the sandbox errors in 32722. Closes ticket 32240.
175 o Testing (continuous integration, backport from 0.4.3.1-alpha):
176 - Use zstd in our Travis Linux builds. Closes ticket 32242.
178 o Testing (Travis CI, backport from 0.4.3.3-alpha):
179 - Remove a redundant distcheck job. Closes ticket 33194.
180 - Sort the Travis jobs in order of speed: putting the slowest jobs
181 first takes full advantage of Travis job concurrency. Closes
183 - Stop allowing the Chutney IPv6 Travis job to fail. This job was
184 previously configured to fast_finish (which requires
185 - When a Travis chutney job fails, use chutney's new "diagnostics.sh"
186 tool to produce detailed diagnostic output. Closes ticket 32792.
189 Changes in version 0.3.5.9 - 2019-12-09
190 Tor 0.3.5.9 backports serveral fixes from later releases, including
191 several that affect bridge users, relay stability, onion services,
194 o Directory authority changes (backport from 0.4.1.5):
195 - The directory authority "dizum" has a new IP address. Closes
198 o Major bugfixes (bridges, backport from 0.4.1.2-alpha):
199 - Consider our directory information to have changed when our list
200 of bridges changes. Previously, Tor would not re-compute the
201 status of its directory information when bridges changed, and
202 therefore would not realize that it was no longer able to build
203 circuits. Fixes part of bug 29875.
204 - Do not count previously configured working bridges towards our
205 total of working bridges. Previously, when Tor's list of bridges
206 changed, it would think that the old bridges were still usable,
207 and delay fetching router descriptors for the new ones. Fixes part
208 of bug 29875; bugfix on 0.3.0.1-alpha.
210 o Major bugfixes (circuit build, guard, backport from 0.4.1.4-rc):
211 - When considering upgrading circuits from "waiting for guard" to
212 "open", always ignore circuits that are marked for close. Otherwise,
213 we can end up in the situation where a subsystem is notified that
214 a closing circuit has just opened, leading to undesirable
215 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
217 o Major bugfixes (NSS, relay, backport from 0.4.0.4-rc):
218 - When running with NSS, disable TLS 1.2 ciphersuites that use
219 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
220 these ciphersuites don't work -- which caused relays to fail to
221 handshake with one another when these ciphersuites were enabled.
222 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
224 o Major bugfixes (Onion service reachability, backport from 0.4.1.3-alpha):
225 - Properly clean up the introduction point map when circuits change
226 purpose from onion service circuits to pathbias, measurement, or
227 other circuit types. This should fix some service-side instances
228 of introduction point failure. Fixes bug 29034; bugfix
231 o Major bugfixes (onion service v3, backport from 0.4.1.1-alpha):
232 - Fix an unreachable bug in which an introduction point could try to
233 send an INTRODUCE_ACK with a status code that Trunnel would refuse
234 to encode, leading the relay to assert(). We've consolidated the
235 ABI values into Trunnel now. Fixes bug 30454; bugfix
237 - Clients can now handle unknown status codes from INTRODUCE_ACK
238 cells. (The NACK behavior will stay the same.) This will allow us
239 to extend status codes in the future without breaking the normal
240 client behavior. Fixes another part of bug 30454; bugfix
243 o Major bugfixes (torrc parsing, backport from 0.4.2.2-alpha):
244 - Stop ignoring torrc options after an %include directive, when the
245 included directory ends with a file that does not contain any
246 config options (but does contain comments or whitespace). Fixes
247 bug 31408; bugfix on 0.3.1.1-alpha.
249 o Major bugfixes (v3 onion services, backport from 0.4.2.3-alpha):
250 - Onion services now always use the exact number of intro points
251 configured with the HiddenServiceNumIntroductionPoints option (or
252 fewer if nodes are excluded). Before, a service could sometimes
253 pick more intro points than configured. Fixes bug 31548; bugfix
256 o Minor features (address selection, backport from 0.4.0.3-alpha):
257 - Treat the subnet 100.64.0.0/10 as public for some purposes;
258 private for others. This subnet is the RFC 6598 (Carrier Grade
259 NAT) IP range, and is deployed by many ISPs as an alternative to
260 RFC 1918 that does not break existing internal networks. Tor now
261 blocks SOCKS and control ports on these addresses and warns users
262 if client ports or ExtORPorts are listening on a RFC 6598 address.
263 Closes ticket 28525. Patch by Neel Chauhan.
265 o Minor features (bandwidth authority, backport from 0.4.0.4-rc):
266 - Make bandwidth authorities ignore relays that are reported in the
267 bandwidth file with the flag "vote=0". This change allows us to
268 report unmeasured relays for diagnostic reasons without including
269 their bandwidth in the bandwidth authorities' vote. Closes
272 o Minor features (compile-time modules, backport from version 0.4.1.1-alpha):
273 - Add a "--list-modules" command to print a list of which compile-
274 time modules are enabled. Closes ticket 30452.
276 o Minor features (continuous integration, backport from 0.4.0.4-rc):
277 - On Travis Rust builds, cleanup Rust registry and refrain from
278 caching the "target/" directory to speed up builds. Resolves
281 o Minor features (continuous integration, backport from 0.4.0.5):
282 - In Travis, tell timelimit to use stem's backtrace signals, and
283 launch python directly from timelimit, so python receives the
284 signals from timelimit, rather than make. Closes ticket 30117.
286 o Minor features (continuous integration, backport from 0.4.1.1-alpha):
287 - Remove sudo configuration lines from .travis.yml as they are no
288 longer needed with current Travis build environment. Resolves
291 o Minor features (continuous integration, backport from 0.4.1.4-rc):
292 - Our Travis configuration now uses Chutney to run some network
293 integration tests automatically. Closes ticket 29280.
295 o Minor features (continuous integration, backport from 0.4.2.2-alpha):
296 - When building on Appveyor and Travis, pass the "-k" flag to make,
297 so that we are informed of all compilation failures, not just the
298 first one or two. Closes ticket 31372.
300 o Minor features (fallback directory list, backport from 0.4.1.4-rc):
301 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
302 in December 2018 (of which ~122 were still functional), with a
303 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
304 in June 2019. Closes ticket 28795.
306 o Minor features (geoip, backport from 0.4.2.5):
307 - Update geoip and geoip6 to the December 3 2019 Maxmind GeoLite2
308 Country database. Closes ticket 32685.
310 o Minor features (NSS, diagnostic, backport from 0.4.0.4-rc):
311 - Try to log an error from NSS (if there is any) and a more useful
312 description of our situation if we are using NSS and a call to
313 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
315 o Minor features (stem tests, backport from 0.4.2.1-alpha):
316 - Change "make test-stem" so it only runs the stem tests that use
317 tor. This change makes test-stem faster and more reliable. Closes
320 o Minor bugfixes (security, backport from 0.4.0.4-rc):
321 - Verify in more places that we are not about to create a buffer
322 with more than INT_MAX bytes, to avoid possible OOB access in the
323 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
324 fixed by Tobias Stoeckmann.
325 - Fix a potential double free bug when reading huge bandwidth files.
326 The issue is not exploitable in the current Tor network because
327 the vulnerable code is only reached when directory authorities
328 read bandwidth files, but bandwidth files come from a trusted
329 source (usually the authorities themselves). Furthermore, the
330 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
331 which are not used by any of the current authorities. Fixes bug
332 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
335 o Minor bugfix (continuous integration, backport from 0.4.0.4-rc):
336 - Reset coverage state on disk after Travis CI has finished. This
337 should prevent future coverage merge errors from causing the test
338 suite for the "process" subsystem to fail. The process subsystem
339 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
341 - Terminate test-stem if it takes more than 9.5 minutes to run.
342 (Travis terminates the job after 10 minutes of no output.)
343 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
345 o Minor bugfixes (Appveyor CI, backport from 0.4.2.2-alpha):
346 - Avoid spurious errors when Appveyor CI fails before the install step.
347 Fixes bug 31884; bugfix on 0.3.4.2-alpha.
349 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
350 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
351 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
353 o Minor bugfixes (C correctness, backport from 0.4.0.4-rc):
354 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
355 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
358 o Minor bugfixes (circuit isolation, backport from 0.4.1.3-alpha):
359 - Fix a logic error that prevented the SessionGroup sub-option from
360 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
362 o Minor bugfixes (client, onion service v3, backport from 0.4.2.4-rc):
363 - Fix a BUG() assertion that occurs within a very small race window
364 between when a client intro circuit opens and when its descriptor
365 gets cleaned up from the cache. The circuit is now closed early,
366 which will trigger a re-fetch of the descriptor and continue the
367 connection. Fixes bug 28970; bugfix on 0.3.2.1-alpha.
369 o Minor bugfixes (clock skew detection, backport from 0.4.1.5):
370 - Don't believe clock skew results from NETINFO cells that appear to
371 arrive before we sent the VERSIONS cells they are responding to.
372 Previously, we would accept them up to 3 minutes "in the past".
373 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
375 o Minor bugfixes (compilation warning, backport from 0.4.1.5):
376 - Fix a compilation warning on Windows about casting a function
377 pointer for GetTickCount64(). Fixes bug 31374; bugfix
380 o Minor bugfixes (compilation, backport from 0.4.0.2-alpha):
381 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
382 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
384 o Minor bugfixes (compilation, backport from 0.4.1.5):
385 - Avoid using labs() on time_t, which can cause compilation warnings
386 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
388 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
389 - Suppress spurious float-conversion warnings from GCC when calling
390 floating-point classifier functions on FreeBSD. Fixes part of bug
391 31687; bugfix on 0.3.1.5-alpha.
393 o Minor bugfixes (compilation, unusual configurations, backport from 0.4.1.1-alpha):
394 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
395 due to missing declarations of abort(), and prevent other such
396 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
398 o Minor bugfixes (configuration, proxies, backport from 0.4.1.2-alpha):
399 - Fix a bug that prevented us from supporting SOCKS5 proxies that
400 want authentication along with configured (but unused!)
401 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
403 o Minor bugfixes (connections, backport from 0.4.2.3-rc):
404 - Avoid trying to read data from closed connections, which can cause
405 needless loops in Libevent and infinite loops in Shadow. Fixes bug
406 30344; bugfix on 0.1.1.1-alpha.
408 o Minor bugfixes (continuous integration, backport from 0.4.1.3-alpha):
409 - Allow the test-stem job to fail in Travis, because it sometimes
410 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
411 - Skip test_rebind on macOS in Travis, because it is unreliable on
412 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
413 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
414 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
416 o Minor bugfixes (crash on exit, backport from 0.4.1.4-rc):
417 - Avoid a set of possible code paths that could try to use freed
418 memory in routerlist_free() while Tor was exiting. Fixes bug
419 31003; bugfix on 0.1.2.2-alpha.
421 o Minor bugfixes (directory authorities, backport from 0.4.1.3-alpha):
422 - Stop crashing after parsing an unknown descriptor purpose
423 annotation. We think this bug can only be triggered by modifying a
424 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
426 o Minor bugfixes (directory authority, backport from 0.4.1.2-alpha):
427 - Move the "bandwidth-file-headers" line in directory authority
428 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
431 o Minor bugfixes (error handling, backport from 0.4.2.1-alpha):
432 - On abort, try harder to flush the output buffers of log messages.
433 On some platforms (macOS), log messages could be discarded when
434 the process terminates. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
435 - Report the tor version whenever an assertion fails. Previously, we
436 only reported the Tor version on some crashes, and some non-fatal
437 assertions. Fixes bug 31571; bugfix on 0.3.5.1-alpha.
439 o Minor bugfixes (FreeBSD, PF-based proxy, IPv6, backport from 0.4.2.1-alpha):
440 - When extracting an IPv6 address from a PF-based proxy, verify that
441 we are actually configured to receive an IPv6 address, and log an
442 internal error if not. Fixes part of bug 31687; bugfix
445 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
446 - When tor is missing descriptors for some primary entry guards,
447 make the log message less alarming. It's normal for descriptors to
448 expire, as long as tor fetches new ones soon after. Fixes bug
449 31657; bugfix on 0.3.3.1-alpha.
451 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
452 - Avoid logging that we are relaxing a circuit timeout when that
453 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
455 o Minor bugfixes (logging, backport from 0.4.0.3-alpha):
456 - Correct a misleading error message when IPv4Only or IPv6Only is
457 used but the resolved address can not be interpreted as an address
458 of the specified IP version. Fixes bug 13221; bugfix on
459 0.2.3.9-alpha. Patch from Kris Katterjohn.
460 - Log the correct port number for listening sockets when "auto" is
461 used to let Tor pick the port number. Previously, port 0 was
462 logged instead of the actual port number. Fixes bug 29144; bugfix
463 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
464 - Stop logging a BUG() warning when Tor is waiting for exit
465 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
467 o Minor bugfixes (logging, backport from 0.4.1.1-alpha):
468 - Do not log a warning when running with an OpenSSL version other
469 than the one Tor was compiled with, if the two versions should be
470 compatible. Previously, we would warn whenever the version was
471 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
473 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
474 - Change log level of message "Hash of session info was not as
475 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
478 o Minor bugfixes (logging, backport from 0.4.2.2-alpha):
479 - Rate-limit our the logging message about the obsolete .exit
480 notation. Previously, there was no limit on this warning, which
481 could potentially be triggered many times by a hostile website.
482 Fixes bug 31466; bugfix on 0.2.2.1-alpha.
484 o Minor bugfixes (logging, protocol violations, backport from 0.4.2.2-alpha):
485 - Do not log a nonfatal assertion failure when receiving a VERSIONS
486 cell on a connection using the obsolete v1 link protocol. Log a
487 protocol_warn instead. Fixes bug 31107; bugfix on 0.2.4.4-alpha.
489 o Minor bugfixes (mainloop, periodic events, in-process API, backport from 0.4.2.3-alpha):
490 - Reset the periodic events' "enabled" flag when Tor is shut down
491 cleanly. Previously, this flag was left on, which caused periodic
492 events not to be re-enabled when Tor was relaunched in-process
493 with tor_api.h after a shutdown. Fixes bug 32058; bugfix
496 o Minor bugfixes (memory leak, backport from 0.4.1.1-alpha):
497 - Avoid a minor memory leak that could occur on relays when failing
498 to create a "keys" directory. Fixes bug 30148; bugfix
501 o Minor bugfixes (memory leak, backport from 0.4.1.4-rc):
502 - Fix a trivial memory leak when parsing an invalid value
503 from a download schedule in the configuration. Fixes bug
504 30894; bugfix on 0.3.4.1-alpha.
506 o Minor bugfixes (memory management, backport from 0.4.0.3-alpha):
507 - Refactor the shared random state's memory management so that it
508 actually takes ownership of the shared random value pointers.
509 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
511 o Minor bugfixes (memory management, testing, backport from 0.4.0.3-alpha):
512 - Stop leaking parts of the shared random state in the shared-random
513 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
515 o Minor bugfixes (onion services, backport from 0.4.1.1-alpha):
516 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
517 implemenation) when failing to load an onion service client
518 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
520 o Minor bugfixes (out-of-memory handler, backport from 0.4.1.2-alpha):
521 - When purging the DNS cache because of an out-of-memory condition,
522 try purging just the older entries at first. Previously, we would
523 always purge the whole thing. Fixes bug 29617; bugfix
526 o Minor bugfixes (portability, backport from 0.4.1.2-alpha):
527 - Avoid crashing in our tor_vasprintf() implementation on systems
528 that define neither vasprintf() nor _vscprintf(). (This bug has
529 been here long enough that we question whether people are running
530 Tor on such systems, but we're applying the fix out of caution.)
531 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
534 o Minor bugfixes (relay, backport from 0.4.2.2-alpha):
535 - Avoid crashing when starting with a corrupt keys directory where
536 the old ntor key and the new ntor key are identical. Fixes bug
537 30916; bugfix on 0.2.4.8-alpha.
539 o Minor bugfixes (rust, backport from 0.4.0.5):
540 - Abort on panic in all build profiles, instead of potentially
541 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
543 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
544 - Correctly exclude a redundant rust build job in Travis. Fixes bug
545 31463; bugfix on 0.3.5.4-alpha.
547 o Minor bugfixes (single onion services, backport from 0.4.0.3-alpha):
548 - Allow connections to single onion services to remain idle without
549 being disconnected. Previously, relays acting as rendezvous points
550 for single onion services were mistakenly closing idle rendezvous
551 circuits after 60 seconds, thinking that they were unused
552 directory-fetching circuits that had served their purpose. Fixes
553 bug 29665; bugfix on 0.2.1.26.
555 o Minor bugfixes (stats, backport from 0.4.0.3-alpha):
556 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
557 relay and bridge extra-info documents. Fixes bug 29017; bugfix
560 o Minor bugfixes (testing, backport from 0.4.0.3-alpha):
561 - Downgrade some LOG_ERR messages in the address/* tests to
562 warnings. The LOG_ERR messages were occurring when we had no
563 configured network. We were failing the unit tests, because we
564 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
565 29530; bugfix on 0.3.5.8.
566 - Fix our gcov wrapper script to look for object files at the
567 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
569 o Minor bugfixes (testing, backport from 0.4.0.4-rc):
570 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
571 recent test-network.sh to use new chutney features in CI. Fixes
572 bug 29703; bugfix on 0.2.9.1-alpha.
573 - Fix a test failure on Windows caused by an unexpected "BUG"
574 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
577 o Minor bugfixes (testing, backport from 0.4.2.3-alpha):
578 - When testing port rebinding, don't busy-wait for tor to log.
579 Instead, actually sleep for a short time before polling again.
580 Also improve the formatting of control commands and log messages.
581 Fixes bug 31837; bugfix on 0.3.5.1-alpha.
583 o Minor bugfixes (TLS protocol, backport form 0.4.0.4-rc):
584 - When classifying a client's selection of TLS ciphers, if the
585 client ciphers are not yet available, do not cache the result.
586 Previously, we had cached the unavailability of the cipher list
587 and never looked again, which in turn led us to assume that the
588 client only supported the ancient V1 link protocol. This, in turn,
589 was causing Stem integration tests to stall in some cases. Fixes
590 bug 30021; bugfix on 0.2.4.8-alpha.
592 o Minor bugfixes (tls, logging, backport from 0.4.2.3-alpha):
593 - Log bugs about the TLS read buffer's length only once, rather than
594 filling the logs with similar warnings. Fixes bug 31939; bugfix
597 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
598 - Always retry v2 single onion service intro and rend circuits with
599 a 3-hop path. Previously, v2 single onion services used a 3-hop
600 path when rendezvous circuits were retried after a remote or
601 delayed failure, but a 1-hop path for immediate retries. Fixes bug
602 23818; bugfix on 0.2.9.3-alpha.
603 - Make v3 single onion services fall back to a 3-hop intro, when all
604 intro points are unreachable via a 1-hop path. Previously, v3
605 single onion services failed when all intro nodes were unreachable
606 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
608 o Minor bugfixes (Windows, CI, backport from 0.4.0.3-alpha):
609 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
610 Windows Server 2012 R2 job. The remaining 2 jobs still provide
611 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
612 fast_finish, so failed jobs terminate the build immediately. Fixes
613 bug 29601; bugfix on 0.3.5.4-alpha.
615 o Documentation (backport from 0.4.2.1-alpha):
616 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
617 notice.html so that operators no longer have to host it
618 themselves. Closes ticket 31089.
620 o Testing (backport from 0.4.1.2-alpha):
621 - Specify torrc paths (with empty files) when launching tor in
622 integration tests; refrain from reading user and system torrcs.
623 Resolves issue 29702.
625 o Testing (continuous integration, backport from 0.4.1.1-alpha):
626 - In Travis, show stem's tor log after failure. Closes ticket 30234.
628 o Testing (continuous integration, backport from 0.4.1.5):
629 - In Travis, make stem log a controller trace to the console, and
630 tail stem's tor log after failure. Closes ticket 30591.
631 - In Travis, only run the stem tests that use a tor binary. Closes
634 o Testing (continuous integration, backport from 0.4.2.3-alpha):
635 - Disable all but one Travis CI macOS build, to mitigate slow
636 scheduling of Travis macOS jobs. Closes ticket 32177.
637 - Run the chutney IPv6 networks as part of Travis CI. Closes
639 - Simplify the Travis CI build matrix, and optimise for build time.
641 - Use Windows Server 2019 instead of Windows Server 2016 in our
642 Appveyor builds. Closes ticket 32086.
644 o Testing (continuous integration, backport from 0.4.2.4-rc):
645 - Use Ubuntu Bionic images for our Travis CI builds, so we can get a
646 recent version of coccinelle. But leave chutney on Ubuntu Trusty,
647 until we can fix some Bionic permissions issues (see ticket
648 32240). Related to ticket 31919.
649 - Install the mingw OpenSSL package in Appveyor. This makes sure
650 that the OpenSSL headers and libraries match in Tor's Appveyor
651 builds. (This bug was triggered by an Appveyor image update.)
652 Fixes bug 32449; bugfix on 0.3.5.6-rc.
653 - In Travis, use Xcode 11.2 on macOS 10.14. Closes ticket 32241.
655 o Testing (continuous integration, backport from 0.4.2.5):
656 - Require C99 standards-conforming code in Travis CI, but allow GNU gcc
657 extensions. Also activates clang's -Wtypedef-redefinition warnings.
658 Build some jobs with -std=gnu99, and some jobs without.
662 Changes in version 0.3.5.8 - 2019-02-21
663 Tor 0.3.5.8 backports serveral fixes from later releases, including fixes
664 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
667 It also includes a fix for a medium-severity security bug affecting Tor
668 0.3.2.1-alpha and later. All Tor instances running an affected release
669 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
671 o Major bugfixes (cell scheduler, KIST, security):
672 - Make KIST consider the outbuf length when computing what it can
673 put in the outbuf. Previously, KIST acted as though the outbuf
674 were empty, which could lead to the outbuf becoming too full. It
675 is possible that an attacker could exploit this bug to cause a Tor
676 client or relay to run out of memory and crash. Fixes bug 29168;
677 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
678 TROVE-2019-001 and CVE-2019-8955.
680 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
681 - Gracefully handle empty username/password fields in SOCKS5
682 username/password auth messsage and allow SOCKS5 handshake to
683 continue. Previously, we had rejected these handshakes, breaking
684 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
686 o Minor features (compilation, backport from 0.4.0.2-alpha):
687 - Compile correctly when OpenSSL is built with engine support
688 disabled, or with deprecated APIs disabled. Closes ticket 29026.
689 Patches from "Mangix".
691 o Minor features (geoip):
692 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
693 Country database. Closes ticket 29478.
695 o Minor features (testing, backport from 0.4.0.2-alpha):
696 - Treat all unexpected ERR and BUG messages as test failures. Closes
699 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
700 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
701 connection waiting for a descriptor that we actually have in the
702 cache. It turns out that this can actually happen, though it is
703 rare. Now, tor will recover and retry the descriptor. Fixes bug
704 28669; bugfix on 0.3.2.4-alpha.
706 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
707 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
708 IPv6 socket was bound using an address family of AF_INET instead
709 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
712 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
713 - Update Cargo.lock file to match the version made by the latest
714 version of Rust, so that "make distcheck" will pass again. Fixes
715 bug 29244; bugfix on 0.3.3.4-alpha.
717 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
718 - Select guards even if the consensus has expired, as long as the
719 consensus is still reasonably live. Fixes bug 24661; bugfix
722 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
723 - Compile correctly on OpenBSD; previously, we were missing some
724 headers required in order to detect it properly. Fixes bug 28938;
725 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
727 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
728 - Describe the contents of the v3 onion service client authorization
729 files correctly: They hold public keys, not private keys. Fixes
730 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
732 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
733 - Rework rep_hist_log_link_protocol_counts() to iterate through all
734 link protocol versions when logging incoming/outgoing connection
735 counts. Tor no longer skips version 5, and we won't have to
736 remember to update this function when new link protocol version is
737 developed. Fixes bug 28920; bugfix on 0.2.6.10.
739 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
740 - Log more information at "warning" level when unable to read a
741 private key; log more information at "info" level when unable to
742 read a public key. We had warnings here before, but they were lost
743 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
745 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
746 - The amount of total available physical memory is now determined
747 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
748 when it is defined and a 64-bit variant is not available. Fixes
749 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
751 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
752 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
753 than one private key for a hidden service. Fixes bug 29040; bugfix
755 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
756 "debug" level. Tor used to log it as a warning, which caused very
757 long log lines to appear for some users. Fixes bug 29135; bugfix
759 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
760 as a warning. Instead, log it as a protocol warning, because there
761 is nothing that relay operators can do to fix it. Fixes bug 29029;
762 bugfix on 0.2.5.7-rc.
764 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
765 - Mark outdated dirservers when Tor only has a reasonably live
766 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
768 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
769 - Detect and suppress "bug" warnings from the util/time test on
770 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
771 - Do not log an error-level message if we fail to find an IPv6
772 network interface from the unit tests. Fixes bug 29160; bugfix
775 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
776 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
777 Some users took this phrasing to mean that the mentioned guard was
778 under their control or responsibility, which it is not. Fixes bug
779 28895; bugfix on Tor 0.3.0.1-alpha.
782 Changes in version 0.3.5.7 - 2019-01-07
783 Tor 0.3.5.7 is the first stable release in its series; it includes
784 compilation and portability fixes, and a fix for a severe problem
785 affecting directory caches.
787 The Tor 0.3.5 series includes several new features and performance
788 improvements, including client authorization for v3 onion services,
789 cleanups to bootstrap reporting, support for improved bandwidth-
790 measurement tools, experimental support for NSS in place of OpenSSL,
791 and much more. It also begins a full reorganization of Tor's code
792 layout, for improved modularity and maintainability in the future.
793 Finally, there is the usual set of performance improvements and
794 bugfixes that we try to do in every release series.
796 There are a couple of changes in the 0.3.5 that may affect
797 compatibility. First, the default version for newly created onion
798 services is now v3. Use the HiddenServiceVersion option if you want to
799 override this. Second, some log messages related to bootstrapping have
800 changed; if you use stem, you may need to update to the latest version
801 so it will recognize them.
803 We have designated 0.3.5 as a "long-term support" (LTS) series: we
804 will continue to patch major bugs in typical configurations of 0.3.5
805 until at least 1 Feb 2022. (We do not plan to provide long-term
806 support for embedding, Rust support, NSS support, running a directory
807 authority, or unsupported platforms. For these, you will need to stick
808 with the latest stable release.)
810 Below are the changes since 0.3.5.6-rc. For a complete list of changes
811 since 0.3.4.9, see the ReleaseNotes file.
813 o Major bugfixes (relay, directory):
814 - Always reactivate linked connections in the main loop so long as
815 any linked connection has been active. Previously, connections
816 serving directory information wouldn't get reactivated after the
817 first chunk of data was sent (usually 32KB), which would prevent
818 clients from bootstrapping. Fixes bug 28912; bugfix on
819 0.3.4.1-alpha. Patch by "cypherpunks3".
821 o Minor features (compilation):
822 - When possible, place our warning flags in a separate file, to
823 avoid flooding verbose build logs. Closes ticket 28924.
825 o Minor features (geoip):
826 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
827 Country database. Closes ticket 29012.
829 o Minor features (OpenSSL bug workaround):
830 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
831 key export function from handling long labels. When this bug is
832 detected, Tor will disable TLS 1.3. We recommend upgrading to a
833 version of OpenSSL without this bug when it becomes available.
836 o Minor features (performance):
837 - Remove about 96% of the work from the function that we run at
838 startup to test our curve25519_basepoint implementation. Since
839 this function has yet to find an actual failure, we now only run
840 it for 8 iterations instead of 200. Based on our profile
841 information, this change should save around 8% of our startup time
842 on typical desktops, and may have a similar effect on other
843 platforms. Closes ticket 28838.
844 - Stop re-validating our hardcoded Diffie-Hellman parameters on
845 every startup. Doing this wasted time and cycles, especially on
846 low-powered devices. Closes ticket 28851.
848 o Minor bugfixes (compilation):
849 - Fix compilation for Android by adding a missing header to
850 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
852 o Minor bugfixes (correctness):
853 - Fix an unreached code path where we checked the value of
854 "hostname" inside send_resolved_hostname_cell(). Previously, we
855 used it before checking it; now we check it first. Fixes bug
856 28879; bugfix on 0.1.2.7-alpha.
858 o Minor bugfixes (testing):
859 - Make sure that test_rebind.py actually obeys its timeout, even
860 when it receives a large number of log messages. Fixes bug 28883;
861 bugfix on 0.3.5.4-alpha.
862 - Stop running stem's unit tests as part of "make test-stem", but
863 continue to run stem's unit and online tests during "make test-
864 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
866 o Minor bugfixes (windows services):
867 - Make Tor start correctly as an NT service again: previously it was
868 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
870 o Code simplification and refactoring:
871 - When parsing a port configuration, make it more obvious to static
872 analyzer tools that we always initialize the address. Closes
876 Changes in version 0.3.5.6-rc - 2018-12-18
877 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
878 It is the first release candidate in the 0.3.5.x series; if no further
879 huge bugs are found, our next release may be the stable 0.3.5.x.
881 o Minor features (continuous integration, Windows):
882 - Always show the configure and test logs, and upload them as build
883 artifacts, when building for Windows using Appveyor CI.
886 o Minor features (fallback directory list):
887 - Replace the 150 fallbacks originally introduced in Tor
888 0.3.3.1-alpha in January 2018 (of which ~115 were still
889 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
890 removed) generated in December 2018. Closes ticket 24803.
892 o Minor features (geoip):
893 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
894 Country database. Closes ticket 28744.
896 o Minor bugfixes (compilation):
897 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
898 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
900 o Minor bugfixes (continuous integration, Windows):
901 - Explicitly specify the path to the OpenSSL library and do not
902 download OpenSSL from Pacman, but instead use the library that is
903 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
905 o Minor bugfixes (onion service v3):
906 - When deleting an ephemeral onion service (DEL_ONION), do not close
907 any rendezvous circuits in order to let the existing client
908 connections finish by themselves or closed by the application. The
909 HS v2 is doing that already so now we have the same behavior for
910 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
912 o Minor bugfixes (restart-in-process, boostrap):
913 - Add missing resets of bootstrap tracking state when shutting down
914 (regression caused by ticket 27169). Fixes bug 28524; bugfix
917 o Minor bugfixes (testing):
918 - Use a separate DataDirectory for the test_rebind script.
919 Previously, this script would run using the default DataDirectory,
920 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
921 Patch from Taylor R Campbell.
922 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
923 bugfix on 0.3.0.1-alpha.
925 o Minor bugfixes (Windows):
926 - Correctly identify Windows 8.1, Windows 10, and Windows Server
927 2008 and later from their NT versions. Fixes bug 28096; bugfix on
928 0.2.2.34; reported by Keifer Bly.
929 - On recent Windows versions, the GetVersionEx() function may report
930 an earlier Windows version than the running OS. To avoid user
931 confusion, add "[or later]" to Tor's version string on affected
932 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
934 - Remove Windows versions that were never supported by the
935 GetVersionEx() function. Stop duplicating the latest Windows
936 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
937 reported by Keifer Bly.
940 - Increase logging and tag all log entries with timestamps in
941 test_rebind.py. Provides diagnostics for issue 28229.
943 o Code simplification and refactoring (shared random, dirauth):
944 - Change many tor_assert() to use BUG() instead. The idea is to not
945 crash a dirauth but rather scream loudly with a stacktrace and let
946 it continue run. The shared random subsystem is very resilient and
947 if anything wrong happens with it, at worst a non coherent value
948 will be put in the vote and discarded by the other authorities.
951 o Documentation (onion services):
952 - Document in the man page that changing ClientOnionAuthDir value or
953 adding a new file in the directory will not work at runtime upon
954 sending a HUP if Sandbox 1. Closes ticket 28128.
955 - Note in the man page that the only real way to fully revoke an
956 onion service v3 client authorization is by restarting the tor
957 process. Closes ticket 28275.
960 Changes in version 0.3.5.5-alpha - 2018-11-16
961 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
962 including several that we hope to backport to older release series in
965 o Major bugfixes (OpenSSL, portability):
966 - Fix our usage of named groups when running as a TLS 1.3 client in
967 OpenSSL 1.1.1. Previously, we only initialized EC groups when
968 running as a relay, which caused clients to fail to negotiate TLS
969 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
972 o Minor features (geoip):
973 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
974 Country database. Closes ticket 28395.
976 o Minor bugfixes (compilation):
977 - Initialize a variable unconditionally in aes_new_cipher(), since
978 some compilers cannot tell that we always initialize it before
979 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
981 o Minor bugfixes (connection, relay):
982 - Avoid a logging a BUG() stacktrace when closing connection held
983 open because the write side is rate limited but not the read side.
984 Now, the connection read side is simply shut down until Tor is
985 able to flush the connection and close it. Fixes bug 27750; bugfix
988 o Minor bugfixes (continuous integration, Windows):
989 - Manually configure the zstd compiler options, when building using
990 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
991 not come with a pkg-config file. Fixes bug 28454; bugfix
993 - Stop using an external OpenSSL install, and stop installing MSYS2
994 packages, when building using mingw on Appveyor Windows CI. Fixes
995 bug 28399; bugfix on 0.3.4.1-alpha.
997 o Minor bugfixes (documentation):
998 - Make Doxygen work again after the code movement in the 0.3.5
999 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
1001 o Minor bugfixes (Linux seccomp2 sandbox):
1002 - Permit the "shutdown()" system call, which is apparently used by
1003 OpenSSL under some circumstances. Fixes bug 28183; bugfix
1006 o Minor bugfixes (logging):
1007 - Stop talking about the Named flag in log messages. Clients have
1008 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
1011 o Minor bugfixes (memory leaks):
1012 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1013 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1015 o Minor bugfixes (onion services):
1016 - On an intro point for a version 3 onion service, stop closing
1017 introduction circuits on an NACK. This lets the client decide
1018 whether to reuse the circuit or discard it. Previously, we closed
1019 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
1020 0.3.2.1-alpha. Patch by Neel Chaunan.
1021 - When replacing a descriptor in the client cache, make sure to
1022 close all client introduction circuits for the old descriptor, so
1023 we don't end up with unusable leftover circuits. Fixes bug 27471;
1024 bugfix on 0.3.2.1-alpha.
1027 Changes in version 0.3.5.4-alpha - 2018-11-08
1028 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
1029 improves our continuous integration support. It continues our attempts
1030 to stabilize this alpha branch and build it into a foundation for an
1031 acceptable long-term-support release.
1033 o Major bugfixes (compilation, rust):
1034 - Rust tests can now build and run successfully with the
1035 --enable-fragile-hardening option enabled. Doing this currently
1036 requires the rust beta channel; it will be possible with stable
1037 rust once Rust version 1.31 is released. Patch from Alex Crichton.
1038 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
1040 o Major bugfixes (embedding, main loop):
1041 - When DisableNetwork becomes set, actually disable periodic events
1042 that are already enabled. (Previously, we would refrain from
1043 enabling new ones, but we would leave the old ones turned on.)
1044 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
1046 o Minor features (continuous integration):
1047 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
1049 - Add new CI job to Travis configuration to run stem-based
1050 integration tests. Closes ticket 27913.
1052 o Minor features (Windows, continuous integration):
1053 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
1054 Appveyor's CI. Closes ticket 28318.
1056 o Minor bugfixes (C correctness, also in 0.3.4.9):
1057 - Avoid undefined behavior in an end-of-string check when parsing
1058 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1061 o Minor bugfixes (compilation):
1062 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
1063 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1065 o Minor bugfixes (compilation, OpenSolaris):
1066 - Fix compilation on OpenSolaris and its descendants by adding a
1067 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
1070 o Minor bugfixes (configuration):
1071 - Refuse to start with relative file paths and RunAsDaemon set
1072 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
1075 o Minor bugfixes (directory authority, also in 0.3.4.9):
1076 - Log additional info when we get a relay that shares an ed25519 ID
1077 with a different relay, instead of a BUG() warning with a
1078 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
1080 o Minor bugfixes (onion service v3):
1081 - Build the service descriptor's signing key certificate before
1082 uploading, so we always have a fresh one: leaving no chances for
1083 it to expire service side. Fixes bug 27838; bugfix
1086 o Minor bugfixes (onion service v3, client authorization):
1087 - Fix an assert() when adding a client authorization for the first
1088 time and then sending a HUP signal to the service. Before that,
1089 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
1091 o Minor bugfixes (onion services):
1092 - Unless we have explicitly set HiddenServiceVersion, detect the
1093 onion service version and then look for invalid options.
1094 Previously, we did the reverse, but that broke existing configs
1095 which were pointed to a v2 service and had options like
1096 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
1097 0.3.5.1-alpha. Patch by Neel Chauhan.
1099 o Minor bugfixes (portability):
1100 - Make the OPE code (which is used for v3 onion services) run
1101 correctly on big-endian platforms. Fixes bug 28115; bugfix
1104 o Minor bugfixes (protover, rust):
1105 - Reject extra commas in version strings. Fixes bug 27197; bugfix
1108 o Minor bugfixes (relay shutdown, systemd):
1109 - Notify systemd of ShutdownWaitLength so it can be set to longer
1110 than systemd's TimeoutStopSec. In Tor's systemd service file, set
1111 TimeoutSec to 60 seconds to allow Tor some time to shut down.
1112 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
1114 o Minor bugfixes (rust, also in 0.3.4.9):
1115 - Fix a potential null dereference in protover_all_supported(). Add
1116 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1117 - Return a string that can be safely freed by C code, not one
1118 created by the rust allocator, in protover_all_supported(). Fixes
1119 bug 27740; bugfix on 0.3.3.1-alpha.
1121 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
1122 - Fix an API mismatch in the rust implementation of
1123 protover_compute_vote(). This bug could have caused crashes on any
1124 directory authorities running Tor with Rust (which we do not yet
1125 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1127 o Minor bugfixes (testing):
1128 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
1129 27968; bugfix on 0.3.5.1-alpha.
1131 o Minor bugfixes (testing, also in 0.3.4.9):
1132 - Treat backtrace test failures as expected on BSD-derived systems
1133 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1134 (FreeBSD failures have been treated as expected since 18204 in
1135 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1137 o Documentation (onion service manpage):
1138 - Improve HSv3 client authorization by making some options more
1139 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
1142 Changes in version 0.3.4.9 - 2018-11-02
1143 Tor 0.3.4.9 is the second stable release in its series; it backports
1144 numerous fixes, including a fix for a bandwidth management bug that
1145 was causing memory exhaustion on relays. Anyone running an earlier
1146 version of Tor 0.3.4.9 should upgrade.
1148 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
1149 - Fix compilation on ARM (and other less-used CPUs) when compiling
1150 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1152 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
1153 - Make sure Tor bootstraps and works properly if only the
1154 ControlPort is set. Prior to this fix, Tor would only bootstrap
1155 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1156 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1158 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
1159 - When our write bandwidth limit is exhausted, stop writing on the
1160 connection. Previously, we had a typo in the code that would make
1161 us stop reading instead, leading to relay connections being stuck
1162 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1165 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1166 - Fix a use-after-free error that could be caused by passing Tor an
1167 impossible set of options that would fail during options_act().
1168 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1170 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1171 - Don't do a distcheck with --disable-module-dirauth in Travis.
1172 Implements ticket 27252.
1173 - Only run one online rust build in Travis, to reduce network
1174 errors. Skip offline rust builds on Travis for Linux gcc, because
1175 they're redundant. Implements ticket 27252.
1176 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1177 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1178 Linux with default settings, because all the non-default builds
1179 use gcc on Linux. Implements ticket 27252.
1181 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1182 - Use the Travis Homebrew addon to install packages on macOS during
1183 Travis CI. The package list is the same, but the Homebrew addon
1184 does not do a `brew update` by default. Implements ticket 27738.
1186 o Minor features (geoip):
1187 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
1188 Country database. Closes ticket 27991.
1190 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
1191 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1192 difference algorithm for 32-bit Apple platforms. Previously, it
1193 would overflow when calculating the difference between two times
1194 more than 47 days apart. Fixes part of bug 27139; bugfix
1196 - Improve the precision of our 32-bit millisecond difference
1197 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1198 bugfix on 0.3.4.1-alpha.
1199 - Relax the tolerance on the mainloop/update_time_jumps test when
1200 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1203 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
1204 - Avoid undefined behavior in an end-of-string check when parsing
1205 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1208 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
1209 - Only install the necessary mingw packages during our appveyor
1210 builds. This change makes the build a little faster, and prevents
1211 a conflict with a preinstalled mingw openssl that appveyor now
1212 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
1214 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1215 - Rewrite our assertion macros so that they no longer suppress the
1216 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1218 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
1219 - Stop reinstalling identical packages in our Windows CI. Fixes bug
1220 27464; bugfix on 0.3.4.1-alpha.
1222 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
1223 - Log additional info when we get a relay that shares an ed25519 ID
1224 with a different relay, instead making a BUG() warning. Fixes bug
1225 27800; bugfix on 0.3.2.1-alpha.
1227 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
1228 - Avoid a double-close when shutting down a stalled directory
1229 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
1231 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
1232 - Fix a bug warning when closing an HTTP tunnel connection due to an
1233 HTTP request we couldn't handle. Fixes bug 26470; bugfix
1236 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1237 - Ensure circuitmux queues are empty before scheduling or sending
1238 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1240 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1241 - When the onion service directory can't be created or has the wrong
1242 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1245 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1246 - Close all SOCKS request (for the same .onion) if the newly fetched
1247 descriptor is unusable. Before that, we would close only the first
1248 one leaving the other hanging and let to time out by themselves.
1249 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1251 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1252 - When selecting a v3 rendezvous point, don't only look at the
1253 protover, but also check whether the curve25519 onion key is
1254 present. This way we avoid picking a relay that supports the v3
1255 rendezvous but for which we don't have the microdescriptor. Fixes
1256 bug 27797; bugfix on 0.3.2.1-alpha.
1258 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1259 - Reject protocol names containing bytes other than alphanumeric
1260 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1263 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1264 - Compute protover votes correctly in the rust version of the
1265 protover code. Previously, the protover rewrite in 24031 allowed
1266 repeated votes from the same voter for the same protocol version
1267 to be counted multiple times in protover_compute_vote(). Fixes bug
1268 27649; bugfix on 0.3.3.5-rc.
1269 - Reject protover names that contain invalid characters. Fixes bug
1270 27687; bugfix on 0.3.3.1-alpha.
1272 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1273 - protover_all_supported() would attempt to allocate up to 16GB on
1274 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1275 bugfix on 0.3.3.5-rc.
1277 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
1278 - Fix an API mismatch in the rust implementation of
1279 protover_compute_vote(). This bug could have caused crashes on any
1280 directory authorities running Tor with Rust (which we do not yet
1281 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1283 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
1284 - Fix a potential null dereference in protover_all_supported(). Add
1285 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1286 - Return a string that can be safely freed by C code, not one
1287 created by the rust allocator, in protover_all_supported(). Fixes
1288 bug 27740; bugfix on 0.3.3.1-alpha.
1290 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1291 - If a unit test running in a subprocess exits abnormally or with a
1292 nonzero status code, treat the test as having failed, even if the
1293 test reported success. Without this fix, memory leaks don't cause
1294 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1295 bugfix on 0.2.2.4-alpha.
1297 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
1298 - Make the hs_service tests use the same time source when creating
1299 the introduction point and when testing it. Now tests work better
1300 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
1303 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
1304 - Treat backtrace test failures as expected on BSD-derived systems
1305 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1306 (FreeBSD failures have been treated as expected since 18204 in
1307 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1310 Changes in version 0.3.5.3-alpha - 2018-10-17
1311 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
1312 versions. One important fix for relays addresses a problem with rate-
1313 limiting code from back in 0.3.4.x: If the fix works out, we'll be
1314 backporting it soon. This release is still an alpha, but we hope it's
1315 getting closer and closer to stability.
1317 o Major features (onion services):
1318 - Version 3 onion services can now use the per-service
1319 HiddenServiceExportCircuitID option to differentiate client
1320 circuits. It communicates with the service by using the HAProxy
1321 protocol to assign virtual IP addresses to inbound client
1322 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
1324 o Major bugfixes (compilation):
1325 - Fix compilation on ARM (and other less-used CPUs) when compiling
1326 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1328 o Major bugfixes (initialization, crash):
1329 - Fix an assertion crash that would stop Tor from starting up if it
1330 tried to activate a periodic event too early. Fixes bug 27861;
1331 bugfix on 0.3.5.1-alpha.
1333 o Major bugfixes (mainloop, bootstrap):
1334 - Make sure Tor bootstraps and works properly if only the
1335 ControlPort is set. Prior to this fix, Tor would only bootstrap
1336 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1337 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1339 o Major bugfixes (relay):
1340 - When our write bandwidth limit is exhausted, stop writing on the
1341 connection. Previously, we had a typo in the code that would make
1342 us stop reading instead, leading to relay connections being stuck
1343 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1346 o Minor features (continuous integration):
1347 - Use the Travis Homebrew addon to install packages on macOS during
1348 Travis CI. The package list is the same, but the Homebrew addon
1349 does not do a `brew update` by default. Implements ticket 27738.
1350 - Report what program produced the mysterious core file that we
1351 occasionally see on Travis CI during make distcheck. Closes
1354 o Minor features (geoip):
1355 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
1356 Country database. Closes ticket 27991.
1358 o Minor bugfixes (code safety):
1359 - Rewrite our assertion macros so that they no longer suppress the
1360 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1363 o Minor bugfixes (compilation):
1364 - Compile the ed25519-donna code with a correct declaration of
1365 crypto_strongest_rand(). Previously, we built it with one type,
1366 but linked it against another in the unit tests, which caused
1367 compilation failures with LTO enabled. This could have caused
1368 other undefined behavior in the tests. Fixes bug 27728; bugfix
1371 o Minor bugfixes (compilation, netbsd):
1372 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
1375 o Minor bugfixes (continuous integration, appveyor):
1376 - Install only the necessary mingw packages during our appveyor
1377 builds. This change makes the build a little faster, and prevents
1378 a conflict with a preinstalled mingw openssl that appveyor now
1379 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
1381 o Minor bugfixes (directory permissions):
1382 - When a user requests a group-readable DataDirectory, give it to
1383 them. Previously, when the DataDirectory and the CacheDirectory
1384 were the same, the default setting (0) for
1385 CacheDirectoryGroupReadable would override the setting for
1386 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1389 o Minor bugfixes (memory leaks):
1390 - Fix a small memory leak when calling Tor with --dump-config. Fixes
1391 bug 27893; bugfix on 0.3.2.1-alpha.
1393 o Minor bugfixes (networking):
1394 - In retry_listeners_ports(), make sure that we're removing a member
1395 of old_conns smartlist at most once. Fixes bug 27808; bugfix
1397 - Refrain from attempting socket rebinding when old and new
1398 listeners are in different address families. Fixes bug 27928;
1399 bugfix on 0.3.5.1-alpha.
1401 o Minor bugfixes (onion service v3):
1402 - Stop dumping a stack trace when trying to connect to an intro
1403 point without having a descriptor for it. Fixes bug 27774; bugfix
1405 - Don't warn so loudly when Tor is unable to decode an onion
1406 descriptor. This can now happen as a normal use case if a client
1407 gets a descriptor with client authorization but the client is not
1408 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1409 - When selecting a v3 rendezvous point, don't only look at the
1410 protover, but also check whether the curve25519 onion key is
1411 present. This way we avoid picking a relay that supports the v3
1412 rendezvous but for which we don't have the microdescriptor. Fixes
1413 bug 27797; bugfix on 0.3.2.1-alpha.
1415 o Minor bugfixes (protover):
1416 - Reject protocol names containing bytes other than alphanumeric
1417 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1420 o Minor bugfixes (testing):
1421 - Make the hs_service tests use the same time source when creating
1422 the introduction point and when testing it. Now tests work better
1423 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
1425 - In test_rebind.py, check if the Python version is in the supported
1426 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
1428 o Code simplification and refactoring:
1429 - Divide more large Tor source files -- especially ones that span
1430 multiple areas of functionality -- into smaller parts, including
1431 onion.c and main.c. Closes ticket 26747.
1432 - Divide the "routerparse.c" module into separate modules for each
1433 group of parsed objects. Closes ticket 27924.
1434 - Move protover_rust.c to the same place protover.c was moved to.
1435 Closes ticket 27814.
1436 - Split directory.c into separate pieces for client, server, and
1437 common functionality. Closes ticket 26744.
1438 - Split the non-statistics-related parts from the rephist.c and
1439 geoip.c modules. Closes ticket 27892.
1440 - Split the router.c file into relay-only and shared components, to
1441 help with future modularization. Closes ticket 27864.
1444 - In the tor-resolve(1) manpage, fix the reference to socks-
1445 extensions.txt by adding a web URL. Resolves ticket 27853.
1446 - Mention that we require Python to be 2.7 or newer for some
1447 integration tests that we ship with Tor. Resolves ticket 27677.
1450 Changes in version 0.3.5.2-alpha - 2018-09-21
1451 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
1452 that made Tor think it had run out of sockets. Anybody running a relay
1453 or an onion service on 0.3.5.1-alpha should upgrade.
1455 o Major bugfixes (relay bandwidth statistics):
1456 - When we close relayed circuits, report the data in the circuit
1457 queues as being written in our relay bandwidth stats. This
1458 mitigates guard discovery and other attacks that close circuits
1459 for the explicit purpose of noticing this discrepancy in
1460 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
1462 o Major bugfixes (socket accounting):
1463 - In our socket accounting code, count a socket as closed even when
1464 it is closed indirectly by the TLS layer. Previously, we would
1465 count these sockets as still in use, and incorrectly believe that
1466 we had run out of sockets. Fixes bug 27795; bugfix
1469 o Minor bugfixes (32-bit OSX and iOS, timing):
1470 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1471 difference algorithm for 32-bit Apple platforms. Previously, it
1472 would overflow when calculating the difference between two times
1473 more than 47 days apart. Fixes part of bug 27139; bugfix
1475 - Improve the precision of our 32-bit millisecond difference
1476 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1477 bugfix on 0.3.4.1-alpha.
1478 - Relax the tolerance on the mainloop/update_time_jumps test when
1479 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1482 o Minor bugfixes (onion service v3):
1483 - Close all SOCKS request (for the same .onion) if the newly fetched
1484 descriptor is unusable. Before that, we would close only the first
1485 one leaving the other hanging and let to time out by themselves.
1486 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1488 o Minor bugfixes (memory leak):
1489 - Fix an unlikely memory leak when trying to read a private key from
1490 a ridiculously large file. Fixes bug 27764; bugfix on
1491 0.3.5.1-alpha. This is CID 1439488.
1493 o Minor bugfixes (NSS):
1494 - Correctly detect failure to open a dummy TCP socket when stealing
1495 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
1498 o Minor bugfixes (rust):
1499 - protover_all_supported() would attempt to allocate up to 16GB on
1500 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1501 bugfix on 0.3.3.5-rc.
1503 o Minor bugfixes (testing):
1504 - Revise the "conditionvar_timeout" test so that it succeeds even on
1505 heavily loaded systems where the test threads are not scheduled
1506 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
1508 o Code simplification and refactoring:
1509 - Divide the routerlist.c and dirserv.c modules into smaller parts.
1510 Closes ticket 27799.
1513 Changes in version 0.3.5.1-alpha - 2018-09-18
1514 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
1515 client authorization for modern (v3) onion services, improves
1516 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
1517 support for NSS in place of OpenSSL, and much more.
1519 o Major features (onion services, UI change):
1520 - For a newly created onion service, the default version is now 3.
1521 Tor still supports existing version 2 services, but the operator
1522 now needs to set "HiddenServiceVersion 2" in order to create a new
1523 version 2 service. For existing services, Tor now learns the
1524 version by reading the key file. Closes ticket 27215.
1526 o Major features (relay, UI change):
1527 - Relays no longer run as exits by default. If the "ExitRelay"
1528 option is auto (or unset), and no exit policy is specified with
1529 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
1530 Previously in this case, we allowed exit traffic and logged a
1531 warning message. Closes ticket 21530. Patch by Neel Chauhan.
1532 - Tor now validates that the ContactInfo config option is valid UTF-
1533 8 when parsing torrc. Closes ticket 27428.
1535 o Major features (bootstrap):
1536 - Don't report directory progress until after a connection to a
1537 relay or bridge has succeeded. Previously, we'd report 80%
1538 progress based on cached directory information when we couldn't
1539 even connect to the network. Closes ticket 27169.
1541 o Major features (new code layout):
1542 - Nearly all of Tor's source code has been moved around into more
1543 logical places. The "common" directory is now divided into a set
1544 of libraries in "lib", and files in the "or" directory have been
1545 split into "core" (logic absolutely needed for onion routing),
1546 "feature" (independent modules in Tor), and "app" (to configure
1547 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
1548 more information. Closes ticket 26481.
1550 This refactoring is not complete: although the libraries have been
1551 refactored to be acyclic, the main body of Tor is still too
1552 interconnected. We will attempt to improve this in the future.
1554 o Major features (onion services v3):
1555 - Implement onion service client authorization at the descriptor
1556 level: only authorized clients can decrypt a service's descriptor
1557 to find out how to contact it. A new torrc option was added to
1558 control this client side: ClientOnionAuthDir <path>. On the
1559 service side, if the "authorized_clients/" directory exists in the
1560 onion service directory path, client configurations are read from
1561 the files within. See the manpage for more details. Closes ticket
1562 27547. Patch done by Suphanat Chunhapanya (haxxpop).
1563 - Improve revision counter generation in next-gen onion services.
1564 Onion services can now scale by hosting multiple instances on
1565 different hosts without synchronization between them, which was
1566 previously impossible because descriptors would get rejected by
1567 HSDirs. Addresses ticket 25552.
1569 o Major features (portability, cryptography, experimental, TLS):
1570 - Tor now has the option to compile with the NSS library instead of
1571 OpenSSL. This feature is experimental, and we expect that bugs may
1572 remain. It is mainly intended for environments where Tor's
1573 performance is not CPU-bound, and where NSS is already known to be
1574 installed. To try it out, configure Tor with the --enable-nss
1575 flag. Closes tickets 26631, 26815, and 26816.
1577 If you are experimenting with this option and using an old cached
1578 consensus, Tor may fail to start. To solve this, delete your
1579 "cached-consensus" and "cached-microdesc-consensus" files,
1580 (if present), and restart Tor.
1582 o Major bugfixes (directory authority):
1583 - Actually check that the address we get from DirAuthority
1584 configuration line is valid IPv4. Explicitly disallow DirAuthority
1585 address to be a DNS hostname. Fixes bug 26488; bugfix
1588 o Major bugfixes (restart-in-process):
1589 - Fix a use-after-free error that could be caused by passing Tor an
1590 impossible set of options that would fail during options_act().
1591 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1593 o Minor features (admin tools):
1594 - Add a new --key-expiration option to print the expiration date of
1595 the signing cert in an ed25519_signing_cert file. Resolves
1598 o Minor features (build):
1599 - If you pass the "--enable-pic" option to configure, Tor will try
1600 to tell the compiler to build position-independent code suitable
1601 to link into a dynamic library. (The default remains -fPIE, for
1602 code suitable for a relocatable executable.) Closes ticket 23846.
1604 o Minor features (code correctness, testing):
1605 - Tor's build process now includes a "check-includes" make target to
1606 verify that no module of Tor relies on any headers from a higher-
1607 level module. We hope to use this feature over time to help
1608 refactor our codebase. Closes ticket 26447.
1610 o Minor features (code layout):
1611 - We have a new "lowest-level" error-handling API for use by code
1612 invoked from within the logging module. With this interface, the
1613 logging code is no longer at risk of calling into itself if a
1614 failure occurs while it is trying to log something. Closes
1617 o Minor features (compilation):
1618 - Tor's configure script now supports a --with-malloc= option to
1619 select your malloc implementation. Supported options are
1620 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
1621 default). Addresses part of ticket 20424. Based on a patch from
1624 o Minor features (config):
1625 - The "auto" keyword in torrc is now case-insensitive. Closes
1628 o Minor features (continuous integration):
1629 - Don't do a distcheck with --disable-module-dirauth in Travis.
1630 Implements ticket 27252.
1631 - Install libcap-dev and libseccomp2-dev so these optional
1632 dependencies get tested on Travis CI. Closes ticket 26560.
1633 - Only run one online rust build in Travis, to reduce network
1634 errors. Skip offline rust builds on Travis for Linux gcc, because
1635 they're redundant. Implements ticket 27252.
1636 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1637 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1638 Linux with default settings, because all the non-default builds
1639 use gcc on Linux. Implements ticket 27252.
1641 o Minor features (controller):
1642 - Emit CIRC_BW events as soon as we detect that we processed an
1643 invalid or otherwise dropped cell on a circuit. This allows
1644 vanguards and other controllers to react more quickly to dropped
1645 cells. Closes ticket 27678.
1646 - For purposes of CIRC_BW-based dropped cell detection, track half-
1647 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1648 bias check cells to arrive without counting it as dropped until
1649 either the END arrives, or the windows are empty. Closes
1651 - Implement a 'GETINFO md/all' controller command to enable getting
1652 all known microdescriptors. Closes ticket 8323.
1653 - The GETINFO command now support an "uptime" argument, to return
1654 Tor's uptime in seconds. Closes ticket 25132.
1656 o Minor features (denial-of-service avoidance):
1657 - Make our OOM handler aware of the DNS cache so that it doesn't
1658 fill up the memory. This check is important for our DoS mitigation
1659 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
1661 o Minor features (development):
1662 - Tor's makefile now supports running the "clippy" Rust style tool
1663 on our Rust code. Closes ticket 22156.
1665 o Minor features (directory authority):
1666 - There is no longer an artificial upper limit on the length of
1667 bandwidth lines. Closes ticket 26223.
1668 - When a bandwidth file is used to obtain the bandwidth measurements,
1669 include this bandwidth file headers in the votes. Closes
1671 - Improved support for networks with only a single authority or a
1672 single fallback directory. Patch from Gabriel Somlo. Closes
1675 o Minor features (embedding API):
1676 - The Tor controller API now supports a function to launch Tor with
1677 a preconstructed owning controller FD, so that embedding
1678 applications don't need to manage controller ports and
1679 authentication. Closes ticket 24204.
1680 - The Tor controller API now has a function that returns the name
1681 and version of the backend implementing the API. Closes
1684 o Minor features (geoip):
1685 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
1686 Country database. Closes ticket 27631.
1688 o Minor features (memory management):
1689 - Get Libevent to use the same memory allocator as Tor, by calling
1690 event_set_mem_functions() during initialization. Resolves
1693 o Minor features (memory usage):
1694 - When not using them, store legacy TAP public onion keys in DER-
1695 encoded format, rather than as expanded public keys. This should
1696 save several megabytes on typical clients. Closes ticket 27246.
1698 o Minor features (OpenSSL):
1699 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
1700 than our own. Resolves ticket 19979.
1702 o Minor features (Rust, code quality):
1703 - Improve rust code quality in the rust protover implementation by
1704 making it more idiomatic. Includes changing an internal API to
1705 take &str instead of &String. Closes ticket 26492.
1707 o Minor features (testing):
1708 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
1709 chutney. Implements ticket 27211.
1711 o Minor features (tor-resolve):
1712 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
1713 Side-effect of the refactoring for ticket 26526.
1715 o Minor features (UI):
1716 - Log each included configuration file or directory as we read it,
1717 to provide more visibility about where Tor is reading from. Patch
1718 from Unto Sten; closes ticket 27186.
1719 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
1720 Closes ticket 26703.
1722 o Minor bugfixes (bootstrap):
1723 - Try harder to get descriptors in non-exit test networks, by using
1724 the mid weight for the third hop when there are no exits. Fixes
1725 bug 27237; bugfix on 0.2.6.2-alpha.
1727 o Minor bugfixes (C correctness):
1728 - Avoid casting smartlist index to int implicitly, as it may trigger
1729 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
1730 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
1731 - Use time_t for all values in
1732 predicted_ports_prediction_time_remaining(). Rework the code that
1733 computes difference between durations/timestamps. Fixes bug 27165;
1734 bugfix on 0.3.1.1-alpha.
1736 o Minor bugfixes (client, memory usage):
1737 - When not running as a directory cache, there is no need to store
1738 the text of the current consensus networkstatus in RAM.
1739 Previously, however, clients would store it anyway, at a cost of
1740 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
1743 o Minor bugfixes (client, reachableaddresses):
1744 - Instead of adding a "reject *:*" line to ReachableAddresses when
1745 loading the configuration, add one to the policy after parsing it
1746 in parse_reachable_addresses(). This prevents extra "reject *.*"
1747 lines from accumulating on reloads. Fixes bug 20874; bugfix on
1748 0.1.1.5-alpha. Patch by Neel Chauhan.
1750 o Minor bugfixes (code quality):
1751 - Rename sandbox_getaddrinfo() and other functions to no longer
1752 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
1753 bugfix on 0.2.7.1-alpha.
1755 o Minor bugfixes (configuration, Onion Services):
1756 - In rend_service_parse_port_config(), disallow any input to remain
1757 after address-port pair was parsed. This will catch address and
1758 port being whitespace-separated by mistake of the user. Fixes bug
1759 27044; bugfix on 0.2.9.10.
1761 o Minor bugfixes (continuous integration):
1762 - Stop reinstalling identical packages in our Windows CI. Fixes bug
1763 27464; bugfix on 0.3.4.1-alpha.
1765 o Minor bugfixes (controller):
1766 - Consider all routerinfo errors other than "not a server" to be
1767 transient for the purpose of "GETINFO exit-policy/*" controller
1768 request. Print stacktrace in the unlikely case of failing to
1769 recompute routerinfo digest. Fixes bug 27034; bugfix
1772 o Minor bugfixes (directory connection shutdown):
1773 - Avoid a double-close when shutting down a stalled directory
1774 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
1776 o Minor bugfixes (HTTP tunnel):
1777 - Fix a bug warning when closing an HTTP tunnel connection due to an
1778 HTTP request we couldn't handle. Fixes bug 26470; bugfix
1781 o Minor bugfixes (ipv6):
1782 - In addrs_in_same_network_family(), we choose the subnet size based
1783 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
1784 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
1785 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
1787 o Minor bugfixes (logging):
1788 - As a precaution, do an early return from log_addr_has_changed() if
1789 Tor is running as client. Also, log a stack trace for debugging as
1790 this function should only be called when Tor runs as server. Fixes
1791 bug 26892; bugfix on 0.1.1.9-alpha.
1792 - Refrain from mentioning bug 21018 in the logs, as it is already
1793 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
1795 o Minor bugfixes (logging, documentation):
1796 - When SafeLogging is enabled, scrub IP address in
1797 channel_tls_process_netinfo_cell(). Also, add a note to manpage
1798 that scrubbing is not guaranteed on loglevels below Notice. Fixes
1799 bug 26882; bugfix on 0.2.4.10-alpha.
1801 o Minor bugfixes (netflow padding):
1802 - Ensure circuitmux queues are empty before scheduling or sending
1803 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1805 o Minor bugfixes (onion service v2):
1806 - Log at level "info", not "warning", in the case that we do not
1807 have a consensus when a .onion request comes in. This can happen
1808 normally while bootstrapping. Fixes bug 27040; bugfix
1811 o Minor bugfixes (onion service v3):
1812 - When the onion service directory can't be created or has the wrong
1813 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1816 o Minor bugfixes (OS compatibility):
1817 - Properly handle configuration changes that move a listener to/from
1818 wildcard IP address. If the first attempt to bind a socket fails,
1819 close the old listener and try binding the socket again. Fixes bug
1820 17873; bugfix on 0.0.8pre-1.
1822 o Minor bugfixes (performance)::
1823 - Rework node_is_a_configured_bridge() to no longer call
1824 node_get_all_orports(), which was performing too many memory
1825 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
1827 o Minor bugfixes (relay statistics):
1828 - Update relay descriptor on bandwidth changes only when the uptime
1829 is smaller than 24h, in order to reduce the efficiency of guard
1830 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1832 o Minor bugfixes (relays):
1833 - Consider the fact that we'll be making direct connections to our
1834 entry and guard nodes when computing the fraction of nodes that
1835 have their descriptors. Also, if we are using bridges and there is
1836 at least one bridge with a full descriptor, treat the fraction of
1837 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
1838 Patch by Neel Chauhan.
1839 - Update the message logged on relays when DirCache is disabled.
1840 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
1841 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
1843 o Minor bugfixes (rust, protover):
1844 - Compute protover votes correctly in the rust version of the
1845 protover code. Previously, the protover rewrite in 24031 allowed
1846 repeated votes from the same voter for the same protocol version
1847 to be counted multiple times in protover_compute_vote(). Fixes bug
1848 27649; bugfix on 0.3.3.5-rc.
1849 - Reject protover names that contain invalid characters. Fixes bug
1850 27687; bugfix on 0.3.3.1-alpha.
1852 o Minor bugfixes (testing):
1853 - Fix two unit tests to work when HOME environment variable is not
1854 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
1855 - If a unit test running in a subprocess exits abnormally or with a
1856 nonzero status code, treat the test as having failed, even if the
1857 test reported success. Without this fix, memory leaks don't cause
1858 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1859 bugfix on 0.2.2.4-alpha.
1860 - When logging a version mismatch in our openssl_version tests,
1861 report the actual offending version strings. Fixes bug 26152;
1862 bugfix on 0.2.9.1-alpha.
1863 - Fix forking tests on Windows when there is a space somewhere in
1864 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
1866 o Code simplification and refactoring:
1867 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
1868 longer needed. Closes ticket 26502.
1869 - Include paths to header files within Tor are now qualified by
1870 directory within the top-level src directory.
1871 - Many structures have been removed from the centralized "or.h"
1872 header, and moved into their own headers. This will allow us to
1873 reduce the number of places in the code that rely on each
1874 structure's contents and layout. Closes ticket 26383.
1875 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
1876 - Remove GetAdaptersAddresses_fn_t. The code that used it was
1877 removed as part of the 26481 refactor. Closes ticket 27467.
1878 - Rework Tor SOCKS server code to use Trunnel and benefit from
1879 autogenerated functions for parsing and generating SOCKS wire
1880 format. New implementation is cleaner, more maintainable and
1881 should be less prone to heartbleed-style vulnerabilities.
1882 Implements a significant fraction of ticket 3569.
1883 - Split sampled_guards_update_from_consensus() and
1884 select_entry_guard_for_circuit() into subfunctions. In
1885 entry_guards_update_primary() unite three smartlist enumerations
1886 into one and move smartlist comparison code out of the function.
1887 Closes ticket 21349.
1888 - Tor now assumes that you have standards-conformant stdint.h and
1889 inttypes.h headers when compiling. Closes ticket 26626.
1890 - Unify our bloom filter logic. Previously we had two copies of this
1891 code: one for routerlist filtering, and one for address set
1892 calculations. Closes ticket 26510.
1893 - Use the simpler strcmpstart() helper in
1894 rend_parse_v2_service_descriptor instead of strncmp(). Closes
1896 - Utility functions that can perform a DNS lookup are now wholly
1897 separated from those that can't, in separate headers and C
1898 modules. Closes ticket 26526.
1901 - Copy paragraph and URL to Tor's code of conduct document from
1902 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
1903 - Remove old instructions from INSTALL document. Closes ticket 26588.
1904 - Warn users that they should not include MyFamily line(s) in their
1905 torrc when running Tor bridge. Closes ticket 26908.
1908 - Tor no longer supports building with the dmalloc library. For
1909 debugging memory issues, we suggest using gperftools or msan
1910 instead. Closes ticket 26426.
1911 - Tor no longer attempts to run on Windows environments without the
1912 GetAdaptersAddresses() function. This function has existed since
1913 Windows XP, which is itself already older than we support.
1914 - Remove Tor2web functionality for version 2 onion services. The
1915 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
1916 (This feature was never shipped in vanilla Tor and it was only
1917 possible to use this feature by building the support at compile
1918 time. Tor2webMode is not implemented for version 3 onion services.)
1919 Closes ticket 26367.
1922 Changes in version 0.2.9.17 - 2018-09-10
1923 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
1925 o Minor features (compatibility, backport from 0.3.4.8):
1926 - Tell OpenSSL to maintain backward compatibility with previous
1927 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
1928 ciphers are disabled by default. Closes ticket 27344.
1930 o Minor features (continuous integration, backport from 0.3.4.7-rc):
1931 - Enable macOS builds in our Travis CI configuration. Closes
1933 - Install libcap-dev and libseccomp2-dev so these optional
1934 dependencies get tested on Travis CI. Closes ticket 26560.
1935 - Run asciidoc during Travis CI. Implements ticket 27087.
1936 - Use ccache in our Travis CI configuration. Closes ticket 26952.
1938 o Minor features (geoip):
1939 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
1940 Country database. Closes ticket 27089.
1942 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
1943 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
1944 tell the compiler not to include the system malloc implementation.
1945 Fixes bug 20424; bugfix on 0.2.0.20-rc.
1947 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
1948 - Silence a spurious compiler warning on the GetAdaptersAddresses
1949 function pointer cast. This issue is already fixed by 26481 in
1950 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
1951 bugfix on 0.2.3.11-alpha.
1952 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
1953 supported, and always fails. Some compilers warn about the
1954 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
1957 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
1958 - Don't link or search for pthreads when building for Windows, even
1959 if we are using build environment (like mingw) that provides a
1960 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
1962 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
1963 - Skip a pair of unreliable key generation tests on Windows, until
1964 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
1965 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
1967 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
1968 - Pass the module flags to distcheck configure, and log the flags
1969 before running configure. (Backported to 0.2.9 and later as a
1970 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
1972 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
1973 - When a Travis build fails, and showing a log fails, keep trying to
1974 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
1975 - When we use echo in Travis, don't pass a --flag as the first
1976 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
1978 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
1979 - When voting for recommended versions, make sure that all of the
1980 versions are well-formed and parsable. Fixes bug 26485; bugfix
1983 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
1984 - Fix a bug in out sandboxing rules for the openat() syscall.
1985 Previously, no openat() call would be permitted, which would break
1986 filesystem operations on recent glibc versions. Fixes bug 25440;
1987 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
1989 o Minor bugfixes (onion services, backport from 0.3.4.8):
1990 - Silence a spurious compiler warning in
1991 rend_client_send_introduction(). Fixes bug 27463; bugfix
1994 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
1995 - Log a protocol warning when single onion services or Tor2web clients
1996 fail to authenticate direct connections to relays.
1997 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
1999 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2000 - Disable core dumps in test_bt.sh, to avoid failures in "make
2001 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2003 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2004 - Before running make test-network-all, delete old logs and test
2005 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2008 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2009 - Our "tortls/cert_matches_key" unit test no longer relies on
2010 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2011 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2012 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2014 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2015 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2016 27185; bugfix on 0.2.2.2-alpha.
2019 Changes in version 0.3.2.12 - 2018-09-10
2020 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
2022 o Minor features (compatibility, backport from 0.3.4.8):
2023 - Tell OpenSSL to maintain backward compatibility with previous
2024 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2025 ciphers are disabled by default. Closes ticket 27344.
2027 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2028 - Enable macOS builds in our Travis CI configuration. Closes
2030 - Install libcap-dev and libseccomp2-dev so these optional
2031 dependencies get tested on Travis CI. Closes ticket 26560.
2032 - Run asciidoc during Travis CI. Implements ticket 27087.
2033 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2035 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2036 - Use cargo cache in our Travis CI configuration. Closes
2039 o Minor features (controller, backport from 0.3.4.6-rc):
2040 - The control port now exposes the list of HTTPTunnelPorts and
2041 ExtOrPorts via GETINFO net/listeners/httptunnel and
2042 net/listeners/extor respectively. Closes ticket 26647.
2044 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2045 - Authorities no longer vote to make the subprotocol version
2046 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2047 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2049 o Minor features (geoip):
2050 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2051 Country database. Closes ticket 27089.
2053 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2054 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2055 tell the compiler not to include the system malloc implementation.
2056 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2057 - Don't try to use a pragma to temporarily disable the
2058 -Wunused-const-variable warning if the compiler doesn't support
2059 it. Fixes bug 26785; bugfix on 0.3.2.11.
2061 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2062 - Silence a spurious compiler warning on the GetAdaptersAddresses
2063 function pointer cast. This issue is already fixed by 26481 in
2064 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2065 bugfix on 0.2.3.11-alpha.
2066 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2067 supported, and always fails. Some compilers warn about the
2068 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2071 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2072 - Don't link or search for pthreads when building for Windows, even
2073 if we are using build environment (like mingw) that provides a
2074 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2076 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2077 - Skip a pair of unreliable key generation tests on Windows, until
2078 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2079 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2081 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2082 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2083 - Pass the module flags to distcheck configure, and log the flags
2084 before running configure. (Backported to 0.2.9 and later as a
2085 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2087 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2088 - When a Travis build fails, and showing a log fails, keep trying to
2089 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2090 - When we use echo in Travis, don't pass a --flag as the first
2091 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2093 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2094 - When voting for recommended versions, make sure that all of the
2095 versions are well-formed and parsable. Fixes bug 26485; bugfix
2098 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2099 - Fix a bug in out sandboxing rules for the openat() syscall.
2100 Previously, no openat() call would be permitted, which would break
2101 filesystem operations on recent glibc versions. Fixes bug 25440;
2102 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2104 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2105 - Improve the log message when connection initiators fail to
2106 authenticate direct connections to relays. Fixes bug 26927; bugfix
2109 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2110 - Fix bug that causes services to not ever rotate their descriptors
2111 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2114 o Minor bugfixes (onion services, backport from 0.3.4.8):
2115 - Silence a spurious compiler warning in
2116 rend_client_send_introduction(). Fixes bug 27463; bugfix
2119 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2120 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2122 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2123 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2124 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2125 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2127 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2128 - Log a protocol warning when single onion services or Tor2web clients
2129 fail to authenticate direct connections to relays.
2130 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2132 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2133 - Disable core dumps in test_bt.sh, to avoid failures in "make
2134 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2136 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2137 - When running make test-network-all, use the mixed+hs-v2 network.
2138 (A previous fix to chutney removed v3 onion services from the
2139 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2140 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2141 - Before running make test-network-all, delete old logs and test
2142 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2145 o Minor bugfixes (testing, openssl compatibility):
2146 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
2147 internals. Previously, it relied on unsupported OpenSSL behavior in
2148 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
2149 bugfix on 0.2.5.1-alpha.
2151 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2152 - Our "tortls/cert_matches_key" unit test no longer relies on
2153 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2154 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2155 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2157 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2158 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2159 27185; bugfix on 0.2.2.2-alpha.
2162 Changes in version 0.3.3.10 - 2018-09-10
2163 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
2165 o Minor features (bug workaround, backport from 0.3.4.7-rc):
2166 - Compile correctly on systems that provide the C11 stdatomic.h
2167 header, but where C11 atomic functions don't actually compile.
2168 Closes ticket 26779; workaround for Debian issue 903709.
2170 o Minor features (compatibility, backport from 0.3.4.8):
2171 - Tell OpenSSL to maintain backward compatibility with previous
2172 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2173 ciphers are disabled by default. Closes ticket 27344.
2175 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2176 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2177 - Enable macOS builds in our Travis CI configuration. Closes
2179 - Install libcap-dev and libseccomp2-dev so these optional
2180 dependencies get tested on Travis CI. Closes ticket 26560.
2181 - Run asciidoc during Travis CI. Implements ticket 27087.
2182 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2184 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2185 - Use cargo cache in our Travis CI configuration. Closes
2188 o Minor features (controller, backport from 0.3.4.6-rc):
2189 - The control port now exposes the list of HTTPTunnelPorts and
2190 ExtOrPorts via GETINFO net/listeners/httptunnel and
2191 net/listeners/extor respectively. Closes ticket 26647.
2193 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2194 - Authorities no longer vote to make the subprotocol version
2195 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2196 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2198 o Minor features (geoip):
2199 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2200 Country database. Closes ticket 27089.
2202 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2203 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2204 tell the compiler not to include the system malloc implementation.
2205 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2206 - Don't try to use a pragma to temporarily disable the
2207 -Wunused-const-variable warning if the compiler doesn't support
2208 it. Fixes bug 26785; bugfix on 0.3.2.11.
2210 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2211 - Silence a spurious compiler warning on the GetAdaptersAddresses
2212 function pointer cast. This issue is already fixed by 26481 in
2213 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2214 bugfix on 0.2.3.11-alpha.
2215 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2216 supported, and always fails. Some compilers warn about the
2217 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2220 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2221 - Don't link or search for pthreads when building for Windows, even
2222 if we are using build environment (like mingw) that provides a
2223 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2225 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2226 - Skip a pair of unreliable key generation tests on Windows, until
2227 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2228 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2230 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2231 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2232 - Pass the module flags to distcheck configure, and log the flags
2233 before running configure. (Backported to 0.2.9 and later as a
2234 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2236 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2237 - When a Travis build fails, and showing a log fails, keep trying to
2238 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2239 - When we use echo in Travis, don't pass a --flag as the first
2240 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2242 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2243 - When voting for recommended versions, make sure that all of the
2244 versions are well-formed and parsable. Fixes bug 26485; bugfix
2247 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
2248 - Always call tor_free_all() when leaving tor_run_main(). When we
2249 did not, restarting tor in-process would cause an assertion
2250 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2252 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2253 - Fix a bug in our sandboxing rules for the openat() syscall.
2254 Previously, no openat() call would be permitted, which would break
2255 filesystem operations on recent glibc versions. Fixes bug 25440;
2256 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2258 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2259 - Improve the log message when connection initiators fail to
2260 authenticate direct connections to relays. Fixes bug 26927; bugfix
2263 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2264 - Fix bug that causes services to not ever rotate their descriptors
2265 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2268 o Minor bugfixes (onion services, backport from 0.3.4.8):
2269 - Silence a spurious compiler warning in
2270 rend_client_send_introduction(). Fixes bug 27463; bugfix
2273 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
2274 - Work around two different bugs in the OS X 10.10 and later SDKs
2275 that would prevent us from successfully targeting earlier versions
2276 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2278 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
2279 - Fix compilation of the unit tests on GNU/Hurd, which does not
2280 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2283 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2284 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2286 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2287 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2288 - Protover parsing was accepting the presence of whitespace in
2289 version strings, which the C implementation would choke on, e.g.
2290 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2291 - Protover parsing was ignoring a 2nd hyphen and everything after
2292 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2294 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2295 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2296 - cd to ${abs_top_builddir}/src/rust before running cargo in
2297 src/test/test_rust.sh. This makes the working directory consistent
2298 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2300 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2301 - Log a protocol warning when single onion services or Tor2web clients
2302 fail to authenticate direct connections to relays.
2303 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2305 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2306 - Disable core dumps in test_bt.sh, to avoid failures in "make
2307 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2309 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2310 - When running make test-network-all, use the mixed+hs-v2 network.
2311 (A previous fix to chutney removed v3 onion services from the
2312 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2313 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2314 - Before running make test-network-all, delete old logs and test
2315 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2318 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2319 - Our "tortls/cert_matches_key" unit test no longer relies on
2320 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2321 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2322 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2324 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
2325 - Stop sending ed25519 link specifiers in v3 onion service introduce
2326 cells and descriptors, when the rendezvous or introduction point
2327 doesn't support ed25519 link authentication. Fixes bug 26627;
2328 bugfix on 0.3.2.4-alpha.
2330 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2331 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2332 27185; bugfix on 0.2.2.2-alpha.
2335 Changes in version 0.3.4.8 - 2018-09-10
2336 Tor 0.3.4.8 is the first stable release in its series; it includes
2337 compilation and portability fixes.
2339 The Tor 0.3.4 series includes improvements for running Tor in
2340 low-power and embedded environments, which should help performance in
2341 general. We've begun work on better modularity, and included preliminary
2342 changes on the directory authority side to accommodate a new bandwidth
2343 measurement system. We've also integrated more continuous-integration
2344 systems into our development process, and made corresponding changes to
2345 Tor's testing infrastructure. Finally, we've continued to refine
2346 our anti-denial-of-service code.
2348 Below are the changes since 0.3.4.7-rc. For a complete list of changes
2349 since 0.3.3.9, see the ReleaseNotes file.
2351 o Minor features (compatibility):
2352 - Tell OpenSSL to maintain backward compatibility with previous
2353 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2354 ciphers are disabled by default. Closes ticket 27344.
2356 o Minor features (continuous integration):
2357 - Log the compiler path and version during Appveyor builds.
2358 Implements ticket 27449.
2359 - Show config.log and test-suite.log after failed Appveyor builds.
2360 Also upload the zipped full logs as a build artifact. Implements
2363 o Minor bugfixes (compilation):
2364 - Silence a spurious compiler warning on the GetAdaptersAddresses
2365 function pointer cast. This issue is already fixed by 26481 in
2366 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2367 bugfix on 0.2.3.11-alpha.
2368 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2369 supported, and always fails. Some compilers warn about the
2370 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2373 o Minor bugfixes (continuous integration):
2374 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
2375 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
2376 Executables compiled for 64-bit Windows with this version of gcc
2377 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
2378 27460; bugfix on 0.3.4.1-alpha.
2379 - When a Travis build fails, and showing a log fails, keep trying to
2380 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2381 - When we use echo in Travis, don't pass a --flag as the first
2382 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2384 o Minor bugfixes (onion services):
2385 - Silence a spurious compiler warning in
2386 rend_client_send_introduction(). Fixes bug 27463; bugfix
2389 o Minor bugfixes (testing, chutney):
2390 - When running make test-network-all, use the mixed+hs-v2 network.
2391 (A previous fix to chutney removed v3 onion services from the
2392 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2393 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2394 - Before running make test-network-all, delete old logs and test
2395 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2398 Changes in version 0.3.4.7-rc - 2018-08-24
2399 Tor 0.3.4.7-rc fixes several small compilation, portability, and
2400 correctness issues in previous versions of Tor. This version is a
2401 release candidate: if no serious bugs are found, we expect that the
2402 stable 0.3.4 release will be (almost) the same as this release.
2404 o Minor features (bug workaround):
2405 - Compile correctly on systems that provide the C11 stdatomic.h
2406 header, but where C11 atomic functions don't actually compile.
2407 Closes ticket 26779; workaround for Debian issue 903709.
2409 o Minor features (continuous integration):
2410 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2411 - Enable macOS builds in our Travis CI configuration. Closes
2413 - Install libcap-dev and libseccomp2-dev so these optional
2414 dependencies get tested on Travis CI. Closes ticket 26560.
2415 - Only post Appveyor IRC notifications when the build fails.
2416 Implements ticket 27275.
2417 - Run asciidoc during Travis CI. Implements ticket 27087.
2418 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2420 o Minor features (continuous integration, rust):
2421 - Use cargo cache in our Travis CI configuration. Closes
2424 o Minor features (directory authorities):
2425 - Authorities no longer vote to make the subprotocol version
2426 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2427 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2429 o Minor features (geoip):
2430 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2431 Country database. Closes ticket 27089.
2433 o Minor bugfixes (compilation, windows):
2434 - Don't link or search for pthreads when building for Windows, even
2435 if we are using build environment (like mingw) that provides a
2436 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2438 o Minor bugfixes (continuous integration):
2439 - Improve Appveyor CI IRC logging. Generate correct branches and
2440 URLs for pull requests and tags. Use unambiguous short commits.
2441 Fixes bug 26979; bugfix on master.
2442 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2443 - Pass the module flags to distcheck configure, and log the flags
2444 before running configure. (Backported to 0.2.9 and later as a
2445 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2447 o Minor bugfixes (in-process restart):
2448 - Always call tor_free_all() when leaving tor_run_main(). When we
2449 did not, restarting tor in-process would cause an assertion
2450 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2452 o Minor bugfixes (linux seccomp2 sandbox):
2453 - Fix a bug in out sandboxing rules for the openat() syscall.
2454 Previously, no openat() call would be permitted, which would break
2455 filesystem operations on recent glibc versions. Fixes bug 25440;
2456 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2458 o Minor bugfixes (onion services):
2459 - Fix bug that causes services to not ever rotate their descriptors
2460 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2463 o Minor bugfixes (portability):
2464 - Fix compilation of the unit tests on GNU/Hurd, which does not
2465 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2468 o Minor bugfixes (rust):
2469 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2471 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2472 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2473 - Protover parsing was accepting the presence of whitespace in
2474 version strings, which the C implementation would choke on, e.g.
2475 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2476 - Protover parsing was ignoring a 2nd hyphen and everything after
2477 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2479 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2480 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2481 - cd to ${abs_top_builddir}/src/rust before running cargo in
2482 src/test/test_rust.sh. This makes the working directory consistent
2483 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2485 o Minor bugfixes (testing, bootstrap):
2486 - When calculating bootstrap progress, check exit policies and the
2487 exit flag. Previously, Tor would only check the exit flag, which
2488 caused race conditions in small and fast networks like chutney.
2489 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
2491 o Minor bugfixes (testing, openssl compatibility):
2492 - Our "tortls/cert_matches_key" unit test no longer relies on
2493 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2494 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2495 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2497 o Minor bugfixes (Windows, compilation):
2498 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2499 27185; bugfix on 0.2.2.2-alpha.
2502 Changes in version 0.3.4.6-rc - 2018-08-06
2503 Tor 0.3.4.6-rc fixes several small compilation, portability, and
2504 correctness issues in previous versions of Tor. This version is a
2505 release candidate: if no serious bugs are found, we expect that the
2506 stable 0.3.4 release will be (almost) the same as this release.
2508 o Major bugfixes (event scheduler):
2509 - When we enable a periodic event, schedule it in the event loop
2510 rather than running it immediately. Previously, we would re-run
2511 periodic events immediately in the middle of (for example)
2512 changing our options, with unpredictable effects. Fixes bug 27003;
2513 bugfix on 0.3.4.1-alpha.
2515 o Minor features (compilation):
2516 - When building Tor, prefer to use Python 3 over Python 2, and more
2517 recent (contemplated) versions over older ones. Closes
2519 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2520 tell the compiler not to include the system malloc implementation.
2521 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2522 - Don't try to use a pragma to temporarily disable the
2523 -Wunused-const-variable warning if the compiler doesn't support
2524 it. Fixes bug 26785; bugfix on 0.3.2.11.
2526 o Minor bugfixes (continuous integration):
2527 - Skip a pair of unreliable key generation tests on Windows, until
2528 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2529 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2531 o Minor features (controller):
2532 - The control port now exposes the list of HTTPTunnelPorts and
2533 ExtOrPorts via GETINFO net/listeners/httptunnel and
2534 net/listeners/extor respectively. Closes ticket 26647.
2536 o Minor bugfixes (directory authority):
2537 - When voting for recommended versions, make sure that all of the
2538 versions are well-formed and parsable. Fixes bug 26485; bugfix
2541 o Minor features (geoip):
2542 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2543 Country database. Closes ticket 26674.
2545 o Minor features (Rust, portability):
2546 - Rust cross-compilation is now supported. Closes ticket 25895.
2548 o Minor bugfixes (compilation):
2549 - Update build system so that tor builds again with --disable-unittests
2550 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
2551 - Fix a compilation warning on some versions of GCC when building
2552 code that calls routerinfo_get_my_routerinfo() twice, assuming
2553 that the second call will succeed if the first one did. Fixes bug
2554 26269; bugfix on 0.2.8.2-alpha.
2556 o Minor bugfixes (controller):
2557 - Report the port correctly when a port is configured to bind to
2558 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
2559 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
2560 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
2561 on 0.3.3.1-alpha. Patch by "akwizgran".
2563 o Minor bugfixes (correctness, flow control):
2564 - Upon receiving a stream-level SENDME cell, verify that our window
2565 has not grown too large. Fixes bug 26214; bugfix on svn
2568 o Minor bugfixes (memory, correctness):
2569 - Fix a number of small memory leaks identified by coverity. Fixes
2570 bug 26467; bugfix on numerous Tor versions.
2572 o Minor bugfixes (logging):
2573 - Improve the log message when connection initiators fail to
2574 authenticate direct connections to relays. Fixes bug 26927; bugfix
2577 o Minor bugfixes (portability):
2578 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
2579 26994; bugfix on 0.3.4.1-alpha.
2580 - Work around two different bugs in the OS X 10.10 and later SDKs
2581 that would prevent us from successfully targeting earlier versions
2582 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2584 o Minor bugfixes (single onion services, Tor2web):
2585 - Log a protocol warning when single onion services or Tor2web
2586 clients fail to authenticate direct connections to relays. Fixes
2587 bug 26924; bugfix on 0.2.9.1-alpha.
2589 o Minor bugfixes (testing):
2590 - Disable core dumps in test_bt.sh, to avoid failures in "make
2591 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2593 o Minor bugfixes (testing, compatibility):
2594 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
2595 only to pass strings (rather than "bytes" objects) to the Python
2596 subprocess module. Python 3 on Windows seems to require this.
2597 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
2598 0.3.1.1-alpha (for hs_ntor_ref.py).
2600 o Minor bugfixes (v3 onion services):
2601 - Stop sending ed25519 link specifiers in v3 onion service introduce
2602 cells and descriptors, when the rendezvous or introduction point
2603 doesn't support ed25519 link authentication. Fixes bug 26627;
2604 bugfix on 0.3.2.4-alpha.
2607 Changes in version 0.3.4.5-rc - 2018-07-13
2608 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
2609 bridge relays should upgrade.
2611 o Directory authority changes:
2612 - The "Bifroest" bridge authority has been retired; the new bridge
2613 authority is "Serge", and it is operated by George from the
2614 TorBSD project. Closes ticket 26771.
2617 Changes in version 0.3.3.9 - 2018-07-13
2618 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
2619 bridge relays should upgrade.
2621 o Directory authority changes:
2622 - The "Bifroest" bridge authority has been retired; the new bridge
2623 authority is "Serge", and it is operated by George from the
2624 TorBSD project. Closes ticket 26771.
2627 Changes in version 0.3.2.11 - 2018-07-13
2628 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
2629 bridge relays should upgrade. We also take this opportunity to backport
2632 o Directory authority changes:
2633 - The "Bifroest" bridge authority has been retired; the new bridge
2634 authority is "Serge", and it is operated by George from the
2635 TorBSD project. Closes ticket 26771.
2637 o Directory authority changes (backport from 0.3.3.7):
2638 - Add an IPv6 address for the "dannenberg" directory authority.
2639 Closes ticket 26343.
2641 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
2642 - When directory authorities read a zero-byte bandwidth file, they
2643 would previously log a warning with the contents of an
2644 uninitialised buffer. They now log a warning about the empty file
2645 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
2647 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
2648 - Correctly detect when onion services get disabled after HUP. Fixes
2649 bug 25761; bugfix on 0.3.2.1.
2651 o Minor features (sandbox, backport from 0.3.3.4-alpha):
2652 - Explicitly permit the poll() system call when the Linux
2653 seccomp2-based sandbox is enabled: apparently, some versions of
2654 libc use poll() when calling getpwnam(). Closes ticket 25313.
2656 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
2657 - Update the Travis CI configuration to use the stable Rust channel,
2658 now that we have decided to require that. Closes ticket 25714.
2660 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
2661 - Our .travis.yml configuration now includes support for testing the
2662 results of "make distcheck". (It's not uncommon for "make check"
2663 to pass but "make distcheck" to fail.) Closes ticket 25814.
2664 - Our Travis CI configuration now integrates with the Coveralls
2665 coverage analysis tool. Closes ticket 25818.
2667 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
2668 - Add several checks to detect whether Tor relays are uploading
2669 their descriptors without specifying why they regenerated them.
2670 Diagnostic for ticket 25686.
2672 o Minor features (compilation, backport from 0.3.4.4-rc):
2673 - When building Tor, prefer to use Python 3 over Python 2, and more
2674 recent (contemplated) versions over older ones. Closes
2677 o Minor features (geoip):
2678 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2679 Country database. Closes ticket 26674.
2681 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
2682 - Upon receiving a malformed connected cell, stop processing the
2683 cell immediately. Previously we would mark the connection for
2684 close, but continue processing the cell as if the connection were
2685 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
2687 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
2688 - Allow the nanosleep() system call, which glibc uses to implement
2689 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2691 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2692 - When running the hs_ntor_ref.py test, make sure only to pass
2693 strings (rather than "bytes" objects) to the Python subprocess
2694 module. Python 3 on Windows seems to require this. Fixes bug
2695 26535; bugfix on 0.3.1.1-alpha.
2696 - When running the ntor_ref.py test, make sure only to pass strings
2697 (rather than "bytes" objects) to the Python subprocess module.
2698 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2701 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
2702 - Work around a change in OpenSSL 1.1.1 where return values that
2703 would previously indicate "no password" now indicate an empty
2704 password. Without this workaround, Tor instances running with
2705 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2706 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2708 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
2709 - Document that the PerConnBW{Rate,Burst} options will fall back to
2710 their corresponding consensus parameters only if those parameters
2711 are set. Previously we had claimed that these values would always
2712 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
2714 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2715 - Fix a compilation warning on some versions of GCC when building
2716 code that calls routerinfo_get_my_routerinfo() twice, assuming
2717 that the second call will succeed if the first one did. Fixes bug
2718 26269; bugfix on 0.2.8.2-alpha.
2720 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
2721 - Don't consider Tor running as a client if the ControlPort is open,
2722 but no actual client ports are open. Fixes bug 26062; bugfix
2725 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
2726 - Prevent a possible out-of-bounds smartlist read in
2727 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
2729 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
2730 - Fix a very unlikely (impossible, we believe) null pointer
2731 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2732 Coverity; this is CID 1430932.
2734 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
2735 - Fix a memory leak when a v3 onion service is configured and gets a
2736 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
2737 - When parsing the descriptor signature, look for the token plus an
2738 extra white-space at the end. This is more correct but also will
2739 allow us to support new fields that might start with "signature".
2740 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
2742 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
2743 - Relays now correctly block attempts to re-extend to the previous
2744 relay by Ed25519 identity. Previously they would warn in this
2745 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2748 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
2749 - Avoid a crash when running with DirPort set but ORPort turned off.
2750 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
2752 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
2753 - Silence unused-const-variable warnings in zstd.h with some GCC
2754 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
2756 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
2757 - Avoid intermittent test failures due to a test that had relied on
2758 onion service introduction point creation finishing within 5
2759 seconds of real clock time. Fixes bug 25450; bugfix
2762 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
2763 - Fix a C99 compliance issue in our configuration script that caused
2764 compilation issues when compiling Tor with certain versions of
2765 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
2767 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2768 - Fix a number of small memory leaks identified by coverity. Fixes
2769 bug 26467; bugfix on numerous Tor versions.
2771 o Code simplification and refactoring (backport from 0.3.3.5-rc):
2772 - Move the list of default directory authorities to its own file.
2773 Closes ticket 24854. Patch by "beastr0".
2776 Changes in version 0.2.9.16 - 2018-07-13
2777 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
2778 bridge relays should upgrade. We also take this opportunity to backport
2781 o Directory authority changes:
2782 - The "Bifroest" bridge authority has been retired; the new bridge
2783 authority is "Serge", and it is operated by George from the
2784 TorBSD project. Closes ticket 26771.
2786 o Directory authority changes (backport from 0.3.3.7):
2787 - Add an IPv6 address for the "dannenberg" directory authority.
2788 Closes ticket 26343.
2790 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
2791 - When directory authorities read a zero-byte bandwidth file, they
2792 would previously log a warning with the contents of an
2793 uninitialised buffer. They now log a warning about the empty file
2794 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
2796 o Minor features (sandbox, backport from 0.3.3.4-alpha):
2797 - Explicitly permit the poll() system call when the Linux
2798 seccomp2-based sandbox is enabled: apparently, some versions of
2799 libc use poll() when calling getpwnam(). Closes ticket 25313.
2801 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
2802 - Our .travis.yml configuration now includes support for testing the
2803 results of "make distcheck". (It's not uncommon for "make check"
2804 to pass but "make distcheck" to fail.) Closes ticket 25814.
2805 - Our Travis CI configuration now integrates with the Coveralls
2806 coverage analysis tool. Closes ticket 25818.
2808 o Minor features (compilation, backport from 0.3.4.4-rc):
2809 - When building Tor, prefer to use Python 3 over Python 2, and more
2810 recent (contemplated) versions over older ones. Closes
2813 o Minor features (geoip):
2814 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2815 Country database. Closes ticket 26674.
2817 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
2818 - Upon receiving a malformed connected cell, stop processing the
2819 cell immediately. Previously we would mark the connection for
2820 close, but continue processing the cell as if the connection were
2821 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
2823 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
2824 - Allow the nanosleep() system call, which glibc uses to implement
2825 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
2827 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2828 - When running the ntor_ref.py test, make sure only to pass strings
2829 (rather than "bytes" objects) to the Python subprocess module.
2830 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2833 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
2834 - Work around a change in OpenSSL 1.1.1 where return values that
2835 would previously indicate "no password" now indicate an empty
2836 password. Without this workaround, Tor instances running with
2837 OpenSSL 1.1.1 would accept descriptors that other Tor instances
2838 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
2840 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2841 - Fix a compilation warning on some versions of GCC when building
2842 code that calls routerinfo_get_my_routerinfo() twice, assuming
2843 that the second call will succeed if the first one did. Fixes bug
2844 26269; bugfix on 0.2.8.2-alpha.
2846 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
2847 - Don't consider Tor running as a client if the ControlPort is open,
2848 but no actual client ports are open. Fixes bug 26062; bugfix
2851 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
2852 - Prevent a possible out-of-bounds smartlist read in
2853 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
2855 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
2856 - Fix a very unlikely (impossible, we believe) null pointer
2857 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
2858 Coverity; this is CID 1430932.
2860 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2861 - Fix a number of small memory leaks identified by coverity. Fixes
2862 bug 26467; bugfix on numerous Tor versions.
2864 o Code simplification and refactoring (backport from 0.3.3.5-rc):
2865 - Move the list of default directory authorities to its own file.
2866 Closes ticket 24854. Patch by "beastr0".
2869 Changes in version 0.3.4.4-rc - 2018-07-09
2870 Tor 0.3.4.4-rc fixes several small compilation, portability, and
2871 correctness issues in previous versions of Tor. This version is a
2872 release candidate: if no serious bugs are found, we expect that the
2873 stable 0.3.4 release will be (almost) the same as this release.
2875 o Minor features (compilation):
2876 - When building Tor, prefer to use Python 3 over Python 2, and more
2877 recent (contemplated) versions over older ones. Closes
2880 o Minor features (geoip):
2881 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2882 Country database. Closes ticket 26674.
2884 o Minor features (Rust, portability):
2885 - Rust cross-compilation is now supported. Closes ticket 25895.
2887 o Minor bugfixes (compilation):
2888 - Fix a compilation warning on some versions of GCC when building
2889 code that calls routerinfo_get_my_routerinfo() twice, assuming
2890 that the second call will succeed if the first one did. Fixes bug
2891 26269; bugfix on 0.2.8.2-alpha.
2893 o Minor bugfixes (control port):
2894 - Report the port correctly when a port is configured to bind to
2895 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
2896 - Handle the HSADDRESS= argument to the HSPOST command properly.
2897 (Previously, this argument was misparsed and thus ignored.) Fixes
2898 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
2900 o Minor bugfixes (correctness, flow control):
2901 - Upon receiving a stream-level SENDME cell, verify that our window
2902 has not grown too large. Fixes bug 26214; bugfix on svn
2905 o Minor bugfixes (memory, correctness):
2906 - Fix a number of small memory leaks identified by coverity. Fixes
2907 bug 26467; bugfix on numerous Tor versions.
2909 o Minor bugfixes (testing, compatibility):
2910 - When running the hs_ntor_ref.py test, make sure only to pass
2911 strings (rather than "bytes" objects) to the Python subprocess
2912 module. Python 3 on Windows seems to require this. Fixes bug
2913 26535; bugfix on 0.3.1.1-alpha.
2914 - When running the ntor_ref.py test, make sure only to pass strings
2915 (rather than "bytes" objects) to the Python subprocess module.
2916 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2920 Changes in version 0.3.3.8 - 2018-07-09
2921 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
2922 fixes for a memory leak affecting directory authorities.
2924 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
2925 - Stop leaking memory on directory authorities when planning to
2926 vote. This bug was crashing authorities by exhausting their
2927 memory. Fixes bug 26435; bugfix on 0.3.3.6.
2929 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
2930 - Make sure that failing tests in Rust will actually cause the build
2931 to fail: previously, they were ignored. Fixes bug 26258; bugfix
2934 o Minor features (compilation, backport from 0.3.4.4-rc):
2935 - When building Tor, prefer to use Python 3 over Python 2, and more
2936 recent (contemplated) versions over older ones. Closes
2939 o Minor features (geoip):
2940 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
2941 Country database. Closes ticket 26674.
2943 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
2944 - Add several checks to detect whether Tor relays are uploading
2945 their descriptors without specifying why they regenerated them.
2946 Diagnostic for ticket 25686.
2948 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
2949 - Don't count path selection failures as circuit build failures.
2950 This change should eliminate cases where Tor blames its guard or
2951 the network for situations like insufficient microdescriptors
2952 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
2955 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
2956 - Fix a compilation warning on some versions of GCC when building
2957 code that calls routerinfo_get_my_routerinfo() twice, assuming
2958 that the second call will succeed if the first one did. Fixes bug
2959 26269; bugfix on 0.2.8.2-alpha.
2961 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
2962 - Handle the HSADDRESS= argument to the HSPOST command properly.
2963 (Previously, this argument was misparsed and thus ignored.) Fixes
2964 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
2966 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
2967 - Fix a number of small memory leaks identified by coverity. Fixes
2968 bug 26467; bugfix on numerous Tor versions.
2970 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
2971 - Relays now correctly block attempts to re-extend to the previous
2972 relay by Ed25519 identity. Previously they would warn in this
2973 case, but not actually reject the attempt. Fixes bug 26158; bugfix
2976 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
2977 - When shutting down, Tor now clears all the flags in the control.c
2978 module. This should prevent a bug where authentication cookies are
2979 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
2981 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
2982 - When running the hs_ntor_ref.py test, make sure only to pass
2983 strings (rather than "bytes" objects) to the Python subprocess
2984 module. Python 3 on Windows seems to require this. Fixes bug
2985 26535; bugfix on 0.3.1.1-alpha.
2986 - When running the ntor_ref.py test, make sure only to pass strings
2987 (rather than "bytes" objects) to the Python subprocess module.
2988 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
2992 Changes in version 0.3.4.3-alpha - 2018-06-26
2993 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
2994 one that was causing stability issues on directory authorities.
2996 o Major bugfixes (directory authority):
2997 - Stop leaking memory on directory authorities when planning to
2998 vote. This bug was crashing authorities by exhausting their
2999 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3001 o Major bugfixes (rust, testing):
3002 - Make sure that failing tests in Rust will actually cause the build
3003 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3006 o Minor feature (directory authorities):
3007 - Stop warning about incomplete bw lines before the first complete
3008 bw line has been found, so that additional header lines can be
3009 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
3011 o Minor features (relay, diagnostic):
3012 - Add several checks to detect whether Tor relays are uploading
3013 their descriptors without specifying why they regenerated them.
3014 Diagnostic for ticket 25686.
3016 o Minor features (unit tests):
3017 - Test complete bandwidth measurements files, and test that
3018 incomplete bandwidth lines only give warnings when the end of the
3019 header has not been detected. Fixes bug 25947; bugfix
3022 o Minor bugfixes (compilation):
3023 - Refrain from compiling unit testing related object files when
3024 --disable-unittests is set to configure script. Fixes bug 24891;
3025 bugfix on 0.2.5.1-alpha.
3026 - When linking the libtor_testing.a library, only include the
3027 dirauth object files once. Previously, they were getting added
3028 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
3029 - The --enable-fatal-warnings flag now affects Rust code as well.
3030 Closes ticket 26245.
3032 o Minor bugfixes (onion services):
3033 - Recompute some consensus information after detecting a clock jump,
3034 or after transitioning from a non-live consensus to a live
3035 consensus. We do this to avoid having an outdated state, and
3036 miscalculating the index for next-generation onion services. Fixes
3037 bug 24977; bugfix on 0.3.2.1-alpha.
3039 o Minor bugfixes (relay):
3040 - Relays now correctly block attempts to re-extend to the previous
3041 relay by Ed25519 identity. Previously they would warn in this
3042 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3045 o Minor bugfixes (testing):
3046 - Fix compilation of the doctests in the Rust crypto crate. Fixes
3047 bug 26415; bugfix on 0.3.4.1-alpha.
3048 - Instead of trying to read the geoip configuration files from
3049 within the unit tests, instead create our own ersatz files with
3050 just enough geoip data in the format we expect. Trying to read
3051 from the source directory created problems on Windows with mingw,
3052 where the build system's paths are not the same as the platform's
3053 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
3054 - Refrain from trying to get an item from an empty smartlist in
3055 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
3056 to catch improper smartlist usage. Furthermore, enable
3057 DEBUG_SMARTLIST globally when build is configured with fragile
3058 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
3061 Changes in version 0.3.3.7 - 2018-06-12
3062 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
3063 fixes for bugs affecting compatibility and stability.
3065 o Directory authority changes:
3066 - Add an IPv6 address for the "dannenberg" directory authority.
3067 Closes ticket 26343.
3069 o Minor features (geoip):
3070 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3071 Country database. Closes ticket 26351.
3073 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3074 - Work around a change in OpenSSL 1.1.1 where return values that
3075 would previously indicate "no password" now indicate an empty
3076 password. Without this workaround, Tor instances running with
3077 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3078 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3080 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3081 - Silence unused-const-variable warnings in zstd.h with some GCC
3082 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3084 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
3085 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3086 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3087 miscounting the total number of circuits for these field values.)
3088 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3090 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3091 - Prevent a possible out-of-bounds smartlist read in
3092 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3094 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
3095 - Only select relays when they have the descriptors we prefer to use
3096 for them. This change fixes a bug where we could select a relay
3097 because it had _some_ descriptor, but reject it later with a
3098 nonfatal assertion error because it didn't have the exact one we
3099 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3102 Changes in version 0.3.4.2-alpha - 2018-06-12
3103 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
3104 release, and forward-ports an authority-only security fix from 0.3.3.6.
3106 o Directory authority changes:
3107 - Add an IPv6 address for the "dannenberg" directory authority.
3108 Closes ticket 26343.
3110 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
3111 - Fix a bug that could have allowed an attacker to force a directory
3112 authority to use up all its RAM by passing it a maliciously
3113 crafted protocol versions string. Fixes bug 25517; bugfix on
3114 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3116 o Minor features (continuous integration):
3117 - Add the necessary configuration files for continuous integration
3118 testing on Windows, via the Appveyor platform. Closes ticket
3119 25549. Patches from Marcin Cieślak and Isis Lovecruft.
3121 o Minor features (geoip):
3122 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3123 Country database. Closes ticket 26351.
3125 o Minor bugfixes (compatibility, openssl):
3126 - Work around a change in OpenSSL 1.1.1 where return values that
3127 would previously indicate "no password" now indicate an empty
3128 password. Without this workaround, Tor instances running with
3129 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3130 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3132 o Minor bugfixes (compilation):
3133 - Silence unused-const-variable warnings in zstd.h with some GCC
3134 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3135 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
3136 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
3137 - Avoid a compiler warning when casting the return value of
3138 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
3139 26283; bugfix on 0.2.4.10-alpha.
3141 o Minor bugfixes (control port):
3142 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
3143 CIRC_BW events. Previously, such cells were counted entirely in
3144 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
3147 o Minor bugfixes (controller):
3148 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3149 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3150 miscounting the total number of circuits for these field values.)
3151 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3153 o Minor bugfixes (hardening):
3154 - Prevent a possible out-of-bounds smartlist read in
3155 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3157 o Minor bugfixes (onion services):
3158 - Fix a bug that blocked the creation of ephemeral v3 onion
3159 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
3161 o Minor bugfixes (test coverage tools):
3162 - Update our "cov-diff" script to handle output from the latest
3163 version of gcov, and to remove extraneous timestamp information
3164 from its output. Fixes bugs 26101 and 26102; bugfix
3168 Changes in version 0.3.3.6 - 2018-05-22
3169 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
3170 backports several important fixes from the 0.3.4.1-alpha.
3172 The Tor 0.3.3 series includes controller support and other
3173 improvements for v3 onion services, official support for embedding Tor
3174 within other applications, and our first non-trivial module written in
3175 the Rust programming language. (Rust is still not enabled by default
3176 when building Tor.) And as usual, there are numerous other smaller
3177 bugfixes, features, and improvements.
3179 Below are the changes since 0.3.3.5-rc. For a list of all changes
3180 since 0.3.2.10, see the ReleaseNotes file.
3182 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
3183 - When directory authorities read a zero-byte bandwidth file, they
3184 would previously log a warning with the contents of an
3185 uninitialised buffer. They now log a warning about the empty file
3186 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3188 o Major bugfixes (security, directory authority, denial-of-service):
3189 - Fix a bug that could have allowed an attacker to force a directory
3190 authority to use up all its RAM by passing it a maliciously
3191 crafted protocol versions string. Fixes bug 25517; bugfix on
3192 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3194 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
3195 - Avoid a rare assertion failure in the circuit build timeout code
3196 if we fail to allow any circuits to actually complete. Fixes bug
3197 25733; bugfix on 0.2.2.2-alpha.
3199 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3200 - Avoid a crash when testing router reachability on a router that
3201 could have an ed25519 ID, but which does not. Fixes bug 25415;
3202 bugfix on 0.3.3.2-alpha.
3204 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3205 - Correctly detect when onion services get disabled after HUP. Fixes
3206 bug 25761; bugfix on 0.3.2.1.
3208 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
3209 - Impose a limit on circuit cell queue size. The limit can be
3210 controlled by a consensus parameter. Fixes bug 25226; bugfix
3213 o Minor features (compatibility, backport from 0.3.4.1-alpha):
3214 - Avoid some compilation warnings with recent versions of LibreSSL.
3215 Closes ticket 26006.
3217 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3218 - Our .travis.yml configuration now includes support for testing the
3219 results of "make distcheck". (It's not uncommon for "make check"
3220 to pass but "make distcheck" to fail.) Closes ticket 25814.
3221 - Our Travis CI configuration now integrates with the Coveralls
3222 coverage analysis tool. Closes ticket 25818.
3224 o Minor features (geoip):
3225 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
3226 database. Closes ticket 26104.
3228 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3229 - Don't consider Tor running as a client if the ControlPort is open,
3230 but no actual client ports are open. Fixes bug 26062; bugfix
3233 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3234 - Upon receiving a malformed connected cell, stop processing the
3235 cell immediately. Previously we would mark the connection for
3236 close, but continue processing the cell as if the connection were
3237 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3239 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
3240 - Stop saying in the manual that clients cache ipv4 dns answers from
3241 exit relays. We haven't used them since 0.2.6.3-alpha, and in
3242 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
3243 we forgot to say so in the man page. Fixes bug 26052; bugfix
3246 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3247 - Allow the nanosleep() system call, which glibc uses to implement
3248 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3250 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3251 - Fix a memory leak when a v3 onion service is configured and gets a
3252 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3253 - When parsing the descriptor signature, look for the token plus an
3254 extra white-space at the end. This is more correct but also will
3255 allow us to support new fields that might start with "signature".
3256 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3258 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3259 - Avoid a crash when running with DirPort set but ORPort turned off.
3260 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3262 o Documentation (backport from 0.3.4.1-alpha):
3263 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
3264 ticket 25857. Patch from "CTassisF".
3267 Changes in version 0.3.4.1-alpha - 2018-05-17
3268 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
3269 includes refactoring to begin reducing Tor's binary size and idle CPU
3270 usage on mobile, along with prep work for new bandwidth scanners,
3271 improvements to the experimental "vanguards" feature, and numerous
3272 other small features and bugfixes.
3274 o New system requirements:
3275 - Tor no longer tries to support old operating systems without
3276 mmap() or some local equivalent. Apparently, compilation on such
3277 systems has been broken for some time, without anybody noticing or
3278 complaining. Closes ticket 25398.
3280 o Major feature (directory authority, modularization):
3281 - The directory authority subsystem has been modularized. The code
3282 is now located in src/or/dirauth/, and is compiled in by default.
3283 To disable the module, the configure option
3284 --disable-module-dirauth has been added. This module may be
3285 disabled by default in some future release. Closes ticket 25610.
3287 o Major features (main loop, CPU usage):
3288 - When Tor is disabled (via DisableNetwork or via hibernation), it
3289 no longer needs to run any per-second events. This change should
3290 make it easier for mobile applications to disable Tor while the
3291 device is sleeping, or Tor is not running. Closes ticket 26063.
3292 - Tor no longer enables all of its periodic events by default.
3293 Previously, Tor would enable all possible main loop events,
3294 regardless of whether it needed them. Furthermore, many of these
3295 events are now disabled with Tor is hibernating or DisableNetwork
3296 is set. This is a big step towards reducing client CPU usage by
3297 reducing the amount of wake-ups the daemon does. Closes ticket
3299 - The bandwidth-limitation logic has been refactored so that
3300 bandwidth calculations are performed on-demand, rather than every
3301 TokenBucketRefillInterval milliseconds. This change should improve
3302 the granularity of our bandwidth calculations, and limit the
3303 number of times that the Tor process needs to wake up when it is
3304 idle. Closes ticket 25373.
3305 - Move responsibility for many operations from a once-per-second
3306 callback to a callback that is only scheduled as needed. Moving
3307 this functionality has allowed us to disable the callback when
3308 Tor's network is disabled. Once enough items are removed from our
3309 once-per-second callback, we can eliminate it entirely to conserve
3310 CPU when idle. The functionality removed includes: closing
3311 connections, circuits, and channels (ticket 25932); consensus
3312 voting (25937); flushing log callbacks (25951); honoring delayed
3313 SIGNEWNYM requests (25949); rescanning the consensus cache
3314 (25931); saving the state file to disk (25948); warning relay
3315 operators about unreachable ports (25952); and keeping track of
3316 Tor's uptime (26009).
3318 o Major bugfixes (directory authorities, security):
3319 - When directory authorities read a zero-byte bandwidth file, they
3320 would previously log a warning with the contents of an
3321 uninitialised buffer. They now log a warning about the empty file
3322 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3324 o Major bugfixes (crash):
3325 - Avoid a rare assertion failure in the circuit build timeout code
3326 if we fail to allow any circuits to actually complete. Fixes bug
3327 25733; bugfix on 0.2.2.2-alpha.
3329 o Major bugfixes (directory authority):
3330 - Avoid a crash when testing router reachability on a router that
3331 could have an ed25519 ID, but which does not. Fixes bug 25415;
3332 bugfix on 0.3.3.2-alpha.
3334 o Major bugfixes (onion service):
3335 - Correctly detect when onion services get disabled after HUP. Fixes
3336 bug 25761; bugfix on 0.3.2.1.
3338 o Major bugfixes (protover, voting):
3339 - Revise Rust implementation of protover to use a more memory-
3340 efficient voting algorithm and corresponding data structures, thus
3341 avoiding a potential (but small impact) DoS attack where specially
3342 crafted protocol strings would expand to several potential
3343 megabytes in memory. In the process, several portions of code were
3344 revised to be methods on new, custom types, rather than functions
3345 taking interchangeable types, thus increasing type safety of the
3346 module. Custom error types and handling were added as well, in
3347 order to facilitate better error dismissal/handling in outside
3348 crates and avoid mistakenly passing an internal error string to C
3349 over the FFI boundary. Many tests were added, and some previous
3350 differences between the C and Rust implementations have been
3351 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
3353 o Major bugfixes (relay, denial of service):
3354 - Impose a limit on circuit cell queue size. The limit can be
3355 controlled by a consensus parameter. Fixes bug 25226; bugfix
3358 o Minor features (accounting):
3359 - When Tor becomes dormant, it now uses a scheduled event to wake up
3360 at the right time. Previously, we would use the per-second timer
3361 to check whether to wake up, but we no longer have any per-second
3362 timers enabled when the network is disabled. Closes ticket 26064.
3364 o Minor features (code quality):
3365 - Add optional spell-checking for the Tor codebase, using the
3366 "misspell" program. To use this feature, run "make check-typos".
3367 Closes ticket 25024.
3369 o Minor features (compatibility):
3370 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
3371 the no-deprecated option, and builds correctly with them. Closes
3372 tickets 19429, 19981, and 25353.
3373 - Avoid some compilation warnings with recent versions of LibreSSL.
3374 Closes ticket 26006.
3376 o Minor features (compression, zstd):
3377 - When running with zstd, Tor now considers using advanced functions
3378 that the zstd maintainers have labeled as potentially unstable. To
3379 prevent breakage, Tor will only use this functionality when the
3380 runtime version of the zstd library matches the version with which
3381 Tor was compiled. Closes ticket 25162.
3383 o Minor features (configuration):
3384 - The "DownloadSchedule" options have been renamed to end with
3385 "DownloadInitialDelay". The old names are still allowed, but will
3386 produce a warning. Comma-separated lists are still permitted for
3387 these options, but all values after the first are ignored (as they
3388 have been since 0.2.9). Closes ticket 23354.
3390 o Minor features (continuous integration):
3391 - Our .travis.yml configuration now includes support for testing the
3392 results of "make distcheck". (It's not uncommon for "make check"
3393 to pass but "make distcheck" to fail.) Closes ticket 25814.
3394 - Our Travis CI configuration now integrates with the Coveralls
3395 coverage analysis tool. Closes ticket 25818.
3397 o Minor features (control port):
3398 - Introduce GETINFO "current-time/{local,utc}" to return the local
3399 and UTC times respectively in ISO format. This helps a controller
3400 like Tor Browser detect a time-related error. Closes ticket 25511.
3401 Patch by Neel Chauhan.
3402 - Introduce new fields to the CIRC_BW event. There are two new
3403 fields in each of the read and written directions. The DELIVERED
3404 fields report the total valid data on the circuit, as measured by
3405 the payload sizes of verified and error-checked relay command
3406 cells. The OVERHEAD fields report the total unused bytes in each
3407 of these cells. Closes ticket 25903.
3409 o Minor features (directory authority):
3410 - Directory authorities now open their key-pinning files as O_SYNC,
3411 to limit their chances of accidentally writing partial lines.
3412 Closes ticket 23909.
3414 o Minor features (directory authority, forward compatibility):
3415 - Make the lines of the measured bandwidth file able to contain
3416 their entries in any order. Previously, the node_id entry needed
3417 to come first. Closes ticket 26004.
3419 o Minor features (entry guards):
3420 - Introduce a new torrc option NumPrimaryGuards for controlling the
3421 number of primary guards. Closes ticket 25843.
3423 o Minor features (geoip):
3424 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
3425 database. Closes ticket 26104.
3427 o Minor features (performance):
3428 - Avoid a needless call to malloc() when processing an incoming
3429 relay cell. Closes ticket 24914.
3430 - Make our timing-wheel code run a tiny bit faster on 32-bit
3431 platforms, by preferring 32-bit math to 64-bit. Closes
3433 - Avoid a needless malloc()/free() pair every time we handle an ntor
3434 handshake. Closes ticket 25150.
3436 o Minor features (testing):
3437 - Add a unit test for voting_schedule_get_start_of_next_interval().
3438 Closes ticket 26014, and helps make unit test coverage
3440 - A new unittests module specifically for testing the functions in
3441 the (new-ish) bridges.c module has been created with new
3442 unittests, raising the code coverage percentages. Closes 25425.
3443 - We now have improved testing for addressmap_get_virtual_address()
3444 function. This should improve our test coverage, and make our test
3445 coverage more deterministic. Closes ticket 25993.
3447 o Minor features (timekeeping, circuit scheduling):
3448 - When keeping track of how busy each circuit have been recently on
3449 a given connection, use coarse-grained monotonic timers rather
3450 than gettimeofday(). This change should marginally increase
3451 accuracy and performance. Implements part of ticket 25927.
3453 o Minor bugfixes (bandwidth management):
3454 - Consider ourselves "low on write bandwidth" if we have exhausted
3455 our write bandwidth some time in the last second. This was the
3456 documented behavior before, but the actual behavior was to change
3457 this value every TokenBucketRefillInterval. Fixes bug 25828;
3458 bugfix on 0.2.3.5-alpha.
3460 o Minor bugfixes (C correctness):
3461 - Add a missing lock acquisition in the shutdown code of the control
3462 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
3463 Coverity; this is CID 1433643.
3465 o Minor bugfixes (circuit path selection):
3466 - Don't count path selection failures as circuit build failures.
3467 This change should eliminate cases where Tor blames its guard or
3468 the network for situations like insufficient microdescriptors
3469 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
3472 o Minor bugfixes (client):
3473 - Don't consider Tor running as a client if the ControlPort is open,
3474 but no actual client ports are open. Fixes bug 26062; bugfix
3477 o Minor bugfixes (code style):
3478 - Fixed multiple includes of transports.h in src/or/connection.c
3479 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
3480 - Remove the unused variable n_possible from the function
3481 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
3483 o Minor bugfixes (control interface):
3484 - Respond with more human-readable error messages to GETINFO exit-
3485 policy/* requests. Also, let controller know if an error is
3486 transient (response code 551) or not (response code 552). Fixes
3487 bug 25852; bugfix on 0.2.8.1-alpha.
3489 o Minor bugfixes (controller):
3490 - Make CIRC_BW event reflect the total of all data sent on a
3491 circuit, including padding and dropped cells. Also fix a mis-
3492 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
3493 bugfix on 0.2.5.2-alpha.
3495 o Minor bugfixes (correctness, client):
3496 - Upon receiving a malformed connected cell, stop processing the cell
3497 immediately. Previously we would mark the connection for close, but
3498 continue processing the cell as if the connection were open. Fixes bug
3499 26072; bugfix on 0.2.4.7-alpha.
3501 o Minor bugfixes (directory client):
3502 - When unverified-consensus is verified, rename it to cached-
3503 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
3504 - Fixed launching a certificate fetch always during the scheduled
3505 periodic consensus fetch by fetching only in those cases when
3506 consensus are waiting for certs. Fixes bug 24740; bugfix
3509 o Minor bugfixes (documentation):
3510 - Stop saying in the manual that clients cache ipv4 dns answers from
3511 exit relays. We haven't used them since 0.2.6.3-alpha, and in
3512 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
3513 we forgot to say so in the man page. Fixes bug 26052; bugfix
3516 o Minor bugfixes (error reporting):
3517 - Improve tolerance for directory authorities with skewed clocks.
3518 Previously, an authority with a clock more than 60 seconds ahead
3519 could cause a client with a correct clock to warn that the
3520 client's clock was behind. Now the clocks of a majority of
3521 directory authorities have to be ahead of the client before this
3522 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
3524 o Minor bugfixes (Linux seccomp2 sandbox):
3525 - Allow the nanosleep() system call, which glibc uses to implement
3526 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3528 o Minor bugfixes (onion service):
3529 - Fix a memory leak when a v3 onion service is configured and gets a
3530 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3531 - When parsing the descriptor signature, look for the token plus an
3532 extra white-space at the end. This is more correct but also will
3533 allow us to support new fields that might start with "signature".
3534 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3536 o Minor bugfixes (path selection):
3537 - Only select relays when they have the descriptors we prefer to use
3538 for them. This change fixes a bug where we could select a relay
3539 because it had _some_ descriptor, but reject it later with a
3540 nonfatal assertion error because it didn't have the exact one we
3541 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3543 o Minor bugfixes (portability):
3544 - Do not align mmap length, as it is not required by POSIX, and the
3545 getpagesize function is deprecated. Fixes bug 25399; bugfix
3548 o Minor bugfixes (portability, FreeBSD):
3549 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
3550 does not stringify on FreeBSD, so we switch to tor_asprintf().
3551 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
3553 o Minor bugfixes (relay statistics):
3554 - When a relay is collecting internal statistics about how many
3555 create cell requests it has seen of each type, accurately count
3556 the requests from relays that temporarily fall out of the
3557 consensus. (To be extra conservative, we were already ignoring
3558 requests from clients in our counts, and we continue ignoring them
3559 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
3561 o Minor bugfixes (relay, crash):
3562 - Avoid a crash when running with DirPort set but ORPort turned off.
3563 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3565 o Minor bugfixes (restart-in-process):
3566 - When shutting down, Tor now clears all the flags in the control.c
3567 module. This should prevent a bug where authentication cookies are
3568 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
3570 o Minor bugfixes (testing):
3571 - When testing workqueue event-cancellation, make sure that we
3572 actually cancel an event, and that cancel each event with equal
3573 probability. (It was previously possible, though extremely
3574 unlikely, for our event-canceling test not to cancel any events.)
3575 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
3576 - Repeat part of the test in test_client_pick_intro() a number of
3577 times, to give it consistent coverage. Fixes bug 25996; bugfix
3579 - Remove randomness from the hs_common/responsible_hsdirs test, so
3580 that it always takes the same path through the function it tests.
3581 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
3582 - Change the behavior of the "channel/outbound" test so that it
3583 never causes a 10-second rollover for the EWMA circuitmux code.
3584 Previously, this behavior would happen randomly, and result in
3585 fluctuating test coverage. Fixes bug 25994; bugfix
3587 - Use X509_new() to allocate certificates that will be freed later
3588 with X509_free(). Previously, some parts of the unit tests had
3589 used tor_malloc_zero(), which is incorrect, and which caused test
3590 failures on Windows when they were built with extra hardening.
3591 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
3593 - While running the circuit_timeout test, fix the PRNG to a
3594 deterministic AES stream, so that the test coverage from this test
3595 will itself be deterministic. Fixes bug 25995; bugfix
3598 o Minor bugfixes (vanguards):
3599 - Allow the last hop in a vanguard circuit to be the same as our
3600 first, to prevent the adversary from influencing guard node choice
3601 by choice of last hop. Also prevent the creation of A - B - A
3602 paths, or A - A paths, which are forbidden by relays. Fixes bug
3603 25870; bugfix on 0.3.3.1-alpha.
3605 o Code simplification and refactoring:
3606 - Remove duplicate code in parse_{c,s}method_line and bootstrap
3607 their functionalities into a single function. Fixes bug 6236;
3608 bugfix on 0.2.3.6-alpha.
3609 - We remove the PortForwsrding and PortForwardingHelper options,
3610 related functions, and the port_forwarding tests. These options
3611 were used by the now-deprecated Vidalia to help ordinary users
3612 become Tor relays or bridges. Closes ticket 25409. Patch by
3614 - In order to make the OR and dir checking function in router.c less
3615 confusing we renamed some functions and
3616 consider_testing_reachability() has been split into
3617 router_should_check_reachability() and
3618 router_do_reachability_checks(). Also we improved the documentation
3619 in some functions. Closes ticket 18918.
3620 - Initial work to isolate Libevent usage to a handful of modules in
3621 our codebase, to simplify our call structure, and so that we can
3622 more easily change event loops in the future if needed. Closes
3624 - Introduce a function to call getsockname() and return tor_addr_t,
3625 to save a little complexity throughout the codebase. Closes
3627 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
3628 as hsdir_index is always present. Also, we move hsdir_index_t into
3629 or.h. Closes ticket 23094. Patch by Neel Chauhan.
3630 - Merge functions used for describing nodes and suppress the
3631 functions that do not allocate memory for the output buffer
3632 string. NODE_DESC_BUF_LEN constant and format_node_description()
3633 function cannot be used externally from router.c module anymore.
3634 Closes ticket 25432. Patch by valentecaio.
3635 - Our main loop has been simplified so that all important operations
3636 happen inside events. Previously, some operations had to happen
3637 outside the event loop, to prevent infinite sequences of event
3638 activations. Closes ticket 25374.
3639 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
3640 it in register_intro_circ() and service_intro_point_new(). This
3641 prevents the digest from being re-calculated each time. Closes
3642 ticket 23107. Patch by Neel Chauhan.
3643 - Refactor token-bucket implementations to use a common backend.
3644 Closes ticket 25766.
3645 - Remove extern declaration of stats_n_seconds_working variable from
3646 main, protecting its accesses with get_uptime() and reset_uptime()
3647 functions. Closes ticket 25081, patch by “valentecaio”.
3648 - Remove our previous logic for "cached gettimeofday()" -- our
3649 coarse monotonic timers are fast enough for this purpose, and far
3650 less error-prone. Implements part of ticket 25927.
3651 - Remove the return value for fascist_firewall_choose_address_base(),
3652 and sister functions such as fascist_firewall_choose_address_node()
3653 and fascist_firewall_choose_address_rs(). Also, while we're here,
3654 initialize the ap argument as leaving it uninitialized can pose a
3655 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
3656 - Rename two fields of connection_t struct. timestamp_lastwritten is
3657 renamed to timestamp_last_write_allowed and timestamp_lastread is
3658 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
3660 - Since Tor requires C99, remove our old workaround code for libc
3661 implementations where free(NULL) doesn't work. Closes ticket 24484.
3662 - Use our standard rate-limiting code to deal with excessive
3663 libevent failures, rather than the hand-rolled logic we had
3664 before. Closes ticket 26016.
3665 - We remove the return value of node_get_prim_orport() and
3666 node_get_prim_dirport(), and introduce node_get_prim_orport() in
3667 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
3668 check for a null address. Closes ticket 23873. Patch by
3670 - We switch to should_record_bridge_info() in
3671 geoip_note_client_seen() and options_need_geoip_info() instead of
3672 accessing the configuration values directly. Fixes bug 25290;
3673 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
3675 o Deprecated features:
3676 - As we are not recommending 0.2.5 anymore, we require relays that
3677 once had an ed25519 key associated with their RSA key to always
3678 have that key, instead of allowing them to drop back to a version
3679 that didn't support ed25519. This means they need to use a new RSA
3680 key if they want to downgrade to an older version of tor without
3681 ed25519. Closes ticket 20522.
3684 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
3685 ticket 25857. Patch from "CTassisF".
3688 - Directory authorities will no longer support voting according to
3689 any consensus method before consensus method 25. This keeps
3690 authorities compatible with all authorities running 0.2.9.8 and
3691 later, and does not break any clients or relays. Implements ticket
3692 24378 and proposal 290.
3693 - The PortForwarding and PortForwardingHelper features have been
3694 removed. The reasoning is, given that implementations of NAT
3695 traversal protocols within common consumer grade routers are
3696 frequently buggy, and that the target audience for a NAT punching
3697 feature is a perhaps less-technically-inclined relay operator,
3698 when the helper fails to setup traversal the problems are usually
3699 deep, ugly, and very router specific, making them horrendously
3700 impossible for technical support to reliable assist with, and thus
3701 resulting in frustration all around. Unfortunately, relay
3702 operators who would like to run relays behind NATs will need to
3703 become more familiar with the port forwarding configurations on
3704 their local router. Closes 25409.
3705 - The TestingEnableTbEmptyEvent option has been removed. It was used
3706 in testing simulations to measure how often connection buckets
3707 were emptied, in order to improve our scheduling, but it has not
3708 been actively used in years. Closes ticket 25760.
3709 - The old "round-robin" circuit multiplexer (circuitmux)
3710 implementation has been removed, along with a fairly large set of
3711 code that existed to support it. It has not been the default
3712 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
3713 but it still required an unreasonable amount of memory and CPU.
3714 Closes ticket 25268.
3717 Changes in version 0.3.3.5-rc - 2018-04-15
3718 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
3719 including some that could affect reliability or correctness.
3721 This is the first release candidate in the 0.3.3 series. If we find no
3722 new bugs or regression here, then the first stable 0.3.3 release will
3723 be nearly identical to this one.
3725 o Major bugfixes (security, protover, voting):
3726 - Revise Rust implementation of protover to use a more memory-
3727 efficient voting algorithm and corresponding data structures, thus
3728 avoiding a potential memory-based DoS attack where specially
3729 crafted protocol strings would expand to fill available memory.
3730 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
3732 o Major bugfixes (performance, load balancing):
3733 - Directory authorities no longer vote in favor of the Guard flag
3734 for relays without directory support. Starting in Tor
3735 0.3.0.1-alpha, clients have been avoiding using such relays in the
3736 Guard position, leading to increasingly broken load balancing for
3737 the 5%-or-so of Guards that don't advertise directory support.
3738 Fixes bug 22310; bugfix on 0.3.0.6.
3740 o Minor feature (continuous integration):
3741 - Update the Travis CI configuration to use the stable Rust channel,
3742 now that we have decided to require that. Closes ticket 25714.
3744 o Minor features (config options):
3745 - Change the way the default value for MaxMemInQueues is calculated.
3746 We now use 40% of the hardware RAM if the system has 8 GB RAM or
3747 more. Otherwise we use the former value of 75%. Closes
3750 o Minor features (geoip):
3751 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
3752 Country database. Closes ticket 25718.
3754 o Minor bugfixes (client):
3755 - When using a listed relay as a bridge, and also using
3756 microdescriptors, and considering that relay as a non-bridge in a
3757 circuit, treat its microdescriptor as a valid source of
3758 information about that relay. This change should prevent a non-
3759 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
3761 o Minor bugfixes (controller):
3762 - Restore the correct operation of the RESOLVE command, which had
3763 been broken since we added the ability to enable/disable DNS on
3764 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
3766 o Minor bugfixes (distribution, compilation, rust):
3767 - Build correctly when the rust dependencies submodule is loaded,
3768 but the TOR_RUST_DEPENDENCIES environment variable is not set.
3769 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
3770 - Actually include all of our Rust source in our source
3771 distributions. (Previously, a few of the files were accidentally
3772 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
3774 o Minor bugfixes (documentation):
3775 - Document that the PerConnBW{Rate,Burst} options will fall back to
3776 their corresponding consensus parameters only if those parameters
3777 are set. Previously we had claimed that these values would always
3778 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3779 - Revert a misformatting issue in the ExitPolicy documentation.
3780 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
3782 o Minor bugfixes (exit relay DNS retries):
3783 - Re-attempt timed-out DNS queries 3 times before failure, since our
3784 timeout is 5 seconds for them, but clients wait 10-15. Also allow
3785 slightly more timeouts per resolver when an exit has multiple
3786 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
3788 o Minor bugfixes (onion services):
3789 - Re-instate counting the client HSDir fetch circuits against the
3790 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
3792 - Remove underscores from the _HSLayer{2,3}Nodes options. This
3793 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
3794 Fixes bug 25581; bugfix on 0.3.3.1-alpha
3796 o Code simplification and refactoring:
3797 - Move the list of default directory authorities to its own file.
3798 Closes ticket 24854. Patch by "beastr0".
3800 o Documentation (manpage, denial of service):
3801 - Provide more detail about the denial-of-service options, by
3802 listing each mitigation and explaining how they relate. Closes
3806 Changes in version 0.3.3.4-alpha - 2018-03-29
3807 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
3808 the alpha testing of earlier releases in its series. We are
3809 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
3811 o New system requirements:
3812 - When built with Rust, Tor now depends on version 0.2.39 of the
3813 libc crate. Closes tickets 25310 and 25664.
3815 o Major bugfixes (relay, connection):
3816 - If we have failed to connect to a relay and received a connection
3817 refused, timeout, or similar error (at the TCP level), do not try
3818 that same address/port again for 60 seconds after the failure has
3819 occurred. Fixes bug 24767; bugfix on 0.0.6.
3821 o Minor features (geoip):
3822 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
3823 Country database. Closes ticket 25469.
3825 o Minor features (log messages):
3826 - Improve log message in the out-of-memory handler to include
3827 information about memory usage from the different compression
3828 backends. Closes ticket 25372.
3830 o Minor features (sandbox):
3831 - Explicitly permit the poll() system call when the Linux
3832 seccomp2-based sandbox is enabled: apparently, some versions of
3833 libc use poll() when calling getpwnam(). Closes ticket 25313.
3835 o Minor bugfixes (C correctness):
3836 - Fix a very unlikely (impossible, we believe) null pointer
3837 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3838 Coverity; this is CID 1430932.
3840 o Minor bugfixes (channel, client):
3841 - Better identify client connection when reporting to the geoip
3842 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
3844 o Minor bugfixes (compilation):
3845 - Fix a C99 compliance issue in our configuration script that caused
3846 compilation issues when compiling Tor with certain versions of
3847 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3849 o Minor bugfixes (controller, reliability):
3850 - Avoid a (nonfatal) assertion failure when extending a one-hop
3851 circuit from the controller to become a multihop circuit. Fixes
3852 bug 24903; bugfix on 0.2.5.2-alpha.
3854 o Major bugfixes (networking):
3855 - Tor will no longer reject IPv6 address strings from Tor Browser
3856 when they are passed as hostnames in SOCKS5 requests. Fixes bug
3857 25036, bugfix on Tor 0.3.1.2.
3859 o Minor bugfixes (networking):
3860 - string_is_valid_hostname() will not consider IP strings to be
3861 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
3863 o Minor bugfixes (onion service v3):
3864 - Avoid an assertion failure when the next onion service
3865 descriptor rotation type is out of sync with the consensus's
3866 valid-after time. Instead, log a warning message with extra
3867 information, so we can better hunt down the cause of this
3868 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
3870 o Minor bugfixes (testing):
3871 - Avoid intermittent test failures due to a test that had relied on
3872 onion service introduction point creation finishing within 5
3873 seconds of real clock time. Fixes bug 25450; bugfix
3875 - Rust crates are now automatically detected and tested. Previously,
3876 some crates were not tested by `make test-rust` due to a static
3877 string in the `src/test/test_rust.sh` script specifying which
3878 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
3880 o Minor bugfixes (testing, benchmarks):
3881 - Fix a crash when running benchmark tests on win32 systems. The
3882 crash was due to a mutex that wasn't initialized before logging
3883 and options were initialized. Fixes bug 25479; bugfix
3886 o Minor bugfixes (warnings, ipv6):
3887 - Avoid a bug warning that could occur when trying to connect to a
3888 relay over IPv6. This warning would occur on a Tor instance that
3889 downloads router descriptors, but prefers to use microdescriptors.
3890 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
3892 o Code simplification and refactoring:
3893 - Remove the old (deterministic) directory retry logic entirely:
3894 We've used exponential backoff exclusively for some time. Closes
3898 - Improved the documentation of AccountingStart parameter. Closes
3900 - Update the documentation for "Log" to include the current list of
3901 logging domains. Closes ticket 25378.
3904 Changes in version 0.3.1.10 - 2018-03-03
3905 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
3908 It includes an important security fix for a remote crash attack
3909 against directory authorities, tracked as TROVE-2018-001.
3911 This release also backports our new system for improved resistance to
3912 denial-of-service attacks against relays.
3914 This release also fixes several minor bugs and annoyances from
3917 All directory authorities should upgrade to one of the versions
3918 released today. Relays running 0.3.1.x may wish to update to one of
3919 the versions released today, for the DoS mitigations.
3921 Please note: according to our release calendar, Tor 0.3.1 will no
3922 longer be supported after 1 July 2018. If you will be running Tor
3923 after that date, you should make sure to plan to upgrade to the latest
3924 stable version, or downgrade to 0.2.9 (which will receive long-term
3927 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
3928 - Fix a protocol-list handling bug that could be used to remotely crash
3929 directory authorities with a null-pointer exception. Fixes bug 25074;
3930 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
3933 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
3934 - Give relays some defenses against the recent network overload. We
3935 start with three defenses (default parameters in parentheses).
3936 First: if a single client address makes too many concurrent
3937 connections (>100), hang up on further connections. Second: if a
3938 single client address makes circuits too quickly (more than 3 per
3939 second, with an allowed burst of 90) while also having too many
3940 connections open (3), refuse new create cells for the next while
3941 (1-2 hours). Third: if a client asks to establish a rendezvous
3942 point to you directly, ignore the request. These defenses can be
3943 manually controlled by new torrc options, but relays will also
3944 take guidance from consensus parameters, so there's no need to
3945 configure anything manually. Implements ticket 24902.
3947 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
3948 - Update the sandbox rules so that they should now work correctly
3949 with Glibc 2.26. Closes ticket 24315.
3951 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
3952 - Fix an "off by 2" error in counting rendezvous failures on the
3953 onion service side. While we thought we would stop the rendezvous
3954 attempt after one failed circuit, we were actually making three
3955 circuit attempts before giving up. Now switch to a default of 2,
3956 and allow the consensus parameter "hs_service_max_rdv_failures" to
3957 override. Fixes bug 24895; bugfix on 0.0.6.
3959 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
3960 - Add Link protocol version 5 to the supported protocols list. Fixes
3961 bug 25070; bugfix on 0.3.1.1-alpha.
3963 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
3964 - Fix a set of false positives where relays would consider
3965 connections to other relays as being client-only connections (and
3966 thus e.g. deserving different link padding schemes) if those
3967 relays fell out of the consensus briefly. Now we look only at the
3968 initial handshake and whether the connection authenticated as a
3969 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
3971 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
3972 - Make our OOM handler aware of the geoip client history cache so it
3973 doesn't fill up the memory. This check is important for IPv6 and
3974 our DoS mitigation subsystem. Closes ticket 25122.
3976 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
3977 - Change relay bandwidth reporting stats interval from 4 hours to 24
3978 hours in order to reduce the efficiency of guard discovery
3979 attacks. Fixes ticket 23856.
3981 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
3982 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
3983 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
3984 since they neither disabled TLS 1.3 nor enabled any of the
3985 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
3986 Closes ticket 24978.
3988 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
3989 - The fallback directory list has been re-generated based on the
3990 current status of the network. Tor uses fallback directories to
3991 bootstrap when it doesn't yet have up-to-date directory
3992 information. Closes ticket 24801.
3993 - Make the default DirAuthorityFallbackRate 0.1, so that clients
3994 prefer to bootstrap from fallback directory mirrors. This is a
3995 follow-up to 24679, which removed weights from the default
3996 fallbacks. Implements ticket 24681.
3998 o Minor features (geoip):
3999 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4002 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4003 - Use the actual observed address of an incoming relay connection,
4004 not the canonical address of the relay from its descriptor, when
4005 making decisions about how to handle the incoming connection.
4006 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4008 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4009 - Directory authorities, when refusing a descriptor from a rejected
4010 relay, now explicitly tell the relay (in its logs) to set a valid
4011 ContactInfo address and contact the bad-relays@ mailing list.
4012 Fixes bug 25170; bugfix on 0.2.9.1.
4014 o Minor bugfixes (address selection, backport from 0.3.2.9):
4015 - When the fascist_firewall_choose_address_ functions don't find a
4016 reachable address, set the returned address to the null address
4017 and port. This is a precautionary measure, because some callers do
4018 not check the return value. Fixes bug 24736; bugfix
4021 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
4022 - Fetch descriptors aggressively whenever we lack enough to build
4023 circuits, regardless of how many descriptors we are missing.
4024 Previously, we would delay launching the fetch when we had fewer
4025 than 15 missing descriptors, even if some of those descriptors
4026 were blocking circuits from building. Fixes bug 23985; bugfix on
4027 0.1.1.11-alpha. The effects of this bug became worse in
4028 0.3.0.3-alpha, when we began treating missing descriptors from our
4029 primary guards as a reason to delay circuits.
4030 - Don't try fetching microdescriptors from relays that have failed
4031 to deliver them in the past. Fixes bug 23817; bugfix
4034 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
4035 - Fix a signed/unsigned comparison warning introduced by our fix to
4036 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4038 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4039 - Avoid a crash when attempting to use the seccomp2 sandbox together
4040 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4043 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4044 - Fix a possible crash on malformed consensus. If a consensus had
4045 contained an unparseable protocol line, it could have made clients
4046 and relays crash with a null-pointer exception. To exploit this
4047 issue, however, an attacker would need to be able to subvert the
4048 directory authority system. Fixes bug 25251; bugfix on
4049 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4051 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
4052 - Recover better from empty or corrupt files in the consensus cache
4053 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4054 - When a consensus diff calculation is only partially successful,
4055 only record the successful parts as having succeeded. Partial
4056 success can happen if (for example) one compression method fails
4057 but the others succeed. Previously we misrecorded all the
4058 calculations as having succeeded, which would later cause a
4059 nonfatal assertion failure. Fixes bug 24086; bugfix
4062 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
4063 - Tor now updates its guard state when it reads a consensus
4064 regardless of whether it's missing descriptors. That makes tor use
4065 its primary guards to fetch descriptors in some edge cases where
4066 it would previously have used fallback directories. Fixes bug
4067 23862; bugfix on 0.3.0.1-alpha.
4069 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4070 - Don't treat inability to store a cached consensus object as a bug:
4071 it can happen normally when we are out of disk space. Fixes bug
4072 24859; bugfix on 0.3.1.1-alpha.
4074 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
4075 - When queuing DESTROY cells on a channel, only queue the circuit-id
4076 and reason fields: not the entire 514-byte cell. This fix should
4077 help mitigate any bugs or attacks that fill up these queues, and
4078 free more RAM for other uses. Fixes bug 24666; bugfix
4081 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
4082 - When closing a connection via close_connection_immediately(), we
4083 mark it as "not blocked on bandwidth", to prevent later calls from
4084 trying to unblock it, and give it permission to read. This fixes a
4085 backtrace warning that can happen on relays under various
4086 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4088 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
4089 - When selecting relays by bandwidth, avoid a rounding error that
4090 could sometimes cause load to be imbalanced incorrectly.
4091 Previously, we would always round upwards; now, we round towards
4092 the nearest integer. This had the biggest effect when a relay's
4093 weight adjustments should have given it weight 0, but it got
4094 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4095 - When calculating the fraction of nodes that have descriptors, and
4096 all nodes in the network have zero bandwidths, count the number of
4097 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4098 - Actually log the total bandwidth in compute_weighted_bandwidths().
4099 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4101 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4102 - Improve the performance of our consensus-diff application code
4103 when Tor is built with the --enable-fragile-hardening option set.
4104 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4106 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4107 - Don't exit the Tor process if setrlimit() fails to change the file
4108 limit (which can happen sometimes on some versions of OSX). Fixes
4109 bug 21074; bugfix on 0.0.9pre5.
4111 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
4112 - Fix a bug in the bit-counting parts of our timing-wheel code on
4113 MSVC. (Note that MSVC is still not a supported build platform, due
4114 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
4117 o Minor bugfixes (relay, partial backport):
4118 - Make the internal channel_is_client() function look at what sort
4119 of connection handshake the other side used, rather than whether
4120 the other side ever sent a create_fast cell to us. Backports part
4121 of the fixes from bugs 22805 and 24898.
4123 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4124 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4126 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4127 bugfix on 0.2.9.4-alpha.
4129 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4130 - Update the "rust dependencies" submodule to be a project-level
4131 repository, rather than a user repository. Closes ticket 25323.
4134 Changes in version 0.2.9.15 - 2018-03-03
4135 Tor 0.2.9.15 backports important security and stability bugfixes from
4138 It includes an important security fix for a remote crash attack
4139 against directory authorities, tracked as TROVE-2018-001.
4141 This release also backports our new system for improved resistance to
4142 denial-of-service attacks against relays.
4144 This release also fixes several minor bugs and annoyances from
4147 All directory authorities should upgrade to one of the versions
4148 released today. Relays running 0.2.9.x may wish to update to one of
4149 the versions released today, for the DoS mitigations.
4151 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4152 - Fix a protocol-list handling bug that could be used to remotely crash
4153 directory authorities with a null-pointer exception. Fixes bug 25074;
4154 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4157 o Major features (denial-of-service mitigation):
4158 - Give relays some defenses against the recent network overload. We
4159 start with three defenses (default parameters in parentheses).
4160 First: if a single client address makes too many concurrent
4161 connections (>100), hang up on further connections. Second: if a
4162 single client address makes circuits too quickly (more than 3 per
4163 second, with an allowed burst of 90) while also having too many
4164 connections open (3), refuse new create cells for the next while
4165 (1-2 hours). Third: if a client asks to establish a rendezvous
4166 point to you directly, ignore the request. These defenses can be
4167 manually controlled by new torrc options, but relays will also
4168 take guidance from consensus parameters, so there's no need to
4169 configure anything manually. Implements ticket 24902.
4171 o Major bugfixes (bootstrapping):
4172 - Fetch descriptors aggressively whenever we lack enough to build
4173 circuits, regardless of how many descriptors we are missing.
4174 Previously, we would delay launching the fetch when we had fewer
4175 than 15 missing descriptors, even if some of those descriptors
4176 were blocking circuits from building. Fixes bug 23985; bugfix on
4177 0.1.1.11-alpha. The effects of this bug became worse in
4178 0.3.0.3-alpha, when we began treating missing descriptors from our
4179 primary guards as a reason to delay circuits.
4181 o Major bugfixes (onion services, retry behavior):
4182 - Fix an "off by 2" error in counting rendezvous failures on the
4183 onion service side. While we thought we would stop the rendezvous
4184 attempt after one failed circuit, we were actually making three
4185 circuit attempts before giving up. Now switch to a default of 2,
4186 and allow the consensus parameter "hs_service_max_rdv_failures" to
4187 override. Fixes bug 24895; bugfix on 0.0.6.
4189 o Minor feature (relay statistics):
4190 - Change relay bandwidth reporting stats interval from 4 hours to 24
4191 hours in order to reduce the efficiency of guard discovery
4192 attacks. Fixes ticket 23856.
4194 o Minor features (compatibility, OpenSSL):
4195 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4196 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4197 since they neither disabled TLS 1.3 nor enabled any of the
4198 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4199 Closes ticket 24978.
4201 o Minor features (denial-of-service avoidance):
4202 - Make our OOM handler aware of the geoip client history cache so it
4203 doesn't fill up the memory. This check is important for IPv6 and
4204 our DoS mitigation subsystem. Closes ticket 25122.
4206 o Minor features (fallback directory mirrors):
4207 - The fallback directory list has been re-generated based on the
4208 current status of the network. Tor uses fallback directories to
4209 bootstrap when it doesn't yet have up-to-date directory
4210 information. Closes ticket 24801.
4211 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4212 prefer to bootstrap from fallback directory mirrors. This is a
4213 follow-up to 24679, which removed weights from the default
4214 fallbacks. Implements ticket 24681.
4216 o Minor features (geoip):
4217 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4220 o Minor features (linux seccomp2 sandbox):
4221 - Update the sandbox rules so that they should now work correctly
4222 with Glibc 2.26. Closes ticket 24315.
4224 o Minor bugfix (channel connection):
4225 - Use the actual observed address of an incoming relay connection,
4226 not the canonical address of the relay from its descriptor, when
4227 making decisions about how to handle the incoming connection.
4228 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4230 o Minor bugfix (directory authority):
4231 - Directory authorities, when refusing a descriptor from a rejected
4232 relay, now explicitly tell the relay (in its logs) to set a valid
4233 ContactInfo address and contact the bad-relays@ mailing list.
4234 Fixes bug 25170; bugfix on 0.2.9.1.
4236 o Minor bugfixes (address selection):
4237 - When the fascist_firewall_choose_address_ functions don't find a
4238 reachable address, set the returned address to the null address
4239 and port. This is a precautionary measure, because some callers do
4240 not check the return value. Fixes bug 24736; bugfix
4243 o Minor bugfixes (compilation):
4244 - Fix a signed/unsigned comparison warning introduced by our fix to
4245 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4247 o Minor bugfixes (control port, linux seccomp2 sandbox):
4248 - Avoid a crash when attempting to use the seccomp2 sandbox together
4249 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4252 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4253 - Fix a possible crash on malformed consensus. If a consensus had
4254 contained an unparseable protocol line, it could have made clients
4255 and relays crash with a null-pointer exception. To exploit this
4256 issue, however, an attacker would need to be able to subvert the
4257 directory authority system. Fixes bug 25251; bugfix on
4258 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4260 o Minor bugfixes (memory usage):
4261 - When queuing DESTROY cells on a channel, only queue the circuit-id
4262 and reason fields: not the entire 514-byte cell. This fix should
4263 help mitigate any bugs or attacks that fill up these queues, and
4264 free more RAM for other uses. Fixes bug 24666; bugfix
4267 o Minor bugfixes (network layer):
4268 - When closing a connection via close_connection_immediately(), we
4269 mark it as "not blocked on bandwidth", to prevent later calls from
4270 trying to unblock it, and give it permission to read. This fixes a
4271 backtrace warning that can happen on relays under various
4272 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4274 o Minor bugfixes (OSX):
4275 - Don't exit the Tor process if setrlimit() fails to change the file
4276 limit (which can happen sometimes on some versions of OSX). Fixes
4277 bug 21074; bugfix on 0.0.9pre5.
4279 o Minor bugfixes (path selection):
4280 - When selecting relays by bandwidth, avoid a rounding error that
4281 could sometimes cause load to be imbalanced incorrectly.
4282 Previously, we would always round upwards; now, we round towards
4283 the nearest integer. This had the biggest effect when a relay's
4284 weight adjustments should have given it weight 0, but it got
4285 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4286 - When calculating the fraction of nodes that have descriptors, and
4287 all nodes in the network have zero bandwidths, count the number of
4288 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4289 - Actually log the total bandwidth in compute_weighted_bandwidths().
4290 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4292 o Minor bugfixes (portability, msvc):
4293 - Fix a bug in the bit-counting parts of our timing-wheel code on
4294 MSVC. (Note that MSVC is still not a supported build platform, due
4295 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
4298 o Minor bugfixes (relay):
4299 - Make the internal channel_is_client() function look at what sort
4300 of connection handshake the other side used, rather than whether
4301 the other side ever sent a create_fast cell to us. Backports part
4302 of the fixes from bugs 22805 and 24898.
4304 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4305 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4307 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4308 bugfix on 0.2.9.4-alpha.
4311 Changes in version 0.3.2.10 - 2018-03-03
4312 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
4313 backports a number of bugfixes, including important fixes for security
4316 It includes an important security fix for a remote crash attack
4317 against directory authorities, tracked as TROVE-2018-001.
4319 Additionally, it backports a fix for a bug whose severity we have
4320 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
4321 triggered in order to crash relays with a use-after-free pattern. As
4322 such, we are now tracking that bug as TROVE-2018-002 and
4323 CVE-2018-0491, and backporting it to earlier releases. This bug
4324 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
4327 This release also backports our new system for improved resistance to
4328 denial-of-service attacks against relays.
4330 This release also fixes several minor bugs and annoyances from
4333 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
4334 today, for the fix to TROVE-2018-002. Directory authorities should
4335 also upgrade. (Relays on earlier versions might want to update too for
4336 the DoS mitigations.)
4338 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4339 - Fix a protocol-list handling bug that could be used to remotely crash
4340 directory authorities with a null-pointer exception. Fixes bug 25074;
4341 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4344 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
4345 - Avoid adding the same channel twice in the KIST scheduler pending
4346 list, which could lead to remote denial-of-service use-after-free
4347 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
4349 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4350 - Give relays some defenses against the recent network overload. We
4351 start with three defenses (default parameters in parentheses).
4352 First: if a single client address makes too many concurrent
4353 connections (>100), hang up on further connections. Second: if a
4354 single client address makes circuits too quickly (more than 3 per
4355 second, with an allowed burst of 90) while also having too many
4356 connections open (3), refuse new create cells for the next while
4357 (1-2 hours). Third: if a client asks to establish a rendezvous
4358 point to you directly, ignore the request. These defenses can be
4359 manually controlled by new torrc options, but relays will also
4360 take guidance from consensus parameters, so there's no need to
4361 configure anything manually. Implements ticket 24902.
4363 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4364 - Fix an "off by 2" error in counting rendezvous failures on the
4365 onion service side. While we thought we would stop the rendezvous
4366 attempt after one failed circuit, we were actually making three
4367 circuit attempts before giving up. Now switch to a default of 2,
4368 and allow the consensus parameter "hs_service_max_rdv_failures" to
4369 override. Fixes bug 24895; bugfix on 0.0.6.
4370 - New-style (v3) onion services now obey the "max rendezvous circuit
4371 attempts" logic. Previously they would make as many rendezvous
4372 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
4373 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
4375 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4376 - Add Link protocol version 5 to the supported protocols list. Fixes
4377 bug 25070; bugfix on 0.3.1.1-alpha.
4379 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4380 - Fix a set of false positives where relays would consider
4381 connections to other relays as being client-only connections (and
4382 thus e.g. deserving different link padding schemes) if those
4383 relays fell out of the consensus briefly. Now we look only at the
4384 initial handshake and whether the connection authenticated as a
4385 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4387 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
4388 - The scheduler subsystem was failing to promptly notice changes in
4389 consensus parameters, making it harder to switch schedulers
4390 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
4392 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
4393 - Make our OOM handler aware of the geoip client history cache so it
4394 doesn't fill up the memory. This check is important for IPv6 and
4395 our DoS mitigation subsystem. Closes ticket 25122.
4397 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4398 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4399 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4400 since they neither disabled TLS 1.3 nor enabled any of the
4401 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4402 Closes ticket 24978.
4404 o Minor features (geoip):
4405 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4408 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
4409 - When logging a failure to create an onion service's descriptor,
4410 also log what the problem with the descriptor was. Diagnostic
4413 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4414 - Use the actual observed address of an incoming relay connection,
4415 not the canonical address of the relay from its descriptor, when
4416 making decisions about how to handle the incoming connection.
4417 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4419 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4420 - Fix a possible crash on malformed consensus. If a consensus had
4421 contained an unparseable protocol line, it could have made clients
4422 and relays crash with a null-pointer exception. To exploit this
4423 issue, however, an attacker would need to be able to subvert the
4424 directory authority system. Fixes bug 25251; bugfix on
4425 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4427 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4428 - Directory authorities, when refusing a descriptor from a rejected
4429 relay, now explicitly tell the relay (in its logs) to set a valid
4430 ContactInfo address and contact the bad-relays@ mailing list.
4431 Fixes bug 25170; bugfix on 0.2.9.1.
4433 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
4434 - When building with Rust on OSX, link against libresolv, to work
4435 around the issue at https://github.com/rust-lang/rust/issues/46797.
4436 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
4438 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
4439 - Remove a BUG() statement when a client fetches an onion descriptor
4440 that has a lower revision counter than the one in its cache. This
4441 can happen in normal circumstances due to HSDir desync. Fixes bug
4442 24976; bugfix on 0.3.2.1-alpha.
4444 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4445 - Don't treat inability to store a cached consensus object as a bug:
4446 it can happen normally when we are out of disk space. Fixes bug
4447 24859; bugfix on 0.3.1.1-alpha.
4449 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4450 - Improve the performance of our consensus-diff application code
4451 when Tor is built with the --enable-fragile-hardening option set.
4452 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4454 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4455 - Don't exit the Tor process if setrlimit() fails to change the file
4456 limit (which can happen sometimes on some versions of OSX). Fixes
4457 bug 21074; bugfix on 0.0.9pre5.
4459 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4460 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4462 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4463 bugfix on 0.2.9.4-alpha.
4465 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
4466 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
4467 25005; bugfix on 0.3.2.7-rc.
4469 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
4470 - Look at the "HSRend" protocol version, not the "HSDir" protocol
4471 version, when deciding whether a consensus entry can support the
4472 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
4473 bugfix on 0.3.2.1-alpha.
4475 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4476 - Update the "rust dependencies" submodule to be a project-level
4477 repository, rather than a user repository. Closes ticket 25323.
4479 o Documentation (backport from 0.3.3.1-alpha)
4480 - Document that operators who run more than one relay or bridge are
4481 expected to set MyFamily and ContactInfo correctly. Closes
4485 Changes in version 0.3.3.3-alpha - 2018-03-03
4486 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
4487 It includes an important security fix for a remote crash attack
4488 against directory authorities tracked as TROVE-2018-001.
4490 Additionally, with this release, we are upgrading the severity of a
4491 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
4492 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
4493 a use-after-free pattern. As such, we are now tracking that bug as
4494 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
4495 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
4497 This release also fixes several minor bugs and annoyances from
4500 Relays running 0.3.2.x should upgrade to one of the versions released
4501 today, for the fix to TROVE-2018-002. Directory authorities should
4502 also upgrade. (Relays on earlier versions might want to update too for
4503 the DoS mitigations.)
4505 o Major bugfixes (denial-of-service, directory authority):
4506 - Fix a protocol-list handling bug that could be used to remotely crash
4507 directory authorities with a null-pointer exception. Fixes bug 25074;
4508 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4511 o Minor features (compatibility, OpenSSL):
4512 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4513 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4514 since they neither disabled TLS 1.3 nor enabled any of the
4515 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4516 Closes ticket 24978.
4518 o Minor features (logging):
4519 - Clarify the log messages produced when getrandom() or a related
4520 entropy-generation mechanism gives an error. Closes ticket 25120.
4522 o Minor features (testing):
4523 - Add a "make test-rust" target to run the rust tests only. Closes
4526 o Minor bugfixes (denial-of-service):
4527 - Fix a possible crash on malformed consensus. If a consensus had
4528 contained an unparseable protocol line, it could have made clients
4529 and relays crash with a null-pointer exception. To exploit this
4530 issue, however, an attacker would need to be able to subvert the
4531 directory authority system. Fixes bug 25251; bugfix on
4532 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4534 o Minor bugfixes (DoS mitigation):
4535 - Add extra safety checks when refilling the circuit creation bucket
4536 to ensure we never set a value above the allowed maximum burst.
4537 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
4538 - When a new consensus arrives, don't update our DoS-mitigation
4539 parameters if we aren't a public relay. Fixes bug 25223; bugfix
4542 o Minor bugfixes (man page, SocksPort):
4543 - Remove dead code from the old "SocksSocket" option, and rename
4544 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
4545 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
4547 o Minor bugfixes (performance):
4548 - Reduce the number of circuits that will be opened at once during
4549 the circuit build timeout phase. This is done by increasing the
4550 idle timeout to 3 minutes, and lowering the maximum number of
4551 concurrent learning circuits to 10. Fixes bug 24769; bugfix
4554 o Minor bugfixes (spec conformance):
4555 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4557 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4558 bugfix on 0.2.9.4-alpha.
4560 o Minor bugfixes (spec conformance, rust):
4561 - Resolve a denial-of-service issue caused by an infinite loop in
4562 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
4563 Also tracked as TROVE-2018-003.
4565 o Code simplification and refactoring:
4566 - Update the "rust dependencies" submodule to be a project-level
4567 repository, rather than a user repository. Closes ticket 25323.
4570 Changes in version 0.3.3.2-alpha - 2018-02-10
4571 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
4572 introduces a mechanism to handle the high loads that many relay
4573 operators have been reporting recently. It also fixes several bugs in
4574 older releases. If this new code proves reliable, we plan to backport
4575 it to older supported release series.
4577 o Major features (denial-of-service mitigation):
4578 - Give relays some defenses against the recent network overload. We
4579 start with three defenses (default parameters in parentheses).
4580 First: if a single client address makes too many concurrent
4581 connections (>100), hang up on further connections. Second: if a
4582 single client address makes circuits too quickly (more than 3 per
4583 second, with an allowed burst of 90) while also having too many
4584 connections open (3), refuse new create cells for the next while
4585 (1-2 hours). Third: if a client asks to establish a rendezvous
4586 point to you directly, ignore the request. These defenses can be
4587 manually controlled by new torrc options, but relays will also
4588 take guidance from consensus parameters, so there's no need to
4589 configure anything manually. Implements ticket 24902.
4591 o Major bugfixes (netflow padding):
4592 - Stop adding unneeded channel padding right after we finish
4593 flushing to a connection that has been trying to flush for many
4594 seconds. Instead, treat all partial or complete flushes as
4595 activity on the channel, which will defer the time until we need
4596 to add padding. This fix should resolve confusing and scary log
4597 messages like "Channel padding timeout scheduled 221453ms in the
4598 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
4600 o Major bugfixes (protocol versions):
4601 - Add Link protocol version 5 to the supported protocols list. Fixes
4602 bug 25070; bugfix on 0.3.1.1-alpha.
4604 o Major bugfixes (scheduler, consensus):
4605 - The scheduler subsystem was failing to promptly notice changes in
4606 consensus parameters, making it harder to switch schedulers
4607 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
4609 o Minor features (denial-of-service avoidance):
4610 - Make our OOM handler aware of the geoip client history cache so it
4611 doesn't fill up the memory. This check is important for IPv6 and
4612 our DoS mitigation subsystem. Closes ticket 25122.
4614 o Minor features (directory authority):
4615 - When directory authorities are unable to add signatures to a
4616 pending consensus, log the reason why. Closes ticket 24849.
4618 o Minor features (geoip):
4619 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4622 o Minor features (logging, diagnostic):
4623 - When logging a failure to create an onion service's descriptor,
4624 also log what the problem with the descriptor was. Diagnostic for
4627 o Minor bugfix (channel connection):
4628 - Use the actual observed address of an incoming relay connection,
4629 not the canonical address of the relay from its descriptor, when
4630 making decisions about how to handle the incoming connection.
4631 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4633 o Minor bugfix (directory authority):
4634 - Directory authorities, when refusing a descriptor from a rejected
4635 relay, now explicitly tell the relay (in its logs) to set a valid
4636 ContactInfo address and contact the bad-relays@ mailing list.
4637 Fixes bug 25170; bugfix on 0.2.9.1.
4639 o Minor bugfixes (all versions of Tor):
4640 - Use the "misspell" tool to detect and fix typos throughout the
4641 source code. Fixes bug 23650; bugfix on various versions of Tor.
4642 Patch from Deepesh Pathak.
4644 o Minor bugfixes (circuit, cannibalization):
4645 - Don't cannibalize preemptively-built circuits if we no longer
4646 recognize their first hop. This situation can happen if our Guard
4647 relay went off the consensus after the circuit was created. Fixes
4648 bug 24469; bugfix on 0.0.6.
4650 o Minor bugfixes (correctness):
4651 - Remove a nonworking, unnecessary check to see whether a circuit
4652 hop's identity digest was set when the circuit failed. Fixes bug
4653 24927; bugfix on 0.2.4.4-alpha.
4655 o Minor bugfixes (logging):
4656 - Don't treat inability to store a cached consensus object as a bug:
4657 it can happen normally when we are out of disk space. Fixes bug
4658 24859; bugfix on 0.3.1.1-alpha.
4659 - Fix a (mostly harmless) race condition when invoking
4660 LOG_PROTOCOL_WARN message from a subthread while the torrc options
4661 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
4663 o Minor bugfixes (onion services):
4664 - Remove a BUG() statement when a client fetches an onion descriptor
4665 that has a lower revision counter than the one in its cache. This
4666 can happen in normal circumstances due to HSDir desync. Fixes bug
4667 24976; bugfix on 0.3.2.1-alpha.
4668 - If we are configured to offer a single onion service, don't log
4669 long-term established one hop rendezvous points in the heartbeat.
4670 Fixes bug 25116; bugfix on 0.2.9.6-rc.
4672 o Minor bugfixes (performance):
4673 - Avoid calling protocol_list_supports_protocol() from inside tight
4674 loops when running with cached routerinfo_t objects. Instead,
4675 summarize the relevant protocols as flags in the routerinfo_t, as
4676 we do for routerstatus_t objects. This change simplifies our code
4677 a little, and saves a large amount of short-term memory allocation
4678 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
4680 o Minor bugfixes (Rust FFI):
4681 - Fix a minor memory leak which would happen whenever the C code
4682 would call the Rust implementation of
4683 protover_get_supported_protocols(). This was due to the C version
4684 returning a static string, whereas the Rust version newly allocated
4685 a CString to pass across the FFI boundary. Consequently, the C
4686 code was not expecting to need to free() what it was given. Fixes
4687 bug 25127; bugfix on 0.3.2.1-alpha.
4689 o Minor bugfixes (scheduler, KIST):
4690 - Avoid adding the same channel twice in the KIST scheduler pending
4691 list, which would waste CPU cycles. Fixes bug 24700; bugfix
4694 o Minor bugfixes (unit test, monotonic time):
4695 - Increase a constant (1msec to 10msec) in the monotonic time test
4696 that makes sure the nsec/usec/msec times read are synchronized.
4697 This change was needed to accommodate slow systems like armel or
4698 when the clock_gettime() is not a VDSO on the running kernel.
4699 Fixes bug 25113; bugfix on 0.2.9.1.
4701 o Minor bugfixes (v3 onion services):
4702 - Look at the "HSRend" protocol version, not the "HSDir" protocol
4703 version, when deciding whether a consensus entry can support the
4704 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
4705 bugfix on 0.3.2.1-alpha.
4707 o Code simplification and refactoring:
4708 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
4710 - Remove a series of counters used to track circuit extend attempts
4711 and connection status but that in reality we aren't using for
4712 anything other than stats logged by a SIGUSR1 signal. Closes
4715 o Documentation (man page):
4716 - The HiddenServiceVersion torrc option accepts only one number:
4717 either version 2 or 3. Closes ticket 25026; bugfix
4721 Changes in version 0.3.3.1-alpha - 2018-01-25
4722 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
4723 several new features to Tor, including several improvements to
4724 bootstrapping, and support for an experimental "vanguards" feature to
4725 resist guard discovery attacks. This series also includes better
4726 support for applications that need to embed Tor or manage v3
4729 o Major features (embedding):
4730 - There is now a documented stable API for programs that need to
4731 embed Tor. See tor_api.h for full documentation and known bugs.
4732 Closes ticket 23684.
4733 - Tor now has support for restarting in the same process.
4734 Controllers that run Tor using the "tor_api.h" interface can now
4735 restart Tor after Tor has exited. This support is incomplete,
4736 however: we fixed crash bugs that prevented it from working at
4737 all, but many bugs probably remain, including a possibility of
4738 security issues. Implements ticket 24581.
4740 o Major features (IPv6, directory documents):
4741 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
4742 consensus. This information makes it easier for IPv6 clients to
4743 bootstrap and choose reachable entry guards. Implements ticket 23826.
4744 - Add consensus method 28, which removes IPv6 ORPorts from
4745 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
4746 are redundant in microdescs. This change will be used by Tor clients
4747 on 0.2.8.x and later. (That is to say, with all Tor clients that
4748 have IPv6 bootstrap and guard support.) Implements ticket 23828.
4749 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
4750 set by different numbers of authorities. Fixes 23870
4753 o Major features (onion service v3, control port):
4754 - The control port now supports commands and events for v3 onion
4755 services. It is now possible to create ephemeral v3 services using
4756 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
4757 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
4758 DEL_ONION) have been extended to support v3 onion services. Closes
4759 ticket 20699; implements proposal 284.
4761 o Major features (onion services):
4762 - Provide torrc options to pin the second and third hops of onion
4763 service circuits to a list of nodes. The option HSLayer2Guards
4764 pins the second hop, and the option HSLayer3Guards pins the third
4765 hop. These options are for use in conjunction with experiments
4766 with "vanguards" for preventing guard enumeration attacks. Closes
4769 o Major features (rust, portability, experimental):
4770 - Tor now ships with an optional implementation of one of its
4771 smaller modules (protover.c) in the Rust programming language. To
4772 try it out, install a Rust build environment, and configure Tor
4773 with "--enable-rust --enable-cargo-online-mode". This should not
4774 cause any user-visible changes, but should help us gain more
4775 experience with Rust, and plan future Rust integration work.
4776 Implementation by Chelsea Komlo. Closes ticket 22840.
4778 o Minor features (storage, configuration):
4779 - Users can store cached directory documents somewhere other than
4780 the DataDirectory by using the CacheDirectory option. Similarly,
4781 the storage location for relay's keys can be overridden with the
4782 KeyDirectory option. Closes ticket 22703.
4784 o Major features (v3 onion services, ipv6):
4785 - When v3 onion service clients send introduce cells, they now
4786 include the IPv6 address of the rendezvous point, if it has one.
4787 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
4788 in future Tor versions, IPv6-only v3 single onion services will be
4789 able to use IPv6 addresses to connect directly to the rendezvous
4790 point. Closes ticket 23577. Patch by Neel Chauhan.
4792 o Major bugfixes (onion services, retry behavior):
4793 - Fix an "off by 2" error in counting rendezvous failures on the
4794 onion service side. While we thought we would stop the rendezvous
4795 attempt after one failed circuit, we were actually making three
4796 circuit attempts before giving up. Now switch to a default of 2,
4797 and allow the consensus parameter "hs_service_max_rdv_failures" to
4798 override. Fixes bug 24895; bugfix on 0.0.6.
4799 - New-style (v3) onion services now obey the "max rendezvous circuit
4800 attempts" logic. Previously they would make as many rendezvous
4801 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
4802 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
4804 o Major bugfixes (relays):
4805 - Fix a set of false positives where relays would consider
4806 connections to other relays as being client-only connections (and
4807 thus e.g. deserving different link padding schemes) if those
4808 relays fell out of the consensus briefly. Now we look only at the
4809 initial handshake and whether the connection authenticated as a
4810 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4812 o Minor feature (IPv6):
4813 - Make IPv6-only clients wait for microdescs for relays, even if we
4814 were previously using descriptors (or were using them as a bridge)
4815 and have a cached descriptor for them. Implements ticket 23827.
4816 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
4817 them, rather than waiting to download microdescriptors.
4818 Implements ticket 23827.
4820 o Minor features (cleanup):
4821 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
4822 when it stops. Closes ticket 23271.
4824 o Minor features (defensive programming):
4825 - Most of the functions in Tor that free objects have been replaced
4826 with macros that free the objects and set the corresponding
4827 pointers to NULL. This change should help prevent a large class of
4828 dangling pointer bugs. Closes ticket 24337.
4829 - Where possible, the tor_free() macro now only evaluates its input
4830 once. Part of ticket 24337.
4831 - Check that microdesc ed25519 ids are non-zero in
4832 node_get_ed25519_id() before returning them. Implements ticket
4833 24001, patch by "aruna1234".
4835 o Minor features (embedding):
4836 - Tor can now start with a preauthenticated control connection
4837 created by the process that launched it. This feature is meant for
4838 use by programs that want to launch and manage a Tor process
4839 without allowing other programs to manage it as well. For more
4840 information, see the __OwningControllerFD option documented in
4841 control-spec.txt. Closes ticket 23900.
4842 - On most errors that would cause Tor to exit, it now tries to
4843 return from the tor_main() function, rather than calling the
4844 system exit() function. Most users won't notice a difference here,
4845 but it should be significant for programs that run Tor inside
4846 a separate thread: they should now be able to survive Tor's exit
4847 conditions rather than having Tor shut down the entire process.
4848 Closes ticket 23848.
4849 - Applications that want to embed Tor can now tell Tor not to
4850 register any of its own POSIX signal handlers, using the
4851 __DisableSignalHandlers option. Closes ticket 24588.
4853 o Minor features (fallback directory list):
4854 - Avoid selecting fallbacks that change their IP addresses too
4855 often. Select more fallbacks by ignoring the Guard flag, and
4856 allowing lower cutoffs for the Running and V2Dir flags. Also allow
4857 a lower bandwidth, and a higher number of fallbacks per operator
4858 (5% of the list). Implements ticket 24785.
4859 - Update the fallback whitelist and blacklist based on opt-ins and
4860 relay changes. Closes tickets 22321, 24678, 22527, 24135,
4863 o Minor features (fallback directory mirror configuration):
4864 - Add a nickname to each fallback in a C comment. This makes it
4865 easier for operators to find their relays, and allows stem to use
4866 nicknames to identify fallbacks. Implements ticket 24600.
4867 - Add a type and version header to the fallback directory mirror
4868 file. Also add a delimiter to the end of each fallback entry. This
4869 helps external parsers like stem and Relay Search. Implements
4871 - Add an extrainfo cache flag for each fallback in a C comment. This
4872 allows stem to use fallbacks to fetch extra-info documents, rather
4873 than using authorities. Implements ticket 22759.
4874 - Add the generateFallbackDirLine.py script for automatically
4875 generating fallback directory mirror lines from relay fingerprints.
4876 No more typos! Add the lookupFallbackDirContact.py script for
4877 automatically looking up operator contact info from relay
4878 fingerprints. Implements ticket 24706, patch by teor and atagar.
4879 - Reject any fallback directory mirror that serves an expired
4880 consensus. Implements ticket 20942, patch by "minik".
4881 - Remove commas and equals signs from external string inputs to the
4882 fallback list. This avoids format confusion attacks. Implements
4884 - Remove the "weight=10" line from fallback directory mirror
4885 entries. Ticket 24681 will maintain the current fallback weights
4886 by changing Tor's default fallback weight to 10. Implements
4888 - Stop logging excessive information about fallback netblocks.
4889 Implements ticket 24791.
4891 o Minor features (forward-compatibility):
4892 - If a relay supports some link authentication protocol that we do
4893 not recognize, then include that relay's ed25519 key when telling
4894 other relays to extend to it. Previously, we treated future
4895 versions as if they were too old to support ed25519 link
4896 authentication. Closes ticket 20895.
4898 o Minor features (heartbeat):
4899 - Add onion service information to our heartbeat logs, displaying
4900 stats about the activity of configured onion services. Closes
4903 o Minor features (instrumentation, development):
4904 - Add the MainloopStats option to allow developers to get
4905 instrumentation information from the main event loop via the
4906 heartbeat messages. We hope to use this to improve Tor's behavior
4907 when it's trying to sleep. Closes ticket 24605.
4909 o Minor features (log messages):
4910 - Improve a warning message that happens when we fail to re-parse an
4911 old router because of an expired certificate. Closes ticket 20020.
4912 - Make the log more quantitative when we hit MaxMemInQueues
4913 threshold exposing some values. Closes ticket 24501.
4915 o Minor features (logging, android):
4916 - Added support for the Android logging subsystem. Closes
4919 o Minor features (performance):
4920 - Support predictive circuit building for onion service circuits
4921 with multiple layers of guards. Closes ticket 23101.
4922 - Use stdatomic.h where available, rather than mutexes, to implement
4923 atomic_counter_t. Closes ticket 23953.
4925 o Minor features (performance, 32-bit):
4926 - Improve performance on 32-bit systems by avoiding 64-bit division
4927 when calculating the timestamp in milliseconds for channel padding
4928 computations. Implements ticket 24613.
4929 - Improve performance on 32-bit systems by avoiding 64-bit division
4930 when timestamping cells and buffer chunks for OOM calculations.
4931 Implements ticket 24374.
4933 o Minor features (performance, OSX, iOS):
4934 - Use the mach_approximate_time() function (when available) to
4935 implement coarse monotonic time. Having a coarse time function
4936 should avoid a large number of system calls, and improve
4937 performance slightly, especially under load. Closes ticket 24427.
4939 o Minor features (performance, windows):
4940 - Improve performance on Windows Vista and Windows 7 by adjusting
4941 TCP send window size according to the recommendation from
4942 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
4945 o Major features (relay):
4946 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
4947 operator to use a more reasonable ("reduced") exit policy, rather
4948 than the default one. If you want to run an exit node without
4949 thinking too hard about which ports to allow, this one is for you.
4950 Closes ticket 13605. Patch from Neel Chauhan.
4952 o Minor features (testing, debugging, embedding):
4953 - For development purposes, Tor now has a mode in which it runs for
4954 a few seconds, then stops, and starts again without exiting the
4955 process. This mode is meant to help us debug various issues with
4956 ticket 23847. To use this feature, compile with
4957 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
4958 environment variable. This is expected to crash a lot, and is
4959 really meant for developers only. It will likely be removed in a
4960 future release. Implements ticket 24583.
4962 o Minor bugfix (network IPv6 test):
4963 - Tor's test scripts now check if "ping -6 ::1" works when the user
4964 runs "make test-network-all". Fixes bug 24677; bugfix on
4965 0.2.9.3-alpha. Patch by "ffmancera".
4967 o Minor bugfixes (build, rust):
4968 - Fix output of autoconf checks to display success messages for Rust
4969 dependencies and a suitable rustc compiler version. Fixes bug
4970 24612; bugfix on 0.3.1.3-alpha.
4971 - When building with Rust on OSX, link against libresolv, to work
4972 around the issue at https://github.com/rust-lang/rust/issues/46797.
4973 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
4974 - Don't pass the --quiet option to cargo: it seems to suppress some
4975 errors, which is not what we want to do when building. Fixes bug
4976 24518; bugfix on 0.3.1.7.
4977 - Build correctly when building from outside Tor's source tree with
4978 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
4981 o Minor bugfixes (directory authorities, IPv6):
4982 - When creating a routerstatus (vote) from a routerinfo (descriptor),
4983 set the IPv6 address to the unspecified IPv6 address, and
4984 explicitly initialize the port to zero. Fixes bug 24488; bugfix
4987 o Minor bugfixes (fallback directory mirrors):
4988 - Make updateFallbackDirs.py search harder for python. (Some OSs
4989 don't put it in /usr/bin.) Fixes bug 24708; bugfix
4992 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
4993 - When hibernating, close connections normally and allow them to
4994 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
4996 - Do not attempt to launch self-reachability tests when entering
4997 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
4998 - Resolve several bugs related to descriptor fetching on bridge
4999 clients with bandwidth accounting enabled. (This combination is
5000 not recommended!) Fixes a case of bug 12062; bugfix
5002 - When hibernating, do not attempt to launch DNS checks. Fixes a
5003 case of bug 12062; bugfix on 0.1.2.2-alpha.
5004 - When hibernating, do not try to upload or download descriptors.
5005 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5007 o Minor bugfixes (IPv6, bridges):
5008 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
5009 bugfix on 0.2.8.2-alpha.
5010 - Tor now sets IPv6 address in the routerstatus as well as in the
5011 router descriptors when updating addresses for a bridge. Closes
5012 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
5014 o Minor bugfixes (linux seccomp2 sandbox):
5015 - When running with the sandbox enabled, reload configuration files
5016 correctly even when %include was used. Previously we would crash.
5017 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
5019 o Minor bugfixes (memory leaks):
5020 - Avoid possible at-exit memory leaks related to use of Libevent's
5021 event_base_once() function. (This function tends to leak memory if
5022 the event_base is closed before the event fires.) Fixes bug 24584;
5023 bugfix on 0.2.8.1-alpha.
5024 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
5027 o Minor bugfixes (OSX):
5028 - Don't exit the Tor process if setrlimit() fails to change the file
5029 limit (which can happen sometimes on some versions of OSX). Fixes
5030 bug 21074; bugfix on 0.0.9pre5.
5032 o Minor bugfixes (performance, fragile-hardening):
5033 - Improve the performance of our consensus-diff application code
5034 when Tor is built with the --enable-fragile-hardening option set.
5035 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5037 o Minor bugfixes (performance, timeouts):
5038 - Consider circuits for timeout as soon as they complete a hop. This
5039 is more accurate than applying the timeout in
5040 circuit_expire_building() because that function is only called
5041 once per second, which is now too slow for typical timeouts on the
5042 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
5043 - Use onion service circuits (and other circuits longer than 3 hops)
5044 to calculate a circuit build timeout. Previously, Tor only
5045 calculated its build timeout based on circuits that planned to be
5046 exactly 3 hops long. With this change, we include measurements
5047 from all circuits at the point where they complete their third
5048 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
5050 o Minor bugfixes (testing):
5051 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
5052 bugfix on 0.2.3.1-alpha.
5053 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5054 25005; bugfix on 0.3.2.7-rc.
5056 o Code simplification and refactoring:
5057 - Remove /usr/athena from search path in configure.ac. Closes
5059 - Remove duplicate code in node_has_curve25519_onion_key() and
5060 node_get_curve25519_onion_key(), and add a check for a zero
5061 microdesc curve25519 onion key. Closes ticket 23966, patch by
5062 "aruna1234" and teor.
5063 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
5064 memory allocations with large numbers of OR connections (e.g.
5065 relays). Closes ticket 24119.
5066 - Separate the function that deletes ephemeral files when Tor
5068 - Small changes to Tor's buf_t API to make it suitable for use as a
5069 general-purpose safe string constructor. Closes ticket 22342.
5070 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
5071 avoid source code identifier confusion. Closes ticket 24467.
5072 - The tor_git_revision[] constant no longer needs to be redeclared
5073 by everything that links against the rest of Tor. Done as part of
5074 ticket 23845, to simplify our external API.
5075 - We make extend_info_from_node() use node_get_curve25519_onion_key()
5076 introduced in ticket 23577 to access the curve25519 public keys
5077 rather than accessing it directly. Closes ticket 23760. Patch by
5079 - Add a function to log channels' scheduler state changes to aid
5080 debugging efforts. Closes ticket 24531.
5083 - Add documentation on how to build tor with Rust dependencies
5084 without having to be online. Closes ticket 22907; bugfix
5086 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
5087 traffic. Closes ticket 24318.
5088 - Document that OutboundBindAddress doesn't apply to DNS requests.
5089 Closes ticket 22145. Patch from Aruna Maurya.
5090 - Document that operators who run more than one relay or bridge are
5091 expected to set MyFamily and ContactInfo correctly. Closes
5094 o Code simplification and refactoring (channels):
5095 - Remove the incoming and outgoing channel queues. These were never
5096 used, but still took up a step in our fast path.
5097 - The majority of the channel unit tests have been rewritten and the
5098 code coverage has now been raised to 83.6% for channel.c. Closes
5100 - Remove other dead code from the channel subsystem: All together,
5101 this cleanup has removed more than 1500 lines of code overall and
5102 adding very little except for unit test.
5104 o Code simplification and refactoring (circuit rendezvous):
5105 - Split the client-side rendezvous circuit lookup into two
5106 functions: one that returns only established circuits and another
5107 that returns all kinds of circuits. Closes ticket 23459.
5109 o Code simplification and refactoring (controller):
5110 - Make most of the variables in networkstatus_getinfo_by_purpose()
5111 const. Implements ticket 24489.
5114 Changes in version 0.3.2.9 - 2018-01-09
5115 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
5117 The 0.3.2 series includes our long-anticipated new onion service
5118 design, with numerous security features. (For more information, see
5119 our blog post at https://blog.torproject.org/fall-harvest.) We also
5120 have a new circuit scheduler algorithm for improved performance on
5121 relays everywhere (see https://blog.torproject.org/kist-and-tell),
5122 along with many smaller features and bugfixes.
5124 Per our stable release policy, we plan to support each stable release
5125 series for at least the next nine months, or for three months after
5126 the first stable release of the next series: whichever is longer. If
5127 you need a release with long-term support, we recommend that you stay
5128 with the 0.2.9 series.
5130 Below is a list of the changes since 0.3.2.8-rc. For a list of all
5131 changes since 0.3.1, see the ReleaseNotes file.
5133 o Minor features (fallback directory mirrors):
5134 - The fallback directory list has been re-generated based on the
5135 current status of the network. Tor uses fallback directories to
5136 bootstrap when it doesn't yet have up-to-date directory
5137 information. Closes ticket 24801.
5138 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5139 prefer to bootstrap from fallback directory mirrors. This is a
5140 follow-up to 24679, which removed weights from the default
5141 fallbacks. Implements ticket 24681.
5143 o Minor features (geoip):
5144 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
5147 o Minor bugfixes (address selection):
5148 - When the fascist_firewall_choose_address_ functions don't find a
5149 reachable address, set the returned address to the null address
5150 and port. This is a precautionary measure, because some callers do
5151 not check the return value. Fixes bug 24736; bugfix
5154 o Minor bugfixes (compilation):
5155 - Resolve a few shadowed-variable warnings in the onion service
5156 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
5158 o Minor bugfixes (portability, msvc):
5159 - Fix a bug in the bit-counting parts of our timing-wheel code on
5160 MSVC. (Note that MSVC is still not a supported build platform, due
5161 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5165 Changes in version 0.3.2.8-rc - 2017-12-21
5166 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
5167 schedulers that had led servers under heavy load to overload their
5168 outgoing connections. All relay operators running earlier 0.3.2.x
5169 versions should upgrade. This version also includes a mitigation for
5170 over-full DESTROY queues leading to out-of-memory conditions: if it
5171 works, we will soon backport it to earlier release series.
5173 This is the second release candidate in the 0.3.2 series. If we find
5174 no new bugs or regression here, then the first stable 0.3.2 release
5175 will be nearly identical to this.
5177 o Major bugfixes (KIST, scheduler):
5178 - The KIST scheduler did not correctly account for data already
5179 enqueued in each connection's send socket buffer, particularly in
5180 cases when the TCP/IP congestion window was reduced between
5181 scheduler calls. This situation lead to excessive per-connection
5182 buffering in the kernel, and a potential memory DoS. Fixes bug
5183 24665; bugfix on 0.3.2.1-alpha.
5185 o Minor features (geoip):
5186 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
5189 o Minor bugfixes (hidden service v3):
5190 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
5191 the probability of reaching a service for a client missing
5192 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
5194 o Minor bugfixes (memory usage):
5195 - When queuing DESTROY cells on a channel, only queue the circuit-id
5196 and reason fields: not the entire 514-byte cell. This fix should
5197 help mitigate any bugs or attacks that fill up these queues, and
5198 free more RAM for other uses. Fixes bug 24666; bugfix
5201 o Minor bugfixes (scheduler, KIST):
5202 - Use a sane write limit for KISTLite when writing onto a connection
5203 buffer instead of using INT_MAX and shoving as much as it can.
5204 Because the OOM handler cleans up circuit queues, we are better
5205 off at keeping them in that queue instead of the connection's
5206 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
5209 Changes in version 0.3.2.7-rc - 2017-12-14
5210 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
5211 including some that could affect reliability or correctness.
5213 This is the first release candidate in the 0.3.2 series. If we find no
5214 new bugs or regression here, then the first stable 0.3.2. release will
5215 be nearly identical to this.
5217 o Major bugfixes (circuit prediction):
5218 - Fix circuit prediction logic so that a client doesn't treat a port
5219 as being "handled" by a circuit if that circuit already has
5220 isolation settings on it. This change should make Tor clients more
5221 responsive by improving their chances of having a pre-created
5222 circuit ready for use when a request arrives. Fixes bug 18859;
5223 bugfix on 0.2.3.3-alpha.
5225 o Minor features (logging):
5226 - Provide better warnings when the getrandom() syscall fails. Closes
5229 o Minor features (portability):
5230 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
5231 (It doesn't yet work with the sandbox enabled.) Closes
5234 o Minor bugfixes (bridge clients, bootstrap):
5235 - Retry directory downloads when we get our first bridge descriptor
5236 during bootstrap or while reconnecting to the network. Keep
5237 retrying every time we get a bridge descriptor, until we have a
5238 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
5239 - Stop delaying bridge descriptor fetches when we have cached bridge
5240 descriptors. Instead, only delay bridge descriptor fetches when we
5241 have at least one reachable bridge. Fixes part of bug 24367;
5242 bugfix on 0.2.0.3-alpha.
5243 - Stop delaying directory fetches when we have cached bridge
5244 descriptors. Instead, only delay bridge descriptor fetches when
5245 all our bridges are definitely unreachable. Fixes part of bug
5246 24367; bugfix on 0.2.0.3-alpha.
5248 o Minor bugfixes (compilation):
5249 - Fix a signed/unsigned comparison warning introduced by our fix to
5250 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5252 o Minor bugfixes (correctness):
5253 - Fix several places in our codebase where a C compiler would be
5254 likely to eliminate a check, based on assuming that undefined
5255 behavior had not happened elsewhere in the code. These cases are
5256 usually a sign of redundant checking or dubious arithmetic. Found
5257 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
5258 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
5261 o Minor bugfixes (onion service v3):
5262 - Fix a race where an onion service would launch a new intro circuit
5263 after closing an old one, but fail to register it before freeing
5264 the previously closed circuit. This bug was making the service
5265 unable to find the established intro circuit and thus not upload
5266 its descriptor, thus making a service unavailable for up to 24
5267 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
5269 o Minor bugfixes (scheduler, KIST):
5270 - Properly set the scheduler state of an unopened channel in the
5271 KIST scheduler main loop. This prevents a harmless but annoying
5272 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
5273 - Avoid a possible integer overflow when computing the available
5274 space on the TCP buffer of a channel. This had no security
5275 implications; but could make KIST allow too many cells on a
5276 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
5277 - Downgrade to "info" a harmless warning about the monotonic time
5278 moving backwards: This can happen on platform not supporting
5279 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
5282 Changes in version 0.3.2.6-alpha - 2017-12-01
5283 This version of Tor is the latest in the 0.3.2 alpha series. It
5284 includes fixes for several important security issues. All Tor users
5285 should upgrade to this release, or to one of the other releases coming
5288 o Major bugfixes (security):
5289 - Fix a denial of service bug where an attacker could use a
5290 malformed directory object to cause a Tor instance to pause while
5291 OpenSSL would try to read a passphrase from the terminal. (Tor
5292 instances run without a terminal, which is the case for most Tor
5293 packages, are not impacted.) Fixes bug 24246; bugfix on every
5294 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5295 Found by OSS-Fuzz as testcase 6360145429790720.
5296 - Fix a denial of service issue where an attacker could crash a
5297 directory authority using a malformed router descriptor. Fixes bug
5298 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5300 - When checking for replays in the INTRODUCE1 cell data for a
5301 (legacy) onion service, correctly detect replays in the RSA-
5302 encrypted part of the cell. We were previously checking for
5303 replays on the entire cell, but those can be circumvented due to
5304 the malleability of Tor's legacy hybrid encryption. This fix helps
5305 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5306 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5309 o Major bugfixes (security, onion service v2):
5310 - Fix a use-after-free error that could crash v2 Tor onion services
5311 when they failed to open circuits while expiring introduction
5312 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5313 also tracked as TROVE-2017-013 and CVE-2017-8823.
5315 o Major bugfixes (security, relay):
5316 - When running as a relay, make sure that we never build a path
5317 through ourselves, even in the case where we have somehow lost the
5318 version of our descriptor appearing in the consensus. Fixes part
5319 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5320 as TROVE-2017-012 and CVE-2017-8822.
5321 - When running as a relay, make sure that we never choose ourselves
5322 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5323 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5325 o Minor feature (relay statistics):
5326 - Change relay bandwidth reporting stats interval from 4 hours to 24
5327 hours in order to reduce the efficiency of guard discovery
5328 attacks. Fixes ticket 23856.
5330 o Minor features (directory authority):
5331 - Add an IPv6 address for the "bastet" directory authority. Closes
5334 o Minor bugfixes (client):
5335 - By default, do not enable storage of client-side DNS values. These
5336 values were unused by default previously, but they should not have
5337 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
5340 Changes in version 0.3.1.9 - 2017-12-01:
5341 Tor 0.3.1.9 backports important security and stability fixes from the
5342 0.3.2 development series. All Tor users should upgrade to this
5343 release, or to another of the releases coming out today.
5345 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5346 - Fix a denial of service bug where an attacker could use a
5347 malformed directory object to cause a Tor instance to pause while
5348 OpenSSL would try to read a passphrase from the terminal. (Tor
5349 instances run without a terminal, which is the case for most Tor
5350 packages, are not impacted.) Fixes bug 24246; bugfix on every
5351 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5352 Found by OSS-Fuzz as testcase 6360145429790720.
5353 - Fix a denial of service issue where an attacker could crash a
5354 directory authority using a malformed router descriptor. Fixes bug
5355 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5357 - When checking for replays in the INTRODUCE1 cell data for a
5358 (legacy) onion service, correctly detect replays in the RSA-
5359 encrypted part of the cell. We were previously checking for
5360 replays on the entire cell, but those can be circumvented due to
5361 the malleability of Tor's legacy hybrid encryption. This fix helps
5362 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5363 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5366 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5367 - Fix a use-after-free error that could crash v2 Tor onion services
5368 when they failed to open circuits while expiring introduction
5369 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5370 also tracked as TROVE-2017-013 and CVE-2017-8823.
5372 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5373 - When running as a relay, make sure that we never build a path
5374 through ourselves, even in the case where we have somehow lost the
5375 version of our descriptor appearing in the consensus. Fixes part
5376 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5377 as TROVE-2017-012 and CVE-2017-8822.
5378 - When running as a relay, make sure that we never choose ourselves
5379 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5380 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5382 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5383 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5384 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5385 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5386 identifying and finding a workaround to this bug and to Moritz,
5387 Arthur Edelstein, and Roger for helping to track it down and
5390 o Minor features (bridge):
5391 - Bridges now include notice in their descriptors that they are
5392 bridges, and notice of their distribution status, based on their
5393 publication settings. Implements ticket 18329. For more fine-
5394 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5397 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5398 - Add an IPv6 address for the "bastet" directory authority. Closes
5401 o Minor features (geoip):
5402 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5405 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5406 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5407 relays, to prevent spurious address resolutions and descriptor
5408 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5409 bugfix on in 0.2.8.1-alpha.
5411 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5412 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5413 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5415 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5416 - When a circuit is marked for close, do not attempt to package any
5417 cells for channels on that circuit. Previously, we would detect
5418 this condition lower in the call stack, when we noticed that the
5419 circuit had no attached channel, and log an annoying message.
5420 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5422 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
5423 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
5424 so it matches dir-spec.txt. Fixes bug 24262; bugfix
5427 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5428 - Avoid a crash when transitioning from client mode to bridge mode.
5429 Previously, we would launch the worker threads whenever our
5430 "public server" mode changed, but not when our "server" mode
5431 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5434 Changes in version 0.3.0.13 - 2017-12-01
5435 Tor 0.3.0.13 backports important security and stability bugfixes from
5436 later Tor releases. All Tor users should upgrade to this release, or
5437 to another of the releases coming out today.
5439 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
5440 2018. If you need a release with long-term support, please stick with
5441 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5443 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5444 - Fix a denial of service bug where an attacker could use a
5445 malformed directory object to cause a Tor instance to pause while
5446 OpenSSL would try to read a passphrase from the terminal. (Tor
5447 instances run without a terminal, which is the case for most Tor
5448 packages, are not impacted.) Fixes bug 24246; bugfix on every
5449 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5450 Found by OSS-Fuzz as testcase 6360145429790720.
5451 - Fix a denial of service issue where an attacker could crash a
5452 directory authority using a malformed router descriptor. Fixes bug
5453 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5455 - When checking for replays in the INTRODUCE1 cell data for a
5456 (legacy) onion service, correctly detect replays in the RSA-
5457 encrypted part of the cell. We were previously checking for
5458 replays on the entire cell, but those can be circumvented due to
5459 the malleability of Tor's legacy hybrid encryption. This fix helps
5460 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5461 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5464 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5465 - Fix a use-after-free error that could crash v2 Tor onion services
5466 when they failed to open circuits while expiring introduction
5467 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5468 also tracked as TROVE-2017-013 and CVE-2017-8823.
5470 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5471 - When running as a relay, make sure that we never build a path
5472 through ourselves, even in the case where we have somehow lost the
5473 version of our descriptor appearing in the consensus. Fixes part
5474 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5475 as TROVE-2017-012 and CVE-2017-8822.
5476 - When running as a relay, make sure that we never choose ourselves
5477 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5478 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5480 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5481 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5482 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5483 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5484 identifying and finding a workaround to this bug and to Moritz,
5485 Arthur Edelstein, and Roger for helping to track it down and
5488 o Minor features (security, windows, backport from 0.3.1.1-alpha):
5489 - Enable a couple of pieces of Windows hardening: one
5490 (HeapEnableTerminationOnCorruption) that has been on-by-default
5491 since Windows 8, and unavailable before Windows 7; and one
5492 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5493 affect us, but shouldn't do any harm. Closes ticket 21953.
5495 o Minor features (bridge, backport from 0.3.1.9):
5496 - Bridges now include notice in their descriptors that they are
5497 bridges, and notice of their distribution status, based on their
5498 publication settings. Implements ticket 18329. For more fine-
5499 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5502 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5503 - Add an IPv6 address for the "bastet" directory authority. Closes
5506 o Minor features (geoip):
5507 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5510 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5511 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5512 relays, to prevent spurious address resolutions and descriptor
5513 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5514 bugfix on in 0.2.8.1-alpha.
5516 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5517 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5518 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5520 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5521 - When a circuit is marked for close, do not attempt to package any
5522 cells for channels on that circuit. Previously, we would detect
5523 this condition lower in the call stack, when we noticed that the
5524 circuit had no attached channel, and log an annoying message.
5525 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5527 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5528 - Avoid a crash when transitioning from client mode to bridge mode.
5529 Previously, we would launch the worker threads whenever our
5530 "public server" mode changed, but not when our "server" mode
5531 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5533 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5534 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5535 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5538 Changes in version 0.2.9.14 - 2017-12-01
5539 Tor 0.3.0.13 backports important security and stability bugfixes from
5540 later Tor releases. All Tor users should upgrade to this release, or
5541 to another of the releases coming out today.
5543 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5544 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5545 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5546 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5547 identifying and finding a workaround to this bug and to Moritz,
5548 Arthur Edelstein, and Roger for helping to track it down and
5551 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5552 - Fix a denial of service bug where an attacker could use a
5553 malformed directory object to cause a Tor instance to pause while
5554 OpenSSL would try to read a passphrase from the terminal. (Tor
5555 instances run without a terminal, which is the case for most Tor
5556 packages, are not impacted.) Fixes bug 24246; bugfix on every
5557 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5558 Found by OSS-Fuzz as testcase 6360145429790720.
5559 - Fix a denial of service issue where an attacker could crash a
5560 directory authority using a malformed router descriptor. Fixes bug
5561 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5563 - When checking for replays in the INTRODUCE1 cell data for a
5564 (legacy) onion service, correctly detect replays in the RSA-
5565 encrypted part of the cell. We were previously checking for
5566 replays on the entire cell, but those can be circumvented due to
5567 the malleability of Tor's legacy hybrid encryption. This fix helps
5568 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5569 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5572 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5573 - Fix a use-after-free error that could crash v2 Tor onion services
5574 when they failed to open circuits while expiring introduction
5575 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5576 also tracked as TROVE-2017-013 and CVE-2017-8823.
5578 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5579 - When running as a relay, make sure that we never build a path
5580 through ourselves, even in the case where we have somehow lost the
5581 version of our descriptor appearing in the consensus. Fixes part
5582 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5583 as TROVE-2017-012 and CVE-2017-8822.
5585 o Minor features (bridge, backport from 0.3.1.9):
5586 - Bridges now include notice in their descriptors that they are
5587 bridges, and notice of their distribution status, based on their
5588 publication settings. Implements ticket 18329. For more fine-
5589 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5592 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5593 - Add an IPv6 address for the "bastet" directory authority. Closes
5596 o Minor features (geoip):
5597 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5600 o Minor features (security, windows, backport from 0.3.1.1-alpha):
5601 - Enable a couple of pieces of Windows hardening: one
5602 (HeapEnableTerminationOnCorruption) that has been on-by-default
5603 since Windows 8, and unavailable before Windows 7; and one
5604 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
5605 affect us, but shouldn't do any harm. Closes ticket 21953.
5607 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5608 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5609 relays, to prevent spurious address resolutions and descriptor
5610 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5611 bugfix on in 0.2.8.1-alpha.
5613 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5614 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5615 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5617 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5618 - When a circuit is marked for close, do not attempt to package any
5619 cells for channels on that circuit. Previously, we would detect
5620 this condition lower in the call stack, when we noticed that the
5621 circuit had no attached channel, and log an annoying message.
5622 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5624 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5625 - Avoid a crash when transitioning from client mode to bridge mode.
5626 Previously, we would launch the worker threads whenever our
5627 "public server" mode changed, but not when our "server" mode
5628 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5630 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5631 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5632 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5635 Changes in version 0.2.8.17 - 2017-12-01
5636 Tor 0.2.8.17 backports important security and stability bugfixes from
5637 later Tor releases. All Tor users should upgrade to this release, or
5638 to another of the releases coming out today.
5640 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
5641 2018. If you need a release with long-term support, please upgrade with
5642 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5644 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5645 - Fix a denial of service bug where an attacker could use a
5646 malformed directory object to cause a Tor instance to pause while
5647 OpenSSL would try to read a passphrase from the terminal. (Tor
5648 instances run without a terminal, which is the case for most Tor
5649 packages, are not impacted.) Fixes bug 24246; bugfix on every
5650 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5651 Found by OSS-Fuzz as testcase 6360145429790720.
5652 - When checking for replays in the INTRODUCE1 cell data for a
5653 (legacy) onion service, correctly detect replays in the RSA-
5654 encrypted part of the cell. We were previously checking for
5655 replays on the entire cell, but those can be circumvented due to
5656 the malleability of Tor's legacy hybrid encryption. This fix helps
5657 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5658 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5661 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5662 - Fix a use-after-free error that could crash v2 Tor onion services
5663 when they failed to open circuits while expiring introduction
5664 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5665 also tracked as TROVE-2017-013 and CVE-2017-8823.
5667 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5668 - When running as a relay, make sure that we never build a path through
5669 ourselves, even in the case where we have somehow lost the version of
5670 our descriptor appearing in the consensus. Fixes part of bug 21534;
5671 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
5674 o Minor features (bridge, backport from 0.3.1.9):
5675 - Bridges now include notice in their descriptors that they are
5676 bridges, and notice of their distribution status, based on their
5677 publication settings. Implements ticket 18329. For more fine-
5678 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5681 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5682 - Add an IPv6 address for the "bastet" directory authority. Closes
5685 o Minor features (geoip):
5686 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5689 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
5690 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
5691 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
5694 Changes in version 0.2.5.16 - 2017-12-01
5695 Tor 0.2.5.13 backports important security and stability bugfixes from
5696 later Tor releases. All Tor users should upgrade to this release, or
5697 to another of the releases coming out today.
5699 Note: the Tor 0.2.5 series will no longer be supported after 1 May
5700 2018. If you need a release with long-term support, please upgrade to
5701 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5703 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5704 - Fix a denial of service bug where an attacker could use a
5705 malformed directory object to cause a Tor instance to pause while
5706 OpenSSL would try to read a passphrase from the terminal. (Tor
5707 instances run without a terminal, which is the case for most Tor
5708 packages, are not impacted.) Fixes bug 24246; bugfix on every
5709 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5710 Found by OSS-Fuzz as testcase 6360145429790720.
5711 - When checking for replays in the INTRODUCE1 cell data for a
5712 (legacy) onion service, correctly detect replays in the RSA-
5713 encrypted part of the cell. We were previously checking for
5714 replays on the entire cell, but those can be circumvented due to
5715 the malleability of Tor's legacy hybrid encryption. This fix helps
5716 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5717 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5720 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5721 - When running as a relay, make sure that we never build a path
5722 through ourselves, even in the case where we have somehow lost the
5723 version of our descriptor appearing in the consensus. Fixes part
5724 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5725 as TROVE-2017-012 and CVE-2017-8822.
5727 o Minor features (bridge, backport from 0.3.1.9):
5728 - Bridges now include notice in their descriptors that they are
5729 bridges, and notice of their distribution status, based on their
5730 publication settings. Implements ticket 18329. For more fine-
5731 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5734 o Minor features (geoip):
5735 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5739 Changes in version 0.3.2.5-alpha - 2017-11-22
5740 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
5741 fixes several stability and reliability bugs, including a fix for
5742 intermittent bootstrapping failures that some people have been seeing
5743 since the 0.3.0.x series.
5745 Please test this alpha out -- many of these fixes will soon be
5746 backported to stable Tor versions if no additional bugs are found
5749 o Major bugfixes (bootstrapping):
5750 - Fetch descriptors aggressively whenever we lack enough to build
5751 circuits, regardless of how many descriptors we are missing.
5752 Previously, we would delay launching the fetch when we had fewer
5753 than 15 missing descriptors, even if some of those descriptors
5754 were blocking circuits from building. Fixes bug 23985; bugfix on
5755 0.1.1.11-alpha. The effects of this bug became worse in
5756 0.3.0.3-alpha, when we began treating missing descriptors from our
5757 primary guards as a reason to delay circuits.
5758 - Don't try fetching microdescriptors from relays that have failed
5759 to deliver them in the past. Fixes bug 23817; bugfix
5762 o Minor features (directory authority):
5763 - Make the "Exit" flag assignment only depend on whether the exit
5764 policy allows connections to ports 80 and 443. Previously relays
5765 would get the Exit flag if they allowed connections to one of
5766 these ports and also port 6667. Resolves ticket 23637.
5768 o Minor features (geoip):
5769 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5772 o Minor features (linux seccomp2 sandbox):
5773 - Update the sandbox rules so that they should now work correctly
5774 with Glibc 2.26. Closes ticket 24315.
5776 o Minor features (logging):
5777 - Downgrade a pair of log messages that could occur when an exit's
5778 resolver gave us an unusual (but not forbidden) response. Closes
5780 - Improve the message we log when re-enabling circuit build timeouts
5781 after having received a consensus. Closes ticket 20963.
5783 o Minor bugfixes (compilation):
5784 - Fix a memory leak warning in one of the libevent-related
5785 configuration tests that could occur when manually specifying
5786 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
5787 Found and patched by Alex Xu.
5788 - When detecting OpenSSL on Windows from our configure script, make
5789 sure to try linking with the ws2_32 library. Fixes bug 23783;
5790 bugfix on 0.3.2.2-alpha.
5792 o Minor bugfixes (control port, linux seccomp2 sandbox):
5793 - Avoid a crash when attempting to use the seccomp2 sandbox together
5794 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5797 o Minor bugfixes (control port, onion services):
5798 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
5799 HS_DESC event when a service is not able to upload a descriptor.
5800 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
5802 o Minor bugfixes (directory cache):
5803 - Recover better from empty or corrupt files in the consensus cache
5804 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
5805 - When a consensus diff calculation is only partially successful,
5806 only record the successful parts as having succeeded. Partial
5807 success can happen if (for example) one compression method fails
5808 but the others succeed. Previously we misrecorded all the
5809 calculations as having succeeded, which would later cause a
5810 nonfatal assertion failure. Fixes bug 24086; bugfix
5813 o Minor bugfixes (logging):
5814 - Only log once if we notice that KIST support is gone. Fixes bug
5815 24158; bugfix on 0.3.2.1-alpha.
5816 - Suppress a log notice when relay descriptors arrive. We already
5817 have a bootstrap progress for this so no need to log notice
5818 everytime tor receives relay descriptors. Microdescriptors behave
5819 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
5821 o Minor bugfixes (network layer):
5822 - When closing a connection via close_connection_immediately(), we
5823 mark it as "not blocked on bandwidth", to prevent later calls from
5824 trying to unblock it, and give it permission to read. This fixes a
5825 backtrace warning that can happen on relays under various
5826 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5828 o Minor bugfixes (onion services):
5829 - The introduction circuit was being timed out too quickly while
5830 waiting for the rendezvous circuit to complete. Keep the intro
5831 circuit around longer instead of timing out and reopening new ones
5832 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
5833 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
5834 so it matches dir-spec.txt. Fixes bug 24262; bugfix
5836 - Silence a warning about failed v3 onion descriptor uploads that
5837 can happen naturally under certain edge cases. Fixes part of bug
5838 23662; bugfix on 0.3.2.1-alpha.
5840 o Minor bugfixes (tests):
5841 - Fix a memory leak in one of the bridge-distribution test cases.
5842 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
5843 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
5844 to correctly handle cases where a caller gives it an RSA key of
5845 under 160 bits. (This is not actually a bug in Tor itself, but
5846 rather in our fuzzing code.) Fixes bug 24247; bugfix on
5847 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
5850 - Add notes in man page regarding OS support for the various
5851 scheduler types. Attempt to use less jargon in the scheduler
5852 section. Closes ticket 24254.
5855 Changes in version 0.3.2.4-alpha - 2017-11-08
5856 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
5857 It fixes several stability and reliability bugs, especially including
5858 a major reliability issue that has been plaguing fast exit relays in
5861 o Major bugfixes (exit relays, DNS):
5862 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5863 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5864 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5865 identifying and finding a workaround to this bug and to Moritz,
5866 Arthur Edelstein, and Roger for helping to track it down and
5869 o Major bugfixes (scheduler, channel):
5870 - Stop processing scheduled channels if they closed while flushing
5871 cells. This can happen if the write on the connection fails
5872 leading to the channel being closed while in the scheduler loop.
5873 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
5875 o Minor features (logging, scheduler):
5876 - Introduce a SCHED_BUG() function to log extra information about
5877 the scheduler state if we ever catch a bug in the scheduler.
5878 Closes ticket 23753.
5880 o Minor features (removed deprecations):
5881 - The ClientDNSRejectInternalAddresses flag can once again be set in
5882 non-testing Tor networks, so long as they do not use the default
5883 directory authorities. This change also removes the deprecation of
5884 this flag from 0.2.9.2-alpha. Closes ticket 21031.
5886 o Minor features (testing):
5887 - Our fuzzing tests now test the encrypted portions of v3 onion
5888 service descriptors. Implements more of 21509.
5890 o Minor bugfixes (directory client):
5891 - On failure to download directory information, delay retry attempts
5892 by a random amount based on the "decorrelated jitter" algorithm.
5893 Our previous delay algorithm tended to produce extra-long delays
5894 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
5896 o Minor bugfixes (IPv6, v3 single onion services):
5897 - Remove buggy code for IPv6-only v3 single onion services, and
5898 reject attempts to configure them. This release supports IPv4,
5899 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
5900 stack v3 single onion services. Fixes bug 23820; bugfix
5903 o Minor bugfixes (logging, relay):
5904 - Give only a protocol warning when the ed25519 key is not
5905 consistent between the descriptor and microdescriptor of a relay.
5906 This can happen, for instance, if the relay has been flagged
5907 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
5909 o Minor bugfixes (manpage, onion service):
5910 - Document that the HiddenServiceNumIntroductionPoints option is
5911 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
5912 bugfix on 0.3.2.1-alpha.
5914 o Minor bugfixes (memory leaks):
5915 - Fix a minor memory leak at exit in the KIST scheduler. This bug
5916 should have no user-visible impact. Fixes bug 23774; bugfix
5918 - Fix a memory leak when decrypting a badly formatted v3 onion
5919 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
5920 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
5922 o Minor bugfixes (onion services):
5923 - Cache some needed onion service client information instead of
5924 constantly computing it over and over again. Fixes bug 23623;
5925 bugfix on 0.3.2.1-alpha.
5926 - Properly retry HSv3 descriptor fetches when missing required
5927 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
5929 o Minor bugfixes (path selection):
5930 - When selecting relays by bandwidth, avoid a rounding error that
5931 could sometimes cause load to be imbalanced incorrectly.
5932 Previously, we would always round upwards; now, we round towards
5933 the nearest integer. This had the biggest effect when a relay's
5934 weight adjustments should have given it weight 0, but it got
5935 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5936 - When calculating the fraction of nodes that have descriptors, and
5937 all nodes in the network have zero bandwidths, count the number of
5938 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5939 - Actually log the total bandwidth in compute_weighted_bandwidths().
5940 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5942 o Minor bugfixes (relay, crash):
5943 - Avoid a crash when transitioning from client mode to bridge mode.
5944 Previously, we would launch the worker threads whenever our
5945 "public server" mode changed, but not when our "server" mode
5946 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5948 o Minor bugfixes (testing):
5949 - Fix a spurious fuzzing-only use of an uninitialized value. Found
5950 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
5951 - Test that IPv6-only clients can use microdescriptors when running
5952 "make test-network-all". Requires chutney master 61c28b9 or later.
5953 Closes ticket 24109.
5956 Changes in version 0.3.2.3-alpha - 2017-10-27
5957 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
5958 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
5959 directory authority, Bastet.
5961 o Directory authority changes:
5962 - Add "Bastet" as a ninth directory authority to the default list.
5963 Closes ticket 23910.
5964 - The directory authority "Longclaw" has changed its IP address.
5965 Closes ticket 23592.
5967 o Minor features (bridge):
5968 - Bridge relays can now set the BridgeDistribution config option to
5969 add a "bridge-distribution-request" line to their bridge
5970 descriptor, which tells BridgeDB how they'd like their bridge
5971 address to be given out. (Note that as of Oct 2017, BridgeDB does
5972 not yet implement this feature.) As a side benefit, this feature
5973 provides a way to distinguish bridge descriptors from non-bridge
5974 descriptors. Implements tickets 18329.
5976 o Minor features (client, entry guards):
5977 - Improve log messages when missing descriptors for primary guards.
5978 Resolves ticket 23670.
5980 o Minor features (geoip):
5981 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
5984 o Minor bugfixes (bridge):
5985 - Overwrite the bridge address earlier in the process of retrieving
5986 its descriptor, to make sure we reach it on the configured
5987 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
5989 o Minor bugfixes (documentation):
5990 - Document better how to read gcov, and what our gcov postprocessing
5991 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
5993 o Minor bugfixes (entry guards):
5994 - Tor now updates its guard state when it reads a consensus
5995 regardless of whether it's missing descriptors. That makes tor use
5996 its primary guards to fetch descriptors in some edge cases where
5997 it would previously have used fallback directories. Fixes bug
5998 23862; bugfix on 0.3.0.1-alpha.
6000 o Minor bugfixes (hidden service client):
6001 - When handling multiple SOCKS request for the same .onion address,
6002 only fetch the service descriptor once.
6003 - When a descriptor fetch fails with a non-recoverable error, close
6004 all pending SOCKS requests for that .onion. Fixes bug 23653;
6005 bugfix on 0.3.2.1-alpha.
6007 o Minor bugfixes (hidden service):
6008 - Always regenerate missing hidden service public key files. Prior
6009 to this, if the public key was deleted from disk, it wouldn't get
6010 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
6012 - Make sure that we have a usable ed25519 key when the intro point
6013 relay supports ed25519 link authentication. Fixes bug 24002;
6014 bugfix on 0.3.2.1-alpha.
6016 o Minor bugfixes (hidden service, v2):
6017 - When reloading configured hidden services, copy all information
6018 from the old service object. Previously, some data was omitted,
6019 causing delays in descriptor upload, and other bugs. Fixes bug
6020 23790; bugfix on 0.2.1.9-alpha.
6022 o Minor bugfixes (memory safety, defensive programming):
6023 - Clear the target address when node_get_prim_orport() returns
6024 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6026 o Minor bugfixes (relay):
6027 - Avoid a BUG warning when receiving a dubious CREATE cell while an
6028 option transition is in progress. Fixes bug 23952; bugfix
6031 o Minor bugfixes (testing):
6032 - Adjust the GitLab CI configuration to more closely match that of
6033 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
6034 - Prevent scripts/test/coverage from attempting to move gcov output
6035 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
6036 - When running unit tests as root, skip a test that would fail
6037 because it expects a permissions error. This affects some
6038 continuous integration setups. Fixes bug 23758; bugfix
6040 - Stop unconditionally mirroring the tor repository in GitLab CI.
6041 This prevented developers from enabling GitLab CI on master. Fixes
6042 bug 23755; bugfix on 0.3.2.2-alpha.
6043 - Fix the hidden service v3 descriptor decoding fuzzing to use the
6044 latest decoding API correctly. Fixes bug 21509; bugfix
6047 o Minor bugfixes (warnings):
6048 - When we get an HTTP request on a SOCKS port, tell the user about
6049 the new HTTPTunnelPort option. Previously, we would give a "Tor is
6050 not an HTTP Proxy" message, which stopped being true when
6051 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
6055 Changes in version 0.2.5.15 - 2017-10-25
6056 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
6057 series. It also adds a new directory authority, Bastet.
6059 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6060 2018. If you need a release with long-term support, please upgrade to
6061 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6063 o Directory authority changes:
6064 - Add "Bastet" as a ninth directory authority to the default list.
6065 Closes ticket 23910.
6066 - The directory authority "Longclaw" has changed its IP address.
6067 Closes ticket 23592.
6069 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6070 - Avoid an assertion failure bug affecting our implementation of
6071 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6072 handling of "0xx" differs from what we had expected. Fixes bug
6073 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6075 o Minor features (geoip):
6076 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6079 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6080 - Fix a memset() off the end of an array when packing cells. This
6081 bug should be harmless in practice, since the corrupted bytes are
6082 still in the same structure, and are always padding bytes,
6083 ignored, or immediately overwritten, depending on compiler
6084 behavior. Nevertheless, because the memset()'s purpose is to make
6085 sure that any other cell-handling bugs can't expose bytes to the
6086 network, we need to fix it. Fixes bug 22737; bugfix on
6087 0.2.4.11-alpha. Fixes CID 1401591.
6089 o Build features (backport from 0.3.1.5-alpha):
6090 - Tor's repository now includes a Travis Continuous Integration (CI)
6091 configuration file (.travis.yml). This is meant to help new
6092 developers and contributors who fork Tor to a Github repository be
6093 better able to test their changes, and understand what we expect
6094 to pass. To use this new build feature, you must fork Tor to your
6095 Github account, then go into the "Integrations" menu in the
6096 repository settings for your fork and enable Travis, then push
6097 your changes. Closes ticket 22636.
6100 Changes in version 0.2.8.16 - 2017-10-25
6101 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
6102 series, including a bugfix for a crash issue that had affected relays
6103 under memory pressure. It also adds a new directory authority, Bastet.
6105 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6106 2018. If you need a release with long-term support, please stick with
6107 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6109 o Directory authority changes:
6110 - Add "Bastet" as a ninth directory authority to the default list.
6111 Closes ticket 23910.
6112 - The directory authority "Longclaw" has changed its IP address.
6113 Closes ticket 23592.
6115 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6116 - Fix a timing-based assertion failure that could occur when the
6117 circuit out-of-memory handler freed a connection's output buffer.
6118 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6120 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6121 - Remove longclaw's IPv6 address, as it will soon change. Authority
6122 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6123 3/8 directory authorities with IPv6 addresses, but there are also
6124 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6126 o Minor features (geoip):
6127 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6131 Changes in version 0.2.9.13 - 2017-10-25
6132 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
6133 series, including a bugfix for a crash issue that had affected relays
6134 under memory pressure. It also adds a new directory authority, Bastet.
6136 o Directory authority changes:
6137 - Add "Bastet" as a ninth directory authority to the default list.
6138 Closes ticket 23910.
6139 - The directory authority "Longclaw" has changed its IP address.
6140 Closes ticket 23592.
6142 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6143 - Fix a timing-based assertion failure that could occur when the
6144 circuit out-of-memory handler freed a connection's output buffer.
6145 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6147 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6148 - Remove longclaw's IPv6 address, as it will soon change. Authority
6149 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6150 3/8 directory authorities with IPv6 addresses, but there are also
6151 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6153 o Minor features (geoip):
6154 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6157 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6158 - When a directory authority rejects a descriptor or extrainfo with
6159 a given digest, mark that digest as undownloadable, so that we do
6160 not attempt to download it again over and over. We previously
6161 tried to avoid downloading such descriptors by other means, but we
6162 didn't notice if we accidentally downloaded one anyway. This
6163 behavior became problematic in 0.2.7.2-alpha, when authorities
6164 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6167 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6168 - Clear the address when node_get_prim_orport() returns early.
6169 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6171 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6172 - When running as a Windows service, set the ID of the main thread
6173 correctly. Failure to do so made us fail to send log messages to
6174 the controller in 0.2.1.16-rc, slowed down controller event
6175 delivery in 0.2.7.3-rc and later, and crash with an assertion
6176 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6177 Patch and diagnosis from "Vort".
6180 Changes in version 0.3.0.12 - 2017-10-25
6181 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
6182 series, including a bugfix for a crash issue that had affected relays
6183 under memory pressure. It also adds a new directory authority, Bastet.
6185 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6186 2018. If you need a release with long-term support, please stick with
6187 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6189 o Directory authority changes:
6190 - Add "Bastet" as a ninth directory authority to the default list.
6191 Closes ticket 23910.
6192 - The directory authority "Longclaw" has changed its IP address.
6193 Closes ticket 23592.
6195 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6196 - Fix a timing-based assertion failure that could occur when the
6197 circuit out-of-memory handler freed a connection's output buffer.
6198 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6200 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6201 - Remove longclaw's IPv6 address, as it will soon change. Authority
6202 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6203 3/8 directory authorities with IPv6 addresses, but there are also
6204 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6206 o Minor features (geoip):
6207 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6210 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6211 - When a directory authority rejects a descriptor or extrainfo with
6212 a given digest, mark that digest as undownloadable, so that we do
6213 not attempt to download it again over and over. We previously
6214 tried to avoid downloading such descriptors by other means, but we
6215 didn't notice if we accidentally downloaded one anyway. This
6216 behavior became problematic in 0.2.7.2-alpha, when authorities
6217 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6220 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
6221 - Avoid a possible double close of a circuit by the intro point on
6222 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6223 bugfix on 0.3.0.1-alpha.
6225 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6226 - Clear the address when node_get_prim_orport() returns early.
6227 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6229 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6230 - When running as a Windows service, set the ID of the main thread
6231 correctly. Failure to do so made us fail to send log messages to
6232 the controller in 0.2.1.16-rc, slowed down controller event
6233 delivery in 0.2.7.3-rc and later, and crash with an assertion
6234 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6235 Patch and diagnosis from "Vort".
6238 Changes in version 0.3.1.8 - 2017-10-25
6239 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
6240 It includes several bugfixes, including a bugfix for a crash issue
6241 that had affected relays under memory pressure. It also adds
6242 a new directory authority, Bastet.
6244 o Directory authority changes:
6245 - Add "Bastet" as a ninth directory authority to the default list.
6246 Closes ticket 23910.
6247 - The directory authority "Longclaw" has changed its IP address.
6248 Closes ticket 23592.
6250 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6251 - Fix a timing-based assertion failure that could occur when the
6252 circuit out-of-memory handler freed a connection's output buffer.
6253 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6255 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6256 - Remove longclaw's IPv6 address, as it will soon change. Authority
6257 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6258 3/8 directory authorities with IPv6 addresses, but there are also
6259 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6261 o Minor features (geoip):
6262 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6265 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
6266 - Fix a compilation warning when building with zstd support on
6267 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
6268 and fixed by Andreas Stieger.
6270 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
6271 - Handle a pathological case when decompressing Zstandard data when
6272 the output buffer size is zero. Fixes bug 23551; bugfix
6275 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
6276 - Remove the length limit on HTTP status lines that authorities can
6277 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
6279 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
6280 - Avoid a possible double close of a circuit by the intro point on
6281 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6282 bugfix on 0.3.0.1-alpha.
6284 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6285 - Clear the address when node_get_prim_orport() returns early.
6286 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6288 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
6289 - Fix additional channelpadding unit test failures by using mocked
6290 time instead of actual time for all tests. Fixes bug 23608; bugfix
6294 Changes in version 0.3.2.2-alpha - 2017-09-29
6295 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
6296 release fixes several minor bugs in the new scheduler and next-
6297 generation onion services; both features were newly added in the 0.3.2
6298 series. Other fixes in this alpha include several fixes for non-fatal
6299 tracebacks which would appear in logs.
6301 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
6302 alpha does not contain any substantial new features. Minor features
6303 include better testing and logging.
6305 The following comprises the complete list of changes included
6308 o Major bugfixes (relay, crash, assertion failure):
6309 - Fix a timing-based assertion failure that could occur when the
6310 circuit out-of-memory handler freed a connection's output buffer.
6311 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6313 o Major bugfixes (scheduler):
6314 - If a channel is put into the scheduler's pending list, then it
6315 starts closing, and then if the scheduler runs before it finishes
6316 closing, the scheduler will get stuck trying to flush its cells
6317 while the lower layers refuse to cooperate. Fix that race
6318 condition by giving the scheduler an escape method. Fixes bug
6319 23676; bugfix on 0.3.2.1-alpha.
6321 o Minor features (build, compilation):
6322 - The "check-changes" feature is now part of the "make check" tests;
6323 we'll use it to try to prevent misformed changes files from
6324 accumulating. Closes ticket 23564.
6325 - Tor builds should now fail if there are any mismatches between the
6326 C type representing a configuration variable and the C type the
6327 data-driven parser uses to store a value there. Previously, we
6328 needed to check these by hand, which sometimes led to mistakes.
6329 Closes ticket 23643.
6331 o Minor features (directory authorities):
6332 - Remove longclaw's IPv6 address, as it will soon change. Authority
6333 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6334 3/8 directory authorities with IPv6 addresses, but there are also
6335 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6337 o Minor features (hidden service, circuit, logging):
6338 - Improve logging of many callsite in the circuit subsystem to print
6339 the circuit identifier(s).
6340 - Log when we cleanup an intro point from a service so we know when
6341 and for what reason it happened. Closes ticket 23604.
6343 o Minor features (logging):
6344 - Log more circuit information whenever we are about to try to
6345 package a relay cell on a circuit with a nonexistent n_chan.
6346 Attempt to diagnose ticket 8185.
6347 - Improve info-level log identification of particular circuits, to
6348 help with debugging. Closes ticket 23645.
6350 o Minor features (relay):
6351 - When choosing which circuits can be expired as unused, consider
6352 circuits from clients even if those clients used regular CREATE
6353 cells to make them; and do not consider circuits from relays even
6354 if they were made with CREATE_FAST. Part of ticket 22805.
6356 o Minor features (robustness):
6357 - Change several fatal assertions when flushing buffers into non-
6358 fatal assertions, to prevent any recurrence of 23690.
6360 o Minor features (spec conformance, bridge, diagnostic):
6361 - When handling the USERADDR command on an ExtOrPort, warn when the
6362 transports provides a USERADDR with no port. In a future version,
6363 USERADDR commands of this format may be rejected. Detects problems
6364 related to ticket 23080.
6366 o Minor features (testing):
6367 - Add a unit test to make sure that our own generated platform
6368 string will be accepted by directory authorities. Closes
6371 o Minor bugfixes (bootstrapping):
6372 - When warning about state file clock skew, report the correct
6373 direction for the detected skew. Fixes bug 23606; bugfix
6375 - Avoid an assertion failure when logging a state file clock skew
6376 very early in bootstrapping. Fixes bug 23607; bugfix
6379 o Minor bugfixes (build, compilation):
6380 - Fix a compilation warning when building with zstd support on
6381 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
6382 and fixed by Andreas Stieger.
6383 - When searching for OpenSSL, don't accept any OpenSSL library that
6384 lacks TLSv1_1_method(): Tor doesn't build with those versions.
6385 Additionally, look in /usr/local/opt/openssl, if it's present.
6386 These changes together repair the default build on OSX systems
6387 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
6389 o Minor bugfixes (compression):
6390 - Handle a pathological case when decompressing Zstandard data when
6391 the output buffer size is zero. Fixes bug 23551; bugfix
6394 o Minor bugfixes (documentation):
6395 - Fix manpage to not refer to the obsolete (and misspelled)
6396 UseEntryGuardsAsDirectoryGuards parameter in the description of
6397 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
6399 o Minor bugfixes (hidden service v3):
6400 - Don't log an assertion failure when we can't find the right
6401 information to extend to an introduction point. In rare cases,
6402 this could happen, causing a warning, even though tor would
6403 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
6404 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
6405 much bigger so the rendezvous point can't distinguish which hidden
6406 service protocol is being used. Fixes bug 23420; bugfix
6409 o Minor bugfixes (hidden service, relay):
6410 - Avoid a possible double close of a circuit by the intro point on
6411 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6412 bugfix on 0.3.0.1-alpha.
6414 o Minor bugfixes (logging, relay shutdown, annoyance):
6415 - When a circuit is marked for close, do not attempt to package any
6416 cells for channels on that circuit. Previously, we would detect
6417 this condition lower in the call stack, when we noticed that the
6418 circuit had no attached channel, and log an annoying message.
6419 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6421 o Minor bugfixes (scheduler):
6422 - When switching schedulers due to a consensus change, we didn't
6423 give the new scheduler a chance to react to the consensus. Fix
6424 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
6425 - Make the KISTSchedRunInterval option a non negative value. With
6426 this, the way to disable KIST through the consensus is to set it
6427 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
6428 - Only notice log the selected scheduler when we switch scheduler
6429 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
6430 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
6431 by a different tv_usec data type. Fixes bug 23575; bugfix
6433 - Make a hard exit if tor is unable to pick a scheduler which can
6434 happen if the user specifies a scheduler type that is not
6435 supported and not other types in Schedulers. Fixes bug 23581;
6436 bugfix on 0.3.2.1-alpha.
6437 - Properly initialize the scheduler last run time counter so it is
6438 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
6440 o Minor bugfixes (testing):
6441 - Capture and detect several "Result does not fit" warnings in unit
6442 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
6444 - Fix additional channelpadding unit test failures by using mocked
6445 time instead of actual time for all tests. Fixes bug 23608; bugfix
6447 - The removal of some old scheduler options caused some tests to
6448 fail on BSD systems. Assume current behavior is correct and make
6449 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
6451 o Code simplification and refactoring:
6452 - Remove various ways of testing circuits and connections for
6453 "clientness"; instead, favor channel_is_client(). Part of
6456 o Deprecated features:
6457 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
6458 now deprecated; they do not apply to relays, and they have had no
6459 effect on clients since 0.2.8.x. Closes ticket 19704.
6462 - HiddenServiceVersion man page entry wasn't mentioning the now
6463 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
6464 - Clarify that the Address option is entirely about setting an
6465 advertised IPv4 address. Closes ticket 18891.
6466 - Clarify the manpage's use of the term "address" to clarify what
6467 kind of address is intended. Closes ticket 21405.
6468 - Document that onion service subdomains are allowed, and ignored.
6469 Closes ticket 18736.
6472 Changes in version 0.3.2.1-alpha - 2017-09-18
6473 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
6474 includes support for our next-generation ("v3") onion service
6475 protocol, and adds a new circuit scheduler for more responsive
6476 forwarding decisions from relays. There are also numerous other small
6477 features and bugfixes here.
6479 Below are the changes since Tor 0.3.1.7.
6481 o Major feature (scheduler, channel):
6482 - Tor now uses new schedulers to decide which circuits should
6483 deliver cells first, in order to improve congestion at relays. The
6484 first type is called "KIST" ("Kernel Informed Socket Transport"),
6485 and is only available on Linux-like systems: it uses feedback from
6486 the kernel to prevent the kernel's TCP buffers from growing too
6487 full. The second new scheduler type is called "KISTLite": it
6488 behaves the same as KIST, but runs on systems without kernel
6489 support for inspecting TCP implementation details. The old
6490 scheduler is still available, under the name "Vanilla". To change
6491 the default scheduler preference order, use the new "Schedulers"
6492 option. (The default preference order is "KIST,KISTLite,Vanilla".)
6494 Matt Traudt implemented KIST, based on research by Rob Jansen,
6495 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
6496 more information, see the design paper at
6497 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
6498 followup implementation paper at https://arxiv.org/abs/1709.01044.
6499 Closes ticket 12541.
6501 o Major features (next-generation onion services):
6502 - Tor now supports the next-generation onion services protocol for
6503 clients and services! As part of this release, the core of
6504 proposal 224 has been implemented and is available for
6505 experimentation and testing by our users. This newer version of
6506 onion services ("v3") features many improvements over the legacy
6509 a) Better crypto (replaced SHA1/DH/RSA1024
6510 with SHA3/ed25519/curve25519)
6512 b) Improved directory protocol, leaking much less information to
6515 c) Improved directory protocol, with smaller surface for
6518 d) Better onion address security against impersonation.
6520 e) More extensible introduction/rendezvous protocol.
6522 f) A cleaner and more modular codebase.
6524 You can identify a next-generation onion address by its length:
6525 they are 56 characters long, as in
6526 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
6528 In the future, we will release more options and features for v3
6529 onion services, but we first need a testing period, so that the
6530 current codebase matures and becomes more robust. Planned features
6531 include: offline keys, advanced client authorization, improved
6532 guard algorithms, and statistics. For full details, see
6535 Legacy ("v2") onion services will still work for the foreseeable
6536 future, and will remain the default until this new codebase gets
6537 tested and hardened. Service operators who want to experiment with
6538 the new system can use the 'HiddenServiceVersion 3' torrc
6539 directive along with the regular onion service configuration
6540 options. We will publish a blog post about this new feature
6543 o Major bugfixes (usability, control port):
6544 - Report trusted clock skew indications as bootstrap errors, so
6545 controllers can more easily alert users when their clocks are
6546 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
6548 o Minor features (bug detection):
6549 - Log a warning message with a stack trace for any attempt to call
6550 get_options() during option validation. This pattern has caused
6551 subtle bugs in the past. Closes ticket 22281.
6553 o Minor features (client):
6554 - You can now use Tor as a tunneled HTTP proxy: use the new
6555 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
6556 requests. Closes ticket 22407.
6557 - Add an extra check to make sure that we always use the newer guard
6558 selection code for picking our guards. Closes ticket 22779.
6559 - When downloading (micro)descriptors, don't split the list into
6560 multiple requests unless we want at least 32 descriptors.
6561 Previously, we split at 4, not 32, which led to significant
6562 overhead in HTTP request size and degradation in compression
6563 performance. Closes ticket 23220.
6565 o Minor features (command line):
6566 - Add a new commandline option, --key-expiration, which prints when
6567 the current signing key is going to expire. Implements ticket
6568 17639; patch by Isis Lovecruft.
6570 o Minor features (control port):
6571 - If an application tries to use the control port as an HTTP proxy,
6572 respond with a meaningful "This is the Tor control port" message,
6573 and log the event. Closes ticket 1667. Patch from Ravi
6575 - Provide better error message for GETINFO desc/(id|name) when not
6576 fetching router descriptors. Closes ticket 5847. Patch by
6578 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
6579 whether Tor will try to download router descriptors and
6580 microdescriptors respectively. Closes ticket 22684.
6581 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
6582 so controllers can tell whether the geoip databases are loaded.
6583 Closes ticket 23237.
6584 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
6585 events. Closes ticket 19254. Patch by "DonnchaC".
6587 o Minor features (development support):
6588 - Developers can now generate a call-graph for Tor using the
6589 "calltool" python program, which post-processes object dumps. It
6590 should work okay on many Linux and OSX platforms, and might work
6591 elsewhere too. To run it, install calltool from
6592 https://gitweb.torproject.org/user/nickm/calltool.git and run
6593 "make callgraph". Closes ticket 19307.
6595 o Minor features (ed25519):
6596 - Add validation function to checks for torsion components in
6597 ed25519 public keys, used by prop224 client-side code. Closes
6598 ticket 22006. Math help by Ian Goldberg.
6600 o Minor features (exit relay, DNS):
6601 - Improve the clarity and safety of the log message from evdns when
6602 receiving an apparently spoofed DNS reply. Closes ticket 3056.
6604 o Minor features (integration, hardening):
6605 - Add a new NoExec option to prevent Tor from running other
6606 programs. When this option is set to 1, Tor will never try to run
6607 another program, regardless of the settings of
6608 PortForwardingHelper, ClientTransportPlugin, or
6609 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
6610 without restarting Tor. Closes ticket 22976.
6612 o Minor features (logging):
6613 - Improve the warning message for specifying a relay by nickname.
6614 The previous message implied that nickname registration was still
6615 part of the Tor network design, which it isn't. Closes
6617 - If the sandbox filter fails to load, suggest to the user that
6618 their kernel might not support seccomp2. Closes ticket 23090.
6620 o Minor features (portability):
6621 - Check at configure time whether uint8_t is the same type as
6622 unsigned char. Lots of existing code already makes this
6623 assumption, and there could be strict aliasing issues if the
6624 assumption is violated. Closes ticket 22410.
6626 o Minor features (relay, configuration):
6627 - Reject attempts to use relative file paths when RunAsDaemon is
6628 set. Previously, Tor would accept these, but the directory-
6629 changing step of RunAsDaemon would give strange and/or confusing
6630 results. Closes ticket 22731.
6632 o Minor features (startup, safety):
6633 - When configured to write a PID file, Tor now exits if it is unable
6634 to do so. Previously, it would warn and continue. Closes
6637 o Minor features (static analysis):
6638 - The BUG() macro has been changed slightly so that Coverity no
6639 longer complains about dead code if the bug is impossible. Closes
6642 o Minor features (testing):
6643 - The default chutney network tests now include tests for the v3
6644 hidden service design. Make sure you have the latest version of
6645 chutney if you want to run these. Closes ticket 22437.
6646 - Add a unit test to verify that we can parse a hardcoded v2 hidden
6647 service descriptor. Closes ticket 15554.
6649 o Minor bugfixes (certificate handling):
6650 - Fix a time handling bug in Tor certificates set to expire after
6651 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
6652 Coverity as CID 1415728.
6654 o Minor bugfixes (client, usability):
6655 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
6656 SOCKS4a requests that contain IP address strings, even when
6657 SafeSocks in enabled, as this prevents user from connecting to
6658 known IP addresses without relying on DNS for resolving. SafeSocks
6659 still rejects SOCKS connections that connect to IP addresses when
6660 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
6661 bugfix on Tor 0.2.6.2-alpha.
6663 o Minor bugfixes (code correctness):
6664 - Call htons() in extend_cell_format() for encoding a 16-bit value.
6665 Previously we used ntohs(), which happens to behave the same on
6666 all the platforms we support, but which isn't really correct.
6667 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
6668 - For defense-in-depth, make the controller's write_escaped_data()
6669 function robust to extremely long inputs. Fixes bug 19281; bugfix
6670 on 0.1.1.1-alpha. Reported by Guido Vranken.
6672 o Minor bugfixes (compilation):
6673 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
6674 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6676 o Minor bugfixes (consensus expiry):
6677 - Check for adequate directory information correctly. Previously, Tor
6678 would reconsider whether it had sufficient directory information
6679 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
6681 o Minor bugfixes (directory protocol):
6682 - Directory servers now include a "Date:" http header for response
6683 codes other than 200. Clients starting with a skewed clock and a
6684 recent consensus were getting "304 Not modified" responses from
6685 directory authorities, so without the Date header, the client
6686 would never hear about a wrong clock. Fixes bug 23499; bugfix
6688 - Make clients wait for 6 seconds before trying to download a
6689 consensus from an authority. Fixes bug 17750; bugfix
6692 o Minor bugfixes (DoS-resistance):
6693 - If future code asks if there are any running bridges, without
6694 checking if bridges are enabled, log a BUG warning rather than
6695 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
6697 o Minor bugfixes (format strictness):
6698 - Restrict several data formats to decimal. Previously, the
6699 BuildTimeHistogram entries in the state file, the "bw=" entries in
6700 the bandwidth authority file, and the process IDs passed to the
6701 __OwningControllerProcess option could all be specified in hex or
6702 octal as well as in decimal. This was not an intentional feature.
6703 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
6706 o Minor bugfixes (heartbeat):
6707 - If we fail to write a heartbeat message, schedule a retry for the
6708 minimum heartbeat interval number of seconds in the future. Fixes
6709 bug 19476; bugfix on 0.2.3.1-alpha.
6711 o Minor bugfixes (linux seccomp2 sandbox, logging):
6712 - Fix some messages on unexpected errors from the seccomp2 library.
6713 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
6715 o Minor bugfixes (logging):
6716 - Remove duplicate log messages regarding opening non-local
6717 SocksPorts upon parsing config and opening listeners at startup.
6718 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
6719 - Use a more comprehensible log message when telling the user
6720 they've excluded every running exit node. Fixes bug 7890; bugfix
6722 - When logging the number of descriptors we intend to download per
6723 directory request, do not log a number higher than then the number
6724 of descriptors we're fetching in total. Fixes bug 19648; bugfix
6726 - When warning about a directory owned by the wrong user, log the
6727 actual name of the user owning the directory. Previously, we'd log
6728 the name of the process owner twice. Fixes bug 23487; bugfix
6730 - The tor specification says hop counts are 1-based, so fix two log
6731 messages that mistakenly logged 0-based hop counts. Fixes bug
6732 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
6733 Credit to Xiaofan Li for reporting this issue.
6735 o Minor bugfixes (portability):
6736 - Stop using the PATH_MAX variable, which is not defined on GNU
6737 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
6739 o Minor bugfixes (relay):
6740 - When uploading our descriptor for the first time after startup,
6741 report the reason for uploading as "Tor just started" rather than
6742 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
6743 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6744 relays, to prevent spurious address resolutions and descriptor
6745 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6746 bugfix on in 0.2.8.1-alpha.
6748 o Minor bugfixes (tests):
6749 - Fix a broken unit test for the OutboundAddress option: the parsing
6750 function was never returning an error on failure. Fixes bug 23366;
6751 bugfix on 0.3.0.3-alpha.
6752 - Fix a signed-integer overflow in the unit tests for
6753 dir/download_status_random_backoff, which was untriggered until we
6754 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
6756 o Minor bugfixes (usability, control port):
6757 - Stop making an unnecessary routerlist check in NETINFO clock skew
6758 detection; this was preventing clients from reporting NETINFO clock
6759 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
6761 o Code simplification and refactoring:
6762 - Extract the code for handling newly-open channels into a separate
6763 function from the general code to handle channel state
6764 transitions. This change simplifies our callgraph, reducing the
6765 size of the largest strongly connected component by roughly a
6766 factor of two. Closes ticket 22608.
6767 - Remove dead code for largely unused statistics on the number of
6768 times we've attempted various public key operations. Fixes bug
6769 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
6770 - Remove several now-obsolete functions for asking about old
6771 variants directory authority status. Closes ticket 22311; patch
6773 - Remove some of the code that once supported "Named" and "Unnamed"
6774 routers. Authorities no longer vote for these flags. Closes
6776 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
6777 and old hidden services, to indicate that they aren't suitable for
6778 new protocols or formats. Closes ticket 23026.
6779 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
6780 22521. Patch from Neel Chauhan.
6781 - Split the enormous circuit_send_next_onion_skin() function into
6782 multiple subfunctions. Closes ticket 22804.
6783 - Split the portions of the buffer.c module that handle particular
6784 protocols into separate modules. Part of ticket 23149.
6785 - Use our test macros more consistently, to produce more useful
6786 error messages when our unit tests fail. Add coccinelle patches to
6787 allow us to re-check for test macro uses. Closes ticket 22497.
6789 o Deprecated features:
6790 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
6791 only applies to direct unencrypted HTTP connections to your
6792 directory server, which your Tor probably isn't using. Closes
6796 - Clarify in the manual that "Sandbox 1" is only supported on Linux
6797 kernels. Closes ticket 22677.
6798 - Document all values of PublishServerDescriptor in the manpage.
6799 Closes ticket 15645.
6800 - Improve the documentation for the directory port part of the
6801 DirAuthority line. Closes ticket 20152.
6802 - Restore documentation for the authorities' "approved-routers"
6803 file. Closes ticket 21148.
6806 - The AllowDotExit option has been removed as unsafe. It has been
6807 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
6808 - The ClientDNSRejectInternalAddresses flag can no longer be set on
6809 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
6810 Closes ticket 21031.
6811 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
6812 nobody was using it any longer. Closes ticket 22377.
6815 Changes in version 0.2.8.15 - 2017-09-18
6816 Tor 0.2.8.15 backports a collection of bugfixes from later
6819 Most significantly, it includes a fix for TROVE-2017-008, a
6820 security bug that affects hidden services running with the
6821 SafeLogging option disabled. For more information, see
6822 https://trac.torproject.org/projects/tor/ticket/23490
6824 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
6825 2018. We suggest that you upgrade to the latest stable release if
6826 possible. If you can't, we recommend that you upgrade at least to
6827 0.2.9, which will be supported until 2020.
6829 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6830 - Avoid an assertion failure bug affecting our implementation of
6831 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6832 handling of "0xx" differs from what we had expected. Fixes bug
6833 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6836 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6839 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6840 - Backport a fix for an "unused variable" warning that appeared
6841 in some versions of mingw. Fixes bug 22838; bugfix on
6844 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6845 - Fix a memset() off the end of an array when packing cells. This
6846 bug should be harmless in practice, since the corrupted bytes are
6847 still in the same structure, and are always padding bytes,
6848 ignored, or immediately overwritten, depending on compiler
6849 behavior. Nevertheless, because the memset()'s purpose is to make
6850 sure that any other cell-handling bugs can't expose bytes to the
6851 network, we need to fix it. Fixes bug 22737; bugfix on
6852 0.2.4.11-alpha. Fixes CID 1401591.
6854 o Build features (backport from 0.3.1.5-alpha):
6855 - Tor's repository now includes a Travis Continuous Integration (CI)
6856 configuration file (.travis.yml). This is meant to help new
6857 developers and contributors who fork Tor to a Github repository be
6858 better able to test their changes, and understand what we expect
6859 to pass. To use this new build feature, you must fork Tor to your
6860 Github account, then go into the "Integrations" menu in the
6861 repository settings for your fork and enable Travis, then push
6862 your changes. Closes ticket 22636.
6865 Changes in version 0.2.9.12 - 2017-09-18
6866 Tor 0.2.9.12 backports a collection of bugfixes from later
6869 Most significantly, it includes a fix for TROVE-2017-008, a
6870 security bug that affects hidden services running with the
6871 SafeLogging option disabled. For more information, see
6872 https://trac.torproject.org/projects/tor/ticket/23490
6874 o Major features (security, backport from 0.3.0.2-alpha):
6875 - Change the algorithm used to decide DNS TTLs on client and server
6876 side, to better resist DNS-based correlation attacks like the
6877 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
6878 Feamster. Now relays only return one of two possible DNS TTL
6879 values, and clients are willing to believe DNS TTL values up to 3
6880 hours long. Closes ticket 19769.
6882 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
6883 - Fix a rare crash when sending a begin cell on a circuit whose
6884 linked directory connection had already been closed. Fixes bug
6885 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
6887 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
6888 - Fix a bug that prevented exit nodes from caching DNS records for
6889 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
6891 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
6892 - Fix a typo that had prevented TPROXY-based transparent proxying
6893 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6894 Patch from "d4fq0fQAgoJ".
6896 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6897 - Avoid an assertion failure bug affecting our implementation of
6898 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6899 handling of "0xx" differs from what we had expected. Fixes bug
6900 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6902 o Minor features (code style, backport from 0.3.1.3-alpha):
6903 - Add "Falls through" comments to our codebase, in order to silence
6904 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6905 Stieger. Closes ticket 22446.
6907 o Minor features (geoip):
6908 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6911 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
6912 - Roll over monthly accounting at the configured hour and minute,
6913 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6914 Found by Andrey Karpov with PVS-Studio.
6916 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
6917 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
6918 bugfix on 0.2.8.1-alpha.
6919 - Fix warnings when building with libscrypt and openssl scrypt support
6920 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
6921 - When building with certain versions the mingw C header files, avoid
6922 float-conversion warnings when calling the C functions isfinite(),
6923 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
6925 o Minor bugfixes (compilation, backport from 0.3.1.7):
6926 - Avoid compiler warnings in the unit tests for running tor_sscanf()
6927 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6929 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6930 - Backport a fix for an "unused variable" warning that appeared
6931 in some versions of mingw. Fixes bug 22838; bugfix on
6934 o Minor bugfixes (controller, backport from 0.3.1.7):
6935 - Do not crash when receiving a HSPOST command with an empty body.
6936 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6937 - Do not crash when receiving a POSTDESCRIPTOR command with an
6938 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6940 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
6941 - Avoid Coverity build warnings related to our BUG() macro. By
6942 default, Coverity treats BUG() as the Linux kernel does: an
6943 instant abort(). We need to override that so our BUG() macro
6944 doesn't prevent Coverity from analyzing functions that use it.
6945 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
6947 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6948 - Fix a memset() off the end of an array when packing cells. This
6949 bug should be harmless in practice, since the corrupted bytes are
6950 still in the same structure, and are always padding bytes,
6951 ignored, or immediately overwritten, depending on compiler
6952 behavior. Nevertheless, because the memset()'s purpose is to make
6953 sure that any other cell-handling bugs can't expose bytes to the
6954 network, we need to fix it. Fixes bug 22737; bugfix on
6955 0.2.4.11-alpha. Fixes CID 1401591.
6957 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
6958 - When setting the maximum number of connections allowed by the OS,
6959 always allow some extra file descriptors for other files. Fixes
6960 bug 22797; bugfix on 0.2.0.10-alpha.
6962 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
6963 - Avoid a sandbox failure when trying to re-bind to a socket and
6964 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
6966 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
6967 - Permit the fchmod system call, to avoid crashing on startup when
6968 starting with the seccomp2 sandbox and an unexpected set of
6969 permissions on the data directory or its contents. Fixes bug
6970 22516; bugfix on 0.2.5.4-alpha.
6972 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
6973 - Avoid a double-marked-circuit warning that could happen when we
6974 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
6977 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
6978 - Reject version numbers with non-numeric prefixes (such as +, -, or
6979 whitespace). Disallowing whitespace prevents differential version
6980 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6981 and part of 21508; bugfix on 0.0.8pre1.
6983 o Build features (backport from 0.3.1.5-alpha):
6984 - Tor's repository now includes a Travis Continuous Integration (CI)
6985 configuration file (.travis.yml). This is meant to help new
6986 developers and contributors who fork Tor to a Github repository be
6987 better able to test their changes, and understand what we expect
6988 to pass. To use this new build feature, you must fork Tor to your
6989 Github account, then go into the "Integrations" menu in the
6990 repository settings for your fork and enable Travis, then push
6991 your changes. Closes ticket 22636.
6994 Changes in version 0.3.0.11 - 2017-09-18
6995 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
6998 Most significantly, it includes a fix for TROVE-2017-008, a
6999 security bug that affects hidden services running with the
7000 SafeLogging option disabled. For more information, see
7001 https://trac.torproject.org/projects/tor/ticket/23490
7003 o Minor features (code style, backport from 0.3.1.7):
7004 - Add "Falls through" comments to our codebase, in order to silence
7005 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7006 Stieger. Closes ticket 22446.
7009 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7012 o Minor bugfixes (compilation, backport from 0.3.1.7):
7013 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7014 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7016 o Minor bugfixes (controller, backport from 0.3.1.7):
7017 - Do not crash when receiving a HSPOST command with an empty body.
7018 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7019 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7020 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7022 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7023 - When setting the maximum number of connections allowed by the OS,
7024 always allow some extra file descriptors for other files. Fixes
7025 bug 22797; bugfix on 0.2.0.10-alpha.
7027 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
7028 - Remove a forgotten debugging message when an introduction point
7029 successfully establishes a hidden service prop224 circuit with
7031 - Change three other log_warn() for an introduction point to
7032 protocol warnings, because they can be failure from the network
7033 and are not relevant to the operator. Fixes bug 23078; bugfix on
7034 0.3.0.1-alpha and 0.3.0.2-alpha.
7037 Changes in version 0.3.1.7 - 2017-09-18
7038 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
7040 With the 0.3.1 series, Tor now serves and downloads directory
7041 information in more compact formats, to save on bandwidth overhead. It
7042 also contains a new padding system to resist netflow-based traffic
7043 analysis, and experimental support for building parts of Tor in Rust
7044 (though no parts of Tor are in Rust yet). There are also numerous
7045 small features, bugfixes on earlier release series, and groundwork for
7046 the hidden services revamp of 0.3.2.
7048 This release also includes a fix for TROVE-2017-008, a security bug
7049 that affects hidden services running with the SafeLogging option
7050 disabled. For more information, see
7051 https://trac.torproject.org/projects/tor/ticket/23490
7053 Per our stable release policy, we plan to support each stable release
7054 series for at least the next nine months, or for three months after
7055 the first stable release of the next series: whichever is longer. If
7056 you need a release with long-term support, we recommend that you stay
7057 with the 0.2.9 series.
7059 Below is a list of the changes since 0.3.1.6-rc. For a list of all
7060 changes since 0.3.0, see the ReleaseNotes file.
7062 o Major bugfixes (security, hidden services, loggging):
7063 - Fix a bug where we could log uninitialized stack when a certain
7064 hidden service error occurred while SafeLogging was disabled.
7065 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
7066 TROVE-2017-008 and CVE-2017-0380.
7068 o Minor features (defensive programming):
7069 - Create a pair of consensus parameters, nf_pad_tor2web and
7070 nf_pad_single_onion, to disable netflow padding in the consensus
7071 for non-anonymous connections in case the overhead is high. Closes
7074 o Minor features (diagnostic):
7075 - Add a stack trace to the bug warnings that can be logged when
7076 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
7077 attempt for bug 23105.
7079 o Minor features (geoip):
7080 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7083 o Minor bugfixes (compilation):
7084 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7085 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7087 o Minor bugfixes (controller):
7088 - Do not crash when receiving a HSPOST command with an empty body.
7089 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7090 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7091 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7093 o Minor bugfixes (relay):
7094 - Inform the geoip and rephist modules about all requests, even on
7095 relays that are only fetching microdescriptors. Fixes a bug
7096 related to 21585; bugfix on 0.3.0.1-alpha.
7098 o Minor bugfixes (unit tests):
7099 - Fix a channelpadding unit test failure on slow systems by using
7100 mocked time instead of actual time. Fixes bug 23077; bugfix
7104 Changes in version 0.3.1.6-rc - 2017-09-05
7105 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
7106 release series, including a bug that produced weird behavior on
7107 Windows directory caches.
7109 This is the first release candidate in the Tor 0.3.1 series. If we
7110 find no new bugs or regressions here, the first stable 0.3.1 release
7111 will be nearly identical to it.
7113 o Major bugfixes (windows, directory cache):
7114 - On Windows, do not try to delete cached consensus documents and
7115 diffs before they are unmapped from memory--Windows won't allow
7116 that. Instead, allow the consensus cache directory to grow larger,
7117 to hold files that might need to stay around longer. Fixes bug
7118 22752; bugfix on 0.3.1.1-alpha.
7120 o Minor features (directory authority):
7121 - Improve the message that authorities report to relays that present
7122 RSA/Ed25519 keypairs that conflict with previously pinned keys.
7123 Closes ticket 22348.
7125 o Minor features (geoip):
7126 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
7129 o Minor features (testing):
7130 - Add more tests for compression backend initialization. Closes
7133 o Minor bugfixes (directory cache):
7134 - Fix a memory leak when recovering space in the consensus cache.
7135 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
7137 o Minor bugfixes (hidden service):
7138 - Increase the number of circuits that a service is allowed to
7139 open over a specific period of time. The value was lower than it
7140 should be (8 vs 12) in the normal case of 3 introduction points.
7141 Fixes bug 22159; bugfix on 0.3.0.5-rc.
7142 - Fix a BUG warning during HSv3 descriptor decoding that could be
7143 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
7144 on 0.3.0.1-alpha. Bug found by "haxxpop".
7145 - Rate-limit the log messages if we exceed the maximum number of
7146 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
7148 o Minor bugfixes (logging, relay):
7149 - Remove a forgotten debugging message when an introduction point
7150 successfully establishes a hidden service prop224 circuit with
7152 - Change three other log_warn() for an introduction point to
7153 protocol warnings, because they can be failure from the network
7154 and are not relevant to the operator. Fixes bug 23078; bugfix on
7155 0.3.0.1-alpha and 0.3.0.2-alpha.
7157 o Minor bugfixes (relay):
7158 - When a relay is not running as a directory cache, it will no
7159 longer generate compressed consensuses and consensus diff
7160 information. Previously, this was a waste of disk and CPU. Fixes
7161 bug 23275; bugfix on 0.3.1.1-alpha.
7163 o Minor bugfixes (robustness, error handling):
7164 - Improve our handling of the cases where OpenSSL encounters a
7165 memory error while encoding keys and certificates. We haven't
7166 observed these errors in the wild, but if they do happen, we now
7167 detect and respond better. Fixes bug 19418; bugfix on all versions
7168 of Tor. Reported by Guido Vranken.
7170 o Minor bugfixes (stability):
7171 - Avoid crashing on a double-free when unable to load or process an
7172 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
7173 with the clang static analyzer.
7175 o Minor bugfixes (testing):
7176 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
7177 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
7178 - Port the hs_ntor handshake test to work correctly with recent
7179 versions of the pysha3 module. Fixes bug 23071; bugfix
7182 o Minor bugfixes (Windows service):
7183 - When running as a Windows service, set the ID of the main thread
7184 correctly. Failure to do so made us fail to send log messages to
7185 the controller in 0.2.1.16-rc, slowed down controller event
7186 delivery in 0.2.7.3-rc and later, and crash with an assertion
7187 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7188 Patch and diagnosis from "Vort".
7191 Changes in version 0.3.0.10 - 2017-08-02
7192 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
7193 from the current Tor alpha series. OpenBSD users and TPROXY users
7194 should upgrade; others are probably okay sticking with 0.3.0.9.
7196 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
7197 - Tor's repository now includes a Travis Continuous Integration (CI)
7198 configuration file (.travis.yml). This is meant to help new
7199 developers and contributors who fork Tor to a Github repository be
7200 better able to test their changes, and understand what we expect
7201 to pass. To use this new build feature, you must fork Tor to your
7202 Github account, then go into the "Integrations" menu in the
7203 repository settings for your fork and enable Travis, then push
7204 your changes. Closes ticket 22636.
7206 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7207 - Fix a typo that had prevented TPROXY-based transparent proxying
7208 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7209 Patch from "d4fq0fQAgoJ".
7211 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7212 - Avoid an assertion failure bug affecting our implementation of
7213 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7214 handling of "0xbar" differs from what we had expected. Fixes bug
7215 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7217 o Minor features (backport from 0.3.1.5-alpha):
7218 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
7221 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
7222 - Roll over monthly accounting at the configured hour and minute,
7223 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7224 Found by Andrey Karpov with PVS-Studio.
7226 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
7227 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7228 bugfix on 0.2.8.1-alpha.
7229 - Fix warnings when building with libscrypt and openssl scrypt
7230 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7231 - When building with certain versions of the mingw C header files,
7232 avoid float-conversion warnings when calling the C functions
7233 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
7236 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7237 - Backport a fix for an "unused variable" warning that appeared
7238 in some versions of mingw. Fixes bug 22838; bugfix on
7241 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
7242 - Avoid Coverity build warnings related to our BUG() macro. By
7243 default, Coverity treats BUG() as the Linux kernel does: an
7244 instant abort(). We need to override that so our BUG() macro
7245 doesn't prevent Coverity from analyzing functions that use it.
7246 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7248 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
7249 - When rejecting a router descriptor for running an obsolete version
7250 of Tor without ntor support, warn about the obsolete tor version,
7251 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
7253 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
7254 - Avoid a sandbox failure when trying to re-bind to a socket and
7255 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7257 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
7258 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
7259 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
7262 Changes in version 0.3.1.5-alpha - 2017-08-01
7263 Tor 0.3.1.5-alpha improves the performance of consensus diff
7264 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
7265 several other bugs. If no serious bugs are found in this version, the
7266 next version will be a release candidate.
7268 This release also marks the end of support for the Tor 0.2.4.x,
7269 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
7270 further bug or security fixes. Anyone still running or distributing
7271 one of those versions should upgrade.
7273 o Major features (build system, continuous integration):
7274 - Tor's repository now includes a Travis Continuous Integration (CI)
7275 configuration file (.travis.yml). This is meant to help new
7276 developers and contributors who fork Tor to a Github repository be
7277 better able to test their changes, and understand what we expect
7278 to pass. To use this new build feature, you must fork Tor to your
7279 Github account, then go into the "Integrations" menu in the
7280 repository settings for your fork and enable Travis, then push
7281 your changes. Closes ticket 22636.
7283 o Major bugfixes (openbsd, denial-of-service):
7284 - Avoid an assertion failure bug affecting our implementation of
7285 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7286 handling of "0xbar" differs from what we had expected. Fixes bug
7287 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7289 o Major bugfixes (relay, performance):
7290 - Perform circuit handshake operations at a higher priority than we
7291 use for consensus diff creation and compression. This should
7292 prevent circuits from starving when a relay or bridge receives a
7293 new consensus, especially on lower-powered machines. Fixes bug
7294 22883; bugfix on 0.3.1.1-alpha.
7296 o Minor features (bridge authority):
7297 - Add "fingerprint" lines to the networkstatus-bridges file produced
7298 by bridge authorities. Closes ticket 22207.
7300 o Minor features (directory cache, consensus diff):
7301 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
7302 operators with low-resource environments to adjust the number of
7303 consensuses they'll store and generate diffs from. Most cache
7304 operators should leave it unchanged. Helps to work around
7307 o Minor features (geoip):
7308 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
7311 o Minor features (relay, performance):
7312 - Always start relays with at least two worker threads, to prevent
7313 priority inversion on slow tasks. Part of the fix for bug 22883.
7314 - Allow background work to be queued with different priorities, so
7315 that a big pile of slow low-priority jobs will not starve out
7316 higher priority jobs. This lays the groundwork for a fix for
7319 o Minor bugfixes (build system, rust):
7320 - Fix a problem where Rust toolchains were not being found when
7321 building without --enable-cargo-online-mode, due to setting the
7322 $HOME environment variable instead of $CARGO_HOME. Fixes bug
7323 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
7325 o Minor bugfixes (compatibility, zstd):
7326 - Write zstd epilogues correctly when the epilogue requires
7327 reallocation of the output buffer, even with zstd 1.3.0.
7328 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
7329 22927; bugfix on 0.3.1.1-alpha.
7331 o Minor bugfixes (compilation warnings):
7332 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
7333 22915; bugfix on 0.2.8.1-alpha.
7334 - Fix warnings when building with libscrypt and openssl scrypt
7335 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7336 - Compile correctly when both openssl 1.1.0 and libscrypt are
7337 detected. Previously this would cause an error. Fixes bug 22892;
7338 bugfix on 0.3.1.1-alpha.
7339 - When building with certain versions of the mingw C header files,
7340 avoid float-conversion warnings when calling the C functions
7341 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
7344 o Minor bugfixes (coverity build support):
7345 - Avoid Coverity build warnings related to our BUG() macro. By
7346 default, Coverity treats BUG() as the Linux kernel does: an
7347 instant abort(). We need to override that so our BUG() macro
7348 doesn't prevent Coverity from analyzing functions that use it.
7349 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7351 o Minor bugfixes (directory authority):
7352 - When a directory authority rejects a descriptor or extrainfo with
7353 a given digest, mark that digest as undownloadable, so that we do
7354 not attempt to download it again over and over. We previously
7355 tried to avoid downloading such descriptors by other means, but we
7356 didn't notice if we accidentally downloaded one anyway. This
7357 behavior became problematic in 0.2.7.2-alpha, when authorities
7358 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7361 o Minor bugfixes (error reporting, windows):
7362 - When formatting Windows error messages, use the English format to
7363 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
7366 o Minor bugfixes (file limits, osx):
7367 - When setting the maximum number of connections allowed by the OS,
7368 always allow some extra file descriptors for other files. Fixes
7369 bug 22797; bugfix on 0.2.0.10-alpha.
7371 o Minor bugfixes (linux seccomp2 sandbox):
7372 - Avoid a sandbox failure when trying to re-bind to a socket and
7373 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7375 o Minor bugfixes (memory leaks):
7376 - Fix a small memory leak when validating a configuration that uses
7377 two or more AF_UNIX sockets for the same port type. Fixes bug
7378 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
7380 o Minor bugfixes (unit tests):
7381 - test_consdiff_base64cmp would fail on OS X because while OS X
7382 follows the standard of (less than zero/zero/greater than zero),
7383 it doesn't follow the convention of (-1/0/+1). Make the test
7384 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
7385 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
7386 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
7389 Changes in version 0.3.1.4-alpha - 2017-06-29
7390 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
7391 to use a guard that was in the same network family as a chosen exit
7392 relay. This is a security regression; all clients running earlier
7393 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
7396 This release also fixes several other bugs introduced in 0.3.0.x
7397 and 0.3.1.x, including others that can affect bandwidth usage
7401 - To build with zstd and lzma support, Tor now requires the
7402 pkg-config tool at build time. (This requirement was new in
7403 0.3.1.1-alpha, but was not noted at the time. Noting it here to
7404 close ticket 22623.)
7406 o Major bugfixes (path selection, security):
7407 - When choosing which guard to use for a circuit, avoid the exit's
7408 family along with the exit itself. Previously, the new guard
7409 selection logic avoided the exit, but did not consider its family.
7410 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
7411 006 and CVE-2017-0377.
7413 o Major bugfixes (compression, zstd):
7414 - Correctly detect a full buffer when decompressing a large zstd-
7415 compressed input. Previously, we would sometimes treat a full
7416 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
7418 o Major bugfixes (directory protocol):
7419 - Ensure that we send "304 Not modified" as HTTP status code when a
7420 client is attempting to fetch a consensus or consensus diff, and
7421 the best one we can send them is one they already have. Fixes bug
7422 22702; bugfix on 0.3.1.1-alpha.
7424 o Major bugfixes (entry guards):
7425 - When starting with an old consensus, do not add new entry guards
7426 unless the consensus is "reasonably live" (under 1 day old). Fixes
7427 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
7429 o Minor features (bug mitigation, diagnostics, logging):
7430 - Avoid an assertion failure, and log a better error message, when
7431 unable to remove a file from the consensus cache on Windows.
7432 Attempts to mitigate and diagnose bug 22752.
7434 o Minor features (geoip):
7435 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
7438 o Minor bugfixes (compression):
7439 - When compressing or decompressing a buffer, check for a failure to
7440 create a compression object. Fixes bug 22626; bugfix
7442 - When decompressing a buffer, check for extra data after the end of
7443 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
7444 - When decompressing an object received over an anonymous directory
7445 connection, if we have already decompressed it using an acceptable
7446 compression method, do not reject it for looking like an
7447 unacceptable compression method. Fixes part of bug 22670; bugfix
7449 - When serving directory votes compressed with zlib, do not claim to
7450 have compressed them with zstd. Fixes bug 22669; bugfix
7452 - When spooling compressed data to an output buffer, don't try to
7453 spool more data when there is no more data to spool and we are not
7454 trying to flush the input. Previously, we would sometimes launch
7455 compression requests with nothing to do, which interferes with our
7456 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
7458 o Minor bugfixes (defensive programming):
7459 - Detect and break out of infinite loops in our compression code. We
7460 don't think that any such loops exist now, but it's best to be
7461 safe. Closes ticket 22672.
7462 - Fix a memset() off the end of an array when packing cells. This
7463 bug should be harmless in practice, since the corrupted bytes are
7464 still in the same structure, and are always padding bytes,
7465 ignored, or immediately overwritten, depending on compiler
7466 behavior. Nevertheless, because the memset()'s purpose is to make
7467 sure that any other cell-handling bugs can't expose bytes to the
7468 network, we need to fix it. Fixes bug 22737; bugfix on
7469 0.2.4.11-alpha. Fixes CID 1401591.
7471 o Minor bugfixes (linux seccomp2 sandbox):
7472 - Permit the fchmod system call, to avoid crashing on startup when
7473 starting with the seccomp2 sandbox and an unexpected set of
7474 permissions on the data directory or its contents. Fixes bug
7475 22516; bugfix on 0.2.5.4-alpha.
7476 - Fix a crash in the LZMA module, when the sandbox was enabled, and
7477 liblzma would allocate more than 16 MB of memory. We solve this by
7478 bumping the mprotect() limit in the sandbox module from 16 MB to
7479 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
7481 o Minor bugfixes (logging):
7482 - When decompressing, do not warn if we fail to decompress using a
7483 compression method that we merely guessed. Fixes part of bug
7484 22670; bugfix on 0.1.1.14-alpha.
7485 - When decompressing, treat mismatch between content-encoding and
7486 actual compression type as a protocol warning. Fixes part of bug
7487 22670; bugfix on 0.1.1.9-alpha.
7488 - Downgrade "assigned_to_cpuworker failed" message to info-level
7489 severity. In every case that can reach it, either a better warning
7490 has already been logged, or no warning is warranted. Fixes bug
7491 22356; bugfix on 0.2.6.3-alpha.
7492 - Demote a warn that was caused by libevent delays to info if
7493 netflow padding is less than 4.5 seconds late, or to notice
7494 if it is more (4.5 seconds is the amount of time that a netflow
7495 record might be emitted after, if we chose the maximum timeout).
7496 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
7498 o Minor bugfixes (process behavior):
7499 - When exiting because of an error, always exit with a nonzero exit
7500 status. Previously, we would fail to report an error in our exit
7501 status in cases related to __OwningControllerProcess failure,
7502 lockfile contention, and Ed25519 key initialization. Fixes bug
7503 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
7504 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
7508 - Add a manpage description for the key-pinning-journal file. Closes
7510 - Correctly note that bandwidth accounting values are stored in the
7511 state file, and the bw_accounting file is now obsolete. Closes
7513 - Document more of the files in the Tor data directory, including
7514 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
7515 approved-routers, sr-random, and diff-cache. Found while fixing
7519 Changes in version 0.3.0.9 - 2017-06-29
7520 Tor 0.3.0.9 fixes a path selection bug that would allow a client
7521 to use a guard that was in the same network family as a chosen exit
7522 relay. This is a security regression; all clients running earlier
7523 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
7526 This release also backports several other bugfixes from the 0.3.1.x
7529 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
7530 - When choosing which guard to use for a circuit, avoid the exit's
7531 family along with the exit itself. Previously, the new guard
7532 selection logic avoided the exit, but did not consider its family.
7533 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
7534 006 and CVE-2017-0377.
7536 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
7537 - Don't block bootstrapping when a primary bridge is offline and we
7538 can't get its descriptor. Fixes bug 22325; fixes one case of bug
7539 21969; bugfix on 0.3.0.3-alpha.
7541 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
7542 - When starting with an old consensus, do not add new entry guards
7543 unless the consensus is "reasonably live" (under 1 day old). Fixes
7544 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
7546 o Minor features (geoip):
7547 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
7550 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
7551 - Reject version numbers with non-numeric prefixes (such as +, -, or
7552 whitespace). Disallowing whitespace prevents differential version
7553 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7554 and part of 21508; bugfix on 0.0.8pre1.
7556 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
7557 - Permit the fchmod system call, to avoid crashing on startup when
7558 starting with the seccomp2 sandbox and an unexpected set of
7559 permissions on the data directory or its contents. Fixes bug
7560 22516; bugfix on 0.2.5.4-alpha.
7562 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
7563 - Fix a memset() off the end of an array when packing cells. This
7564 bug should be harmless in practice, since the corrupted bytes are
7565 still in the same structure, and are always padding bytes,
7566 ignored, or immediately overwritten, depending on compiler
7567 behavior. Nevertheless, because the memset()'s purpose is to make
7568 sure that any other cell-handling bugs can't expose bytes to the
7569 network, we need to fix it. Fixes bug 22737; bugfix on
7570 0.2.4.11-alpha. Fixes CID 1401591.
7573 Changes in version 0.3.1.3-alpha - 2017-06-08
7574 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
7575 remotely crash a hidden service with an assertion failure. Anyone
7576 running a hidden service should upgrade to this version, or to some
7577 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
7579 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
7580 that sometimes made relays unreliable, as well as several other
7581 bugfixes described below.
7583 o Major bugfixes (hidden service, relay, security):
7584 - Fix a remotely triggerable assertion failure when a hidden service
7585 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
7586 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
7587 - Fix a remotely triggerable assertion failure caused by receiving a
7588 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7589 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7592 o Major bugfixes (relay, link handshake):
7593 - When performing the v3 link handshake on a TLS connection, report
7594 that we have the x509 certificate that we actually used on that
7595 connection, even if we have changed certificates since that
7596 connection was first opened. Previously, we would claim to have
7597 used our most recent x509 link certificate, which would sometimes
7598 make the link handshake fail. Fixes one case of bug 22460; bugfix
7601 o Major bugfixes (relays, key management):
7602 - Regenerate link and authentication certificates whenever the key
7603 that signs them changes; also, regenerate link certificates
7604 whenever the signed key changes. Previously, these processes were
7605 only weakly coupled, and we relays could (for minutes to hours)
7606 wind up with an inconsistent set of keys and certificates, which
7607 other relays would not accept. Fixes two cases of bug 22460;
7608 bugfix on 0.3.0.1-alpha.
7609 - When sending an Ed25519 signing->link certificate in a CERTS cell,
7610 send the certificate that matches the x509 certificate that we
7611 used on the TLS connection. Previously, there was a race condition
7612 if the TLS context rotated after we began the TLS handshake but
7613 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
7616 o Major bugfixes (torrc, crash):
7617 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
7618 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
7620 o Minor features (code style):
7621 - Add "Falls through" comments to our codebase, in order to silence
7622 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7623 Stieger. Closes ticket 22446.
7625 o Minor features (diagnostic):
7626 - Add logging messages to try to diagnose a rare bug that seems to
7627 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
7628 think this is happening because of incorrect system clocks, but
7629 we'd like to know for certain. Diagnostic for bug 22466.
7631 o Minor bugfixes (correctness):
7632 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7633 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7635 o Minor bugfixes (directory protocol):
7636 - Check for libzstd >= 1.1, because older versions lack the
7637 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
7639 o Minor bugfixes (link handshake):
7640 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
7641 months, and regenerate it when it is within one month of expiring.
7642 Previously, we had generated this certificate at startup with a
7643 ten-year lifetime, but that could lead to weird behavior when Tor
7644 was started with a grossly inaccurate clock. Mitigates bug 22466;
7645 mitigation on 0.3.0.1-alpha.
7647 o Minor bugfixes (storage directories):
7648 - Always check for underflows in the cached storage directory usage.
7649 If the usage does underflow, re-calculate it. Also, avoid a
7650 separate underflow when the usage is not known. Fixes bug 22424;
7651 bugfix on 0.3.1.1-alpha.
7653 o Minor bugfixes (unit tests):
7654 - The unit tests now pass on systems where localhost is misconfigured
7655 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
7659 - Clarify the manpage for the (deprecated) torify script. Closes
7662 Changes in version 0.3.0.8 - 2017-06-08
7663 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
7664 remotely crash a hidden service with an assertion failure. Anyone
7665 running a hidden service should upgrade to this version, or to some
7666 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
7668 Tor 0.3.0.8 also includes fixes for several key management bugs
7669 that sometimes made relays unreliable, as well as several other
7670 bugfixes described below.
7672 o Major bugfixes (hidden service, relay, security, backport
7673 from 0.3.1.3-alpha):
7674 - Fix a remotely triggerable assertion failure when a hidden service
7675 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
7676 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
7677 - Fix a remotely triggerable assertion failure caused by receiving a
7678 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7679 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7682 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
7683 - When performing the v3 link handshake on a TLS connection, report
7684 that we have the x509 certificate that we actually used on that
7685 connection, even if we have changed certificates since that
7686 connection was first opened. Previously, we would claim to have
7687 used our most recent x509 link certificate, which would sometimes
7688 make the link handshake fail. Fixes one case of bug 22460; bugfix
7691 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
7692 - Regenerate link and authentication certificates whenever the key
7693 that signs them changes; also, regenerate link certificates
7694 whenever the signed key changes. Previously, these processes were
7695 only weakly coupled, and we relays could (for minutes to hours)
7696 wind up with an inconsistent set of keys and certificates, which
7697 other relays would not accept. Fixes two cases of bug 22460;
7698 bugfix on 0.3.0.1-alpha.
7699 - When sending an Ed25519 signing->link certificate in a CERTS cell,
7700 send the certificate that matches the x509 certificate that we
7701 used on the TLS connection. Previously, there was a race condition
7702 if the TLS context rotated after we began the TLS handshake but
7703 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
7706 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
7707 - Stop rejecting v3 hidden service descriptors because their size
7708 did not match an old padding rule. Fixes bug 22447; bugfix on
7711 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7712 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7713 December 2016 (of which ~126 were still functional) with a list of
7714 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7715 2017. Resolves ticket 21564.
7717 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
7718 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
7719 bug 22252; bugfix on 0.2.9.3-alpha.
7721 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
7722 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7723 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7725 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
7726 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
7727 months, and regenerate it when it is within one month of expiring.
7728 Previously, we had generated this certificate at startup with a
7729 ten-year lifetime, but that could lead to weird behavior when Tor
7730 was started with a grossly inaccurate clock. Mitigates bug 22466;
7731 mitigation on 0.3.0.1-alpha.
7733 o Minor bugfixes (memory leak, directory authority, backport from
7735 - When directory authorities reject a router descriptor due to
7736 keypinning, free the router descriptor rather than leaking the
7737 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7740 Changes in version 0.2.9.11 - 2017-06-08
7741 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
7742 remotely crash a hidden service with an assertion failure. Anyone
7743 running a hidden service should upgrade to this version, or to some
7744 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7745 are not affected by TROVE-2017-004.)
7747 Tor 0.2.9.11 also backports fixes for several key management bugs
7748 that sometimes made relays unreliable, as well as several other
7749 bugfixes described below.
7751 o Major bugfixes (hidden service, relay, security, backport
7752 from 0.3.1.3-alpha):
7753 - Fix a remotely triggerable assertion failure caused by receiving a
7754 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7755 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7758 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
7759 - When performing the v3 link handshake on a TLS connection, report
7760 that we have the x509 certificate that we actually used on that
7761 connection, even if we have changed certificates since that
7762 connection was first opened. Previously, we would claim to have
7763 used our most recent x509 link certificate, which would sometimes
7764 make the link handshake fail. Fixes one case of bug 22460; bugfix
7767 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7768 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7769 December 2016 (of which ~126 were still functional) with a list of
7770 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7771 2017. Resolves ticket 21564.
7773 o Minor features (future-proofing, backport from 0.3.0.7):
7774 - Tor no longer refuses to download microdescriptors or descriptors if
7775 they are listed as "published in the future". This change will
7776 eventually allow us to stop listing meaningful "published" dates
7777 in microdescriptor consensuses, and thereby allow us to reduce the
7778 resources required to download consensus diffs by over 50%.
7779 Implements part of ticket 21642; implements part of proposal 275.
7781 o Minor features (directory authorities, backport from 0.3.0.4-rc)
7782 - Directory authorities now reject relays running versions
7783 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
7784 suffer from bug 20499 and don't keep their consensus cache
7785 up-to-date. Resolves ticket 20509.
7787 o Minor features (geoip):
7788 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7791 o Minor bugfixes (control port, backport from 0.3.0.6):
7792 - The GETINFO extra-info/digest/<digest> command was broken because
7793 of a wrong base16 decode return value check, introduced when
7794 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
7796 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
7797 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7798 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7800 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
7801 - The getpid() system call is now permitted under the Linux seccomp2
7802 sandbox, to avoid crashing with versions of OpenSSL (and other
7803 libraries) that attempt to learn the process's PID by using the
7804 syscall rather than the VDSO code. Fixes bug 21943; bugfix
7807 o Minor bugfixes (memory leak, directory authority, backport
7808 from 0.3.1.2-alpha):
7809 - When directory authorities reject a router descriptor due to
7810 keypinning, free the router descriptor rather than leaking the
7811 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7813 Changes in version 0.2.8.14 - 2017-06-08
7814 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
7815 remotely crash a hidden service with an assertion failure. Anyone
7816 running a hidden service should upgrade to this version, or to some
7817 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7818 are not affected by TROVE-2017-004.)
7820 o Major bugfixes (hidden service, relay, security):
7821 - Fix a remotely triggerable assertion failure caused by receiving a
7822 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7823 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7826 o Minor features (geoip):
7827 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7830 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7831 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7832 December 2016 (of which ~126 were still functional) with a list of
7833 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7834 2017. Resolves ticket 21564.
7836 o Minor bugfixes (correctness):
7837 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7838 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7840 Changes in version 0.2.7.8 - 2017-06-08
7841 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
7842 remotely crash a hidden service with an assertion failure. Anyone
7843 running a hidden service should upgrade to this version, or to some
7844 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7845 are not affected by TROVE-2017-004.)
7847 o Major bugfixes (hidden service, relay, security):
7848 - Fix a remotely triggerable assertion failure caused by receiving a
7849 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7850 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7853 o Minor features (geoip):
7854 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7857 o Minor bugfixes (correctness):
7858 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7859 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7862 Changes in version 0.2.6.12 - 2017-06-08
7863 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
7864 remotely crash a hidden service with an assertion failure. Anyone
7865 running a hidden service should upgrade to this version, or to some
7866 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7867 are not affected by TROVE-2017-004.)
7869 o Major bugfixes (hidden service, relay, security):
7870 - Fix a remotely triggerable assertion failure caused by receiving a
7871 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7872 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7875 o Minor features (geoip):
7876 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7879 o Minor bugfixes (correctness):
7880 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7881 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7883 Changes in version 0.2.5.14 - 2017-06-08
7884 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
7885 remotely crash a hidden service with an assertion failure. Anyone
7886 running a hidden service should upgrade to this version, or to some
7887 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7888 are not affected by TROVE-2017-004.)
7890 o Major bugfixes (hidden service, relay, security):
7891 - Fix a remotely triggerable assertion failure caused by receiving a
7892 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7893 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7896 o Minor features (geoip):
7897 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7900 o Minor bugfixes (correctness):
7901 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7902 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7904 Changes in version 0.2.4.29 - 2017-06-08
7905 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
7906 remotely crash a hidden service with an assertion failure. Anyone
7907 running a hidden service should upgrade to this version, or to some
7908 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7909 are not affected by TROVE-2017-004.)
7911 o Major bugfixes (hidden service, relay, security):
7912 - Fix a remotely triggerable assertion failure caused by receiving a
7913 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7914 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7917 o Minor features (geoip):
7918 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7921 o Minor bugfixes (correctness):
7922 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7923 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7926 Changes in version 0.3.1.2-alpha - 2017-05-26
7927 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
7928 fixes a few bugs found while testing 0.3.1.1-alpha, including a
7929 memory corruption bug that affected relay stability.
7931 o Major bugfixes (crash, relay):
7932 - Fix a memory-corruption bug in relays that set MyFamily.
7933 Previously, they would double-free MyFamily elements when making
7934 the next descriptor or when changing their configuration. Fixes
7935 bug 22368; bugfix on 0.3.1.1-alpha.
7937 o Minor bugfixes (logging):
7938 - Log a better message when a directory authority replies to an
7939 upload with an unexpected status code. Fixes bug 11121; bugfix
7942 o Minor bugfixes (memory leak, directory authority):
7943 - When directory authorities reject a router descriptor due to
7944 keypinning, free the router descriptor rather than leaking the
7945 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7948 Changes in version 0.3.1.1-alpha - 2017-05-22
7949 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
7950 reduces the bandwidth usage for Tor's directory protocol, adds some
7951 basic padding to resist netflow-based traffic analysis and to serve as
7952 the basis of other padding in the future, and adds rust support to the
7955 It also contains numerous other small features and improvements to
7956 security, correctness, and performance.
7958 Below are the changes since 0.3.0.7.
7960 o Major features (directory protocol):
7961 - Tor relays and authorities can now serve clients an abbreviated
7962 version of the consensus document, containing only the changes
7963 since an older consensus document that the client holds. Clients
7964 now request these documents when available. When both client and
7965 server use this new protocol, they will use far less bandwidth (up
7966 to 94% less) to keep the client's consensus up-to-date. Implements
7967 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
7968 - Tor can now compress directory traffic with lzma or with zstd
7969 compression algorithms, which can deliver better bandwidth
7970 performance. Because lzma is computationally expensive, it's only
7971 used for documents that can be compressed once and served many
7972 times. Support for these algorithms requires that tor is built
7973 with the libzstd and/or liblzma libraries available. Implements
7974 proposal 278; closes ticket 21662.
7975 - Relays now perform the more expensive compression operations, and
7976 consensus diff generation, in worker threads. This separation
7977 avoids delaying the main thread when a new consensus arrives.
7979 o Major features (experimental):
7980 - Tor can now build modules written in Rust. To turn this on, pass
7981 the "--enable-rust" flag to the configure script. It's not time to
7982 get excited yet: currently, there is no actual Rust functionality
7983 beyond some simple glue code, and a notice at startup to tell you
7984 that Rust is running. Still, we hope that programmers and
7985 packagers will try building Tor with Rust support, so that we can
7986 find issues and solve portability problems. Closes ticket 22106.
7988 o Major features (traffic analysis resistance):
7989 - Connections between clients and relays now send a padding cell in
7990 each direction every 1.5 to 9.5 seconds (tunable via consensus
7991 parameters). This padding will not resist specialized
7992 eavesdroppers, but it should be enough to make many ISPs' routine
7993 network flow logging less useful in traffic analysis against
7996 Padding is negotiated using Tor's link protocol, so both relays
7997 and clients must upgrade for this to take effect. Clients may
7998 still send padding despite the relay's version by setting
7999 ConnectionPadding 1 in torrc, and may disable padding by setting
8000 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
8001 users with the torrc option ReducedConnectionPadding. Implements
8002 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
8003 - Relays will publish 24 hour totals of padding and non-padding cell
8004 counts to their extra-info descriptors, unless PaddingStatistics 0
8005 is set in torrc. These 24 hour totals are also rounded to
8008 o Major bugfixes (connection usage):
8009 - We use NETINFO cells to try to determine if both relays involved
8010 in a connection will agree on the canonical status of that
8011 connection. We prefer the connections where this is the case for
8012 extend cells, and try to close connections where relays disagree
8013 on their canonical status early. Also, we now prefer the oldest
8014 valid connection for extend cells. These two changes should reduce
8015 the number of long-term connections that are kept open between
8016 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
8017 - Relays now log hourly statistics (look for
8018 "channel_check_for_duplicates" lines) on the total number of
8019 connections to other relays. If the number of connections per
8020 relay is unexpectedly large, this log message is at notice level.
8021 Otherwise it is at info.
8023 o Major bugfixes (entry guards):
8024 - Don't block bootstrapping when a primary bridge is offline and we
8025 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8026 21969; bugfix on 0.3.0.3-alpha.
8028 o Major bugfixes (linux TPROXY support):
8029 - Fix a typo that had prevented TPROXY-based transparent proxying
8030 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8031 Patch from "d4fq0fQAgoJ".
8033 o Minor features (security, windows):
8034 - Enable a couple of pieces of Windows hardening: one
8035 (HeapEnableTerminationOnCorruption) that has been on-by-default
8036 since Windows 8, and unavailable before Windows 7; and one
8037 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
8038 affect us, but shouldn't do any harm. Closes ticket 21953.
8040 o Minor features (config options):
8041 - Allow "%include" directives in torrc configuration files. These
8042 directives import the settings from other files, or from all the
8043 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
8044 - Make SAVECONF return an error when overwriting a torrc that has
8045 includes. Using SAVECONF with the FORCE option will allow it to
8046 overwrite torrc even if includes are used. Related to ticket 1922.
8047 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
8048 will work without the FORCE option. Related to ticket 1922.
8050 o Minor features (controller):
8051 - Warn the first time that a controller requests data in the long-
8052 deprecated 'GETINFO network-status' format. Closes ticket 21703.
8054 o Minor features (defaults):
8055 - The default value for UseCreateFast is now 0: clients which
8056 haven't yet received a consensus document will now use a proper
8057 ntor handshake to talk to their directory servers whenever they
8058 can. Closes ticket 21407.
8059 - Onion key rotation and expiry intervals are now defined as a
8060 network consensus parameter, per proposal 274. The default
8061 lifetime of an onion key is increased from 7 to 28 days. Old onion
8062 keys will expire after 7 days by default. This change will make
8063 consensus diffs much smaller, and save significant bandwidth.
8064 Closes ticket 21641.
8066 o Minor features (fallback directory list):
8067 - Update the fallback directory mirror whitelist and blacklist based
8068 on operator emails. Closes task 21121.
8069 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8070 December 2016 (of which ~126 were still functional) with a list of
8071 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8072 2017. Resolves ticket 21564.
8074 o Minor features (hidden services, logging):
8075 - Log a message when a hidden service descriptor has fewer
8076 introduction points than specified in
8077 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
8078 - Log a message when a hidden service reaches its introduction point
8079 circuit limit, and when that limit is reset. Follow up to ticket
8080 21594; closes ticket 21622.
8081 - Warn user if multiple entries in EntryNodes and at least one
8082 HiddenService are used together. Pinning EntryNodes along with a
8083 hidden service can be possibly harmful; for instance see ticket
8084 14917 or 21155. Closes ticket 21155.
8086 o Minor features (linux seccomp2 sandbox):
8087 - We now have a document storage backend compatible with the Linux
8088 seccomp2 sandbox. This backend is used for consensus documents and
8089 diffs between them; in the long term, we'd like to use it for
8090 unparseable directory material too. Closes ticket 21645
8091 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
8092 from 1MB to 16MB. This was necessary with the glibc allocator in
8093 order to allow worker threads to allocate more memory -- which in
8094 turn is necessary because of our new use of worker threads for
8095 compression. Closes ticket 22096.
8097 o Minor features (logging):
8098 - Log files are no longer created world-readable by default.
8099 (Previously, most distributors would store the logs in a non-
8100 world-readable location to prevent inappropriate access. This
8101 change is an extra precaution.) Closes ticket 21729; patch
8104 o Minor features (performance):
8105 - Our Keccak (SHA-3) implementation now accesses memory more
8106 efficiently, especially on little-endian systems. Closes
8108 - Add an O(1) implementation of channel_find_by_global_id(), to
8109 speed some controller functions.
8111 o Minor features (relay, configuration):
8112 - The MyFamily option may now be repeated as many times as desired,
8113 for relays that want to configure large families. Closes ticket
8114 4998; patch by Daniel Pinto.
8116 o Minor features (safety):
8117 - Add an explicit check to extrainfo_parse_entry_from_string() for
8118 NULL inputs. We don't believe this can actually happen, but it may
8119 help silence a warning from the Clang analyzer. Closes
8122 o Minor features (testing):
8123 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
8124 When Tor is compiled with this option, we disable a number of
8125 redundant memory-safety failsafes that are intended to stop bugs
8126 from becoming security issues. This makes it easier to hunt for
8127 bugs that would be security issues without the failsafes turned
8128 on. Closes ticket 21439.
8129 - Add a general event-tracing instrumentation support to Tor. This
8130 subsystem will enable developers and researchers to add fine-
8131 grained instrumentation to their Tor instances, for use when
8132 examining Tor network performance issues. There are no trace
8133 events yet, and event-tracing is off by default unless enabled at
8134 compile time. Implements ticket 13802.
8135 - Improve our version parsing tests: add tests for typical version
8136 components, add tests for invalid versions, including numeric
8137 range and non-numeric prefixes. Unit tests 21278, 21450, and
8138 21507. Partially implements 21470.
8140 o Minor bugfixes (bandwidth accounting):
8141 - Roll over monthly accounting at the configured hour and minute,
8142 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8143 Found by Andrey Karpov with PVS-Studio.
8145 o Minor bugfixes (code correctness):
8146 - Accurately identify client connections by their lack of peer
8147 authentication. This means that we bail out earlier if asked to
8148 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
8151 o Minor bugfixes (configuration):
8152 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8153 bug 22252; bugfix on 0.2.9.3-alpha.
8155 o Minor bugfixes (connection lifespan):
8156 - Allow more control over how long TLS connections are kept open:
8157 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
8158 single option called CircuitsAvailableTimeout. Also, allow the
8159 consensus to control the default values for both this preference
8160 and the lifespan of relay-to-relay connections. Fixes bug 17592;
8161 bugfix on 0.2.5.5-alpha.
8162 - Increase the initial circuit build timeout testing frequency, to
8163 help ensure that ReducedConnectionPadding clients finish learning
8164 a timeout before their orconn would expire. The initial testing
8165 rate was set back in the days of TAP and before the Tor Browser
8166 updater, when we had to be much more careful about new clients
8167 making lots of circuits. With this change, a circuit build timeout
8168 is learned in about 15-20 minutes, instead of 100-120 minutes.
8170 o Minor bugfixes (controller):
8171 - GETINFO onions/current and onions/detached no longer respond with
8172 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
8173 - Trigger HS descriptor events on the control port when the client
8174 fails to pick a hidden service directory for a hidden service.
8175 This can happen if all the hidden service directories are in
8176 ExcludeNodes, or they have all been queried within the last 15
8177 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
8179 o Minor bugfixes (directory authority):
8180 - When rejecting a router descriptor for running an obsolete version
8181 of Tor without ntor support, warn about the obsolete tor version,
8182 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8183 - Prevent the shared randomness subsystem from asserting when
8184 initialized by a bridge authority with an incomplete configuration
8185 file. Fixes bug 21586; bugfix on 0.2.9.8.
8187 o Minor bugfixes (exit-side DNS):
8188 - Fix an untriggerable assertion that checked the output of a
8189 libevent DNS error, so that the assertion actually behaves as
8190 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
8191 Karpov using PVS-Studio.
8193 o Minor bugfixes (fallback directories):
8194 - Make the usage example in updateFallbackDirs.py actually work, and
8195 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
8196 - Decrease the guard flag average required to be a fallback. This
8197 allows us to keep relays that have their guard flag removed when
8198 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
8199 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
8200 bugfix on 0.2.8.1-alpha.
8201 - Make sure fallback directory mirrors have the same address, port,
8202 and relay identity key for at least 30 days before they are
8203 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
8205 o Minor bugfixes (hidden services):
8206 - Stop printing a cryptic warning when a hidden service gets a
8207 request to connect to a virtual port that it hasn't configured.
8208 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
8209 - Simplify hidden service descriptor creation by using an existing
8210 flag to check if an introduction point is established. Fixes bug
8211 21599; bugfix on 0.2.7.2-alpha.
8213 o Minor bugfixes (memory leak):
8214 - Fix a small memory leak at exit from the backtrace handler code.
8215 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
8217 o Minor bugfixes (protocol, logging):
8218 - Downgrade a log statement about unexpected relay cells from "bug"
8219 to "protocol warning", because there is at least one use case
8220 where it can be triggered by a buggy tor implementation. Fixes bug
8221 21293; bugfix on 0.1.1.14-alpha.
8223 o Minor bugfixes (testing):
8224 - Use unbuffered I/O for utility functions around the
8225 process_handle_t type. This fixes unit test failures reported on
8226 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
8227 - Make display of captured unit test log messages consistent. Fixes
8228 bug 21510; bugfix on 0.2.9.3-alpha.
8229 - Make test-network.sh always call chutney's test-network.sh.
8230 Previously, this only worked on systems which had bash installed,
8231 due to some bash-specific code in the script. Fixes bug 19699;
8232 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
8234 o Minor bugfixes (voting consistency):
8235 - Reject version numbers with non-numeric prefixes (such as +, -, or
8236 whitespace). Disallowing whitespace prevents differential version
8237 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8238 and part of 21508; bugfix on 0.0.8pre1.
8240 o Minor bugfixes (windows, relay):
8241 - Resolve "Failure from drain_fd: No error" warnings on Windows
8242 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
8244 o Code simplification and refactoring:
8245 - Break up the 630-line function connection_dir_client_reached_eof()
8246 into a dozen smaller functions. This change should help
8247 maintainability and readability of the client directory code.
8248 - Isolate our use of the openssl headers so that they are only
8249 included from our crypto wrapper modules, and from tests that
8250 examine those modules' internals. Closes ticket 21841.
8251 - Simplify our API to launch directory requests, making it more
8252 extensible and less error-prone. Now it's easier to add extra
8253 headers to directory requests. Closes ticket 21646.
8254 - Our base64 decoding functions no longer overestimate the output
8255 space that they need when parsing unpadded inputs. Closes
8257 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
8258 Resolves ticket 22213.
8259 - The logic that directory caches use to spool request to clients,
8260 serving them one part at a time so as not to allocate too much
8261 memory, has been refactored for consistency. Previously there was
8262 a separate spooling implementation per type of spoolable data. Now
8263 there is one common spooling implementation, with extensible data
8264 types. Closes ticket 21651.
8265 - Tor's compression module now supports multiple backends. Part of
8266 the implementation for proposal 278; closes ticket 21663.
8269 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
8270 Closes ticket 21873.
8271 - Correct documentation about the default DataDirectory value.
8272 Closes ticket 21151.
8273 - Document the default behavior of NumEntryGuards and
8274 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
8276 - Document key=value pluggable transport arguments for Bridge lines
8277 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
8278 - Note that bandwidth-limiting options don't affect TCP headers or
8279 DNS. Closes ticket 17170.
8281 o Removed features (configuration options, all in ticket 22060):
8282 - These configuration options are now marked Obsolete, and no longer
8283 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
8284 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
8285 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
8286 in 0.2.9.2-alpha and have now been removed. The previous default
8287 behavior is now always chosen; the previous (less secure) non-
8288 default behavior is now unavailable.
8289 - CloseHSClientCircuitsImmediatelyOnTimeout and
8290 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
8291 0.2.9.2-alpha and now have been removed. HS circuits never close
8292 on circuit build timeout; they have a longer timeout period.
8293 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
8294 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
8295 (and others) to configure listen-only and advertise-only addresses.
8297 o Removed features (tools):
8298 - We've removed the tor-checkkey tool from src/tools. Long ago, we
8299 used it to help people detect RSA keys that were generated by
8300 versions of Debian affected by CVE-2008-0166. But those keys have
8301 been out of circulation for ages, and this tool is no longer
8302 required. Closes ticket 21842.
8305 Changes in version 0.3.0.7 - 2017-05-15
8306 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
8307 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
8308 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
8309 clients are not affected.
8311 o Major bugfixes (hidden service directory, security):
8312 - Fix an assertion failure in the hidden service directory code, which
8313 could be used by an attacker to remotely cause a Tor relay process to
8314 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
8315 should upgrade. This security issue is tracked as TROVE-2017-002.
8316 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
8319 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8322 o Minor features (future-proofing):
8323 - Tor no longer refuses to download microdescriptors or descriptors
8324 if they are listed as "published in the future". This change will
8325 eventually allow us to stop listing meaningful "published" dates
8326 in microdescriptor consensuses, and thereby allow us to reduce the
8327 resources required to download consensus diffs by over 50%.
8328 Implements part of ticket 21642; implements part of proposal 275.
8330 o Minor bugfixes (Linux seccomp2 sandbox):
8331 - The getpid() system call is now permitted under the Linux seccomp2
8332 sandbox, to avoid crashing with versions of OpenSSL (and other
8333 libraries) that attempt to learn the process's PID by using the
8334 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8338 Changes in version 0.3.0.6 - 2017-04-26
8339 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
8341 With the 0.3.0 series, clients and relays now use Ed25519 keys to
8342 authenticate their link connections to relays, rather than the old
8343 RSA1024 keys that they used before. (Circuit crypto has been
8344 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
8345 the guard selection and replacement algorithm to behave more robustly
8346 in the presence of unreliable networks, and to resist guard-
8349 This series also includes numerous other small features and bugfixes,
8350 along with more groundwork for the upcoming hidden-services revamp.
8352 Per our stable release policy, we plan to support the Tor 0.3.0
8353 release series for at least the next nine months, or for three months
8354 after the first stable release of the 0.3.1 series: whichever is
8355 longer. If you need a release with long-term support, we recommend
8356 that you stay with the 0.2.9 series.
8358 Below are the changes since 0.3.0.5-rc. For a list of all changes
8359 since 0.2.9, see the ReleaseNotes file.
8361 o Minor features (geoip):
8362 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
8365 o Minor bugfixes (control port):
8366 - The GETINFO extra-info/digest/<digest> command was broken because
8367 of a wrong base16 decode return value check, introduced when
8368 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8370 o Minor bugfixes (crash prevention):
8371 - Fix a (currently untriggerable, but potentially dangerous) crash
8372 bug when base32-encoding inputs whose sizes are not a multiple of
8373 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
8376 Changes in version 0.3.0.5-rc - 2017-04-05
8377 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
8378 0.3.0 release series.
8380 This is the second release candidate in the Tor 0.3.0 series, and has
8381 much fewer changes than the first. If we find no new bugs or
8382 regressions here, the first stable 0.3.0 release will be nearly
8385 o Major bugfixes (crash, directory connections):
8386 - Fix a rare crash when sending a begin cell on a circuit whose
8387 linked directory connection had already been closed. Fixes bug
8388 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
8390 o Major bugfixes (guard selection):
8391 - Fix a guard selection bug where Tor would refuse to bootstrap in
8392 some cases if the user swapped a bridge for another bridge in
8393 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
8394 Reported by "torvlnt33r".
8396 o Minor features (geoip):
8397 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
8400 o Minor bugfix (compilation):
8401 - Fix a warning when compiling hs_service.c. Previously, it had no
8402 exported symbols when compiled for libor.a, resulting in a
8403 compilation warning from clang. Fixes bug 21825; bugfix
8406 o Minor bugfixes (hidden services):
8407 - Make hidden services check for failed intro point connections,
8408 even when they have exceeded their intro point creation limit.
8409 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
8410 - Make hidden services with 8 to 10 introduction points check for
8411 failed circuits immediately after startup. Previously, they would
8412 wait for 5 minutes before performing their first checks. Fixes bug
8413 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
8415 o Minor bugfixes (memory leaks):
8416 - Fix a memory leak when using GETCONF on a port option. Fixes bug
8417 21682; bugfix on 0.3.0.3-alpha.
8419 o Minor bugfixes (relay):
8420 - Avoid a double-marked-circuit warning that could happen when we
8421 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
8424 o Minor bugfixes (tests):
8425 - Run the entry_guard_parse_from_state_full() test with the time set
8426 to a specific date. (The guard state that this test was parsing
8427 contained guards that had expired since the test was first
8428 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
8431 - Update the description of the directory server options in the
8432 manual page, to clarify that a relay no longer needs to set
8433 DirPort in order to be a directory cache. Closes ticket 21720.
8437 Changes in version 0.2.8.13 - 2017-03-03
8438 Tor 0.2.8.13 backports a security fix from later Tor
8439 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
8440 this release, if for some reason they cannot upgrade to a later
8441 release series, and if they build Tor with the --enable-expensive-hardening
8444 Note that support for Tor 0.2.8.x is ending next year: we will not issue
8445 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
8446 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8448 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8449 - Fix an integer underflow bug when comparing malformed Tor
8450 versions. This bug could crash Tor when built with
8451 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8452 0.2.9.8, which were built with -ftrapv by default. In other cases
8453 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8454 on 0.0.8pre1. Found by OSS-Fuzz.
8456 o Minor features (geoip):
8457 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8461 Changes in version 0.2.7.7 - 2017-03-03
8462 Tor 0.2.7.7 backports a number of security fixes from later Tor
8463 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
8464 this release, if for some reason they cannot upgrade to a later
8467 Note that support for Tor 0.2.7.x is ending this year: we will not issue
8468 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
8469 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8471 o Directory authority changes (backport from 0.2.8.5-rc):
8472 - Urras is no longer a directory authority. Closes ticket 19271.
8474 o Directory authority changes (backport from 0.2.9.2-alpha):
8475 - The "Tonga" bridge authority has been retired; the new bridge
8476 authority is "Bifroest". Closes tickets 19728 and 19690.
8478 o Directory authority key updates (backport from 0.2.8.1-alpha):
8479 - Update the V3 identity key for the dannenberg directory authority:
8480 it was changed on 18 November 2015. Closes task 17906. Patch
8483 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8484 - Fix a bug in parsing that could cause clients to read a single
8485 byte past the end of an allocated region. This bug could be used
8486 to cause hardened clients (built with --enable-expensive-hardening)
8487 to crash if they tried to visit a hostile hidden service. Non-
8488 hardened clients are only affected depending on the details of
8489 their platform's memory allocator. Fixes bug 21018; bugfix on
8490 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8491 2016-12-002 and as CVE-2016-1254.
8493 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8494 - Stop a crash that could occur when a client running with DNSPort
8495 received a query with multiple address types, and the first
8496 address type was not supported. Found and fixed by Scott Dial.
8497 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8498 - Prevent a class of security bugs caused by treating the contents
8499 of a buffer chunk as if they were a NUL-terminated string. At
8500 least one such bug seems to be present in all currently used
8501 versions of Tor, and would allow an attacker to remotely crash
8502 most Tor instances, especially those compiled with extra compiler
8503 hardening. With this defense in place, such bugs can't crash Tor,
8504 though we should still fix them as they occur. Closes ticket
8505 20384 (TROVE-2016-10-001).
8507 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8508 - Avoid a difficult-to-trigger heap corruption attack when extending
8509 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8510 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8511 Reported by Guido Vranken.
8513 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8514 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8515 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8517 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8518 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8519 pointer to the previous (uninitialized) key value. The impact here
8520 should be limited to a difficult-to-trigger crash, if OpenSSL is
8521 running an engine that makes key generation failures possible, or
8522 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8523 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8526 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8527 - Fix an integer underflow bug when comparing malformed Tor
8528 versions. This bug could crash Tor when built with
8529 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8530 0.2.9.8, which were built with -ftrapv by default. In other cases
8531 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8532 on 0.0.8pre1. Found by OSS-Fuzz.
8534 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8535 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8536 zero size. Check size argument to memwipe() for underflow. Fixes
8537 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8540 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8541 - Make Tor survive errors involving connections without a
8542 corresponding event object. Previously we'd fail with an
8543 assertion; now we produce a log message. Related to bug 16248.
8545 o Minor features (geoip):
8546 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8550 Changes in version 0.2.6.11 - 2017-03-03
8551 Tor 0.2.6.11 backports a number of security fixes from later Tor
8552 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
8553 this release, if for some reason they cannot upgrade to a later
8556 Note that support for Tor 0.2.6.x is ending this year: we will not issue
8557 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
8558 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8560 o Directory authority changes (backport from 0.2.8.5-rc):
8561 - Urras is no longer a directory authority. Closes ticket 19271.
8563 o Directory authority changes (backport from 0.2.9.2-alpha):
8564 - The "Tonga" bridge authority has been retired; the new bridge
8565 authority is "Bifroest". Closes tickets 19728 and 19690.
8567 o Directory authority key updates (backport from 0.2.8.1-alpha):
8568 - Update the V3 identity key for the dannenberg directory authority:
8569 it was changed on 18 November 2015. Closes task 17906. Patch
8572 o Major features (security fixes, backport from 0.2.9.4-alpha):
8573 - Prevent a class of security bugs caused by treating the contents
8574 of a buffer chunk as if they were a NUL-terminated string. At
8575 least one such bug seems to be present in all currently used
8576 versions of Tor, and would allow an attacker to remotely crash
8577 most Tor instances, especially those compiled with extra compiler
8578 hardening. With this defense in place, such bugs can't crash Tor,
8579 though we should still fix them as they occur. Closes ticket
8580 20384 (TROVE-2016-10-001).
8582 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8583 - Fix a bug in parsing that could cause clients to read a single
8584 byte past the end of an allocated region. This bug could be used
8585 to cause hardened clients (built with --enable-expensive-hardening)
8586 to crash if they tried to visit a hostile hidden service. Non-
8587 hardened clients are only affected depending on the details of
8588 their platform's memory allocator. Fixes bug 21018; bugfix on
8589 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8590 2016-12-002 and as CVE-2016-1254.
8592 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8593 - Stop a crash that could occur when a client running with DNSPort
8594 received a query with multiple address types, and the first
8595 address type was not supported. Found and fixed by Scott Dial.
8596 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8598 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8599 - Fix an error that could cause us to read 4 bytes before the
8600 beginning of an openssl string. This bug could be used to cause
8601 Tor to crash on systems with unusual malloc implementations, or
8602 systems with unusual hardening installed. Fixes bug 17404; bugfix
8605 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8606 - Avoid a difficult-to-trigger heap corruption attack when extending
8607 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8608 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8609 Reported by Guido Vranken.
8611 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8612 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8613 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8615 o Major bugfixes (guard selection, backport from 0.2.7.6):
8616 - Actually look at the Guard flag when selecting a new directory
8617 guard. When we implemented the directory guard design, we
8618 accidentally started treating all relays as if they have the Guard
8619 flag during guard selection, leading to weaker anonymity and worse
8620 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8623 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8624 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8625 pointer to the previous (uninitialized) key value. The impact here
8626 should be limited to a difficult-to-trigger crash, if OpenSSL is
8627 running an engine that makes key generation failures possible, or
8628 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8629 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8632 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8633 - Fix an integer underflow bug when comparing malformed Tor
8634 versions. This bug could crash Tor when built with
8635 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8636 0.2.9.8, which were built with -ftrapv by default. In other cases
8637 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8638 on 0.0.8pre1. Found by OSS-Fuzz.
8640 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8641 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8642 zero size. Check size argument to memwipe() for underflow. Fixes
8643 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8646 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8647 - Make Tor survive errors involving connections without a
8648 corresponding event object. Previously we'd fail with an
8649 assertion; now we produce a log message. Related to bug 16248.
8651 o Minor features (geoip):
8652 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8655 o Minor bugfixes (compilation, backport from 0.2.7.6):
8656 - Fix a compilation warning with Clang 3.6: Do not check the
8657 presence of an address which can never be NULL. Fixes bug 17781.
8660 Changes in version 0.2.5.13 - 2017-03-03
8661 Tor 0.2.5.13 backports a number of security fixes from later Tor
8662 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
8663 this release, if for some reason they cannot upgrade to a later
8666 Note that support for Tor 0.2.5.x is ending next year: we will not issue
8667 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
8668 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8670 o Directory authority changes (backport from 0.2.8.5-rc):
8671 - Urras is no longer a directory authority. Closes ticket 19271.
8673 o Directory authority changes (backport from 0.2.9.2-alpha):
8674 - The "Tonga" bridge authority has been retired; the new bridge
8675 authority is "Bifroest". Closes tickets 19728 and 19690.
8677 o Directory authority key updates (backport from 0.2.8.1-alpha):
8678 - Update the V3 identity key for the dannenberg directory authority:
8679 it was changed on 18 November 2015. Closes task 17906. Patch
8682 o Major features (security fixes, backport from 0.2.9.4-alpha):
8683 - Prevent a class of security bugs caused by treating the contents
8684 of a buffer chunk as if they were a NUL-terminated string. At
8685 least one such bug seems to be present in all currently used
8686 versions of Tor, and would allow an attacker to remotely crash
8687 most Tor instances, especially those compiled with extra compiler
8688 hardening. With this defense in place, such bugs can't crash Tor,
8689 though we should still fix them as they occur. Closes ticket
8690 20384 (TROVE-2016-10-001).
8692 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8693 - Fix a bug in parsing that could cause clients to read a single
8694 byte past the end of an allocated region. This bug could be used
8695 to cause hardened clients (built with --enable-expensive-hardening)
8696 to crash if they tried to visit a hostile hidden service. Non-
8697 hardened clients are only affected depending on the details of
8698 their platform's memory allocator. Fixes bug 21018; bugfix on
8699 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8700 2016-12-002 and as CVE-2016-1254.
8702 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8703 - Stop a crash that could occur when a client running with DNSPort
8704 received a query with multiple address types, and the first
8705 address type was not supported. Found and fixed by Scott Dial.
8706 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8708 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8709 - Fix an error that could cause us to read 4 bytes before the
8710 beginning of an openssl string. This bug could be used to cause
8711 Tor to crash on systems with unusual malloc implementations, or
8712 systems with unusual hardening installed. Fixes bug 17404; bugfix
8715 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8716 - Avoid a difficult-to-trigger heap corruption attack when extending
8717 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8718 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8719 Reported by Guido Vranken.
8721 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8722 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8723 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8725 o Major bugfixes (guard selection, backport from 0.2.7.6):
8726 - Actually look at the Guard flag when selecting a new directory
8727 guard. When we implemented the directory guard design, we
8728 accidentally started treating all relays as if they have the Guard
8729 flag during guard selection, leading to weaker anonymity and worse
8730 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8733 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8734 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8735 pointer to the previous (uninitialized) key value. The impact here
8736 should be limited to a difficult-to-trigger crash, if OpenSSL is
8737 running an engine that makes key generation failures possible, or
8738 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8739 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8742 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8743 - Fix an integer underflow bug when comparing malformed Tor
8744 versions. This bug could crash Tor when built with
8745 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8746 0.2.9.8, which were built with -ftrapv by default. In other cases
8747 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8748 on 0.0.8pre1. Found by OSS-Fuzz.
8750 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8751 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8752 zero size. Check size argument to memwipe() for underflow. Fixes
8753 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8756 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8757 - Make Tor survive errors involving connections without a
8758 corresponding event object. Previously we'd fail with an
8759 assertion; now we produce a log message. Related to bug 16248.
8761 o Minor features (geoip):
8762 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8765 o Minor bugfixes (compilation, backport from 0.2.7.6):
8766 - Fix a compilation warning with Clang 3.6: Do not check the
8767 presence of an address which can never be NULL. Fixes bug 17781.
8769 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
8770 - Check for failures from crypto_early_init, and refuse to continue.
8771 A previous typo meant that we could keep going with an
8772 uninitialized crypto library, and would have OpenSSL initialize
8773 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
8774 when implementing ticket 4900. Patch by "teor".
8776 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8777 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8778 a client authorized hidden service. Fixes bug 15823; bugfix
8782 Changes in version 0.2.4.28 - 2017-03-03
8783 Tor 0.2.4.28 backports a number of security fixes from later Tor
8784 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
8785 this release, if for some reason they cannot upgrade to a later
8788 Note that support for Tor 0.2.4.x is ending soon: we will not issue
8789 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
8790 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
8792 o Directory authority changes (backport from 0.2.8.5-rc):
8793 - Urras is no longer a directory authority. Closes ticket 19271.
8795 o Directory authority changes (backport from 0.2.9.2-alpha):
8796 - The "Tonga" bridge authority has been retired; the new bridge
8797 authority is "Bifroest". Closes tickets 19728 and 19690.
8799 o Directory authority key updates (backport from 0.2.8.1-alpha):
8800 - Update the V3 identity key for the dannenberg directory authority:
8801 it was changed on 18 November 2015. Closes task 17906. Patch
8804 o Major features (security fixes, backport from 0.2.9.4-alpha):
8805 - Prevent a class of security bugs caused by treating the contents
8806 of a buffer chunk as if they were a NUL-terminated string. At
8807 least one such bug seems to be present in all currently used
8808 versions of Tor, and would allow an attacker to remotely crash
8809 most Tor instances, especially those compiled with extra compiler
8810 hardening. With this defense in place, such bugs can't crash Tor,
8811 though we should still fix them as they occur. Closes ticket
8812 20384 (TROVE-2016-10-001).
8814 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8815 - Fix a bug in parsing that could cause clients to read a single
8816 byte past the end of an allocated region. This bug could be used
8817 to cause hardened clients (built with --enable-expensive-hardening)
8818 to crash if they tried to visit a hostile hidden service. Non-
8819 hardened clients are only affected depending on the details of
8820 their platform's memory allocator. Fixes bug 21018; bugfix on
8821 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8822 2016-12-002 and as CVE-2016-1254.
8824 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8825 - Fix an error that could cause us to read 4 bytes before the
8826 beginning of an openssl string. This bug could be used to cause
8827 Tor to crash on systems with unusual malloc implementations, or
8828 systems with unusual hardening installed. Fixes bug 17404; bugfix
8831 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8832 - Avoid a difficult-to-trigger heap corruption attack when extending
8833 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8834 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8835 Reported by Guido Vranken.
8837 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8838 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8839 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8841 o Major bugfixes (guard selection, backport from 0.2.7.6):
8842 - Actually look at the Guard flag when selecting a new directory
8843 guard. When we implemented the directory guard design, we
8844 accidentally started treating all relays as if they have the Guard
8845 flag during guard selection, leading to weaker anonymity and worse
8846 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8849 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8850 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8851 pointer to the previous (uninitialized) key value. The impact here
8852 should be limited to a difficult-to-trigger crash, if OpenSSL is
8853 running an engine that makes key generation failures possible, or
8854 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8855 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8858 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8859 - Fix an integer underflow bug when comparing malformed Tor
8860 versions. This bug could crash Tor when built with
8861 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8862 0.2.9.8, which were built with -ftrapv by default. In other cases
8863 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8864 on 0.0.8pre1. Found by OSS-Fuzz.
8866 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8867 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8868 zero size. Check size argument to memwipe() for underflow. Fixes
8869 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8872 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8873 - Make Tor survive errors involving connections without a
8874 corresponding event object. Previously we'd fail with an
8875 assertion; now we produce a log message. Related to bug 16248.
8877 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
8878 - Make it harder for attackers to overload hidden services with
8879 introductions, by blocking multiple introduction requests on the
8880 same circuit. Resolves ticket 15515.
8882 o Minor features (geoip):
8883 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8886 o Minor bugfixes (compilation, backport from 0.2.7.6):
8887 - Fix a compilation warning with Clang 3.6: Do not check the
8888 presence of an address which can never be NULL. Fixes bug 17781.
8890 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8891 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8892 a client authorized hidden service. Fixes bug 15823; bugfix
8896 Changes in version 0.3.0.4-rc - 2017-03-01
8897 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
8898 0.3.0 release series, and introduces a few reliability features to
8899 keep them from coming back.
8901 This is the first release candidate in the Tor 0.3.0 series. If we
8902 find no new bugs or regressions here, the first stable 0.3.0 release
8903 will be nearly identical to it.
8905 o Major bugfixes (bridges):
8906 - When the same bridge is configured multiple times with the same
8907 identity, but at different address:port combinations, treat those
8908 bridge instances as separate guards. This fix restores the ability
8909 of clients to configure the same bridge with multiple pluggable
8910 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
8912 o Major bugfixes (hidden service directory v3):
8913 - Stop crashing on a failed v3 hidden service descriptor lookup
8914 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
8916 o Major bugfixes (parsing):
8917 - When parsing a malformed content-length field from an HTTP
8918 message, do not read off the end of the buffer. This bug was a
8919 potential remote denial-of-service attack against Tor clients and
8920 relays. A workaround was released in October 2016, to prevent this
8921 bug from crashing Tor. This is a fix for the underlying issue,
8922 which should no longer matter (if you applied the earlier patch).
8923 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
8924 using AFL (http://lcamtuf.coredump.cx/afl/).
8925 - Fix an integer underflow bug when comparing malformed Tor
8926 versions. This bug could crash Tor when built with
8927 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8928 0.2.9.8, which were built with -ftrapv by default. In other cases
8929 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8930 on 0.0.8pre1. Found by OSS-Fuzz.
8932 o Minor feature (protocol versioning):
8933 - Add new protocol version for proposal 224. HSIntro now advertises
8934 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
8936 o Minor features (directory authorities):
8937 - Directory authorities now reject descriptors that claim to be
8938 malformed versions of Tor. Helps prevent exploitation of
8940 - Reject version numbers with components that exceed INT32_MAX.
8941 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
8942 Fixes bug 21450; bugfix on 0.0.8pre1.
8943 - Directory authorities now reject relays running versions
8944 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8945 suffer from bug 20499 and don't keep their consensus cache
8946 up-to-date. Resolves ticket 20509.
8948 o Minor features (geoip):
8949 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8952 o Minor features (reliability, crash):
8953 - Try better to detect problems in buffers where they might grow (or
8954 think they have grown) over 2 GB in size. Diagnostic for
8957 o Minor features (testing):
8958 - During 'make test-network-all', if tor logs any warnings, ask
8959 chutney to output them. Requires a recent version of chutney with
8960 the 21572 patch. Implements 21570.
8962 o Minor bugfixes (certificate expiration time):
8963 - Avoid using link certificates that don't become valid till some
8964 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
8966 o Minor bugfixes (code correctness):
8967 - Repair a couple of (unreachable or harmless) cases of the risky
8968 comparison-by-subtraction pattern that caused bug 21278.
8969 - Remove a redundant check for the UseEntryGuards option from the
8970 options_transition_affects_guards() function. Fixes bug 21492;
8971 bugfix on 0.3.0.1-alpha.
8973 o Minor bugfixes (directory mirrors):
8974 - Allow relays to use directory mirrors without a DirPort: these
8975 relays need to be contacted over their ORPorts using a begindir
8976 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
8977 - Clarify the message logged when a remote relay is unexpectedly
8978 missing an ORPort or DirPort: users were confusing this with a
8979 local port. Fixes another case of bug 20711; bugfix
8982 o Minor bugfixes (guards):
8983 - Don't warn about a missing guard state on timeout-measurement
8984 circuits: they aren't supposed to be using guards. Fixes an
8985 instance of bug 21007; bugfix on 0.3.0.1-alpha.
8986 - Silence a BUG() warning when attempting to use a guard whose
8987 descriptor we don't know, and make this scenario less likely to
8988 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
8990 o Minor bugfixes (hidden service):
8991 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
8992 cells. Previously, we were using sizeof() on a pointer, instead of
8993 the real destination buffer. Fortunately, that value was only used
8994 to double-check that there was enough room--which was already
8995 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
8997 o Minor bugfixes (testing):
8998 - Fix Raspbian build issues related to missing socket errno in
8999 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
9001 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
9002 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
9003 - Use bash in src/test/test-network.sh. This ensures we reliably
9004 call chutney's newer tools/test-network.sh when available. Fixes
9005 bug 21562; bugfix on 0.2.9.1-alpha.
9008 - Small fixes to the fuzzing documentation. Closes ticket 21472.
9011 Changes in version 0.2.9.10 - 2017-03-01
9012 Tor 0.2.9.10 backports a security fix from later Tor release. It also
9013 includes fixes for some major issues affecting directory authorities,
9014 LibreSSL compatibility, and IPv6 correctness.
9016 The Tor 0.2.9.x release series is now marked as a long-term-support
9017 series. We intend to backport security fixes to 0.2.9.x until at
9018 least January of 2020.
9020 o Major bugfixes (directory authority, 0.3.0.3-alpha):
9021 - During voting, when marking a relay as a probable sybil, do not
9022 clear its BadExit flag: sybils can still be bad in other ways
9023 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9026 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
9027 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9028 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9029 exit policy rejects that port on more than an IPv6 /16 of
9030 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9031 which rejected a relay's own IPv6 address by default. Fixes bug
9032 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9034 o Major bugfixes (parsing, also in 0.3.0.4-rc):
9035 - Fix an integer underflow bug when comparing malformed Tor
9036 versions. This bug could crash Tor when built with
9037 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9038 0.2.9.8, which were built with -ftrapv by default. In other cases
9039 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9040 on 0.0.8pre1. Found by OSS-Fuzz.
9042 o Minor features (directory authorities, also in 0.3.0.4-rc):
9043 - Directory authorities now reject descriptors that claim to be
9044 malformed versions of Tor. Helps prevent exploitation of
9046 - Reject version numbers with components that exceed INT32_MAX.
9047 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
9048 Fixes bug 21450; bugfix on 0.0.8pre1.
9050 o Minor features (geoip):
9051 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9054 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
9055 - Autoconf now checks to determine if OpenSSL structures are opaque,
9056 instead of explicitly checking for OpenSSL version numbers. Part
9058 - Support building with recent LibreSSL code that uses opaque
9059 structures. Closes ticket 21359.
9061 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
9062 - Repair a couple of (unreachable or harmless) cases of the risky
9063 comparison-by-subtraction pattern that caused bug 21278.
9065 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
9066 - The tor-resolve command line tool now rejects hostnames over 255
9067 characters in length. Previously, it would silently truncate them,
9068 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9069 Patch by "junglefowl".
9072 Changes in version 0.3.0.3-alpha - 2017-02-03
9073 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
9074 0.3.0.x development series, including some that could cause
9075 authorities to behave badly. There is also a fix for a longstanding
9076 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
9077 includes some smaller features and bugfixes.
9079 The Tor 0.3.0.x release series is now in patch-freeze: no additional
9080 features will be considered for inclusion in 0.3.0.x. We suspect that
9081 some bugs will probably remain, however, and we encourage people to
9084 o Major bugfixes (directory authority):
9085 - During voting, when marking a relay as a probable sybil, do not
9086 clear its BadExit flag: sybils can still be bad in other ways
9087 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9089 - When deciding whether we have just found a router to be reachable,
9090 do not penalize it for not having performed an Ed25519 link
9091 handshake if it does not claim to support an Ed25519 handshake.
9092 Previously, we would treat such relays as non-running. Fixes bug
9093 21107; bugfix on 0.3.0.1-alpha.
9095 o Major bugfixes (entry guards):
9096 - Stop trying to build circuits through entry guards for which we
9097 have no descriptor. Also, stop crashing in the case that we *do*
9098 accidentally try to build a circuit in such a state. Fixes bug
9099 21242; bugfix on 0.3.0.1-alpha.
9101 o Major bugfixes (IPv6 Exits):
9102 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9103 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9104 exit policy rejects that port on more than an IPv6 /16 of
9105 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9106 which rejected a relay's own IPv6 address by default. Fixes bug
9107 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9109 o Minor feature (client):
9110 - Enable IPv6 traffic on the SocksPort by default. To disable this,
9111 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
9113 o Minor feature (fallback scripts):
9114 - Add a check_existing mode to updateFallbackDirs.py, which checks
9115 if fallbacks in the hard-coded list are working. Closes ticket
9116 20174. Patch by haxxpop.
9118 o Minor features (ciphersuite selection):
9119 - Clients now advertise a list of ciphersuites closer to the ones
9120 preferred by Firefox. Closes part of ticket 15426.
9121 - Allow relays to accept a wider range of ciphersuites, including
9122 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
9124 o Minor features (controller, configuration):
9125 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
9126 and so on, now comes with a __*Port variant that will not be saved
9127 to the torrc file by the controller's SAVECONF command. This
9128 change allows TorBrowser to set up a single-use domain socket for
9129 each time it launches Tor. Closes ticket 20956.
9130 - The GETCONF command can now query options that may only be
9131 meaningful in context-sensitive lists. This allows the controller
9132 to query the mixed SocksPort/__SocksPort style options introduced
9133 in feature 20956. Implements ticket 21300.
9135 o Minor features (portability, compilation):
9136 - Autoconf now checks to determine if OpenSSL structures are opaque,
9137 instead of explicitly checking for OpenSSL version numbers. Part
9139 - Support building with recent LibreSSL code that uses opaque
9140 structures. Closes ticket 21359.
9142 o Minor features (relay):
9143 - We now allow separation of exit and relay traffic to different
9144 source IP addresses, using the OutboundBindAddressExit and
9145 OutboundBindAddressOR options respectively. Closes ticket 17975.
9146 Written by Michael Sonntag.
9148 o Minor bugfix (logging):
9149 - Don't recommend the use of Tor2web in non-anonymous mode.
9150 Recommending Tor2web is a bad idea because the client loses all
9151 anonymity. Tor2web should only be used in specific cases by users
9152 who *know* and understand the issues. Fixes bug 21294; bugfix
9155 o Minor bugfixes (client):
9156 - Always recover from failures in extend_info_from_node(), in an
9157 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
9158 bugfix on 0.2.3.1-alpha.
9160 o Minor bugfixes (client, entry guards):
9161 - Fix a bug warning (with backtrace) when we fail a channel that
9162 circuits to fallback directories on it. Fixes bug 21128; bugfix
9164 - Fix a spurious bug warning (with backtrace) when removing an
9165 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
9166 - Fix a bug of the new guard algorithm where tor could stall for up
9167 to 10 minutes before retrying a guard after a long period of no
9168 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
9169 - Do not try to build circuits until we have descriptors for our
9170 primary entry guards. Related to fix for bug 21242.
9172 o Minor bugfixes (configure, autoconf):
9173 - Rename the configure option --enable-expensive-hardening to
9174 --enable-fragile-hardening. Expensive hardening makes the tor
9175 daemon abort when some kinds of issues are detected. Thus, it
9176 makes tor more at risk of remote crashes but safer against RCE or
9177 heartbleed bug category. We now try to explain this issue in a
9178 message from the configure script. Fixes bug 21290; bugfix
9181 o Minor bugfixes (controller):
9182 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
9183 20824; bugfix on 0.3.0.1-alpha.
9185 o Minor bugfixes (hidden service):
9186 - Clean up the code for expiring intro points with no associated
9187 circuits. It was causing, rarely, a service with some expiring
9188 introduction points to not open enough additional introduction
9189 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
9190 - Stop setting the torrc option HiddenServiceStatistics to "0" just
9191 because we're not a bridge or relay. Instead, we preserve whatever
9192 value the user set (or didn't set). Fixes bug 21150; bugfix
9194 - Resolve two possible underflows which could lead to creating and
9195 closing a lot of introduction point circuits in a non-stop loop.
9196 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
9198 o Minor bugfixes (portability):
9199 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
9200 It is supported by OpenBSD itself, and also by most OpenBSD
9201 variants (such as Bitrig). Fixes bug 20980; bugfix
9203 - When mapping a file of length greater than SIZE_MAX, do not
9204 silently truncate its contents. This issue could occur on 32 bit
9205 systems with large file support and files which are larger than 4
9206 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
9208 o Minor bugfixes (tor-resolve):
9209 - The tor-resolve command line tool now rejects hostnames over 255
9210 characters in length. Previously, it would silently truncate them,
9211 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9212 Patch by "junglefowl".
9214 o Minor bugfixes (Windows services):
9215 - Be sure to initialize the monotonic time subsystem before using
9216 it, even when running as an NT service. Fixes bug 21356; bugfix
9220 Changes in version 0.3.0.2-alpha - 2017-01-23
9221 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
9222 cause relays and clients to crash, even if they were not built with
9223 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
9224 versions, and also affects 0.3.0.1-alpha: all relays running an affected
9225 version should upgrade.
9227 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
9228 time-to-live values, makes directory authorities enforce the 1-to-1
9229 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
9230 client-side onion service reachability bug, does better at selecting
9231 the set of fallback directories, and more.
9233 o Major bugfixes (security, also in 0.2.9.9):
9234 - Downgrade the "-ftrapv" option from "always on" to "only on when
9235 --enable-expensive-hardening is provided." This hardening option, like
9236 others, can turn survivable bugs into crashes--and having it on by
9237 default made a (relatively harmless) integer overflow bug into a
9238 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
9241 o Major features (security):
9242 - Change the algorithm used to decide DNS TTLs on client and server
9243 side, to better resist DNS-based correlation attacks like the
9244 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
9245 Feamster. Now relays only return one of two possible DNS TTL
9246 values, and clients are willing to believe DNS TTL values up to 3
9247 hours long. Closes ticket 19769.
9249 o Major features (directory authority, security):
9250 - The default for AuthDirPinKeys is now 1: directory authorities
9251 will reject relays where the RSA identity key matches a previously
9252 seen value, but the Ed25519 key has changed. Closes ticket 18319.
9254 o Major bugfixes (client, guard, crash):
9255 - In circuit_get_global_origin_list(), return the actual list of
9256 origin circuits. The previous version of this code returned the
9257 list of all the circuits, and could have caused strange bugs,
9258 including possible crashes. Fixes bug 21118; bugfix
9261 o Major bugfixes (client, onion service, also in 0.2.9.9):
9262 - Fix a client-side onion service reachability bug, where multiple
9263 socks requests to an onion service (or a single slow request)
9264 could cause us to mistakenly mark some of the service's
9265 introduction points as failed, and we cache that failure so
9266 eventually we run out and can't reach the service. Also resolves a
9267 mysterious "Remote server sent bogus reason code 65021" log
9268 warning. The bug was introduced in ticket 17218, where we tried to
9269 remember the circuit end reason as a uint16_t, which mangled
9270 negative values. Partially fixes bug 21056 and fixes bug 20307;
9271 bugfix on 0.2.8.1-alpha.
9273 o Major bugfixes (DNS):
9274 - Fix a bug that prevented exit nodes from caching DNS records for
9275 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
9277 o Minor features (controller):
9278 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
9279 shared-random values to the controller. Closes ticket 19925.
9281 o Minor features (entry guards):
9282 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
9283 break regression tests.
9284 - Require UseEntryGuards when UseBridges is set, in order to make
9285 sure bridges aren't bypassed. Resolves ticket 20502.
9287 o Minor features (fallback directories):
9288 - Select 200 fallback directories for each release. Closes
9290 - Allow 3 fallback relays per operator, which is safe now that we
9291 are choosing 200 fallback relays. Closes ticket 20912.
9292 - Exclude relays affected by bug 20499 from the fallback list.
9293 Exclude relays from the fallback list if they are running versions
9294 known to be affected by bug 20499, or if in our tests they deliver
9295 a stale consensus (i.e. one that expired more than 24 hours ago).
9296 Closes ticket 20539.
9297 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
9299 - Require fallback directories to have the same address and port for
9300 7 days (now that we have enough relays with this stability).
9301 Relays whose OnionOO stability timer is reset on restart by bug
9302 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
9303 this issue. Closes ticket 20880; maintains short-term fix
9305 - Require fallbacks to have flags for 90% of the time (weighted
9306 decaying average), rather than 95%. This allows at least 73% of
9307 clients to bootstrap in the first 5 seconds without contacting an
9308 authority. Part of ticket 18828.
9309 - Annotate updateFallbackDirs.py with the bandwidth and consensus
9310 weight for each candidate fallback. Closes ticket 20878.
9311 - Make it easier to change the output sort order of fallbacks.
9312 Closes ticket 20822.
9313 - Display the relay fingerprint when downloading consensuses from
9314 fallbacks. Closes ticket 20908.
9316 o Minor features (geoip, also in 0.2.9.9):
9317 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
9320 o Minor features (next-gen onion service directories):
9321 - Remove the "EnableOnionServicesV3" consensus parameter that we
9322 introduced in 0.3.0.1-alpha: relays are now always willing to act
9323 as v3 onion service directories. Resolves ticket 19899.
9325 o Minor features (linting):
9326 - Enhance the changes file linter to warn on Tor versions that are
9327 prefixed with "tor-". Closes ticket 21096.
9329 o Minor features (logging):
9330 - In several places, describe unset ed25519 keys as "<unset>",
9331 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
9333 o Minor bugfix (control protocol):
9334 - The reply to a "GETINFO config/names" request via the control
9335 protocol now spells the type "Dependent" correctly. This is a
9336 breaking change in the control protocol. (The field seems to be
9337 ignored by the most common known controllers.) Fixes bug 18146;
9338 bugfix on 0.1.1.4-alpha.
9340 o Minor bugfixes (bug resilience):
9341 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
9342 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
9343 Hans Jerry Illikainen.
9345 o Minor bugfixes (build):
9346 - Replace obsolete Autoconf macros with their modern equivalent and
9347 prevent similar issues in the future. Fixes bug 20990; bugfix
9350 o Minor bugfixes (client, guards):
9351 - Fix bug where Tor would think that there are circuits waiting for
9352 better guards even though those circuits have been freed. Fixes
9353 bug 21142; bugfix on 0.3.0.1-alpha.
9355 o Minor bugfixes (config):
9356 - Don't assert on startup when trying to get the options list and
9357 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
9358 options so of course they aren't ready yet. Fixes bug 21062;
9359 bugfix on 0.2.9.3-alpha.
9361 o Minor bugfixes (controller):
9362 - Make the GETINFO interface for inquiring about entry guards
9363 support the new guards backend. Fixes bug 20823; bugfix
9366 o Minor bugfixes (dead code):
9367 - Remove a redundant check for PidFile changes at runtime in
9368 options_transition_allowed(): this check is already performed
9369 regardless of whether the sandbox is active. Fixes bug 21123;
9370 bugfix on 0.2.5.4-alpha.
9372 o Minor bugfixes (documentation):
9373 - Update the tor manual page to document every option that can not
9374 be changed while tor is running. Fixes bug 21122.
9376 o Minor bugfixes (fallback directories):
9377 - Stop failing when a relay has no uptime data in
9378 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
9379 - Avoid checking fallback candidates' DirPorts if they are down in
9380 OnionOO. When a relay operator has multiple relays, this
9381 prioritizes relays that are up over relays that are down. Fixes
9382 bug 20926; bugfix on 0.2.8.3-alpha.
9383 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
9384 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
9386 o Minor bugfixes (guards, bootstrapping):
9387 - When connecting to a directory guard during bootstrap, do not mark
9388 the guard as successful until we receive a good-looking directory
9389 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
9391 o Minor bugfixes (onion services):
9392 - Fix the config reload pruning of old vs new services so it
9393 actually works when both ephemeral and non-ephemeral services are
9394 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
9395 - Allow the number of introduction points to be as low as 0, rather
9396 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
9398 o Minor bugfixes (IPv6):
9399 - Make IPv6-using clients try harder to find an IPv6 directory
9400 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
9401 - When IPv6 addresses have not been downloaded yet (microdesc
9402 consensus documents don't list relay IPv6 addresses), use hard-
9403 coded addresses for authorities, fallbacks, and configured
9404 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
9405 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
9407 o Minor bugfixes (memory leaks):
9408 - Fix a memory leak when configuring hidden services. Fixes bug
9409 20987; bugfix on 0.3.0.1-alpha.
9411 o Minor bugfixes (portability, also in 0.2.9.9):
9412 - Avoid crashing when Tor is built using headers that contain
9413 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
9414 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
9416 - Fix Libevent detection on platforms without Libevent 1 headers
9417 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
9419 o Minor bugfixes (relay):
9420 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
9421 initializing the keys would reset the DataDirectory to 0700
9422 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
9423 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
9425 o Minor bugfixes (testing):
9426 - Remove undefined behavior from the backtrace generator by removing
9427 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
9429 o Minor bugfixes (unit tests):
9430 - Allow the unit tests to pass even when DNS lookups of bogus
9431 addresses do not fail as expected. Fixes bug 20862 and 20863;
9432 bugfix on unit tests introduced in 0.2.8.1-alpha
9433 through 0.2.9.4-alpha.
9435 o Code simplification and refactoring:
9436 - Refactor code to manipulate global_origin_circuit_list into
9437 separate functions. Closes ticket 20921.
9439 o Documentation (formatting):
9440 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
9441 blocks were incorrectly appearing. Closes ticket 20885.
9443 o Documentation (man page):
9444 - Clarify many options in tor.1 and add some min/max values for
9445 HiddenService options. Closes ticket 21058.
9448 Changes in version 0.2.9.9 - 2017-01-23
9449 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
9450 cause relays and clients to crash, even if they were not built with
9451 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
9452 versions, and also affects 0.3.0.1-alpha: all relays running an affected
9453 version should upgrade.
9455 This release also resolves a client-side onion service reachability
9456 bug, and resolves a pair of small portability issues.
9458 o Major bugfixes (security):
9459 - Downgrade the "-ftrapv" option from "always on" to "only on when
9460 --enable-expensive-hardening is provided." This hardening option,
9461 like others, can turn survivable bugs into crashes -- and having
9462 it on by default made a (relatively harmless) integer overflow bug
9463 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
9464 bugfix on 0.2.9.1-alpha.
9466 o Major bugfixes (client, onion service):
9467 - Fix a client-side onion service reachability bug, where multiple
9468 socks requests to an onion service (or a single slow request)
9469 could cause us to mistakenly mark some of the service's
9470 introduction points as failed, and we cache that failure so
9471 eventually we run out and can't reach the service. Also resolves a
9472 mysterious "Remote server sent bogus reason code 65021" log
9473 warning. The bug was introduced in ticket 17218, where we tried to
9474 remember the circuit end reason as a uint16_t, which mangled
9475 negative values. Partially fixes bug 21056 and fixes bug 20307;
9476 bugfix on 0.2.8.1-alpha.
9478 o Minor features (geoip):
9479 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
9482 o Minor bugfixes (portability):
9483 - Avoid crashing when Tor is built using headers that contain
9484 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
9485 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
9487 - Fix Libevent detection on platforms without Libevent 1 headers
9488 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
9491 Changes in version 0.3.0.1-alpha - 2016-12-19
9492 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
9493 series. It strengthens Tor's link and circuit handshakes by
9494 identifying relays by their Ed25519 keys, improves the algorithm that
9495 clients use to choose and maintain their list of guards, and includes
9496 additional backend support for the next-generation hidden service
9497 design. It also contains numerous other small features and
9498 improvements to security, correctness, and performance.
9500 Below are the changes since 0.2.9.8.
9502 o Major features (guard selection algorithm):
9503 - Tor's guard selection algorithm has been redesigned from the
9504 ground up, to better support unreliable networks and restrictive
9505 sets of entry nodes, and to better resist guard-capture attacks by
9506 hostile local networks. Implements proposal 271; closes
9509 o Major features (next-generation hidden services):
9510 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
9511 prop224 aka "Next Generation Hidden Services". Service and clients
9512 don't use this functionality yet. Closes ticket 19043. Based on
9513 initial code by Alec Heifetz.
9514 - Relays now support the HSDir version 3 protocol, so that they can
9515 can store and serve v3 descriptors. This is part of the next-
9516 generation onion service work detailed in proposal 224. Closes
9519 o Major features (protocol, ed25519 identity keys):
9520 - Relays now use Ed25519 to prove their Ed25519 identities and to
9521 one another, and to clients. This algorithm is faster and more
9522 secure than the RSA-based handshake we've been doing until now.
9523 Implements the second big part of proposal 220; Closes
9525 - Clients now support including Ed25519 identity keys in the EXTEND2
9526 cells they generate. By default, this is controlled by a consensus
9527 parameter, currently disabled. You can turn this feature on for
9528 testing by setting ExtendByEd25519ID in your configuration. This
9529 might make your traffic appear different than the traffic
9530 generated by other users, however. Implements part of ticket
9531 15056; part of proposal 220.
9532 - Relays now understand requests to extend to other relays by their
9533 Ed25519 identity keys. When an Ed25519 identity key is included in
9534 an EXTEND2 cell, the relay will only extend the circuit if the
9535 other relay can prove ownership of that identity. Implements part
9536 of ticket 15056; part of proposal 220.
9538 o Major bugfixes (scheduler):
9539 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
9540 caused the channel scheduler to behave more or less randomly,
9541 rather than preferring channels with higher-priority circuits.
9542 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
9544 o Minor features (controller):
9545 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
9546 rather than "unrecognized." Closes ticket 20389; patch from
9549 o Minor features (diagnostic, directory client):
9550 - Warn when we find an unexpected inconsistency in directory
9551 download status objects. Prevents some negative consequences of
9554 o Minor features (directory authority):
9555 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
9556 default) to control whether authorities should try to probe relays
9557 by their Ed25519 link keys. This option will go away in a few
9558 releases--unless we encounter major trouble in our ed25519 link
9559 protocol rollout, in which case it will serve as a safety option.
9561 o Minor features (directory cache):
9562 - Relays and bridges will now refuse to serve the consensus they
9563 have if they know it is too old for a client to use. Closes
9566 o Minor features (ed25519 link handshake):
9567 - Advertise support for the ed25519 link handshake using the
9568 subprotocol-versions mechanism, so that clients can tell which
9569 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
9571 o Minor features (fingerprinting resistance, authentication):
9572 - Extend the length of RSA keys used for TLS link authentication to
9573 2048 bits. (These weren't used for forward secrecy; for forward
9574 secrecy, we used P256.) Closes ticket 13752.
9576 o Minor features (infrastructure):
9577 - Implement smartlist_add_strdup() function. Replaces the use of
9578 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
9580 o Minor bugfixes (client):
9581 - When clients that use bridges start up with a cached consensus on
9582 disk, they were ignoring it and downloading a new one. Now they
9583 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
9585 o Minor bugfixes (configuration):
9586 - Accept non-space whitespace characters after the severity level in
9587 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
9588 - Support "TByte" and "TBytes" units in options given in bytes.
9589 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
9590 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
9592 o Minor bugfixes (consensus weight):
9593 - Add new consensus method that initializes bw weights to 1 instead
9594 of 0. This prevents a zero weight from making it all the way to
9595 the end (happens in small testing networks) and causing an error.
9596 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
9598 o Minor bugfixes (descriptors):
9599 - Correctly recognise downloaded full descriptors as valid, even
9600 when using microdescriptors as circuits. This affects clients with
9601 FetchUselessDescriptors set, and may affect directory authorities.
9602 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
9604 o Minor bugfixes (directory system):
9605 - Download all consensus flavors, descriptors, and authority
9606 certificates when FetchUselessDescriptors is set, regardless of
9607 whether tor is a directory cache or not. Fixes bug 20667; bugfix
9608 on all recent tor versions.
9609 - Bridges and relays now use microdescriptors (like clients do)
9610 rather than old-style router descriptors. Now bridges will blend
9611 in with clients in terms of the circuits they build. Fixes bug
9612 6769; bugfix on 0.2.3.2-alpha.
9614 o Minor bugfixes (ed25519 certificates):
9615 - Correctly interpret ed25519 certificates that would expire some
9616 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
9618 o Minor bugfixes (hidden services):
9619 - Stop ignoring misconfigured hidden services. Instead, refuse to
9620 start tor until the misconfigurations have been corrected. Fixes
9621 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
9624 o Minor bugfixes (memory leak at exit):
9625 - Fix a small harmless memory leak at exit of the previously unused
9626 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
9629 o Minor bugfixes (util):
9630 - When finishing writing a file to disk, if we were about to replace
9631 the file with the temporary file created before and we fail to
9632 replace it, remove the temporary file so it doesn't stay on disk.
9633 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
9635 o Minor bugfixes (Windows):
9636 - Check for getpagesize before using it to mmap files. This fixes
9637 compilation in some MinGW environments. Fixes bug 20530; bugfix on
9638 0.1.2.1-alpha. Reported by "ice".
9640 o Code simplification and refactoring:
9641 - Abolish all global guard context in entrynodes.c; replace with new
9642 guard_selection_t structure as preparation for proposal 271.
9643 Closes ticket 19858.
9644 - Introduce rend_service_is_ephemeral() that tells if given onion
9645 service is ephemeral. Replace unclear NULL-checkings for service
9646 directory with this function. Closes ticket 20526.
9647 - Extract magic numbers in circuituse.c into defined variables.
9648 - Refactor circuit_is_available_for_use to remove unnecessary check.
9649 - Refactor circuit_predict_and_launch_new for readability and
9650 testability. Closes ticket 18873.
9651 - Refactor large if statement in purpose_needs_anonymity to use
9652 switch statement instead. Closes part of ticket 20077.
9653 - Refactor the hashing API to return negative values for errors, as
9654 is done as throughout the codebase. Closes ticket 20717.
9655 - Remove data structures that were used to index or_connection
9656 objects by their RSA identity digests. These structures are fully
9657 redundant with the similar structures used in the
9658 channel abstraction.
9659 - Remove duplicate code in the channel_write_*cell() functions.
9660 Closes ticket 13827; patch from Pingl.
9661 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
9662 use only purpose_needs_anonymity. Closes part of ticket 20077.
9663 - The code to generate and parse EXTEND and EXTEND2 cells has been
9664 replaced with code automatically generated by the
9668 - Include the "TBits" unit in Tor's man page. Fixes part of bug
9669 20622; bugfix on 0.2.5.1-alpha.
9670 - Change '1' to 'weight_scale' in consensus bw weights calculation
9671 comments, as that is reality. Closes ticket 20273. Patch
9673 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
9674 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
9676 - Stop the man page from incorrectly stating that HiddenServiceDir
9677 must already exist. Fixes 20486.
9678 - Clarify that when ClientRejectInternalAddresses is enabled (which
9679 is the default), multicast DNS hostnames for machines on the local
9680 network (of the form *.local) are also rejected. Closes
9684 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
9685 limit for relays running on a single IP applies to authority IP
9686 addresses as well as to non-authority IP addresses. Closes
9688 - The UseDirectoryGuards torrc option no longer exists: all users
9689 that use entry guards will also use directory guards. Related to
9690 proposal 271; implements part of ticket 20831.
9693 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
9694 from "overcaffeinated".
9695 - Perform the coding style checks when running the tests and fail
9696 when coding style violations are found. Closes ticket 5500.
9697 - Add tests for networkstatus_compute_bw_weights_v10.
9698 - Add unit tests circuit_predict_and_launch_new.
9699 - Extract dummy_origin_circuit_new so it can be used by other
9703 Changes in version 0.2.8.12 - 2016-12-19
9704 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
9705 below) where Tor clients could crash when attempting to visit a
9706 hostile hidden service. Clients are recommended to upgrade as packages
9707 become available for their systems.
9709 It also includes an updated list of fallback directories, backported
9712 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
9713 backported to 0.2.8 in the future.
9715 o Major bugfixes (parsing, security, backported from 0.2.9.8):
9716 - Fix a bug in parsing that could cause clients to read a single
9717 byte past the end of an allocated region. This bug could be used
9718 to cause hardened clients (built with --enable-expensive-hardening)
9719 to crash if they tried to visit a hostile hidden service. Non-
9720 hardened clients are only affected depending on the details of
9721 their platform's memory allocator. Fixes bug 21018; bugfix on
9722 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9723 2016-12-002 and as CVE-2016-1254.
9725 o Minor features (fallback directory list, backported from 0.2.9.8):
9726 - Replace the 81 remaining fallbacks of the 100 originally
9727 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
9728 fallbacks (123 new, 54 existing, 27 removed) generated in December
9729 2016. Resolves ticket 20170.
9731 o Minor features (geoip, backported from 0.2.9.7-rc):
9732 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
9736 Changes in version 0.2.9.8 - 2016-12-19
9737 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
9739 The Tor 0.2.9 series makes mandatory a number of security features
9740 that were formerly optional. It includes support for a new shared-
9741 randomness protocol that will form the basis for next generation
9742 hidden services, includes a single-hop hidden service mode for
9743 optimizing .onion services that don't actually want to be hidden,
9744 tries harder not to overload the directory authorities with excessive
9745 downloads, and supports a better protocol versioning scheme for
9746 improved compatibility with other implementations of the Tor protocol.
9748 And of course, there are numerous other bugfixes and improvements.
9750 This release also includes a fix for a medium-severity issue (bug
9751 21018 below) where Tor clients could crash when attempting to visit a
9752 hostile hidden service. Clients are recommended to upgrade as packages
9753 become available for their systems.
9755 Below are the changes since 0.2.9.7-rc. For a list of all changes
9756 since 0.2.8, see the ReleaseNotes file.
9758 o Major bugfixes (parsing, security):
9759 - Fix a bug in parsing that could cause clients to read a single
9760 byte past the end of an allocated region. This bug could be used
9761 to cause hardened clients (built with --enable-expensive-hardening)
9762 to crash if they tried to visit a hostile hidden service. Non-
9763 hardened clients are only affected depending on the details of
9764 their platform's memory allocator. Fixes bug 21018; bugfix on
9765 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9766 2016-12-002 and as CVE-2016-1254.
9768 o Minor features (fallback directory list):
9769 - Replace the 81 remaining fallbacks of the 100 originally
9770 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
9771 fallbacks (123 new, 54 existing, 27 removed) generated in December
9772 2016. Resolves ticket 20170.
9775 Changes in version 0.2.9.7-rc - 2016-12-12
9776 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
9777 including a few that had prevented tests from passing on
9780 o Minor features (geoip):
9781 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
9784 o Minor bugfix (build):
9785 - The current Git revision when building from a local repository is
9786 now detected correctly when using git worktrees. Fixes bug 20492;
9787 bugfix on 0.2.3.9-alpha.
9789 o Minor bugfixes (directory authority):
9790 - When computing old Tor protocol line version in protover, we were
9791 looking at 0.2.7.5 twice instead of a specific case for
9792 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
9794 o Minor bugfixes (download scheduling):
9795 - Resolve a "bug" warning when considering a download schedule whose
9796 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
9798 o Minor bugfixes (logging):
9799 - Downgrade a harmless log message about the
9800 pending_entry_connections list from "warn" to "info". Mitigates
9803 o Minor bugfixes (memory leak):
9804 - Fix a small memory leak when receiving AF_UNIX connections on a
9805 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
9806 - When moving a signed descriptor object from a source to an
9807 existing destination, free the allocated memory inside that
9808 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
9810 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
9811 - Fix a memory leak and use-after-free error when removing entries
9812 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
9813 0.2.5.5-alpha. Patch from "cypherpunks".
9815 o Minor bugfixes (portability):
9816 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
9817 Fixes bug 20935; bugfix on 0.2.9.6-rc.
9819 o Minor bugfixes (unit tests):
9820 - Stop expecting NetBSD unit tests to report success for ipfw. Part
9821 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
9822 - Fix tolerances in unit tests for monotonic time comparisons
9823 between nanoseconds and microseconds. Previously, we accepted a 10
9824 us difference only, which is not realistic on every platform's
9825 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
9826 - Remove a double-free in the single onion service unit test. Stop
9827 ignoring a return value. Make future changes less error-prone.
9828 Fixes bug 20864; bugfix on 0.2.9.6-rc.
9831 Changes in version 0.2.8.11 - 2016-12-08
9832 Tor 0.2.8.11 backports fixes for additional portability issues that
9833 could prevent Tor from building correctly on OSX Sierra, or with
9834 OpenSSL 1.1. Affected users should upgrade; others can safely stay
9837 o Minor bugfixes (portability):
9838 - Avoid compilation errors when building on OSX Sierra. Sierra began
9839 to support the getentropy() and clock_gettime() APIs, but created
9840 a few problems in doing so. Tor 0.2.9 has a more thorough set of
9841 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
9842 monotonic time interfaces. Fixes bug 20865. Bugfix
9845 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
9846 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
9847 architectures. Closes ticket 20588.
9850 Changes in version 0.2.8.10 - 2016-12-02
9851 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
9852 unusable after they left standby mode. It also backports fixes for
9853 a few portability issues and a small but problematic memory leak.
9855 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
9856 - When Tor leaves standby because of a new application request, open
9857 circuits as needed to serve that request. Previously, we would
9858 potentially wait a very long time. Fixes part of bug 19969; bugfix
9861 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
9862 - Clients now respond to new application stream requests immediately
9863 when they arrive, rather than waiting up to one second before
9864 starting to handle them. Fixes part of bug 19969; bugfix
9867 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
9868 - Work around a bug in the OSX 10.12 SDK that would prevent us from
9869 successfully targeting earlier versions of OSX. Resolves
9872 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
9873 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
9874 20551; bugfix on 0.2.1.1-alpha.
9876 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
9877 - Work around a memory leak in OpenSSL 1.1 when encoding public
9878 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
9880 o Minor features (geoip):
9881 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
9884 Changes in version 0.2.9.6-rc - 2016-12-02
9885 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
9886 version. We hope that it will be ready to become stable soon, and we
9887 encourage everyone to test this release. If no showstopper bugs are
9888 found here, the next 0.2.9 release will be stable.
9890 o Major bugfixes (relay, resolver, logging):
9891 - For relays that don't know their own address, avoid attempting a
9892 local hostname resolve for each descriptor we download. This
9893 will cut down on the number of "Success: chose address 'x.x.x.x'"
9894 log lines, and also avoid confusing clock jumps if the resolver
9895 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
9897 o Minor bugfixes (client, fascistfirewall):
9898 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
9899 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
9901 o Minor bugfixes (hidden services):
9902 - Stop ignoring the anonymity status of saved keys for hidden
9903 services and single onion services when first starting tor.
9904 Instead, refuse to start tor if any hidden service key has been
9905 used in a different hidden service anonymity mode. Fixes bug
9906 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
9908 o Minor bugfixes (portability):
9909 - Work around a bug in the OSX 10.12 SDK that would prevent us from
9910 successfully targeting earlier versions of OSX. Resolves
9912 - Run correctly when built on Windows build environments that
9913 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
9915 o Minor bugfixes (single onion services, Tor2web):
9916 - Stop complaining about long-term one-hop circuits deliberately
9917 created by single onion services and Tor2web. These log messages
9918 are intended to diagnose issue 8387, which relates to circuits
9919 hanging around forever for no reason. Fixes bug 20613; bugfix on
9920 0.2.9.1-alpha. Reported by "pastly".
9922 o Minor bugfixes (unit tests):
9923 - Stop spurious failures in the local interface address discovery
9924 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
9928 - Correct the minimum bandwidth value in torrc.sample, and queue a
9929 corresponding change for torrc.minimal. Closes ticket 20085.
9932 Changes in version 0.2.9.5-alpha - 2016-11-08
9933 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
9934 version. We believe one or two probably remain, and we encourage
9935 everyone to test this release.
9937 o Major bugfixes (client performance):
9938 - Clients now respond to new application stream requests immediately
9939 when they arrive, rather than waiting up to one second before
9940 starting to handle them. Fixes part of bug 19969; bugfix
9943 o Major bugfixes (client reliability):
9944 - When Tor leaves standby because of a new application request, open
9945 circuits as needed to serve that request. Previously, we would
9946 potentially wait a very long time. Fixes part of bug 19969; bugfix
9949 o Major bugfixes (download scheduling):
9950 - When using an exponential backoff schedule, do not give up on
9951 downloading just because we have failed a bunch of times. Since
9952 each delay is longer than the last, retrying indefinitely won't
9953 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
9954 - If a consensus expires while we are waiting for certificates to
9955 download, stop waiting for certificates.
9956 - If we stop waiting for certificates less than a minute after we
9957 started downloading them, do not consider the certificate download
9958 failure a separate failure. Fixes bug 20533; bugfix
9960 - Remove the maximum delay on exponential-backoff scheduling. Since
9961 we now allow an infinite number of failures (see ticket 20536), we
9962 must now allow the time to grow longer on each failure. Fixes part
9963 of bug 20534; bugfix on 0.2.9.1-alpha.
9964 - Make our initial download delays closer to those from 0.2.8. Fixes
9965 another part of bug 20534; bugfix on 0.2.9.1-alpha.
9966 - When determining when to download a directory object, handle times
9967 after 2038 if the operating system supports them. (Someday this
9968 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
9969 - When using exponential backoff in test networks, use a lower
9970 exponent, so the delays do not vary as much. This helps test
9971 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
9973 o Minor features (geoip):
9974 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
9977 o Minor bugfixes (client directory scheduling):
9978 - Treat "relay too busy to answer request" as a failed request and a
9979 reason to back off on our retry frequency. This is safe now that
9980 exponential backoffs retry indefinitely, and avoids a bug where we
9981 would reset our download schedule erroneously. Fixes bug 20593;
9982 bugfix on 0.2.9.1-alpha.
9984 o Minor bugfixes (client, logging):
9985 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
9986 assume all nodes support EXTEND2. Use ntor whenever a key is
9987 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
9988 - On DNSPort, stop logging a BUG warning on a failed hostname
9989 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
9991 o Minor bugfixes (hidden services):
9992 - When configuring hidden services, check every hidden service
9993 directory's permissions. Previously, we only checked the last
9994 hidden service. Fixes bug 20529; bugfix the work to fix 13942
9997 o Minor bugfixes (portability):
9998 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
9999 architectures. Closes ticket 20588.
10000 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
10001 removed the ECDH ciphers which caused the tests to fail on
10002 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
10003 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10004 20551; bugfix on 0.2.1.1-alpha.
10006 o Minor bugfixes (relay bootstrap):
10007 - Ensure relays don't make multiple connections during bootstrap.
10008 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
10010 o Minor bugfixes (relay):
10011 - Work around a memory leak in OpenSSL 1.1 when encoding public
10012 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10013 - Avoid a small memory leak when informing worker threads about
10014 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
10015 - Do not try to parallelize workers more than 16x without the user
10016 explicitly configuring us to do so, even if we do detect more than
10017 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10019 o Minor bugfixes (single onion services):
10020 - Start correctly when creating a single onion service in a
10021 directory that did not previously exist. Fixes bug 20484; bugfix
10024 o Minor bugfixes (testing):
10025 - Avoid a unit test failure on systems with over 16 detectable CPU
10026 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10029 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
10030 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
10031 - Module-level documentation for several more modules. Closes
10032 tickets 19287 and 19290.
10035 Changes in version 0.2.8.9 - 2016-10-17
10036 Tor 0.2.8.9 backports a fix for a security hole in previous versions
10037 of Tor that would allow a remote attacker to crash a Tor client,
10038 hidden service, relay, or authority. All Tor users should upgrade to
10039 this version, or to 0.2.9.4-alpha. Patches will be released for older
10042 o Major features (security fixes, also in 0.2.9.4-alpha):
10043 - Prevent a class of security bugs caused by treating the contents
10044 of a buffer chunk as if they were a NUL-terminated string. At
10045 least one such bug seems to be present in all currently used
10046 versions of Tor, and would allow an attacker to remotely crash
10047 most Tor instances, especially those compiled with extra compiler
10048 hardening. With this defense in place, such bugs can't crash Tor,
10049 though we should still fix them as they occur. Closes ticket
10050 20384 (TROVE-2016-10-001).
10052 o Minor features (geoip):
10053 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10057 Changes in version 0.2.9.4-alpha - 2016-10-17
10058 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
10059 that would allow a remote attacker to crash a Tor client, hidden
10060 service, relay, or authority. All Tor users should upgrade to this
10061 version, or to 0.2.8.9. Patches will be released for older versions
10064 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
10065 previous versions of Tor, including the implementation of a feature to
10066 future- proof the Tor ecosystem against protocol changes, some bug
10067 fixes necessary for Tor Browser to use unix domain sockets correctly,
10068 and several portability improvements. We anticipate that this will be
10069 the last alpha in the Tor 0.2.9 series, and that the next release will
10070 be a release candidate.
10072 o Major features (security fixes):
10073 - Prevent a class of security bugs caused by treating the contents
10074 of a buffer chunk as if they were a NUL-terminated string. At
10075 least one such bug seems to be present in all currently used
10076 versions of Tor, and would allow an attacker to remotely crash
10077 most Tor instances, especially those compiled with extra compiler
10078 hardening. With this defense in place, such bugs can't crash Tor,
10079 though we should still fix them as they occur. Closes ticket
10080 20384 (TROVE-2016-10-001).
10082 o Major features (subprotocol versions):
10083 - Tor directory authorities now vote on a set of recommended
10084 subprotocol versions, and on a set of required subprotocol
10085 versions. Clients and relays that lack support for a _required_
10086 subprotocol version will not start; those that lack support for a
10087 _recommended_ subprotocol version will warn the user to upgrade.
10088 Closes ticket 19958; implements part of proposal 264.
10089 - Tor now uses "subprotocol versions" to indicate compatibility.
10090 Previously, versions of Tor looked at the declared Tor version of
10091 a relay to tell whether they could use a given feature. Now, they
10092 should be able to rely on its declared subprotocol versions. This
10093 change allows compatible implementations of the Tor protocol(s) to
10094 exist without pretending to be 100% bug-compatible with particular
10095 releases of Tor itself. Closes ticket 19958; implements part of
10098 o Minor feature (fallback directories):
10099 - Remove broken fallbacks from the hard-coded fallback directory
10100 list. Closes ticket 20190; patch by teor.
10102 o Minor features (client, directory):
10103 - Since authorities now omit all routers that lack the Running and
10104 Valid flags, we assume that any relay listed in the consensus must
10105 have those flags. Closes ticket 20001; implements part of
10108 o Minor features (compilation, portability):
10109 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
10112 o Minor features (development tools, etags):
10113 - Teach the "make tags" Makefile target how to correctly find
10114 "MOCK_IMPL" function definitions. Patch from nherring; closes
10117 o Minor features (geoip):
10118 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10121 o Minor features (unix domain sockets):
10122 - When configuring a unix domain socket for a SocksPort,
10123 ControlPort, or Hidden service, you can now wrap the address in
10124 quotes, using C-style escapes inside the quotes. This allows unix
10125 domain socket paths to contain spaces.
10127 o Minor features (virtual addresses):
10128 - Increase the maximum number of bits for the IPv6 virtual network
10129 prefix from 16 to 104. In this way, the condition for address
10130 allocation is less restrictive. Closes ticket 20151; feature
10133 o Minor bugfixes (address discovery):
10134 - Stop reordering IP addresses returned by the OS. This makes it
10135 more likely that Tor will guess the same relay IP address every
10136 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
10137 Reported by René Mayrhofer, patch by "cypherpunks".
10139 o Minor bugfixes (client, unix domain sockets):
10140 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
10141 the client address is meaningless. Fixes bug 20261; bugfix
10144 o Minor bugfixes (compilation, OpenBSD):
10145 - Detect Libevent2 functions correctly on systems that provide
10146 libevent2, but where libevent1 is linked with -levent. Fixes bug
10147 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
10149 o Minor bugfixes (configuration):
10150 - When parsing quoted configuration values from the torrc file,
10151 handle windows line endings correctly. Fixes bug 19167; bugfix on
10152 0.2.0.16-alpha. Patch from "Pingl".
10154 o Minor bugfixes (getpass):
10155 - Defensively fix a non-triggerable heap corruption at do_getpass()
10156 to protect ourselves from mistakes in the future. Fixes bug
10157 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
10160 o Minor bugfixes (hidden service):
10161 - Allow hidden services to run on IPv6 addresses even when the
10162 IPv6Exit option is not set. Fixes bug 18357; bugfix
10166 - Add module-level internal documentation for 36 C files that
10167 previously didn't have a high-level overview. Closes ticket #20385.
10169 o Required libraries:
10170 - When building with OpenSSL, Tor now requires version 1.0.1 or
10171 later. OpenSSL 1.0.0 and earlier are no longer supported by the
10172 OpenSSL team, and should not be used. Closes ticket 20303.
10175 Changes in version 0.2.9.3-alpha - 2016-09-23
10176 Tor 0.2.9.3-alpha adds improved support for entities that want to make
10177 high-performance services available through the Tor .onion mechanism
10178 without themselves receiving anonymity as they host those services. It
10179 also tries harder to ensure that all steps on a circuit are using the
10180 strongest crypto possible, strengthens some TLS properties, and
10181 resolves several bugs -- including a pair of crash bugs from the 0.2.8
10182 series. Anybody running an earlier version of 0.2.9.x should upgrade.
10184 o Major bugfixes (crash, also in 0.2.8.8):
10185 - Fix a complicated crash bug that could affect Tor clients
10186 configured to use bridges when replacing a networkstatus consensus
10187 in which one of their bridges was mentioned. OpenBSD users saw
10188 more crashes here, but all platforms were potentially affected.
10189 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
10191 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
10192 - Fix a timing-dependent assertion failure that could occur when we
10193 tried to flush from a circuit after having freed its cells because
10194 of an out-of-memory condition. Fixes bug 20203; bugfix on
10195 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
10198 o Major features (circuit building, security):
10199 - Authorities, relays and clients now require ntor keys in all
10200 descriptors, for all hops (except for rare hidden service protocol
10201 cases), for all circuits, and for all other roles. Part of
10203 - Tor authorities, relays, and clients only use ntor, except for
10204 rare cases in the hidden service protocol. Part of ticket 19163.
10206 o Major features (single-hop "hidden" services):
10207 - Add experimental HiddenServiceSingleHopMode and
10208 HiddenServiceNonAnonymousMode options. When both are set to 1,
10209 every hidden service on a Tor instance becomes a non-anonymous
10210 Single Onion Service. Single Onions make one-hop (direct)
10211 connections to their introduction and renzedvous points. One-hop
10212 circuits make Single Onion servers easily locatable, but clients
10213 remain location-anonymous. This is compatible with the existing
10214 hidden service implementation, and works on the current tor
10215 network without any changes to older relays or clients. Implements
10216 proposal 260, completes ticket 17178. Patch by teor and asn.
10218 o Major features (resource management):
10219 - Tor can now notice it is about to run out of sockets, and
10220 preemptively close connections of lower priority. (This feature is
10221 off by default for now, since the current prioritizing method is
10222 yet not mature enough. You can enable it by setting
10223 "DisableOOSCheck 0", but watch out: it might close some sockets
10224 you would rather have it keep.) Closes ticket 18640.
10226 o Major bugfixes (circuit building):
10227 - Hidden service client-to-intro-point and service-to-rendezvous-
10228 point circuits use the TAP key supplied by the protocol, to avoid
10229 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
10231 o Major bugfixes (compilation, OpenBSD):
10232 - Fix a Libevent-detection bug in our autoconf script that would
10233 prevent Tor from linking successfully on OpenBSD. Patch from
10234 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
10236 o Major bugfixes (hidden services):
10237 - Clients now require hidden services to include the TAP keys for
10238 their intro points in the hidden service descriptor. This prevents
10239 an inadvertent upgrade to ntor, which a malicious hidden service
10240 could use to distinguish clients by consensus version. Fixes bug
10241 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
10243 o Minor features (security, TLS):
10244 - Servers no longer support clients that without AES ciphersuites.
10245 (3DES is no longer considered an acceptable cipher.) We believe
10246 that no such Tor clients currently exist, since Tor has required
10247 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
10249 o Minor feature (fallback directories):
10250 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
10251 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
10252 2016. Closes ticket 20190; patch by teor.
10254 o Minor features (geoip, also in 0.2.8.8):
10255 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
10258 o Minor feature (port flags):
10259 - Add new flags to the *Port options to finer control over which
10260 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
10261 and the synthetic flag OnionTrafficOnly, which is equivalent to
10262 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
10263 18693; patch by "teor".
10265 o Minor features (directory authority):
10266 - After voting, if the authorities decide that a relay is not
10267 "Valid", they no longer include it in the consensus at all. Closes
10268 ticket 20002; implements part of proposal 272.
10270 o Minor features (testing):
10271 - Disable memory protections on OpenBSD when performing our unit
10272 tests for memwipe(). The test deliberately invokes undefined
10273 behavior, and the OpenBSD protections interfere with this. Patch
10274 from "rubiate". Closes ticket 20066.
10276 o Minor features (testing, ipv6):
10277 - Add the single-onion and single-onion-ipv6 chutney targets to
10278 "make test-network-all". This requires a recent chutney version
10279 with the single onion network flavours (git c72a652 or later).
10280 Closes ticket 20072; patch by teor.
10281 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
10282 tests. Remove bridges+hs, as it's somewhat redundant. This
10283 requires a recent chutney version that supports IPv6 clients,
10284 relays, and authorities. Closes ticket 20069; patch by teor.
10286 o Minor features (Tor2web):
10287 - Make Tor2web clients respect ReachableAddresses. This feature was
10288 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
10289 0.2.8.7. Implements feature 20034. Patch by teor.
10291 o Minor features (unit tests):
10292 - We've done significant work to make the unit tests run faster.
10293 - Our link-handshake unit tests now check that when invalid
10294 handshakes fail, they fail with the error messages we expected.
10295 - Our unit testing code that captures log messages no longer
10296 prevents them from being written out if the user asked for them
10297 (by passing --debug or --info or or --notice --warn to the "test"
10298 binary). This change prevents us from missing unexpected log
10299 messages simply because we were looking for others. Related to
10301 - The unit tests now log all warning messages with the "BUG" flag.
10302 Previously, they only logged errors by default. This change will
10303 help us make our testing code more correct, and make sure that we
10304 only hit this code when we mean to. In the meantime, however,
10305 there will be more warnings in the unit test logs than before.
10306 This is preparatory work for ticket 19999.
10307 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
10308 assertion as a test failure.
10310 o Minor bug fixes (circuits):
10311 - Use the CircuitBuildTimeout option whenever
10312 LearnCircuitBuildTimeout is disabled. Previously, we would respect
10313 the option when a user disabled it, but not when it was disabled
10314 because some other option was set. Fixes bug 20073; bugfix on
10315 0.2.4.12-alpha. Patch by teor.
10317 o Minor bugfixes (allocation):
10318 - Change how we allocate memory for large chunks on buffers, to
10319 avoid a (currently impossible) integer overflow, and to waste less
10320 space when allocating unusually large chunks. Fixes bug 20081;
10321 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
10322 - Always include orconfig.h before including any other C headers.
10323 Sometimes, it includes macros that affect the behavior of the
10324 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
10325 first version to use AC_USE_SYSTEM_EXTENSIONS).
10326 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
10327 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
10328 Patch from Gisle Vanem.
10329 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
10330 They apparently require a set of annotations that we aren't
10331 currently using, and they create false positives in our pthreads
10332 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
10334 o Minor bugfixes (directory authority):
10335 - Die with a more useful error when the operator forgets to place
10336 the authority_signing_key file into the keys directory. This
10337 avoids an uninformative assert & traceback about having an invalid
10338 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
10339 - When allowing private addresses, mark Exits that only exit to
10340 private locations as such. Fixes bug 20064; bugfix
10343 o Minor bugfixes (documentation):
10344 - Document the default PathsNeededToBuildCircuits value that's used
10345 by clients when the directory authorities don't set
10346 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
10347 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
10348 - Fix manual for the User option: it takes a username, not a UID.
10349 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
10352 o Minor bugfixes (hidden services):
10353 - Stop logging intro point details to the client log on certain
10354 error conditions. Fixed as part of bug 20012; bugfix on
10355 0.2.4.8-alpha. Patch by teor.
10357 o Minor bugfixes (IPv6, testing):
10358 - Check for IPv6 correctly on Linux when running test networks.
10359 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
10361 o Minor bugfixes (Linux seccomp2 sandbox):
10362 - Add permission to run the sched_yield() and sigaltstack() system
10363 calls, in order to support versions of Tor compiled with asan or
10364 ubsan code that use these calls. Now "sandbox 1" and
10365 "--enable-expensive-hardening" should be compatible on more
10366 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
10368 o Minor bugfixes (logging):
10369 - When logging a message from the BUG() macro, be explicit about
10370 what we were asserting. Previously we were confusing what we were
10371 asserting with what the bug was. Fixes bug 20093; bugfix
10373 - When we are unable to remove the bw_accounting file, do not warn
10374 if the reason we couldn't remove it was that it didn't exist.
10375 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
10377 o Minor bugfixes (option parsing):
10378 - Count unix sockets when counting client listeners (SOCKS, Trans,
10379 NATD, and DNS). This has no user-visible behaviour changes: these
10380 options are set once, and never read. Required for correct
10381 behaviour in ticket 17178. Fixes bug 19677; bugfix on
10382 0.2.6.3-alpha. Patch by teor.
10384 o Minor bugfixes (options):
10385 - Check the consistency of UseEntryGuards and EntryNodes more
10386 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
10388 - Stop changing the configured value of UseEntryGuards on
10389 authorities and Tor2web clients. Fixes bug 20074; bugfix on
10390 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
10393 o Minor bugfixes (Tor2web):
10394 - Prevent Tor2web clients running hidden services, these services
10395 are not anonymous due to the one-hop client paths. Fixes bug
10396 19678. Patch by teor.
10398 o Minor bugfixes (unit tests):
10399 - Fix a shared-random unit test that was failing on big endian
10400 architectures due to internal representation of a integer copied
10401 to a buffer. The test is changed to take a full 32 bytes of data
10402 and use the output of a python script that make the COMMIT and
10403 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
10405 - The tor_tls_server_info_callback unit test no longer crashes when
10406 debug-level logging is turned on. Fixes bug 20041; bugfix
10410 Changes in version 0.2.8.8 - 2016-09-23
10411 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
10412 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
10413 who select public relays as their bridges.
10415 o Major bugfixes (crash):
10416 - Fix a complicated crash bug that could affect Tor clients
10417 configured to use bridges when replacing a networkstatus consensus
10418 in which one of their bridges was mentioned. OpenBSD users saw
10419 more crashes here, but all platforms were potentially affected.
10420 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
10422 o Major bugfixes (relay, OOM handler):
10423 - Fix a timing-dependent assertion failure that could occur when we
10424 tried to flush from a circuit after having freed its cells because
10425 of an out-of-memory condition. Fixes bug 20203; bugfix on
10426 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
10429 o Minor feature (fallback directories):
10430 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
10431 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
10432 2016. Closes ticket 20190; patch by teor.
10434 o Minor features (geoip):
10435 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
10439 Changes in version 0.2.9.2-alpha - 2016-08-24
10440 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
10441 several new features and bugfixes. It also includes an important
10442 authority update and an important bugfix from 0.2.8.7. Everyone who
10443 sets the ReachableAddresses option, and all bridges, are strongly
10444 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
10446 o Directory authority changes (also in 0.2.8.7):
10447 - The "Tonga" bridge authority has been retired; the new bridge
10448 authority is "Bifroest". Closes tickets 19728 and 19690.
10450 o Major bugfixes (client, security, also in 0.2.8.7):
10451 - Only use the ReachableAddresses option to restrict the first hop
10452 in a path. In earlier versions of 0.2.8.x, it would apply to
10453 every hop in the path, with a possible degradation in anonymity
10454 for anyone using an uncommon ReachableAddress setting. Fixes bug
10455 19973; bugfix on 0.2.8.2-alpha.
10457 o Major features (user interface):
10458 - Tor now supports the ability to declare options deprecated, so
10459 that we can recommend that people stop using them. Previously,
10460 this was done in an ad-hoc way. Closes ticket 19820.
10462 o Major bugfixes (directory downloads):
10463 - Avoid resetting download status for consensuses hourly, since we
10464 already have another, smarter retry mechanism. Fixes bug 8625;
10465 bugfix on 0.2.0.9-alpha.
10467 o Minor features (config):
10468 - Warn users when descriptor and port addresses are inconsistent.
10469 Mitigates bug 13953; patch by teor.
10471 o Minor features (geoip):
10472 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
10475 o Minor features (user interface):
10476 - There is a new --list-deprecated-options command-line option to
10477 list all of the deprecated options. Implemented as part of
10480 o Minor bugfixes (code style):
10481 - Fix an integer signedness conversion issue in the case conversion
10482 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
10484 o Minor bugfixes (compilation):
10485 - Build correctly on versions of libevent2 without support for
10486 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
10488 - Fix a compilation warning on GCC versions before 4.6. Our
10489 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
10490 when it is also required as an argument to the compiler pragma.
10491 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
10493 o Minor bugfixes (compilation, also in 0.2.8.7):
10494 - Remove an inappropriate "inline" in tortls.c that was causing
10495 warnings on older versions of GCC. Fixes bug 19903; bugfix
10498 o Minor bugfixes (fallback directories, also in 0.2.8.7):
10499 - Avoid logging a NULL string pointer when loading fallback
10500 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
10501 and 0.2.8.1-alpha. Report and patch by "rubiate".
10503 o Minor bugfixes (logging):
10504 - Log a more accurate message when we fail to dump a microdescriptor.
10505 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
10507 o Minor bugfixes (memory leak):
10508 - Fix a series of slow memory leaks related to parsing torrc files
10509 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
10511 o Deprecated features:
10512 - A number of DNS-cache-related sub-options for client ports are now
10513 deprecated for security reasons, and may be removed in a future
10514 version of Tor. (We believe that client-side DNS caching is a bad
10515 idea for anonymity, and you should not turn it on.) The options
10516 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
10517 UseIPv4Cache, and UseIPv6Cache.
10518 - A number of options are deprecated for security reasons, and may
10519 be removed in a future version of Tor. The options are:
10520 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
10521 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
10522 CloseHSClientCircuitsImmediatelyOnTimeout,
10523 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
10524 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
10525 UseNTorHandshake, and WarnUnsafeSocks.
10526 - The *ListenAddress options are now deprecated as unnecessary: the
10527 corresponding *Port options should be used instead. These options
10528 may someday be removed. The affected options are:
10529 ControlListenAddress, DNSListenAddress, DirListenAddress,
10530 NATDListenAddress, ORListenAddress, SocksListenAddress,
10531 and TransListenAddress.
10534 - Correct the IPv6 syntax in our documentation for the
10535 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
10538 - We no longer include the (dead, deprecated) bufferevent code in
10539 Tor. Closes ticket 19450. Based on a patch from U+039b.
10542 Changes in version 0.2.8.7 - 2016-08-24
10543 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
10544 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
10545 who sets the ReachableAddresses option, and all bridges, are strongly
10546 encouraged to upgrade.
10548 o Directory authority changes:
10549 - The "Tonga" bridge authority has been retired; the new bridge
10550 authority is "Bifroest". Closes tickets 19728 and 19690.
10552 o Major bugfixes (client, security):
10553 - Only use the ReachableAddresses option to restrict the first hop
10554 in a path. In earlier versions of 0.2.8.x, it would apply to
10555 every hop in the path, with a possible degradation in anonymity
10556 for anyone using an uncommon ReachableAddress setting. Fixes bug
10557 19973; bugfix on 0.2.8.2-alpha.
10559 o Minor features (geoip):
10560 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
10563 o Minor bugfixes (compilation):
10564 - Remove an inappropriate "inline" in tortls.c that was causing
10565 warnings on older versions of GCC. Fixes bug 19903; bugfix
10568 o Minor bugfixes (fallback directories):
10569 - Avoid logging a NULL string pointer when loading fallback
10570 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
10571 and 0.2.8.1-alpha. Report and patch by "rubiate".
10574 Changes in version 0.2.9.1-alpha - 2016-08-08
10575 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
10576 series. It improves our support for hardened builds and compiler
10577 warnings, deploys some critical infrastructure for improvements to
10578 hidden services, includes a new timing backend that we hope to use for
10579 better support for traffic padding, makes it easier for programmers to
10580 log unexpected events, and contains other small improvements to
10581 security, correctness, and performance.
10583 Below are the changes since 0.2.8.6.
10585 o New system requirements:
10586 - Tor now requires Libevent version 2.0.10-stable or later. Older
10587 versions of Libevent have less efficient backends for several
10588 platforms, and lack the DNS code that we use for our server-side
10589 DNS support. This implements ticket 19554.
10590 - Tor now requires zlib version 1.2 or later, for security,
10591 efficiency, and (eventually) gzip support. (Back when we started,
10592 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
10593 released in 2003. We recommend the latest version.)
10595 o Major features (build, hardening):
10596 - Tor now builds with -ftrapv by default on compilers that support
10597 it. This option detects signed integer overflow (which C forbids),
10598 and turns it into a hard-failure. We do not apply this option to
10599 code that needs to run in constant time to avoid side-channels;
10600 instead, we use -fwrapv in that code. Closes ticket 17983.
10601 - When --enable-expensive-hardening is selected, stop applying the
10602 clang/gcc sanitizers to code that needs to run in constant time.
10603 Although we are aware of no introduced side-channels, we are not
10604 able to prove that there are none. Related to ticket 17983.
10606 o Major features (compilation):
10607 - Our big list of extra GCC warnings is now enabled by default when
10608 building with GCC (or with anything like Clang that claims to be
10609 GCC-compatible). To make all warnings into fatal compilation
10610 errors, pass --enable-fatal-warnings to configure. Closes
10612 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
10613 turn on C and POSIX extensions. (Previously, we attempted to do
10614 this on an ad hoc basis.) Closes ticket 19139.
10616 o Major features (directory authorities, hidden services):
10617 - Directory authorities can now perform the shared randomness
10618 protocol specified by proposal 250. Using this protocol, directory
10619 authorities generate a global fresh random value every day. In the
10620 future, this value will be used by hidden services to select
10621 HSDirs. This release implements the directory authority feature;
10622 the hidden service side will be implemented in the future as part
10623 of proposal 224. Resolves ticket 16943; implements proposal 250.
10625 o Major features (downloading, random exponential backoff):
10626 - When we fail to download an object from a directory service, wait
10627 for an (exponentially increasing) randomized amount of time before
10628 retrying, rather than a fixed interval as we did before. This
10629 prevents a group of Tor instances from becoming too synchronized,
10630 or a single Tor instance from becoming too predictable, in its
10631 download schedule. Closes ticket 15942.
10633 o Major bugfixes (exit policies):
10634 - Avoid disclosing exit outbound bind addresses, configured port
10635 bind addresses, and local interface addresses in relay descriptors
10636 by default under ExitPolicyRejectPrivate. Instead, only reject
10637 these (otherwise unlisted) addresses if
10638 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
10639 0.2.7.2-alpha. Patch by teor.
10641 o Major bugfixes (hidden service client):
10642 - Allow Tor clients with appropriate controllers to work with
10643 FetchHidServDescriptors set to 0. Previously, this option also
10644 disabled descriptor cache lookup, thus breaking hidden services
10645 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
10647 o Minor features (build, hardening):
10648 - Detect and work around a libclang_rt problem that would prevent
10649 clang from finding __mulodi4() on some 32-bit platforms, and thus
10650 keep -ftrapv from linking on those systems. Closes ticket 19079.
10651 - When building on a system without runtime support for the runtime
10652 hardening options, try to log a useful warning at configuration
10653 time, rather than an incomprehensible warning at link time. If
10654 expensive hardening was requested, this warning becomes an error.
10655 Closes ticket 18895.
10657 o Minor features (code safety):
10658 - In our integer-parsing functions, ensure that maxiumum value we
10659 give is no smaller than the minimum value. Closes ticket 19063;
10662 o Minor features (controller):
10663 - Implement new GETINFO queries for all downloads that use
10664 download_status_t to schedule retries. This allows controllers to
10665 examine the schedule for pending downloads. Closes ticket 19323.
10666 - Allow controllers to configure basic client authorization on
10667 hidden services when they create them with the ADD_ONION control
10668 command. Implements ticket 15588. Patch by "special".
10669 - Fire a STATUS_SERVER controller event whenever the hibernation
10670 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
10672 o Minor features (directory authority):
10673 - Directory authorities now only give the Guard flag to a relay if
10674 they are also giving it the Stable flag. This change allows us to
10675 simplify path selection for clients. It should have minimal effect
10676 in practice, since >99% of Guards already have the Stable flag.
10677 Implements ticket 18624.
10678 - Directory authorities now write their v3-status-votes file out to
10679 disk earlier in the consensus process, so we have a record of the
10680 votes even if we abort the consensus process. Resolves
10683 o Minor features (hidden service):
10684 - Stop being so strict about the payload length of "rendezvous1"
10685 cells. We used to be locked in to the "TAP" handshake length, and
10686 now we can handle better handshakes like "ntor". Resolves
10689 o Minor features (infrastructure, time):
10690 - Tor now uses the operating system's monotonic timers (where
10691 available) for internal fine-grained timing. Previously we would
10692 look at the system clock, and then attempt to compensate for the
10693 clock running backwards. Closes ticket 18908.
10694 - Tor now includes an improved timer backend, so that we can
10695 efficiently support tens or hundreds of thousands of concurrent
10696 timers, as will be needed for some of our planned anti-traffic-
10697 analysis work. This code is based on William Ahern's "timeout.c"
10698 project, which implements a "tickless hierarchical timing wheel".
10699 Closes ticket 18365.
10701 o Minor features (logging):
10702 - Provide a more useful warning message when configured with an
10703 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
10704 - When dumping unparseable router descriptors, optionally store them
10705 in separate files, named by digest, up to a configurable size
10706 limit. You can change the size limit by setting the
10707 MaxUnparseableDescSizeToLog option, and disable this feature by
10708 setting that option to 0. Closes ticket 18322.
10709 - Add a set of macros to check nonfatal assertions, for internal
10710 use. Migrating more of our checks to these should help us avoid
10711 needless crash bugs. Closes ticket 18613.
10713 o Minor features (performance):
10714 - Changer the "optimistic data" extension from "off by default" to
10715 "on by default". The default was ordinarily overridden by a
10716 consensus option, but when clients were bootstrapping for the
10717 first time, they would not have a consensus to get the option
10718 from. Changing this default When fetching a consensus for the
10719 first time, use optimistic data. This saves a round-trip during
10720 startup. Closes ticket 18815.
10722 o Minor features (relay, usability):
10723 - When the directory authorities refuse a bad relay's descriptor,
10724 encourage the relay operator to contact us. Many relay operators
10725 won't notice this line in their logs, but it's a win if even a few
10726 learn why we don't like what their relay was doing. Resolves
10729 o Minor features (testing):
10730 - Let backtrace tests work correctly under AddressSanitizer. Fixes
10731 part of bug 18934; bugfix on 0.2.5.2-alpha.
10732 - Move the test-network.sh script to chutney, and modify tor's test-
10733 network.sh to call the (newer) chutney version when available.
10734 Resolves ticket 19116. Patch by teor.
10735 - Use the lcov convention for marking lines as unreachable, so that
10736 we don't count them when we're generating test coverage data.
10737 Update our coverage tools to understand this convention. Closes
10740 o Minor bugfixes (bootstrap):
10741 - Remember the directory we fetched the consensus or previous
10742 certificates from, and use it to fetch future authority
10743 certificates. This change improves bootstrapping performance.
10744 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
10746 o Minor bugfixes (build):
10747 - The test-stem and test-network makefile targets now depend only on
10748 the tor binary that they are testing. Previously, they depended on
10749 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
10750 patch from "cypherpunks".
10752 o Minor bugfixes (circuits):
10753 - Make sure extend_info_from_router() is only called on servers.
10754 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
10756 o Minor bugfixes (compilation):
10757 - When building with Clang, use a full set of GCC warnings.
10758 (Previously, we included only a subset, because of the way we
10759 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
10761 o Minor bugfixes (directory authority):
10762 - Authorities now sort the "package" lines in their votes, for ease
10763 of debugging. (They are already sorted in consensus documents.)
10764 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
10765 - When parsing a detached signature, make sure we use the length of
10766 the digest algorithm instead of an hardcoded DIGEST256_LEN in
10767 order to avoid comparing bytes out-of-bounds with a smaller digest
10768 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
10770 o Minor bugfixes (documentation):
10771 - Document the --passphrase-fd option in the tor manpage. Fixes bug
10772 19504; bugfix on 0.2.7.3-rc.
10773 - Fix the description of the --passphrase-fd option in the
10774 tor-gencert manpage. The option is used to pass the number of a
10775 file descriptor to read the passphrase from, not to read the file
10776 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
10778 o Minor bugfixes (ephemeral hidden service):
10779 - When deleting an ephemeral hidden service, close its intro points
10780 even if they are not completely open. Fixes bug 18604; bugfix
10783 o Minor bugfixes (guard selection):
10784 - Use a single entry guard even if the NumEntryGuards consensus
10785 parameter is not provided. Fixes bug 17688; bugfix
10787 - Don't mark guards as unreachable if connection_connect() fails.
10788 That function fails for local reasons, so it shouldn't reveal
10789 anything about the status of the guard. Fixes bug 14334; bugfix
10792 o Minor bugfixes (hidden service client):
10793 - Increase the minimum number of internal circuits we preemptively
10794 build from 2 to 3, so a circuit is available when a client
10795 connects to another onion service. Fixes bug 13239; bugfix
10798 o Minor bugfixes (logging):
10799 - When logging a directory ownership mismatch, log the owning
10800 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
10802 o Minor bugfixes (memory leaks):
10803 - Fix a small, uncommon memory leak that could occur when reading a
10804 truncated ed25519 key file. Fixes bug 18956; bugfix
10807 o Minor bugfixes (testing):
10808 - Allow clients to retry HSDirs much faster in test networks. Fixes
10809 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
10810 - Disable ASAN's detection of segmentation faults while running
10811 test_bt.sh, so that we can make sure that our own backtrace
10812 generation code works. Fixes another aspect of bug 18934; bugfix
10813 on 0.2.5.2-alpha. Patch from "cypherpunks".
10814 - Fix the test-network-all target on out-of-tree builds by using the
10815 correct path to the test driver script. Fixes bug 19421; bugfix
10818 o Minor bugfixes (time):
10819 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
10820 bugfix on all released tor versions.
10821 - When computing the difference between two times in milliseconds,
10822 we now round to the nearest millisecond correctly. Previously, we
10823 could sometimes round in the wrong direction. Fixes bug 19428;
10824 bugfix on 0.2.2.2-alpha.
10826 o Minor bugfixes (user interface):
10827 - Display a more accurate number of suppressed messages in the log
10828 rate-limiter. Previously, there was a potential integer overflow
10829 in the counter. Now, if the number of messages hits a maximum, the
10830 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
10832 - Fix a typo in the passphrase prompt for the ed25519 identity key.
10833 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
10835 o Code simplification and refactoring:
10836 - Remove redundant declarations of the MIN macro. Closes
10838 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
10839 Closes ticket 18462; patch from "icanhasaccount".
10840 - Split the 600-line directory_handle_command_get function into
10841 separate functions for different URL types. Closes ticket 16698.
10844 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
10845 ticket 19153. Patch from "U+039b".
10847 o Removed features:
10848 - Remove support for "GET /tor/bytes.txt" DirPort request, and
10849 "GETINFO dir-usage" controller request, which were only available
10850 via a compile-time option in Tor anyway. Feature was added in
10851 0.2.2.1-alpha. Resolves ticket 19035.
10852 - There is no longer a compile-time option to disable support for
10853 TransPort. (If you don't want TransPort; just don't use it.) Patch
10854 from "U+039b". Closes ticket 19449.
10857 - Run more workqueue tests as part of "make check". These had
10858 previously been implemented, but you needed to know special
10859 command-line options to enable them.
10860 - We now have unit tests for our code to reject zlib "compression
10861 bombs". (Fortunately, the code works fine.)
10864 Changes in version 0.2.8.6 - 2016-08-02
10866 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
10868 The Tor 0.2.8 series improves client bootstrapping performance,
10869 completes the authority-side implementation of improved identity
10870 keys for relays, and includes numerous bugfixes and performance
10871 improvements throughout the program. This release continues to
10872 improve the coverage of Tor's test suite. For a full list of
10873 changes since Tor 0.2.7, see the ReleaseNotes file.
10875 Changes since 0.2.8.5-rc:
10877 o Minor features (geoip):
10878 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
10881 o Minor bugfixes (compilation):
10882 - Fix a compilation warning in the unit tests on systems where char
10883 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
10885 o Minor bugfixes (fallback directories):
10886 - Remove 1 fallback that was on the hardcoded list, then opted-out,
10887 leaving 89 of the 100 fallbacks originally introduced in Tor
10888 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
10890 o Minor bugfixes (Linux seccomp2 sandbox):
10891 - Allow more syscalls when running with "Sandbox 1" enabled:
10892 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
10893 some systems, these are required for Tor to start. Fixes bug
10894 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
10895 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
10896 so that get_interface_address6_via_udp_socket_hack() can work.
10897 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
10900 Changes in version 0.2.8.5-rc - 2016-07-07
10901 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
10902 series. If we find no new bugs or regressions here, the first stable
10903 0.2.8 release will be identical to it. It has a few small bugfixes
10904 against previous versions.
10906 o Directory authority changes:
10907 - Urras is no longer a directory authority. Closes ticket 19271.
10909 o Major bugfixes (heartbeat):
10910 - Fix a regression that would crash Tor when the periodic
10911 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
10912 0.2.8.1-alpha. Reported by "kubaku".
10914 o Minor features (build):
10915 - Tor now again builds with the recent OpenSSL 1.1 development
10916 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
10917 - When building manual pages, set the timezone to "UTC", so that the
10918 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
10919 Patch from intrigeri.
10921 o Minor bugfixes (fallback directory selection):
10922 - Avoid errors during fallback selection if there are no eligible
10923 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
10926 o Minor bugfixes (IPv6, microdescriptors):
10927 - Don't check node addresses when we only have a routerstatus. This
10928 allows IPv6-only clients to bootstrap by fetching microdescriptors
10929 from fallback directory mirrors. (The microdescriptor consensus
10930 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
10933 o Minor bugfixes (logging):
10934 - Reduce pointlessly verbose log messages when directory servers
10935 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
10936 0.2.8.1-alpha. Patch by teor.
10937 - When a fallback directory changes its fingerprint from the hard-
10938 coded fingerprint, log a less severe, more explanatory log
10939 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
10941 o Minor bugfixes (Linux seccomp2 sandboxing):
10942 - Allow statistics to be written to disk when "Sandbox 1" is
10943 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
10944 0.2.6.1-alpha respectively.
10946 o Minor bugfixes (user interface):
10947 - Remove a warning message "Service [scrubbed] not found after
10948 descriptor upload". This message appears when one uses HSPOST
10949 control command to upload a service descriptor. Since there is
10950 only a descriptor and no service, showing this message is
10951 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
10953 o Fallback directory list:
10954 - Add a comment to the generated fallback directory list that
10955 explains how to comment out unsuitable fallbacks in a way that's
10956 compatible with the stem fallback parser.
10957 - Update fallback whitelist and blacklist based on relay operator
10958 emails. Blacklist unsuitable (non-working, over-volatile)
10959 fallbacks. Resolves ticket 19071. Patch by teor.
10960 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
10961 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
10962 ticket 19071; patch by teor.
10965 Changes in version 0.2.8.4-rc - 2016-06-15
10966 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
10967 If we find no new bugs or regressions here, the first stable 0.2.8
10968 release will be identical to it. It has a few small bugfixes against
10971 o Major bugfixes (user interface):
10972 - Correctly give a warning in the cases where a relay is specified
10973 by nickname, and one such relay is found, but it is not officially
10974 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
10976 o Minor features (build):
10977 - Tor now builds once again with the recent OpenSSL 1.1 development
10978 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
10980 o Minor features (geoip):
10981 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
10984 o Minor bugfixes (compilation):
10985 - Cause the unit tests to compile correctly on mingw64 versions that
10986 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
10988 o Minor bugfixes (downloading):
10989 - Predict more correctly whether we'll be downloading over HTTP when
10990 we determine the maximum length of a URL. This should avoid a
10991 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
10995 Changes in version 0.2.8.3-alpha - 2016-05-26
10996 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
10997 the course of the 0.2.8 development cycle. It improves the behavior of
10998 directory clients, fixes several crash bugs, fixes a gap in compiler
10999 hardening, and allows the full integration test suite to run on
11002 o Major bugfixes (security, client, DNS proxy):
11003 - Stop a crash that could occur when a client running with DNSPort
11004 received a query with multiple address types, and the first
11005 address type was not supported. Found and fixed by Scott Dial.
11006 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11008 o Major bugfixes (security, compilation):
11009 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
11010 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
11011 cause a compiler warning, thereby making other checks fail, and
11012 needlessly disabling compiler-hardening support. Fixes one case of
11013 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
11015 o Major bugfixes (security, directory authorities):
11016 - Fix a crash and out-of-bounds write during authority voting, when
11017 the list of relays includes duplicate ed25519 identity keys. Fixes
11018 bug 19032; bugfix on 0.2.8.2-alpha.
11020 o Major bugfixes (client, bootstrapping):
11021 - Check if bootstrap consensus downloads are still needed when the
11022 linked connection attaches. This prevents tor making unnecessary
11023 begindir-style connections, which are the only directory
11024 connections tor clients make since the fix for 18483 was merged.
11025 - Fix some edge cases where consensus download connections may not
11026 have been closed, even though they were not needed. Related to fix
11028 - Make relays retry consensus downloads the correct number of times,
11029 rather than the more aggressive client retry count. Fixes part of
11031 - Stop downloading consensuses when we have a consensus, even if we
11032 don't have all the certificates for it yet. Fixes bug 18809;
11033 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
11035 o Major bugfixes (directory mirrors):
11036 - Decide whether to advertise begindir support in the the same way
11037 we decide whether to advertise our DirPort. Allowing these
11038 decisions to become out-of-sync led to surprising behavior like
11039 advertising begindir support when hibernation made us not
11040 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
11043 o Major bugfixes (IPv6 bridges, client):
11044 - Actually use IPv6 addresses when selecting directory addresses for
11045 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
11048 o Major bugfixes (key management):
11049 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11050 pointer to the previous (uninitialized) key value. The impact here
11051 should be limited to a difficult-to-trigger crash, if OpenSSL is
11052 running an engine that makes key generation failures possible, or
11053 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11054 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11057 o Major bugfixes (testing):
11058 - Fix a bug that would block 'make test-network-all' on systems where
11059 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
11060 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
11061 bugfix on 0.2.8.1-alpha.
11063 o Minor features (clients):
11064 - Make clients, onion services, and bridge relays always use an
11065 encrypted begindir connection for directory requests. Resolves
11066 ticket 18483. Patch by "teor".
11068 o Minor features (fallback directory mirrors):
11069 - Give each fallback the same weight for client selection; restrict
11070 fallbacks to one per operator; report fallback directory detail
11071 changes when rebuilding list; add new fallback directory mirrors
11072 to the whitelist; and many other minor simplifications and fixes.
11073 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
11074 0.2.8.1-alpha; patch by "teor".
11075 - Replace the 21 fallbacks generated in January 2016 and included in
11076 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
11077 2016. Closes task 17158; patch by "teor".
11079 o Minor features (geoip):
11080 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
11083 o Minor bugfixes (assert, portability):
11084 - Fix an assertion failure in memarea.c on systems where "long" is
11085 shorter than the size of a pointer. Fixes bug 18716; bugfix
11088 o Minor bugfixes (bootstrap):
11089 - Consistently use the consensus download schedule for authority
11090 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
11092 o Minor bugfixes (build):
11093 - Remove a pair of redundant AM_CONDITIONAL declarations from
11094 configure.ac. Fixes one final case of bug 17744; bugfix
11096 - Resolve warnings when building on systems that are concerned with
11097 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
11099 - When libscrypt.h is found, but no libscrypt library can be linked,
11100 treat libscrypt as absent. Fixes bug 19161; bugfix
11103 o Minor bugfixes (client):
11104 - Turn all TestingClientBootstrap* into non-testing torrc options.
11105 This changes simply renames them by removing "Testing" in front of
11106 them and they do not require TestingTorNetwork to be enabled
11107 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
11108 - Make directory node selection more reliable, mainly for IPv6-only
11109 clients and clients with few reachable addresses. Fixes bug 18929;
11110 bugfix on 0.2.8.1-alpha. Patch by "teor".
11112 o Minor bugfixes (controller, microdescriptors):
11113 - Make GETINFO dir/status-vote/current/consensus conform to the
11114 control specification by returning "551 Could not open cached
11115 consensus..." when not caching consensuses. Fixes bug 18920;
11116 bugfix on 0.2.2.6-alpha.
11118 o Minor bugfixes (crypto, portability):
11119 - The SHA3 and SHAKE routines now produce the correct output on Big
11120 Endian systems. No code calls either algorithm yet, so this is
11121 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
11122 - Tor now builds again with the recent OpenSSL 1.1 development
11123 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
11126 o Minor bugfixes (directories):
11127 - When fetching extrainfo documents, compare their SHA256 digests
11128 and Ed25519 signing key certificates with the routerinfo that led
11129 us to fetch them, rather than with the most recent routerinfo.
11130 Otherwise we generate many spurious warnings about mismatches.
11131 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
11133 o Minor bugfixes (logging):
11134 - When we can't generate a signing key because OfflineMasterKey is
11135 set, do not imply that we should have been able to load it. Fixes
11136 bug 18133; bugfix on 0.2.7.2-alpha.
11137 - Stop periodic_event_dispatch() from blasting twelve lines per
11138 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
11139 - When rejecting a misformed INTRODUCE2 cell, only log at
11140 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
11142 o Minor bugfixes (pluggable transports):
11143 - Avoid reporting a spurious error when we decide that we don't need
11144 to terminate a pluggable transport because it has already exited.
11145 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
11147 o Minor bugfixes (pointer arithmetic):
11148 - Fix a bug in memarea_alloc() that could have resulted in remote
11149 heap write access, if Tor had ever passed an unchecked size to
11150 memarea_alloc(). Fortunately, all the sizes we pass to
11151 memarea_alloc() are pre-checked to be less than 128 kilobytes.
11152 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
11155 o Minor bugfixes (relays):
11156 - Consider more config options when relays decide whether to
11157 regenerate their descriptor. Fixes more of bug 12538; bugfix
11159 - Resolve some edge cases where we might launch an ORPort
11160 reachability check even when DisableNetwork is set. Noticed while
11161 fixing bug 18616; bugfix on 0.2.3.9-alpha.
11163 o Minor bugfixes (statistics):
11164 - We now include consensus downloads via IPv6 in our directory-
11165 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
11167 o Minor bugfixes (testing):
11168 - Allow directories in small networks to bootstrap by skipping
11169 DirPort checks when the consensus has no exits. Fixes bug 19003;
11170 bugfix on 0.2.8.1-alpha. Patch by teor.
11171 - Fix a small memory leak that would occur when the
11172 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
11173 bugfix on 0.2.5.2-alpha.
11175 o Minor bugfixes (time handling):
11176 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
11177 field. Otherwise, our unit tests crash on Windows. Fixes bug
11178 18977; bugfix on 0.2.2.25-alpha.
11181 - Document the contents of the 'datadir/keys' subdirectory in the
11182 manual page. Closes ticket 17621.
11183 - Stop recommending use of nicknames to identify relays in our
11184 MapAddress documentation. Closes ticket 18312.
11187 Changes in version 0.2.8.2-alpha - 2016-03-28
11188 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
11189 bugs in earlier versions of Tor, including some that prevented
11190 authorities using Tor 0.2.7.x from running correctly. IPv6 and
11191 directory support should also be much improved.
11193 o New system requirements:
11194 - Tor no longer supports versions of OpenSSL with a broken
11195 implementation of counter mode. (This bug was present in OpenSSL
11196 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
11197 longer runs with, these versions.
11198 - Tor no longer attempts to support platforms where the "time_t"
11199 type is unsigned. (To the best of our knowledge, only OpenVMS does
11200 this, and Tor has never actually built on OpenVMS.) Closes
11202 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
11203 later (released in 2008 and 2009 respectively). If you are
11204 building Tor from the git repository instead of from the source
11205 distribution, and your tools are older than this, you will need to
11206 upgrade. Closes ticket 17732.
11208 o Major bugfixes (security, pointers):
11209 - Avoid a difficult-to-trigger heap corruption attack when extending
11210 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11211 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11212 Reported by Guido Vranken.
11214 o Major bugfixes (bridges, pluggable transports):
11215 - Modify the check for OR connections to private addresses. Allow
11216 bridges on private addresses, including pluggable transports that
11217 ignore the (potentially private) address in the bridge line. Fixes
11218 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
11220 o Major bugfixes (compilation):
11221 - Repair hardened builds under the clang compiler. Previously, our
11222 use of _FORTIFY_SOURCE would conflict with clang's address
11223 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
11225 o Major bugfixes (crash on shutdown):
11226 - Correctly handle detaching circuits from muxes when shutting down.
11227 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
11228 - Fix an assert-on-exit bug related to counting memory usage in
11229 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
11231 o Major bugfixes (crash on startup):
11232 - Fix a segfault during startup: If a Unix domain socket was
11233 configured as listener (such as a ControlSocket or a SocksPort
11234 "unix:" socket), and tor was started as root but not configured to
11235 switch to another user, tor would segfault while trying to string
11236 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
11239 o Major bugfixes (dns proxy mode, crash):
11240 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
11241 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
11243 o Major bugfixes (relays, bridge clients):
11244 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
11245 bridge clients use the address configured in the bridge line.
11246 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
11249 o Major bugfixes (voting):
11250 - Actually enable support for authorities to match routers by their
11251 Ed25519 identities. Previously, the code had been written, but
11252 some debugging code that had accidentally been left in the
11253 codebase made it stay turned off. Fixes bug 17702; bugfix
11255 - When collating votes by Ed25519 identities, authorities now
11256 include a "NoEdConsensus" flag if the ed25519 value (or lack
11257 thereof) for a server does not reflect the majority consensus.
11258 Related to bug 17668; bugfix on 0.2.7.2-alpha.
11259 - When generating a vote with keypinning disabled, never include two
11260 entries for the same ed25519 identity. This bug was causing
11261 authorities to generate votes that they could not parse when a
11262 router violated key pinning by changing its RSA identity but
11263 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
11264 18318. Bugfix on 0.2.7.2-alpha.
11266 o Minor features (security, win32):
11267 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
11268 attack. Fixes bug 18123; bugfix on all tor versions. Patch
11271 o Minor features (bug-resistance):
11272 - Make Tor survive errors involving connections without a
11273 corresponding event object. Previously we'd fail with an
11274 assertion; now we produce a log message. Related to bug 16248.
11276 o Minor features (build):
11277 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
11278 as having possible IPFW support. Closes ticket 18448. Patch from
11279 Steven Chamberlain.
11281 o Minor features (code hardening):
11282 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
11283 level code, to harden against accidental failures to NUL-
11284 terminate. Part of ticket 17852. Patch from jsturgix. Found
11287 o Minor features (crypto):
11288 - Validate the hard-coded Diffie-Hellman parameters and ensure that
11289 p is a safe prime, and g is a suitable generator. Closes
11292 o Minor features (geoip):
11293 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
11296 o Minor features (hidden service directory):
11297 - Streamline relay-side hsdir handling: when relays consider whether
11298 to accept an uploaded hidden service descriptor, they no longer
11299 check whether they are one of the relays in the network that is
11300 "supposed" to handle that descriptor. Implements ticket 18332.
11302 o Minor features (IPv6):
11303 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
11304 to 1, tor prefers IPv6 directory addresses.
11305 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
11306 avoids using IPv4 for client OR and directory connections.
11307 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
11308 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
11309 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
11311 o Minor features (linux seccomp2 sandbox):
11312 - Reject attempts to change our Address with "Sandbox 1" enabled.
11313 Changing Address with Sandbox turned on would never actually work,
11314 but previously it would fail in strange and confusing ways. Found
11315 while fixing 18548.
11317 o Minor features (robustness):
11318 - Exit immediately with an error message if the code attempts to use
11319 Libevent without having initialized it. This should resolve some
11320 frequently-made mistakes in our unit tests. Closes ticket 18241.
11322 o Minor features (unix domain sockets):
11323 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
11324 Unix domain sockets without checking the permissions on the parent
11325 directory. (Tor checks permissions by default because some
11326 operating systems only check permissions on the parent directory.
11327 However, some operating systems do look at permissions on the
11328 socket, and tor's default check is unneeded.) Closes ticket 18458.
11331 o Minor bugfixes (exit policies, security):
11332 - Refresh an exit relay's exit policy when interface addresses
11333 change. Previously, tor only refreshed the exit policy when the
11334 configured external address changed. Fixes bug 18208; bugfix on
11335 0.2.7.3-rc. Patch by teor.
11337 o Minor bugfixes (security, hidden services):
11338 - Prevent hidden services connecting to client-supplied rendezvous
11339 addresses that are reserved as internal or multicast. Fixes bug
11340 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
11342 o Minor bugfixes (build):
11343 - Do not link the unit tests against both the testing and non-
11344 testing versions of the static libraries. Fixes bug 18490; bugfix
11346 - Avoid spurious failures from configure files related to calling
11347 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
11348 0.2.0.1-alpha. Patch from "cypherpunks".
11349 - Silence spurious clang-scan warnings in the ed25519_donna code by
11350 explicitly initializing some objects. Fixes bug 18384; bugfix on
11351 0.2.7.2-alpha. Patch by teor.
11353 o Minor bugfixes (client, bootstrap):
11354 - Count receipt of new microdescriptors as progress towards
11355 bootstrapping. Previously, with EntryNodes set, Tor might not
11356 successfully repopulate the guard set on bootstrapping. Fixes bug
11357 16825; bugfix on 0.2.3.1-alpha.
11359 o Minor bugfixes (code correctness):
11360 - Update to the latest version of Trunnel, which tries harder to
11361 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
11362 by clang address sanitizer. Fixes bug 18373; bugfix
11365 o Minor bugfixes (configuration):
11366 - Fix a tiny memory leak when parsing a port configuration ending in
11367 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
11369 o Minor bugfixes (containers):
11370 - If we somehow attempt to construct a heap with more than
11371 1073741822 elements, avoid an integer overflow when maintaining
11372 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
11374 o Minor bugfixes (correctness):
11375 - Fix a bad memory handling bug that would occur if we had queued a
11376 cell on a channel's incoming queue. Fortunately, we can't actually
11377 queue a cell like that as our code is constructed today, but it's
11378 best to avoid this kind of error, even if there isn't any code
11379 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
11381 o Minor bugfixes (directory):
11382 - When generating a URL for a directory server on an IPv6 address,
11383 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
11384 on 0.2.3.9-alpha. Patch from Malek.
11386 o Minor bugfixes (fallback directory mirrors):
11387 - When requesting extrainfo descriptors from a trusted directory
11388 server, check whether it is an authority or a fallback directory
11389 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
11390 0.2.4.7-alpha. Reported by atagar, patch by teor.
11392 o Minor bugfixes (hidden service, client):
11393 - Handle the case where the user makes several fast consecutive
11394 requests to the same .onion address. Previously, the first six
11395 requests would each trigger a descriptor fetch, each picking a
11396 directory (there are 6 overall) and the seventh one would fail
11397 because no directories were left, thereby triggering a close on
11398 all current directory connections asking for the hidden service.
11399 The solution here is to not close the connections if we have
11400 pending directory fetches. Fixes bug 15937; bugfix
11403 o Minor bugfixes (hidden service, control port):
11404 - Add the onion address to the HS_DESC event for the UPLOADED action
11405 both on success or failure. It was previously hardcoded with
11406 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
11408 o Minor bugfixes (hidden service, directory):
11409 - Bridges now refuse "rendezvous2" (hidden service descriptor)
11410 publish attempts. Suggested by ticket 18332.
11412 o Minor bugfixes (linux seccomp2 sandbox):
11413 - Allow the setrlimit syscall, and the prlimit and prlimit64
11414 syscalls, which some libc implementations use under the hood.
11415 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
11416 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
11417 enabled and no DNS resolvers configured. This should help TAILS
11418 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
11419 - Fix the sandbox's interoperability with unix domain sockets under
11420 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
11422 o Minor bugfixes (logging):
11423 - When logging information about an unparsable networkstatus vote or
11424 consensus, do not say "vote" when we mean consensus. Fixes bug
11425 18368; bugfix on 0.2.0.8-alpha.
11426 - Scrub service name in "unrecognized service ID" log messages.
11427 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
11428 - Downgrade logs and backtraces about IP versions to info-level.
11429 Only log backtraces once each time tor runs. Assists in diagnosing
11430 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
11431 Christian, patch by teor.
11433 o Minor bugfixes (memory safety):
11434 - Avoid freeing an uninitialized pointer when opening a socket fails
11435 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
11436 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
11438 - Correctly duplicate addresses in get_interface_address6_list().
11439 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
11440 patch by "cypherpunks".
11441 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
11443 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
11444 18672; bugfix on 0.2.5.1-alpha.
11446 o Minor bugfixes (private directory):
11447 - Prevent a race condition when creating private directories. Fixes
11448 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
11449 Patch from jsturgix. Found with Flawfinder.
11451 o Minor bugfixes (test networks, IPv6):
11452 - Allow internal IPv6 addresses in descriptors in test networks.
11453 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
11456 o Minor bugfixes (testing):
11457 - We no longer disable assertions in the unit tests when coverage is
11458 enabled. Instead, we require you to say --disable-asserts-in-tests
11459 to the configure script if you need assertions disabled in the
11460 unit tests (for example, if you want to perform branch coverage).
11461 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
11463 o Minor bugfixes (time parsing):
11464 - Avoid overflow in tor_timegm when parsing dates in and after 2038
11465 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
11466 0.0.2pre14. Patch by teor.
11468 o Minor bugfixes (tor-gencert):
11469 - Correctly handle the case where an authority operator enters a
11470 passphrase but sends an EOF before sending a newline. Fixes bug
11471 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
11473 o Code simplification and refactoring:
11474 - Quote all the string interpolations in configure.ac -- even those
11475 which we are pretty sure can't contain spaces. Closes ticket
11476 17744. Patch from zerosion.
11477 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
11478 inplace, so there's no need to have a separate implementation for
11479 the non-inplace code. Closes ticket 18258. Patch from Malek.
11480 - Simplify return types for some crypto functions that can't
11481 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
11484 - Change build messages to refer to "Fedora" instead of "Fedora
11485 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
11486 Patches from "icanhasaccount" and "cypherpunks".
11488 o Removed features:
11489 - We no longer maintain an internal freelist in memarea.c.
11490 Allocators should be good enough to make this code unnecessary,
11491 and it's doubtful that it ever had any performance benefit.
11494 - Fix several warnings from clang's address sanitizer produced in
11496 - Treat backtrace test failures as expected on FreeBSD until we
11497 solve bug 17808. Closes ticket 18204.
11500 Changes in version 0.2.8.1-alpha - 2016-02-04
11501 Tor 0.2.8.1-alpha is the first alpha release in its series. It
11502 includes numerous small features and bugfixes against previous Tor
11503 versions, and numerous small infrastructure improvements. The most
11504 notable features are a set of improvements to the directory subsystem.
11506 o Major features (security, Linux):
11507 - When Tor starts as root on Linux and is told to switch user ID, it
11508 can now retain the capability to bind to low ports. By default,
11509 Tor will do this only when it's switching user ID and some low
11510 ports have been configured. You can change this behavior with the
11511 new option KeepBindCapabilities. Closes ticket 8195.
11513 o Major features (directory system):
11514 - When bootstrapping multiple consensus downloads at a time, use the
11515 first one that starts downloading, and close the rest. This
11516 reduces failures when authorities or fallback directories are slow
11517 or down. Together with the code for feature 15775, this feature
11518 should reduces failures due to fallback churn. Implements ticket
11519 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
11520 "mikeperry" and "teor".
11521 - Include a trial list of 21 default fallback directories, generated
11522 in January 2016, based on an opt-in survey of suitable relays.
11523 Doing this should make clients bootstrap more quickly and reliably,
11524 and reduce the load on the directory authorities. Closes ticket
11525 15775. Patch by "teor".
11526 Candidates identified using an OnionOO script by "weasel", "teor",
11527 "gsathya", and "karsten".
11528 - Previously only relays that explicitly opened a directory port
11529 (DirPort) accepted directory requests from clients. Now all
11530 relays, with and without a DirPort, accept and serve tunneled
11531 directory requests that they receive through their ORPort. You can
11532 disable this behavior using the new DirCache option. Closes
11535 o Major key updates:
11536 - Update the V3 identity key for the dannenberg directory authority:
11537 it was changed on 18 November 2015. Closes task 17906. Patch
11540 o Minor features (security, clock):
11541 - Warn when the system clock appears to move back in time (when the
11542 state file was last written in the future). Tor doesn't know that
11543 consensuses have expired if the clock is in the past. Patch by
11544 "teor". Implements ticket 17188.
11546 o Minor features (security, exit policies):
11547 - ExitPolicyRejectPrivate now rejects more private addresses by
11548 default. Specifically, it now rejects the relay's outbound bind
11549 addresses (if configured), and the relay's configured port
11550 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
11551 0.2.0.11-alpha. Patch by "teor".
11553 o Minor features (security, memory erasure):
11554 - Set the unused entries in a smartlist to NULL. This helped catch
11555 a (harmless) bug, and shouldn't affect performance too much.
11556 Implements ticket 17026.
11557 - Use SecureMemoryWipe() function to securely clean memory on
11558 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
11559 Implements feature 17986.
11560 - Use explicit_bzero or memset_s when present. Previously, we'd use
11561 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
11562 from <logan@hackers.mu> and <selven@hackers.mu>.
11563 - Make memwipe() do nothing when passed a NULL pointer or buffer of
11564 zero size. Check size argument to memwipe() for underflow. Fixes
11565 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
11568 o Minor features (security, RNG):
11569 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
11570 positively are not allowed to fail. Previously we depended on
11571 internal details of OpenSSL's behavior. Closes ticket 17686.
11572 - Never use the system entropy output directly for anything besides
11573 seeding the PRNG. When we want to generate important keys, instead
11574 of using system entropy directly, we now hash it with the PRNG
11575 stream. This may help resist certain attacks based on broken OS
11576 entropy implementations. Closes part of ticket 17694.
11577 - Use modern system calls (like getentropy() or getrandom()) to
11578 generate strong entropy on platforms that have them. Closes
11581 o Minor features (accounting):
11582 - Added two modes to the AccountingRule option: One for limiting
11583 only the number of bytes sent ("AccountingRule out"), and one for
11584 limiting only the number of bytes received ("AccountingRule in").
11585 Closes ticket 15989; patch from "unixninja92".
11587 o Minor features (build):
11588 - Since our build process now uses "make distcheck", we no longer
11589 force "make dist" to depend on "make check". Closes ticket 17893;
11590 patch from "cypherpunks."
11591 - Tor now builds successfully with the recent OpenSSL 1.1
11592 development branch, and with the latest LibreSSL. Closes tickets
11593 17549, 17921, and 17984.
11595 o Minor features (controller):
11596 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
11597 tickets 16774 and 17817. Patch by George Tankersley.
11598 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
11599 service descriptor from a service's local hidden service
11600 descriptor cache. Closes ticket 14846.
11601 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
11602 controllers can examine the the reject rules added by
11603 ExitPolicyRejectPrivate. This makes it easier for stem to display
11606 o Minor features (crypto):
11607 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
11609 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
11610 - When allocating a digest state object, allocate no more space than
11611 we actually need. Previously, we would allocate as much space as
11612 the state for the largest algorithm would need. This change saves
11613 up to 672 bytes per circuit. Closes ticket 17796.
11614 - Improve performance when hashing non-multiple of 8 sized buffers,
11615 based on Andrew Moon's public domain SipHash-2-4 implementation.
11616 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
11618 o Minor features (directory downloads):
11619 - Wait for busy authorities and fallback directories to become non-
11620 busy when bootstrapping. (A similar change was made in 6c443e987d
11621 for directory caches chosen from the consensus.) Closes ticket
11622 17864; patch by "teor".
11623 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
11624 directory mirrors. The default is 1; set it to 0 to disable
11625 fallbacks. Implements ticket 17576. Patch by "teor".
11627 o Minor features (geoip):
11628 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
11631 o Minor features (IPv6):
11632 - Add an argument 'ipv6=address:orport' to the DirAuthority and
11633 FallbackDir torrc options, to specify an IPv6 address for an
11634 authority or fallback directory. Add hard-coded ipv6 addresses for
11635 directory authorities that have them. Closes ticket 17327; patch
11636 from Nick Mathewson and "teor".
11637 - Add address policy assume_action support for IPv6 addresses.
11638 - Limit IPv6 mask bits to 128.
11639 - Warn when comparing against an AF_UNSPEC address in a policy, it's
11640 almost always a bug. Closes ticket 17863; patch by "teor".
11641 - Allow users to configure directory authorities and fallback
11642 directory servers with IPv6 addresses and ORPorts. Resolves
11644 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
11645 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
11646 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
11647 17638; bugfix on 0.0.2pre8. Patch by "teor".
11649 o Minor features (logging):
11650 - When logging to syslog, allow a tag to be added to the syslog
11651 identity (the string prepended to every log message). The tag can
11652 be configured with SyslogIdentityTag and defaults to none. Setting
11653 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
11656 o Minor features (portability):
11657 - Use timingsafe_memcmp() where available. Closes ticket 17944;
11658 patch from <logan@hackers.mu>.
11660 o Minor features (relay, address discovery):
11661 - Add a family argument to get_interface_addresses_raw() and
11662 subfunctions to make network interface address interogation more
11663 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
11664 types of interfaces from the operating system. Resolves
11666 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
11667 fails to enumerate interface addresses using the platform-specific
11668 API, have it rely on the UDP socket fallback technique to try and
11669 find out what IP addresses (both IPv4 and IPv6) our machine has.
11670 Resolves ticket 17951.
11672 o Minor features (replay cache):
11673 - The replay cache now uses SHA256 instead of SHA1. Implements
11674 feature 8961. Patch by "teor", issue reported by "rransom".
11676 o Minor features (unix file permissions):
11677 - Defer creation of Unix sockets until after setuid. This avoids
11678 needing CAP_CHOWN and CAP_FOWNER when using systemd's
11679 CapabilityBoundingSet, or chown and fowner when using SELinux.
11680 Implements part of ticket 17562. Patch from Jamie Nguyen.
11681 - If any directory created by Tor is marked as group readable, the
11682 filesystem group is allowed to be either the default GID or the
11683 root user. Allowing root to read the DataDirectory prevents the
11684 need for CAP_READ_SEARCH when using systemd's
11685 CapabilityBoundingSet, or dac_read_search when using SELinux.
11686 Implements part of ticket 17562. Patch from Jamie Nguyen.
11687 - Introduce a new DataDirectoryGroupReadable option. If it is set to
11688 1, the DataDirectory will be made readable by the default GID.
11689 Implements part of ticket 17562. Patch from Jamie Nguyen.
11691 o Minor bugfixes (accounting):
11692 - The max bandwidth when using 'AccountRule sum' is now correctly
11693 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
11694 from "unixninja92".
11696 o Minor bugfixes (code correctness):
11697 - When closing an entry connection, generate a warning if we should
11698 have sent an end cell for it but we haven't. Fixes bug 17876;
11699 bugfix on 0.2.3.2-alpha.
11700 - Assert that allocated memory held by the reputation code is freed
11701 according to its internal counters. Fixes bug 17753; bugfix
11703 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
11706 o Minor bugfixes (compilation):
11707 - Mark all object files that include micro-revision.i as depending
11708 on it, so as to make parallel builds more reliable. Fixes bug
11709 17826; bugfix on 0.2.5.1-alpha.
11710 - Don't try to use the pthread_condattr_setclock() function unless
11711 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
11712 17819; bugfix on 0.2.6.3-alpha.
11713 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
11715 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
11716 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
11717 - Fix search for libevent libraries on OpenBSD (and other systems
11718 that install libevent 1 and libevent 2 in parallel). Fixes bug
11719 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
11720 - Isolate environment variables meant for tests from the rest of the
11721 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
11722 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
11724 - Remove config.log only from make distclean, not from make clean.
11725 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
11727 o Minor bugfixes (crypto):
11728 - Check the return value of HMAC() and assert on failure. Fixes bug
11729 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
11731 o Minor bugfixes (fallback directories):
11732 - Mark fallbacks as "too busy" when they return a 503 response,
11733 rather than just marking authorities. Fixes bug 17572; bugfix on
11734 0.2.4.7-alpha. Patch by "teor".
11736 o Minor bugfixes (IPv6):
11737 - Update the limits in max_dl_per_request for IPv6 address length.
11738 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
11740 o Minor bugfixes (linux seccomp2 sandbox):
11741 - Fix a crash when using offline master ed25519 keys with the Linux
11742 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
11744 o Minor bugfixes (logging):
11745 - In log messages that include a function name, use __FUNCTION__
11746 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
11747 with clang __PRETTY_FUNCTION__ has extra information we don't
11748 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
11750 - Remove needless quotes from a log message about unparseable
11751 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
11753 o Minor bugfixes (portability):
11754 - Remove an #endif from configure.ac so that we correctly detect the
11755 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
11758 o Minor bugfixes (relays):
11759 - Check that both the ORPort and DirPort (if present) are reachable
11760 before publishing a relay descriptor. Otherwise, relays publish a
11761 descriptor with DirPort 0 when the DirPort reachability test takes
11762 longer than the ORPort reachability test. Fixes bug 18050; bugfix
11763 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
11765 o Minor bugfixes (relays, hidden services):
11766 - Refuse connection requests to private OR addresses unless
11767 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
11768 then refuse to send any cells to a private address. Fixes bugs
11769 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
11771 o Minor bugfixes (safe logging):
11772 - When logging a malformed hostname received through socks4, scrub
11773 it if SafeLogging says we should. Fixes bug 17419; bugfix
11776 o Minor bugfixes (statistics code):
11777 - Consistently check for overflow in round_*_to_next_multiple_of
11778 functions, and add unit tests with additional and maximal values.
11779 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
11780 - Handle edge cases in the laplace functions: avoid division by
11781 zero, avoid taking the log of zero, and silence clang type
11782 conversion warnings using round and trunc. Add unit tests for edge
11783 cases with maximal values. Fixes part of bug 13192; bugfix
11786 o Minor bugfixes (testing):
11787 - The test for log_heartbeat was incorrectly failing in timezones
11788 with non-integer offsets. Instead of comparing the end of the time
11789 string against a constant, compare it to the output of
11790 format_local_iso_time when given the correct input. Fixes bug
11791 18039; bugfix on 0.2.5.4-alpha.
11792 - Make unit tests pass on IPv6-only systems, and systems without
11793 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
11794 bugfix on 0.2.7.3-rc. Patch by "teor".
11795 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
11797 - Check the full results of SHA256 and SHA512 digests in the unit
11798 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
11800 o Code simplification and refactoring:
11801 - Move logging of redundant policy entries in
11802 policies_parse_exit_policy_internal into its own function. Closes
11803 ticket 17608; patch from "juce".
11804 - Extract the more complicated parts of circuit_mark_for_close()
11805 into a new function that we run periodically before circuits are
11806 freed. This change removes more than half of the functions
11807 currently in the "blob". Closes ticket 17218.
11808 - Clean up a little duplicated code in
11809 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
11811 - Decouple the list of streams waiting to be attached to circuits
11812 from the overall connection list. This change makes it possible to
11813 attach streams quickly while simplifying Tor's callgraph and
11814 avoiding O(N) scans of the entire connection list. Closes
11816 - When a direct directory request fails immediately on launch,
11817 instead of relaunching that request from inside the code that
11818 launches it, instead mark the connection for teardown. This change
11819 simplifies Tor's callback and prevents the directory-request
11820 launching code from invoking itself recursively. Closes
11822 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
11823 use them. Closes ticket 17926.
11826 - Add a description of the correct use of the '--keygen' command-
11827 line option. Closes ticket 17583; based on text by 's7r'.
11828 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
11829 - Explain actual minima for BandwidthRate. Closes ticket 16382.
11830 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
11831 - Mention torspec URL in the manpage and point the reader to it
11832 whenever we mention a document that belongs in torspce. Fixes
11835 o Removed features:
11836 - Remove client-side support for connecting to Tor relays running
11837 versions of Tor before 0.2.3.6-alpha. These relays didn't support
11838 the v3 TLS handshake protocol, and are no longer allowed on the
11839 Tor network. Implements the client side of ticket 11150. Based on
11840 patches by Tom van der Woerdt.
11843 - Add unit tests to check for common RNG failure modes, such as
11844 returning all zeroes, identical values, or incrementing values
11845 (OpenSSL's rand_predictable feature). Patch by "teor".
11846 - Log more information when the backtrace tests fail. Closes ticket
11847 17892. Patch from "cypherpunks."
11848 - Always test both ed25519 backends, so that we can be sure that our
11849 batch-open replacement code works. Part of ticket 16794.
11850 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
11851 portion of ticket 16831.
11852 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
11853 util_format.c, directory.c, and options_validate.c. Closes tickets
11854 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
11856 - Unit tests for directory_handle_command_get. Closes ticket 17004.
11857 Patch from Reinaldo de Souza Jr.
11860 Changes in version 0.2.7.6 - 2015-12-10
11861 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
11862 well as a minor bug in hidden service reliability.
11864 o Major bugfixes (guard selection):
11865 - Actually look at the Guard flag when selecting a new directory
11866 guard. When we implemented the directory guard design, we
11867 accidentally started treating all relays as if they have the Guard
11868 flag during guard selection, leading to weaker anonymity and worse
11869 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
11872 o Minor features (geoip):
11873 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
11876 o Minor bugfixes (compilation):
11877 - When checking for net/pfvar.h, include netinet/in.h if possible.
11878 This fixes transparent proxy detection on OpenBSD. Fixes bug
11879 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
11880 - Fix a compilation warning with Clang 3.6: Do not check the
11881 presence of an address which can never be NULL. Fixes bug 17781.
11883 o Minor bugfixes (correctness):
11884 - When displaying an IPv6 exit policy, include the mask bits
11885 correctly even when the number is greater than 31. Fixes bug
11886 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
11887 - The wrong list was used when looking up expired intro points in a
11888 rend service object, causing what we think could be reachability
11889 issues for hidden services, and triggering a BUG log. Fixes bug
11890 16702; bugfix on 0.2.7.2-alpha.
11891 - Fix undefined behavior in the tor_cert_checksig function. Fixes
11892 bug 17722; bugfix on 0.2.7.2-alpha.
11895 Changes in version 0.2.7.5 - 2015-11-20
11896 The Tor 0.2.7 release series is dedicated to the memory of Tor user
11897 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
11898 tirelessly to advocate human rights regardless of national borders,
11899 and oppose the encroachments of mass surveillance. He opposed national
11900 exceptionalism, he brought clarity to legal and policy debates, he
11901 understood and predicted the impact of mass surveillance on the world,
11902 and he laid the groundwork for resisting it. While serving on the Tor
11903 Project's board of directors, he brought us his uncompromising focus
11904 on technical excellence in the service of humankind. Caspar was an
11905 inimitable force for good and a wonderful friend. He was kind,
11906 humorous, generous, gallant, and believed we should protect one
11907 another without exception. We honor him here for his ideals, his
11908 efforts, and his accomplishments. Please honor his memory with works
11909 that would make him proud.
11911 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
11913 The 0.2.7 series adds a more secure identity key type for relays,
11914 improves cryptography performance, resolves several longstanding
11915 hidden-service performance issues, improves controller support for
11916 hidden services, and includes small bugfixes and performance
11917 improvements throughout the program. This release series also includes
11918 more tests than before, and significant simplifications to which parts
11919 of Tor invoke which others.
11921 (This release contains no code changes since 0.2.7.4-rc.)
11924 Changes in version 0.2.7.4-rc - 2015-10-21
11925 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
11926 fixes some important memory leaks, and a scary-looking (but mostly
11927 harmless in practice) invalid-read bug. It also has a few small
11928 bugfixes, notably fixes for compilation and portability on different
11929 platforms. If no further significant bounds are found, the next
11930 release will the the official stable release.
11932 o Major bugfixes (security, correctness):
11933 - Fix an error that could cause us to read 4 bytes before the
11934 beginning of an openssl string. This bug could be used to cause
11935 Tor to crash on systems with unusual malloc implementations, or
11936 systems with unusual hardening installed. Fixes bug 17404; bugfix
11939 o Major bugfixes (correctness):
11940 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
11941 bug 17401; bugfix on 0.2.7.3-rc.
11943 o Major bugfixes (memory leaks):
11944 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
11945 17398; bugfix on 0.2.6.1-alpha.
11946 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
11947 17402; bugfix on 0.2.7.3-rc.
11948 - Fix a memory leak when reading an expired signing key from disk.
11949 Fixes bug 17403; bugfix on 0.2.7.2-rc.
11951 o Minor features (geoIP):
11952 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
11955 o Minor bugfixes (compilation):
11956 - Repair compilation with the most recent (unreleased, alpha)
11957 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
11958 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
11959 17251; bugfix on 0.2.7.2-alpha.
11960 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
11961 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
11963 o Minor bugfixes (portability):
11964 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
11965 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
11968 o Minor bugfixes (sandbox):
11969 - Add the "hidserv-stats" filename to our sandbox filter for the
11970 HiddenServiceStatistics option to work properly. Fixes bug 17354;
11971 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
11973 o Minor bugfixes (testing):
11974 - Add unit tests for get_interface_address* failure cases. Fixes bug
11975 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
11976 - Fix breakage when running 'make check' with BSD make. Fixes bug
11977 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
11978 - Make the get_ifaddrs_* unit tests more tolerant of different
11979 network configurations. (Don't assume every test box has an IPv4
11980 address, and don't assume every test box has a non-localhost
11981 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
11982 - Skip backtrace tests when backtrace support is not compiled in.
11983 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
11987 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
11988 - Note that HiddenServicePorts can take a unix domain socket. Closes
11992 Changes in version 0.2.7.3-rc - 2015-09-25
11993 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
11994 contains numerous usability fixes for Ed25519 keys, safeguards against
11995 several misconfiguration problems, significant simplifications to
11996 Tor's callgraph, and numerous bugfixes and small features.
11998 This is the most tested release of Tor to date. The unit tests cover
11999 39.40% of the code, and the integration tests (accessible with "make
12000 test-full-online", requiring stem and chutney and a network
12001 connection) raise the coverage to 64.49%.
12003 o Major features (security, hidden services):
12004 - Hidden services, if using the EntryNodes option, are required to
12005 use more than one EntryNode, in order to avoid a guard discovery
12006 attack. (This would only affect people who had configured hidden
12007 services and manually specified the EntryNodes option with a
12008 single entry-node. The impact was that it would be easy to
12009 remotely identify the guard node used by such a hidden service.
12010 See ticket for more information.) Fixes ticket 14917.
12012 o Major features (Ed25519 keys, keypinning):
12013 - The key-pinning option on directory authorities is now advisory-
12014 only by default. In a future version, or when the AuthDirPinKeys
12015 option is set, pins are enforced again. Disabling key-pinning
12016 seemed like a good idea so that we can survive the fallout of any
12017 usability problems associated with Ed25519 keys. Closes
12020 o Major features (Ed25519 performance):
12021 - Improve the speed of Ed25519 operations and Curve25519 keypair
12022 generation when built targeting 32 bit x86 platforms with SSE2
12023 available. Implements ticket 16535.
12024 - Improve the runtime speed of Ed25519 signature verification by
12025 using Ed25519-donna's batch verification support. Implements
12028 o Major features (performance testing):
12029 - The test-network.sh script now supports performance testing.
12030 Requires corresponding chutney performance testing changes. Patch
12031 by "teor". Closes ticket 14175.
12033 o Major features (relay, Ed25519):
12034 - Significant usability improvements for Ed25519 key management. Log
12035 messages are better, and the code can recover from far more
12036 failure conditions. Thanks to "s7r" for reporting and diagnosing
12038 - Add a new OfflineMasterKey option to tell Tor never to try loading
12039 or generating a secret Ed25519 identity key. You can use this in
12040 combination with tor --keygen to manage offline and/or encrypted
12041 Ed25519 keys. Implements ticket 16944.
12042 - Add a --newpass option to allow changing or removing the
12043 passphrase of an encrypted key with tor --keygen. Implements part
12045 - On receiving a HUP signal, check to see whether the Ed25519
12046 signing key has changed, and reload it if so. Closes ticket 16790.
12048 o Major bugfixes (relay, Ed25519):
12049 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
12050 0.2.7.2-alpha. Reported by "s7r".
12051 - Improve handling of expired signing keys with offline master keys.
12052 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
12054 o Minor features (client-side privacy):
12055 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
12056 lifespan when IsolateSOCKSAuth and streams with SOCKS
12057 authentication are attached to the circuit. This allows
12058 applications like TorBrowser to manage circuit lifetime on their
12059 own. Implements feature 15482.
12060 - When logging malformed hostnames from SOCKS5 requests, respect
12061 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
12063 o Minor features (compilation):
12064 - Give a warning as early as possible when trying to build with an
12065 unsupported OpenSSL version. Closes ticket 16901.
12066 - Fail during configure if we're trying to build against an OpenSSL
12067 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
12068 which started requiring ECC.
12070 o Minor features (geoip):
12071 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
12074 o Minor features (hidden services):
12075 - Relays need to have the Fast flag to get the HSDir flag. As this
12076 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
12077 drop. This change should make some attacks against the hidden
12078 service directory system harder. Fixes ticket 15963.
12079 - Turn on hidden service statistics collection by setting the torrc
12080 option HiddenServiceStatistics to "1" by default. (This keeps
12081 track only of the fraction of traffic used by hidden services, and
12082 the total number of hidden services in existence.) Closes
12084 - Client now uses an introduction point failure cache to know when
12085 to fetch or keep a descriptor in their cache. Previously, failures
12086 were recorded implicitly, but not explicitly remembered. Closes
12089 o Minor features (testing, authorities, documentation):
12090 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
12091 explicitly manage consensus flags in testing networks. Patch by
12092 "robgjansen", modified by "teor". Implements part of ticket 14882.
12094 o Minor bugfixes (security, exit policies):
12095 - ExitPolicyRejectPrivate now also rejects the relay's published
12096 IPv6 address (if any), and any publicly routable IPv4 or IPv6
12097 addresses on any local interfaces. ticket 17027. Patch by "teor".
12098 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
12100 o Minor bug fixes (torrc exit policies):
12101 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
12102 produce IPv6 wildcard addresses. Previously they would produce
12103 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
12104 of bug 16069; bugfix on 0.2.4.7-alpha.
12105 - When parsing torrc ExitPolicies, we now warn for a number of cases
12106 where the user's intent is likely to differ from Tor's actual
12107 behavior. These include: using an IPv4 address with an accept6 or
12108 reject6 line; using "private" on an accept6 or reject6 line; and
12109 including any ExitPolicy lines after accept *:* or reject *:*.
12110 Related to ticket 16069.
12111 - When parsing torrc ExitPolicies, we now issue an info-level
12112 message when expanding an "accept/reject *" line to include both
12113 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
12114 - In each instance above, usage advice is provided to avoid the
12115 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
12116 16069; bugfix on 0.2.4.7-alpha.
12118 o Minor bugfixes (authority):
12119 - Don't assign "HSDir" to a router if it isn't Valid and Running.
12120 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
12121 - Downgrade log messages about Ed25519 key issues if they are in old
12122 cached router descriptors. Fixes part of bug 16286; bugfix
12124 - When we find an Ed25519 key issue in a cached descriptor, stop
12125 saying the descriptor was just "uploaded". Fixes another part of
12126 bug 16286; bugfix on 0.2.7.2-alpha.
12128 o Minor bugfixes (control port):
12129 - Repair a warning and a spurious result when getting the maximum
12130 number of file descriptors from the controller. Fixes bug 16697;
12131 bugfix on 0.2.7.2-alpha.
12133 o Minor bugfixes (correctness):
12134 - When calling channel_free_list(), avoid calling smartlist_remove()
12135 while inside a FOREACH loop. This partially reverts commit
12136 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
12137 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
12139 o Minor bugfixes (documentation):
12140 - Advise users on how to configure separate IPv4 and IPv6 exit
12141 policies in the manpage and sample torrcs. Related to ticket 16069.
12142 - Fix the usage message of tor-resolve(1) so that it no longer lists
12143 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
12144 - Fix an error in the manual page and comments for
12145 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
12146 required "ORPort connectivity". While this is true, it is in no
12147 way unique to the HSDir flag. Of all the flags, only HSDirs need a
12148 DirPort configured in order for the authorities to assign that
12149 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
12152 o Minor bugfixes (Ed25519):
12153 - Fix a memory leak when reading router descriptors with expired
12154 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
12156 o Minor bugfixes (linux seccomp2 sandbox):
12157 - Allow bridge authorities to run correctly under the seccomp2
12158 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
12159 - Allow routers with ed25519 keys to run correctly under the
12160 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
12162 o Minor bugfixes (open file limit):
12163 - Fix set_max_file_descriptors() to set by default the max open file
12164 limit to the current limit when setrlimit() fails. Fixes bug
12165 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
12167 o Minor bugfixes (portability):
12168 - Try harder to normalize the exit status of the Tor process to the
12169 standard-provided range. Fixes bug 16975; bugfix on every version
12171 - Check correctly for Windows socket errors in the workqueue
12172 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
12173 - Fix the behavior of crypto_rand_time_range() when told to consider
12174 times before 1970. (These times were possible when running in a
12175 simulated network environment where time()'s output starts at
12176 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
12177 - Restore correct operation of TLS client-cipher detection on
12178 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
12180 o Minor bugfixes (relay):
12181 - Ensure that worker threads actually exit when a fatal error or
12182 shutdown is indicated. This fix doesn't currently affect the
12183 behavior of Tor, because Tor workers never indicates fatal error
12184 or shutdown except in the unit tests. Fixes bug 16868; bugfix
12186 - Unblock threads before releasing the work queue mutex to ensure
12187 predictable scheduling behavior. Fixes bug 16644; bugfix
12190 o Code simplification and refactoring:
12191 - Change the function that's called when we need to retry all
12192 downloads so that it only reschedules the downloads to happen
12193 immediately, rather than launching them all at once itself. This
12194 further simplifies Tor's callgraph.
12195 - Move some format-parsing functions out of crypto.c and
12196 crypto_curve25519.c into crypto_format.c and/or util_format.c.
12197 - Move the client-only parts of init_keys() into a separate
12198 function. Closes ticket 16763.
12199 - Simplify the microdesc_free() implementation so that it no longer
12200 appears (to code analysis tools) to potentially invoke a huge
12201 suite of other microdesc functions.
12202 - Simply the control graph further by deferring the inner body of
12203 directory_all_unreachable() into a callback. Closes ticket 16762.
12204 - Treat the loss of an owning controller as equivalent to a SIGTERM
12205 signal. This removes a tiny amount of duplicated code, and
12206 simplifies our callgraph. Closes ticket 16788.
12207 - When generating an event to send to the controller, we no longer
12208 put the event over the network immediately. Instead, we queue
12209 these events, and use a Libevent callback to deliver them. This
12210 change simplifies Tor's callgraph by reducing the number of
12211 functions from which all other Tor functions are reachable. Closes
12213 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
12214 that try to scan or compile every file on Unix won't decide that
12216 - Remove the unused "nulterminate" argument from buf_pullup().
12219 - Recommend a 40 GB example AccountingMax in torrc.sample rather
12220 than a 4 GB max. Closes ticket 16742.
12221 - Include the TUNING document in our source tarball. It is referred
12222 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
12226 - The internal pure-C tor-fw-helper tool is now removed from the Tor
12227 distribution, in favor of the pure-Go clone available from
12228 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
12229 used by the C tor-fw-helper are not, in our opinion, very
12230 confidence- inspiring in their secure-programming techniques.
12231 Closes ticket 13338.
12232 - Remove the code that would try to aggressively flush controller
12233 connections while writing to them. This code was introduced in
12234 0.1.2.7-alpha, in order to keep output buffers from exceeding
12235 their limits. But there is no longer a maximum output buffer size,
12236 and flushing data in this way caused some undesirable recursions
12237 in our call graph. Closes ticket 16480.
12240 - Make "bridges+hs" the default test network. This tests almost all
12241 tor functionality during make test-network, while allowing tests
12242 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
12243 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
12244 (chutney). Patches by "teor".
12245 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
12246 by-side in the same parent directory. Closes ticket 16903. Patch
12248 - Use environment variables rather than autoconf substitutions to
12249 send variables from the build system to the test scripts. This
12250 change should be easier to maintain, and cause 'make distcheck' to
12251 work better than before. Fixes bug 17148.
12252 - Add a new set of callgraph analysis scripts that use clang to
12253 produce a list of which Tor functions are reachable from which
12254 other Tor functions. We're planning to use these to help simplify
12255 our code structure by identifying illogical dependencies.
12256 - Add new 'test-full' and 'test-full-online' targets to run all
12257 tests, including integration tests with stem and chutney.
12258 - Make the test-workqueue test work on Windows by initializing the
12259 network before we begin.
12260 - New make target (make test-network-all) to run multiple applicable
12261 chutney test cases. Patch from Teor; closes 16953.
12262 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
12263 functions in dns.c. Implements a portion of ticket 16831.
12264 - When building Tor with testing coverage enabled, run Chutney tests
12265 (if any) using the 'tor-cov' coverage binary.
12266 - When running test-network or test-stem, check for the absence of
12267 stem/chutney before doing any build operations.
12270 Changes in version 0.2.7.2-alpha - 2015-07-27
12271 This, the second alpha in the Tor 0.2.7 series, has a number of new
12272 features, including a way to manually pick the number of introduction
12273 points for hidden services, and the much stronger Ed25519 signing key
12274 algorithm for regular Tor relays (including support for encrypted
12275 offline identity keys in the new algorithm).
12277 Support for Ed25519 on relays is currently limited to signing router
12278 descriptors; later alphas in this series will extend Ed25519 key
12279 support to more parts of the Tor protocol.
12281 o Major features (Ed25519 identity keys, Proposal 220):
12282 - All relays now maintain a stronger identity key, using the Ed25519
12283 elliptic curve signature format. This master key is designed so
12284 that it can be kept offline. Relays also generate an online
12285 signing key, and a set of other Ed25519 keys and certificates.
12286 These are all automatically regenerated and rotated as needed.
12287 Implements part of ticket 12498.
12288 - Directory authorities now vote on Ed25519 identity keys along with
12289 RSA1024 keys. Implements part of ticket 12498.
12290 - Directory authorities track which Ed25519 identity keys have been
12291 used with which RSA1024 identity keys, and do not allow them to
12292 vary freely. Implements part of ticket 12498.
12293 - Microdescriptors now include Ed25519 identity keys. Implements
12294 part of ticket 12498.
12295 - Add support for offline encrypted Ed25519 master keys. To use this
12296 feature on your tor relay, run "tor --keygen" to make a new master
12297 key (or to make a new signing key if you already have a master
12298 key). Closes ticket 13642.
12300 o Major features (Hidden services):
12301 - Add the torrc option HiddenServiceNumIntroductionPoints, to
12302 specify a fixed number of introduction points. Its maximum value
12303 is 10 and default is 3. Using this option can increase a hidden
12304 service's reliability under load, at the cost of making it more
12305 visible that the hidden service is facing extra load. Closes
12307 - Remove the adaptive algorithm for choosing the number of
12308 introduction points, which used to change the number of
12309 introduction points (poorly) depending on the number of
12310 connections the HS sees. Closes ticket 4862.
12312 o Major features (onion key cross-certification):
12313 - Relay descriptors now include signatures of their own identity
12314 keys, made using the TAP and ntor onion keys. These signatures
12315 allow relays to prove ownership of their own onion keys. Because
12316 of this change, microdescriptors will no longer need to include
12317 RSA identity keys. Implements proposal 228; closes ticket 12499.
12319 o Major features (performance):
12320 - Improve the runtime speed of Ed25519 operations by using the
12321 public-domain Ed25519-donna by Andrew M. ("floodyberry").
12322 Implements ticket 16467.
12323 - Improve the runtime speed of the ntor handshake by using an
12324 optimized curve25519 basepoint scalarmult implementation from the
12325 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
12326 ideas by Adam Langley. Implements ticket 9663.
12328 o Major bugfixes (client-side privacy, also in 0.2.6.9):
12329 - Properly separate out each SOCKSPort when applying stream
12330 isolation. The error occurred because each port's session group
12331 was being overwritten by a default value when the listener
12332 connection was initialized. Fixes bug 16247; bugfix on
12333 0.2.6.3-alpha. Patch by "jojelino".
12335 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
12336 - Stop refusing to store updated hidden service descriptors on a
12337 client. This reverts commit 9407040c59218 (which indeed fixed bug
12338 14219, but introduced a major hidden service reachability
12339 regression detailed in bug 16381). This is a temporary fix since
12340 we can live with the minor issue in bug 14219 (it just results in
12341 some load on the network) but the regression of 16381 is too much
12342 of a setback. First-round fix for bug 16381; bugfix
12345 o Major bugfixes (hidden services):
12346 - When cannibalizing a circuit for an introduction point, always
12347 extend to the chosen exit node (creating a 4 hop circuit).
12348 Previously Tor would use the current circuit exit node, which
12349 changed the original choice of introduction point, and could cause
12350 the hidden service to skip excluded introduction points or
12351 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
12354 o Major bugfixes (open file limit):
12355 - The open file limit wasn't checked before calling
12356 tor_accept_socket_nonblocking(), which would make Tor exceed the
12357 limit. Now, before opening a new socket, Tor validates the open
12358 file limit just before, and if the max has been reached, return an
12359 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
12361 o Major bugfixes (stability, also in 0.2.6.10):
12362 - Stop crashing with an assertion failure when parsing certain kinds
12363 of malformed or truncated microdescriptors. Fixes bug 16400;
12364 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
12365 by "cypherpunks_backup".
12366 - Stop random client-side assertion failures that could occur when
12367 connecting to a busy hidden service, or connecting to a hidden
12368 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
12371 o Minor features (directory authorities, security, also in 0.2.6.9):
12372 - The HSDir flag given by authorities now requires the Stable flag.
12373 For the current network, this results in going from 2887 to 2806
12374 HSDirs. Also, it makes it harder for an attacker to launch a sybil
12375 attack by raising the effort for a relay to become Stable to
12376 require at the very least 7 days, while maintaining the 96 hours
12377 uptime requirement for HSDir. Implements ticket 8243.
12379 o Minor features (client):
12380 - Relax the validation of hostnames in SOCKS5 requests, allowing the
12381 character '_' to appear, in order to cope with domains observed in
12382 the wild that are serving non-RFC compliant records. Resolves
12384 - Relax the validation done to hostnames in SOCKS5 requests, and
12385 allow a single trailing '.' to cope with clients that pass FQDNs
12386 using that syntax to explicitly indicate that the domain name is
12387 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
12388 - Add GroupWritable and WorldWritable options to unix-socket based
12389 SocksPort and ControlPort options. These options apply to a single
12390 socket, and override {Control,Socks}SocketsGroupWritable. Closes
12393 o Minor features (control protocol):
12394 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
12395 the control protocol. Resolves ticket 15358.
12397 o Minor features (directory authorities):
12398 - Directory authorities no longer vote against the "Fast", "Stable",
12399 and "HSDir" flags just because they were going to vote against
12400 "Running": if the consensus turns out to be that the router was
12401 running, then the authority's vote should count. Patch from Peter
12402 Retzlaff; closes issue 8712.
12404 o Minor features (geoip, also in 0.2.6.10):
12405 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
12406 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
12408 o Minor features (hidden services):
12409 - Add the new options "HiddenServiceMaxStreams" and
12410 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
12411 limit the maximum number of simultaneous streams per circuit, and
12412 optionally tear down the circuit when the limit is exceeded. Part
12415 o Minor features (portability):
12416 - Use C99 variadic macros when the compiler is not GCC. This avoids
12417 failing compilations on MSVC, and fixes a log-file-based race
12418 condition in our old workarounds. Original patch from Gisle Vanem.
12420 o Minor bugfixes (compilation, also in 0.2.6.9):
12421 - Build with --enable-systemd correctly when libsystemd is
12422 installed, but systemd is not. Fixes bug 16164; bugfix on
12423 0.2.6.3-alpha. Patch from Peter Palfrader.
12425 o Minor bugfixes (controller):
12426 - Add the descriptor ID in each HS_DESC control event. It was
12427 missing, but specified in control-spec.txt. Fixes bug 15881;
12428 bugfix on 0.2.5.2-alpha.
12430 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
12431 - Check for failures from crypto_early_init, and refuse to continue.
12432 A previous typo meant that we could keep going with an
12433 uninitialized crypto library, and would have OpenSSL initialize
12434 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12435 when implementing ticket 4900. Patch by "teor".
12437 o Minor bugfixes (hidden services):
12438 - Fix a crash when reloading configuration while at least one
12439 configured and one ephemeral hidden service exists. Fixes bug
12440 16060; bugfix on 0.2.7.1-alpha.
12441 - Avoid crashing with a double-free bug when we create an ephemeral
12442 hidden service but adding it fails for some reason. Fixes bug
12443 16228; bugfix on 0.2.7.1-alpha.
12445 o Minor bugfixes (Linux seccomp2 sandbox):
12446 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
12447 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
12449 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
12450 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
12451 these when eventfd2() support is missing. Fixes bug 16363; bugfix
12452 on 0.2.6.3-alpha. Patch from "teor".
12454 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
12455 - Fix sandboxing to work when running as a relay, by allowing the
12456 renaming of secret_id_key, and allowing the eventfd2 and futex
12457 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
12459 - Allow systemd connections to work with the Linux seccomp2 sandbox
12460 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
12463 o Minor bugfixes (relay):
12464 - Fix a rarely-encountered memory leak when failing to initialize
12465 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
12466 from "cypherpunks".
12468 o Minor bugfixes (systemd):
12469 - Fix an accidental formatting error that broke the systemd
12470 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
12471 - Tor's systemd unit file no longer contains extraneous spaces.
12472 These spaces would sometimes confuse tools like deb-systemd-
12473 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
12475 o Minor bugfixes (tests):
12476 - Use the configured Python executable when running test-stem-full.
12477 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
12479 o Minor bugfixes (tests, also in 0.2.6.9):
12480 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
12481 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
12483 o Minor bugfixes (threads, comments):
12484 - Always initialize return value in compute_desc_id in rendcommon.c
12485 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12486 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
12487 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12488 - Remove undefined directive-in-macro in test_util_writepid clang
12489 3.7 complains that using a preprocessor directive inside a macro
12490 invocation in test_util_writepid in test_util.c is undefined.
12491 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
12493 o Code simplification and refactoring:
12494 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
12495 to ensure they remain consistent and visible everywhere.
12496 - Remove some vestigial workarounds for the MSVC6 compiler. We
12497 haven't supported that in ages.
12498 - The link authentication code has been refactored for better
12499 testability and reliability. It now uses code generated with the
12500 "trunnel" binary encoding generator, to reduce the risk of bugs
12501 due to programmer error. Done as part of ticket 12498.
12504 - Include a specific and (hopefully) accurate documentation of the
12505 torrc file's meta-format in doc/torrc_format.txt. This is mainly
12506 of interest to people writing programs to parse or generate torrc
12507 files. This document is not a commitment to long-term
12508 compatibility; some aspects of the current format are a bit
12509 ridiculous. Closes ticket 2325.
12511 o Removed features:
12512 - Tor no longer supports copies of OpenSSL that are missing support
12513 for Elliptic Curve Cryptography. (We began using ECC when
12514 available in 0.2.4.8-alpha, for more safe and efficient key
12515 negotiation.) In particular, support for at least one of P256 or
12516 P224 is now required, with manual configuration needed if only
12517 P224 is available. Resolves ticket 16140.
12518 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
12519 on an operating system that has not upgraded to OpenSSL 1.0 or
12520 later, and you compile Tor from source, you will need to install a
12521 more recent OpenSSL to link Tor against.) These versions of
12522 OpenSSL are still supported by the OpenSSL, but the numerous
12523 cryptographic improvements in later OpenSSL releases makes them a
12524 clear choice. Resolves ticket 16034.
12525 - Remove the HidServDirectoryV2 option. Now all relays offer to
12526 store hidden service descriptors. Related to 16543.
12527 - Remove the VoteOnHidServDirectoriesV2 option, since all
12528 authorities have long set it to 1. Closes ticket 16543.
12531 - Document use of coverity, clang static analyzer, and clang dynamic
12532 undefined behavior and address sanitizers in doc/HACKING. Include
12533 detailed usage instructions in the blacklist. Patch by "teor".
12534 Closes ticket 15817.
12535 - The link authentication protocol code now has extensive tests.
12536 - The relay descriptor signature testing code now has
12538 - The test_workqueue program now runs faster, and is enabled by
12539 default as a part of "make check".
12540 - Now that OpenSSL has its own scrypt implementation, add an unit
12541 test that checks for interoperability between libscrypt_scrypt()
12542 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
12543 and rely on EVP_PBE_scrypt() whenever possible. Resolves
12547 Changes in version 0.2.6.10 - 2015-07-12
12548 Tor version 0.2.6.10 fixes some significant stability and hidden
12549 service client bugs, bulletproofs the cryptography init process, and
12550 fixes a bug when using the sandbox code with some older versions of
12551 Linux. Everyone running an older version, especially an older version
12552 of 0.2.6, should upgrade.
12554 o Major bugfixes (hidden service clients, stability):
12555 - Stop refusing to store updated hidden service descriptors on a
12556 client. This reverts commit 9407040c59218 (which indeed fixed bug
12557 14219, but introduced a major hidden service reachability
12558 regression detailed in bug 16381). This is a temporary fix since
12559 we can live with the minor issue in bug 14219 (it just results in
12560 some load on the network) but the regression of 16381 is too much
12561 of a setback. First-round fix for bug 16381; bugfix
12564 o Major bugfixes (stability):
12565 - Stop crashing with an assertion failure when parsing certain kinds
12566 of malformed or truncated microdescriptors. Fixes bug 16400;
12567 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
12568 by "cypherpunks_backup".
12569 - Stop random client-side assertion failures that could occur when
12570 connecting to a busy hidden service, or connecting to a hidden
12571 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
12574 o Minor features (geoip):
12575 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
12576 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
12578 o Minor bugfixes (crypto error-handling):
12579 - Check for failures from crypto_early_init, and refuse to continue.
12580 A previous typo meant that we could keep going with an
12581 uninitialized crypto library, and would have OpenSSL initialize
12582 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
12583 when implementing ticket 4900. Patch by "teor".
12585 o Minor bugfixes (Linux seccomp2 sandbox):
12586 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
12587 these when eventfd2() support is missing. Fixes bug 16363; bugfix
12588 on 0.2.6.3-alpha. Patch from "teor".
12591 Changes in version 0.2.6.9 - 2015-06-11
12592 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
12593 requirements for receiving an HSDir flag, and addresses some other small
12594 bugs in the systemd and sandbox code. Clients using circuit isolation
12595 should upgrade; all directory authorities should upgrade.
12597 o Major bugfixes (client-side privacy):
12598 - Properly separate out each SOCKSPort when applying stream
12599 isolation. The error occurred because each port's session group was
12600 being overwritten by a default value when the listener connection
12601 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
12604 o Minor feature (directory authorities, security):
12605 - The HSDir flag given by authorities now requires the Stable flag.
12606 For the current network, this results in going from 2887 to 2806
12607 HSDirs. Also, it makes it harder for an attacker to launch a sybil
12608 attack by raising the effort for a relay to become Stable which
12609 takes at the very least 7 days to do so and by keeping the 96
12610 hours uptime requirement for HSDir. Implements ticket 8243.
12612 o Minor bugfixes (compilation):
12613 - Build with --enable-systemd correctly when libsystemd is
12614 installed, but systemd is not. Fixes bug 16164; bugfix on
12615 0.2.6.3-alpha. Patch from Peter Palfrader.
12617 o Minor bugfixes (Linux seccomp2 sandbox):
12618 - Fix sandboxing to work when running as a relaymby renaming of
12619 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
12620 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
12621 - Allow systemd connections to work with the Linux seccomp2 sandbox
12622 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
12625 o Minor bugfixes (tests):
12626 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
12627 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
12630 Changes in version 0.2.6.8 - 2015-05-21
12631 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
12632 fixes an authority-side bug in assigning the HSDir flag. All directory
12633 authorities should upgrade.
12635 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
12636 - Revert commit that made directory authorities assign the HSDir
12637 flag to relays without a DirPort; this was bad because such relays
12638 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
12641 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
12642 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12643 a client authorized hidden service. Fixes bug 15823; bugfix
12646 o Minor features (geoip):
12647 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
12648 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
12652 Changes in version 0.2.7.1-alpha - 2015-05-12
12653 Tor 0.2.7.1-alpha is the first alpha release in its series. It
12654 includes numerous small features and bugfixes against previous Tor
12655 versions, and numerous small infrastructure improvements. The most
12656 notable features are several new ways for controllers to interact with
12657 the hidden services subsystem.
12659 o New system requirements:
12660 - Tor no longer includes workarounds to support Libevent versions
12661 before 1.3e. Libevent 2.0 or later is recommended. Closes
12664 o Major features (controller):
12665 - Add the ADD_ONION and DEL_ONION commands that allow the creation
12666 and management of hidden services via the controller. Closes
12668 - New "GETINFO onions/current" and "GETINFO onions/detached"
12669 commands to get information about hidden services created via the
12670 controller. Part of ticket 6411.
12671 - New HSFETCH command to launch a request for a hidden service
12672 descriptor. Closes ticket 14847.
12673 - New HSPOST command to upload a hidden service descriptor. Closes
12674 ticket 3523. Patch by "DonnchaC".
12676 o Major bugfixes (hidden services):
12677 - Revert commit that made directory authorities assign the HSDir
12678 flag to relays without a DirPort; this was bad because such relays
12679 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
12682 o Minor features (clock-jump tolerance):
12683 - Recover better when our clock jumps back many hours, like might
12684 happen for Tails or Whonix users who start with a very wrong
12685 hardware clock, use Tor to discover a more accurate time, and then
12686 fix their clock. Resolves part of ticket 8766.
12688 o Minor features (command-line interface):
12689 - Make --hash-password imply --hush to prevent unnecessary noise.
12690 Closes ticket 15542. Patch from "cypherpunks".
12691 - Print a warning whenever we find a relative file path being used
12692 as torrc option. Resolves issue 14018.
12694 o Minor features (controller):
12695 - Add DirAuthority lines for default directory authorities to the
12696 output of the "GETINFO config/defaults" command if not already
12697 present. Implements ticket 14840.
12698 - Controllers can now use "GETINFO hs/client/desc/id/..." to
12699 retrieve items from the client's hidden service descriptor cache.
12700 Closes ticket 14845.
12701 - Implement a new controller command "GETINFO status/fresh-relay-
12702 descs" to fetch a descriptor/extrainfo pair that was generated on
12703 demand just for the controller's use. Implements ticket 14784.
12705 o Minor features (DoS-resistance):
12706 - Make it harder for attackers to overload hidden services with
12707 introductions, by blocking multiple introduction requests on the
12708 same circuit. Resolves ticket 15515.
12710 o Minor features (geoip):
12711 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
12712 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
12715 o Minor features (HS popularity countermeasure):
12716 - To avoid leaking HS popularity, don't cycle the introduction point
12717 when we've handled a fixed number of INTRODUCE2 cells but instead
12718 cycle it when a random number of introductions is reached, thus
12719 making it more difficult for an attacker to find out the amount of
12720 clients that have used the introduction point for a specific HS.
12721 Closes ticket 15745.
12723 o Minor features (logging):
12724 - Include the Tor version in all LD_BUG log messages, since people
12725 tend to cut and paste those into the bugtracker. Implements
12728 o Minor features (pluggable transports):
12729 - When launching managed pluggable transports on Linux systems,
12730 attempt to have the kernel deliver a SIGTERM on tor exit if the
12731 pluggable transport process is still running. Resolves
12733 - When launching managed pluggable transports, setup a valid open
12734 stdin in the child process that can be used to detect if tor has
12735 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
12736 can be used by implementations to detect this new behavior.
12737 Resolves ticket 15435.
12739 o Minor features (testing):
12740 - Add a test to verify that the compiler does not eliminate our
12741 memwipe() implementation. Closes ticket 15377.
12742 - Add make rule `check-changes` to verify the format of changes
12743 files. Closes ticket 15180.
12744 - Add unit tests for control_event_is_interesting(). Add a compile-
12745 time check that the number of events doesn't exceed the capacity
12746 of control_event_t.event_mask. Closes ticket 15431, checks for
12747 bugs similar to 13085. Patch by "teor".
12748 - Command-line argument tests moved to Stem. Resolves ticket 14806.
12749 - Integrate the ntor, backtrace, and zero-length keys tests into the
12750 automake test suite. Closes ticket 15344.
12751 - Remove assertions during builds to determine Tor's test coverage.
12752 We don't want to trigger these even in assertions, so including
12753 them artificially makes our branch coverage look worse than it is.
12754 This patch provides the new test-stem-full and coverage-html-full
12755 configure options. Implements ticket 15400.
12757 o Minor bugfixes (build):
12758 - Improve out-of-tree builds by making non-standard rules work and
12759 clean up additional files and directories. Fixes bug 15053; bugfix
12762 o Minor bugfixes (command-line interface):
12763 - When "--quiet" is provided along with "--validate-config", do not
12764 write anything to stdout on success. Fixes bug 14994; bugfix
12766 - When complaining about bad arguments to "--dump-config", use
12767 stderr, not stdout.
12769 o Minor bugfixes (configuration, unit tests):
12770 - Only add the default fallback directories when the DirAuthorities,
12771 AlternateDirAuthority, and FallbackDir directory config options
12772 are set to their defaults. The default fallback directory list is
12773 currently empty, this fix will only change tor's behavior when it
12774 has default fallback directories. Includes unit tests for
12775 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
12776 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
12778 o Minor bugfixes (correctness):
12779 - For correctness, avoid modifying a constant string in
12780 handle_control_postdescriptor. Fixes bug 15546; bugfix
12782 - Remove side-effects from tor_assert() calls. This was harmless,
12783 because we never disable assertions, but it is bad style and
12784 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
12787 o Minor bugfixes (hidden service):
12788 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
12789 a client authorized hidden service. Fixes bug 15823; bugfix
12791 - Remove an extraneous newline character from the end of hidden
12792 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
12794 o Minor bugfixes (interface):
12795 - Print usage information for --dump-config when it is used without
12796 an argument. Also, fix the error message to use different wording
12797 and add newline at the end. Fixes bug 15541; bugfix
12800 o Minor bugfixes (logs):
12801 - When building Tor under Clang, do not include an extra set of
12802 parentheses in log messages that include function names. Fixes bug
12803 15269; bugfix on every released version of Tor when compiled with
12804 recent enough Clang.
12806 o Minor bugfixes (network):
12807 - When attempting to use fallback technique for network interface
12808 lookup, disregard loopback and multicast addresses since they are
12809 unsuitable for public communications.
12811 o Minor bugfixes (statistics):
12812 - Disregard the ConnDirectionStatistics torrc options when Tor is
12813 not a relay since in that mode of operation no sensible data is
12814 being collected and because Tor might run into measurement hiccups
12815 when running as a client for some time, then becoming a relay.
12816 Fixes bug 15604; bugfix on 0.2.2.35.
12818 o Minor bugfixes (test networks):
12819 - When self-testing reachability, use ExtendAllowPrivateAddresses to
12820 determine if local/private addresses imply reachability. The
12821 previous fix used TestingTorNetwork, which implies
12822 ExtendAllowPrivateAddresses, but this excluded rare configurations
12823 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
12824 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
12825 issue discovered by CJ Ess.
12827 o Minor bugfixes (testing):
12828 - Check for matching value in server response in ntor_ref.py. Fixes
12829 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
12831 - Set the severity correctly when testing
12832 get_interface_addresses_ifaddrs() and
12833 get_interface_addresses_win32(), so that the tests fail gracefully
12834 instead of triggering an assertion. Fixes bug 15759; bugfix on
12835 0.2.6.3-alpha. Reported by Nicolas Derive.
12837 o Code simplification and refactoring:
12838 - Move the hacky fallback code out of get_interface_address6() into
12839 separate function and get it covered with unit-tests. Resolves
12841 - Refactor hidden service client-side cache lookup to intelligently
12842 report its various failure cases, and disentangle failure cases
12843 involving a lack of introduction points. Closes ticket 14391.
12844 - Use our own Base64 encoder instead of OpenSSL's, to allow more
12845 control over the output. Part of ticket 15652.
12848 - Improve the descriptions of statistics-related torrc options in
12849 the manpage to describe rationale and possible uses cases. Fixes
12851 - Improve the layout and formatting of ./configure --help messages.
12852 Closes ticket 15024. Patch from "cypherpunks".
12853 - Standardize on the term "server descriptor" in the manual page.
12854 Previously, we had used "router descriptor", "server descriptor",
12855 and "relay descriptor" interchangeably. Part of ticket 14987.
12858 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
12859 and always use the internal Base64 decoder. The internal decoder
12860 has been part of tor since 0.2.0.10-alpha, and no one should
12861 be using the OpenSSL one. Part of ticket 15652.
12862 - Remove the 'tor_strclear()' function; use memwipe() instead.
12863 Closes ticket 14922.
12865 o Removed features:
12866 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
12867 fingerprinting we now recommend pluggable transports; for forward-
12868 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
12869 - Remove the undocumented "--digests" command-line option. It
12870 complicated our build process, caused subtle build issues on
12871 multiple platforms, and is now redundant since we started
12872 including git version identifiers. Closes ticket 14742.
12873 - Tor no longer contains checks for ancient directory cache versions
12874 that didn't know about microdescriptors.
12875 - Tor no longer contains workarounds for stat files generated by
12876 super-old versions of Tor that didn't choose guards sensibly.
12879 Changes in version 0.2.4.27 - 2015-04-06
12880 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
12881 could be used by an attacker to crash hidden services, or crash clients
12882 visiting hidden services. Hidden services should upgrade as soon as
12883 possible; clients should upgrade whenever packages become available.
12885 This release also backports a simple improvement to make hidden
12886 services a bit less vulnerable to denial-of-service attacks.
12888 o Major bugfixes (security, hidden service):
12889 - Fix an issue that would allow a malicious client to trigger an
12890 assertion failure and halt a hidden service. Fixes bug 15600;
12891 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12892 - Fix a bug that could cause a client to crash with an assertion
12893 failure when parsing a malformed hidden service descriptor. Fixes
12894 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12896 o Minor features (DoS-resistance, hidden service):
12897 - Introduction points no longer allow multiple INTRODUCE1 cells to
12898 arrive on the same circuit. This should make it more expensive for
12899 attackers to overwhelm hidden services with introductions.
12900 Resolves ticket 15515.
12903 Changes in version 0.2.5.12 - 2015-04-06
12904 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
12905 could be used by an attacker to crash hidden services, or crash clients
12906 visiting hidden services. Hidden services should upgrade as soon as
12907 possible; clients should upgrade whenever packages become available.
12909 This release also backports a simple improvement to make hidden
12910 services a bit less vulnerable to denial-of-service attacks.
12912 o Major bugfixes (security, hidden service):
12913 - Fix an issue that would allow a malicious client to trigger an
12914 assertion failure and halt a hidden service. Fixes bug 15600;
12915 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12916 - Fix a bug that could cause a client to crash with an assertion
12917 failure when parsing a malformed hidden service descriptor. Fixes
12918 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12920 o Minor features (DoS-resistance, hidden service):
12921 - Introduction points no longer allow multiple INTRODUCE1 cells to
12922 arrive on the same circuit. This should make it more expensive for
12923 attackers to overwhelm hidden services with introductions.
12924 Resolves ticket 15515.
12927 Changes in version 0.2.6.7 - 2015-04-06
12928 Tor 0.2.6.7 fixes two security issues that could be used by an
12929 attacker to crash hidden services, or crash clients visiting hidden
12930 services. Hidden services should upgrade as soon as possible; clients
12931 should upgrade whenever packages become available.
12933 This release also contains two simple improvements to make hidden
12934 services a bit less vulnerable to denial-of-service attacks.
12936 o Major bugfixes (security, hidden service):
12937 - Fix an issue that would allow a malicious client to trigger an
12938 assertion failure and halt a hidden service. Fixes bug 15600;
12939 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
12940 - Fix a bug that could cause a client to crash with an assertion
12941 failure when parsing a malformed hidden service descriptor. Fixes
12942 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
12944 o Minor features (DoS-resistance, hidden service):
12945 - Introduction points no longer allow multiple INTRODUCE1 cells to
12946 arrive on the same circuit. This should make it more expensive for
12947 attackers to overwhelm hidden services with introductions.
12948 Resolves ticket 15515.
12949 - Decrease the amount of reattempts that a hidden service performs
12950 when its rendezvous circuits fail. This reduces the computational
12951 cost for running a hidden service under heavy load. Resolves
12955 Changes in version 0.2.6.6 - 2015-03-24
12956 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
12958 It adds numerous safety, security, correctness, and performance
12959 improvements. Client programs can be configured to use more kinds of
12960 sockets, AutomapHosts works better, the multithreading backend is
12961 improved, cell transmission is refactored, test coverage is much
12962 higher, more denial-of-service attacks are handled, guard selection is
12963 improved to handle long-term guards better, pluggable transports
12964 should work a bit better, and some annoying hidden service performance
12965 bugs should be addressed.
12967 o Minor bugfixes (portability):
12968 - Use the correct datatype in the SipHash-2-4 function to prevent
12969 compilers from assuming any sort of alignment. Fixes bug 15436;
12970 bugfix on 0.2.5.3-alpha.
12972 Changes in version 0.2.6.5-rc - 2015-03-18
12973 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
12974 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
12976 o Major bugfixes (client):
12977 - Avoid crashing when making certain configuration option changes on
12978 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
12981 o Major bugfixes (pluggable transports):
12982 - Initialize the extended OR Port authentication cookie before
12983 launching pluggable transports. This prevents a race condition
12984 that occurred when server-side pluggable transports would cache the
12985 authentication cookie before it has been (re)generated. Fixes bug
12986 15240; bugfix on 0.2.5.1-alpha.
12988 o Major bugfixes (portability):
12989 - Do not crash on startup when running on Solaris. Fixes a bug
12990 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
12993 o Minor features (heartbeat):
12994 - On relays, report how many connections we negotiated using each
12995 version of the Tor link protocols. This information will let us
12996 know if removing support for very old versions of the Tor
12997 protocols is harming the network. Closes ticket 15212.
12999 o Code simplification and refactoring:
13000 - Refactor main loop to extract the 'loop' part. This makes it
13001 easier to run Tor under Shadow. Closes ticket 15176.
13004 Changes in version 0.2.5.11 - 2015-03-17
13005 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
13007 It backports several bugfixes from the 0.2.6 branch, including a
13008 couple of medium-level security fixes for relays and exit nodes.
13009 It also updates the list of directory authorities.
13011 o Directory authority changes:
13012 - Remove turtles as a directory authority.
13013 - Add longclaw as a new (v3) directory authority. This implements
13014 ticket 13296. This keeps the directory authority count at 9.
13015 - The directory authority Faravahar has a new IP address. This
13016 closes ticket 14487.
13018 o Major bugfixes (crash, OSX, security):
13019 - Fix a remote denial-of-service opportunity caused by a bug in
13020 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13023 o Major bugfixes (relay, stability, possible security):
13024 - Fix a bug that could lead to a relay crashing with an assertion
13025 failure if a buffer of exactly the wrong layout was passed to
13026 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13027 0.2.0.10-alpha. Patch from 'cypherpunks'.
13028 - Do not assert if the 'data' pointer on a buffer is advanced to the
13029 very end of the buffer; log a BUG message instead. Only assert if
13030 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13032 o Major bugfixes (exit node stability):
13033 - Fix an assertion failure that could occur under high DNS load.
13034 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13035 diagnosed and fixed by "cypherpunks".
13037 o Major bugfixes (Linux seccomp2 sandbox):
13038 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13039 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13040 0.2.5.1-alpha. Patch from "sanic".
13042 o Minor features (controller):
13043 - New "GETINFO bw-event-cache" to get information about recent
13044 bandwidth events. Closes ticket 14128. Useful for controllers to
13045 get recent bandwidth history after the fix for ticket 13988.
13047 o Minor features (geoip):
13048 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13049 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13052 o Minor bugfixes (client, automapping):
13053 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
13054 no value follows the option. Fixes bug 14142; bugfix on
13055 0.2.4.7-alpha. Patch by "teor".
13056 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
13057 14195; bugfix on 0.1.0.1-rc.
13059 o Minor bugfixes (compilation):
13060 - Build without warnings with the stock OpenSSL srtp.h header, which
13061 has a duplicate declaration of SSL_get_selected_srtp_profile().
13062 Fixes bug 14220; this is OpenSSL's bug, not ours.
13064 o Minor bugfixes (directory authority):
13065 - Allow directory authorities to fetch more data from one another if
13066 they find themselves missing lots of votes. Previously, they had
13067 been bumping against the 10 MB queued data limit. Fixes bug 14261;
13068 bugfix on 0.1.2.5-alpha.
13069 - Enlarge the buffer to read bwauth generated files to avoid an
13070 issue when parsing the file in dirserv_read_measured_bandwidths().
13071 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
13073 o Minor bugfixes (statistics):
13074 - Increase period over which bandwidth observations are aggregated
13075 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
13077 o Minor bugfixes (preventative security, C safety):
13078 - When reading a hexadecimal, base-32, or base-64 encoded value from
13079 a string, always overwrite the whole output buffer. This prevents
13080 some bugs where we would look at (but fortunately, not reveal)
13081 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
13085 Changes in version 0.2.4.26 - 2015-03-17
13086 Tor 0.2.4.26 includes an updated list of directory authorities. It
13087 also backports a couple of stability and security bugfixes from 0.2.5
13090 o Directory authority changes:
13091 - Remove turtles as a directory authority.
13092 - Add longclaw as a new (v3) directory authority. This implements
13093 ticket 13296. This keeps the directory authority count at 9.
13094 - The directory authority Faravahar has a new IP address. This
13095 closes ticket 14487.
13097 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
13098 - Fix an assertion failure that could occur under high DNS load.
13099 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13100 diagnosed and fixed by "cypherpunks".
13102 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
13103 - Fix a bug that could lead to a relay crashing with an assertion
13104 failure if a buffer of exactly the wrong layout was passed to
13105 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13106 0.2.0.10-alpha. Patch from 'cypherpunks'.
13107 - Do not assert if the 'data' pointer on a buffer is advanced to the
13108 very end of the buffer; log a BUG message instead. Only assert if
13109 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13111 o Minor features (geoip):
13112 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13113 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13116 Changes in version 0.2.6.4-rc - 2015-03-09
13117 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
13118 attacker might be able to use in order to crash certain Tor
13119 directories. It also resolves some minor issues left over from, or
13120 introduced in, Tor 0.2.6.3-alpha or earlier.
13122 o Major bugfixes (crash, OSX, security):
13123 - Fix a remote denial-of-service opportunity caused by a bug in
13124 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13127 o Major bugfixes (relay, stability, possible security):
13128 - Fix a bug that could lead to a relay crashing with an assertion
13129 failure if a buffer of exactly the wrong layout is passed to
13130 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13131 0.2.0.10-alpha. Patch from "cypherpunks".
13132 - Do not assert if the 'data' pointer on a buffer is advanced to the
13133 very end of the buffer; log a BUG message instead. Only assert if
13134 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13136 o Major bugfixes (FreeBSD IPFW transparent proxy):
13137 - Fix address detection with FreeBSD transparent proxies, when
13138 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
13141 o Major bugfixes (Linux seccomp2 sandbox):
13142 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
13143 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
13145 - Allow AF_UNIX hidden services to be used with the seccomp2
13146 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
13147 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13148 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13149 0.2.5.1-alpha. Patch from "sanic".
13151 o Minor features (controller):
13152 - Messages about problems in the bootstrap process now include
13153 information about the server we were trying to connect to when we
13154 noticed the problem. Closes ticket 15006.
13156 o Minor features (geoip):
13157 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13158 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13161 o Minor features (logs):
13162 - Quiet some log messages in the heartbeat and at startup. Closes
13165 o Minor bugfixes (certificate handling):
13166 - If an authority operator accidentally makes a signing certificate
13167 with a future publication time, do not discard its real signing
13168 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
13169 - Remove any old authority certificates that have been superseded
13170 for at least two days. Previously, we would keep superseded
13171 certificates until they expired, if they were published close in
13172 time to the certificate that superseded them. Fixes bug 11454;
13173 bugfix on 0.2.1.8-alpha.
13175 o Minor bugfixes (compilation):
13176 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
13178 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
13181 o Minor bugfixes (testing):
13182 - Fix endianness issues in unit test for resolve_my_address() to
13183 have it pass on big endian systems. Fixes bug 14980; bugfix on
13185 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
13186 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
13187 - When running the new 'make test-stem' target, use the configured
13188 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
13189 from "cypherpunks".
13190 - When running the zero-length-keys tests, do not use the default
13191 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
13194 o Directory authority IP change:
13195 - The directory authority Faravahar has a new IP address. This
13196 closes ticket 14487.
13199 - Remove some lingering dead code that once supported mempools.
13200 Mempools were disabled by default in 0.2.5, and removed entirely
13201 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
13205 Changes in version 0.2.6.3-alpha - 2015-02-19
13206 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
13207 the 0.2.6.x series. It introduces support for more kinds of sockets,
13208 makes it harder to accidentally run an exit, improves our
13209 multithreading backend, incorporates several fixes for the
13210 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
13212 If no major regressions or security holes are found in this version,
13213 the next version will be a release candidate.
13215 o Deprecated versions:
13216 - Tor relays older than 0.2.4.18-rc are no longer allowed to
13217 advertise themselves on the network. Closes ticket 13555.
13219 o Major features (security, unix domain sockets):
13220 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
13221 applications can reach Tor without having to create AF_INET or
13222 AF_INET6 sockets, meaning they can completely disable their
13223 ability to make non-Tor network connections. To create a socket of
13224 this type, use "SocksPort unix:/path/to/socket". Implements
13226 - Support mapping hidden service virtual ports to AF_UNIX sockets.
13227 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
13228 Implements ticket 11485.
13230 o Major features (changed defaults):
13231 - Prevent relay operators from unintentionally running exits: When a
13232 relay is configured as an exit node, we now warn the user unless
13233 the "ExitRelay" option is set to 1. We warn even more loudly if
13234 the relay is configured with the default exit policy, since this
13235 can indicate accidental misconfiguration. Setting "ExitRelay 0"
13236 stops Tor from running as an exit relay. Closes ticket 10067.
13238 o Major features (directory system):
13239 - When downloading server- or microdescriptors from a directory
13240 server, we no longer launch multiple simultaneous requests to the
13241 same server. This reduces load on the directory servers,
13242 especially when directory guards are in use. Closes ticket 9969.
13243 - When downloading server- or microdescriptors over a tunneled
13244 connection, do not limit the length of our requests to what the
13245 Squid proxy is willing to handle. Part of ticket 9969.
13246 - Authorities can now vote on the correct digests and latest
13247 versions for different software packages. This allows packages
13248 that include Tor to use the Tor authority system as a way to get
13249 notified of updates and their correct digests. Implements proposal
13250 227. Closes ticket 10395.
13252 o Major features (guards):
13253 - Introduce the Guardfraction feature to improves load balancing on
13254 guard nodes. Specifically, it aims to reduce the traffic gap that
13255 guard nodes experience when they first get the Guard flag. This is
13256 a required step if we want to increase the guard lifetime to 9
13257 months or greater. Closes ticket 9321.
13259 o Major features (performance):
13260 - Make the CPU worker implementation more efficient by avoiding the
13261 kernel and lengthening pipelines. The original implementation used
13262 sockets to transfer data from the main thread to the workers, and
13263 didn't allow any thread to be assigned more than a single piece of
13264 work at once. The new implementation avoids communications
13265 overhead by making requests in shared memory, avoiding kernel IO
13266 where possible, and keeping more requests in flight at once.
13267 Implements ticket 9682.
13269 o Major features (relay):
13270 - Raise the minimum acceptable configured bandwidth rate for bridges
13271 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
13272 20 KiB/sec.) Closes ticket 13822.
13274 o Major bugfixes (exit node stability):
13275 - Fix an assertion failure that could occur under high DNS load.
13276 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13277 diagnosed and fixed by "cypherpunks".
13279 o Major bugfixes (mixed relay-client operation):
13280 - When running as a relay and client at the same time (not
13281 recommended), if we decide not to use a new guard because we want
13282 to retry older guards, only close the locally-originating circuits
13283 passing through that guard. Previously we would close all the
13284 circuits through that guard. Fixes bug 9819; bugfix on
13285 0.2.1.1-alpha. Reported by "skruffy".
13287 o Minor features (build):
13288 - New --disable-system-torrc compile-time option to prevent Tor from
13289 looking for the system-wide torrc or torrc-defaults files.
13290 Resolves ticket 13037.
13292 o Minor features (controller):
13293 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
13294 events so controllers can observe circuit isolation inputs. Closes
13296 - ControlPort now supports the unix:/path/to/socket syntax as an
13297 alternative to the ControlSocket option, for consistency with
13298 SocksPort and HiddenServicePort. Closes ticket 14451.
13299 - New "GETINFO bw-event-cache" to get information about recent
13300 bandwidth events. Closes ticket 14128. Useful for controllers to
13301 get recent bandwidth history after the fix for ticket 13988.
13303 o Minor features (Denial of service resistance):
13304 - Count the total number of bytes used storing hidden service
13305 descriptors against the value of MaxMemInQueues. If we're low on
13306 memory, and more than 20% of our memory is used holding hidden
13307 service descriptors, free them until no more than 10% of our
13308 memory holds hidden service descriptors. Free the least recently
13309 fetched descriptors first. Resolves ticket 13806.
13310 - When we have recently been under memory pressure (over 3/4 of
13311 MaxMemInQueues is allocated), then allocate smaller zlib objects
13312 for small requests. Closes ticket 11791.
13314 o Minor features (geoip):
13315 - Update geoip and geoip6 files to the January 7 2015 Maxmind
13316 GeoLite2 Country database.
13318 o Minor features (guard nodes):
13319 - Reduce the time delay before saving guard status to disk from 10
13320 minutes to 30 seconds (or from one hour to 10 minutes if
13321 AvoidDiskWrites is set). Closes ticket 12485.
13323 o Minor features (hidden service):
13324 - Make Sybil attacks against hidden services harder by changing the
13325 minimum time required to get the HSDir flag from 25 hours up to 96
13326 hours. Addresses ticket 14149.
13327 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
13328 services to disable the anti-scanning feature introduced in
13329 0.2.6.2-alpha. With this option not set, a connection to an
13330 unlisted port closes the circuit. With this option set, only a
13331 RELAY_DONE cell is sent. Closes ticket 14084.
13333 o Minor features (interface):
13334 - Implement "-f -" command-line option to read torrc configuration
13335 from standard input, if you don't want to store the torrc file in
13336 the file system. Implements feature 13865.
13338 o Minor features (logging):
13339 - Add a count of unique clients to the bridge heartbeat message.
13340 Resolves ticket 6852.
13341 - Suppress "router info incompatible with extra info" message when
13342 reading extrainfo documents from cache. (This message got loud
13343 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
13345 - Elevate hidden service authorized-client message from DEBUG to
13346 INFO. Closes ticket 14015.
13348 o Minor features (stability):
13349 - Add assertions in our hash-table iteration code to check for
13350 corrupted values that could cause infinite loops. Closes
13353 o Minor features (systemd):
13354 - Various improvements and modernizations in systemd hardening
13355 support. Closes ticket 13805. Patch from Craig Andrews.
13357 o Minor features (testing networks):
13358 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
13359 and the default on a testing network to 2 minutes. Drop the
13360 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
13361 keep the default on a testing network at 30 seconds. This reduces
13362 HS bootstrap time to around 25 seconds. Also, change the default
13363 time in test-network.sh to match. Closes ticket 13401. Patch
13365 - Create TestingDirAuthVoteHSDir to correspond to
13366 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
13367 HSDir flag for the listed relays regardless of uptime or ORPort
13368 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
13369 Partial implementation for ticket 14067. Patch by "teor".
13371 o Minor features (tor2web mode):
13372 - Introduce the config option Tor2webRendezvousPoints, which allows
13373 clients in Tor2webMode to select a specific Rendezvous Point to be
13374 used in HS circuits. This might allow better performance for
13375 Tor2Web nodes. Implements ticket 12844.
13377 o Minor bugfixes (client DNS):
13378 - Report the correct cached DNS expiration times on SOCKS port or in
13379 DNS replies. Previously, we would report everything as "never
13380 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
13381 - Avoid a small memory leak when we find a cached answer for a
13382 reverse DNS lookup in a client-side DNS cache. (Remember, client-
13383 side DNS caching is off by default, and is not recommended.) Fixes
13384 bug 14259; bugfix on 0.2.0.1-alpha.
13386 o Minor bugfixes (client, automapping):
13387 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
13388 no value follows the option. Fixes bug 14142; bugfix on
13389 0.2.4.7-alpha. Patch by "teor".
13390 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
13391 14195; bugfix on 0.1.0.1-rc.
13392 - Prevent changes to other options from removing the wildcard value
13393 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
13395 - Allow MapAddress and AutomapHostsOnResolve to work together when
13396 an address is mapped into another address type (like .onion) that
13397 must be automapped at resolve time. Fixes bug 7555; bugfix
13400 o Minor bugfixes (client, bridges):
13401 - When we are using bridges and we had a network connectivity
13402 problem, only retry connecting to our currently configured
13403 bridges, not all bridges we know about and remember using. Fixes
13404 bug 14216; bugfix on 0.2.2.17-alpha.
13406 o Minor bugfixes (client, IPv6):
13407 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
13408 flag is not set; and not because the NoIPv4Traffic flag was set.
13409 Previously we'd looked at the NoIPv4Traffic flag for both types of
13410 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
13412 o Minor bugfixes (compilation):
13413 - The address of an array in the middle of a structure will always
13414 be non-NULL. clang recognises this and complains. Disable the
13415 tautologous and redundant check to silence this warning. Fixes bug
13416 14001; bugfix on 0.2.1.2-alpha.
13417 - Avoid warnings when building with systemd 209 or later. Fixes bug
13418 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
13419 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
13420 Addresses ticket 14188.
13421 - Build without warnings with the stock OpenSSL srtp.h header, which
13422 has a duplicate declaration of SSL_get_selected_srtp_profile().
13423 Fixes bug 14220; this is OpenSSL's bug, not ours.
13424 - Do not compile any code related to Tor2Web mode when Tor2Web mode
13425 is not enabled at compile time. Previously, this code was included
13426 in a disabled state. See discussion on ticket 12844.
13427 - Remove the --disable-threads configure option again. It was
13428 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
13429 14819; bugfix on 0.2.6.2-alpha.
13431 o Minor bugfixes (controller):
13432 - Report "down" in response to the "GETINFO entry-guards" command
13433 when relays are down with an unreachable_since value. Previously,
13434 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
13435 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
13436 14116; bugfix on 0.2.2.9-alpha.
13437 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
13438 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
13440 o Minor bugfixes (directory authority):
13441 - Allow directory authorities to fetch more data from one another if
13442 they find themselves missing lots of votes. Previously, they had
13443 been bumping against the 10 MB queued data limit. Fixes bug 14261;
13444 bugfix on 0.1.2.5-alpha.
13445 - Do not attempt to download extrainfo documents which we will be
13446 unable to validate with a matching server descriptor. Fixes bug
13447 13762; bugfix on 0.2.0.1-alpha.
13448 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
13449 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
13450 - Enlarge the buffer to read bwauth generated files to avoid an
13451 issue when parsing the file in dirserv_read_measured_bandwidths().
13452 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
13454 o Minor bugfixes (file handling):
13455 - Stop failing when key files are zero-length. Instead, generate new
13456 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
13457 on all versions of Tor. Patch by "teor".
13458 - Stop generating a fresh .old RSA onion key file when the .old file
13459 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
13460 - Avoid overwriting .old key files with empty key files.
13461 - Skip loading zero-length extrainfo store, router store, stats,
13462 state, and key files.
13463 - Avoid crashing when trying to reload a torrc specified as a
13464 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
13467 o Minor bugfixes (hidden services):
13468 - Close the introduction circuit when we have no more usable intro
13469 points, instead of waiting for it to time out. This also ensures
13470 that no follow-up HS descriptor fetch is triggered when the
13471 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
13472 - When fetching a hidden service descriptor for a down service that
13473 was recently up, do not keep refetching until we try the same
13474 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
13475 - Successfully launch Tor with a nonexistent hidden service
13476 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
13477 14106; bugfix on 0.2.6.2-alpha.
13479 o Minor bugfixes (logging):
13480 - Avoid crashing when there are more log domains than entries in
13481 domain_list. Bugfix on 0.2.3.1-alpha.
13482 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
13484 - Don't log messages to stdout twice when starting up. Fixes bug
13485 13993; bugfix on 0.2.6.1-alpha.
13487 o Minor bugfixes (parsing):
13488 - Stop accepting milliseconds (or other junk) at the end of
13489 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
13490 - Support two-number and three-number version numbers correctly, in
13491 case we change the Tor versioning system in the future. Fixes bug
13492 13661; bugfix on 0.0.8pre1.
13494 o Minor bugfixes (path counting):
13495 - When deciding whether the consensus lists any exit nodes, count
13496 the number listed in the consensus, not the number we have
13497 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
13498 - When deciding whether we have any exit nodes, only examine
13499 ExitNodes when the ExitNodes option is actually set. Fixes part of
13500 bug 14918; bugfix on 0.2.6.2-alpha.
13501 - Get rid of redundant and possibly scary warnings that we are
13502 missing directory information while we bootstrap. Fixes part of
13503 bug 14918; bugfix on 0.2.6.2-alpha.
13505 o Minor bugfixes (portability):
13506 - Fix the ioctl()-based network interface lookup code so that it
13507 will work on systems that have variable-length struct ifreq, for
13509 - Fix scheduler compilation on targets where char is unsigned. Fixes
13510 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
13512 o Minor bugfixes (sandbox):
13513 - Allow glibc fatal errors to be sent to stderr before Tor exits.
13514 Previously, glibc would try to write them to /dev/tty, and the
13515 sandbox would trap the call and make Tor exit prematurely. Fixes
13516 bug 14759; bugfix on 0.2.5.1-alpha.
13518 o Minor bugfixes (shutdown):
13519 - When shutting down, always call event_del() on lingering read or
13520 write events before freeing them. Otherwise, we risk double-frees
13521 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
13524 o Minor bugfixes (small memory leaks):
13525 - Avoid leaking memory when using IPv6 virtual address mappings.
13526 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
13529 o Minor bugfixes (statistics):
13530 - Increase period over which bandwidth observations are aggregated
13531 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
13533 o Minor bugfixes (systemd support):
13534 - Fix detection and operation of systemd watchdog. Fixes part of bug
13535 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
13536 - Run correctly under systemd with the RunAsDaemon option set. Fixes
13537 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
13538 - Inform the systemd supervisor about more changes in the Tor
13539 process status. Implements part of ticket 14141. Patch from
13541 - Cause the "--disable-systemd" option to actually disable systemd
13542 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
13545 o Minor bugfixes (TLS):
13546 - Check more thoroughly throughout the TLS code for possible
13547 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
13549 o Minor bugfixes (transparent proxy):
13550 - Use getsockname, not getsockopt, to retrieve the address for a
13551 TPROXY-redirected connection. Fixes bug 13796; bugfix
13554 o Code simplification and refactoring:
13555 - Move fields related to isolating and configuring client ports into
13556 a shared structure. Previously, they were duplicated across
13557 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
13558 to copy them correctly had been the cause of at least one bug in
13559 the past. Closes ticket 8546.
13560 - Refactor the get_interface_addresses_raw() doom-function into
13561 multiple smaller and simpler subfunctions. Cover the resulting
13562 subfunctions with unit-tests. Fixes a significant portion of
13564 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
13565 only for version <= 0.2.2.24 which is now deprecated. Closes
13567 - Remove a test for a long-defunct broken version-one
13571 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
13572 for writing the OpenBSD-specific tips. Resolves ticket 13702.
13573 - Make the tor-resolve documentation match its help string and its
13574 options. Resolves part of ticket 14325.
13575 - Log a more useful error message from tor-resolve when failing to
13576 look up a hidden service address. Resolves part of ticket 14325.
13578 o Downgraded warnings:
13579 - Don't warn when we've attempted to contact a relay using the wrong
13580 ntor onion key. Closes ticket 9635.
13582 o Removed features:
13583 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
13584 longer silently accepted as an alias for "ExitNodes".
13585 - The --enable-mempool and --enable-buf-freelists options, which
13586 were originally created to work around bad malloc implementations,
13587 no longer exist. They were off-by-default in 0.2.5. Closes
13591 - Make the checkdir/perms test complete successfully even if the
13592 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
13593 - Test that tor does not fail when key files are zero-length. Check
13594 that tor generates new keys, and overwrites the empty key files.
13595 - Test that tor generates new keys when keys are missing
13596 (existing behavior).
13597 - Test that tor does not overwrite key files that already contain
13598 data (existing behavior). Tests bug 13111. Patch by "teor".
13599 - New "make test-stem" target to run stem integration tests.
13600 Requires that the "STEM_SOURCE_DIR" environment variable be set.
13601 Closes ticket 14107.
13602 - Make the test_cmdline_args.py script work correctly on Windows.
13603 Patch from Gisle Vanem.
13604 - Move the slower unit tests into a new "./src/test/test-slow"
13605 binary that can be run independently of the other tests. Closes
13607 - Avoid undefined behavior when sampling huge values from the
13608 Laplace distribution. This made unittests fail on Raspberry Pi.
13609 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
13612 Changes in version 0.2.6.2-alpha - 2014-12-31
13613 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
13614 It introduces a major new backend for deciding when to send cells on
13615 channels, which should lead down the road to big performance
13616 increases. It contains security and statistics features for better
13617 work on hidden services, and numerous bugfixes.
13619 This release contains many new unit tests, along with major
13620 performance improvements for running testing networks using Chutney.
13621 Thanks to a series of patches contributed by "teor", testing networks
13622 should now bootstrap in seconds, rather than minutes.
13624 o Major features (relay, infrastructure):
13625 - Complete revision of the code that relays use to decide which cell
13626 to send next. Formerly, we selected the best circuit to write on
13627 each channel, but we didn't select among channels in any
13628 sophisticated way. Now, we choose the best circuits globally from
13629 among those whose channels are ready to deliver traffic.
13631 This patch implements a new inter-cmux comparison API, a global
13632 high/low watermark mechanism and a global scheduler loop for
13633 transmission prioritization across all channels as well as among
13634 circuits on one channel. This schedule is currently tuned to
13635 (tolerantly) avoid making changes in network performance, but it
13636 should form the basis for major circuit performance increases in
13637 the future. Code by Andrea; tuning by Rob Jansen; implements
13640 o Major features (hidden services):
13641 - Make HS port scanning more difficult by immediately closing the
13642 circuit when a user attempts to connect to a nonexistent port.
13643 Closes ticket 13667.
13644 - Add a HiddenServiceStatistics option that allows Tor relays to
13645 gather and publish statistics about the overall size and volume of
13646 hidden service usage. Specifically, when this option is turned on,
13647 an HSDir will publish an approximate number of hidden services
13648 that have published descriptors to it the past 24 hours. Also, if
13649 a relay has acted as a hidden service rendezvous point, it will
13650 publish the approximate amount of rendezvous cells it has relayed
13651 the past 24 hours. The statistics themselves are obfuscated so
13652 that the exact values cannot be derived. For more details see
13653 proposal 238, "Better hidden service stats from Tor relays". This
13654 feature is currently disabled by default. Implements feature 13192.
13656 o Major bugfixes (client, automap):
13657 - Repair automapping with IPv6 addresses. This automapping should
13658 have worked previously, but one piece of debugging code that we
13659 inserted to detect a regression actually caused the regression to
13660 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
13661 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
13664 o Major bugfixes (hidden services):
13665 - When closing an introduction circuit that was opened in parallel
13666 with others, don't mark the introduction point as unreachable.
13667 Previously, the first successful connection to an introduction
13668 point would make the other introduction points get marked as
13669 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
13671 o Directory authority changes:
13672 - Remove turtles as a directory authority.
13673 - Add longclaw as a new (v3) directory authority. This implements
13674 ticket 13296. This keeps the directory authority count at 9.
13676 o Major removed features:
13677 - Tor clients no longer support connecting to hidden services
13678 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
13679 option has been removed. (There shouldn't be any hidden services
13680 running these versions on the network.) Closes ticket 7803.
13682 o Minor features (client):
13683 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
13684 is enabled, reject requests with IP addresses as hostnames.
13685 Resolves ticket 13315.
13687 o Minor features (controller):
13688 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
13689 write an unscheduled heartbeat message to the log. Implements
13692 o Minor features (geoip):
13693 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
13696 o Minor features (hidden services):
13697 - When re-enabling the network, don't try to build introduction
13698 circuits until we have successfully built a circuit. This makes
13699 hidden services come up faster when the network is re-enabled.
13700 Patch from "akwizgran". Closes ticket 13447.
13701 - When we fail to retrieve a hidden service descriptor, send the
13702 controller an "HS_DESC FAILED" controller event. Implements
13704 - New HiddenServiceDirGroupReadable option to cause hidden service
13705 directories and hostname files to be created group-readable. Patch
13706 from "anon", David Stainton, and "meejah". Closes ticket 11291.
13708 o Minor features (systemd):
13709 - Where supported, when running with systemd, report successful
13710 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
13711 - When running with systemd, support systemd watchdog messages. Part
13712 of ticket 11016. Patch by Michael Scherer.
13714 o Minor features (transparent proxy):
13715 - Update the transparent proxy option checks to allow for both ipfw
13716 and pf on OS X. Closes ticket 14002.
13717 - Use the correct option when using IPv6 with transparent proxy
13718 support on Linux. Resolves 13808. Patch by Francisco Blas
13721 o Minor bugfixes (preventative security, C safety):
13722 - When reading a hexadecimal, base-32, or base-64 encoded value from
13723 a string, always overwrite the whole output buffer. This prevents
13724 some bugs where we would look at (but fortunately, not reveal)
13725 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
13727 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
13728 just the part that's used. This makes it harder for data leak bugs
13729 to occur in the event of other programming failures. Resolves
13732 o Minor bugfixes (client, microdescriptors):
13733 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
13734 computing which microdescriptors to download. This keeps us from
13735 erroneous download behavior if two microdescriptor digests ever
13736 have the same first 160 bits. Fixes part of bug 13399; bugfix
13738 - Reset a router's status if its microdescriptor digest changes,
13739 even if the first 160 bits remain the same. Fixes part of bug
13740 13399; bugfix on 0.2.3.1-alpha.
13742 o Minor bugfixes (compilation):
13743 - Silence clang warnings under --enable-expensive-hardening,
13744 including implicit truncation of 64 bit values to 32 bit, const
13745 char assignment to self, tautological compare, and additional
13746 parentheses around equality tests. Fixes bug 13577; bugfix
13748 - Fix a clang warning about checking whether an address in the
13749 middle of a structure is NULL. Fixes bug 14001; bugfix
13752 o Minor bugfixes (hidden services):
13753 - Correctly send a controller event when we find that a rendezvous
13754 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
13755 - Pre-check directory permissions for new hidden-services to avoid
13756 at least one case of "Bug: Acting on config options left us in a
13757 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
13758 - When adding a new hidden service (for example, via SETCONF), Tor
13759 no longer congratulates the user for running a relay. Fixes bug
13760 13941; bugfix on 0.2.6.1-alpha.
13761 - When fetching hidden service descriptors, we now check not only
13762 for whether we got the hidden service we had in mind, but also
13763 whether we got the particular descriptors we wanted. This prevents
13764 a class of inefficient but annoying DoS attacks by hidden service
13765 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
13768 o Minor bugfixes (Linux seccomp2 sandbox):
13769 - Make transparent proxy support work along with the seccomp2
13770 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
13771 by Francisco Blas Izquierdo Riera.
13772 - Fix a memory leak in tor-resolve when running with the sandbox
13773 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
13775 o Minor bugfixes (logging):
13776 - Downgrade warnings about RSA signature failures to info log level.
13777 Emit a warning when an extra info document is found incompatible
13778 with a corresponding router descriptor. Fixes bug 9812; bugfix
13780 - Make connection_ap_handshake_attach_circuit() log the circuit ID
13781 correctly. Fixes bug 13701; bugfix on 0.0.6.
13783 o Minor bugfixes (misc):
13784 - Stop allowing invalid address patterns like "*/24" that contain
13785 both a wildcard address and a bit prefix length. This affects all
13786 our address-range parsing code. Fixes bug 7484; bugfix
13789 o Minor bugfixes (testing networks, fast startup):
13790 - Allow Tor to build circuits using a consensus with no exits. If
13791 the consensus has no exits (typical of a bootstrapping test
13792 network), allow Tor to build circuits once enough descriptors have
13793 been downloaded. This assists in bootstrapping a testing Tor
13794 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
13796 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
13797 header to directory servers. This allows us to obtain consensuses
13798 promptly when the consensus interval is very short. This assists
13799 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
13800 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
13801 - Stop assuming that private addresses are local when checking
13802 reachability in a TestingTorNetwork. Instead, when testing, assume
13803 all OR connections are remote. (This is necessary due to many test
13804 scenarios running all relays on localhost.) This assists in
13805 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
13806 0.1.0.1-rc. Patch by "teor".
13807 - Avoid building exit circuits from a consensus with no exits. Now
13808 thanks to our fix for 13718, we accept a no-exit network as not
13809 wholly lost, but we need to remember not to try to build exit
13810 circuits on it. Closes ticket 13814; patch by "teor".
13811 - Stop requiring exits to have non-zero bandwithcapacity in a
13812 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
13813 ignore exit bandwidthcapacity. This assists in bootstrapping a
13814 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
13815 on 0.2.0.3-alpha. Patch by "teor".
13816 - Add "internal" to some bootstrap statuses when no exits are
13817 available. If the consensus does not contain Exits, Tor will only
13818 build internal circuits. In this case, relevant statuses will
13819 contain the word "internal" as indicated in the Tor control-
13820 spec.txt. When bootstrap completes, Tor will be ready to build
13821 internal circuits. If a future consensus contains Exits, exit
13822 circuits may become available. Fixes part of bug 13718; bugfix on
13823 0.2.4.10-alpha. Patch by "teor".
13824 - Decrease minimum consensus interval to 10 seconds when
13825 TestingTorNetwork is set, or 5 seconds for the first consensus.
13826 Fix assumptions throughout the code that assume larger intervals.
13827 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
13829 - Avoid excluding guards from path building in minimal test
13830 networks, when we're in a test network and excluding guards would
13831 exclude all relays. This typically occurs in incredibly small tor
13832 networks, and those using "TestingAuthVoteGuard *". Fixes part of
13833 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
13835 o Code simplification and refactoring:
13836 - Stop using can_complete_circuits as a global variable; access it
13837 with a function instead.
13838 - Avoid using operators directly as macro arguments: this lets us
13839 apply coccinelle transformations to our codebase more directly.
13840 Closes ticket 13172.
13841 - Combine the functions used to parse ClientTransportPlugin and
13842 ServerTransportPlugin into a single function. Closes ticket 6456.
13843 - Add inline functions and convenience macros for inspecting channel
13844 state. Refactor the code to use convenience macros instead of
13845 checking channel state directly. Fixes issue 7356.
13846 - Document all members of was_router_added_t and rename
13847 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
13848 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
13849 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
13850 constant instead of hardcoded value. Fixes issue 13840.
13851 - Refactor our generic strmap and digestmap types into a single
13852 implementation, so that we can add a new digest256map
13856 - Document the bridge-authority-only 'networkstatus-bridges' file.
13857 Closes ticket 13713; patch from "tom".
13858 - Fix typo in PredictedPortsRelevanceTime option description in
13859 manpage. Resolves issue 13707.
13860 - Stop suggesting that users specify relays by nickname: it isn't a
13861 good idea. Also, properly cross-reference how to specify relays in
13862 all parts of manual documenting options that take a list of
13863 relays. Closes ticket 13381.
13864 - Clarify the HiddenServiceDir option description in manpage to make
13865 it clear that relative paths are taken with respect to the current
13866 working directory. Also clarify that this behavior is not
13867 guaranteed to remain indefinitely. Fixes issue 13913.
13870 - New tests for many parts of channel, relay, and circuitmux
13871 functionality. Code by Andrea; part of 9262.
13872 - New tests for parse_transport_line(). Part of ticket 6456.
13873 - In the unit tests, use chgrp() to change the group of the unit
13874 test temporary directory to the current user, so that the sticky
13875 bit doesn't interfere with tests that check directory groups.
13877 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
13881 Changes in version 0.2.6.1-alpha - 2014-10-30
13882 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
13883 includes numerous code cleanups and new tests, and fixes a large
13884 number of annoying bugs. Out-of-memory conditions are handled better
13885 than in 0.2.5, pluggable transports have improved proxy support, and
13886 clients now use optimistic data for contacting hidden services. Also,
13887 we are now more robust to changes in what we consider a parseable
13888 directory object, so that tightening restrictions does not have a risk
13889 of introducing infinite download loops.
13891 This is the first alpha release in a new series, so expect there to be
13892 bugs. Users who would rather test out a more stable branch should stay
13893 with 0.2.5.x for now.
13895 o New compiler and system requirements:
13896 - Tor 0.2.6.x requires that your compiler support more of the C99
13897 language standard than before. The 'configure' script now detects
13898 whether your compiler supports C99 mid-block declarations and
13899 designated initializers. If it does not, Tor will not compile.
13901 We may revisit this requirement if it turns out that a significant
13902 number of people need to build Tor with compilers that don't
13903 bother implementing a 15-year-old standard. Closes ticket 13233.
13904 - Tor no longer supports systems without threading support. When we
13905 began working on Tor, there were several systems that didn't have
13906 threads, or where the thread support wasn't able to run the
13907 threads of a single process on multiple CPUs. That no longer
13908 holds: every system where Tor needs to run well now has threading
13909 support. Resolves ticket 12439.
13911 o Removed platform support:
13912 - We no longer include special code to build on Windows CE; as far
13913 as we know, nobody has used Tor on Windows CE in a very long time.
13914 Closes ticket 11446.
13916 o Major features (bridges):
13917 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
13918 transports if they are configured via the "TOR_PT_PROXY"
13919 environment variable. Implements proposal 232. Resolves
13922 o Major features (client performance, hidden services):
13923 - Allow clients to use optimistic data when connecting to a hidden
13924 service, which should remove a round-trip from hidden service
13925 initialization. See proposal 181 for details. Implements
13928 o Major features (directory system):
13929 - Upon receiving an unparseable directory object, if its digest
13930 matches what we expected, then don't try to download it again.
13931 Previously, when we got a descriptor we didn't like, we would keep
13932 trying to download it over and over. Closes ticket 11243.
13934 o Major features (sample torrc):
13935 - Add a new, infrequently-changed "torrc.minimal". This file is
13936 similar to torrc.sample, but it will change as infrequently as
13937 possible, for the benefit of users whose systems prompt them for
13938 intervention whenever a default configuration file is changed.
13939 Making this change allows us to update torrc.sample to be a more
13940 generally useful "sample torrc".
13942 o Major bugfixes (directory authorities):
13943 - Do not assign the HSDir flag to relays if they are not Valid, or
13944 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
13946 o Major bugfixes (directory bandwidth performance):
13947 - Don't flush the zlib buffer aggressively when compressing
13948 directory information for clients. This should save about 7% of
13949 the bandwidth currently used for compressed descriptors and
13950 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
13952 o Minor features (security, memory wiping):
13953 - Ensure we securely wipe keys from memory after
13954 crypto_digest_get_digest and init_curve25519_keypair_from_file
13955 have finished using them. Resolves ticket 13477.
13957 o Minor features (security, out-of-memory handling):
13958 - When handling an out-of-memory condition, allocate less memory for
13959 temporary data structures. Fixes issue 10115.
13960 - When handling an out-of-memory condition, consider more types of
13961 buffers, including those on directory connections, and zlib
13962 buffers. Resolves ticket 11792.
13965 - When identity keypair is generated for first time, log a
13966 congratulatory message that links to the new relay lifecycle
13967 document. Implements feature 10427.
13969 o Minor features (client):
13970 - Clients are now willing to send optimistic data (before they
13971 receive a 'connected' cell) to relays of any version. (Relays
13972 without support for optimistic data are no longer supported on the
13973 Tor network.) Resolves ticket 13153.
13975 o Minor features (directory authorities):
13976 - Don't list relays with a bandwidth estimate of 0 in the consensus.
13977 Implements a feature proposed during discussion of bug 13000.
13978 - In tor-gencert, report an error if the user provides the same
13979 argument more than once.
13980 - If a directory authority can't find a best consensus method in the
13981 votes that it holds, it now falls back to its favorite consensus
13982 method. Previously, it fell back to method 1. Neither of these is
13983 likely to get enough signatures, but "fall back to favorite"
13984 doesn't require us to maintain support an obsolete consensus
13985 method. Implements part of proposal 215.
13987 o Minor features (logging):
13988 - On Unix-like systems, you can now use named pipes as the target of
13989 the Log option, and other options that try to append to files.
13990 Closes ticket 12061. Patch from "carlo von lynX".
13991 - When opening a log file at startup, send it every log message that
13992 we generated between startup and opening it. Previously, log
13993 messages that were generated before opening the log file were only
13994 logged to stdout. Closes ticket 6938.
13995 - Add a TruncateLogFile option to overwrite logs instead of
13996 appending to them. Closes ticket 5583.
13998 o Minor features (portability, Solaris):
13999 - Threads are no longer disabled by default on Solaris; we believe
14000 that the versions of Solaris with broken threading support are all
14001 obsolete by now. Resolves ticket 9495.
14003 o Minor features (relay):
14004 - Re-check our address after we detect a changed IP address from
14005 getsockname(). This ensures that the controller command "GETINFO
14006 address" will report the correct value. Resolves ticket 11582.
14008 - A new AccountingRule option lets Relays set whether they'd like
14009 AccountingMax to be applied separately to inbound and outbound
14010 traffic, or applied to the sum of inbound and outbound traffic.
14011 Resolves ticket 961. Patch by "chobe".
14013 o Minor features (testing networks):
14014 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
14015 the "Exit" flag regardless of their uptime, bandwidth, or exit
14016 policy. TestingTorNetwork must be set for this option to have any
14017 effect. Previously, authorities would take up to 35 minutes to
14018 give nodes the Exit flag in a test network. Partially implements
14021 o Minor features (validation):
14022 - Check all date/time values passed to tor_timegm and
14023 parse_rfc1123_time for validity, taking leap years into account.
14024 Improves HTTP header validation. Implemented with bug 13476.
14025 - In correct_tm(), limit the range of values returned by system
14026 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
14027 This means we don't have to deal with negative or too large dates,
14028 even if a clock is wrong. Otherwise we might fail to read a file
14029 written by us which includes such a date. Fixes bug 13476.
14031 o Minor bugfixes (bridge clients):
14032 - When configured to use a bridge without an identity digest (not
14033 recommended), avoid launching an extra channel to it when
14034 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
14036 o Minor bugfixes (bridges):
14037 - When DisableNetwork is set, do not launch pluggable transport
14038 plugins, and if any are running, terminate them. Fixes bug 13213;
14039 bugfix on 0.2.3.6-alpha.
14041 o Minor bugfixes (C correctness):
14042 - Fix several instances of possible integer overflow/underflow/NaN.
14043 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
14045 - In circuit_build_times_calculate_timeout() in circuitstats.c,
14046 avoid dividing by zero in the pareto calculations. This traps
14047 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
14049 - Fix an integer overflow in format_time_interval(). Fixes bug
14050 13393; bugfix on 0.2.0.10-alpha.
14051 - Set the correct day of year value when the system's localtime(_r)
14052 or gmtime(_r) functions fail to set struct tm. Not externally
14053 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
14054 - Avoid unlikely signed integer overflow in tor_timegm on systems
14055 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
14057 o Minor bugfixes (client):
14058 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
14059 BadExit flag are not considered worthy candidates. Fixes bug
14060 13066; bugfix on 0.1.2.3-alpha.
14061 - Use the consensus schedule for downloading consensuses, and not
14062 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
14063 - Handle unsupported or malformed SOCKS5 requests properly by
14064 responding with the appropriate error message before closing the
14065 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
14067 o Minor bugfixes (client, torrc):
14068 - Stop modifying the value of our DirReqStatistics torrc option just
14069 because we're not a bridge or relay. This bug was causing Tor
14070 Browser users to write "DirReqStatistics 0" in their torrc files
14071 as if they had chosen to change the config. Fixes bug 4244; bugfix
14073 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
14074 that our options have changed every time we SIGHUP. Fixes bug
14075 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
14077 o Minor bugfixes (controller):
14078 - Return an error when the second or later arguments of the
14079 "setevents" controller command are invalid events. Previously we
14080 would return success while silently skipping invalid events. Fixes
14081 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
14083 o Minor bugfixes (directory system):
14084 - Always believe that v3 directory authorities serve extra-info
14085 documents, whether they advertise "caches-extra-info" or not.
14086 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14087 - When running as a v3 directory authority, advertise that you serve
14088 extra-info documents so that clients who want them can find them
14089 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14090 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
14091 Previously, directories offering BRIDGE_DIRINFO and some other
14092 flag (i.e. microdescriptors or extrainfo) would be ignored when
14093 looking for bridges. Partially fixes bug 13163; bugfix
14096 o Minor bugfixes (networking):
14097 - Check for orconns and use connection_or_close_for_error() rather
14098 than connection_mark_for_close() directly in the getsockopt()
14099 failure case of connection_handle_write_impl(). Fixes bug 11302;
14100 bugfix on 0.2.4.4-alpha.
14102 o Minor bugfixes (relay):
14103 - When generating our family list, remove spaces from around the
14104 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
14105 - If our previous bandwidth estimate was 0 bytes, allow publishing a
14106 new relay descriptor immediately. Fixes bug 13000; bugfix
14109 o Minor bugfixes (testing networks):
14110 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
14111 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
14112 - Stop using the default authorities in networks which provide both
14113 AlternateDirAuthority and AlternateBridgeAuthority. Partially
14114 fixes bug 13163; bugfix on 0.2.0.13-alpha.
14116 o Minor bugfixes (testing):
14117 - Stop spawn test failures due to a race condition between the
14118 SIGCHLD handler updating the process status, and the test reading
14119 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
14121 o Minor bugfixes (testing, Windows):
14122 - Avoid passing an extra backslash when creating a temporary
14123 directory for running the unit tests on Windows. Fixes bug 12392;
14124 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
14126 o Minor bugfixes (windows):
14127 - Remove code to special-case handling of NTE_BAD_KEYSET when
14128 acquiring windows CryptoAPI context. This error can't actually
14129 occur for the parameters we're providing. Fixes bug 10816; bugfix
14132 o Minor bugfixes (zlib):
14133 - Avoid truncating a zlib stream when trying to finalize it with an
14134 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
14137 - Allow our configure script to build correctly with autoconf 2.62
14138 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
14139 - Improve the error message from ./configure to make it clear that
14140 when asciidoc has not been found, the user will have to either add
14141 --disable-asciidoc argument or install asciidoc. Resolves
14144 o Code simplification and refactoring:
14145 - Change the entry_is_live() function to take named bitfield
14146 elements instead of an unnamed list of booleans. Closes
14148 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
14149 Resolves ticket 12205.
14150 - Use calloc and reallocarray functions instead of multiply-
14151 then-malloc. This makes it less likely for us to fall victim to an
14152 integer overflow attack when allocating. Resolves ticket 12855.
14153 - Use the standard macro name SIZE_MAX, instead of our
14155 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
14156 functions which take them as arguments. Replace 0 with NO_DIRINFO
14157 in a function call for clarity. Seeks to prevent future issues
14159 - Avoid 4 null pointer errors under clang static analysis by using
14160 tor_assert() to prove that the pointers aren't null. Fixes
14162 - Rework the API of policies_parse_exit_policy() to use a bitmask to
14163 represent parsing options, instead of a confusing mess of
14164 booleans. Resolves ticket 8197.
14165 - Introduce a helper function to parse ExitPolicy in
14166 or_options_t structure.
14169 - Add a doc/TUNING document with tips for handling large numbers of
14170 TCP connections when running busy Tor relay. Update the warning
14171 message to point to this file when running out of sockets
14172 operating system is allowing to use simultaneously. Resolves
14175 o Removed features:
14176 - We no longer remind the user about configuration options that have
14177 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
14178 - Remove our old, non-weighted bandwidth-based node selection code.
14179 Previously, we used it as a fallback when we couldn't perform
14180 weighted bandwidth-based node selection. But that would only
14181 happen in the cases where we had no consensus, or when we had a
14182 consensus generated by buggy or ancient directory authorities. In
14183 either case, it's better to use the more modern, better maintained
14184 algorithm, with reasonable defaults for the weights. Closes
14186 - Remove the --disable-curve25519 configure option. Relays and
14187 clients now are required to support curve25519 and the
14189 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
14190 used to be deprecated synonyms for "StrictNodes", are now marked
14191 obsolete. Resolves ticket 12226.
14192 - Clients don't understand the BadDirectory flag in the consensus
14193 anymore, and ignore it.
14196 - Refactor the function that chooses guard nodes so that it can more
14197 easily be tested; write some tests for it.
14198 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
14199 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
14200 - Create unit tests for format_time_interval(). With bug 13393.
14201 - Add unit tests for tor_timegm signed overflow, tor_timegm and
14202 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
14203 tests (visible) fixes in bug 13476.
14204 - Add a "coverage-html" make target to generate HTML-visualized
14205 coverage results when building with --enable-coverage. (Requires
14206 lcov.) Patch from Kevin Murray.
14207 - Enable the backtrace handler (where supported) when running the
14209 - Revise all unit tests that used the legacy test_* macros to
14210 instead use the recommended tt_* macros. This patch was generated
14211 with coccinelle, to avoid manual errors. Closes ticket 13119.
14213 o Distribution (systemd):
14214 - systemd unit file: only allow tor to write to /var/lib/tor and
14215 /var/log/tor. The rest of the filesystem is accessible for reading
14216 only. Patch by intrigeri; resolves ticket 12751.
14217 - systemd unit file: ensure that the process and all its children
14218 can never gain new privileges. Patch by intrigeri; resolves
14220 - systemd unit file: set up /var/run/tor as writable for the Tor
14221 service. Patch by intrigeri; resolves ticket 13196.
14223 o Removed features (directory authorities):
14224 - Remove code that prevented authorities from listing Tor relays
14225 affected by CVE-2011-2769 as guards. These relays are already
14226 rejected altogether due to the minimum version requirement of
14227 0.2.3.16-alpha. Closes ticket 13152.
14228 - The "AuthDirRejectUnlisted" option no longer has any effect, as
14229 the fingerprints file (approved-routers) has been deprecated.
14230 - Directory authorities do not support being Naming dirauths anymore.
14231 The "NamingAuthoritativeDir" config option is now obsolete.
14232 - Directory authorities do not support giving out the BadDirectory
14234 - Directory authorities no longer advertise or support consensus
14235 methods 1 through 12 inclusive. These consensus methods were
14236 obsolete and/or insecure: maintaining the ability to support them
14237 served no good purpose. Implements part of proposal 215; closes
14240 o Testing (test-network.sh):
14241 - Stop using "echo -n", as some shells' built-in echo doesn't
14242 support "-n". Instead, use "/bin/echo -n". Partially fixes
14244 - Stop an apparent test-network hang when used with make -j2. Fixes
14246 - Add a --delay option to test-network.sh, which configures the
14247 delay before the chutney network tests for data transmission.
14248 Partially implements ticket 13161.
14251 Changes in version 0.2.5.10 - 2014-10-24
14252 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
14254 It adds several new security features, including improved
14255 denial-of-service resistance for relays, new compiler hardening
14256 options, and a system-call sandbox for hardened installations on Linux
14257 (requires seccomp2). The controller protocol has several new features,
14258 resolving IPv6 addresses should work better than before, and relays
14259 should be a little more CPU-efficient. We've added support for more
14260 OpenBSD and FreeBSD transparent proxy types. We've improved the build
14261 system and testing infrastructure to allow unit testing of more parts
14262 of the Tor codebase. Finally, we've addressed several nagging pluggable
14263 transport usability issues, and included numerous other small bugfixes
14264 and features mentioned below.
14266 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
14267 have accumulated many known flaws; everyone should upgrade.
14269 o Deprecated versions:
14270 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
14271 attention for some while.
14274 Changes in version 0.2.5.9-rc - 2014-10-20
14275 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
14276 series. It disables SSL3 in response to the recent "POODLE" attack
14277 (even though POODLE does not affect Tor). It also works around a crash
14278 bug caused by some operating systems' response to the "POODLE" attack
14279 (which does affect Tor). It also contains a few miscellaneous fixes.
14281 o Major security fixes:
14282 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
14283 today support TLS 1.0 or later, so we can safely turn off support
14284 for this old (and insecure) protocol. Fixes bug 13426.
14286 o Major bugfixes (openssl bug workaround):
14287 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
14288 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
14289 13471. This is a workaround for an OpenSSL bug.
14292 - Disable the sandbox name resolver cache when running tor-resolve:
14293 tor-resolve doesn't use the sandbox code, and turning it on was
14294 breaking attempts to do tor-resolve on a non-default server on
14295 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
14297 o Compilation fixes:
14298 - Build and run correctly on systems like OpenBSD-current that have
14299 patched OpenSSL to remove get_cipher_by_char and/or its
14300 implementations. Fixes issue 13325.
14302 o Downgraded warnings:
14303 - Downgrade the severity of the 'unexpected sendme cell from client'
14304 from 'warn' to 'protocol warning'. Closes ticket 8093.
14307 Changes in version 0.2.4.25 - 2014-10-20
14308 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
14309 (even though POODLE does not affect Tor). It also works around a crash
14310 bug caused by some operating systems' response to the "POODLE" attack
14311 (which does affect Tor).
14313 o Major security fixes (also in 0.2.5.9-rc):
14314 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
14315 today support TLS 1.0 or later, so we can safely turn off support
14316 for this old (and insecure) protocol. Fixes bug 13426.
14318 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
14319 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
14320 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
14321 13471. This is a workaround for an OpenSSL bug.
14324 Changes in version 0.2.5.8-rc - 2014-09-22
14325 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
14326 series. It fixes a bug that affects consistency and speed when
14327 connecting to hidden services, and it updates the location of one of
14328 the directory authorities.
14331 - Clients now send the correct address for their chosen rendezvous
14332 point when trying to access a hidden service. They used to send
14333 the wrong address, which would still work some of the time because
14334 they also sent the identity digest of the rendezvous point, and if
14335 the hidden service happened to try connecting to the rendezvous
14336 point from a relay that already had a connection open to it,
14337 the relay would reuse that connection. Now connections to hidden
14338 services should be more robust and faster. Also, this bug meant
14339 that clients were leaking to the hidden service whether they were
14340 on a little-endian (common) or big-endian (rare) system, which for
14341 some users might have reduced their anonymity. Fixes bug 13151;
14342 bugfix on 0.2.1.5-alpha.
14344 o Directory authority changes:
14345 - Change IP address for gabelmoo (v3 directory authority).
14348 Changes in version 0.2.4.24 - 2014-09-22
14349 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
14350 connecting to hidden services, and it updates the location of one of
14351 the directory authorities.
14354 - Clients now send the correct address for their chosen rendezvous
14355 point when trying to access a hidden service. They used to send
14356 the wrong address, which would still work some of the time because
14357 they also sent the identity digest of the rendezvous point, and if
14358 the hidden service happened to try connecting to the rendezvous
14359 point from a relay that already had a connection open to it,
14360 the relay would reuse that connection. Now connections to hidden
14361 services should be more robust and faster. Also, this bug meant
14362 that clients were leaking to the hidden service whether they were
14363 on a little-endian (common) or big-endian (rare) system, which for
14364 some users might have reduced their anonymity. Fixes bug 13151;
14365 bugfix on 0.2.1.5-alpha.
14367 o Directory authority changes:
14368 - Change IP address for gabelmoo (v3 directory authority).
14370 o Minor features (geoip):
14371 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
14375 Changes in version 0.2.5.7-rc - 2014-09-11
14376 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
14377 release series, and some long-standing bugs related to ORPort reachability
14378 testing and failure to send CREATE cells. It is the first release
14379 candidate for the Tor 0.2.5.x series.
14381 o Major bugfixes (client, startup):
14382 - Start making circuits as soon as DisabledNetwork is turned off.
14383 When Tor started with DisabledNetwork set, it would correctly
14384 conclude that it shouldn't build circuits, but it would mistakenly
14385 cache this conclusion, and continue believing it even when
14386 DisableNetwork is set to 0. Fixes the bug introduced by the fix
14387 for bug 11200; bugfix on 0.2.5.4-alpha.
14388 - Resume expanding abbreviations for command-line options. The fix
14389 for bug 4647 accidentally removed our hack from bug 586 that
14390 rewrote HashedControlPassword to __HashedControlSessionPassword
14391 when it appears on the commandline (which allowed the user to set
14392 her own HashedControlPassword in the torrc file while the
14393 controller generates a fresh session password for each run). Fixes
14394 bug 12948; bugfix on 0.2.5.1-alpha.
14395 - Warn about attempts to run hidden services and relays in the same
14396 process: that's probably not a good idea. Closes ticket 12908.
14398 o Major bugfixes (relay):
14399 - Avoid queuing or sending destroy cells for circuit ID zero when we
14400 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
14401 Found and fixed by "cypherpunks".
14402 - Fix ORPort reachability detection on relays running behind a
14403 proxy, by correctly updating the "local" mark on the controlling
14404 channel when changing the address of an or_connection_t after the
14405 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
14407 o Minor features (bridge):
14408 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
14409 cookie file for the ExtORPort g+r by default.
14411 o Minor features (geoip):
14412 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
14415 o Minor bugfixes (logging):
14416 - Reduce the log severity of the "Pluggable transport proxy does not
14417 provide any needed transports and will not be launched." message,
14418 since Tor Browser includes several ClientTransportPlugin lines in
14419 its torrc-defaults file, leading every Tor Browser user who looks
14420 at her logs to see these notices and wonder if they're dangerous.
14421 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
14422 - Downgrade "Unexpected onionskin length after decryption" warning
14423 to a protocol-warn, since there's nothing relay operators can do
14424 about a client that sends them a malformed create cell. Resolves
14425 bug 12996; bugfix on 0.0.6rc1.
14426 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
14427 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
14428 - When logging information about an EXTEND2 or EXTENDED2 cell, log
14429 their names correctly. Fixes part of bug 12700; bugfix
14431 - When logging information about a relay cell whose command we don't
14432 recognize, log its command as an integer. Fixes part of bug 12700;
14433 bugfix on 0.2.1.10-alpha.
14434 - Escape all strings from the directory connection before logging
14435 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
14437 o Minor bugfixes (controller):
14438 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
14439 bug 12864; bugfix on 0.2.5.1-alpha.
14440 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
14441 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
14444 o Minor bugfixes (compilation):
14445 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
14446 bugfix on 0.2.5.5-alpha.
14447 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
14448 0.2.5.1-alpha. Patch from "NewEraCracker".
14449 - In routerlist_assert_ok(), don't take the address of a
14450 routerinfo's cache_info member unless that routerinfo is non-NULL.
14451 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
14452 - Fix a large number of false positive warnings from the clang
14453 analyzer static analysis tool. This should make real warnings
14454 easier for clang analyzer to find. Patch from "teor". Closes
14457 o Distribution (systemd):
14458 - Verify configuration file via ExecStartPre in the systemd unit
14459 file. Patch from intrigeri; resolves ticket 12730.
14460 - Explicitly disable RunAsDaemon in the systemd unit file. Our
14461 current systemd unit uses "Type = simple", so systemd does not
14462 expect tor to fork. If the user has "RunAsDaemon 1" in their
14463 torrc, then things won't work as expected. This is e.g. the case
14464 on Debian (and derivatives), since there we pass "--defaults-torrc
14465 /usr/share/tor/tor-service-defaults-torrc" (that contains
14466 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
14470 - Adjust the URLs in the README to refer to the new locations of
14471 several documents on the website. Fixes bug 12830. Patch from
14473 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
14477 Changes in version 0.2.5.6-alpha - 2014-07-28
14478 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
14479 risk from guard rotation, and fixes a variety of other issues to get
14480 us closer to a release candidate.
14482 o Major features (also in 0.2.4.23):
14483 - Make the number of entry guards configurable via a new
14484 NumEntryGuards consensus parameter, and the number of directory
14485 guards configurable via a new NumDirectoryGuards consensus
14486 parameter. Implements ticket 12688.
14488 o Major bugfixes (also in 0.2.4.23):
14489 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
14490 implementation that caused incorrect results on 32-bit
14491 implementations when certain malformed inputs were used along with
14492 a small class of private ntor keys. This bug does not currently
14493 appear to allow an attacker to learn private keys or impersonate a
14494 Tor server, but it could provide a means to distinguish 32-bit Tor
14495 implementations from 64-bit Tor implementations. Fixes bug 12694;
14496 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
14500 - Perform circuit cleanup operations even when circuit
14501 construction operations are disabled (because the network is
14502 disabled, or because there isn't enough directory information).
14503 Previously, when we were not building predictive circuits, we
14504 were not closing expired circuits either. Fixes bug 8387; bugfix on
14505 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
14506 became more strict about when we have "enough directory information
14507 to build circuits".
14510 - Authorities now assign the Guard flag to the fastest 25% of the
14511 network (it used to be the fastest 50%). Also raise the consensus
14512 weight that guarantees the Guard flag from 250 to 2000. For the
14513 current network, this results in about 1100 guards, down from 2500.
14514 This step paves the way for moving the number of entry guards
14515 down to 1 (proposal 236) while still providing reasonable expected
14516 performance for most users. Implements ticket 12690.
14517 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
14519 - Slightly enhance the diagnostic message for bug 12184.
14521 o Minor bugfixes (also in 0.2.4.23):
14522 - Warn and drop the circuit if we receive an inbound 'relay early'
14523 cell. Those used to be normal to receive on hidden service circuits
14524 due to bug 1038, but the buggy Tor versions are long gone from
14525 the network so we can afford to resume watching for them. Resolves
14526 the rest of bug 1038; bugfix on 0.2.1.19.
14527 - Correct a confusing error message when trying to extend a circuit
14528 via the control protocol but we don't know a descriptor or
14529 microdescriptor for one of the specified relays. Fixes bug 12718;
14530 bugfix on 0.2.3.1-alpha.
14533 - Fix compilation when building with bufferevents enabled. (This
14534 configuration is still not expected to work, however.)
14535 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
14536 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
14538 - Compile correctly with builds and forks of OpenSSL (such as
14539 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
14540 0.2.1.1-alpha. Patch from "dhill".
14543 Changes in version 0.2.4.23 - 2014-07-28
14544 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
14545 guard rotation, and also backports several important fixes from the
14546 Tor 0.2.5 alpha release series.
14549 - Clients now look at the "usecreatefast" consensus parameter to
14550 decide whether to use CREATE_FAST or CREATE cells for the first hop
14551 of their circuit. This approach can improve security on connections
14552 where Tor's circuit handshake is stronger than the available TLS
14553 connection security levels, but the tradeoff is more computational
14554 load on guard relays. Implements proposal 221. Resolves ticket 9386.
14555 - Make the number of entry guards configurable via a new
14556 NumEntryGuards consensus parameter, and the number of directory
14557 guards configurable via a new NumDirectoryGuards consensus
14558 parameter. Implements ticket 12688.
14561 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
14562 implementation that caused incorrect results on 32-bit
14563 implementations when certain malformed inputs were used along with
14564 a small class of private ntor keys. This bug does not currently
14565 appear to allow an attacker to learn private keys or impersonate a
14566 Tor server, but it could provide a means to distinguish 32-bit Tor
14567 implementations from 64-bit Tor implementations. Fixes bug 12694;
14568 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
14572 - Warn and drop the circuit if we receive an inbound 'relay early'
14573 cell. Those used to be normal to receive on hidden service circuits
14574 due to bug 1038, but the buggy Tor versions are long gone from
14575 the network so we can afford to resume watching for them. Resolves
14576 the rest of bug 1038; bugfix on 0.2.1.19.
14577 - Correct a confusing error message when trying to extend a circuit
14578 via the control protocol but we don't know a descriptor or
14579 microdescriptor for one of the specified relays. Fixes bug 12718;
14580 bugfix on 0.2.3.1-alpha.
14581 - Avoid an illegal read from stack when initializing the TLS
14582 module using a version of OpenSSL without all of the ciphers
14583 used by the v2 link handshake. Fixes bug 12227; bugfix on
14584 0.2.4.8-alpha. Found by "starlight".
14587 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
14591 Changes in version 0.2.5.5-alpha - 2014-06-18
14592 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
14593 0.2.5.x release series, including a couple of DoS issues, some
14594 performance regressions, a large number of bugs affecting the Linux
14595 seccomp2 sandbox code, and various other bugfixes. It also adds
14596 diagnostic bugfixes for a few tricky issues that we're trying to
14599 o Major features (security, traffic analysis resistance):
14600 - Several major improvements to the algorithm used to decide when to
14601 close TLS connections. Previous versions of Tor closed connections
14602 at a fixed interval after the last time a non-padding cell was
14603 sent over the connection, regardless of the target of the
14604 connection. Now, we randomize the intervals by adding up to 50% of
14605 their base value, we measure the length of time since connection
14606 last had at least one circuit, and we allow connections to known
14607 ORs to remain open a little longer (15 minutes instead of 3
14608 minutes minimum). These changes should improve Tor's resistance
14609 against some kinds of traffic analysis, and lower some overhead
14610 from needlessly closed connections. Fixes ticket 6799.
14611 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
14613 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
14614 - Fix a memory leak that could occur if a microdescriptor parse
14615 fails during the tokenizing step. This bug could enable a memory
14616 exhaustion attack by directory servers. Fixes bug 11649; bugfix
14619 o Major bugfixes (security, directory authorities):
14620 - Directory authorities now include a digest of each relay's
14621 identity key as a part of its microdescriptor.
14623 This is a workaround for bug 11743 (reported by "cypherpunks"),
14624 where Tor clients do not support receiving multiple
14625 microdescriptors with the same SHA256 digest in the same
14626 consensus. When clients receive a consensus like this, they only
14627 use one of the relays. Without this fix, a hostile relay could
14628 selectively disable some client use of target relays by
14629 constructing a router descriptor with a different identity and the
14630 same microdescriptor parameters and getting the authorities to
14631 list it in a microdescriptor consensus. This fix prevents an
14632 attacker from causing a microdescriptor collision, because the
14633 router's identity is not forgeable.
14635 o Major bugfixes (relay):
14636 - Use a direct dirport connection when uploading non-anonymous
14637 descriptors to the directory authorities. Previously, relays would
14638 incorrectly use tunnel connections under a fairly wide variety of
14639 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
14640 - When a circuit accidentally has the same circuit ID for its
14641 forward and reverse direction, correctly detect the direction of
14642 cells using that circuit. Previously, this bug made roughly one
14643 circuit in a million non-functional. Fixes bug 12195; this is a
14644 bugfix on every version of Tor.
14646 o Major bugfixes (client, pluggable transports):
14647 - When managing pluggable transports, use OS notification facilities
14648 to learn if they have crashed, and don't attempt to kill any
14649 process that has already exited. Fixes bug 8746; bugfix
14652 o Minor features (diagnostic):
14653 - When logging a warning because of bug 7164, additionally check the
14654 hash table for consistency (as proposed on ticket 11737). This may
14655 help diagnose bug 7164.
14656 - When we log a heartbeat, log how many one-hop circuits we have
14657 that are at least 30 minutes old, and log status information about
14658 a few of them. This is an attempt to track down bug 8387.
14659 - When encountering an unexpected CR while writing text to a file on
14660 Windows, log the name of the file. Should help diagnosing
14662 - Give more specific warnings when a client notices that an onion
14663 handshake has failed. Fixes ticket 9635.
14664 - Add significant new logging code to attempt to diagnose bug 12184,
14665 where relays seem to run out of available circuit IDs.
14666 - Improve the diagnostic log message for bug 8387 even further to
14667 try to improve our odds of figuring out why one-hop directory
14668 circuits sometimes do not get closed.
14670 o Minor features (security, memory management):
14671 - Memory allocation tricks (mempools and buffer freelists) are now
14672 disabled by default. You can turn them back on with
14673 --enable-mempools and --enable-buf-freelists respectively. We're
14674 disabling these features because malloc performance is good enough
14675 on most platforms, and a similar feature in OpenSSL exacerbated
14676 exploitation of the Heartbleed attack. Resolves ticket 11476.
14678 o Minor features (security):
14679 - Apply the secure SipHash-2-4 function to the hash table mapping
14680 circuit IDs and channels to circuits. We missed this one when we
14681 were converting all the other hash functions to use SipHash back
14682 in 0.2.5.3-alpha. Resolves ticket 11750.
14684 o Minor features (build):
14685 - The configure script has a --disable-seccomp option to turn off
14686 support for libseccomp on systems that have it, in case it (or
14687 Tor's use of it) is broken. Resolves ticket 11628.
14689 o Minor features (other):
14690 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
14693 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
14694 - When running a hidden service, do not allow TunneledDirConns 0;
14695 this will keep the hidden service from running, and also
14696 make it publish its descriptors directly over HTTP. Fixes bug 10849;
14697 bugfix on 0.2.1.1-alpha.
14699 o Minor bugfixes (performance):
14700 - Avoid a bug where every successful connection made us recompute
14701 the flag telling us whether we have sufficient information to
14702 build circuits. Previously, we would forget our cached value
14703 whenever we successfully opened a channel (or marked a router as
14704 running or not running for any other reason), regardless of
14705 whether we had previously believed the router to be running. This
14706 forced us to run an expensive update operation far too often.
14707 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
14708 - Avoid using tor_memeq() for checking relay cell integrity. This
14709 removes a possible performance bottleneck. Fixes part of bug
14710 12169; bugfix on 0.2.1.31.
14712 o Minor bugfixes (compilation):
14713 - Fix compilation of test_status.c when building with MVSC. Bugfix
14714 on 0.2.5.4-alpha. Patch from Gisle Vanem.
14715 - Resolve GCC complaints on OpenBSD about discarding constness in
14716 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
14717 on 0.1.1.23. Patch from Dana Koch.
14718 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
14719 treatment of long and time_t as comparable types. Fixes part of
14720 bug 11633. Patch from Dana Koch.
14721 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
14722 11623; bugfix on 0.2.5.3-alpha.
14723 - When deciding whether to build the 64-bit curve25519
14724 implementation, detect platforms where we can compile 128-bit
14725 arithmetic but cannot link it. Fixes bug 11729; bugfix on
14726 0.2.4.8-alpha. Patch from "conradev".
14727 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
14728 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
14729 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
14732 o Minor bugfixes (Directory server):
14733 - When sending a compressed set of descriptors or microdescriptors,
14734 make sure to finalize the zlib stream. Previously, we would write
14735 all the compressed data, but if the last descriptor we wanted to
14736 send was missing or too old, we would not mark the stream as
14737 finished. This caused problems for decompression tools. Fixes bug
14738 11648; bugfix on 0.1.1.23.
14740 o Minor bugfixes (Linux seccomp sandbox):
14741 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
14742 11622; bugfix on 0.2.5.1-alpha.
14743 - Avoid crashing when re-opening listener ports with the seccomp
14744 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
14745 - Avoid crashing with the seccomp sandbox enabled along with
14746 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
14747 - When we receive a SIGHUP with the sandbox enabled, correctly
14748 support rotating our log files. Fixes bug 12032; bugfix
14750 - Avoid crash when running with sandboxing enabled and
14751 DirReqStatistics not disabled. Fixes bug 12035; bugfix
14753 - Fix a "BUG" warning when trying to write bridge-stats files with
14754 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
14756 - Prevent the sandbox from crashing on startup when run with the
14757 --enable-expensive-hardening configuration option. Fixes bug
14758 11477; bugfix on 0.2.5.4-alpha.
14759 - When running with DirPortFrontPage and sandboxing both enabled,
14760 reload the DirPortFrontPage correctly when restarting. Fixes bug
14761 12028; bugfix on 0.2.5.1-alpha.
14762 - Don't try to enable the sandbox when using the Tor binary to check
14763 its configuration, hash a passphrase, or so on. Doing so was
14764 crashing on startup for some users. Fixes bug 11609; bugfix
14766 - Avoid warnings when running with sandboxing and node statistics
14767 enabled at the same time. Fixes part of 12064; bugfix on
14768 0.2.5.1-alpha. Patch from Michael Wolf.
14769 - Avoid warnings when running with sandboxing enabled at the same
14770 time as cookie authentication, hidden services, or directory
14771 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
14772 - Do not allow options that require calls to exec to be enabled
14773 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
14774 bug 12043; bugfix on 0.2.5.1-alpha.
14775 - Handle failures in getpwnam()/getpwuid() when running with the
14776 User option set and the Linux syscall sandbox enabled. Fixes bug
14777 11946; bugfix on 0.2.5.1-alpha.
14778 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
14779 to avoid calling getaddrinfo() after installing the sandbox
14780 filters. Previously, it preloaded a cache with the IPv4 address
14781 for our hostname, and nothing else. Now, it loads the cache with
14782 every address that it used to initialize the Tor process. Fixes
14783 bug 11970; bugfix on 0.2.5.1-alpha.
14785 o Minor bugfixes (pluggable transports):
14786 - Enable the ExtORPortCookieAuthFile option, to allow changing the
14787 default location of the authentication token for the extended OR
14788 Port as used by sever-side pluggable transports. We had
14789 implemented this option before, but the code to make it settable
14790 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
14791 - Avoid another 60-second delay when starting Tor in a pluggable-
14792 transport-using configuration when we already have cached
14793 descriptors for our bridges. Fixes bug 11965; bugfix
14796 o Minor bugfixes (client):
14797 - Avoid "Tried to open a socket with DisableNetwork set" warnings
14798 when starting a client with bridges configured and DisableNetwork
14799 set. (Tor launcher starts Tor with DisableNetwork set the first
14800 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
14802 o Minor bugfixes (testing):
14803 - The Python parts of the test scripts now work on Python 3 as well
14804 as Python 2, so systems where '/usr/bin/python' is Python 3 will
14805 no longer have the tests break. Fixes bug 11608; bugfix
14807 - When looking for versions of python that we could run the tests
14808 with, check for "python2.7" and "python3.3"; previously we were
14809 only looking for "python", "python2", and "python3". Patch from
14810 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
14811 - Fix all valgrind warnings produced by the unit tests. There were
14812 over a thousand memory leak warnings previously, mostly produced
14813 by forgetting to free things in the unit test code. Fixes bug
14814 11618, bugfixes on many versions of Tor.
14816 o Minor bugfixes (tor-fw-helper):
14817 - Give a correct log message when tor-fw-helper fails to launch.
14818 (Previously, we would say something like "tor-fw-helper sent us a
14819 string we could not parse".) Fixes bug 9781; bugfix
14822 o Minor bugfixes (relay, threading):
14823 - Check return code on spawn_func() in cpuworker code, so that we
14824 don't think we've spawned a nonworking cpuworker and write junk to
14825 it forever. Fix related to bug 4345; bugfix on all released Tor
14826 versions. Found by "skruffy".
14827 - Use a pthread_attr to make sure that spawn_func() cannot return an
14828 error while at the same time launching a thread. Fix related to
14829 bug 4345; bugfix on all released Tor versions. Reported
14832 o Minor bugfixes (relay, oom prevention):
14833 - Correctly detect the total available system memory. We tried to do
14834 this in 0.2.5.4-alpha, but the code was set up to always return an
14835 error value, even on success. Fixes bug 11805; bugfix
14838 o Minor bugfixes (relay, other):
14839 - We now drop CREATE cells for already-existent circuit IDs and for
14840 zero-valued circuit IDs, regardless of other factors that might
14841 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
14843 - Avoid an illegal read from stack when initializing the TLS module
14844 using a version of OpenSSL without all of the ciphers used by the
14845 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
14847 - When rejecting DATA cells for stream_id zero, still count them
14848 against the circuit's deliver window so that we don't fail to send
14849 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
14851 o Minor bugfixes (logging):
14852 - Fix a misformatted log message about delayed directory fetches.
14853 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
14854 - Squelch a spurious LD_BUG message "No origin circuit for
14855 successful SOCKS stream" in certain hidden service failure cases;
14859 - Include a tor.service file in contrib/dist for use with systemd.
14860 Some distributions will be able to use this file unmodified;
14861 others will need to tweak it, or write their own. Patch from Jamie
14862 Nguyen; resolves ticket 8368.
14865 - Clean up several option names in the manpage to match their real
14866 names, add the missing documentation for a couple of testing and
14867 directory authority options, remove the documentation for a
14868 V2-directory fetching option that no longer exists. Resolves
14870 - Correct the documentation so that it lists the correct directory
14871 for the stats files. (They are in a subdirectory called "stats",
14873 - In the manpage, move more authority-only options into the
14874 directory authority section so that operators of regular directory
14875 caches don't get confused.
14878 - The contrib directory has been sorted and tidied. Before, it was
14879 an unsorted dumping ground for useful and not-so-useful things.
14880 Now, it is divided based on functionality, and the items which
14881 seemed to be nonfunctional or useless have been removed. Resolves
14882 ticket 8966; based on patches from "rl1987".
14885 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
14886 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
14887 - The TunnelDirConns and PreferTunnelledDirConns options no longer
14888 exist; tunneled directory connections have been available since
14889 0.1.2.5-alpha, and turning them off is not a good idea. This is a
14890 brute-force fix for 10849, where "TunnelDirConns 0" would break
14894 Changes in version 0.2.4.22 - 2014-05-16
14895 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
14896 alpha release series. These include blocking all authority signing
14897 keys that may have been affected by the OpenSSL "heartbleed" bug,
14898 choosing a far more secure set of TLS ciphersuites by default, closing
14899 a couple of memory leaks that could be used to run a target relay out
14900 of RAM, and several others.
14902 o Major features (security, backport from 0.2.5.4-alpha):
14903 - Block authority signing keys that were used on authorities
14904 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
14905 don't have any evidence that these keys _were_ compromised; we're
14906 doing this to be prudent.) Resolves ticket 11464.
14908 o Major bugfixes (security, OOM):
14909 - Fix a memory leak that could occur if a microdescriptor parse
14910 fails during the tokenizing step. This bug could enable a memory
14911 exhaustion attack by directory servers. Fixes bug 11649; bugfix
14914 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
14915 - The relay ciphersuite list is now generated automatically based on
14916 uniform criteria, and includes all OpenSSL ciphersuites with
14917 acceptable strength and forward secrecy. Previously, we had left
14918 some perfectly fine ciphersuites unsupported due to omission or
14919 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
14920 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
14921 - Relays now trust themselves to have a better view than clients of
14922 which TLS ciphersuites are better than others. (Thanks to bug
14923 11513, the relay list is now well-considered, whereas the client
14924 list has been chosen mainly for anti-fingerprinting purposes.)
14925 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
14926 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
14927 AES128. Resolves ticket 11528.
14928 - Clients now try to advertise the same list of ciphersuites as
14929 Firefox 28. This change enables selection of (fast) GCM
14930 ciphersuites, disables some strange old ciphers, and stops
14931 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
14932 Resolves ticket 11438.
14934 o Minor bugfixes (configuration, security):
14935 - When running a hidden service, do not allow TunneledDirConns 0:
14936 trying to set that option together with a hidden service would
14937 otherwise prevent the hidden service from running, and also make
14938 it publish its descriptors directly over HTTP. Fixes bug 10849;
14939 bugfix on 0.2.1.1-alpha.
14941 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
14942 - Avoid sending a garbage value to the controller when a circuit is
14943 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
14945 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
14946 - Stop leaking memory when we successfully resolve a PTR record.
14947 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
14949 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
14950 - Avoid 60-second delays in the bootstrapping process when Tor is
14951 launching for a second time while using bridges. Fixes bug 9229;
14952 bugfix on 0.2.0.3-alpha.
14954 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
14955 - Give the correct URL in the warning message when trying to run a
14956 relay on an ancient version of Windows. Fixes bug 9393.
14958 o Minor bugfixes (compilation):
14959 - Fix a compilation error when compiling with --disable-curve25519.
14960 Fixes bug 9700; bugfix on 0.2.4.17-rc.
14963 - Downgrade the warning severity for the the "md was still
14964 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
14965 for trying to diagnose this bug, and the current warning in
14966 earlier versions of tor achieves nothing useful. Addresses warning
14969 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
14970 - When we run out of usable circuit IDs on a channel, log only one
14971 warning for the whole channel, and describe how many circuits
14972 there were on the channel. Fixes part of ticket 11553.
14974 o Minor features (security, backport from 0.2.5.4-alpha):
14975 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
14976 leave the default at 8GBytes), to better support Raspberry Pi
14977 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
14979 o Documentation (backport from 0.2.5.4-alpha):
14980 - Correctly document that we search for a system torrc file before
14981 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
14985 Changes in version 0.2.5.4-alpha - 2014-04-25
14986 Tor 0.2.5.4-alpha includes several security and performance
14987 improvements for clients and relays, including blacklisting authority
14988 signing keys that were used while susceptible to the OpenSSL
14989 "heartbleed" bug, fixing two expensive functions on busy relays,
14990 improved TLS ciphersuite preference lists, support for run-time
14991 hardening on compilers that support AddressSanitizer, and more work on
14992 the Linux sandbox code.
14994 There are also several usability fixes for clients (especially clients
14995 that use bridges), two new TransPort protocols supported (one on
14996 OpenBSD, one on FreeBSD), and various other bugfixes.
14998 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
14999 have accumulated many known flaws; everyone should upgrade.
15001 o Major features (security):
15002 - If you don't specify MaxMemInQueues yourself, Tor now tries to
15003 pick a good value based on your total system memory. Previously,
15004 the default was always 8 GB. You can still override the default by
15005 setting MaxMemInQueues yourself. Resolves ticket 11396.
15006 - Block authority signing keys that were used on authorities
15007 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15008 don't have any evidence that these keys _were_ compromised; we're
15009 doing this to be prudent.) Resolves ticket 11464.
15011 o Major features (relay performance):
15012 - Speed up server-side lookups of rendezvous and introduction point
15013 circuits by using hashtables instead of linear searches. These
15014 functions previously accounted between 3 and 7% of CPU usage on
15015 some busy relays. Resolves ticket 9841.
15016 - Avoid wasting CPU when extending a circuit over a channel that is
15017 nearly out of circuit IDs. Previously, we would do a linear scan
15018 over possible circuit IDs before finding one or deciding that we
15019 had exhausted our possibilities. Now, we try at most 64 random
15020 circuit IDs before deciding that we probably won't succeed. Fixes
15021 a possible root cause of ticket 11553.
15023 o Major features (seccomp2 sandbox, Linux only):
15024 - The seccomp2 sandbox can now run a test network for multiple hours
15025 without crashing. The sandbox is still experimental, and more bugs
15026 will probably turn up. To try it, enable "Sandbox 1" on a Linux
15027 host. Resolves ticket 11351.
15028 - Strengthen sandbox code: the sandbox can now test the arguments
15029 for rename(), and blocks _sysctl() entirely. Resolves another part
15031 - When the sandbox blocks a system call, it now tries to log a stack
15032 trace before exiting. Resolves ticket 11465.
15034 o Major bugfixes (TLS cipher selection):
15035 - The relay ciphersuite list is now generated automatically based on
15036 uniform criteria, and includes all OpenSSL ciphersuites with
15037 acceptable strength and forward secrecy. Previously, we had left
15038 some perfectly fine ciphersuites unsupported due to omission or
15039 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15040 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15041 - Relays now trust themselves to have a better view than clients of
15042 which TLS ciphersuites are better than others. (Thanks to bug
15043 11513, the relay list is now well-considered, whereas the client
15044 list has been chosen mainly for anti-fingerprinting purposes.)
15045 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
15046 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
15047 AES128. Resolves ticket 11528.
15048 - Clients now try to advertise the same list of ciphersuites as
15049 Firefox 28. This change enables selection of (fast) GCM
15050 ciphersuites, disables some strange old ciphers, and stops
15051 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
15052 Resolves ticket 11438.
15054 o Major bugfixes (bridge client):
15055 - Avoid 60-second delays in the bootstrapping process when Tor is
15056 launching for a second time while using bridges. Fixes bug 9229;
15057 bugfix on 0.2.0.3-alpha.
15059 o Minor features (transparent proxy, *BSD):
15060 - Support FreeBSD's ipfw firewall interface for TransPort ports on
15061 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
15062 10267; patch from "yurivict".
15063 - Support OpenBSD's divert-to rules with the pf firewall for
15064 transparent proxy ports. To enable it, set "TransProxyType
15065 pf-divert". This allows Tor to run a TransPort transparent proxy
15066 port on OpenBSD 4.4 or later without root privileges. See the
15067 pf.conf(5) manual page for information on configuring pf to use
15068 divert-to rules. Closes ticket 10896; patch from Dana Koch.
15070 o Minor features (security):
15071 - New --enable-expensive-hardening option to enable security
15072 hardening options that consume nontrivial amounts of CPU and
15073 memory. Right now, this includes AddressSanitizer and UbSan, which
15074 are supported in newer versions of GCC and Clang. Closes ticket
15077 o Minor features (log verbosity):
15078 - Demote the message that we give when a flushing connection times
15079 out for too long from NOTICE to INFO. It was usually meaningless.
15080 Resolves ticket 5286.
15081 - Don't log so many notice-level bootstrapping messages at startup
15082 about downloading descriptors. Previously, we'd log a notice
15083 whenever we learned about more routers. Now, we only log a notice
15084 at every 5% of progress. Fixes bug 9963.
15085 - Warn less verbosely when receiving a malformed
15086 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
15087 - When we run out of usable circuit IDs on a channel, log only one
15088 warning for the whole channel, and describe how many circuits
15089 there were on the channel. Fixes part of ticket 11553.
15091 o Minor features (relay):
15092 - If a circuit timed out for at least 3 minutes, check if we have a
15093 new external IP address, and publish a new descriptor with the new
15094 IP address if it changed. Resolves ticket 2454.
15096 o Minor features (controller):
15097 - Make the entire exit policy available from the control port via
15098 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
15100 - Because of the fix for ticket 11396, the real limit for memory
15101 usage may no longer match the configured MaxMemInQueues value. The
15102 real limit is now exposed via GETINFO limits/max-mem-in-queues.
15104 o Minor features (bridge client):
15105 - Report a more useful failure message when we can't connect to a
15106 bridge because we don't have the right pluggable transport
15107 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
15109 o Minor features (diagnostic):
15110 - Add more log messages to diagnose bug 7164, which causes
15111 intermittent "microdesc_free() called but md was still referenced"
15112 warnings. We now include more information, to figure out why we
15113 might be cleaning a microdescriptor for being too old if it's
15114 still referenced by a live node_t object.
15116 o Minor bugfixes (client, DNSPort):
15117 - When using DNSPort, try to respond to AAAA requests with AAAA
15118 answers. Previously, we hadn't looked at the request type when
15119 deciding which answer type to prefer. Fixes bug 10468; bugfix on
15121 - When receiving a DNS query for an unsupported record type, reply
15122 with no answer rather than with a NOTIMPL error. This behavior
15123 isn't correct either, but it will break fewer client programs, we
15124 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
15127 o Minor bugfixes (exit relay):
15128 - Stop leaking memory when we successfully resolve a PTR record.
15129 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
15131 o Minor bugfixes (bridge client):
15132 - Stop accepting bridge lines containing hostnames. Doing so would
15133 cause clients to perform DNS requests on the hostnames, which was
15134 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
15135 - Avoid a 60-second delay in the bootstrapping process when a Tor
15136 client with pluggable transports re-reads its configuration at
15137 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
15139 o Minor bugfixes (client, logging during bootstrap):
15140 - Warn only once if we start logging in an unsafe way. Previously,
15141 we complain as many times as we had problems. Fixes bug 9870;
15142 bugfix on 0.2.5.1-alpha.
15143 - Only report the first fatal bootstrap error on a given OR
15144 connection. This stops us from telling the controller bogus error
15145 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
15146 - Be more helpful when trying to run sandboxed on Linux without
15147 libseccomp. Instead of saying "Sandbox is not implemented on this
15148 platform", we now explain that we need to be built with
15149 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
15150 - Avoid generating spurious warnings when starting with
15151 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
15154 o Minor bugfixes (closing OR connections):
15155 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
15156 check if it's an or_connection_t and correctly call
15157 connection_or_close_for_error() rather than
15158 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
15160 - When closing all connections on setting DisableNetwork to 1, use
15161 connection_or_close_normally() rather than closing OR connections
15162 out from under the channel layer. Fixes bug 11306; bugfix on
15165 o Minor bugfixes (controller):
15166 - Avoid sending a garbage value to the controller when a circuit is
15167 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
15169 o Minor bugfixes (tor-fw-helper):
15170 - Allow tor-fw-helper to build again by adding src/ext to its
15171 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
15173 o Minor bugfixes (bridges):
15174 - Avoid potential crashes or bad behavior when launching a
15175 server-side managed proxy with ORPort or ExtORPort temporarily
15176 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
15178 o Minor bugfixes (platform-specific):
15179 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
15180 bug 11426; bugfix on 0.2.5.3-alpha.
15181 - When dumping a malformed directory object to disk, save it in
15182 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
15184 - Don't report failures from make_socket_reuseable() on incoming
15185 sockets on OSX: this can happen when incoming connections close
15186 early. Fixes bug 10081.
15188 o Minor bugfixes (trivial memory leaks):
15189 - Fix a small memory leak when signing a directory object. Fixes bug
15190 11275; bugfix on 0.2.4.13-alpha.
15191 - Free placeholder entries in our circuit table at exit; fixes a
15192 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
15193 - Don't re-initialize a second set of OpenSSL mutexes when starting
15194 up. Previously, we'd make one set of mutexes, and then immediately
15195 replace them with another. Fixes bug 11726; bugfix on
15197 - Resolve some memory leaks found by coverity in the unit tests, on
15198 exit in tor-gencert, and on a failure to compute digests for our
15199 own keys when generating a v3 networkstatus vote. These leaks
15200 should never have affected anyone in practice.
15202 o Minor bugfixes (hidden service):
15203 - Only retry attempts to connect to a chosen rendezvous point 8
15204 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
15206 o Minor bugfixes (misc code correctness):
15207 - Fix various instances of undefined behavior in channeltls.c,
15208 tor_memmem(), and eventdns.c that would cause us to construct
15209 pointers to memory outside an allocated object. (These invalid
15210 pointers were not accessed, but C does not even allow them to
15211 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
15212 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
15213 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
15214 fix some miscellaneous errors in our tests and codebase. Fixes bug
15215 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
15216 - Always check return values for unlink, munmap, UnmapViewOfFile;
15217 check strftime return values more often. In some cases all we can
15218 do is report a warning, but this may help prevent deeper bugs from
15219 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
15221 - Fix numerous warnings from the clang "scan-build" static analyzer.
15222 Some of these are programming style issues; some of them are false
15223 positives that indicated awkward code; some are undefined behavior
15224 cases related to constructing (but not using) invalid pointers;
15225 some are assumptions about API behavior; some are (harmlessly)
15226 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
15227 correct; and one or two are genuine bugs that weren't reachable
15228 from the rest of the program. Fixes bug 8793; bugfixes on many,
15232 - Build the torify.1 manpage again. Previously, we were only trying
15233 to build it when also building tor-fw-helper. That's why we didn't
15234 notice that we'd broken the ability to build it. Fixes bug 11321;
15235 bugfix on 0.2.5.1-alpha.
15236 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
15237 11061; bugfix on 0.2.4.7-alpha.
15238 - Correctly document that we search for a system torrc file before
15239 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
15241 - Resolve warnings from Doxygen.
15243 o Code simplifications and refactoring:
15244 - Remove is_internal_IP() function. Resolves ticket 4645.
15245 - Remove unused function circuit_dump_by_chan from circuitlist.c.
15246 Closes issue 9107; patch from "marek".
15247 - Change our use of the ENUM_BF macro to avoid declarations that
15250 o Deprecated versions:
15251 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
15252 attention for some while. Directory authorities no longer accept
15253 descriptors from relays running any version of Tor prior to Tor
15254 0.2.3.16-alpha. Resolves ticket 11149.
15257 - New macros in test.h to simplify writing mock-functions for unit
15258 tests. Part of ticket 11507. Patch from Dana Koch.
15259 - Complete tests for the status.c module. Resolves ticket 11507.
15260 Patch from Dana Koch.
15263 - Remove all code for the long unused v1 directory protocol.
15264 Resolves ticket 11070.
15267 Changes in version 0.2.5.3-alpha - 2014-03-22
15268 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
15269 two new anti-DoS features for Tor relays, resolves a bug that kept
15270 SOCKS5 support for IPv6 from working, fixes several annoying usability
15271 issues for bridge users, and removes more old code for unused
15274 The Tor 0.2.5.x release series is now in patch-freeze: no feature
15275 patches not already written will be considered for inclusion in 0.2.5.x.
15277 o Major features (relay security, DoS-resistance):
15278 - When deciding whether we have run out of memory and we need to
15279 close circuits, also consider memory allocated in buffers for
15280 streams attached to each circuit.
15282 This change, which extends an anti-DoS feature introduced in
15283 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
15284 better resist more memory-based DoS attacks than before. Since the
15285 MaxMemInCellQueues option now applies to all queues, it is renamed
15286 to MaxMemInQueues. This feature fixes bug 10169.
15287 - Avoid hash-flooding denial-of-service attacks by using the secure
15288 SipHash-2-4 hash function for our hashtables. Without this
15289 feature, an attacker could degrade performance of a targeted
15290 client or server by flooding their data structures with a large
15291 number of entries to be stored at the same hash table position,
15292 thereby slowing down the Tor instance. With this feature, hash
15293 table positions are derived from a randomized cryptographic key,
15294 and an attacker cannot predict which entries will collide. Closes
15296 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
15297 the default at 8GBytes), to better support Raspberry Pi users. Fixes
15298 bug 9686; bugfix on 0.2.4.14-alpha.
15300 o Minor features (bridges, pluggable transports):
15301 - Bridges now write the SHA1 digest of their identity key
15302 fingerprint (that is, a hash of a hash of their public key) to
15303 notice-level logs, and to a new hashed-fingerprint file. This
15304 information will help bridge operators look up their bridge in
15305 Globe and similar tools. Resolves ticket 10884.
15306 - Improve the message that Tor displays when running as a bridge
15307 using pluggable transports without an Extended ORPort listener.
15308 Also, log the message in the log file too. Resolves ticket 11043.
15310 o Minor features (other):
15311 - Add a new option, PredictedPortsRelevanceTime, to control how long
15312 after having received a request to connect to a given port Tor
15313 will try to keep circuits ready in anticipation of future requests
15314 for that port. Patch from "unixninja92"; implements ticket 9176.
15315 - Generate a warning if any ports are listed in the SocksPolicy,
15316 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
15317 AuthDirBadExit options. (These options only support address
15318 ranges.) Fixes part of ticket 11108.
15319 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
15322 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
15323 - Build without warnings under clang 3.4. (We have some macros that
15324 define static functions only some of which will get used later in
15325 the module. Starting with clang 3.4, these give a warning unless the
15326 unused attribute is set on them.) Resolves ticket 10904.
15327 - Fix build warnings about missing "a2x" comment when building the
15328 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
15329 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
15331 o Minor bugfixes (client):
15332 - Improve the log message when we can't connect to a hidden service
15333 because all of the hidden service directory nodes hosting its
15334 descriptor are excluded. Improves on our fix for bug 10722, which
15335 was a bugfix on 0.2.0.10-alpha.
15336 - Raise a control port warning when we fail to connect to all of
15337 our bridges. Previously, we didn't inform the controller, and
15338 the bootstrap process would stall. Fixes bug 11069; bugfix on
15340 - Exit immediately when a process-owning controller exits.
15341 Previously, tor relays would wait for a little while after their
15342 controller exited, as if they had gotten an INT signal -- but this
15343 was problematic, since there was no feedback for the user. To do a
15344 clean shutdown, controllers should send an INT signal and give Tor
15345 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
15346 - Stop attempting to connect to bridges before our pluggable
15347 transports are configured (harmless but resulted in some erroneous
15348 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
15349 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
15350 generating incorrect SOCKS5 responses, and confusing client
15351 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
15353 o Minor bugfixes (relays and bridges):
15354 - Avoid crashing on a malformed resolv.conf file when running a
15355 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
15356 - Non-exit relays no longer launch mock DNS requests to check for
15357 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
15358 non-exit relays stopped servicing DNS requests. Fixes bug 965;
15359 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
15360 - Bridges now report complete directory request statistics. Related
15361 to bug 5824; bugfix on 0.2.2.1-alpha.
15362 - Bridges now never collect statistics that were designed for
15363 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
15364 - Stop giving annoying warning messages when we decide not to launch
15365 a pluggable transport proxy that we don't need (because there are
15366 no bridges configured to use it). Resolves ticket 5018; bugfix
15368 - Give the correct URL in the warning message when trying to run a
15369 relay on an ancient version of Windows. Fixes bug 9393.
15371 o Minor bugfixes (backtrace support):
15372 - Support automatic backtraces on more platforms by using the
15373 "-fasynchronous-unwind-tables" compiler option. This option is
15374 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
15375 is on by default and table generation is not. This doesn't yet
15376 add Windows support; only Linux, OSX, and some BSDs are affected.
15377 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
15378 - Avoid strange behavior if two threads hit failed assertions at the
15379 same time and both try to log backtraces at once. (Previously, if
15380 this had happened, both threads would have stored their intermediate
15381 results in the same buffer, and generated junk outputs.) Reported by
15382 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
15383 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
15384 0.2.5.2-alpha; patch from Nick Hopper.
15386 o Minor bugfixes (unit tests):
15387 - Fix a small bug in the unit tests that might have made the tests
15388 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
15389 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
15392 - Remove all remaining code related to version-0 hidden service
15393 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
15394 the rest of bug 10841.
15397 - Document in the manpage that "KBytes" may also be written as
15398 "kilobytes" or "KB", that "Kbits" may also be written as
15399 "kilobits", and so forth. Closes ticket 9222.
15400 - Document that the ClientOnly config option overrides ORPort.
15401 Our old explanation made ClientOnly sound as though it did
15402 nothing at all. Resolves bug 9059.
15403 - Explain that SocksPolicy, DirPolicy, and similar options don't
15404 take port arguments. Fixes the other part of ticket 11108.
15405 - Fix a comment about the rend_server_descriptor_t.protocols field
15406 to more accurately describe its range. Also, make that field
15407 unsigned, to more accurately reflect its usage. Fixes bug 9099;
15408 bugfix on 0.2.1.5-alpha.
15409 - Fix the manpage's description of HiddenServiceAuthorizeClient:
15410 the maximum client name length is 16, not 19. Fixes bug 11118;
15411 bugfix on 0.2.1.6-alpha.
15413 o Code simplifications and refactoring:
15414 - Get rid of router->address, since in all cases it was just the
15415 string representation of router->addr. Resolves ticket 5528.
15417 o Test infrastructure:
15418 - Update to the latest version of tinytest.
15419 - Improve the tinytest implementation of string operation tests so
15420 that comparisons with NULL strings no longer crash the tests; they
15421 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
15424 Changes in version 0.2.4.21 - 2014-02-28
15425 Tor 0.2.4.21 further improves security against potential adversaries who
15426 find breaking 1024-bit crypto doable, and backports several stability
15427 and robustness patches from the 0.2.5 branch.
15429 o Major features (client security):
15430 - When we choose a path for a 3-hop circuit, make sure it contains
15431 at least one relay that supports the NTor circuit extension
15432 handshake. Otherwise, there is a chance that we're building
15433 a circuit that's worth attacking by an adversary who finds
15434 breaking 1024-bit crypto doable, and that chance changes the game
15435 theory. Implements ticket 9777.
15438 - Do not treat streams that fail with reason
15439 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
15440 since it could also indicate an ENETUNREACH connection error. Fixes
15441 part of bug 10777; bugfix on 0.2.4.8-alpha.
15443 o Code simplification and refactoring:
15444 - Remove data structures which were introduced to implement the
15445 CellStatistics option: they are now redundant with the new timestamp
15446 field in the regular packed_cell_t data structure, which we did
15447 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
15450 - Always clear OpenSSL bignums before freeing them -- even bignums
15451 that don't contain secrets. Resolves ticket 10793. Patch by
15453 - Build without warnings under clang 3.4. (We have some macros that
15454 define static functions only some of which will get used later in
15455 the module. Starting with clang 3.4, these give a warning unless the
15456 unused attribute is set on them.) Resolves ticket 10904.
15457 - Update geoip and geoip6 files to the February 7 2014 Maxmind
15458 GeoLite2 Country database.
15461 - Set the listen() backlog limit to the largest actually supported
15462 on the system, not to the value in a header file. Fixes bug 9716;
15463 bugfix on every released Tor.
15464 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
15465 exit node as a NOROUTE error, not an INTERNAL error, since they
15466 can apparently happen when trying to connect to the wrong sort
15467 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
15468 - Fix build warnings about missing "a2x" comment when building the
15469 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
15470 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
15471 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
15472 not entirely remove it from the connection lists. Fixes bug 9602;
15473 bugfix on 0.2.4.4-alpha.
15474 - Fix a segmentation fault in our benchmark code when running with
15475 Fedora's OpenSSL package, or any other OpenSSL that provides
15476 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
15477 - Turn "circuit handshake stats since last time" log messages into a
15478 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
15480 o Documentation fixes:
15481 - Document that all but one DirPort entry must have the NoAdvertise
15482 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
15485 Changes in version 0.2.5.2-alpha - 2014-02-13
15486 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
15487 like the "poor random number generation" fix and the "building too many
15488 circuits" fix. It also further improves security against potential
15489 adversaries who find breaking 1024-bit crypto doable, and launches
15490 pluggable transports on demand (which gets us closer to integrating
15491 pluggable transport support by default -- not to be confused with Tor
15492 bundles enabling pluggable transports and bridges by default).
15494 o Major features (client security):
15495 - When we choose a path for a 3-hop circuit, make sure it contains
15496 at least one relay that supports the NTor circuit extension
15497 handshake. Otherwise, there is a chance that we're building
15498 a circuit that's worth attacking by an adversary who finds
15499 breaking 1024-bit crypto doable, and that chance changes the game
15500 theory. Implements ticket 9777.
15501 - Clients now look at the "usecreatefast" consensus parameter to
15502 decide whether to use CREATE_FAST or CREATE cells for the first hop
15503 of their circuit. This approach can improve security on connections
15504 where Tor's circuit handshake is stronger than the available TLS
15505 connection security levels, but the tradeoff is more computational
15506 load on guard relays. Implements proposal 221. Resolves ticket 9386.
15508 o Major features (bridges):
15509 - Don't launch pluggable transport proxies if we don't have any
15510 bridges configured that would use them. Now we can list many
15511 pluggable transports, and Tor will dynamically start one when it
15512 hears a bridge address that needs it. Resolves ticket 5018.
15513 - The bridge directory authority now assigns status flags (Stable,
15514 Guard, etc) to bridges based on thresholds calculated over all
15515 Running bridges. Now bridgedb can finally make use of its features
15516 to e.g. include at least one Stable bridge in its answers. Fixes
15519 o Major features (other):
15520 - Extend ORCONN controller event to include an "ID" parameter,
15521 and add four new controller event types CONN_BW, CIRC_BW,
15522 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
15523 The new events are emitted in private Tor networks only, with the
15524 goal of being able to better track performance and load during
15525 full-network simulations. Implements proposal 218 and ticket 7359.
15526 - On some platforms (currently: recent OSX versions, glibc-based
15527 platforms that support the ELF format, and a few other
15528 Unix-like operating systems), Tor can now dump stack traces
15529 when a crash occurs or an assertion fails. By default, traces
15530 are dumped to stderr (if possible) and to any logs that are
15531 reporting errors. Implements ticket 9299.
15534 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
15535 not entirely remove it from the connection lists. Fixes bug 9602;
15536 bugfix on 0.2.4.4-alpha.
15537 - Do not treat streams that fail with reason
15538 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
15539 since it could also indicate an ENETUNREACH connection error. Fixes
15540 part of bug 10777; bugfix on 0.2.4.8-alpha.
15542 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
15543 - Do not allow OpenSSL engines to replace the PRNG, even when
15544 HardwareAccel is set. The only default builtin PRNG engine uses
15545 the Intel RDRAND instruction to replace the entire PRNG, and
15546 ignores all attempts to seed it with more entropy. That's
15547 cryptographically stupid: the right response to a new alleged
15548 entropy source is never to discard all previously used entropy
15549 sources. Fixes bug 10402; works around behavior introduced in
15550 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
15552 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
15553 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
15554 - Avoid launching spurious extra circuits when a stream is pending.
15555 This fixes a bug where any circuit that _wasn't_ unusable for new
15556 streams would be treated as if it were, causing extra circuits to
15557 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
15559 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15560 - No longer stop reading or writing on cpuworker connections when
15561 our rate limiting buckets go empty. Now we should handle circuit
15562 handshake requests more promptly. Resolves bug 9731.
15563 - Stop trying to bootstrap all our directory information from
15564 only our first guard. Discovered while fixing bug 9946; bugfix
15567 o Minor features (bridges, pluggable transports):
15568 - Add threshold cutoffs to the networkstatus document created by
15569 the Bridge Authority. Fixes bug 1117.
15570 - On Windows, spawn background processes using the CREATE_NO_WINDOW
15571 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
15572 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
15573 Vidalia set this option for us.) Implements ticket 10297.
15575 o Minor features (security):
15576 - Always clear OpenSSL bignums before freeing them -- even bignums
15577 that don't contain secrets. Resolves ticket 10793. Patch by
15580 o Minor features (config options and command line):
15581 - Add an --allow-missing-torrc commandline option that tells Tor to
15582 run even if the configuration file specified by -f is not available.
15583 Implements ticket 10060.
15584 - Add support for the TPROXY transparent proxying facility on Linux.
15585 See documentation for the new TransProxyType option for more
15586 details. Implementation by "thomo". Closes ticket 10582.
15588 o Minor features (controller):
15589 - Add a new "HS_DESC" controller event that reports activities
15590 related to hidden service descriptors. Resolves ticket 8510.
15591 - New "DROPGUARDS" controller command to forget all current entry
15592 guards. Not recommended for ordinary use, since replacing guards
15593 too frequently makes several attacks easier. Resolves ticket 9934;
15596 o Minor features (build):
15597 - Assume that a user using ./configure --host wants to cross-compile,
15598 and give an error if we cannot find a properly named
15599 tool-chain. Add a --disable-tool-name-check option to proceed
15600 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
15601 - If we run ./configure and the compiler recognizes -fstack-protector
15602 but the linker rejects it, warn the user about a potentially missing
15603 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
15605 o Minor features (testing):
15606 - If Python is installed, "make check" now runs extra tests beyond
15607 the unit test scripts.
15608 - When bootstrapping a test network, sometimes very few relays get
15609 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
15610 specify a set of relays which should be voted Guard regardless of
15611 their uptime or bandwidth. Addresses ticket 9206.
15613 o Minor features (log messages):
15614 - When ServerTransportPlugin is set on a bridge, Tor can write more
15615 useful statistics about bridge use in its extrainfo descriptors,
15616 but only if the Extended ORPort ("ExtORPort") is set too. Add a
15617 log message to inform the user in this case. Resolves ticket 9651.
15618 - When receiving a new controller connection, log the origin address.
15619 Resolves ticket 9698; patch from "sigpipe".
15620 - When logging OpenSSL engine status at startup, log the status of
15621 more engines. Fixes ticket 10043; patch from Joshua Datko.
15622 - Turn "circuit handshake stats since last time" log messages into a
15623 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
15625 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15626 - Improve the circuit queue out-of-memory handler. Previously, when
15627 we ran low on memory, we'd close whichever circuits had the most
15628 queued cells. Now, we close those that have the *oldest* queued
15629 cells, on the theory that those are most responsible for us
15630 running low on memory. Based on analysis from a forthcoming paper
15631 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
15632 - Generate bootstrapping status update events correctly when fetching
15633 microdescriptors. Fixes bug 9927.
15634 - Update to the October 2 2013 Maxmind GeoLite Country database.
15636 o Minor bugfixes (clients):
15637 - When closing a channel that has already been open, do not close
15638 pending circuits that were waiting to connect to the same relay.
15639 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
15642 o Minor bugfixes (relays):
15643 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
15644 exit node as a NOROUTE error, not an INTERNAL error, since they
15645 can apparently happen when trying to connect to the wrong sort
15646 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
15648 o Minor bugfixes (bridges):
15649 - Fix a bug where the first connection works to a bridge that uses a
15650 pluggable transport with client-side parameters, but we don't send
15651 the client-side parameters on subsequent connections. (We don't
15652 use any pluggable transports with client-side parameters yet,
15653 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
15654 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
15656 o Minor bugfixes (node selection):
15657 - If ExcludeNodes is set, consider non-excluded hidden service
15658 directory servers before excluded ones. Do not consider excluded
15659 hidden service directory servers at all if StrictNodes is
15660 set. (Previously, we would sometimes decide to connect to those
15661 servers, and then realize before we initiated a connection that
15662 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
15663 Reported by "mr-4".
15664 - If we set the ExitNodes option but it doesn't include any nodes
15665 that have the Exit flag, we would choose not to bootstrap. Now we
15666 bootstrap so long as ExitNodes includes nodes which can exit to
15667 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
15669 o Minor bugfixes (controller and command-line):
15670 - If changing a config option via "setconf" fails in a recoverable
15671 way, we used to nonetheless write our new control ports to the
15672 file described by the "ControlPortWriteToFile" option. Now we only
15673 write out that file if we successfully switch to the new config
15674 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
15675 - When a command-line option such as --version or --help that
15676 ordinarily implies --hush appears on the command line along with
15677 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
15678 only if it appeared later on the command line. Fixes bug 9578;
15679 bugfix on 0.2.5.1-alpha.
15681 o Minor bugfixes (code correctness):
15682 - Previously we used two temporary files when writing descriptors to
15683 disk; now we only use one. Fixes bug 1376.
15684 - Remove an erroneous (but impossible and thus harmless) pointer
15685 comparison that would have allowed compilers to skip a bounds
15686 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
15687 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
15688 - Fix an always-true assertion in pluggable transports code so it
15689 actually checks what it was trying to check. Fixes bug 10046;
15690 bugfix on 0.2.3.9-alpha. Found by "dcb".
15692 o Minor bugfixes (protocol correctness):
15693 - When receiving a VERSIONS cell with an odd number of bytes, close
15694 the connection immediately since the cell is malformed. Fixes bug
15695 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
15698 o Minor bugfixes (build):
15699 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
15700 turned off (that is, without support for v2 link handshakes). Fixes
15701 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
15702 - Fix compilation warnings and startup issues when running with
15703 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
15705 - Fix compilation on Solaris 9, which didn't like us having an
15706 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
15708 o Minor bugfixes (testing):
15709 - Fix a segmentation fault in our benchmark code when running with
15710 Fedora's OpenSSL package, or any other OpenSSL that provides
15711 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
15713 o Minor bugfixes (log messages):
15714 - Fix a bug where clients using bridges would report themselves
15715 as 50% bootstrapped even without a live consensus document.
15716 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
15717 - Suppress a warning where, if there's only one directory authority
15718 in the network, we would complain that votes and signatures cannot
15719 be uploaded to other directory authorities. Fixes bug 10842;
15720 bugfix on 0.2.2.26-beta.
15721 - Report bootstrapping progress correctly when we're downloading
15722 microdescriptors. We had updated our "do we have enough microdescs
15723 to begin building circuits?" logic most recently in 0.2.4.10-alpha
15724 (see bug 5956), but we left the bootstrap status event logic at
15725 "how far through getting 1/4 of them are we?" Fixes bug 9958;
15726 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
15728 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
15729 - Avoid a crash bug when starting with a corrupted microdescriptor
15730 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
15731 - If we fail to dump a previously cached microdescriptor to disk, avoid
15732 freeing duplicate data later on. Fixes bug 10423; bugfix on
15733 0.2.4.13-alpha. Spotted by "bobnomnom".
15735 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15736 - Correctly log long IPv6 exit policies, instead of truncating them
15737 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
15738 - Our default TLS ecdhe groups were backwards: we meant to be using
15739 P224 for relays (for performance win) and P256 for bridges (since
15740 it is more common in the wild). Instead we had it backwards. After
15741 reconsideration, we decided that the default should be P256 on all
15742 hosts, since its security is probably better, and since P224 is
15743 reportedly used quite little in the wild. Found by "skruffy" on
15744 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
15745 - Free directory authority certificate download statuses on exit
15746 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
15748 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15749 - If the guard we choose first doesn't answer, we would try the
15750 second guard, but once we connected to the second guard we would
15751 abandon it and retry the first one, slowing down bootstrapping.
15752 The fix is to treat all our initially chosen guards as acceptable
15753 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
15754 - Fix an assertion failure that would occur when disabling the
15755 ORPort setting on a running Tor process while accounting was
15756 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
15757 - When examining the list of network interfaces to find our address,
15758 do not consider non-running or disabled network interfaces. Fixes
15759 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
15760 - Avoid an off-by-one error when checking buffer boundaries when
15761 formatting the exit status of a pluggable transport helper.
15762 This is probably not an exploitable bug, but better safe than
15763 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
15766 o Removed code and features:
15767 - Clients now reject any directory authority certificates lacking
15768 a dir-key-crosscert element. These have been included since
15769 0.2.1.9-alpha, so there's no real reason for them to be optional
15770 any longer. Completes proposal 157. Resolves ticket 10162.
15771 - Remove all code that existed to support the v2 directory system,
15772 since there are no longer any v2 directory authorities. Resolves
15774 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
15775 options, which were used for designating authorities as "Hidden
15776 service authorities". There has been no use of hidden service
15777 authorities since 0.2.2.1-alpha, when we stopped uploading or
15778 downloading v0 hidden service descriptors. Fixes bug 10881; also
15779 part of a fix for bug 10841.
15781 o Code simplification and refactoring:
15782 - Remove some old fallback code designed to keep Tor clients working
15783 in a network with only two working relays. Elsewhere in the code we
15784 have long since stopped supporting such networks, so there wasn't
15785 much point in keeping it around. Addresses ticket 9926.
15786 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
15787 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
15788 - Remove data structures which were introduced to implement the
15789 CellStatistics option: they are now redundant with the addition
15790 of a timestamp to the regular packed_cell_t data structure, which
15791 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
15794 o Documentation (man page) fixes:
15795 - Update manpage to describe some of the files you can expect to
15796 find in Tor's DataDirectory. Addresses ticket 9839.
15797 - Document that all but one DirPort entry must have the NoAdvertise
15798 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
15800 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
15801 - Clarify the usage and risks of setting the ContactInfo torrc line
15802 for your relay or bridge. Resolves ticket 9854.
15803 - Add anchors to the manpage so we can link to the html version of
15804 the documentation for specific options. Resolves ticket 9866.
15805 - Replace remaining references to DirServer in man page and
15806 log entries. Resolves ticket 10124.
15809 - Make the "tor-gencert" tool used by directory authority operators
15810 create 2048-bit signing keys by default (rather than 1024-bit, since
15811 1024-bit is uncomfortably small these days). Addresses ticket 10324.
15814 Changes in version 0.2.4.20 - 2013-12-22
15815 Tor 0.2.4.20 fixes potentially poor random number generation for users
15816 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
15817 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
15818 and 4) have no state file in their DataDirectory (as would happen on
15819 first start). Users who generated relay or hidden service identity
15820 keys in such a situation should discard them and generate new ones.
15822 This release also fixes a logic error that caused Tor clients to build
15823 many more preemptive circuits than they actually need.
15826 - Do not allow OpenSSL engines to replace the PRNG, even when
15827 HardwareAccel is set. The only default builtin PRNG engine uses
15828 the Intel RDRAND instruction to replace the entire PRNG, and
15829 ignores all attempts to seed it with more entropy. That's
15830 cryptographically stupid: the right response to a new alleged
15831 entropy source is never to discard all previously used entropy
15832 sources. Fixes bug 10402; works around behavior introduced in
15833 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
15835 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
15836 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
15837 - Avoid launching spurious extra circuits when a stream is pending.
15838 This fixes a bug where any circuit that _wasn't_ unusable for new
15839 streams would be treated as if it were, causing extra circuits to
15840 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
15843 - Avoid a crash bug when starting with a corrupted microdescriptor
15844 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
15845 - If we fail to dump a previously cached microdescriptor to disk, avoid
15846 freeing duplicate data later on. Fixes bug 10423; bugfix on
15847 0.2.4.13-alpha. Spotted by "bobnomnom".
15850 Changes in version 0.2.4.19 - 2013-12-11
15851 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
15852 (1986-2013). Aaron worked on diverse projects including helping to guide
15853 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
15854 transparency to the U.S government's PACER documents, and contributing
15855 design and development for Tor and Tor2Web. Aaron was one of the latest
15856 martyrs in our collective fight for civil liberties and human rights,
15857 and his death is all the more painful because he was one of us.
15859 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
15860 a new circuit handshake and link encryption that use ECC to provide
15861 better security and efficiency; makes relays better manage circuit
15862 creation requests; uses "directory guards" to reduce client enumeration
15863 risks; makes bridges collect and report statistics about the pluggable
15864 transports they support; cleans up and improves our geoip database;
15865 gets much closer to IPv6 support for clients, bridges, and relays; makes
15866 directory authorities use measured bandwidths rather than advertised
15867 ones when computing flags and thresholds; disables client-side DNS
15868 caching to reduce tracking risks; and fixes a big bug in bridge
15869 reachability testing. This release introduces two new design
15870 abstractions in the code: a new "channel" abstraction between circuits
15871 and or_connections to allow for implementing alternate relay-to-relay
15872 transports, and a new "circuitmux" abstraction storing the queue of
15873 circuits for a channel. The release also includes many stability,
15874 security, and privacy fixes.
15877 Changes in version 0.2.4.18-rc - 2013-11-16
15878 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
15879 series. It takes a variety of fixes from the 0.2.5.x branch to improve
15880 stability, performance, and better handling of edge cases.
15883 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
15884 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
15885 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
15886 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
15887 them to solve bug 6033.)
15890 - No longer stop reading or writing on cpuworker connections when
15891 our rate limiting buckets go empty. Now we should handle circuit
15892 handshake requests more promptly. Resolves bug 9731.
15893 - If we are unable to save a microdescriptor to the journal, do not
15894 drop it from memory and then reattempt downloading it. Fixes bug
15895 9645; bugfix on 0.2.2.6-alpha.
15896 - Stop trying to bootstrap all our directory information from
15897 only our first guard. Discovered while fixing bug 9946; bugfix
15899 - The new channel code sometimes lost track of in-progress circuits,
15900 causing long-running clients to stop building new circuits. The
15901 fix is to always call circuit_n_chan_done(chan, 0) from
15902 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
15904 o Minor bugfixes (on 0.2.4.x):
15905 - Correctly log long IPv6 exit policies, instead of truncating them
15906 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
15907 - Our default TLS ecdhe groups were backwards: we meant to be using
15908 P224 for relays (for performance win) and P256 for bridges (since
15909 it is more common in the wild). Instead we had it backwards. After
15910 reconsideration, we decided that the default should be P256 on all
15911 hosts, since its security is probably better, and since P224 is
15912 reportedly used quite little in the wild. Found by "skruffy" on
15913 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
15914 - Free directory authority certificate download statuses on exit
15915 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
15917 o Minor bugfixes (on 0.2.3.x and earlier):
15918 - If the guard we choose first doesn't answer, we would try the
15919 second guard, but once we connected to the second guard we would
15920 abandon it and retry the first one, slowing down bootstrapping.
15921 The fix is to treat all our initially chosen guards as acceptable
15922 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
15923 - Fix an assertion failure that would occur when disabling the
15924 ORPort setting on a running Tor process while accounting was
15925 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
15926 - When examining the list of network interfaces to find our address,
15927 do not consider non-running or disabled network interfaces. Fixes
15928 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
15929 - Avoid an off-by-one error when checking buffer boundaries when
15930 formatting the exit status of a pluggable transport helper.
15931 This is probably not an exploitable bug, but better safe than
15932 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
15935 o Minor features (protecting client timestamps):
15936 - Clients no longer send timestamps in their NETINFO cells. These were
15937 not used for anything, and they provided one small way for clients
15938 to be distinguished from each other as they moved from network to
15939 network or behind NAT. Implements part of proposal 222.
15940 - Clients now round timestamps in INTRODUCE cells down to the nearest
15941 10 minutes. If a new Support022HiddenServices option is set to 0, or
15942 if it's set to "auto" and the feature is disabled in the consensus,
15943 the timestamp is sent as 0 instead. Implements part of proposal 222.
15944 - Stop sending timestamps in AUTHENTICATE cells. This is not such
15945 a big deal from a security point of view, but it achieves no actual
15946 good purpose, and isn't needed. Implements part of proposal 222.
15947 - Reduce down accuracy of timestamps in hidden service descriptors.
15948 Implements part of proposal 222.
15950 o Minor features (other):
15951 - Improve the circuit queue out-of-memory handler. Previously, when
15952 we ran low on memory, we'd close whichever circuits had the most
15953 queued cells. Now, we close those that have the *oldest* queued
15954 cells, on the theory that those are most responsible for us
15955 running low on memory. Based on analysis from a forthcoming paper
15956 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
15957 - Generate bootstrapping status update events correctly when fetching
15958 microdescriptors. Fixes bug 9927.
15959 - Update to the October 2 2013 Maxmind GeoLite Country database.
15961 o Documentation fixes:
15962 - Clarify the usage and risks of setting the ContactInfo torrc line
15963 for your relay or bridge. Resolves ticket 9854.
15964 - Add anchors to the manpage so we can link to the html version of
15965 the documentation for specific options. Resolves ticket 9866.
15966 - Replace remaining references to DirServer in man page and
15967 log entries. Resolves ticket 10124.
15970 Changes in version 0.2.5.1-alpha - 2013-10-02
15971 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
15972 on Linux, allows bridges that offer pluggable transports to report usage
15973 statistics, fixes many issues to make testing easier, and provides
15974 a pile of minor features and bugfixes that have been waiting for a
15975 release of the new branch.
15977 This is the first alpha release in a new series, so expect there to
15978 be bugs. Users who would rather test out a more stable branch should
15979 stay with 0.2.4.x for now.
15981 o Major features (security):
15982 - Use the seccomp2 syscall filtering facility on Linux to limit
15983 which system calls Tor can invoke. This is an experimental,
15984 Linux-only feature to provide defense-in-depth against unknown
15985 attacks. To try turning it on, set "Sandbox 1" in your torrc
15986 file. Please be ready to report bugs. We hope to add support
15987 for better sandboxing in the future, including more fine-grained
15988 filters, better division of responsibility, and support for more
15989 platforms. This work has been done by Cristian-Matei Toader for
15990 Google Summer of Code.
15991 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
15992 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
15993 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
15994 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
15995 them to solve bug 6033.)
15997 o Major features (other):
15998 - Add support for passing arguments to managed pluggable transport
15999 proxies. Implements ticket 3594.
16000 - Bridges now track GeoIP information and the number of their users
16001 even when pluggable transports are in use, and report usage
16002 statistics in their extra-info descriptors. Resolves tickets 4773
16004 - Make testing Tor networks bootstrap better: lower directory fetch
16005 retry schedules and maximum interval without directory requests,
16006 and raise maximum download tries. Implements ticket 6752.
16007 - Add make target 'test-network' to run tests on a Chutney network.
16008 Implements ticket 8530.
16009 - The ntor handshake is now on-by-default, no matter what the
16010 directory authorities recommend. Implements ticket 8561.
16013 - Instead of writing destroy cells directly to outgoing connection
16014 buffers, queue them and intersperse them with other outgoing cells.
16015 This can prevent a set of resource starvation conditions where too
16016 many pending destroy cells prevent data cells from actually getting
16017 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
16018 bugfix on 0.2.0.1-alpha.
16019 - If we are unable to save a microdescriptor to the journal, do not
16020 drop it from memory and then reattempt downloading it. Fixes bug
16021 9645; bugfix on 0.2.2.6-alpha.
16022 - The new channel code sometimes lost track of in-progress circuits,
16023 causing long-running clients to stop building new circuits. The
16024 fix is to always call circuit_n_chan_done(chan, 0) from
16025 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16028 - Tor now builds each source file in two modes: a mode that avoids
16029 exposing identifiers needlessly, and another mode that exposes
16030 more identifiers for testing. This lets the compiler do better at
16031 optimizing the production code, while enabling us to take more
16032 radical measures to let the unit tests test things.
16033 - The production builds no longer include functions used only in
16034 the unit tests; all functions exposed from a module only for
16035 unit-testing are now static in production builds.
16036 - Add an --enable-coverage configuration option to make the unit
16037 tests (and a new src/or/tor-cov target) to build with gcov test
16041 - We now have rudimentary function mocking support that our unit
16042 tests can use to test functions in isolation. Function mocking
16043 lets the tests temporarily replace a function's dependencies with
16044 stub functions, so that the tests can check the function without
16045 invoking the other functions it calls.
16046 - Add more unit tests for the <circid,channel>->circuit map, and
16047 the destroy-cell-tracking code to fix bug 7912.
16048 - Unit tests for failing cases of the TAP onion handshake.
16049 - More unit tests for address-manipulation functions.
16051 o Minor features (protecting client timestamps):
16052 - Clients no longer send timestamps in their NETINFO cells. These were
16053 not used for anything, and they provided one small way for clients
16054 to be distinguished from each other as they moved from network to
16055 network or behind NAT. Implements part of proposal 222.
16056 - Clients now round timestamps in INTRODUCE cells down to the nearest
16057 10 minutes. If a new Support022HiddenServices option is set to 0, or
16058 if it's set to "auto" and the feature is disabled in the consensus,
16059 the timestamp is sent as 0 instead. Implements part of proposal 222.
16060 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16061 a big deal from a security point of view, but it achieves no actual
16062 good purpose, and isn't needed. Implements part of proposal 222.
16063 - Reduce down accuracy of timestamps in hidden service descriptors.
16064 Implements part of proposal 222.
16066 o Minor features (config options):
16067 - Config (torrc) lines now handle fingerprints which are missing
16068 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
16069 - Support a --dump-config option to print some or all of the
16070 configured options. Mainly useful for debugging the command-line
16071 option parsing code. Helps resolve ticket 4647.
16072 - Raise awareness of safer logging: notify user of potentially
16073 unsafe config options, like logging more verbosely than severity
16074 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
16075 - Add a new configuration option TestingV3AuthVotingStartOffset
16076 that bootstraps a network faster by changing the timing for
16077 consensus votes. Addresses ticket 8532.
16078 - Add a new torrc option "ServerTransportOptions" that allows
16079 bridge operators to pass configuration parameters to their
16080 pluggable transports. Resolves ticket 8929.
16081 - The config (torrc) file now accepts bandwidth and space limits in
16082 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
16083 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
16086 o Minor features (build):
16087 - Add support for `--library-versions` flag. Implements ticket 6384.
16088 - Return the "unexpected sendme" warnings to a warn severity, but make
16089 them rate limited, to help diagnose ticket 8093.
16090 - Detect a missing asciidoc, and warn the user about it, during
16091 configure rather than at build time. Fixes issue 6506. Patch from
16094 o Minor features (other):
16095 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
16096 sockets in a single system call. Implements ticket 5129.
16097 - Log current accounting state (bytes sent and received + remaining
16098 time for the current accounting period) in the relay's heartbeat
16099 message. Implements ticket 5526; patch from Peter Retzlaff.
16100 - Implement the TRANSPORT_LAUNCHED control port event that
16101 notifies controllers about new launched pluggable
16102 transports. Resolves ticket 5609.
16103 - If we're using the pure-C 32-bit curve25519_donna implementation
16104 of curve25519, build it with the -fomit-frame-pointer option to
16105 make it go faster on register-starved hosts. This improves our
16106 handshake performance by about 6% on i386 hosts without nacl.
16107 Closes ticket 8109.
16108 - Update to the September 4 2013 Maxmind GeoLite Country database.
16111 - Set the listen() backlog limit to the largest actually supported
16112 on the system, not to the value in a header file. Fixes bug 9716;
16113 bugfix on every released Tor.
16114 - No longer accept malformed http headers when parsing urls from
16115 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
16116 bugfix on 0.0.6pre1.
16117 - In munge_extrainfo_into_routerinfo(), check the return value of
16118 memchr(). This would have been a serious issue if we ever passed
16119 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
16121 - On the chance that somebody manages to build Tor on a
16122 platform where time_t is unsigned, correct the way that
16123 microdesc_add_to_cache() handles negative time arguments.
16124 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
16125 - Reject relative control socket paths and emit a warning. Previously,
16126 single-component control socket paths would be rejected, but Tor
16127 would not log why it could not validate the config. Fixes bug 9258;
16128 bugfix on 0.2.3.16-alpha.
16130 o Minor bugfixes (command line):
16131 - Use a single command-line parser for parsing torrc options on the
16132 command line and for finding special command-line options to avoid
16133 inconsistent behavior for torrc option arguments that have the same
16134 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
16136 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
16137 9573; bugfix on 0.0.9pre5.
16139 o Minor fixes (build, auxiliary programs):
16140 - Stop preprocessing the "torify" script with autoconf, since
16141 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
16143 - The tor-fw-helper program now follows the standard convention and
16144 exits with status code "0" on success. Fixes bug 9030; bugfix on
16145 0.2.3.1-alpha. Patch by Arlo Breault.
16146 - Corrected ./configure advice for what openssl dev package you should
16147 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
16149 o Minor code improvements:
16150 - Remove constants and tests for PKCS1 padding; it's insecure and
16151 shouldn't be used for anything new. Fixes bug 8792; patch
16153 - Remove instances of strcpy() from the unit tests. They weren't
16154 hurting anything, since they were only in the unit tests, but it's
16155 embarrassing to have strcpy() in the code at all, and some analysis
16156 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
16157 0.2.3.8-alpha. Patch from Arlo Breault.
16159 o Removed features:
16160 - Remove migration code from when we renamed the "cached-routers"
16161 file to "cached-descriptors" back in 0.2.0.8-alpha. This
16162 incidentally resolves ticket 6502 by cleaning up the related code
16163 a bit. Patch from Akshay Hebbar.
16165 o Code simplification and refactoring:
16166 - Extract the common duplicated code for creating a subdirectory
16167 of the data directory and writing to a file in it. Fixes ticket
16168 4282; patch from Peter Retzlaff.
16169 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
16170 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
16171 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
16172 - Add a set of accessor functions for the circuit timeout data
16173 structure. Fixes ticket 6153; patch from "piet".
16174 - Clean up exit paths from connection_listener_new(). Closes ticket
16175 8789. Patch from Arlo Breault.
16176 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
16177 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
16178 - Use a doubly-linked list to implement the global circuit list.
16179 Resolves ticket 9108. Patch from Marek Majkowski.
16180 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
16183 Changes in version 0.2.4.17-rc - 2013-09-05
16184 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
16185 series. It adds an emergency step to help us tolerate the massive
16186 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
16187 circuit-level handshakes now effectively jump the queue compared to
16188 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
16189 big bug hindering bridge reachability tests.
16192 - Relays now process the new "NTor" circuit-level handshake requests
16193 with higher priority than the old "TAP" circuit-level handshake
16194 requests. We still process some TAP requests to not totally starve
16195 0.2.3 clients when NTor becomes popular. A new consensus parameter
16196 "NumNTorsPerTAP" lets us tune the balance later if we need to.
16197 Implements ticket 9574.
16200 - If the circuit build timeout logic is disabled (via the consensus,
16201 or because we are an authority), then don't build testing circuits.
16202 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
16203 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
16204 previously they did not, which prevented them from receiving
16205 successful connections from relays for self-test or bandwidth
16206 testing. Also, when a relay is extending a circuit to a bridge,
16207 it needs to send a NETINFO cell, even when the bridge hasn't sent
16208 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
16209 - If the time to download the next old-style networkstatus is in
16210 the future, do not decline to consider whether to download the
16211 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
16215 - Avoid double-closing the listener socket in our socketpair()
16216 replacement (used on Windows) in the case where the addresses on
16217 our opened sockets don't match what we expected. Fixes bug 9400;
16218 bugfix on 0.0.2pre7. Found by Coverity.
16220 o Minor fixes (config options):
16221 - Avoid overflows when the user sets MaxCircuitDirtiness to a
16222 ridiculously high value, by imposing a (ridiculously high) 30-day
16223 maximum on MaxCircuitDirtiness.
16224 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
16225 message is logged at notice, not at info.
16226 - Warn and fail if a server is configured not to advertise any
16227 ORPorts at all. (We need *something* to put in our descriptor,
16228 or we just won't work.)
16231 - Track how many "TAP" and "NTor" circuit handshake requests we get,
16232 and how many we complete, and log it every hour to help relay
16233 operators follow trends in network load. Addresses ticket 9658.
16234 - Update to the August 7 2013 Maxmind GeoLite Country database.
16237 Changes in version 0.2.4.16-rc - 2013-08-10
16238 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
16239 series. It fixes several crash bugs in the 0.2.4 branch.
16242 - Fix a bug in the voting algorithm that could yield incorrect results
16243 when a non-naming authority declared too many flags. Fixes bug 9200;
16244 bugfix on 0.2.0.3-alpha.
16245 - Fix an uninitialized read that could in some cases lead to a remote
16246 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
16247 Anybody running a hidden service on the experimental 0.2.4.x
16248 branch should upgrade. (This is, so far as we know, unrelated to
16250 - Avoid an assertion failure when processing DNS replies without the
16251 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
16252 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
16253 0.2.4.15-rc. Found by stem integration tests.
16256 - Fix an invalid memory read that occurred when a pluggable
16257 transport proxy failed its configuration protocol.
16258 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
16259 - When evaluating whether to use a connection that we haven't
16260 decided is canonical using a recent link protocol version,
16261 decide that it's canonical only if it used address _does_
16262 match the desired address. Fixes bug 9309; bugfix on
16263 0.2.4.4-alpha. Reported by skruffy.
16264 - Make the default behavior of NumDirectoryGuards be to track
16265 NumEntryGuards. Now a user who changes only NumEntryGuards will get
16266 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
16267 - Fix a spurious compilation warning with some older versions of
16268 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
16271 - Update to the July 3 2013 Maxmind GeoLite Country database.
16274 Changes in version 0.2.4.15-rc - 2013-07-01
16275 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
16276 series. It fixes a few smaller bugs, but generally appears stable.
16277 Please test it and let us know whether it is!
16280 - When receiving a new configuration file via the control port's
16281 LOADCONF command, do not treat the defaults file as absent.
16282 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
16285 - Issue a warning when running with the bufferevents backend enabled.
16286 It's still not stable, and people should know that they're likely
16287 to hit unexpected problems. Closes ticket 9147.
16290 Changes in version 0.2.4.14-alpha - 2013-06-18
16291 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
16292 present in 0.2.4.13-alpha.
16295 - When we have too much memory queued in circuits (according to a new
16296 MaxMemInCellQueues option), close the circuits consuming the most
16297 memory. This prevents us from running out of memory as a relay if
16298 circuits fill up faster than they can be drained. Fixes bug 9063;
16299 bugfix on the 54th commit of Tor. This bug is a further fix beyond
16300 bug 6252, whose fix was merged into 0.2.3.21-rc.
16302 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
16303 where we tried to solve this issue simply by imposing an upper limit
16304 on the number of queued cells for a single circuit. That approach
16305 proved to be problematic, since there are ways to provoke clients to
16306 send a number of cells in excess of any such reasonable limit. Fixes
16307 bug 9072; bugfix on 0.2.4.13-alpha.
16309 - Limit hidden service descriptors to at most ten introduction
16310 points, to slow one kind of guard enumeration. Fixes bug 9002;
16311 bugfix on 0.1.1.11-alpha.
16314 Changes in version 0.2.4.13-alpha - 2013-06-14
16315 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
16316 vulnerabilities, makes socks5 username/password circuit isolation
16317 actually actually work (this time for sure!), and cleans up a bunch
16318 of other issues in preparation for a release candidate.
16320 o Major bugfixes (robustness):
16321 - Close any circuit that has too many cells queued on it. Fixes
16322 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
16323 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
16324 - Prevent the get_freelists() function from running off the end of
16325 the list of freelists if it somehow gets an unrecognized
16326 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
16328 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
16329 when an exit connection with optimistic data succeeds immediately
16330 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
16332 - Fix a directory authority crash bug when building a consensus
16333 using an older consensus as its basis. Fixes bug 8833. Bugfix
16337 - Avoid a memory leak where we would leak a consensus body when we
16338 find that a consensus which we couldn't previously verify due to
16339 missing certificates is now verifiable. Fixes bug 8719; bugfix
16341 - We used to always request authority certificates by identity digest,
16342 meaning we'd get the newest one even when we wanted one with a
16343 different signing key. Then we would complain about being given
16344 a certificate we already had, and never get the one we really
16345 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
16346 resource to request the one we want. Fixes bug 5595; bugfix on
16348 - Follow the socks5 protocol when offering username/password
16349 authentication. The fix for bug 8117 exposed this bug, and it
16350 turns out real-world applications like Pidgin do care. Bugfix on
16351 0.2.3.2-alpha; fixes bug 8879.
16352 - Prevent failures on Windows Vista and later when rebuilding the
16353 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
16354 bugfix on 0.2.4.12-alpha.
16357 - Fix an impossible buffer overrun in the AES unit tests. Fixes
16358 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
16359 - If for some reason we fail to write a microdescriptor while
16360 rebuilding the cache, do not let the annotations from that
16361 microdescriptor linger in the cache file, and do not let the
16362 microdescriptor stay recorded as present in its old location.
16363 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
16364 - Fix a memory leak that would occur whenever a configuration
16365 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
16366 - Paste the description for PathBias parameters from the man
16367 page into or.h, so the code documents them too. Fixes bug 7982;
16368 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
16369 - Relays now treat a changed IPv6 ORPort as sufficient reason to
16370 publish an updated descriptor. Fixes bug 6026; bugfix on
16372 - When launching a resolve request on behalf of an AF_UNIX control
16373 socket, omit the address field of the new entry connection, used in
16374 subsequent controller events, rather than letting tor_dup_addr()
16375 set it to "<unknown address type>". Fixes bug 8639; bugfix on
16378 o Minor bugfixes (log messages):
16379 - Fix a scaling issue in the path bias accounting code that
16380 resulted in "Bug:" log messages from either
16381 pathbias_scale_close_rates() or pathbias_count_build_success().
16382 This represents a bugfix on a previous bugfix: the original fix
16383 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
16385 - Give a less useless error message when the user asks for an IPv4
16386 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
16390 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
16391 to tolerate bug 8093 for now.
16392 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
16393 in directory authority votes to describe whether they have enough
16394 measured bandwidths to ignore advertised (relay descriptor)
16395 bandwidth claims. Resolves ticket 8711.
16396 - Update to the June 5 2013 Maxmind GeoLite Country database.
16398 o Removed documentation:
16399 - Remove some of the older contents of doc/ as obsolete; move others
16400 to torspec.git. Fixes bug 8965.
16402 o Code simplification and refactoring:
16403 - Avoid using character buffers when constructing most directory
16404 objects: this approach was unwieldy and error-prone. Instead,
16405 build smartlists of strings, and concatenate them when done.
16408 Changes in version 0.2.4.12-alpha - 2013-04-18
16409 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
16410 process for lengthening the guard rotation period, makes directory
16411 authority opinions in the consensus a bit less gameable, makes socks5
16412 username/password circuit isolation actually work, and fixes a wide
16413 variety of other issues.
16416 - Raise the default time that a client keeps an entry guard from
16417 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
16418 2012 paper. (We would make it even longer, but we need better client
16419 load balancing first.) Also, make the guard lifetime controllable
16420 via a new GuardLifetime torrc option and a GuardLifetime consensus
16421 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
16422 - Directory authorities now prefer using measured bandwidths to
16423 advertised ones when computing flags and thresholds. Resolves
16425 - Directory authorities that have more than a threshold number
16426 of relays with measured bandwidths now treat relays with unmeasured
16427 bandwidths as having bandwidth 0. Resolves ticket 8435.
16429 o Major bugfixes (assert / resource use):
16430 - Avoid a bug where our response to TLS renegotiation under certain
16431 network conditions could lead to a busy-loop, with 100% CPU
16432 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
16433 - Avoid an assertion when we discover that we'd like to write a cell
16434 onto a closing connection: just discard the cell. Fixes another
16435 case of bug 7350; bugfix on 0.2.4.4-alpha.
16437 o Major bugfixes (client-side privacy):
16438 - When we mark a circuit as unusable for new circuits, have it
16439 continue to be unusable for new circuits even if MaxCircuitDirtiness
16440 is increased too much at the wrong time, or the system clock jumps
16441 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
16442 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
16443 which have resolved to internal addresses") is set, apply that
16444 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
16445 - When an exit relay rejects a stream with reason "exit policy", but
16446 we only know an exit policy summary (e.g. from the microdesc
16447 consensus) for it, do not mark the relay as useless for all exiting.
16448 Instead, mark just the circuit as unsuitable for that particular
16449 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
16450 - Allow applications to get proper stream isolation with
16451 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
16452 username/password authentication also offer "no authentication". Tor
16453 had previously preferred "no authentication", so the applications
16454 never actually sent Tor their auth details. Now Tor selects
16455 username/password authentication if it's offered. You can disable
16456 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
16457 bug 8117; bugfix on 0.2.3.3-alpha.
16459 o Major bugfixes (other):
16460 - When unable to find any working directory nodes to use as a
16461 directory guard, give up rather than adding the same non-working
16462 nodes to the directory guard list over and over. Fixes bug 8231;
16463 bugfix on 0.2.4.8-alpha.
16466 - Reject as invalid most directory objects containing a NUL.
16467 Belt-and-suspender fix for bug 8037.
16468 - In our testsuite, create temporary directories with a bit more
16469 entropy in their name to make name collisions less likely. Fixes
16471 - Add CACHED keyword to ADDRMAP events in the control protocol
16472 to indicate whether a DNS result will be cached or not. Resolves
16474 - Update to the April 3 2013 Maxmind GeoLite Country database.
16476 o Minor features (build):
16477 - Detect and reject attempts to build Tor with threading support
16478 when OpenSSL has been compiled without threading support.
16480 - Clarify that when autoconf is checking for nacl, it is checking
16481 specifically for nacl with a fast curve25519 implementation.
16483 - Warn if building on a platform with an unsigned time_t: there
16484 are too many places where Tor currently assumes that time_t can
16485 hold negative values. We'd like to fix them all, but probably
16488 o Minor bugfixes (build):
16489 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
16490 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
16491 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
16492 - Add the old src/or/micro-revision.i filename to CLEANFILES.
16493 On the off chance that somebody has one, it will go away as soon
16494 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
16495 - Build Tor correctly on 32-bit platforms where the compiler can build
16496 but not run code using the "uint128_t" construction. Fixes bug 8587;
16497 bugfix on 0.2.4.8-alpha.
16498 - Fix compilation warning with some versions of clang that would
16499 prefer the -Wswitch-enum compiler flag to warn about switch
16500 statements with missing enum values, even if those switch
16501 statements have a "default:" statement. Fixes bug 8598; bugfix
16504 o Minor bugfixes (protocol):
16505 - Fix the handling of a TRUNCATE cell when it arrives while the
16506 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
16507 - Fix a misframing issue when reading the version numbers in a
16508 VERSIONS cell. Previously we would recognize [00 01 00 02] as
16509 'version 1, version 2, and version 0x100', when it should have
16510 only included versions 1 and 2. Fixes bug 8059; bugfix on
16511 0.2.0.10-alpha. Reported pseudonymously.
16512 - Make the format and order of STREAM events for DNS lookups
16513 consistent among the various ways to launch DNS lookups. Fixes
16514 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
16515 - Correct our check for which versions of Tor support the EXTEND2
16516 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
16517 later, when support was really added in version 0.2.4.8-alpha.
16518 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
16520 o Minor bugfixes (other):
16521 - Correctly store microdescriptors and extrainfo descriptors with
16522 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
16523 Bug reported by "cypherpunks".
16524 - Increase the width of the field used to remember a connection's
16525 link protocol version to two bytes. Harmless for now, since the
16526 only currently recognized versions are one byte long. Reported
16527 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
16528 - If the state file's path bias counts are invalid (presumably from a
16529 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
16530 additional checks and log messages to the scaling of Path Bias
16531 counts, in case there still are remaining issues with scaling.
16532 Should help resolve bug 8235.
16533 - Eliminate several instances where we use "Nickname=ID" to refer to
16534 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
16535 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
16536 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
16538 o Minor bugfixes (syscalls):
16539 - Always check the return values of functions fcntl() and
16540 setsockopt(). We don't believe these are ever actually failing in
16541 practice, but better safe than sorry. Also, checking these return
16542 values should please analysis tools like Coverity. Patch from
16543 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
16544 - Use direct writes rather than stdio when building microdescriptor
16545 caches, in an attempt to mitigate bug 8031, or at least make it
16548 o Minor bugfixes (config):
16549 - When rejecting a configuration because we were unable to parse a
16550 quoted string, log an actual error message. Fixes bug 7950; bugfix
16552 - Behave correctly when the user disables LearnCircuitBuildTimeout
16553 but doesn't tell us what they would like the timeout to be. Fixes
16554 bug 6304; bugfix on 0.2.2.14-alpha.
16555 - When autodetecting the number of CPUs, use the number of available
16556 CPUs in preference to the number of configured CPUs. Inform the
16557 user if this reduces the number of available CPUs. Fixes bug 8002;
16558 bugfix on 0.2.3.1-alpha.
16559 - Make it an error when you set EntryNodes but disable UseGuardNodes,
16560 since it will (surprisingly to some users) ignore EntryNodes. Fixes
16561 bug 8180; bugfix on 0.2.3.11-alpha.
16562 - Allow TestingTorNetworks to override the 4096-byte minimum for
16563 the Fast threshold. Otherwise they can't bootstrap until they've
16564 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
16565 - Fix some logic errors when the user manually overrides the
16566 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
16569 o Minor bugfixes (log messages to help diagnose bugs):
16570 - If we fail to free a microdescriptor because of bug 7164, log
16571 the filename and line number from which we tried to free it.
16572 - Add another diagnostic to the heartbeat message: track and log
16573 overhead that TLS is adding to the data we write. If this is
16574 high, we are sending too little data to SSL_write at a time.
16575 Diagnostic for bug 7707.
16576 - Add more detail to a log message about relaxed timeouts, to help
16578 - Warn more aggressively when flushing microdescriptors to a
16579 microdescriptor cache fails, in an attempt to mitigate bug 8031,
16580 or at least make it more diagnosable.
16581 - Improve debugging output to help track down bug 8185 ("Bug:
16582 outgoing relay cell has n_chan==NULL. Dropping.")
16583 - Log the purpose of a path-bias testing circuit correctly.
16584 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
16586 o Minor bugfixes (0.2.4.x log messages that were too noisy):
16587 - Don't attempt to relax the timeout of already opened 1-hop circuits.
16588 They might never timeout. This should eliminate some/all cases of
16589 the relaxed timeout log message.
16590 - Use circuit creation time for network liveness evaluation. This
16591 should eliminate warning log messages about liveness caused
16592 by changes in timeout evaluation. Fixes bug 6572; bugfix on
16594 - Reduce a path bias length check from notice to info. The message
16595 is triggered when creating controller circuits. Fixes bug 8196;
16596 bugfix on 0.2.4.8-alpha.
16597 - Fix a path state issue that triggered a notice during relay startup.
16598 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
16599 - Reduce occurrences of warns about circuit purpose in
16600 connection_ap_expire_building(). Fixes bug 8477; bugfix on
16603 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
16604 - If we encounter a write failure on a SOCKS connection before we
16605 finish our SOCKS handshake, don't warn that we closed the
16606 connection before we could send a SOCKS reply. Fixes bug 8427;
16607 bugfix on 0.1.0.1-rc.
16608 - Correctly recognize that [::1] is a loopback address. Fixes
16609 bug 8377; bugfix on 0.2.1.3-alpha.
16610 - Fix a directory authority warn caused when we have a large amount
16611 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
16612 - Don't log inappropriate heartbeat messages when hibernating: a
16613 hibernating node is _expected_ to drop out of the consensus,
16614 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
16615 bugfix on 0.2.3.1-alpha.
16616 - Don't complain about bootstrapping problems while hibernating.
16617 These complaints reflect a general code problem, but not one
16618 with any problematic effects (no connections are actually
16619 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
16621 o Documentation fixes:
16622 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
16623 names match. Fixes bug 7768.
16624 - Make the torify manpage no longer refer to tsocks; torify hasn't
16625 supported tsocks since 0.2.3.14-alpha.
16626 - Make the tor manpage no longer reference tsocks.
16627 - Fix the GeoIPExcludeUnknown documentation to refer to
16628 ExcludeExitNodes rather than the currently nonexistent
16629 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
16632 - The tor-tsocks.conf is no longer distributed or installed. We
16633 recommend that tsocks users use torsocks instead. Resolves
16637 Changes in version 0.2.4.11-alpha - 2013-03-11
16638 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
16639 more robust, makes hidden service authentication work again, and
16640 resolves a DPI fingerprint for Tor's SSL transport.
16642 o Major features (directory authorities):
16643 - Directory authorities now support a new consensus method (17)
16644 where they cap the published bandwidth of servers for which
16645 insufficient bandwidth measurements exist. Fixes part of bug 2286.
16646 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
16647 serve any v2 directory information. Now we can test disabling the
16648 old deprecated v2 directory format, and see whether doing so has
16649 any effect on network load. Begins to fix bug 6783.
16650 - Directory authorities now include inside each vote a statement of
16651 the performance thresholds they used when assigning flags.
16652 Implements ticket 8151.
16654 o Major bugfixes (directory authorities):
16655 - Stop marking every relay as having been down for one hour every
16656 time we restart a directory authority. These artificial downtimes
16657 were messing with our Stable and Guard flag calculations. Fixes
16658 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
16660 o Major bugfixes (hidden services):
16661 - Allow hidden service authentication to succeed again. When we
16662 refactored the hidden service introduction code back
16663 in 0.2.4.1-alpha, we didn't update the code that checks
16664 whether authentication information is present, causing all
16665 authentication checks to return "false". Fix for bug 8207; bugfix
16666 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
16668 o Minor features (relays, bridges):
16669 - Make bridge relays check once a minute for whether their IP
16670 address has changed, rather than only every 15 minutes. Resolves
16671 bugs 1913 and 1992.
16672 - Refactor resolve_my_address() so it returns the method by which we
16673 decided our public IP address (explicitly configured, resolved from
16674 explicit hostname, guessed from interfaces, learned by gethostname).
16675 Now we can provide more helpful log messages when a relay guesses
16676 its IP address incorrectly (e.g. due to unexpected lines in
16677 /etc/hosts). Resolves ticket 2267.
16678 - Teach bridge-using clients to avoid 0.2.2 bridges when making
16679 microdescriptor-related dir requests, and only fall back to normal
16680 descriptors if none of their bridges can handle microdescriptors
16681 (as opposed to the fix in ticket 4013, which caused them to fall
16682 back to normal descriptors if *any* of their bridges preferred
16683 them). Resolves ticket 4994.
16684 - Randomize the lifetime of our SSL link certificate, so censors can't
16685 use the static value for filtering Tor flows. Resolves ticket 8443;
16686 related to ticket 4014 which was included in 0.2.2.33.
16687 - Support a new version of the link protocol that allows 4-byte circuit
16688 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
16689 a possible resource exhaustion issue. Closes ticket 7351; implements
16692 o Minor features (portability):
16693 - Tweak the curve25519-donna*.c implementations to tolerate systems
16694 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
16695 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
16696 the signs of types during autoconf. This is better than our old
16697 approach, which didn't work when cross-compiling.
16698 - Detect the sign of enum values, rather than assuming that MSC is the
16699 only compiler where enum types are all signed. Fixes bug 7727;
16700 bugfix on 0.2.4.10-alpha.
16702 o Minor features (other):
16703 - Say "KBytes" rather than "KB" in the man page (for various values
16704 of K), to further reduce confusion about whether Tor counts in
16705 units of memory or fractions of units of memory. Resolves ticket 7054.
16706 - Clear the high bit on curve25519 public keys before passing them to
16707 our backend, in case we ever wind up using a backend that doesn't do
16708 so itself. If we used such a backend, and *didn't* clear the high bit,
16709 we could wind up in a situation where users with such backends would
16710 be distinguishable from users without. Fixes bug 8121; bugfix on
16712 - Update to the March 6 2013 Maxmind GeoLite Country database.
16714 o Minor bugfixes (clients):
16715 - When we receive a RELAY_END cell with the reason DONE, or with no
16716 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
16717 status as "connection refused". Previously we reported these cases
16718 as success but then immediately closed the connection. Fixes bug
16719 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
16720 - Downgrade an assertion in connection_ap_expire_beginning to an
16721 LD_BUG message. The fix for bug 8024 should prevent this message
16722 from displaying, but just in case, a warn that we can diagnose
16723 is better than more assert crashes. Fixes bug 8065; bugfix on
16725 - Lower path use bias thresholds to .80 for notice and .60 for warn.
16726 Also make the rate limiting flags for the path use bias log messages
16727 independent from the original path bias flags. Fixes bug 8161;
16728 bugfix on 0.2.4.10-alpha.
16730 o Minor bugfixes (relays):
16731 - Stop trying to resolve our hostname so often (e.g. every time we
16732 think about doing a directory fetch). Now we reuse the cached
16733 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
16734 and 2410 (bugfix on 0.1.2.2-alpha).
16735 - Stop sending a stray "(null)" in some cases for the server status
16736 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
16738 - When choosing which stream on a formerly stalled circuit to wake
16739 first, make better use of the platform's weak RNG. Previously,
16740 we had been using the % ("modulo") operator to try to generate a
16741 1/N chance of picking each stream, but this behaves badly with
16742 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
16744 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
16745 Irix's random() only return 15 bits; Solaris's random() returns more
16746 bits but its RAND_MAX says it only returns 15, and so on. Motivated
16747 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
16749 o Minor bugfixes (directory authorities):
16750 - Directory authorities now use less space when formatting identical
16751 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
16754 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
16755 - Avoid leaking memory if we fail to compute a consensus signature
16756 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
16757 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
16759 - Fix a memory leak during safe-cookie controller authentication.
16760 Bugfix on 0.2.3.13-alpha.
16761 - Avoid memory leak of IPv6 policy content if we fail to format it into
16762 a router descriptor. Bugfix on 0.2.4.7-alpha.
16764 o Minor bugfixes (other code correctness issues):
16765 - Avoid a crash if we fail to generate an extrainfo descriptor.
16766 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
16767 this is CID 718634.
16768 - When detecting the largest possible file descriptor (in order to
16769 close all file descriptors when launching a new program), actually
16770 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
16771 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
16773 - Fix a copy-and-paste error when adding a missing A1 to a routerset
16774 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
16775 Bugfix on 0.2.4.10-alpha.
16776 - Fix an impossible-to-trigger integer overflow when estimating how
16777 long our onionskin queue would take. (This overflow would require us
16778 to accept 4 million onionskins before processing 100 of them.) Fixes
16779 bug 8210; bugfix on 0.2.4.10-alpha.
16781 o Code simplification and refactoring:
16782 - Add a wrapper function for the common "log a message with a
16786 Changes in version 0.2.4.10-alpha - 2013-02-04
16787 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
16788 certain attacks that flood the network with relays; changes the queue
16789 for circuit create requests from a sized-based limit to a time-based
16790 limit; resumes building with MSVC on Windows; and fixes a wide variety
16793 o Major bugfixes (directory authority):
16794 - When computing directory thresholds, ignore any rejected-as-sybil
16795 nodes during the computation so that they can't influence Fast,
16796 Guard, etc. (We should have done this for proposal 109.) Fixes
16798 - When marking a node as a likely sybil, reset its uptime metrics
16799 to zero, so that it cannot time towards getting marked as Guard,
16800 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
16804 - When a TLS write is partially successful but incomplete, remember
16805 that the flushed part has been flushed, and notice that bytes were
16806 actually written. Reported and fixed pseudonymously. Fixes bug
16807 7708; bugfix on Tor 0.1.0.5-rc.
16808 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
16809 ID: these could be used to create unexpected streams and circuits
16810 which would count as "present" to some parts of Tor but "absent"
16811 to others, leading to zombie circuits and streams or to a bandwidth
16812 denial-of-service. Fixes bug 7889; bugfix on every released version
16813 of Tor. Reported by "oftc_must_be_destroyed".
16814 - Rename all macros in our local copy of queue.h to begin with "TOR_".
16815 This change seems the only good way to permanently prevent conflicts
16816 with queue.h on various operating systems. Fixes bug 8107; bugfix
16819 o Major features (relay):
16820 - Instead of limiting the number of queued onionskins (aka circuit
16821 create requests) to a fixed, hard-to-configure number, we limit
16822 the size of the queue based on how many we expect to be able to
16823 process in a given amount of time. We estimate the time it will
16824 take to process an onionskin based on average processing time
16825 of previous onionskins. Closes ticket 7291. You'll never have to
16826 configure MaxOnionsPending again.
16828 o Major features (portability):
16829 - Resume building correctly with MSVC and Makefile.nmake. This patch
16830 resolves numerous bugs and fixes reported by ultramage, including
16831 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
16832 - Make the ntor and curve25519 code build correctly with MSVC.
16833 Fix on 0.2.4.8-alpha.
16836 - When directory authorities are computing thresholds for flags,
16837 never let the threshold for the Fast flag fall below 4096
16838 bytes. Also, do not consider nodes with extremely low bandwidths
16839 when deciding thresholds for various directory flags. This change
16840 should raise our threshold for Fast relays, possibly in turn
16841 improving overall network performance; see ticket 1854. Resolves
16843 - The Tor client now ignores sub-domain components of a .onion
16844 address. This change makes HTTP "virtual" hosting
16845 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
16846 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
16847 hosted on the same hidden service. Implements proposal 204.
16848 - We compute the overhead from passing onionskins back and forth to
16849 cpuworkers, and report it when dumping statistics in response to
16850 SIGUSR1. Supports ticket 7291.
16852 o Minor features (path selection):
16853 - When deciding whether we have enough descriptors to build circuits,
16854 instead of looking at raw relay counts, look at which fraction
16855 of (bandwidth-weighted) paths we're able to build. This approach
16856 keeps clients from building circuits if their paths are likely to
16857 stand out statistically. The default fraction of paths needed is
16858 taken from the consensus directory; you can override it with the
16859 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
16860 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
16861 and we have GeoIP information, also exclude all nodes with unknown
16862 countries "??" and "A1". This behavior is controlled by the
16863 new GeoIPExcludeUnknown option: you can make such nodes always
16864 excluded with "GeoIPExcludeUnknown 1", and disable the feature
16865 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
16866 gets you the default behavior. Implements feature 7706.
16867 - Path Use Bias: Perform separate accounting for successful circuit
16868 use. Keep separate statistics on stream attempt rates versus stream
16869 success rates for each guard. Provide configurable thresholds to
16870 determine when to emit log messages or disable use of guards that
16871 fail too many stream attempts. Resolves ticket 7802.
16873 o Minor features (log messages):
16874 - When learning a fingerprint for a bridge, log its corresponding
16875 transport type. Implements ticket 7896.
16876 - Improve the log message when "Bug/attack: unexpected sendme cell
16877 from client" occurs, to help us track bug 8093.
16880 - Remove a couple of extraneous semicolons that were upsetting the
16881 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
16882 bugfix on 0.2.2.1-alpha.
16883 - Remove a source of rounding error during path bias count scaling;
16884 don't count cannibalized circuits as used for path bias until we
16885 actually try to use them; and fix a circuit_package_relay_cell()
16886 warning message about n_chan==NULL. Fixes bug 7802.
16887 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
16888 actually link against nacl when we're configured to use it. Fixes
16889 bug 7972; bugfix on 0.2.4.8-alpha.
16890 - Compile correctly with the --disable-curve25519 option. Fixes
16891 bug 8153; bugfix on 0.2.4.8-alpha.
16893 o Build improvements:
16894 - Do not report status verbosely from autogen.sh unless the -v flag
16895 is specified. Fixes issue 4664. Patch from Onizuka.
16896 - Replace all calls to snprintf() outside of src/ext with
16897 tor_snprintf(). Also remove the #define to replace snprintf with
16898 _snprintf on Windows; they have different semantics, and all of
16899 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
16900 - Try to detect if we are ever building on a platform where
16901 memset(...,0,...) does not set the value of a double to 0.0. Such
16902 platforms are permitted by the C standard, though in practice
16903 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
16904 currently support them, but it's better to detect them and fail
16905 than to perform erroneously.
16907 o Removed features:
16908 - Stop exporting estimates of v2 and v3 directory traffic shares
16909 in extrainfo documents. They were unneeded and sometimes inaccurate.
16910 Also stop exporting any v2 directory request statistics. Resolves
16912 - Drop support for detecting and warning about versions of Libevent
16913 before 1.3e. Nothing reasonable ships with them any longer;
16914 warning the user about them shouldn't be needed. Resolves ticket
16917 o Code simplifications and refactoring:
16918 - Rename "isin" functions to "contains", for grammar. Resolves
16920 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
16921 with the natural logarithm function from the system libm. Resolves
16925 Changes in version 0.2.4.9-alpha - 2013-01-15
16926 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
16927 work more robustly.
16930 - Fix backward compatibility logic when receiving an embedded ntor
16931 handshake tunneled in a CREATE cell. This clears up the "Bug:
16932 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
16936 Changes in version 0.2.4.8-alpha - 2013-01-14
16937 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
16938 risks, adds a new stronger and faster circuit handshake, and offers
16939 stronger and faster link encryption when both sides support it.
16942 - Preliminary support for directory guards (proposal 207): when
16943 possible, clients now use their entry guards for non-anonymous
16944 directory requests. This can help prevent client enumeration. Note
16945 that this behavior only works when we have a usable consensus
16946 directory, and when options about what to download are more or less
16947 standard. In the future we should re-bootstrap from our guards,
16948 rather than re-bootstrapping from the preconfigured list of
16949 directory sources that ships with Tor. Resolves ticket 6526.
16950 - Tor relays and clients now support a better CREATE/EXTEND cell
16951 format, allowing the sender to specify multiple address, identity,
16952 and handshake types. Implements Robert Ransom's proposal 200;
16953 closes ticket 7199.
16955 o Major features (new circuit handshake):
16956 - Tor now supports a new circuit extension handshake designed by Ian
16957 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
16958 circuit extension handshake, later called "TAP", was a bit slow
16959 (especially on the relay side), had a fragile security proof, and
16960 used weaker keys than we'd now prefer. The new circuit handshake
16961 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
16962 function, making it significantly more secure than the older
16963 handshake, and significantly faster. Tor can use one of two built-in
16964 pure-C curve25519-donna implementations by Adam Langley, or it
16965 can link against the "nacl" library for a tuned version if present.
16967 The built-in version is very fast for 64-bit systems when building
16968 with GCC. The built-in 32-bit version is still faster than the
16969 old TAP protocol, but using libnacl is better on most such hosts.
16971 Clients don't currently use this protocol by default, since
16972 comparatively few clients support it so far. To try it, set
16973 UseNTorHandshake to 1.
16975 Implements proposal 216; closes ticket 7202.
16977 o Major features (better link encryption):
16978 - Relays can now enable the ECDHE TLS ciphersuites when available
16979 and appropriate. These ciphersuites let us negotiate forward-secure
16980 TLS secret keys more safely and more efficiently than with our
16981 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
16982 public relays prefer the (faster) P224 group, and bridges prefer
16983 the (more common) P256 group; you can override this with the
16986 Enabling these ciphers was a little tricky, since for a long time,
16987 clients had been claiming to support them without actually doing
16988 so, in order to foil fingerprinting. But with the client-side
16989 implementation of proposal 198 in 0.2.3.17-beta, clients can now
16990 match the ciphers from recent Firefox versions *and* list the
16991 ciphers they actually mean, so relays can believe such clients
16992 when they advertise ECDHE support in their TLS ClientHello messages.
16994 This feature requires clients running 0.2.3.17-beta or later,
16995 and requires both sides to be running OpenSSL 1.0.0 or later
16996 with ECC support. OpenSSL 1.0.1, with the compile-time option
16997 "enable-ec_nistp_64_gcc_128", is highly recommended.
16999 Implements the relay side of proposal 198; closes ticket 7200.
17002 - Avoid crashing when, as a relay without IPv6-exit support, a
17003 client insists on getting an IPv6 address or nothing. Fixes bug
17004 7814; bugfix on 0.2.4.7-alpha.
17007 - Improve circuit build timeout handling for hidden services.
17008 In particular: adjust build timeouts more accurately depending
17009 upon the number of hop-RTTs that a particular circuit type
17010 undergoes. Additionally, launch intro circuits in parallel
17011 if they timeout, and take the first one to reply as valid.
17012 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
17013 separate error codes; or at least, don't break for that reason.
17014 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
17015 - Update to the January 2 2013 Maxmind GeoLite Country database.
17017 o Minor features (testing):
17018 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
17019 (P-256) Diffie-Hellman handshakes to src/or/bench.
17020 - Add benchmark functions to test onion handshake performance.
17022 o Minor features (path bias detection):
17023 - Alter the Path Bias log messages to be more descriptive in terms
17024 of reporting timeouts and other statistics.
17025 - Create three levels of Path Bias log messages, as opposed to just
17026 two. These are configurable via consensus as well as via the torrc
17027 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
17028 The default values are 0.70, 0.50, and 0.30 respectively.
17029 - Separate the log message levels from the decision to drop guards,
17030 which also is available via torrc option PathBiasDropGuards.
17031 PathBiasDropGuards still defaults to 0 (off).
17032 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
17033 in combination with PathBiasExtremeRate.
17034 - Increase the default values for PathBiasScaleThreshold and
17035 PathBiasCircThreshold from (200, 20) to (300, 150).
17036 - Add in circuit usage accounting to path bias. If we try to use a
17037 built circuit but fail for any reason, it counts as path bias.
17038 Certain classes of circuits where the adversary gets to pick your
17039 destination node are exempt from this accounting. Usage accounting
17040 can be specifically disabled via consensus parameter or torrc.
17041 - Convert all internal path bias state to double-precision floating
17042 point, to avoid roundoff error and other issues.
17043 - Only record path bias information for circuits that have completed
17044 *two* hops. Assuming end-to-end tagging is the attack vector, this
17045 makes us more resilient to ambient circuit failure without any
17046 detection capability loss.
17048 o Minor bugfixes (log messages):
17049 - Rate-limit the "No circuits are opened. Relaxed timeout for a
17050 circuit with channel state open..." message to once per hour to
17051 keep it from filling the notice logs. Mitigates bug 7799 but does
17052 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
17053 - Avoid spurious warnings when configuring multiple client ports of
17054 which only some are nonlocal. Previously, we had claimed that some
17055 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
17058 o Code simplifications and refactoring:
17059 - Get rid of a couple of harmless clang warnings, where we compared
17060 enums to ints. These warnings are newly introduced in clang 3.2.
17061 - Split the onion.c file into separate modules for the onion queue
17062 and the different handshakes it supports.
17063 - Remove the marshalling/unmarshalling code for sending requests to
17064 cpuworkers over a socket, and instead just send structs. The
17065 recipient will always be the same Tor binary as the sender, so
17066 any encoding is overkill.
17069 Changes in version 0.2.4.7-alpha - 2012-12-24
17070 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
17071 directory mirrors for more robust bootstrapping; fixes more issues where
17072 clients with changing network conditions refuse to make any circuits;
17073 adds initial support for exiting to IPv6 addresses; resumes being able
17074 to update our GeoIP database, and includes the geoip6 file this time;
17075 turns off the client-side DNS cache by default due to privacy risks;
17076 and fixes a variety of other issues.
17078 o Major features (client resilience):
17079 - Add a new "FallbackDir" torrc option to use when we can't use
17080 a directory mirror from the consensus (either because we lack a
17081 consensus, or because they're all down). Currently, all authorities
17082 are fallbacks by default, and there are no other default fallbacks,
17083 but that will change. This option will allow us to give clients a
17084 longer list of servers to try to get a consensus from when first
17085 connecting to the Tor network, and thereby reduce load on the
17086 directory authorities. Implements proposal 206, "Preconfigured
17087 directory sources for bootstrapping". We also removed the old
17088 "FallbackNetworkstatus" option, since we never got it working well
17089 enough to use it. Closes bug 572.
17090 - If we have no circuits open, use a relaxed timeout (the
17091 95-percentile cutoff) until a circuit succeeds. This heuristic
17092 should allow Tor to succeed at building circuits even when the
17093 network connection drastically changes. Should help with bug 3443.
17095 o Major features (IPv6):
17096 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
17097 connectivity, then set the IPv6Exit flag to 1. Also make sure your
17098 exit policy reads as you would like: the address * applies to all
17099 address families, whereas *4 is IPv4 address only, and *6 is IPv6
17100 addresses only. On the client side, you'll need to wait until the
17101 authorities have upgraded, wait for enough exits to support IPv6,
17102 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
17103 ticket 5547, implements proposal 117 as revised in proposal 208.
17105 We DO NOT recommend that clients with actual anonymity needs start
17106 using IPv6 over Tor yet, since not enough exits support it yet.
17108 o Major features (geoip database):
17109 - Maxmind began labelling Tor relays as being in country "A1",
17110 which breaks by-country node selection inside Tor. Now we use a
17111 script to replace "A1" ("Anonymous Proxy") entries in our geoip
17112 file with real country codes. This script fixes about 90% of "A1"
17113 entries automatically and uses manual country code assignments to
17114 fix the remaining 10%. See src/config/README.geoip for details.
17115 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
17116 Country database, as modified above.
17118 o Major bugfixes (client-side DNS):
17119 - Turn off the client-side DNS cache by default. Updating and using
17120 the DNS cache is now configurable on a per-client-port
17121 level. SOCKSPort, DNSPort, etc lines may now contain
17122 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
17123 cache these types of DNS answers when we receive them from an
17124 exit node in response to an application request on this port, and
17125 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
17126 cached DNS answers of these types, we shouldn't use them. It's
17127 potentially risky to use cached DNS answers at the client, since
17128 doing so can indicate to one exit what answers we've gotten
17129 for DNS lookups in the past. With IPv6, this becomes especially
17130 problematic. Using cached DNS answers for requests on the same
17131 circuit would present less linkability risk, since all traffic
17132 on a circuit is already linkable, but it would also provide
17133 little performance benefit: the exit node caches DNS replies
17134 too. Implements a simplified version of Proposal 205. Implements
17137 o Major bugfixes (other):
17138 - Alter circuit build timeout measurement to start at the point
17139 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
17140 initialization). This should make our timeout measurements more
17141 uniform. Previously, we were sometimes including ORconn setup time
17142 in our circuit build time measurements. Should resolve bug 3443.
17143 - Fix an assertion that could trigger in hibernate_go_dormant() when
17144 closing an or_connection_t: call channel_mark_for_close() rather
17145 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
17147 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
17148 7655; bugfix on 0.2.4.6-alpha.
17151 - Add a new torrc option "ServerTransportListenAddr" to let bridge
17152 operators select the address where their pluggable transports will
17153 listen for connections. Resolves ticket 7013.
17154 - Allow an optional $ before the node identity digest in the
17155 controller command GETINFO ns/id/<identity>, for consistency with
17156 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
17157 - Log packaged cell fullness as part of the heartbeat message.
17158 Diagnosis to try to determine the extent of bug 7743.
17160 o Minor features (IPv6):
17161 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
17162 prefer to hand out virtual IPv6 addresses, since there are more of
17163 them and we can't run out. To override this behavior and make IPv4
17164 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
17165 or DNSPort you're using for resolving. Implements ticket 7571.
17166 - AutomapHostsOnResolve responses are now randomized, to avoid
17167 annoying situations where Tor is restarted and applications
17168 connect to the wrong addresses.
17169 - Never try more than 1000 times to pick a new virtual address when
17170 AutomapHostsOnResolve is set. That's good enough so long as we
17171 aren't close to handing out our entire virtual address space;
17172 if you're getting there, it's best to switch to IPv6 virtual
17176 - The ADDRMAP command can no longer generate an ill-formed error
17177 code on a failed MAPADDRESS. It now says "internal" rather than
17178 an English sentence fragment with spaces in the middle. Bugfix on
17179 Tor 0.2.0.19-alpha.
17180 - Fix log messages and comments to avoid saying "GMT" when we mean
17181 "UTC". Fixes bug 6113.
17182 - Compile on win64 using mingw64. Fixes bug 7260; patches from
17184 - Fix a crash when debugging unit tests on Windows: deallocate a
17185 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
17186 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
17189 - The DirServer option is now DirAuthority, for consistency with
17190 current naming patterns. You can still use the old DirServer form.
17192 o Code simplification and refactoring:
17193 - Move the client-side address-map/virtual-address/DNS-cache code
17194 out of connection_edge.c into a new addressmap.c module.
17195 - Remove unused code for parsing v1 directories and "running routers"
17196 documents. Fixes bug 6887.
17199 Changes in version 0.2.3.25 - 2012-11-19
17200 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
17201 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
17202 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
17203 programmer, and friend. Unstinting in his dedication to the cause of
17204 freedom, he inspired and helped many of us as we began our work on
17205 anonymity, and inspires us still. Please honor his memory by writing
17206 software to protect people's freedoms, and by helping others to do so.
17208 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
17209 significantly reduced directory overhead (via microdescriptors),
17210 enormous crypto performance improvements for fast relays on new
17211 enough hardware, a new v3 TLS handshake protocol that can better
17212 resist fingerprinting, support for protocol obfuscation plugins (aka
17213 pluggable transports), better scalability for hidden services, IPv6
17214 support for bridges, performance improvements like allowing clients
17215 to skip the first round-trip on the circuit ("optimistic data") and
17216 refilling token buckets more often, a new "stream isolation" design
17217 to isolate different applications on different circuits, and many
17218 stability, security, and privacy fixes.
17221 - Tor tries to wipe potentially sensitive data after using it, so
17222 that if some subsequent security failure exposes Tor's memory,
17223 the damage will be limited. But we had a bug where the compiler
17224 was eliminating these wipe operations when it decided that the
17225 memory was no longer visible to a (correctly running) program,
17226 hence defeating our attempt at defense in depth. We fix that
17227 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
17228 is unlikely to optimize away. Future versions of Tor may use
17229 a less ridiculously heavy approach for this. Fixes bug 7352.
17230 Reported in an article by Andrey Karpov.
17233 - Fix a harmless bug when opting against publishing a relay descriptor
17234 because DisableNetwork is set. Fixes bug 7464; bugfix on
17238 Changes in version 0.2.4.6-alpha - 2012-11-13
17239 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
17240 makes our defense-in-depth memory wiping more reliable, and begins to
17241 count IPv6 addresses in bridge statistics,
17244 - Fix an assertion failure that could occur when closing a connection
17245 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
17247 - Tor tries to wipe potentially sensitive data after using it, so
17248 that if some subsequent security failure exposes Tor's memory,
17249 the damage will be limited. But we had a bug where the compiler
17250 was eliminating these wipe operations when it decided that the
17251 memory was no longer visible to a (correctly running) program,
17252 hence defeating our attempt at defense in depth. We fix that
17253 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
17254 is unlikely to optimize away. Future versions of Tor may use
17255 a less ridiculously heavy approach for this. Fixes bug 7352.
17256 Reported in an article by Andrey Karpov.
17259 - Add GeoIP database for IPv6 addresses. The new config option
17261 - Bridge statistics now count bridge clients connecting over IPv6:
17262 bridge statistics files now list "bridge-ip-versions" and
17263 extra-info documents list "geoip6-db-digest". The control protocol
17264 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
17265 implementation by "shkoo", addressing ticket 5055.
17268 - Warn when we are binding low ports when hibernation is enabled;
17269 previously we had warned when we were _advertising_ low ports with
17270 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
17271 - Fix a harmless bug when opting against publishing a relay descriptor
17272 because DisableNetwork is set. Fixes bug 7464; bugfix on
17274 - Add warning message when a managed proxy dies during configuration.
17275 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
17276 - Fix a linking error when building tor-fw-helper without miniupnp.
17277 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
17278 - Check for closing an or_connection_t without going through correct
17279 channel functions; emit a warning and then call
17280 connection_or_close_for_error() so we don't assert as in bugs 7212
17282 - Compile correctly on compilers without C99 designated initializer
17283 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
17284 - Avoid a possible assert that can occur when channel_send_destroy() is
17285 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
17286 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
17287 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
17288 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
17289 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
17291 o Code simplification and refactoring:
17292 - Start using OpenBSD's implementation of queue.h, so that we don't
17293 need to hand-roll our own pointer and list structures whenever we
17294 need them. (We can't rely on a sys/queue.h, since some operating
17295 systems don't have them, and the ones that do have them don't all
17296 present the same extensions.)
17299 Changes in version 0.2.4.5-alpha - 2012-10-25
17300 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
17301 two important security vulnerabilities that could lead to remotely
17302 triggerable relay crashes, fix a major bug that was preventing clients
17303 from choosing suitable exit nodes, and refactor some of our code.
17305 o Major bugfixes (security, also in 0.2.3.24-rc):
17306 - Fix a group of remotely triggerable assertion failures related to
17307 incorrect link protocol negotiation. Found, diagnosed, and fixed
17308 by "some guy from France". Fix for CVE-2012-2250; bugfix on
17310 - Fix a denial of service attack by which any directory authority
17311 could crash all the others, or by which a single v2 directory
17312 authority could crash everybody downloading v2 directory
17313 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
17315 o Major bugfixes (also in 0.2.3.24-rc):
17316 - When parsing exit policy summaries from microdescriptors, we had
17317 previously been ignoring the last character in each one, so that
17318 "accept 80,443,8080" would be treated by clients as indicating
17319 a node that allows access to ports 80, 443, and 808. That would
17320 lead to clients attempting connections that could never work,
17321 and ignoring exit nodes that would support their connections. Now
17322 clients parse these exit policy summaries correctly. Fixes bug 7192;
17323 bugfix on 0.2.3.1-alpha.
17325 o Minor bugfixes (also in 0.2.3.24-rc):
17326 - Clients now consider the ClientRejectInternalAddresses config option
17327 when using a microdescriptor consensus stanza to decide whether
17328 an exit relay would allow exiting to an internal address. Fixes
17329 bug 7190; bugfix on 0.2.3.1-alpha.
17332 - Only disable TLS session ticket support when running as a TLS
17333 server. Now clients will blend better with regular Firefox
17334 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
17336 o Code simplification and refactoring:
17337 - Start using OpenBSD's implementation of queue.h (originally by
17339 - Move the entry node code from circuitbuild.c to its own file.
17340 - Move the circuit build timeout tracking code from circuitbuild.c
17344 Changes in version 0.2.3.24-rc - 2012-10-25
17345 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
17346 could lead to remotely triggerable relay crashes, and fixes
17347 a major bug that was preventing clients from choosing suitable exit
17350 o Major bugfixes (security):
17351 - Fix a group of remotely triggerable assertion failures related to
17352 incorrect link protocol negotiation. Found, diagnosed, and fixed
17353 by "some guy from France". Fix for CVE-2012-2250; bugfix on
17355 - Fix a denial of service attack by which any directory authority
17356 could crash all the others, or by which a single v2 directory
17357 authority could crash everybody downloading v2 directory
17358 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
17361 - When parsing exit policy summaries from microdescriptors, we had
17362 previously been ignoring the last character in each one, so that
17363 "accept 80,443,8080" would be treated by clients as indicating
17364 a node that allows access to ports 80, 443, and 808. That would
17365 lead to clients attempting connections that could never work,
17366 and ignoring exit nodes that would support their connections. Now
17367 clients parse these exit policy summaries correctly. Fixes bug 7192;
17368 bugfix on 0.2.3.1-alpha.
17371 - Clients now consider the ClientRejectInternalAddresses config option
17372 when using a microdescriptor consensus stanza to decide whether
17373 an exit relay would allow exiting to an internal address. Fixes
17374 bug 7190; bugfix on 0.2.3.1-alpha.
17377 Changes in version 0.2.4.4-alpha - 2012-10-20
17378 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
17379 vulnerability introduced by a change in OpenSSL, fixes a remotely
17380 triggerable assert, and adds new channel_t and circuitmux_t abstractions
17381 that will make it easier to test new connection transport and cell
17382 scheduling algorithms.
17384 o New directory authorities (also in 0.2.3.23-rc):
17385 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
17386 authority. Closes ticket 5749.
17388 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
17389 - Disable TLS session tickets. OpenSSL's implementation was giving
17390 our TLS session keys the lifetime of our TLS context objects, when
17391 perfect forward secrecy would want us to discard anything that
17392 could decrypt a link connection as soon as the link connection
17393 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
17394 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
17395 - Discard extraneous renegotiation attempts once the V3 link
17396 protocol has been initiated. Failure to do so left us open to
17397 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
17398 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
17400 o Internal abstraction features:
17401 - Introduce new channel_t abstraction between circuits and
17402 or_connection_t to allow for implementing alternate OR-to-OR
17403 transports. A channel_t is an abstract object which can either be a
17404 cell-bearing channel, which is responsible for authenticating and
17405 handshaking with the remote OR and transmitting cells to and from
17406 it, or a listening channel, which spawns new cell-bearing channels
17407 at the request of remote ORs. Implements part of ticket 6465.
17408 - Also new is the channel_tls_t subclass of channel_t, adapting it
17409 to the existing or_connection_t code. The V2/V3 protocol handshaking
17410 code which formerly resided in command.c has been moved below the
17411 channel_t abstraction layer and may be found in channeltls.c now.
17412 Implements the rest of ticket 6465.
17413 - Introduce new circuitmux_t storing the queue of circuits for
17414 a channel; this encapsulates and abstracts the queue logic and
17415 circuit selection policy, and allows the latter to be overridden
17416 easily by switching out a policy object. The existing EWMA behavior
17417 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
17419 o Required libraries:
17420 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
17421 strongly recommended.
17424 - Warn users who run hidden services on a Tor client with
17425 UseEntryGuards disabled that their hidden services will be
17426 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
17427 attack which motivated Tor to support entry guards in the first
17428 place). Resolves ticket 6889.
17429 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
17430 dhill. Resolves ticket 6982.
17431 - Option OutboundBindAddress can be specified multiple times and
17432 accepts IPv6 addresses. Resolves ticket 6876.
17434 o Minor bugfixes (also in 0.2.3.23-rc):
17435 - Don't serve or accept v2 hidden service descriptors over a
17436 relay's DirPort. It's never correct to do so, and disabling it
17437 might make it more annoying to exploit any bugs that turn up in the
17438 descriptor-parsing code. Fixes bug 7149.
17439 - Fix two cases in src/or/transports.c where we were calling
17440 fmt_addr() twice in a parameter list. Bug found by David
17441 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
17442 - Fix memory leaks whenever we logged any message about the "path
17443 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
17444 - When relays refuse a "create" cell because their queue of pending
17445 create cells is too big (typically because their cpu can't keep up
17446 with the arrival rate), send back reason "resource limit" rather
17447 than reason "internal", so network measurement scripts can get a
17448 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
17451 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
17452 - Free some more still-in-use memory at exit, to make hunting for
17453 memory leaks easier. Resolves bug 7029.
17454 - When a Tor client gets a "truncated" relay cell, the first byte of
17455 its payload specifies why the circuit was truncated. We were
17456 ignoring this 'reason' byte when tearing down the circuit, resulting
17457 in the controller not being told why the circuit closed. Now we
17458 pass the reason from the truncated cell to the controller. Bugfix
17459 on 0.1.2.3-alpha; fixes bug 7039.
17460 - Downgrade "Failed to hand off onionskin" messages to "debug"
17461 severity, since they're typically redundant with the "Your computer
17462 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
17463 - Make clients running with IPv6 bridges connect over IPv6 again,
17464 even without setting new config options ClientUseIPv6 and
17465 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
17466 - Use square brackets around IPv6 addresses in numerous places
17467 that needed them, including log messages, HTTPS CONNECT proxy
17468 requests, TransportProxy statefile entries, and pluggable transport
17469 extra-info lines. Fixes bug 7011; patch by David Fifield.
17471 o Code refactoring and cleanup:
17472 - Source files taken from other packages now reside in src/ext;
17473 previously they were scattered around the rest of Tor.
17474 - Avoid use of reserved identifiers in our C code. The C standard
17475 doesn't like us declaring anything that starts with an
17476 underscore, so let's knock it off before we get in trouble. Fix
17477 for bug 1031; bugfix on the first Tor commit.
17480 Changes in version 0.2.3.23-rc - 2012-10-20
17481 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
17482 vulnerability introduced by a change in OpenSSL, and fixes a variety
17483 of smaller bugs in preparation for the release.
17485 o New directory authorities:
17486 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
17487 authority. Closes ticket 5749.
17489 o Major bugfixes (security/privacy):
17490 - Disable TLS session tickets. OpenSSL's implementation was giving
17491 our TLS session keys the lifetime of our TLS context objects, when
17492 perfect forward secrecy would want us to discard anything that
17493 could decrypt a link connection as soon as the link connection
17494 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
17495 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
17496 - Discard extraneous renegotiation attempts once the V3 link
17497 protocol has been initiated. Failure to do so left us open to
17498 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
17499 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
17502 - Fix a possible crash bug when checking for deactivated circuits
17503 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
17504 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
17506 o Minor bugfixes (on 0.2.3.x):
17507 - Fix two cases in src/or/transports.c where we were calling
17508 fmt_addr() twice in a parameter list. Bug found by David
17509 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
17510 - Convert an assert in the pathbias code to a log message. The assert
17511 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
17512 bugfix on 0.2.3.17-beta.
17513 - Fix memory leaks whenever we logged any message about the "path
17514 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
17516 o Minor bugfixes (on 0.2.2.x and earlier):
17517 - Don't serve or accept v2 hidden service descriptors over a relay's
17518 DirPort. It's never correct to do so, and disabling it might
17519 make it more annoying to exploit any bugs that turn up in the
17520 descriptor-parsing code. Fixes bug 7149.
17521 - When relays refuse a "create" cell because their queue of pending
17522 create cells is too big (typically because their cpu can't keep up
17523 with the arrival rate), send back reason "resource limit" rather
17524 than reason "internal", so network measurement scripts can get a
17525 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
17526 - Correct file sizes when reading binary files on Cygwin, to avoid
17527 a bug where Tor would fail to read its state file. Fixes bug 6844;
17528 bugfix on 0.1.2.7-alpha.
17529 - Avoid undefined behavior when parsing the list of supported
17530 rendezvous/introduction protocols in a hidden service descriptor.
17531 Previously, Tor would have confused (as-yet-unused) protocol version
17532 numbers greater than 32 with lower ones on many platforms. Fixes
17533 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
17535 o Documentation fixes:
17536 - Clarify that hidden services are TCP only. Fixes bug 6024.
17539 Changes in version 0.2.4.3-alpha - 2012-09-22
17540 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
17541 assertion, resumes letting relays test reachability of their DirPort,
17542 and cleans up a bunch of smaller bugs.
17545 - Fix an assertion failure in tor_timegm() that could be triggered
17546 by a badly formatted directory object. Bug found by fuzzing with
17547 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
17550 - Fix a possible crash bug when checking for deactivated circuits
17551 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
17552 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
17553 - Allow routers to detect that their own DirPorts are running. When
17554 we removed support for versions_supports_begindir, we also
17555 accidentally removed the mechanism we used to self-test our
17556 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
17557 bugfix on 0.2.4.2-alpha.
17559 o Security features:
17560 - Switch to a completely time-invariant approach for picking nodes
17561 weighted by bandwidth. Our old approach would run through the
17562 part of the loop after it had made its choice slightly slower
17563 than it ran through the part of the loop before it had made its
17564 choice. Addresses ticket 6538.
17565 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
17566 by tor2web clients allows hidden services to identify tor2web
17567 clients through their repeated selection of the same rendezvous
17568 and introduction point circuit endpoints (their guards). Resolves
17572 - Enable Tor to read configuration, state, and key information from
17573 a FIFO. Previously Tor would only read from files with a positive
17574 stat.st_size. Code from meejah; fixes bug 6044.
17577 - Correct file sizes when reading binary files on Cygwin, to avoid
17578 a bug where Tor would fail to read its state file. Fixes bug 6844;
17579 bugfix on 0.1.2.7-alpha.
17580 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
17581 bugfix on 0.2.0.3-alpha.
17582 - When complaining about a client port on a public address, log
17583 which address we're complaining about. Fixes bug 4020; bugfix on
17584 0.2.3.3-alpha. Patch by Tom Fitzhenry.
17585 - Convert an assert in the pathbias code to a log message. The assert
17586 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
17587 bugfix on 0.2.3.17-beta.
17588 - Our new buildsystem was overzealous about rebuilding manpages: it
17589 would rebuild them all whenever any one of them changed. Now our
17590 dependency checking should be correct. Fixes bug 6843; bugfix on
17592 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
17593 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
17594 - Correct log printout about which address family is preferred
17595 when connecting to a bridge with both an IPv4 and IPv6 OR port.
17596 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
17598 o Minor bugfixes (code cleanliness):
17599 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
17600 with large values. This situation was untriggered, but nevertheless
17601 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
17602 - Reject consensus votes with more than 64 known-flags. We aren't even
17603 close to that limit yet, and our code doesn't handle it correctly.
17604 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
17605 - Avoid undefined behavior when parsing the list of supported
17606 rendezvous/introduction protocols in a hidden service descriptor.
17607 Previously, Tor would have confused (as-yet-unused) protocol version
17608 numbers greater than 32 with lower ones on many platforms. Fixes
17609 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
17610 - Fix handling of rendezvous client authorization types over 8.
17611 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
17612 - Fix building with older versions of GCC (2.95, for one) that don't
17613 like preprocessor directives inside macro arguments. Found by
17614 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
17615 - Switch weighted node selection rule from using a list of doubles
17616 to using a list of int64_t. This change should make the process
17617 slightly easier to debug and maintain. Needed to finish ticket 6538.
17619 o Code simplification and refactoring:
17620 - Move the generic "config" code into a new file, and have "config.c"
17621 hold only torrc- and state-related code. Resolves ticket 6823.
17622 - Move the core of our "choose a weighted element at random" logic
17623 into its own function, and give it unit tests. Now the logic is
17624 testable, and a little less fragile too.
17625 - Removed the testing_since field of node_t, which hasn't been used
17626 for anything since 0.2.0.9-alpha.
17628 o Documentation fixes:
17629 - Clarify that hidden services are TCP only. Fixes bug 6024.
17630 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
17634 Changes in version 0.2.3.22-rc - 2012-09-11
17635 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
17639 - Fix an assertion failure in tor_timegm() that could be triggered
17640 by a badly formatted directory object. Bug found by fuzzing with
17641 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
17644 - Avoid segfault when starting up having run with an extremely old
17645 version of Tor and parsing its state file. Fixes bug 6801; bugfix
17649 Changes in version 0.2.2.39 - 2012-09-11
17650 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
17654 - Fix an assertion failure in tor_timegm() that could be triggered
17655 by a badly formatted directory object. Bug found by fuzzing with
17656 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
17657 - Do not crash when comparing an address with port value 0 to an
17658 address policy. This bug could have been used to cause a remote
17659 assertion failure by or against directory authorities, or to
17660 allow some applications to crash clients. Fixes bug 6690; bugfix
17664 Changes in version 0.2.4.2-alpha - 2012-09-10
17665 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
17666 raises the default rate limiting even more, and makes the bootstrapping
17667 log messages less noisy.
17670 - Automatically forward the TCP ports of pluggable transport
17671 proxies using tor-fw-helper if PortForwarding is enabled. Implements
17675 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
17676 to 1GB/1GB. The previous defaults were intended to be "basically
17677 infinite", but it turns out they're now limiting our 100mbit+
17678 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
17679 last time we raised it).
17682 - Detect when we're running with a version of OpenSSL other than the
17683 one we compiled with. This has occasionally given people hard-to-
17685 - Log fewer lines at level "notice" about our OpenSSL and Libevent
17686 versions and capabilities when everything is going right. Resolves
17687 part of ticket 6736.
17688 - Directory authorities no long accept descriptors for any version of
17689 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
17690 These versions are insecure, unsupported, or both. Implements
17694 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
17695 to start with a triple-underscore so the controller won't touch it.
17696 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
17697 - Avoid segfault when starting up having run with an extremely old
17698 version of Tor and parsing its state file. Fixes bug 6801; bugfix
17700 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
17701 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
17702 - Don't follow the NULL pointer if microdescriptor generation fails.
17703 (This does not appear to be triggerable, but it's best to be safe.)
17704 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
17705 - Fix mis-declared dependencies on src/common/crypto.c and
17706 src/or/tor_main.c that could break out-of-tree builds under some
17707 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
17708 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
17709 6778; bugfix on 0.2.4.1-alpha.
17710 - Fix a harmless (in this case) build warning for implicitly
17711 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
17713 o Removed features:
17714 - Now that all versions before 0.2.2.x are disallowed, we no longer
17715 need to work around their missing features. Thus we can remove a
17716 bunch of compatibility code.
17718 o Code refactoring:
17719 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
17720 TCP ports to forward. In the past it only accepted two ports:
17721 the ORPort and the DirPort.
17724 Changes in version 0.2.4.1-alpha - 2012-09-05
17725 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
17726 bridgedb; lets relays use IPv6 addresses and directory authorities
17727 advertise them; and switches to a cleaner build interface.
17729 This is the first alpha release in a new series, so expect there to
17730 be bugs. Users who would rather test out a more stable branch should
17731 stay with 0.2.3.x for now.
17733 o Major features (bridges):
17734 - Bridges now report the pluggable transports they support to the
17735 bridge authority, so it can pass the supported transports on to
17736 bridgedb and/or eventually do reachability testing. Implements
17739 o Major features (IPv6):
17740 - Bridge authorities now accept IPv6 bridge addresses and include
17741 them in network status documents. Implements ticket 5534.
17742 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
17743 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
17744 to happen. Implements ticket 5535.
17745 - All kind of relays, not just bridges, can now advertise an IPv6
17746 OR port. Implements ticket 6362.
17747 - Directory authorities vote on IPv6 OR ports using the new consensus
17748 method 14. Implements ticket 6363.
17750 o Major features (build):
17751 - Switch to a nonrecursive Makefile structure. Now instead of each
17752 Makefile.am invoking other Makefile.am's, there is a master
17753 Makefile.am that includes the others. This change makes our build
17754 process slightly more maintainable, and improves parallelism for
17755 building with make -j. Original patch by Stewart Smith; various
17756 fixes by Jim Meyering.
17757 - Where available, we now use automake's "silent" make rules by
17758 default, so that warnings are easier to spot. You can get the old
17759 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
17761 o Minor features (code security and spec conformance):
17762 - Clear keys and key-derived material left on the stack in
17763 rendservice.c and rendclient.c. Check return value of
17764 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
17765 These fixes should make us more forward-secure against cold-boot
17766 attacks and the like. Fixes bug 2385.
17767 - Reject EXTEND cells sent to nonexistent streams. According to the
17768 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
17769 we were only checking for stream IDs that were currently in use.
17770 Found while hunting for more instances of bug 6271. Bugfix on
17771 0.0.2pre8, which introduced incremental circuit construction.
17773 o Minor features (streamlining);
17774 - No longer include the "opt" prefix when generating routerinfos
17775 or v2 directories: it has been needless since Tor 0.1.2. Closes
17777 - Remove some now-needless code that tried to aggressively flush
17778 OR connections as data was added to them. Since 0.2.0.1-alpha, our
17779 cell queue logic has saved us from the failure mode that this code
17780 was supposed to prevent. Removing this code will limit the number
17781 of baroque control flow paths through Tor's network logic. Reported
17782 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
17784 o Minor features (controller):
17785 - Add a "GETINFO signal/names" control port command. Implements
17787 - Provide default values for all options via "GETINFO config/defaults".
17788 Implements ticket 4971.
17790 o Minor features (IPv6):
17791 - New config option "AuthDirHasIPv6Connectivity 1" that directory
17792 authorities should set if they have IPv6 connectivity and want to
17793 do reachability tests for IPv6 relays. Implements feature 5974.
17794 - A relay with an IPv6 OR port now sends that address in NETINFO
17795 cells (in addition to its other address). Implements ticket 6364.
17797 o Minor features (log messages):
17798 - Omit the first heartbeat log message, because it never has anything
17799 useful to say, and it clutters up the bootstrapping messages.
17800 Resolves ticket 6758.
17801 - Don't log about reloading the microdescriptor cache at startup. Our
17802 bootstrap warnings are supposed to tell the user when there's a
17803 problem, and our bootstrap notices say when there isn't. Resolves
17804 ticket 6759; bugfix on 0.2.2.6-alpha.
17805 - Don't log "I learned some more directory information" when we're
17806 reading cached directory information. Reserve it for when new
17807 directory information arrives in response to a fetch. Resolves
17809 - Prevent rounding error in path bias counts when scaling
17810 them down, and use the correct scale factor default. Also demote
17811 some path bias related log messages down a level and make others
17812 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
17813 - We no longer warn so much when generating manpages from their
17816 o Code simplifications and refactoring:
17817 - Enhance our internal sscanf replacement so that we can eliminate
17818 the last remaining uses of the system sscanf. (Though those uses
17819 of sscanf were safe, sscanf itself is generally error prone, so
17820 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
17822 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
17823 - Move last_reachable and testing_since from routerinfo_t to node_t.
17824 Implements ticket 5529.
17825 - Add replaycache_t structure, functions and unit tests, then refactor
17826 rend_service_introduce() to be more clear to read, improve, debug,
17827 and test. Resolves bug 6177.
17828 - Finally remove support for malloc_good_size and malloc_usable_size.
17829 We had hoped that these functions would let us eke a little more
17830 memory out of our malloc implementation. Unfortunately, the only
17831 implementations that provided these functions are also ones that
17832 are already efficient about not overallocation: they never got us
17833 more than 7 or so bytes per allocation. Removing them saves us a
17834 little code complexity and a nontrivial amount of build complexity.
17836 o New requirements:
17837 - Tor maintainers now require Automake version 1.9 or later to build
17838 Tor from the Git repository. (Automake is not required when building
17839 from a source distribution.)
17842 Changes in version 0.2.3.21-rc - 2012-09-05
17843 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
17844 series. It fixes a trio of potential security bugs, fixes a bug where
17845 we were leaving some of the fast relays out of the microdescriptor
17846 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
17847 and cleans up other smaller issues.
17849 o Major bugfixes (security):
17850 - Tear down the circuit if we get an unexpected SENDME cell. Clients
17851 could use this trick to make their circuits receive cells faster
17852 than our flow control would have allowed, or to gum up the network,
17853 or possibly to do targeted memory denial-of-service attacks on
17854 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
17855 from July 2002, before the release of Tor 0.0.0. We had committed
17856 this patch previously, but we had to revert it because of bug 6271.
17857 Now that 6271 is fixed, this patch appears to work.
17858 - Reject any attempt to extend to an internal address. Without
17859 this fix, a router could be used to probe addresses on an internal
17860 network to see whether they were accepting connections. Fixes bug
17861 6710; bugfix on 0.0.8pre1.
17862 - Do not crash when comparing an address with port value 0 to an
17863 address policy. This bug could have been used to cause a remote
17864 assertion failure by or against directory authorities, or to
17865 allow some applications to crash clients. Fixes bug 6690; bugfix
17869 - Remove the upper bound on microdescriptor length. We were hitting
17870 the limit for routers with complex exit policies or family
17871 declarations, causing clients to not use them. Fixes the first
17872 piece of bug 6404; fix on 0.2.2.6-alpha.
17873 - Detect "ORPort 0" as meaning, uniformly, that we're not running
17874 as a relay. Previously, some of our code would treat the presence
17875 of any ORPort line as meaning that we should act like a relay,
17876 even though our new listener code would correctly not open any
17877 ORPorts for ORPort 0. Similar bugs in other Port options are also
17878 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
17881 - Avoid a pair of double-free and use-after-mark bugs that can
17882 occur with certain timings in canceled and re-received DNS
17883 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
17884 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
17885 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
17886 - Allow one-hop directory fetching circuits the full "circuit build
17887 timeout" period, rather than just half of it, before failing them
17888 and marking the relay down. This fix should help reduce cases where
17889 clients declare relays (or worse, bridges) unreachable because
17890 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
17891 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
17893 - Authorities no longer include any router in their microdescriptor
17894 consensuses for which they couldn't generate or agree on a
17895 microdescriptor. Fixes the second piece of bug 6404; fix on
17897 - Detect and reject attempts to specify both "FooPort" and
17898 "FooPort 0" in the same configuration domain. (It's still okay
17899 to have a FooPort in your configuration file, and use "FooPort 0"
17900 on the command line to disable it.) Fixes the second half of bug
17901 6507; bugfix on 0.2.3.3-alpha.
17902 - Make wildcarded addresses (that is, ones beginning with "*.") work
17903 when provided via the controller's MapAddress command. Previously,
17904 they were accepted, but we never actually noticed that they were
17905 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
17906 - Avoid crashing on a malformed state file where EntryGuardPathBias
17907 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
17908 - Add a (probably redundant) memory clear between iterations of
17909 the router status voting loop, to prevent future coding errors
17910 where data might leak between iterations of the loop. Resolves
17913 o Minor bugfixes (log messages):
17914 - Downgrade "set buildtimeout to low value" messages to "info"
17915 severity; they were never an actual problem, there was never
17916 anything reasonable to do about them, and they tended to spam logs
17917 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
17918 - Downgrade path-bias warning messages to "info". We'll try to get
17919 them working better in 0.2.4. Add internal circuit construction
17920 state to protect against the noisy warn message "Unexpectedly high
17921 circuit_successes". Also add some additional rate-limited notice
17922 messages to help determine the root cause of the warn. Fixes bug
17923 6475. Bugfix against 0.2.3.17-beta.
17924 - Move log message when unable to find a microdesc in a routerstatus
17925 entry to parse time. Previously we'd spam this warning every time
17926 we tried to figure out which microdescriptors to download. Fixes
17927 the third piece of bug 6404; fix on 0.2.3.18-rc.
17930 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
17931 change when the authority is deciding whether to accept a newly
17932 uploaded descriptor. Implements ticket 6423.
17933 - Add missing documentation for consensus and microdesc files.
17934 Resolves ticket 6732.
17937 Changes in version 0.2.2.38 - 2012-08-12
17938 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
17939 attack that could in theory leak path information.
17942 - Avoid an uninitialized memory read when reading a vote or consensus
17943 document that has an unrecognized flavor name. This read could
17944 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
17945 - Try to leak less information about what relays a client is
17946 choosing to a side-channel attacker. Previously, a Tor client would
17947 stop iterating through the list of available relays as soon as it
17948 had chosen one, thus finishing a little earlier when it picked
17949 a router earlier in the list. If an attacker can recover this
17950 timing information (nontrivial but not proven to be impossible),
17951 they could learn some coarse-grained information about which relays
17952 a client was picking (middle nodes in particular are likelier to
17953 be affected than exits). The timing attack might be mitigated by
17954 other factors (see bug 6537 for some discussion), but it's best
17955 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
17958 Changes in version 0.2.3.20-rc - 2012-08-05
17959 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
17960 series. It fixes a pair of code security bugs and a potential anonymity
17961 issue, updates our RPM spec files, and cleans up other smaller issues.
17964 - Avoid read-from-freed-memory and double-free bugs that could occur
17965 when a DNS request fails while launching it. Fixes bug 6480;
17966 bugfix on 0.2.0.1-alpha.
17967 - Avoid an uninitialized memory read when reading a vote or consensus
17968 document that has an unrecognized flavor name. This read could
17969 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
17970 - Try to leak less information about what relays a client is
17971 choosing to a side-channel attacker. Previously, a Tor client would
17972 stop iterating through the list of available relays as soon as it
17973 had chosen one, thus finishing a little earlier when it picked
17974 a router earlier in the list. If an attacker can recover this
17975 timing information (nontrivial but not proven to be impossible),
17976 they could learn some coarse-grained information about which relays
17977 a client was picking (middle nodes in particular are likelier to
17978 be affected than exits). The timing attack might be mitigated by
17979 other factors (see bug 6537 for some discussion), but it's best
17980 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
17983 - Try to make the warning when giving an obsolete SOCKSListenAddress
17984 a little more useful.
17985 - Terminate active server managed proxies if Tor stops being a
17986 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
17987 - Provide a better error message about possible OSX Asciidoc failure
17988 reasons. Fixes bug 6436.
17989 - Warn when Tor is configured to use accounting in a way that can
17990 link a hidden service to some other hidden service or public
17991 address. Resolves ticket 6490.
17994 - Check return value of fputs() when writing authority certificate
17995 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
17996 - Ignore ServerTransportPlugin lines when Tor is not configured as
17997 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
17998 - When disabling guards for having too high a proportion of failed
17999 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
18003 - Update our default RPM spec files to work with mock and rpmbuild
18004 on RHEL/Fedora. They have an updated set of dependencies and
18005 conflicts, a fix for an ancient typo when creating the "_tor"
18006 user, and better instructions. Thanks to Ondrej Mikle for the
18007 patch series. Fixes bug 6043.
18010 - Make it possible to set the TestingTorNetwork configuration
18011 option using AlternateDirAuthority and AlternateBridgeAuthority
18012 as an alternative to setting DirServer. Addresses ticket 6377.
18015 - Clarify the documentation for the Alternate*Authority options.
18017 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
18019 o Code simplification and refactoring:
18020 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
18021 10 lines. Also, don't nest them. Doing so in the past has
18022 led to hard-to-debug code. The new style is to use the
18023 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
18026 Changes in version 0.2.3.19-rc - 2012-07-06
18027 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
18028 series. It fixes the compile on Windows, reverts to a GeoIP database
18029 that isn't as broken, and fixes a flow control bug that has been around
18030 since the beginning of Tor.
18033 - Fix a bug handling SENDME cells on nonexistent streams that could
18034 result in bizarre window values. Report and patch contributed
18035 pseudonymously. Fixes part of bug 6271. This bug was introduced
18036 before the first Tor release, in svn commit r152.
18037 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
18038 June 2012 database, Maxmind marked many Tor relays as country "A1",
18039 which will cause risky behavior for clients that set EntryNodes
18040 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
18041 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
18042 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
18045 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
18046 bugfix on 0.2.1.10-alpha.
18049 Changes in version 0.2.3.18-rc - 2012-06-28
18050 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
18051 series. It fixes a few smaller bugs, but generally appears stable.
18052 Please test it and let us know whether it is!
18055 - Allow wildcarded mapaddress targets to be specified on the
18056 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
18057 - Make our linker option detection code more robust against linkers
18058 such as on FreeBSD 8, where a bad combination of options completes
18059 successfully but makes an unrunnable binary. Fixes bug 6173;
18060 bugfix on 0.2.3.17-beta.
18062 o Minor bugfixes (on 0.2.2.x and earlier):
18063 - Avoid a false positive in the util/threads unit test by increasing
18064 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
18065 - Replace "Sending publish request" log messages with "Launching
18066 upload", so that they no longer confusingly imply that we're
18067 sending something to a directory we might not even be connected
18068 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
18069 - Make sure to set *socket_error in all error cases in
18070 connection_connect(), so it can't produce a warning about
18071 errno being zero from errno_to_orconn_end_reason(). Bugfix on
18072 0.2.1.1-alpha; resolves ticket 6028.
18073 - Downgrade "Got a certificate, but we already have it" log messages
18074 from warning to info, except when we're a dirauth. Fixes bug 5238;
18075 bugfix on 0.2.1.7-alpha.
18076 - When checking for requested signatures on the latest consensus
18077 before serving it to a client, make sure to check the right
18078 consensus flavor. Bugfix on 0.2.2.6-alpha.
18079 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
18080 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
18082 o Minor bugfixes (on 0.2.3.x):
18083 - Make format_helper_exit_status() avoid unnecessary space padding
18084 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
18086 - Downgrade a message about cleaning the microdescriptor cache to
18087 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
18088 - Log a BUG message at severity INFO if we have a networkstatus with
18089 a missing entry for some microdescriptor. Continues on a patch
18091 - Improve the log message when a managed proxy fails to launch. Fixes
18092 bug 5099; bugfix on 0.2.3.6-alpha.
18093 - Don't do DNS lookups when parsing corrupted managed proxy protocol
18094 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
18095 - When formatting wildcarded address mappings for the controller,
18096 be sure to include "*." as appropriate. Partially fixes bug 6244;
18097 bugfix on 0.2.3.9-alpha.
18098 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
18099 Bugfix on 0.2.3.13-alpha.
18100 - Stop logging messages about running with circuit timeout learning
18101 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
18102 - Disable a spurious warning about reading on a marked and flushing
18103 connection. We shouldn't be doing that, but apparently we
18104 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
18105 - Fix a bug that stopped AllowDotExit from working on addresses
18106 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
18109 o Code simplification, refactoring, unit tests:
18110 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
18111 Libevent's notion of cached time when possible.
18112 - Remove duplicate code for invoking getrlimit() from control.c.
18113 - Add a unit test for the environment_variable_names_equal function.
18116 - Document the --defaults-torrc option, and the new (in 0.2.3)
18117 semantics for overriding, extending, and clearing lists of
18118 options. Closes bug 4748.
18121 Changes in version 0.2.3.17-beta - 2012-06-15
18122 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
18123 gets our TLS handshake back on track for being able to blend in with
18124 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
18125 with Vidalia, and otherwise continues to get us closer to a release
18129 - Enable gcc and ld hardening by default. Resolves ticket 5210.
18130 - Update TLS cipher list to match Firefox 8 and later. Resolves
18132 - Implement the client side of proposal 198: remove support for
18133 clients falsely claiming to support standard ciphersuites that
18134 they can actually provide. As of modern OpenSSL versions, it's not
18135 necessary to fake any standard ciphersuite, and doing so prevents
18136 us from using better ciphersuites in the future, since servers
18137 can't know whether an advertised ciphersuite is really supported or
18138 not. Some hosts -- notably, ones with very old versions of OpenSSL
18139 or where OpenSSL has been built with ECC disabled -- will stand
18140 out because of this change; TBB users should not be affected.
18143 - Change the default value for DynamicDHGroups (introduced in
18144 0.2.3.9-alpha) to 0. This feature can make Tor relays less
18145 identifiable by their use of the mod_ssl DH group, but at
18146 the cost of some usability (#4721) and bridge tracing (#6087)
18147 regressions. Resolves ticket 5598.
18148 - Send a CRLF at the end of each STATUS_* control protocol event. This
18149 bug tickled a bug in Vidalia which would make it freeze. Fixes
18150 bug 6094; bugfix on 0.2.3.16-alpha.
18153 - Disable writing on marked-for-close connections when they are
18154 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
18155 bug 5263; bugfix on 0.0.2pre13, where we first added a special
18156 case for flushing marked connections.
18157 - Detect SSL handshake even when the initial attempt to write the
18158 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
18159 - Change the AllowDotExit rules so they should actually work.
18160 We now enforce AllowDotExit only immediately after receiving an
18161 address via SOCKS or DNSPort: other sources are free to provide
18162 .exit addresses after the resolution occurs. Fixes bug 3940;
18163 bugfix on 0.2.2.1-alpha.
18164 - Fix a (harmless) integer overflow in cell statistics reported by
18165 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
18166 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
18167 right places and never depends on the consensus parameters or
18168 computes adaptive timeouts when it is disabled. Fixes bug 5049;
18169 bugfix on 0.2.2.14-alpha.
18170 - When building Tor on Windows with -DUNICODE (not default), ensure
18171 that error messages, filenames, and DNS server names are always
18172 NUL-terminated when we convert them to a single-byte encoding.
18173 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
18174 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
18175 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
18176 - Fix an edge case where TestingTorNetwork is set but the authorities
18177 and relays all have an uptime of zero, where the private Tor network
18178 could briefly lack support for hidden services. Fixes bug 3886;
18179 bugfix on 0.2.2.18-alpha.
18180 - Correct the manpage's descriptions for the default values of
18181 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
18183 - Fix the documentation for the --hush and --quiet command line
18184 options, which changed their behavior back in 0.2.3.3-alpha.
18185 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
18189 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
18190 more information to it, so that we can track it down in case it
18191 returns again. Mitigates bug 5235.
18192 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
18193 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
18194 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
18195 - Warn the user when HTTPProxy, but no other proxy type, is
18196 configured. This can cause surprising behavior: it doesn't send
18197 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
18198 directory traffic only. Resolves ticket 4663.
18199 - Issue a notice if a guard completes less than 40% of your circuits.
18200 Threshold is configurable by torrc option PathBiasNoticeRate and
18201 consensus parameter pb_noticepct. There is additional, off-by-
18202 default code to disable guards which fail too many circuits.
18203 Addresses ticket 5458.
18204 - Update to the June 6 2012 Maxmind GeoLite Country database.
18206 o Code simplifications and refactoring:
18207 - Remove validate_pluggable_transports_config(): its warning
18208 message is now handled by connection_or_connect().
18211 Changes in version 0.2.2.37 - 2012-06-06
18212 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
18213 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
18217 - Work around a bug in OpenSSL that broke renegotiation with TLS
18218 1.1 and TLS 1.2. Without this workaround, all attempts to speak
18219 the v2 Tor connection protocol when both sides were using OpenSSL
18220 1.0.1 would fail. Resolves ticket 6033.
18221 - When waiting for a client to renegotiate, don't allow it to add
18222 any bytes to the input buffer. This fixes a potential DoS issue.
18223 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
18224 - Fix an edge case where if we fetch or publish a hidden service
18225 descriptor, we might build a 4-hop circuit and then use that circuit
18226 for exiting afterwards -- even if the new last hop doesn't obey our
18227 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
18230 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
18231 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
18234 - Tell GCC and Clang to check for any errors in format strings passed
18235 to the tor_v*(print|scan)f functions.
18238 Changes in version 0.2.3.16-alpha - 2012-06-05
18239 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
18240 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
18241 currently). It also fixes a variety of smaller bugs and other cleanups
18242 that get us closer to a release candidate.
18244 o Major bugfixes (general):
18245 - Work around a bug in OpenSSL that broke renegotiation with TLS
18246 1.1 and TLS 1.2. Without this workaround, all attempts to speak
18247 the v2 Tor connection protocol when both sides were using OpenSSL
18248 1.0.1 would fail. Resolves ticket 6033.
18249 - When waiting for a client to renegotiate, don't allow it to add
18250 any bytes to the input buffer. This fixes a potential DoS issue.
18251 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
18252 - Pass correct OR address to managed proxies (like obfsproxy),
18253 even when ORListenAddress is used. Fixes bug 4865; bugfix on
18255 - The advertised platform of a router now includes only its operating
18256 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
18257 service pack level (for Windows) or its CPU architecture (for Unix).
18258 We also no longer include the "git-XYZ" tag in the version. Resolves
18261 o Major bugfixes (clients):
18262 - If we are unable to find any exit that supports our predicted ports,
18263 stop calling them predicted, so that we don't loop and build
18264 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
18265 which introduced predicted ports.
18266 - Fix an edge case where if we fetch or publish a hidden service
18267 descriptor, we might build a 4-hop circuit and then use that circuit
18268 for exiting afterwards -- even if the new last hop doesn't obey our
18269 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
18270 - Check at each new consensus whether our entry guards were picked
18271 long enough ago that we should rotate them. Previously, we only
18272 did this check at startup, which could lead to us holding a guard
18273 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
18274 - When fetching a bridge descriptor from a bridge authority,
18275 always do so anonymously, whether we have been able to open
18276 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
18277 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
18278 but we'll need to wait for bug 6010 before it's actually usable.
18280 o Major bugfixes (directory authorities):
18281 - When computing weight parameters, behave more robustly in the
18282 presence of a bad bwweightscale value. Previously, the authorities
18283 would crash if they agreed on a sufficiently broken weight_scale
18284 value: now, they use a reasonable default and carry on. Partial
18285 fix for 5786; bugfix on 0.2.2.17-alpha.
18286 - Check more thoroughly to prevent a rogue authority from
18287 double-voting on any consensus directory parameter. Previously,
18288 authorities would crash in this case if the total number of
18289 votes for any parameter exceeded the number of active voters,
18290 but would let it pass otherwise. Partial fix for bug 5786; bugfix
18294 - Rate-limit log messages when asked to connect anonymously to
18295 a private address. When these hit, they tended to hit fast and
18296 often. Also, don't bother trying to connect to addresses that we
18297 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
18298 reply makes us think we have been lied to, even when the address the
18299 client tried to connect to was "localhost." Resolves ticket 2822.
18300 - Allow packagers to insert an extra string in server descriptor
18301 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
18302 Resolves the rest of ticket 2988.
18303 - Raise the threshold of server descriptors needed (75%) and exit
18304 server descriptors needed (50%) before we will declare ourselves
18305 bootstrapped. This will make clients start building circuits a
18306 little later, but makes the initially constructed circuits less
18307 skewed and less in conflict with further directory fetches. Fixes
18309 - Close any connection that sends unrecognized junk before the
18310 handshake. Solves an issue noted in bug 4369.
18311 - Improve log messages about managed transports. Resolves ticket 5070.
18312 - Tag a bridge's descriptor as "never to be sent unencrypted".
18313 This shouldn't matter, since bridges don't open non-anonymous
18314 connections to the bridge authority and don't allow unencrypted
18315 directory connections from clients, but we might as well make
18316 sure. Closes bug 5139.
18317 - Expose our view of whether we have gone dormant to the controller,
18318 via a new "GETINFO dormant" value. Torbutton and other controllers
18319 can use this to avoid doing periodic requests through Tor while
18320 it's dormant (bug 4718). Fixes bug 5954.
18321 - Tell GCC and Clang to check for any errors in format strings passed
18322 to the tor_v*(print|scan)f functions.
18323 - Update to the May 1 2012 Maxmind GeoLite Country database.
18325 o Minor bugfixes (already included in 0.2.2.36):
18326 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
18327 Fixes bug 5346; bugfix on 0.0.8pre3.
18328 - Correct parsing of certain date types in parse_http_time().
18329 Without this patch, If-Modified-Since would behave
18330 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
18331 Esteban Manchado Velázques.
18332 - Make our number-parsing functions always treat too-large values
18333 as an error, even when those values exceed the width of the
18334 underlying type. Previously, if the caller provided these
18335 functions with minima or maxima set to the extreme values of the
18336 underlying integer type, these functions would return those
18337 values on overflow rather than treating overflow as an error.
18338 Fixes part of bug 5786; bugfix on 0.0.9.
18339 - If we hit the error case where routerlist_insert() replaces an
18340 existing (old) server descriptor, make sure to remove that
18341 server descriptor from the old_routers list. Fix related to bug
18342 1776. Bugfix on 0.2.2.18-alpha.
18343 - Clarify the behavior of MaxCircuitDirtiness with hidden service
18344 circuits. Fixes issue 5259.
18346 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
18347 - Prevent a null-pointer dereference when receiving a data cell
18348 for a nonexistent stream when the circuit in question has an
18349 empty deliver window. We don't believe this is triggerable,
18350 since we don't currently allow deliver windows to become empty,
18351 but the logic is tricky enough that it's better to make the code
18352 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
18353 - Fix a memory leak when trying to launch a DNS request when the
18354 network is disabled or the nameservers are unconfigurable. Fixes
18355 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
18356 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
18357 - Don't hold a Windows file handle open for every file mapping;
18358 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
18360 - Avoid O(n^2) performance characteristics when parsing a large
18361 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
18362 - Format more doubles with %f, not %lf. Patch from grarpamp to make
18363 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
18365 - Make our replacement implementation of strtok_r() compatible with
18366 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
18367 bugfix on 0.2.2.1-alpha.
18368 - Fix a NULL-pointer dereference on a badly formed
18369 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
18370 bugfix on 0.2.2.9-alpha.
18371 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
18372 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
18373 - Defensively refactor rend_mid_rendezvous() so that protocol
18374 violations and length checks happen in the beginning. Fixes
18376 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
18377 that IPv6 stuff will compile on MSVC, and compilation issues
18378 will be easier to track down. Fixes bug 5861.
18380 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
18381 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
18382 resource exhaustion, so that clients can adjust their load to
18383 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
18384 started using END_STREAM_REASON_RESOURCELIMIT.
18385 - Don't check for whether the address we're using for outbound
18386 connections has changed until after the outbound connection has
18387 completed. On Windows, getsockname() doesn't succeed until the
18388 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
18389 - If the configuration tries to set MyFamily on a bridge, refuse to
18390 do so, and warn about the security implications. Fixes bug 4657;
18391 bugfix on 0.2.0.3-alpha.
18392 - If the client fails to set a reasonable set of ciphersuites
18393 during its v2 handshake renegotiation, allow the renegotiation to
18394 continue nevertheless (i.e. send all the required certificates).
18395 Fixes bug 4591; bugfix on 0.2.0.20-rc.
18396 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
18397 option is set to 0 (which Vidalia version 0.2.16 now does when
18398 a SAVECONF attempt fails), perform other actions that SIGHUP
18399 usually causes (like reopening the logs). Fixes bug 5095; bugfix
18401 - If we fail to write a microdescriptor to the disk cache, do not
18402 continue replacing the old microdescriptor file. Fixes bug 2954;
18403 bugfix on 0.2.2.6-alpha.
18404 - Exit nodes don't need to fetch certificates for authorities that
18405 they don't recognize; only directory authorities, bridges,
18406 and caches need to do that. Fixes part of bug 2297; bugfix on
18408 - Correctly handle checking the permissions on the parent
18409 directory of a control socket in the root directory. Bug found
18410 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
18412 - When told to add a bridge with the same digest as a preexisting
18413 bridge but a different addr:port, change the addr:port as
18414 requested. Previously we would not notice the change. Fixes half
18415 of bug 5603; fix on 0.2.2.26-beta.
18416 - End AUTHCHALLENGE error messages (in the control protocol) with
18417 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
18419 o Minor bugfixes (on 0.2.3.x):
18420 - Turn an assertion (that the number of handshakes received as a
18421 server is not < 1) into a warning. Fixes bug 4873; bugfix on
18423 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
18424 we had reversed them when the answer was cached.) Fixes bug
18425 5723; bugfix on 0.2.3.1-alpha.
18426 - Work correctly on Linux systems with accept4 support advertised in
18427 their headers, but without accept4 support in the kernel. Fix
18428 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
18429 - When told to add a bridge with the same addr:port as a preexisting
18430 bridge but a different transport, change the transport as
18431 requested. Previously we would not notice the change. Fixes half
18432 of bug 5603; fix on 0.2.3.2-alpha.
18433 - Avoid a "double-reply" warning when replying to a SOCKS request
18434 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
18435 bugfix on 0.2.3.4-alpha.
18436 - Fix a bug where a bridge authority crashes if it has seen no
18437 directory requests when it's time to write statistics to disk.
18438 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
18440 - Don't try to open non-control listeners when DisableNetwork is set.
18441 Previously, we'd open all listeners, then immediately close them.
18442 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
18443 - Don't abort the managed proxy protocol if the managed proxy
18444 sends us an unrecognized line; ignore it instead. Fixes bug
18445 5910; bugfix on 0.2.3.9-alpha.
18446 - Fix a compile warning in crypto.c when compiling with clang 3.1.
18447 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
18448 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
18449 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
18450 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
18451 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
18452 - Resolve numerous small warnings and build issues with MSVC. Resolves
18455 o Documentation fixes:
18456 - Improve the manual's documentation for the NT Service command-line
18457 options. Addresses ticket 3964.
18458 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
18459 - Document the changes to the ORPort and DirPort options, and the
18460 fact that {OR/Dir}ListenAddress is now unnecessary (and
18461 therefore deprecated). Resolves ticket 5597.
18464 - Remove the torrc.bridge file: we don't use it for anything, and
18465 it had become badly desynchronized from torrc.sample. Resolves
18469 Changes in version 0.2.2.36 - 2012-05-24
18470 Tor 0.2.2.36 updates the addresses for two of the eight directory
18471 authorities, fixes some potential anonymity and security issues,
18472 and fixes several crash bugs.
18474 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
18475 known flaws, and nobody should be using them. You should upgrade. If
18476 you're using a Linux or BSD and its packages are obsolete, stop using
18477 those packages and upgrade anyway.
18479 o Directory authority changes:
18480 - Change IP address for maatuska (v3 directory authority).
18481 - Change IP address for ides (v3 directory authority), and rename
18485 - When building or running with any version of OpenSSL earlier
18486 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
18487 versions have a bug (CVE-2011-4576) in which their block cipher
18488 padding includes uninitialized data, potentially leaking sensitive
18489 information to any peer with whom they make a SSLv3 connection. Tor
18490 does not use SSL v3 by default, but a hostile client or server
18491 could force an SSLv3 connection in order to gain information that
18492 they shouldn't have been able to get. The best solution here is to
18493 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
18494 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
18495 to make sure that the bug can't happen.
18496 - Never use a bridge or a controller-supplied node as an exit, even
18497 if its exit policy allows it. Found by wanoskarnet. Fixes bug
18498 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
18499 and 0.2.0.3-alpha (for bridge-purpose descriptors).
18500 - Only build circuits if we have a sufficient threshold of the total
18501 descriptors that are marked in the consensus with the "Exit"
18502 flag. This mitigates an attack proposed by wanoskarnet, in which
18503 all of a client's bridges collude to restrict the exit nodes that
18504 the client knows about. Fixes bug 5343.
18505 - Provide controllers with a safer way to implement the cookie
18506 authentication mechanism. With the old method, if another locally
18507 running program could convince a controller that it was the Tor
18508 process, then that program could trick the controller into telling
18509 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
18510 authentication method uses a challenge-response approach to prevent
18511 this attack. Fixes bug 5185; implements proposal 193.
18514 - Avoid logging uninitialized data when unable to decode a hidden
18515 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
18516 - Avoid a client-side assertion failure when receiving an INTRODUCE2
18517 cell on a general purpose circuit. Fixes bug 5644; bugfix on
18519 - Fix builds when the path to sed, openssl, or sha1sum contains
18520 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
18522 - Correct our replacements for the timeradd() and timersub() functions
18523 on platforms that lack them (for example, Windows). The timersub()
18524 function is used when expiring circuits, while timeradd() is
18525 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
18526 bugfix on 0.2.2.24-alpha.
18527 - Fix the SOCKET_OK test that we use to tell when socket
18528 creation fails so that it works on Win64. Fixes part of bug 4533;
18529 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
18532 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
18533 Fixes bug 5346; bugfix on 0.0.8pre3.
18534 - Make our number-parsing functions always treat too-large values
18535 as an error, even when those values exceed the width of the
18536 underlying type. Previously, if the caller provided these
18537 functions with minima or maxima set to the extreme values of the
18538 underlying integer type, these functions would return those
18539 values on overflow rather than treating overflow as an error.
18540 Fixes part of bug 5786; bugfix on 0.0.9.
18541 - Older Linux kernels erroneously respond to strange nmap behavior
18542 by having accept() return successfully with a zero-length
18543 socket. When this happens, just close the connection. Previously,
18544 we would try harder to learn the remote address: but there was
18545 no such remote address to learn, and our method for trying to
18546 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
18547 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
18548 - Correct parsing of certain date types in parse_http_time().
18549 Without this patch, If-Modified-Since would behave
18550 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
18551 Esteban Manchado Velázques.
18552 - Change the BridgePassword feature (part of the "bridge community"
18553 design, which is not yet implemented) to use a time-independent
18554 comparison. The old behavior might have allowed an adversary
18555 to use timing to guess the BridgePassword value. Fixes bug 5543;
18556 bugfix on 0.2.0.14-alpha.
18557 - Detect and reject certain misformed escape sequences in
18558 configuration values. Previously, these values would cause us
18559 to crash if received in a torrc file or over an authenticated
18560 control port. Bug found by Esteban Manchado Velázquez, and
18561 independently by Robert Connolly from Matta Consulting who further
18562 noted that it allows a post-authentication heap overflow. Patch
18563 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
18564 bugfix on 0.2.0.16-alpha.
18565 - Fix a compile warning when using the --enable-openbsd-malloc
18566 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
18567 - During configure, detect when we're building with clang version
18568 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
18569 CFLAGS. clang doesn't support them yet.
18570 - When sending an HTTP/1.1 proxy request, include a Host header.
18571 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
18572 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
18573 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
18574 - If we hit the error case where routerlist_insert() replaces an
18575 existing (old) server descriptor, make sure to remove that
18576 server descriptor from the old_routers list. Fix related to bug
18577 1776. Bugfix on 0.2.2.18-alpha.
18579 o Minor bugfixes (documentation and log messages):
18580 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
18581 Fixes bug 4856; bugfix on Tor 0.0.6.
18582 - Update "ClientOnly" man page entry to explain that there isn't
18583 really any point to messing with it. Resolves ticket 5005.
18584 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
18585 directory authority option (introduced in Tor 0.2.2.34).
18586 - Downgrade the "We're missing a certificate" message from notice
18587 to info: people kept mistaking it for a real problem, whereas it
18588 is seldom the problem even when we are failing to bootstrap. Fixes
18589 bug 5067; bugfix on 0.2.0.10-alpha.
18590 - Correctly spell "connect" in a log message on failure to create a
18591 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
18592 - Clarify the behavior of MaxCircuitDirtiness with hidden service
18593 circuits. Fixes issue 5259.
18596 - Directory authorities now reject versions of Tor older than
18597 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
18598 inclusive. These versions accounted for only a small fraction of
18599 the Tor network, and have numerous known security issues. Resolves
18601 - Update to the May 1 2012 Maxmind GeoLite Country database.
18604 - When sending or relaying a RELAY_EARLY cell, we used to convert
18605 it to a RELAY cell if the connection was using the v1 link
18606 protocol. This was a workaround for older versions of Tor, which
18607 didn't handle RELAY_EARLY cells properly. Now that all supported
18608 versions can handle RELAY_EARLY cells, and now that we're enforcing
18609 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
18610 remove this workaround. Addresses bug 4786.
18613 Changes in version 0.2.3.15-alpha - 2012-04-30
18614 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
18615 the development branch build on Windows again.
18617 o Minor bugfixes (on 0.2.2.x and earlier):
18618 - Make sure that there are no unhandled pending TLS errors before
18619 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
18620 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
18621 Bugfix on 0.1.0.5-rc; fixes bug 4528.
18622 - Fix an assert that directory authorities could trigger on sighup
18623 during some configuration state transitions. We now don't treat
18624 it as a fatal error when the new descriptor we just generated in
18625 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
18626 - After we pick a directory mirror, we would refuse to use it if
18627 it's in our ExcludeExitNodes list, resulting in mysterious failures
18628 to bootstrap for people who just wanted to avoid exiting from
18629 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
18630 - When building with --enable-static-tor on OpenBSD, do not
18631 erroneously attempt to link -lrt. Fixes bug 5103.
18633 o Minor bugfixes (on 0.2.3.x):
18634 - When Tor is built with kernel headers from a recent (last few
18635 years) Linux kernel, do not fail to run on older (pre-2.6.28
18636 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
18637 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
18638 and 0.2.3.12-alpha.
18639 - Fix compilation with miniupnpc version 1.6; patch from
18640 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
18641 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
18642 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
18643 - Fix compilation on platforms without unistd.h, or where environ
18644 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
18647 - Directory authorities are now a little more lenient at accepting
18648 older router descriptors, or newer router descriptors that don't
18649 make big changes. This should help ameliorate past and future
18650 issues where routers think they have uploaded valid descriptors,
18651 but the authorities don't think so. Fix for ticket 2479.
18652 - Make the code that clients use to detect an address change be
18653 IPv6-aware, so that it won't fill clients' logs with error
18654 messages when trying to get the IPv4 address of an IPv6
18655 connection. Implements ticket 5537.
18657 o Removed features:
18658 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
18659 authorities needed to use it for a while to keep the network working
18660 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
18661 that was six months ago. As of now, it should no longer be needed
18665 Changes in version 0.2.3.14-alpha - 2012-04-23
18666 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
18667 candidate. It also dramatically speeds up AES: fast relays should
18668 consider switching to the newer OpenSSL library.
18670 o Directory authority changes:
18671 - Change IP address for ides (v3 directory authority), and rename
18675 - Avoid logging uninitialized data when unable to decode a hidden
18676 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
18677 - Avoid a client-side assertion failure when receiving an INTRODUCE2
18678 cell on a general purpose circuit. Fixes bug 5644; bugfix on
18680 - If authorities are unable to get a v2 consensus document from other
18681 directory authorities, they no longer fall back to fetching
18682 them from regular directory caches. Fixes bug 5635; bugfix on
18683 0.2.2.26-beta, where routers stopped downloading v2 consensus
18684 documents entirely.
18685 - When we start a Tor client with a normal consensus already cached,
18686 be willing to download a microdescriptor consensus. Fixes bug 4011;
18687 fix on 0.2.3.1-alpha.
18689 o Major features (performance):
18690 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
18691 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
18692 vectorized AES implementations as appropriate. These can be much,
18693 much faster than other AES implementations.
18695 o Minor bugfixes (0.2.2.x and earlier):
18696 - Don't launch more than 10 service-side introduction-point circuits
18697 for a hidden service in five minutes. Previously, we would consider
18698 launching more introduction-point circuits if at least one second
18699 had passed without any introduction-point circuits failing. Fixes
18700 bug 4607; bugfix on 0.0.7pre1.
18701 - Change the BridgePassword feature (part of the "bridge community"
18702 design, which is not yet implemented) to use a time-independent
18703 comparison. The old behavior might have allowed an adversary
18704 to use timing to guess the BridgePassword value. Fixes bug 5543;
18705 bugfix on 0.2.0.14-alpha.
18706 - Enforce correct return behavior of tor_vsscanf() when the '%%'
18707 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
18708 - When sending an HTTP/1.1 proxy request, include a Host header.
18709 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
18710 - Don't log that we have "decided to publish new relay descriptor"
18711 unless we are actually publishing a descriptor. Fixes bug 3942;
18712 bugfix on 0.2.2.28-beta.
18714 o Minor bugfixes (0.2.3.x):
18715 - Fix a bug where a bridge authority crashes (on a failed assert)
18716 if it has seen no directory requests when it's time to write
18717 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
18718 - Fix bug stomping on ORPort option NoListen and ignoring option
18719 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
18720 - In the testsuite, provide a large enough buffer in the tor_sscanf
18721 unit test. Otherwise we'd overrun that buffer and crash during
18722 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
18724 - Make sure we create the keys directory if it doesn't exist and we're
18725 about to store the dynamic Diffie-Hellman parameters. Fixes bug
18726 5572; bugfix on 0.2.3.13-alpha.
18727 - Fix a small memory leak when trying to decode incorrect base16
18728 authenticator during SAFECOOKIE authentication. Found by
18729 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
18732 - Add more information to a log statement that might help track down
18733 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
18734 non-IP address" messages (or any Bug messages, for that matter!),
18735 please let us know about it.
18736 - Relays now understand an IPv6 address when they get one from a
18737 directory server. Resolves ticket 4875.
18738 - Resolve IPv6 addresses in bridge and entry statistics to country
18739 code "??" which means we at least count them. Resolves ticket 5053;
18740 improves on 0.2.3.9-alpha.
18741 - Update to the April 3 2012 Maxmind GeoLite Country database.
18742 - Begin a doc/state-contents.txt file to explain the contents of
18743 the Tor state file. Fixes bug 2987.
18745 o Default torrc changes:
18746 - Stop listing "socksport 9050" in torrc.sample. We open a socks
18747 port on 9050 by default anyway, so this should not change anything
18749 - Stop mentioning the deprecated *ListenAddress options in
18750 torrc.sample. Fixes bug 5438.
18751 - Document unit of bandwidth related options in sample torrc.
18754 o Removed features:
18755 - The "torify" script no longer supports the "tsocks" socksifier
18756 tool, since tsocks doesn't support DNS and UDP right for Tor.
18757 Everyone should be using torsocks instead. Fixes bugs 3530 and
18758 5180. Based on a patch by "ugh".
18760 o Code refactoring:
18761 - Change the symmetric cipher interface so that creating and
18762 initializing a stream cipher are no longer separate functions.
18763 - Remove all internal support for unpadded RSA. We never used it, and
18764 it would be a bad idea to start.
18767 Changes in version 0.2.3.13-alpha - 2012-03-26
18768 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
18769 in managed pluggable transports, as well as providing other cleanups
18770 that get us closer to a release candidate.
18772 o Directory authority changes:
18773 - Change IP address for maatuska (v3 directory authority).
18776 - Provide controllers with a safer way to implement the cookie
18777 authentication mechanism. With the old method, if another locally
18778 running program could convince a controller that it was the Tor
18779 process, then that program could trick the controller into telling
18780 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
18781 authentication method uses a challenge-response approach to prevent
18782 this attack. Fixes bug 5185, implements proposal 193.
18783 - Never use a bridge or a controller-supplied node as an exit, even
18784 if its exit policy allows it. Found by wanoskarnet. Fixes bug
18785 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
18786 and 0.2.0.3-alpha (for bridge-purpose descriptors).
18787 - Only build circuits if we have a sufficient threshold of the total
18788 descriptors that are marked in the consensus with the "Exit"
18789 flag. This mitigates an attack proposed by wanoskarnet, in which
18790 all of a client's bridges collude to restrict the exit nodes that
18791 the client knows about. Fixes bug 5343.
18793 o Major bugfixes (on Tor 0.2.3.x):
18794 - Avoid an assert when managed proxies like obfsproxy are configured,
18795 and we receive HUP signals or setconf attempts too rapidly. This
18796 situation happens most commonly when Vidalia tries to attach to
18797 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
18798 bugfix on 0.2.3.6-alpha.
18799 - Fix a relay-side pluggable transports bug where managed proxies were
18800 unreachable from the Internet, because Tor asked them to bind on
18801 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
18802 - Stop discarding command-line arguments when TestingTorNetwork
18803 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
18804 0.2.3.9-alpha, where task 4552 added support for two layers of
18806 - Resume allowing the unit tests to run in gdb. This was accidentally
18807 made impossible when the DisableDebuggerAttachment option was
18808 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
18809 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
18810 0.2.3.11-alpha. Reported by Anthony G. Basile.
18812 o Minor bugfixes (on 0.2.2.x and earlier):
18813 - Ensure we don't cannibalize circuits that are longer than three hops
18814 already, so we don't end up making circuits with 5 or more
18815 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
18816 0.1.0.1-rc which introduced cannibalization.
18817 - Detect and reject certain misformed escape sequences in
18818 configuration values. Previously, these values would cause us
18819 to crash if received in a torrc file or over an authenticated
18820 control port. Bug found by Esteban Manchado Velázquez, and
18821 independently by Robert Connolly from Matta Consulting who further
18822 noted that it allows a post-authentication heap overflow. Patch
18823 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
18824 bugfix on 0.2.0.16-alpha.
18825 - Fix a compile warning when using the --enable-openbsd-malloc
18826 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
18827 - Directory caches no longer refuse to clean out descriptors because
18828 of missing v2 networkstatus documents, unless they're configured
18829 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
18830 0.2.2.26-beta. Patch by Daniel Bryg.
18831 - Update to the latest version of the tinytest unit testing framework.
18832 This includes a couple of bugfixes that can be relevant for
18833 running forked unit tests on Windows, and removes all reserved
18836 o Minor bugfixes (on 0.2.3.x):
18837 - On a failed pipe() call, don't leak file descriptors. Fixes bug
18838 4296; bugfix on 0.2.3.1-alpha.
18839 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
18840 until after we have received a CERTS cell. Fixes bug 4361; bugfix
18841 on 0.2.3.6-alpha. Patch by "frosty".
18842 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
18843 option, so that the IP stack doesn't decide to use it for IPv4
18844 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
18845 - Ensure that variables set in Tor's environment cannot override
18846 environment variables that Tor passes to a managed
18847 pluggable-transport proxy. Previously, Tor would pass every
18848 variable in its environment to managed proxies along with the new
18849 ones, in such a way that on many operating systems, the inherited
18850 environment variables would override those which Tor tried to
18851 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
18852 bugfix on 0.2.3.9-alpha for Windows.
18855 - A wide variety of new unit tests by Esteban Manchado Velázquez.
18856 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
18857 - Update to the March 6 2012 Maxmind GeoLite Country database.
18860 Changes in version 0.2.3.12-alpha - 2012-02-13
18861 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
18862 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
18863 when Tor is configured to use a pluggable transport like obfsproxy.
18866 - Fix builds when the path to sed, openssl, or sha1sum contains
18867 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
18869 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
18870 connections. This change should allow busy exit relays to stop
18871 running out of available sockets as quickly. Fixes bug 4950;
18872 bugfix on 0.2.2.26-beta.
18873 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
18874 would ask the bridge for microdescriptors, which are only supported
18875 in 0.2.3.x, and then fail to bootstrap when it didn't get the
18876 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
18877 - Properly set up obfsproxy's environment when in managed mode. The
18878 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
18879 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
18880 5076 and 5082; bugfix on 0.2.3.6-alpha.
18883 - Use the dead_strip option when building Tor on OS X. This reduces
18884 binary size by almost 19% when linking openssl and libevent
18885 statically, which we do for Tor Browser Bundle.
18886 - Fix broken URLs in the sample torrc file, and tell readers about
18887 the OutboundBindAddress, ExitPolicyRejectPrivate, and
18888 PublishServerDescriptor options. Addresses bug 4652.
18889 - Update to the February 7 2012 Maxmind GeoLite Country database.
18892 - Downgrade the "We're missing a certificate" message from notice
18893 to info: people kept mistaking it for a real problem, whereas it
18894 is seldom the problem even when we are failing to bootstrap. Fixes
18895 bug 5067; bugfix on 0.2.0.10-alpha.
18896 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
18897 managed pluggable transport server proxy's environment.
18898 Previously, we would put it there, even though Tor doesn't
18899 implement an 'extended server port' yet, and even though Tor
18900 almost certainly isn't listening at that address. For now, we set
18901 it to an empty string to avoid crashing older obfsproxies. Bugfix
18903 - Log the heartbeat message every HeartbeatPeriod seconds, not every
18904 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
18905 0.2.3.1-alpha. Bug reported by Scott Bennett.
18906 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
18907 bugfix on 0.2.3.11-alpha.
18908 - Update "ClientOnly" man page entry to explain that there isn't
18909 really any point to messing with it. Resolves ticket 5005.
18910 - Use the correct CVE number for CVE-2011-4576 in our comments and
18911 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
18914 o Code simplifications and refactoring:
18915 - Use the _WIN32 macro throughout our code to detect Windows.
18916 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
18920 Changes in version 0.2.3.11-alpha - 2012-01-22
18921 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
18922 the last step of the plan to limit maximum circuit length, includes
18923 a wide variety of hidden service performance and correctness fixes,
18924 works around an OpenSSL security flaw if your distro is too stubborn
18925 to upgrade, and fixes a bunch of smaller issues.
18928 - Now that Tor 0.2.0.x is completely deprecated, enable the final
18929 part of "Proposal 110: Avoiding infinite length circuits" by
18930 refusing all circuit-extend requests that do not use a relay_early
18931 cell. This change helps Tor resist a class of denial-of-service
18932 attacks by limiting the maximum circuit length.
18933 - Adjust the number of introduction points that a hidden service
18934 will try to maintain based on how long its introduction points
18935 remain in use and how many introductions they handle. Fixes
18937 - Try to use system facilities for enumerating local interface
18938 addresses, before falling back to our old approach (which was
18939 binding a UDP socket, and calling getsockname() on it). That
18940 approach was scaring OS X users whose draconian firewall
18941 software warned about binding to UDP sockets, regardless of
18942 whether packets were sent. Now we try to use getifaddrs(),
18943 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
18944 system supports. Resolves ticket 1827.
18946 o Major security workaround:
18947 - When building or running with any version of OpenSSL earlier
18948 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
18949 versions have a bug (CVE-2011-4576) in which their block cipher
18950 padding includes uninitialized data, potentially leaking sensitive
18951 information to any peer with whom they make a SSLv3 connection. Tor
18952 does not use SSL v3 by default, but a hostile client or server
18953 could force an SSLv3 connection in order to gain information that
18954 they shouldn't have been able to get. The best solution here is to
18955 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
18956 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
18957 to make sure that the bug can't happen.
18960 - Fix the SOCKET_OK test that we use to tell when socket
18961 creation fails so that it works on Win64. Fixes part of bug 4533;
18962 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
18963 - Correct our replacements for the timeradd() and timersub() functions
18964 on platforms that lack them (for example, Windows). The timersub()
18965 function is used when expiring circuits, while timeradd() is
18966 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
18967 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
18968 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
18969 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
18970 bug at runtime, not compile time, because some distributions hack
18971 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
18972 on 0.2.3.9-alpha. Found by Pascal.
18974 o Minor features (controller):
18975 - Use absolute path names when reporting the torrc filename in the
18976 control protocol, so a controller can more easily find the torrc
18977 file. Resolves bug 1101.
18978 - Extend the control protocol to report flags that control a circuit's
18979 path selection in CIRC events and in replies to 'GETINFO
18980 circuit-status'. Implements part of ticket 2411.
18981 - Extend the control protocol to report the hidden service address
18982 and current state of a hidden-service-related circuit in CIRC
18983 events and in replies to 'GETINFO circuit-status'. Implements part
18985 - When reporting the path to the cookie file to the controller,
18986 give an absolute path. Resolves ticket 4881.
18987 - Allow controllers to request an event notification whenever a
18988 circuit is cannibalized or its purpose is changed. Implements
18989 part of ticket 3457.
18990 - Include the creation time of a circuit in CIRC and CIRC2
18991 control-port events and the list produced by the 'GETINFO
18992 circuit-status' control-port command.
18994 o Minor features (directory authorities):
18995 - Directory authorities now reject versions of Tor older than
18996 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
18997 inclusive. These versions accounted for only a small fraction of
18998 the Tor network, and have numerous known security issues. Resolves
19000 - Authority operators can now vote for all relays in a given
19001 set of countries to be BadDir/BadExit/Invalid/Rejected.
19002 - Provide two consensus parameters (FastFlagMinThreshold and
19003 FastFlagMaxThreshold) to control the range of allowable bandwidths
19004 for the Fast directory flag. These allow authorities to run
19005 experiments on appropriate requirements for being a "Fast" node.
19006 The AuthDirFastGuarantee config value still applies. Implements
19008 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19009 directory authority option (introduced in Tor 0.2.2.34).
19011 o Minor features (other):
19012 - Don't disable the DirPort when we cannot exceed our AccountingMax
19013 limit during this interval because the effective bandwidthrate is
19014 low enough. This is useful in a situation where AccountMax is only
19015 used as an additional safeguard or to provide statistics.
19016 - Prepend an informative header to generated dynamic_dh_params files.
19017 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
19018 EntryNodes will have no effect. Resolves issue 2571.
19019 - Log more useful messages when we fail to disable debugger
19021 - Log which authority we're missing votes from when we go to fetch
19022 them from the other auths.
19023 - Log (at debug level) whenever a circuit's purpose is changed.
19024 - Add missing documentation for the MaxClientCircuitsPending,
19025 UseMicrodescriptors, UserspaceIOCPBuffers, and
19026 _UseFilteringSSLBufferevents options, all introduced during
19027 the 0.2.3.x series.
19028 - Update to the January 3 2012 Maxmind GeoLite Country database.
19030 o Minor bugfixes (hidden services):
19031 - Don't close hidden service client circuits which have almost
19032 finished connecting to their destination when they reach
19033 the normal circuit-build timeout. Previously, we would close
19034 introduction circuits which are waiting for an acknowledgement
19035 from the introduction point, and rendezvous circuits which have
19036 been specified in an INTRODUCE1 cell sent to a hidden service,
19037 after the normal CBT. Now, we mark them as 'timed out', and launch
19038 another rendezvous attempt in parallel. This behavior change can
19039 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
19040 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
19041 - Don't close hidden-service-side rendezvous circuits when they
19042 reach the normal circuit-build timeout. This behavior change can
19043 be disabled using the new
19044 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
19045 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
19046 - Make sure we never mark the wrong rendezvous circuit as having
19047 had its introduction cell acknowledged by the introduction-point
19048 relay. Previously, when we received an INTRODUCE_ACK cell on a
19049 client-side hidden-service introduction circuit, we might have
19050 marked a rendezvous circuit other than the one we specified in
19051 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
19052 a warning message and interfered with the hidden service
19053 connection-establishment process. Fixes bug 4759; bugfix on
19054 0.2.3.3-alpha, when we added the stream-isolation feature which
19055 might cause Tor to open multiple rendezvous circuits for the same
19057 - Don't trigger an assertion failure when we mark a new client-side
19058 hidden-service introduction circuit for close during the process
19059 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
19062 o Minor bugfixes (log messages):
19063 - Correctly spell "connect" in a log message on failure to create a
19064 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
19066 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19067 Fixes bug 4856; bugfix on Tor 0.0.6.
19068 - Fix the log message describing how we work around discovering
19069 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
19070 4837; bugfix on 0.2.2.9-alpha.
19071 - When logging about a disallowed .exit name, do not also call it
19072 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
19074 o Minor bugfixes (build fixes):
19075 - During configure, detect when we're building with clang version
19076 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19077 CFLAGS. clang doesn't support them yet.
19078 - During configure, search for library containing cos function as
19079 libm lives in libcore on some platforms (BeOS/Haiku). Linking
19080 against libm was hard-coded before. Fixes the first part of bug
19081 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
19083 - Detect attempts to build Tor on (as yet hypothetical) versions
19084 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
19085 fix for bug 4533. Bugfix on 0.2.2.28-beta.
19086 - Preprocessor directives should not be put inside the arguments
19087 of a macro. This would break compilation with GCC releases prior
19088 to version 3.3. We would never recommend such an old GCC version,
19089 but it is apparently required for binary compatibility on some
19090 platforms (namely, certain builds of Haiku). Fixes the other part
19091 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
19094 o Minor bugfixes (other):
19095 - Older Linux kernels erroneously respond to strange nmap behavior
19096 by having accept() return successfully with a zero-length
19097 socket. When this happens, just close the connection. Previously,
19098 we would try harder to learn the remote address: but there was
19099 no such remote address to learn, and our method for trying to
19100 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19101 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19102 - Fix null-pointer access that could occur if TLS allocation failed.
19103 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
19104 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
19105 accidentally been reverted.
19106 - Fix our implementation of crypto_random_hostname() so it can't
19107 overflow on ridiculously large inputs. (No Tor version has ever
19108 provided this kind of bad inputs, but let's be correct in depth.)
19109 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
19110 - Find more places in the code that should have been testing for
19111 invalid sockets using the SOCKET_OK macro. Required for a fix
19112 for bug 4533. Bugfix on 0.2.2.28-beta.
19113 - Fix an assertion failure when, while running with bufferevents, a
19114 connection finishes connecting after it is marked for close, but
19115 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
19116 - test_util_spawn_background_ok() hardcoded the expected value
19117 for ENOENT to 2. This isn't portable as error numbers are
19118 platform specific, and particularly the hurd has ENOENT at
19119 0x40000002. Construct expected string at runtime, using the correct
19120 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
19121 - Reject attempts to disable DisableDebuggerAttachment while Tor is
19122 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
19123 - Use an appropriate-width type for sockets in tor-fw-helper on
19124 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
19127 - When sending or relaying a RELAY_EARLY cell, we used to convert
19128 it to a RELAY cell if the connection was using the v1 link
19129 protocol. This was a workaround for older versions of Tor, which
19130 didn't handle RELAY_EARLY cells properly. Now that all supported
19131 versions can handle RELAY_EARLY cells, and now that we're enforcing
19132 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19133 remove this workaround. Addresses bug 4786.
19135 o Code simplifications and refactoring:
19136 - Use OpenSSL's built-in SSL_state_string_long() instead of our
19137 own homebrewed ssl_state_to_string() replacement. Patch from
19138 Emile Snyder. Fixes bug 4653.
19139 - Use macros to indicate OpenSSL versions, so we don't need to worry
19140 about accidental hexadecimal bit shifts.
19141 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
19143 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
19144 - Use the smartlist_add_asprintf() alias more consistently.
19145 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
19146 invalid value, rather than just -1.
19147 - Rename a handful of old identifiers, mostly related to crypto
19148 structures and crypto functions. By convention, our "create an
19149 object" functions are called "type_new()", our "free an object"
19150 functions are called "type_free()", and our types indicate that
19151 they are types only with a final "_t". But a handful of older
19152 types and functions broke these rules, with function names like
19153 "type_create" or "subsystem_op_type", or with type names like
19157 Changes in version 0.2.3.10-alpha - 2011-12-16
19158 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
19159 Tor's buffers code. Absolutely everybody should upgrade.
19161 The bug relied on an incorrect calculation when making data continuous
19162 in one of our IO buffers, if the first chunk of the buffer was
19163 misaligned by just the wrong amount. The miscalculation would allow an
19164 attacker to overflow a piece of heap-allocated memory. To mount this
19165 attack, the attacker would need to either open a SOCKS connection to
19166 Tor's SocksPort (usually restricted to localhost), or target a Tor
19167 instance configured to make its connections through a SOCKS proxy
19168 (which Tor does not do by default).
19170 Good security practice requires that all heap-overflow bugs should be
19171 presumed to be exploitable until proven otherwise, so we are treating
19172 this as a potential code execution attack. Please upgrade immediately!
19173 This bug does not affect bufferevents-based builds of Tor. Special
19174 thanks to "Vektor" for reporting this issue to us!
19176 This release also contains a few minor bugfixes for issues discovered
19180 - Fix a heap overflow bug that could occur when trying to pull
19181 data into the first chunk of a buffer, when that chunk had
19182 already had some data drained from it. Fixes CVE-2011-2778;
19183 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19186 - If we can't attach streams to a rendezvous circuit when we
19187 finish connecting to a hidden service, clear the rendezvous
19188 circuit's stream-isolation state and try to attach streams
19189 again. Previously, we cleared rendezvous circuits' isolation
19190 state either too early (if they were freshly built) or not at all
19191 (if they had been built earlier and were cannibalized). Bugfix on
19192 0.2.3.3-alpha; fixes bug 4655.
19193 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
19194 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
19195 - Fix an assertion failure when a relay with accounting enabled
19196 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
19199 - Update to the December 6 2011 Maxmind GeoLite Country database.
19202 Changes in version 0.2.2.35 - 2011-12-16
19203 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
19204 buffers code. Absolutely everybody should upgrade.
19206 The bug relied on an incorrect calculation when making data continuous
19207 in one of our IO buffers, if the first chunk of the buffer was
19208 misaligned by just the wrong amount. The miscalculation would allow an
19209 attacker to overflow a piece of heap-allocated memory. To mount this
19210 attack, the attacker would need to either open a SOCKS connection to
19211 Tor's SocksPort (usually restricted to localhost), or target a Tor
19212 instance configured to make its connections through a SOCKS proxy
19213 (which Tor does not do by default).
19215 Good security practice requires that all heap-overflow bugs should be
19216 presumed to be exploitable until proven otherwise, so we are treating
19217 this as a potential code execution attack. Please upgrade immediately!
19218 This bug does not affect bufferevents-based builds of Tor. Special
19219 thanks to "Vektor" for reporting this issue to us!
19221 Tor 0.2.2.35 also fixes several bugs in previous versions, including
19222 crash bugs for unusual configurations, and a long-term bug that
19223 would prevent Tor from starting on Windows machines with draconian
19226 With this release, we remind everyone that 0.2.0.x has reached its
19227 formal end-of-life. Those Tor versions have many known flaws, and
19228 nobody should be using them. You should upgrade -- ideally to the
19229 0.2.2.x series. If you're using a Linux or BSD and its packages are
19230 obsolete, stop using those packages and upgrade anyway.
19232 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
19233 longer receive support after some time in early 2012.
19236 - Fix a heap overflow bug that could occur when trying to pull
19237 data into the first chunk of a buffer, when that chunk had
19238 already had some data drained from it. Fixes CVE-2011-2778;
19239 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19240 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
19241 that it doesn't attempt to allocate a socketpair. This could cause
19242 some problems on Windows systems with overzealous firewalls. Fix for
19243 bug 4457; workaround for Libevent versions 2.0.1-alpha through
19245 - If we mark an OR connection for close based on a cell we process,
19246 don't process any further cells on it. We already avoid further
19247 reads on marked-for-close connections, but now we also discard the
19248 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
19249 which was the first version where we might mark a connection for
19250 close based on processing a cell on it.
19251 - Correctly sanity-check that we don't underflow on a memory
19252 allocation (and then assert) for hidden service introduction
19253 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19254 bugfix on 0.2.1.5-alpha.
19255 - Fix a memory leak when we check whether a hidden service
19256 descriptor has any usable introduction points left. Fixes bug
19257 4424. Bugfix on 0.2.2.25-alpha.
19258 - Don't crash when we're running as a relay and don't have a GeoIP
19259 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
19260 we've had in the 0.2.3.x branch already.
19261 - When running as a client, do not print a misleading (and plain
19262 wrong) log message that we're collecting "directory request"
19263 statistics: clients don't collect statistics. Also don't create a
19264 useless (because empty) stats file in the stats/ directory. Fixes
19265 bug 4353; bugfix on 0.2.2.34.
19268 - Detect failure to initialize Libevent. This fix provides better
19269 detection for future instances of bug 4457.
19270 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
19271 function. This was eating up hideously large amounts of time on some
19272 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
19273 - Resolve an integer overflow bug in smartlist_ensure_capacity().
19274 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
19276 - Don't warn about unused log_mutex in log.c when building with
19277 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
19278 0.1.0.6-rc which introduced --disable-threads.
19279 - When configuring, starting, or stopping an NT service, stop
19280 immediately after the service configuration attempt has succeeded
19281 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
19282 - When sending a NETINFO cell, include the original address
19283 received for the other side, not its canonical address. Found
19284 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
19285 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
19286 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
19287 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
19288 occurred when a client tried to fetch a descriptor for a bridge
19289 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
19290 - Backport fixes for a pair of compilation warnings on Windows.
19291 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
19292 - If we had ever tried to call tor_addr_to_str on an address of
19293 unknown type, we would have done a strdup on an uninitialized
19294 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
19295 Reported by "troll_un".
19296 - Correctly detect and handle transient lookup failures from
19297 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
19298 Reported by "troll_un".
19299 - Fix null-pointer access that could occur if TLS allocation failed.
19300 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
19301 - Use tor_socket_t type for listener argument to accept(). Fixes bug
19302 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
19305 - Add two new config options for directory authorities:
19306 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
19307 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
19308 that is always sufficient to satisfy the bandwidth requirement for
19309 the Guard flag. Now it will be easier for researchers to simulate
19310 Tor networks with different values. Resolves ticket 4484.
19311 - When Tor ignores a hidden service specified in its configuration,
19312 include the hidden service's directory in the warning message.
19313 Previously, we would only tell the user that some hidden service
19314 was ignored. Bugfix on 0.0.6; fixes bug 4426.
19315 - Update to the December 6 2011 Maxmind GeoLite Country database.
19317 o Packaging changes:
19318 - Make it easier to automate expert package builds on Windows,
19319 by removing an absolute path from makensis.exe command.
19322 Changes in version 0.2.1.32 - 2011-12-16
19323 Tor 0.2.1.32 backports important security and privacy fixes for
19324 oldstable. This release is intended only for package maintainers and
19325 others who cannot use the 0.2.2 stable series. All others should be
19326 using Tor 0.2.2.x or newer.
19328 The Tor 0.2.1.x series will reach formal end-of-life some time in
19329 early 2012; we will stop releasing patches for it then.
19331 o Major bugfixes (also included in 0.2.2.x):
19332 - Correctly sanity-check that we don't underflow on a memory
19333 allocation (and then assert) for hidden service introduction
19334 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19335 bugfix on 0.2.1.5-alpha.
19336 - Fix a heap overflow bug that could occur when trying to pull
19337 data into the first chunk of a buffer, when that chunk had
19338 already had some data drained from it. Fixes CVE-2011-2778;
19339 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19342 - Update to the December 6 2011 Maxmind GeoLite Country database.
19345 Changes in version 0.2.3.9-alpha - 2011-12-08
19346 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
19347 a "DisableNetwork" security feature that bundles can use to avoid
19348 touching the network until bridges are configured, moves forward on
19349 the pluggable transport design, fixes a flaw in the hidden service
19350 design that unnecessarily prevented clients with wrong clocks from
19351 reaching hidden services, and fixes a wide variety of other issues.
19354 - Clients can now connect to private bridges over IPv6. Bridges
19355 still need at least one IPv4 address in order to connect to
19356 other relays. Note that we don't yet handle the case where the
19357 user has two bridge lines for the same bridge (one IPv4, one
19358 IPv6). Implements parts of proposal 186.
19359 - New "DisableNetwork" config option to prevent Tor from launching any
19360 connections or accepting any connections except on a control port.
19361 Bundles and controllers can set this option before letting Tor talk
19362 to the rest of the network, for example to prevent any connections
19363 to a non-bridge address. Packages like Orbot can also use this
19364 option to instruct Tor to save power when the network is off.
19365 - Clients and bridges can now be configured to use a separate
19366 "transport" proxy. This approach makes the censorship arms race
19367 easier by allowing bridges to use protocol obfuscation plugins. It
19368 implements the "managed proxy" part of proposal 180 (ticket 3472).
19369 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
19370 implementation. It makes AES_CTR about 7% faster than our old one
19371 (which was about 10% faster than the one OpenSSL used to provide).
19372 Resolves ticket 4526.
19373 - Add a "tor2web mode" for clients that want to connect to hidden
19374 services non-anonymously (and possibly more quickly). As a safety
19375 measure to try to keep users from turning this on without knowing
19376 what they are doing, tor2web mode must be explicitly enabled at
19377 compile time, and a copy of Tor compiled to run in tor2web mode
19378 cannot be used as a normal Tor client. Implements feature 2553.
19379 - Add experimental support for running on Windows with IOCP and no
19380 kernel-space socket buffers. This feature is controlled by a new
19381 "UserspaceIOCPBuffers" config option (off by default), which has
19382 no effect unless Tor has been built with support for bufferevents,
19383 is running on Windows, and has enabled IOCP. This may, in the long
19384 run, help solve or mitigate bug 98.
19385 - Use a more secure consensus parameter voting algorithm. Now at
19386 least three directory authorities or a majority of them must
19387 vote on a given parameter before it will be included in the
19388 consensus. Implements proposal 178.
19391 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
19392 They used to check that the timestamp was within 30 minutes
19393 of their system clock, so they could cap the size of their
19394 replay-detection cache, but that approach unnecessarily refused
19395 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
19396 the v3 intro-point protocol (the first one which sent a timestamp
19397 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
19398 - Only use the EVP interface when AES acceleration is enabled,
19399 to avoid a 5-7% performance regression. Resolves issue 4525;
19400 bugfix on 0.2.3.8-alpha.
19402 o Privacy/anonymity features (bridge detection):
19403 - Make bridge SSL certificates a bit more stealthy by using random
19404 serial numbers, in the same fashion as OpenSSL when generating
19405 self-signed certificates. Implements ticket 4584.
19406 - Introduce a new config option "DynamicDHGroups", enabled by
19407 default, which provides each bridge with a unique prime DH modulus
19408 to be used during SSL handshakes. This option attempts to help
19409 against censors who might use the Apache DH modulus as a static
19410 identifier for bridges. Addresses ticket 4548.
19412 o Minor features (new/different config options):
19413 - New configuration option "DisableDebuggerAttachment" (on by default)
19414 to prevent basic debugging attachment attempts by other processes.
19415 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
19416 - Allow MapAddress directives to specify matches against super-domains,
19417 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
19418 Implements issue 933.
19419 - Slightly change behavior of "list" options (that is, config
19420 options that can appear more than once) when they appear both in
19421 torrc and on the command line. Previously, the command-line options
19422 would be appended to the ones from torrc. Now, the command-line
19423 options override the torrc options entirely. This new behavior
19424 allows the user to override list options (like exit policies and
19425 ports to listen on) from the command line, rather than simply
19426 appending to the list.
19427 - You can get the old (appending) command-line behavior for "list"
19428 options by prefixing the option name with a "+".
19429 - You can remove all the values for a "list" option from the command
19430 line without adding any new ones by prefixing the option name
19432 - Add experimental support for a "defaults" torrc file to be parsed
19433 before the regular torrc. Torrc options override the defaults file's
19434 options in the same way that the command line overrides the torrc.
19435 The SAVECONF controller command saves only those options which
19436 differ between the current configuration and the defaults file. HUP
19437 reloads both files. (Note: This is an experimental feature; its
19438 behavior will probably be refined in future 0.2.3.x-alpha versions
19439 to better meet packagers' needs.) Implements task 4552.
19442 - Try to make the introductory warning message that Tor prints on
19443 startup more useful for actually finding help and information.
19444 Resolves ticket 2474.
19445 - Running "make version" now displays the version of Tor that
19446 we're about to build. Idea from katmagic; resolves issue 4400.
19447 - Expire old or over-used hidden service introduction points.
19448 Required by fix for bug 3460.
19449 - Move the replay-detection cache for the RSA-encrypted parts of
19450 INTRODUCE2 cells to the introduction point data structures.
19451 Previously, we would use one replay-detection cache per hidden
19452 service. Required by fix for bug 3460.
19453 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
19454 public key replay-detection cache from 60 minutes to 5 minutes. This
19455 replay-detection cache is now used only to detect multiple
19456 INTRODUCE2 cells specifying the same rendezvous point, so we can
19457 avoid launching multiple simultaneous attempts to connect to it.
19459 o Minor bugfixes (on Tor 0.2.2.x and earlier):
19460 - Resolve an integer overflow bug in smartlist_ensure_capacity().
19461 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
19463 - Fix a minor formatting issue in one of tor-gencert's error messages.
19465 - Prevent a false positive from the check-spaces script, by disabling
19466 the "whitespace between function name and (" check for functions
19468 - Fix a log message suggesting that people contact a non-existent
19469 email address. Fixes bug 3448.
19470 - Fix null-pointer access that could occur if TLS allocation failed.
19471 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
19472 - Report a real bootstrap problem to the controller on router
19473 identity mismatch. Previously we just said "foo", which probably
19474 made a lot of sense at the time. Fixes bug 4169; bugfix on
19476 - If we had ever tried to call tor_addr_to_str() on an address of
19477 unknown type, we would have done a strdup() on an uninitialized
19478 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
19479 Reported by "troll_un".
19480 - Correctly detect and handle transient lookup failures from
19481 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
19482 Reported by "troll_un".
19483 - Use tor_socket_t type for listener argument to accept(). Fixes bug
19484 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
19485 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
19486 bug 4532; found by "troll_un".
19488 o Minor bugfixes (on Tor 0.2.3.x):
19489 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
19491 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
19492 circuit for use as a hidden service client's rendezvous point.
19493 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
19494 with help from wanoskarnet.
19495 - Restore behavior of overriding SocksPort, ORPort, and similar
19496 options from the command line. Bugfix on 0.2.3.3-alpha.
19499 - Properly handle the case where the build-tree is not the same
19500 as the source tree when generating src/common/common_sha1.i,
19501 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
19502 bugfix on 0.2.0.1-alpha.
19504 o Code simplifications, cleanups, and refactorings:
19505 - Remove the pure attribute from all functions that used it
19506 previously. In many cases we assigned it incorrectly, because the
19507 functions might assert or call impure functions, and we don't have
19508 evidence that keeping the pure attribute is worthwhile. Implements
19509 changes suggested in ticket 4421.
19510 - Remove some dead code spotted by coverity. Fixes cid 432.
19511 Bugfix on 0.2.3.1-alpha, closes bug 4637.
19514 Changes in version 0.2.3.8-alpha - 2011-11-22
19515 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
19516 socketpair-related bug that has been bothering Windows users. It adds
19517 support to serve microdescriptors to controllers, so Vidalia's network
19518 map can resume listing relays (once Vidalia implements its side),
19519 and adds better support for hardware AES acceleration. Finally, it
19520 starts the process of adjusting the bandwidth cutoff for getting the
19521 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
19522 that tiny relays harm performance more than they help network capacity.
19525 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
19526 that it doesn't attempt to allocate a socketpair. This could cause
19527 some problems on Windows systems with overzealous firewalls. Fix for
19528 bug 4457; workaround for Libevent versions 2.0.1-alpha through
19530 - Correctly sanity-check that we don't underflow on a memory
19531 allocation (and then assert) for hidden service introduction
19532 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
19533 bugfix on 0.2.1.5-alpha.
19534 - Remove the artificially low cutoff of 20KB to guarantee the Fast
19535 flag. In the past few years the average relay speed has picked
19536 up, and while the "top 7/8 of the network get the Fast flag" and
19537 "all relays with 20KB or more of capacity get the Fast flag" rules
19538 used to have the same result, now the top 7/8 of the network has
19539 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
19540 - Fix a rare assertion failure when checking whether a v0 hidden
19541 service descriptor has any usable introduction points left, and
19542 we don't have enough information to build a circuit to the first
19543 intro point named in the descriptor. The HS client code in
19544 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
19545 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
19546 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
19547 - Make bridge authorities not crash when they are asked for their own
19548 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
19549 - When running as a client, do not print a misleading (and plain
19550 wrong) log message that we're collecting "directory request"
19551 statistics: clients don't collect statistics. Also don't create a
19552 useless (because empty) stats file in the stats/ directory. Fixes
19553 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
19556 - Allow Tor controllers like Vidalia to obtain the microdescriptor
19557 for a relay by identity digest or nickname. Previously,
19558 microdescriptors were only available by their own digests, so a
19559 controller would have to ask for and parse the whole microdescriptor
19560 consensus in order to look up a single relay's microdesc. Fixes
19561 bug 3832; bugfix on 0.2.3.1-alpha.
19562 - Use OpenSSL's EVP interface for AES encryption, so that all AES
19563 operations can use hardware acceleration (if present). Resolves
19566 o Minor bugfixes (on 0.2.2.x and earlier):
19567 - Detect failure to initialize Libevent. This fix provides better
19568 detection for future instances of bug 4457.
19569 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
19570 function. This was eating up hideously large amounts of time on some
19571 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
19572 - Don't warn about unused log_mutex in log.c when building with
19573 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
19574 0.1.0.6-rc which introduced --disable-threads.
19575 - Allow manual 'authenticate' commands to the controller interface
19576 from netcat (nc) as well as telnet. We were rejecting them because
19577 they didn't come with the expected whitespace at the end of the
19578 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
19579 - Fix some (not actually triggerable) buffer size checks in usage of
19580 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
19582 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
19583 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
19584 - When configuring, starting, or stopping an NT service, stop
19585 immediately after the service configuration attempt has succeeded
19586 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
19587 - When sending a NETINFO cell, include the original address
19588 received for the other side, not its canonical address. Found
19589 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
19590 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
19591 can pick them up when the tests aren't disabled. Bugfix on
19592 0.2.2.4-alpha which introduced tinytest.
19593 - Fix a memory leak when we check whether a hidden service
19594 descriptor has any usable introduction points left. Fixes bug
19595 4424. Bugfix on 0.2.2.25-alpha.
19596 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
19597 occurred when a client tried to fetch a descriptor for a bridge
19598 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
19600 o Minor bugfixes (on 0.2.3.x):
19601 - Make util unit tests build correctly with MSVC. Bugfix on
19602 0.2.3.3-alpha. Patch by Gisle Vanem.
19603 - Successfully detect AUTH_CHALLENGE cells with no recognized
19604 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
19605 Found by frosty_un.
19606 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
19607 it should still send a NETINFO cell to allow the connection to
19608 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
19610 - Log less loudly when we get an invalid authentication certificate
19611 from a source other than a directory authority: it's not unusual
19612 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
19614 - Tolerate servers with more clock skew in their authentication
19615 certificates than previously. Fixes bug 4371; bugfix on
19617 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
19618 on 0.2.3.4-alpha and 0.2.3.6-alpha.
19621 - Add two new config options for directory authorities:
19622 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
19623 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
19624 that is always sufficient to satisfy the bandwidth requirement for
19625 the Guard flag. Now it will be easier for researchers to simulate
19626 Tor networks with different values. Resolves ticket 4484.
19627 - When Tor ignores a hidden service specified in its configuration,
19628 include the hidden service's directory in the warning message.
19629 Previously, we would only tell the user that some hidden service
19630 was ignored. Bugfix on 0.0.6; fixes bug 4426.
19631 - When we fail to initialize Libevent, retry with IOCP disabled so we
19632 don't need to turn on multi-threading support in Libevent, which in
19633 turn requires a working socketpair(). This is a workaround for bug
19634 4457, which affects Libevent versions from 2.0.1-alpha through
19636 - Detect when we try to build on a platform that doesn't define
19637 AF_UNSPEC to 0. We don't work there, so refuse to compile.
19638 - Update to the November 1 2011 Maxmind GeoLite Country database.
19640 o Packaging changes:
19641 - Make it easier to automate expert package builds on Windows,
19642 by removing an absolute path from makensis.exe command.
19644 o Code simplifications and refactoring:
19645 - Remove some redundant #include directives throughout the code.
19646 Patch from Andrea Gelmini.
19647 - Unconditionally use OpenSSL's AES implementation instead of our
19648 old built-in one. OpenSSL's AES has been better for a while, and
19649 relatively few servers should still be on any version of OpenSSL
19650 that doesn't have good optimized assembly AES.
19651 - Use the name "CERTS" consistently to refer to the new cell type;
19652 we were calling it CERT in some places and CERTS in others.
19655 - Numerous new unit tests for functions in util.c and address.c by
19657 - The long-disabled benchmark tests are now split into their own
19658 ./src/test/bench binary.
19659 - The benchmark tests can now use more accurate timers than
19660 gettimeofday() when such timers are available.
19663 Changes in version 0.2.3.7-alpha - 2011-10-30
19664 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
19665 the new v3 handshake. It also resolves yet another bridge address
19669 - If we mark an OR connection for close based on a cell we process,
19670 don't process any further cells on it. We already avoid further
19671 reads on marked-for-close connections, but now we also discard the
19672 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
19673 which was the first version where we might mark a connection for
19674 close based on processing a cell on it.
19675 - Fix a double-free bug that would occur when we received an invalid
19676 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
19677 bugfix on 0.2.3.6-alpha.
19678 - Bridges no longer include their address in NETINFO cells on outgoing
19679 OR connections, to allow them to blend in better with clients.
19680 Removes another avenue for enumerating bridges. Reported by
19681 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
19682 cells were introduced.
19685 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
19686 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
19689 Changes in version 0.2.3.6-alpha - 2011-10-26
19690 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
19691 anonymity vulnerability where an attacker can deanonymize Tor
19692 users. Everybody should upgrade.
19694 This release also features support for a new v3 connection handshake
19695 protocol, and fixes to make hidden service connections more robust.
19698 - Implement a new handshake protocol (v3) for authenticating Tors to
19699 each other over TLS. It should be more resistant to fingerprinting
19700 than previous protocols, and should require less TLS hacking for
19701 future Tor implementations. Implements proposal 176.
19702 - Allow variable-length padding cells to disguise the length of
19703 Tor's TLS records. Implements part of proposal 184.
19705 o Privacy/anonymity fixes (clients):
19706 - Clients and bridges no longer send TLS certificate chains on
19707 outgoing OR connections. Previously, each client or bridge would
19708 use the same cert chain for all outgoing OR connections until
19709 its IP address changes, which allowed any relay that the client
19710 or bridge contacted to determine which entry guards it is using.
19711 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19712 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19713 no longer considers that connection as suitable for satisfying a
19714 circuit EXTEND request. Now relays can protect clients from the
19715 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19716 - Directory authorities no longer assign the Guard flag to relays
19717 that haven't upgraded to the above "refuse EXTEND requests
19718 to client connections" fix. Now directory authorities can
19719 protect clients from the CVE-2011-2768 issue even if neither
19720 the clients nor the relays have upgraded yet. There's a new
19721 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
19722 to let us transition smoothly, else tomorrow there would be no
19725 o Major bugfixes (hidden services):
19726 - Improve hidden service robustness: when an attempt to connect to
19727 a hidden service ends, be willing to refetch its hidden service
19728 descriptors from each of the HSDir relays responsible for them
19729 immediately. Previously, we would not consider refetching the
19730 service's descriptors from each HSDir for 15 minutes after the last
19731 fetch, which was inconvenient if the hidden service was not running
19732 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
19733 - When one of a hidden service's introduction points appears to be
19734 unreachable, stop trying it. Previously, we would keep trying
19735 to build circuits to the introduction point until we lost the
19736 descriptor, usually because the user gave up and restarted Tor.
19737 Partly fixes bug 3825.
19738 - Don't launch a useless circuit after failing to use one of a
19739 hidden service's introduction points. Previously, we would
19740 launch a new introduction circuit, but not set the hidden service
19741 which that circuit was intended to connect to, so it would never
19742 actually be used. A different piece of code would then create a
19743 new introduction circuit correctly. Bug reported by katmagic and
19744 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
19746 o Major bugfixes (other):
19747 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19748 that they initiated. Relays could distinguish incoming bridge
19749 connections from client connections, creating another avenue for
19750 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19751 Found by "frosty_un".
19752 - Don't update the AccountingSoftLimitHitAt state file entry whenever
19753 tor gets started. This prevents a wrong average bandwidth
19754 estimate, which would cause relays to always start a new accounting
19755 interval at the earliest possible moment. Fixes bug 2003; bugfix
19756 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
19757 immensely in tracking this bug down.
19758 - Fix a crash bug when changing node restrictions while a DNS lookup
19759 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
19762 o Minor bugfixes (on 0.2.2.x and earlier):
19763 - When a hidden service turns an extra service-side introduction
19764 circuit into a general-purpose circuit, free the rend_data and
19765 intro_key fields first, so we won't leak memory if the circuit
19766 is cannibalized for use as another service-side introduction
19767 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
19768 - Rephrase the log message emitted if the TestSocks check is
19769 successful. Patch from Fabian Keil; fixes bug 4094.
19770 - Bridges now skip DNS self-tests, to act a little more stealthily.
19771 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
19772 bridges. Patch by "warms0x".
19773 - Remove a confusing dollar sign from the example fingerprint in the
19774 man page, and also make the example fingerprint a valid one. Fixes
19775 bug 4309; bugfix on 0.2.1.3-alpha.
19776 - Fix internal bug-checking logic that was supposed to catch
19777 failures in digest generation so that it will fail more robustly
19778 if we ask for a nonexistent algorithm. Found by Coverity Scan.
19779 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
19780 - Report any failure in init_keys() calls launched because our
19781 IP address has changed. Spotted by Coverity Scan. Bugfix on
19782 0.1.1.4-alpha; fixes CID 484.
19784 o Minor bugfixes (on 0.2.3.x):
19785 - Fix a bug in configure.in that kept it from building a configure
19786 script with autoconf versions earlier than 2.61. Fixes bug 2430;
19787 bugfix on 0.2.3.1-alpha.
19788 - Don't warn users that they are exposing a client port to the
19789 Internet if they have specified an RFC1918 address. Previously,
19790 we would warn if the user had specified any non-loopback
19791 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
19792 - Fix memory leaks in the failing cases of the new SocksPort and
19793 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
19794 fixes coverity CIDs 485, 486, and 487.
19797 - When a hidden service's introduction point times out, consider
19798 trying it again during the next attempt to connect to the
19799 HS. Previously, we would not try it again unless a newly fetched
19800 descriptor contained it. Required by fixes for bugs 1297 and 3825.
19801 - The next version of Windows will be called Windows 8, and it has
19802 a major version of 6, minor version of 2. Correctly identify that
19803 version instead of calling it "Very recent version". Resolves
19804 ticket 4153; reported by funkstar.
19805 - The Bridge Authority now writes statistics on how many bridge
19806 descriptors it gave out in total, and how many unique descriptors
19807 it gave out. It also lists how often the most and least commonly
19808 fetched descriptors were given out, as well as the median and
19809 25th/75th percentile. Implements tickets 4200 and 4294.
19810 - Update to the October 4 2011 Maxmind GeoLite Country database.
19812 o Code simplifications and refactoring:
19813 - Remove some old code to remember statistics about which descriptors
19814 we've served as a directory mirror. The feature wasn't used and
19815 is outdated now that microdescriptors are around.
19816 - Rename Tor functions that turn strings into addresses, so that
19817 "parse" indicates that no hostname resolution occurs, and
19818 "lookup" indicates that hostname resolution may occur. This
19819 should help prevent mistakes in the future. Fixes bug 3512.
19822 Changes in version 0.2.2.34 - 2011-10-26
19823 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
19824 can deanonymize Tor users. Everybody should upgrade.
19826 The attack relies on four components: 1) Clients reuse their TLS cert
19827 when talking to different relays, so relays can recognize a user by
19828 the identity key in her cert. 2) An attacker who knows the client's
19829 identity key can probe each guard relay to see if that identity key
19830 is connected to that guard relay right now. 3) A variety of active
19831 attacks in the literature (starting from "Low-Cost Traffic Analysis
19832 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
19833 discover the guard relays that a Tor user visiting the website is using.
19834 4) Clients typically pick three guards at random, so the set of guards
19835 for a given user could well be a unique fingerprint for her. This
19836 release fixes components #1 and #2, which is enough to block the attack;
19837 the other two remain as open research problems. Special thanks to
19838 "frosty_un" for reporting the issue to us!
19840 Clients should upgrade so they are no longer recognizable by the TLS
19841 certs they present. Relays should upgrade so they no longer allow a
19842 remote attacker to probe them to test whether unpatched clients are
19843 currently connected to them.
19845 This release also fixes several vulnerabilities that allow an attacker
19846 to enumerate bridge relays. Some bridge enumeration attacks still
19847 remain; see for example proposal 188.
19849 o Privacy/anonymity fixes (clients):
19850 - Clients and bridges no longer send TLS certificate chains on
19851 outgoing OR connections. Previously, each client or bridge would
19852 use the same cert chain for all outgoing OR connections until
19853 its IP address changes, which allowed any relay that the client
19854 or bridge contacted to determine which entry guards it is using.
19855 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19856 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19857 no longer considers that connection as suitable for satisfying a
19858 circuit EXTEND request. Now relays can protect clients from the
19859 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19860 - Directory authorities no longer assign the Guard flag to relays
19861 that haven't upgraded to the above "refuse EXTEND requests
19862 to client connections" fix. Now directory authorities can
19863 protect clients from the CVE-2011-2768 issue even if neither
19864 the clients nor the relays have upgraded yet. There's a new
19865 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
19866 to let us transition smoothly, else tomorrow there would be no
19869 o Privacy/anonymity fixes (bridge enumeration):
19870 - Bridge relays now do their directory fetches inside Tor TLS
19871 connections, like all the other clients do, rather than connecting
19872 directly to the DirPort like public relays do. Removes another
19873 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
19874 - Bridges relays now build circuits for themselves in a more similar
19875 way to how clients build them. Removes another avenue for
19876 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
19877 when bridges were introduced.
19878 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19879 that they initiated. Relays could distinguish incoming bridge
19880 connections from client connections, creating another avenue for
19881 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19882 Found by "frosty_un".
19885 - Fix a crash bug when changing node restrictions while a DNS lookup
19886 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
19888 - Don't launch a useless circuit after failing to use one of a
19889 hidden service's introduction points. Previously, we would
19890 launch a new introduction circuit, but not set the hidden service
19891 which that circuit was intended to connect to, so it would never
19892 actually be used. A different piece of code would then create a
19893 new introduction circuit correctly. Bug reported by katmagic and
19894 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
19897 - Change an integer overflow check in the OpenBSD_Malloc code so
19898 that GCC is less likely to eliminate it as impossible. Patch
19899 from Mansour Moufid. Fixes bug 4059.
19900 - When a hidden service turns an extra service-side introduction
19901 circuit into a general-purpose circuit, free the rend_data and
19902 intro_key fields first, so we won't leak memory if the circuit
19903 is cannibalized for use as another service-side introduction
19904 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
19905 - Bridges now skip DNS self-tests, to act a little more stealthily.
19906 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
19907 bridges. Patch by "warms0x".
19908 - Fix internal bug-checking logic that was supposed to catch
19909 failures in digest generation so that it will fail more robustly
19910 if we ask for a nonexistent algorithm. Found by Coverity Scan.
19911 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
19912 - Report any failure in init_keys() calls launched because our
19913 IP address has changed. Spotted by Coverity Scan. Bugfix on
19914 0.1.1.4-alpha; fixes CID 484.
19916 o Minor bugfixes (log messages and documentation):
19917 - Remove a confusing dollar sign from the example fingerprint in the
19918 man page, and also make the example fingerprint a valid one. Fixes
19919 bug 4309; bugfix on 0.2.1.3-alpha.
19920 - The next version of Windows will be called Windows 8, and it has
19921 a major version of 6, minor version of 2. Correctly identify that
19922 version instead of calling it "Very recent version". Resolves
19923 ticket 4153; reported by funkstar.
19924 - Downgrade log messages about circuit timeout calibration from
19925 "notice" to "info": they don't require or suggest any human
19926 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
19927 bugfix on 0.2.2.14-alpha.
19930 - Turn on directory request statistics by default and include them in
19931 extra-info descriptors. Don't break if we have no GeoIP database.
19932 Backported from 0.2.3.1-alpha; implements ticket 3951.
19933 - Update to the October 4 2011 Maxmind GeoLite Country database.
19936 Changes in version 0.2.1.31 - 2011-10-26
19937 Tor 0.2.1.31 backports important security and privacy fixes for
19938 oldstable. This release is intended only for package maintainers and
19939 others who cannot use the 0.2.2 stable series. All others should be
19940 using Tor 0.2.2.x or newer.
19942 o Security fixes (also included in 0.2.2.x):
19943 - Replace all potentially sensitive memory comparison operations
19944 with versions whose runtime does not depend on the data being
19945 compared. This will help resist a class of attacks where an
19946 adversary can use variations in timing information to learn
19947 sensitive data. Fix for one case of bug 3122. (Safe memcmp
19948 implementation by Robert Ransom based partially on code by DJB.)
19949 - Fix an assert in parsing router descriptors containing IPv6
19950 addresses. This one took down the directory authorities when
19951 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
19953 o Privacy/anonymity fixes (also included in 0.2.2.x):
19954 - Clients and bridges no longer send TLS certificate chains on
19955 outgoing OR connections. Previously, each client or bridge would
19956 use the same cert chain for all outgoing OR connections until
19957 its IP address changes, which allowed any relay that the client
19958 or bridge contacted to determine which entry guards it is using.
19959 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
19960 - If a relay receives a CREATE_FAST cell on a TLS connection, it
19961 no longer considers that connection as suitable for satisfying a
19962 circuit EXTEND request. Now relays can protect clients from the
19963 CVE-2011-2768 issue even if the clients haven't upgraded yet.
19964 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
19965 that they initiated. Relays could distinguish incoming bridge
19966 connections from client connections, creating another avenue for
19967 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
19968 Found by "frosty_un".
19969 - When receiving a hidden service descriptor, check that it is for
19970 the hidden service we wanted. Previously, Tor would store any
19971 hidden service descriptors that a directory gave it, whether it
19972 wanted them or not. This wouldn't have let an attacker impersonate
19973 a hidden service, but it did let directories pre-seed a client
19974 with descriptors that it didn't want. Bugfix on 0.0.6.
19975 - Avoid linkability based on cached hidden service descriptors: forget
19976 all hidden service descriptors cached as a client when processing a
19977 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
19978 - Make the bridge directory authority refuse to answer directory
19979 requests for "all" descriptors. It used to include bridge
19980 descriptors in its answer, which was a major information leak.
19981 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
19982 - Don't attach new streams to old rendezvous circuits after SIGNAL
19983 NEWNYM. Previously, we would keep using an existing rendezvous
19984 circuit if it remained open (i.e. if it were kept open by a
19985 long-lived stream, or if a new stream were attached to it before
19986 Tor could notice that it was old and no longer in use). Bugfix on
19987 0.1.1.15-rc; fixes bug 3375.
19989 o Minor bugfixes (also included in 0.2.2.x):
19990 - When we restart our relay, we might get a successful connection
19991 from the outside before we've started our reachability tests,
19992 triggering a warning: "ORPort found reachable, but I have no
19993 routerinfo yet. Failing to inform controller of success." This
19994 bug was harmless unless Tor is running under a controller
19995 like Vidalia, in which case the controller would never get a
19996 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
19998 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
19999 enabled. Fixes bug 1526.
20000 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20001 anything since 0.2.1.16-rc.
20002 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20003 None of the cases where we did this before were wrong, but by making
20004 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20005 - Fix a rare crash bug that could occur when a client was configured
20006 with a large number of bridges. Fixes bug 2629; bugfix on
20007 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20008 - Correct the warning displayed when a rendezvous descriptor exceeds
20009 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20011 - Fix an uncommon assertion failure when running with DNSPort under
20012 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20013 - When warning about missing zlib development packages during compile,
20014 give the correct package names. Bugfix on 0.2.0.1-alpha.
20015 - Require that introduction point keys and onion keys have public
20016 exponent 65537. Bugfix on 0.2.0.10-alpha.
20017 - Do not crash when our configuration file becomes unreadable, for
20018 example due to a permissions change, between when we start up
20019 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20021 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20023 - Always NUL-terminate the sun_path field of a sockaddr_un before
20024 passing it to the kernel. (Not a security issue: kernels are
20025 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20026 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20027 - Don't stack-allocate the list of supplementary GIDs when we're
20028 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20029 could take up to 256K, which is way too much stack. Found by
20030 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20032 o Minor bugfixes (only in 0.2.1.x):
20033 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
20034 rely on them. Bugfix on 0.2.1.30.
20035 - Use git revisions instead of svn revisions when generating our
20036 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20038 o Minor features (also included in 0.2.2.x):
20039 - Adjust the expiration time on our SSL session certificates to
20040 better match SSL certs seen in the wild. Resolves ticket 4014.
20041 - Allow nameservers with IPv6 address. Resolves bug 2574.
20042 - Update to the October 4 2011 Maxmind GeoLite Country database.
20045 Changes in version 0.2.3.5-alpha - 2011-09-28
20046 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
20047 bridge relays; fixes an assertion error that many users started hitting
20048 today; and adds the ability to refill token buckets more often than
20049 once per second, allowing significant performance improvements.
20052 - Bridge relays now do their directory fetches inside Tor TLS
20053 connections, like all the other clients do, rather than connecting
20054 directly to the DirPort like public relays do. Removes another
20055 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20056 - Bridges relays now build circuits for themselves in a more similar
20057 way to how clients build them. Removes another avenue for
20058 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20059 when bridges were introduced.
20062 - Fix an "Assertion md->held_by_node == 1 failed" error that could
20063 occur when the same microdescriptor was referenced by two node_t
20064 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
20066 o Major features (networking):
20067 - Add a new TokenBucketRefillInterval option to refill token buckets
20068 more frequently than once per second. This should improve network
20069 performance, alleviate queueing problems, and make traffic less
20070 bursty. Implements proposal 183; closes ticket 3630. Design by
20071 Florian Tschorsch and Björn Scheuermann; implementation by
20075 - Change an integer overflow check in the OpenBSD_Malloc code so
20076 that GCC is less likely to eliminate it as impossible. Patch
20077 from Mansour Moufid. Fixes bug 4059.
20079 o Minor bugfixes (usability):
20080 - Downgrade log messages about circuit timeout calibration from
20081 "notice" to "info": they don't require or suggest any human
20082 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20083 bugfix on 0.2.2.14-alpha.
20085 o Minor features (diagnostics):
20086 - When the system call to create a listener socket fails, log the
20087 error message explaining why. This may help diagnose bug 4027.
20090 Changes in version 0.2.3.4-alpha - 2011-09-13
20091 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
20092 tweak to Tor's TLS handshake that makes relays and bridges that run
20093 this new version reachable from Iran again. It also fixes a few new
20094 bugs in 0.2.3.x, and teaches relays to recognize when they're not
20095 listed in the network consensus and republish.
20097 o Major bugfixes (also part of 0.2.2.33):
20098 - Avoid an assertion failure when reloading a configuration with
20099 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20100 3923; bugfix on 0.2.2.25-alpha.
20102 o Minor features (security, also part of 0.2.2.33):
20103 - Check for replays of the public-key encrypted portion of an
20104 INTRODUCE1 cell, in addition to the current check for replays of
20105 the g^x value. This prevents a possible class of active attacks
20106 by an attacker who controls both an introduction point and a
20107 rendezvous point, and who uses the malleability of AES-CTR to
20108 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20109 that these attacks are infeasible (requiring the attacker to send
20110 on the order of zettabytes of altered cells in a short interval),
20111 but we'd rather block them off in case there are any classes of
20112 this attack that we missed. Reported by Willem Pinckaers.
20114 o Minor features (also part of 0.2.2.33):
20115 - Adjust the expiration time on our SSL session certificates to
20116 better match SSL certs seen in the wild. Resolves ticket 4014.
20117 - Change the default required uptime for a relay to be accepted as
20118 a HSDir (hidden service directory) from 24 hours to 25 hours.
20119 Improves on 0.2.0.10-alpha; resolves ticket 2649.
20120 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
20121 authorities to abstain from voting on assignment of the HSDir
20122 consensus flag. Related to bug 2649.
20123 - Update to the September 6 2011 Maxmind GeoLite Country database.
20125 o Minor bugfixes (also part of 0.2.2.33):
20126 - Demote the 'replay detected' log message emitted when a hidden
20127 service receives the same Diffie-Hellman public key in two different
20128 INTRODUCE2 cells to info level. A normal Tor client can cause that
20129 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
20130 fixes part of bug 2442.
20131 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
20132 level. There is nothing that a hidden service's operator can do
20133 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
20135 - Clarify a log message specifying the characters permitted in
20136 HiddenServiceAuthorizeClient client names. Previously, the log
20137 message said that "[A-Za-z0-9+-_]" were permitted; that could have
20138 given the impression that every ASCII character between "+" and "_"
20139 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
20141 o Build fixes (also part of 0.2.2.33):
20142 - Clean up some code issues that prevented Tor from building on older
20143 BSDs. Fixes bug 3894; reported by "grarpamp".
20144 - Search for a platform-specific version of "ar" when cross-compiling.
20145 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
20148 - Fix a bug where the SocksPort option (for example) would get
20149 ignored and replaced by the default if a SocksListenAddress
20150 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
20154 - Relays now try regenerating and uploading their descriptor more
20155 frequently if they are not listed in the consensus, or if the
20156 version of their descriptor listed in the consensus is too
20157 old. This fix should prevent situations where a server declines
20158 to re-publish itself because it has done so too recently, even
20159 though the authorities decided not to list its recent-enough
20160 descriptor. Fix for bug 3327.
20163 - Relays now include a reason for regenerating their descriptors
20164 in an HTTP header when uploading to the authorities. This will
20165 make it easier to debug descriptor-upload issues in the future.
20166 - When starting as root and then changing our UID via the User
20167 control option, and we have a ControlSocket configured, make sure
20168 that the ControlSocket is owned by the same account that Tor will
20169 run under. Implements ticket 3421; fix by Jérémy Bobbio.
20172 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
20173 utility function used in the control-port code). This shouldn't
20174 ever happen unless Tor is completely out of memory, but if it did
20175 happen and Tor somehow recovered from it, Tor could have sent a log
20176 message to a control port in the middle of a reply to a controller
20177 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
20178 - Make 'FetchUselessDescriptors' cause all descriptor types and
20179 all consensus types (including microdescriptors) to get fetched.
20180 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
20182 o Code refactoring:
20183 - Make a new "entry connection" struct as an internal subtype of "edge
20184 connection", to simplify the code and make exit connections smaller.
20187 Changes in version 0.2.2.33 - 2011-09-13
20188 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
20189 TLS handshake that makes relays and bridges that run this new version
20190 reachable from Iran again.
20193 - Avoid an assertion failure when reloading a configuration with
20194 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20195 3923; bugfix on 0.2.2.25-alpha.
20197 o Minor features (security):
20198 - Check for replays of the public-key encrypted portion of an
20199 INTRODUCE1 cell, in addition to the current check for replays of
20200 the g^x value. This prevents a possible class of active attacks
20201 by an attacker who controls both an introduction point and a
20202 rendezvous point, and who uses the malleability of AES-CTR to
20203 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20204 that these attacks are infeasible (requiring the attacker to send
20205 on the order of zettabytes of altered cells in a short interval),
20206 but we'd rather block them off in case there are any classes of
20207 this attack that we missed. Reported by Willem Pinckaers.
20210 - Adjust the expiration time on our SSL session certificates to
20211 better match SSL certs seen in the wild. Resolves ticket 4014.
20212 - Change the default required uptime for a relay to be accepted as
20213 a HSDir (hidden service directory) from 24 hours to 25 hours.
20214 Improves on 0.2.0.10-alpha; resolves ticket 2649.
20215 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
20216 authorities to abstain from voting on assignment of the HSDir
20217 consensus flag. Related to bug 2649.
20218 - Update to the September 6 2011 Maxmind GeoLite Country database.
20220 o Minor bugfixes (documentation and log messages):
20221 - Correct the man page to explain that HashedControlPassword and
20222 CookieAuthentication can both be set, in which case either method
20223 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
20224 when we decided to allow these config options to both be set. Issue
20225 raised by bug 3898.
20226 - Demote the 'replay detected' log message emitted when a hidden
20227 service receives the same Diffie-Hellman public key in two different
20228 INTRODUCE2 cells to info level. A normal Tor client can cause that
20229 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
20230 fixes part of bug 2442.
20231 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
20232 level. There is nothing that a hidden service's operator can do
20233 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
20235 - Clarify a log message specifying the characters permitted in
20236 HiddenServiceAuthorizeClient client names. Previously, the log
20237 message said that "[A-Za-z0-9+-_]" were permitted; that could have
20238 given the impression that every ASCII character between "+" and "_"
20239 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
20242 - Provide a substitute implementation of lround() for MSVC, which
20243 apparently lacks it. Patch from Gisle Vanem.
20244 - Clean up some code issues that prevented Tor from building on older
20245 BSDs. Fixes bug 3894; reported by "grarpamp".
20246 - Search for a platform-specific version of "ar" when cross-compiling.
20247 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
20250 Changes in version 0.2.3.3-alpha - 2011-09-01
20251 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
20252 security, and provides client-side support for the microdescriptor
20253 and optimistic data features introduced earlier in the 0.2.3.x
20254 series. It also includes numerous critical bugfixes in the (optional)
20255 bufferevent-based networking backend.
20257 o Major features (stream isolation):
20258 - You can now configure Tor so that streams from different
20259 applications are isolated on different circuits, to prevent an
20260 attacker who sees your streams as they leave an exit node from
20261 linking your sessions to one another. To do this, choose some way
20262 to distinguish the applications: have them connect to different
20263 SocksPorts, or have one of them use SOCKS4 while the other uses
20264 SOCKS5, or have them pass different authentication strings to the
20265 SOCKS proxy. Then, use the new SocksPort syntax to configure the
20266 degree of isolation you need. This implements Proposal 171.
20267 - There's a new syntax for specifying multiple client ports (such as
20268 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
20269 multiple *Port entries with full addr:port syntax on each.
20270 The old *ListenAddress format is still supported, but you can't
20271 mix it with the new *Port syntax.
20273 o Major features (other):
20274 - Enable microdescriptor fetching by default for clients. This allows
20275 clients to download a much smaller amount of directory information.
20276 To disable it (and go back to the old-style consensus and
20277 descriptors), set "UseMicrodescriptors 0" in your torrc file.
20278 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
20279 "PortForwarding" config option), now supports Windows.
20280 - When using an exit relay running 0.2.3.x, clients can now
20281 "optimistically" send data before the exit relay reports that
20282 the stream has opened. This saves a round trip when starting
20283 connections where the client speaks first (such as web browsing).
20284 This behavior is controlled by a consensus parameter (currently
20285 disabled). To turn it on or off manually, use the "OptimisticData"
20286 torrc option. Implements proposal 181; code by Ian Goldberg.
20288 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
20289 - When using IOCP on Windows, we need to enable Libevent windows
20291 - The IOCP backend now works even when the user has not specified
20292 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
20293 Fixes part of bug 3752.
20294 - Correctly record the bytes we've read and written when using
20295 bufferevents, so that we can include them in our bandwidth history
20296 and advertised bandwidth. Fixes bug 3803.
20297 - Apply rate-limiting only at the bottom of a chain of filtering
20298 bufferevents. This prevents us from filling up internal read
20299 buffers and violating rate-limits when filtering bufferevents
20300 are enabled. Fixes part of bug 3804.
20301 - Add high-watermarks to the output buffers for filtered
20302 bufferevents. This prevents us from filling up internal write
20303 buffers and wasting CPU cycles when filtering bufferevents are
20304 enabled. Fixes part of bug 3804.
20305 - Correctly notice when data has been written from a bufferevent
20306 without flushing it completely. Fixes bug 3805.
20307 - Fix a bug where server-side tunneled bufferevent-based directory
20308 streams would get closed prematurely. Fixes bug 3814.
20309 - Fix a use-after-free error with per-connection rate-limiting
20310 buckets. Fixes bug 3888.
20312 o Major bugfixes (also part of 0.2.2.31-rc):
20313 - If we're configured to write our ControlPorts to disk, only write
20314 them after switching UID and creating the data directory. This way,
20315 we don't fail when starting up with a nonexistent DataDirectory
20316 and a ControlPortWriteToFile setting based on that directory. Fixes
20317 bug 3747; bugfix on Tor 0.2.2.26-beta.
20320 - Added a new CONF_CHANGED event so that controllers can be notified
20321 of any configuration changes made by other controllers, or by the
20322 user. Implements ticket 1692.
20323 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
20324 leak when using bufferevents, and lets Libevent worry about how to
20325 best copy data out of a buffer.
20326 - Replace files in stats/ rather than appending to them. Now that we
20327 include statistics in extra-info descriptors, it makes no sense to
20328 keep old statistics forever. Implements ticket 2930.
20330 o Minor features (build compatibility):
20331 - Limited, experimental support for building with nmake and MSVC.
20332 - Provide a substitute implementation of lround() for MSVC, which
20333 apparently lacks it. Patch from Gisle Vanem.
20335 o Minor features (also part of 0.2.2.31-rc):
20336 - Update to the August 2 2011 Maxmind GeoLite Country database.
20338 o Minor bugfixes (on 0.2.3.x-alpha):
20339 - Fix a spurious warning when parsing SOCKS requests with
20340 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
20341 - Get rid of a harmless warning that could happen on relays running
20342 with bufferevents. The warning was caused by someone doing an http
20343 request to a relay's orport. Also don't warn for a few related
20344 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
20346 o Minor bugfixes (on 2.2.x and earlier):
20347 - Correct the man page to explain that HashedControlPassword and
20348 CookieAuthentication can both be set, in which case either method
20349 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
20350 when we decided to allow these config options to both be set. Issue
20351 raised by bug 3898.
20352 - The "--quiet" and "--hush" options now apply not only to Tor's
20353 behavior before logs are configured, but also to Tor's behavior in
20354 the absence of configured logs. Fixes bug 3550; bugfix on
20357 o Minor bugfixes (also part of 0.2.2.31-rc):
20358 - Write several files in text mode, on OSes that distinguish text
20359 mode from binary mode (namely, Windows). These files are:
20360 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
20361 that collect those statistics; 'client_keys' and 'hostname' for
20362 hidden services that use authentication; and (in the tor-gencert
20363 utility) newly generated identity and signing keys. Previously,
20364 we wouldn't specify text mode or binary mode, leading to an
20365 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
20366 the DirRecordUsageByCountry option which would have triggered
20367 the assertion failure was added), although this assertion failure
20368 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
20369 - Selectively disable deprecation warnings on OS X because Lion
20370 started deprecating the shipped copy of openssl. Fixes bug 3643.
20371 - Remove an extra pair of quotation marks around the error
20372 message in control-port STATUS_GENERAL BUG events. Bugfix on
20373 0.1.2.6-alpha; fixes bug 3732.
20374 - When unable to format an address as a string, report its value
20375 as "???" rather than reusing the last formatted address. Bugfix
20378 o Code simplifications and refactoring:
20379 - Rewrite the listener-selection logic so that parsing which ports
20380 we want to listen on is now separate from binding to the ports
20384 - Building Tor with bufferevent support now requires Libevent
20385 2.0.13-stable or later. Previous versions of Libevent had bugs in
20386 SSL-related bufferevents and related issues that would make Tor
20387 work badly with bufferevents. Requiring 2.0.13-stable also allows
20388 Tor with bufferevents to take advantage of Libevent APIs
20389 introduced after 2.0.8-rc.
20392 Changes in version 0.2.2.32 - 2011-08-27
20393 The Tor 0.2.2 release series is dedicated to the memory of Andreas
20394 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
20395 a founder of the PETS community, a leader in our field, a mentor,
20396 and a friend. He left us with these words: "I had the possibility
20397 to contribute to this world that is not as it should be. I hope I
20398 could help in some areas to make the world a better place, and that
20399 I could also encourage other people to be engaged in improving the
20400 world. Please, stay engaged. This world needs you, your love, your
20401 initiative -- now I cannot be part of that anymore."
20403 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
20404 ready. More than two years in the making, this release features improved
20405 client performance and hidden service reliability, better compatibility
20406 for Android, correct behavior for bridges that listen on more than
20407 one address, more extensible and flexible directory object handling,
20408 better reporting of network statistics, improved code security, and
20409 many many other features and bugfixes.
20412 Changes in version 0.2.2.31-rc - 2011-08-17
20413 Tor 0.2.2.31-rc is the second and hopefully final release candidate
20414 for the Tor 0.2.2.x series.
20417 - Remove an extra pair of quotation marks around the error
20418 message in control-port STATUS_GENERAL BUG events. Bugfix on
20419 0.1.2.6-alpha; fixes bug 3732.
20420 - If we're configured to write our ControlPorts to disk, only write
20421 them after switching UID and creating the data directory. This way,
20422 we don't fail when starting up with a nonexistent DataDirectory
20423 and a ControlPortWriteToFile setting based on that directory. Fixes
20424 bug 3747; bugfix on Tor 0.2.2.26-beta.
20427 - Update to the August 2 2011 Maxmind GeoLite Country database.
20430 - Allow GETINFO fingerprint to return a fingerprint even when
20431 we have not yet built a router descriptor. Fixes bug 3577;
20432 bugfix on 0.2.0.1-alpha.
20433 - Write several files in text mode, on OSes that distinguish text
20434 mode from binary mode (namely, Windows). These files are:
20435 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
20436 that collect those statistics; 'client_keys' and 'hostname' for
20437 hidden services that use authentication; and (in the tor-gencert
20438 utility) newly generated identity and signing keys. Previously,
20439 we wouldn't specify text mode or binary mode, leading to an
20440 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
20441 the DirRecordUsageByCountry option which would have triggered
20442 the assertion failure was added), although this assertion failure
20443 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
20444 - Selectively disable deprecation warnings on OS X because Lion
20445 started deprecating the shipped copy of openssl. Fixes bug 3643.
20446 - When unable to format an address as a string, report its value
20447 as "???" rather than reusing the last formatted address. Bugfix
20451 Changes in version 0.2.3.2-alpha - 2011-07-18
20452 Tor 0.2.3.2-alpha introduces two new experimental features:
20453 microdescriptors and pluggable transports. It also continues cleaning
20454 up a variety of recently introduced features.
20457 - Clients can now use microdescriptors instead of regular descriptors
20458 to build circuits. Microdescriptors are authority-generated
20459 summaries of regular descriptors' contents, designed to change
20460 very rarely (see proposal 158 for details). This feature is
20461 designed to save bandwidth, especially for clients on slow internet
20462 connections. It's off by default for now, since nearly no caches
20463 support it, but it will be on-by-default for clients in a future
20464 version. You can use the UseMicrodescriptors option to turn it on.
20465 - Tor clients using bridges can now be configured to use a separate
20466 'transport' proxy for each bridge. This approach helps to resist
20467 censorship by allowing bridges to use protocol obfuscation
20468 plugins. It implements part of proposal 180. Implements ticket 2841.
20469 - While we're trying to bootstrap, record how many TLS connections
20470 fail in each state, and report which states saw the most failures
20471 in response to any bootstrap failures. This feature may speed up
20472 diagnosis of censorship events. Implements ticket 3116.
20474 o Major bugfixes (on 0.2.3.1-alpha):
20475 - When configuring a large set of nodes in EntryNodes (as with
20476 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
20477 random subset to be guards, and choose them in random
20478 order. Fixes bug 2798.
20479 - Tor could crash when remembering a consensus in a non-used consensus
20480 flavor without having a current consensus set. Fixes bug 3361.
20481 - Comparing an unknown address to a microdescriptor's shortened exit
20482 policy would always give a "rejected" result. Fixes bug 3599.
20483 - Using microdescriptors as a client no longer prevents Tor from
20484 uploading and downloading hidden service descriptors. Fixes
20488 - Allow nameservers with IPv6 address. Resolves bug 2574.
20489 - Accept attempts to include a password authenticator in the
20490 handshake, as supported by SOCKS5. This handles SOCKS clients that
20491 don't know how to omit a password when authenticating. Resolves
20493 - When configuring a large set of nodes in EntryNodes, and there are
20494 enough of them listed as Guard so that we don't need to consider
20495 the non-guard entries, prefer the ones listed with the Guard flag.
20496 - Check for and recover from inconsistency in the microdescriptor
20497 cache. This will make it harder for us to accidentally free a
20498 microdescriptor without removing it from the appropriate data
20499 structures. Fixes issue 3135; issue noted by "wanoskarnet".
20500 - Log SSL state transitions at log level DEBUG, log domain
20501 HANDSHAKE. This can be useful for debugging censorship events.
20502 Implements ticket 3264.
20503 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
20504 implements ticket 3439.
20506 o Minor bugfixes (on 0.2.3.1-alpha):
20507 - Do not free all general-purpose regular descriptors just
20508 because microdescriptor use is enabled. Fixes bug 3113.
20509 - Correctly link libevent_openssl when --enable-static-libevent
20510 is passed to configure. Fixes bug 3118.
20511 - Bridges should not complain during their heartbeat log messages that
20512 they are unlisted in the consensus: that's more or less the point
20513 of being a bridge. Fixes bug 3183.
20514 - Report a SIGNAL event to controllers when acting on a delayed
20515 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
20516 event to the controller if we acted on a SIGNAL NEWNYM command
20517 immediately, and otherwise not report a SIGNAL event for the
20518 command at all. Fixes bug 3349.
20519 - Fix a crash when handling the SIGNAL controller command or
20520 reporting ERR-level status events with bufferevents enabled. Found
20521 by Robert Ransom. Fixes bug 3367.
20522 - Always ship the tor-fw-helper manpage in our release tarballs.
20523 Fixes bug 3389. Reported by Stephen Walker.
20524 - Fix a class of double-mark-for-close bugs when bufferevents
20525 are enabled. Fixes bug 3403.
20526 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
20527 - Add SIGNAL to the list returned by the 'GETINFO events/names'
20528 control-port command. Fixes part of bug 3465.
20529 - Prevent using negative indices during unit test runs when read_all()
20530 fails. Spotted by coverity.
20531 - Fix a rare memory leak when checking the nodelist without it being
20532 present. Found by coverity.
20533 - Only try to download a microdescriptor-flavored consensus from
20534 a directory cache that provides them.
20536 o Minor bugfixes (on 0.2.2.x and earlier):
20537 - Assert that hidden-service-related operations are not performed
20538 using single-hop circuits. Previously, Tor would assert that
20539 client-side streams are not attached to single-hop circuits,
20540 but not that other sensitive operations on the client and service
20541 side are not performed using single-hop circuits. Fixes bug 3332;
20543 - Don't publish a new relay descriptor when we reload our onion key,
20544 unless the onion key has actually changed. Fixes bug 3263 and
20545 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
20546 - Allow GETINFO fingerprint to return a fingerprint even when
20547 we have not yet built a router descriptor. Fixes bug 3577;
20548 bugfix on 0.2.0.1-alpha.
20549 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
20550 on 0.2.2.4-alpha; fixes bug 3427.
20552 o Code simplification and refactoring:
20553 - Use tor_sscanf() in place of scanf() in more places through the
20554 code. This makes us a little more locale-independent, and
20555 should help shut up code-analysis tools that can't tell
20556 a safe sscanf string from a dangerous one.
20557 - Use tt_assert(), not tor_assert(), for checking for test failures.
20558 This makes the unit tests more able to go on in the event that
20560 - Split connection_about_to_close() into separate functions for each
20564 - On Windows, we now define the _WIN32_WINNT macros only if they
20565 are not already defined. This lets the person building Tor decide,
20566 if they want, to require a later version of Windows.
20569 Changes in version 0.2.2.30-rc - 2011-07-07
20570 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
20571 series. It fixes a few smaller bugs, but generally appears stable.
20572 Please test it and let us know whether it is!
20575 - Send a SUCCEEDED stream event to the controller when a reverse
20576 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
20577 discovered by katmagic.
20578 - Always NUL-terminate the sun_path field of a sockaddr_un before
20579 passing it to the kernel. (Not a security issue: kernels are
20580 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20581 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20582 - Don't stack-allocate the list of supplementary GIDs when we're
20583 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20584 could take up to 256K, which is way too much stack. Found by
20585 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20586 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
20587 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
20588 fixes part of bug 3465.
20589 - Fix a memory leak when receiving a descriptor for a hidden
20590 service we didn't ask for. Found by Coverity; CID #30. Bugfix
20594 - Update to the July 1 2011 Maxmind GeoLite Country database.
20597 Changes in version 0.2.2.29-beta - 2011-06-20
20598 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
20599 have bridge lines in their torrc but don't want to use them; gets
20600 us closer to having the control socket feature working on Debian;
20601 and fixes a variety of smaller bugs.
20604 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
20605 When we changed the default behavior to "use bridges if any
20606 are listed in the torrc", we surprised users who had bridges
20607 in their torrc files but who didn't actually want to use them.
20608 Partial resolution for bug 3354.
20611 - Don't attach new streams to old rendezvous circuits after SIGNAL
20612 NEWNYM. Previously, we would keep using an existing rendezvous
20613 circuit if it remained open (i.e. if it were kept open by a
20614 long-lived stream, or if a new stream were attached to it before
20615 Tor could notice that it was old and no longer in use). Bugfix on
20616 0.1.1.15-rc; fixes bug 3375.
20619 - Fix a bug when using ControlSocketsGroupWritable with User. The
20620 directory's group would be checked against the current group, not
20621 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
20622 bugfix on 0.2.2.26-beta.
20623 - Make connection_printf_to_buf()'s behavior sane. Its callers
20624 expect it to emit a CRLF iff the format string ends with CRLF;
20625 it actually emitted a CRLF iff (a) the format string ended with
20626 CRLF or (b) the resulting string was over 1023 characters long or
20627 (c) the format string did not end with CRLF *and* the resulting
20628 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
20629 fixes part of bug 3407.
20630 - Make send_control_event_impl()'s behavior sane. Its callers
20631 expect it to always emit a CRLF at the end of the string; it
20632 might have emitted extra control characters as well. Bugfix on
20633 0.1.1.9-alpha; fixes another part of bug 3407.
20634 - Make crypto_rand_int() check the value of its input correctly.
20635 Previously, it accepted values up to UINT_MAX, but could return a
20636 negative number if given a value above INT_MAX+1. Found by George
20637 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
20638 - Avoid a segfault when reading a malformed circuit build state
20639 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
20641 - When asked about a DNS record type we don't support via a
20642 client DNSPort, reply with NOTIMPL rather than an empty
20643 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
20644 - Fix a rare memory leak during stats writing. Found by coverity.
20647 - Update to the June 1 2011 Maxmind GeoLite Country database.
20649 o Code simplifications and refactoring:
20650 - Remove some dead code as indicated by coverity.
20651 - Remove a few dead assignments during router parsing. Found by
20653 - Add some forgotten return value checks during unit tests. Found
20655 - Don't use 1-bit wide signed bit fields. Found by coverity.
20658 Changes in version 0.2.2.28-beta - 2011-06-04
20659 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
20660 fixed a big bug in whether relays stay in the consensus consistently,
20661 we moved closer to handling bridges and hidden services correctly,
20662 and we started the process of better handling the dreaded "my Vidalia
20663 died, and now my Tor demands a password when I try to reconnect to it"
20667 - Don't decide to make a new descriptor when receiving a HUP signal.
20668 This bug has caused a lot of 0.2.2.x relays to disappear from the
20669 consensus periodically. Fixes the most common case of triggering
20670 bug 1810; bugfix on 0.2.2.7-alpha.
20671 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
20672 - Don't try to build descriptors if "ORPort auto" is set and we
20673 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
20675 - Resolve a crash that occurred when setting BridgeRelay to 1 with
20676 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
20677 - Apply circuit timeouts to opened hidden-service-related circuits
20678 based on the correct start time. Previously, we would apply the
20679 circuit build timeout based on time since the circuit's creation;
20680 it was supposed to be applied based on time since the circuit
20681 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
20682 - Use the same circuit timeout for client-side introduction
20683 circuits as for other four-hop circuits, rather than the timeout
20684 for single-hop directory-fetch circuits; the shorter timeout may
20685 have been appropriate with the static circuit build timeout in
20686 0.2.1.x and earlier, but caused many hidden service access attempts
20687 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
20688 on 0.2.2.2-alpha; fixes another part of bug 1297.
20689 - In ticket 2511 we fixed a case where you could use an unconfigured
20690 bridge if you had configured it as a bridge the last time you ran
20691 Tor. Now fix another edge case: if you had configured it as a bridge
20692 but then switched to a different bridge via the controller, you
20693 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
20697 - Add an __OwningControllerProcess configuration option and a
20698 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
20699 that when it exits, Tor will shut down. Implements feature 3049.
20700 - If "UseBridges 1" is set and no bridges are configured, Tor will
20701 now refuse to build any circuits until some bridges are set.
20702 If "UseBridges auto" is set, Tor will use bridges if they are
20703 configured and we are not running as a server, but otherwise will
20704 make circuits as usual. The new default is "auto". Patch by anonym,
20705 so the Tails LiveCD can stop automatically revealing you as a Tor
20709 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20710 - Remove a trailing asterisk from "exit-policy/default" in the
20711 output of the control port command "GETINFO info/names". Bugfix
20713 - Use a wide type to hold sockets when built for 64-bit Windows builds.
20715 - Warn when the user configures two HiddenServiceDir lines that point
20716 to the same directory. Bugfix on 0.0.6 (the version introducing
20717 HiddenServiceDir); fixes bug 3289.
20718 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
20719 part of bug 2748; bugfix on 0.2.0.10-alpha.
20720 - Log malformed requests for rendezvous descriptors as protocol
20721 warnings, not warnings. Also, use a more informative log message
20722 in case someone sees it at log level warning without prior
20723 info-level messages. Fixes the other part of bug 2748; bugfix
20725 - Clear the table recording the time of the last request for each
20726 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
20727 Previously, we would clear our HS descriptor cache on SIGNAL
20728 NEWNYM, but if we had previously retrieved a descriptor (or tried
20729 to) from every directory responsible for it, we would refuse to
20730 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
20732 - Fix a log message that said "bits" while displaying a value in
20733 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
20735 - When checking for 1024-bit keys, check for 1024 bits, not 128
20736 bytes. This allows Tor to correctly discard keys of length 1017
20737 through 1023. Bugfix on 0.0.9pre5.
20740 - Relays now log the reason for publishing a new relay descriptor,
20741 so we have a better chance of hunting down instances of bug 1810.
20742 Resolves ticket 3252.
20743 - Revise most log messages that refer to nodes by nickname to
20744 instead use the "$key=nickname at address" format. This should be
20745 more useful, especially since nicknames are less and less likely
20746 to be unique. Resolves ticket 3045.
20747 - Log (at info level) when purging pieces of hidden-service-client
20748 state because of SIGNAL NEWNYM.
20751 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20752 anything since 0.2.1.16-rc.
20755 Changes in version 0.2.2.27-beta - 2011-05-18
20756 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
20757 release, and also adds a few more general bugfixes.
20760 - Fix a crash bug when changing bridges in a running Tor process.
20761 Fixes bug 3213; bugfix on 0.2.2.26-beta.
20762 - When the controller configures a new bridge, don't wait 10 to 60
20763 seconds before trying to fetch its descriptor. Bugfix on
20764 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
20767 - Require that onion keys have exponent 65537 in microdescriptors too.
20768 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
20769 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
20770 Changed the limit to 512 characters by removing base64 newlines.
20771 Fixes bug 2752. Fix by Michael Yakubovich.
20772 - When a client starts or stops using bridges, never use a circuit
20773 that was built before the configuration change. This behavior could
20774 put at risk a user who uses bridges to ensure that her traffic
20775 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
20779 Changes in version 0.2.2.26-beta - 2011-05-17
20780 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
20781 also introduces a new "socksport auto" approach that should make it
20782 easier to run multiple Tors on the same system, and does a lot of
20783 cleanup to get us closer to a release candidate.
20785 o Security/privacy fixes:
20786 - Replace all potentially sensitive memory comparison operations
20787 with versions whose runtime does not depend on the data being
20788 compared. This will help resist a class of attacks where an
20789 adversary can use variations in timing information to learn
20790 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20791 implementation by Robert Ransom based partially on code by DJB.)
20792 - When receiving a hidden service descriptor, check that it is for
20793 the hidden service we wanted. Previously, Tor would store any
20794 hidden service descriptors that a directory gave it, whether it
20795 wanted them or not. This wouldn't have let an attacker impersonate
20796 a hidden service, but it did let directories pre-seed a client
20797 with descriptors that it didn't want. Bugfix on 0.0.6.
20798 - On SIGHUP, do not clear out all TrackHostExits mappings, client
20799 DNS cache entries, and virtual address mappings: that's what
20800 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
20803 - The options SocksPort, ControlPort, and so on now all accept a
20804 value "auto" that opens a socket on an OS-selected port. A
20805 new ControlPortWriteToFile option tells Tor to write its
20806 actual control port or ports to a chosen file. If the option
20807 ControlPortFileGroupReadable is set, the file is created as
20808 group-readable. Now users can run two Tor clients on the same
20809 system without needing to manually mess with parameters. Resolves
20810 part of ticket 3076.
20811 - Set SO_REUSEADDR on all sockets, not just listeners. This should
20812 help busy exit nodes avoid running out of useable ports just
20813 because all the ports have been used in the near past. Resolves
20817 - New "GETINFO net/listeners/(type)" controller command to return
20818 a list of addresses and ports that are bound for listeners for a
20819 given connection type. This is useful when the user has configured
20820 "SocksPort auto" and the controller needs to know which port got
20821 chosen. Resolves another part of ticket 3076.
20822 - Add a new ControlSocketsGroupWritable configuration option: when
20823 it is turned on, ControlSockets are group-writeable by the default
20824 group of the current user. Patch by Jérémy Bobbio; implements
20826 - Tor now refuses to create a ControlSocket in a directory that is
20827 world-readable (or group-readable if ControlSocketsGroupWritable
20828 is 0). This is necessary because some operating systems do not
20829 enforce permissions on an AF_UNIX sockets. Permissions on the
20830 directory holding the socket, however, seems to work everywhere.
20831 - Rate-limit a warning about failures to download v2 networkstatus
20832 documents. Resolves part of bug 1352.
20833 - Backport code from 0.2.3.x that allows directory authorities to
20834 clean their microdescriptor caches. Needed to resolve bug 2230.
20835 - When an HTTPS proxy reports "403 Forbidden", we now explain
20836 what it means rather than calling it an unexpected status code.
20837 Closes bug 2503. Patch from Michael Yakubovich.
20838 - Update to the May 1 2011 Maxmind GeoLite Country database.
20841 - Authorities now clean their microdesc cache periodically and when
20842 reading from disk initially, not only when adding new descriptors.
20843 This prevents a bug where we could lose microdescriptors. Bugfix
20844 on 0.2.2.6-alpha. Fixes bug 2230.
20845 - Do not crash when our configuration file becomes unreadable, for
20846 example due to a permissions change, between when we start up
20847 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20849 - Avoid a bug that would keep us from replacing a microdescriptor
20850 cache on Windows. (We would try to replace the file while still
20851 holding it open. That's fine on Unix, but Windows doesn't let us
20852 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
20853 - Add missing explanations for the authority-related torrc options
20854 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
20855 man page. Resolves issue 2379.
20856 - As an authority, do not upload our own vote or signature set to
20857 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
20858 it would get flagged as a duplicate. Resolves bug 3026.
20859 - Accept hidden service descriptors if we think we might be a hidden
20860 service directory, regardless of what our consensus says. This
20861 helps robustness, since clients and hidden services can sometimes
20862 have a more up-to-date view of the network consensus than we do,
20863 and if they think that the directory authorities list us a HSDir,
20864 we might actually be one. Related to bug 2732; bugfix on
20866 - When a controller changes TrackHostExits, remove mappings for
20867 hosts that should no longer have their exits tracked. Bugfix on
20869 - When a controller changes VirtualAddrNetwork, remove any mappings
20870 for hosts that were automapped to the old network. Bugfix on
20872 - When a controller changes one of the AutomapHosts* options, remove
20873 any mappings for hosts that should no longer be automapped. Bugfix
20875 - Do not reset the bridge descriptor download status every time we
20876 re-parse our configuration or get a configuration change. Fixes
20877 bug 3019; bugfix on 0.2.0.3-alpha.
20879 o Minor bugfixes (code cleanup):
20880 - When loading the microdesc journal, remember its current size.
20881 In 0.2.2, this helps prevent the microdesc journal from growing
20882 without limit on authorities (who are the only ones to use it in
20883 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
20884 Fix posted by "cypherpunks."
20885 - The microdesc journal is supposed to get rebuilt only if it is
20886 at least _half_ the length of the store, not _twice_ the length
20887 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
20888 - Fix a potential null-pointer dereference while computing a
20889 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
20891 - Avoid a possible null-pointer dereference when rebuilding the mdesc
20892 cache without actually having any descriptors to cache. Bugfix on
20893 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
20894 - If we fail to compute the identity digest of a v3 legacy keypair,
20895 warn, and don't use a buffer-full of junk instead. Bugfix on
20896 0.2.1.1-alpha; fixes bug 3106.
20897 - Resolve an untriggerable issue in smartlist_string_num_isin(),
20898 where if the function had ever in the future been used to check
20899 for the presence of a too-large number, it would have given an
20900 incorrect result. (Fortunately, we only used it for 16-bit
20901 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
20902 - Require that introduction point keys and onion handshake keys
20903 have a public exponent of 65537. Starts to fix bug 3207; bugfix
20906 o Removed features:
20907 - Caches no longer download and serve v2 networkstatus documents
20908 unless FetchV2Networkstatus flag is set: these documents haven't
20909 haven't been used by clients or relays since 0.2.0.x. Resolves
20913 Changes in version 0.2.3.1-alpha - 2011-05-05
20914 Tor 0.2.3.1-alpha adds some new experimental features, including support
20915 for an improved network IO backend, IOCP networking on Windows,
20916 microdescriptor caching, "fast-start" support for streams, and automatic
20917 home router configuration. There are also numerous internal improvements
20918 to try to make the code easier for developers to work with.
20920 This is the first alpha release in a new series, so expect there to be
20921 bugs. Users who would rather test out a more stable branch should
20922 stay with 0.2.2.x for now.
20925 - Tor can now optionally build with the "bufferevents" buffered IO
20926 backend provided by Libevent 2. To use this feature, make sure you
20927 have the latest possible version of Libevent, and pass the
20928 --enable-bufferevents flag to configure when building Tor from
20929 source. This feature will make our networking code more flexible,
20930 let us stack layers on each other, and let us use more efficient
20931 zero-copy transports where available.
20932 - As an experimental feature, Tor can use IOCP for networking on Windows.
20933 Once this code is tuned and optimized, it promises much better
20934 performance than the select-based backend we've used in the past. To
20935 try this feature, you must build Tor with Libevent 2, configure Tor
20936 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
20937 your torrc. There are known bugs here: only try this if you can help
20938 debug it as it breaks.
20939 - The EntryNodes option can now include country codes like {de} or IP
20940 addresses or network masks. Previously we had disallowed these options
20941 because we didn't have an efficient way to keep the list up to
20942 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
20943 - Exit nodes now accept and queue data on not-yet-connected streams.
20944 Previously, the client wasn't allowed to send data until the stream was
20945 connected, which slowed down all connections. This change will enable
20946 clients to perform a "fast-start" on streams and send data without
20947 having to wait for a confirmation that the stream has opened. (Patch
20948 from Ian Goldberg; implements the server side of Proposal 174.)
20949 - Tor now has initial support for automatic port mapping on the many
20950 home routers that support NAT-PMP or UPnP. (Not yet supported on
20951 Windows). To build the support code, you'll need to have libnatpnp
20952 library and/or the libminiupnpc library, and you'll need to enable the
20953 feature specifically by passing "--enable-upnp" and/or
20954 "--enable-natpnp" to configure. To turn it on, use the new
20955 PortForwarding option.
20956 - Caches now download, cache, and serve multiple "flavors" of the
20957 consensus, including a flavor that describes microdescriptors.
20958 - Caches now download, cache, and serve microdescriptors -- small
20959 summaries of router descriptors that are authenticated by all of the
20960 directory authorities. Once enough caches are running this code,
20961 clients will be able to save significant amounts of directory bandwidth
20962 by downloading microdescriptors instead of router descriptors.
20965 - Make logging resolution configurable with a new LogTimeGranularity
20966 option, and change the default from 1 millisecond to 1 second.
20967 Implements enhancement 1668.
20968 - We log which torrc file we're using on startup. Implements ticket
20970 - Ordinarily, Tor does not count traffic from private addresses (like
20971 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
20972 There is now a new option, CountPrivateBandwidth, to disable this
20973 behavior. Patch from Daniel Cagara.
20974 - New --enable-static-tor configure option for building Tor as
20975 statically as possible. Idea, general hackery and thoughts from
20976 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
20978 - If you set the NumCPUs option to 0, Tor will now try to detect how
20979 many CPUs you have. This is the new default behavior.
20980 - Turn on directory request statistics by default and include them in
20981 extra-info descriptors. Don't break if we have no GeoIP database.
20982 - Relays that set "ConnDirectionStatistics 1" write statistics on the
20983 bidirectional use of connections to disk every 24 hours.
20984 - Add a GeoIP file digest to the extra-info descriptor. Implements
20986 - The NodeFamily option -- which let you declare that you want to
20987 consider nodes to be part of a family whether they list themselves
20988 that way or not -- now allows IP address ranges and country codes.
20989 - Add a new 'Heartbeat' log message type to periodically log a message
20990 describing Tor's status at level Notice. This feature is meant for
20991 operators who log at notice, and want to make sure that their Tor
20992 server is still working. Implementation by George Kadianakis.
20994 o Minor bugfixes (on 0.2.2.25-alpha):
20995 - When loading the microdesc journal, remember its current size.
20996 In 0.2.2, this helps prevent the microdesc journal from growing
20997 without limit on authorities (who are the only ones to use it in
20998 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
20999 Fix posted by "cypherpunks."
21000 - The microdesc journal is supposed to get rebuilt only if it is
21001 at least _half_ the length of the store, not _twice_ the length
21002 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21003 - If as an authority we fail to compute the identity digest of a v3
21004 legacy keypair, warn, and don't use a buffer-full of junk instead.
21005 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
21006 - Authorities now clean their microdesc cache periodically and when
21007 reading from disk initially, not only when adding new descriptors.
21008 This prevents a bug where we could lose microdescriptors. Bugfix
21011 o Minor features (controller):
21012 - Add a new SIGNAL event to the controller interface so that
21013 controllers can be notified when Tor handles a signal. Resolves
21014 issue 1955. Patch by John Brooks.
21015 - Add a new GETINFO option to get total bytes read and written. Patch
21016 from pipe, revised by atagar. Resolves ticket 2345.
21017 - Implement some GETINFO controller fields to provide information about
21018 the Tor process's pid, euid, username, and resource limits.
21021 - Our build system requires automake 1.6 or later to create the
21022 Makefile.in files. Previously, you could have used 1.4.
21023 This only affects developers and people building Tor from git;
21024 people who build Tor from the source distribution without changing
21025 the Makefile.am files should be fine.
21026 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
21027 so on. This is more robust against some of the failure modes
21028 associated with running the autotools pieces on their own.
21030 o Minor packaging issues:
21031 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
21032 already created. Patch from Andreas Stieger. Fixes bug 2573.
21034 o Code simplifications and refactoring:
21035 - A major revision to our internal node-selecting and listing logic.
21036 Tor already had at least two major ways to look at the question of
21037 "which Tor servers do we know about": a list of router descriptors,
21038 and a list of entries in the current consensus. With
21039 microdescriptors, we're adding a third. Having so many systems
21040 without an abstraction layer over them was hurting the codebase.
21041 Now, we have a new "node_t" abstraction that presents a consistent
21042 interface to a client's view of a Tor node, and holds (nearly) all
21043 of the mutable state formerly in routerinfo_t and routerstatus_t.
21044 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
21045 no longer link against Libevent: they never used it, but
21046 our library structure used to force them to link it.
21048 o Removed features:
21049 - Remove some old code to work around even older versions of Tor that
21050 used forked processes to handle DNS requests. Such versions of Tor
21051 are no longer in use as servers.
21053 o Documentation fixes:
21054 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
21055 - Add missing documentation for the authority-related torrc options
21056 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
21060 Changes in version 0.2.2.25-alpha - 2011-04-29
21061 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
21062 robust, routers no longer overreport their bandwidth, Win7 should crash
21063 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
21064 now prevents hidden service-related activity from being linkable. It
21065 provides more information to Vidalia so you can see if your bridge is
21066 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
21067 StrictNodes configuration options to make them more reliable, more
21068 understandable, and more regularly applied. If you use those options,
21069 please see the revised documentation for them in the manual page.
21072 - Relays were publishing grossly inflated bandwidth values because
21073 they were writing their state files wrong--now they write the
21074 correct value. Also, resume reading bandwidth history from the
21075 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
21076 - Improve hidden service robustness: When we find that we have
21077 extended a hidden service's introduction circuit to a relay not
21078 listed as an introduction point in the HS descriptor we currently
21079 have, retry with an introduction point from the current
21080 descriptor. Previously we would just give up. Fixes bugs 1024 and
21081 1930; bugfix on 0.2.0.10-alpha.
21082 - Clients now stop trying to use an exit node associated with a given
21083 destination by TrackHostExits if they fail to reach that exit node.
21084 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
21085 - Fix crash bug on platforms where gmtime and localtime can return
21086 NULL. Windows 7 users were running into this one. Fixes part of bug
21087 2077. Bugfix on all versions of Tor. Found by boboper.
21089 o Security and stability fixes:
21090 - Don't double-free a parsable, but invalid, microdescriptor, even if
21091 it is followed in the blob we're parsing by an unparsable
21092 microdescriptor. Fixes an issue reported in a comment on bug 2954.
21093 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
21094 - If the Nickname configuration option isn't given, Tor would pick a
21095 nickname based on the local hostname as the nickname for a relay.
21096 Because nicknames are not very important in today's Tor and the
21097 "Unnamed" nickname has been implemented, this is now problematic
21098 behavior: It leaks information about the hostname without being
21099 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
21100 introduced the Unnamed nickname. Reported by tagnaq.
21101 - Fix an uncommon assertion failure when running with DNSPort under
21102 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
21103 - Avoid linkability based on cached hidden service descriptors: forget
21104 all hidden service descriptors cached as a client when processing a
21105 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
21108 - Export GeoIP information on bridge usage to controllers even if we
21109 have not yet been running for 24 hours. Now Vidalia bridge operators
21110 can get more accurate and immediate feedback about their
21111 contributions to the network.
21113 o Major features and bugfixes (node selection):
21114 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
21115 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
21116 options. Previously, we had been ambiguous in describing what
21117 counted as an "exit" node, and what operations exactly "StrictNodes
21118 0" would permit. This created confusion when people saw nodes built
21119 through unexpected circuits, and made it hard to tell real bugs from
21120 surprises. Now the intended behavior is:
21121 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
21122 a node that delivers user traffic outside the Tor network.
21123 . "Entry", in the context of EntryNodes, means a node used as the
21124 first hop of a multihop circuit. It doesn't include direct
21125 connections to directory servers.
21126 . "ExcludeNodes" applies to all nodes.
21127 . "StrictNodes" changes the behavior of ExcludeNodes only. When
21128 StrictNodes is set, Tor should avoid all nodes listed in
21129 ExcludeNodes, even when it will make user requests fail. When
21130 StrictNodes is *not* set, then Tor should follow ExcludeNodes
21131 whenever it can, except when it must use an excluded node to
21132 perform self-tests, connect to a hidden service, provide a
21133 hidden service, fulfill a .exit request, upload directory
21134 information, or fetch directory information.
21135 Collectively, the changes to implement the behavior fix bug 1090.
21136 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
21137 a node is listed in both, it's treated as excluded.
21138 - ExcludeNodes now applies to directory nodes -- as a preference if
21139 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
21140 Don't exclude all the directory authorities and set StrictNodes to 1
21141 unless you really want your Tor to break.
21142 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
21143 - ExcludeExitNodes now overrides .exit requests.
21144 - We don't use bridges listed in ExcludeNodes.
21145 - When StrictNodes is 1:
21146 . We now apply ExcludeNodes to hidden service introduction points
21147 and to rendezvous points selected by hidden service users. This
21148 can make your hidden service less reliable: use it with caution!
21149 . If we have used ExcludeNodes on ourself, do not try relay
21150 reachability self-tests.
21151 . If we have excluded all the directory authorities, we will not
21152 even try to upload our descriptor if we're a relay.
21153 . Do not honor .exit requests to an excluded node.
21154 - Remove a misfeature that caused us to ignore the Fast/Stable flags
21155 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
21156 - When the set of permitted nodes changes, we now remove any mappings
21157 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
21159 - We never cannibalize a circuit that had excluded nodes on it, even
21160 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
21161 - Revert a change where we would be laxer about attaching streams to
21162 circuits than when building the circuits. This was meant to prevent
21163 a set of bugs where streams were never attachable, but our improved
21164 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
21165 - Keep track of how many times we launch a new circuit to handle a
21166 given stream. Too many launches could indicate an inconsistency
21167 between our "launch a circuit to handle this stream" logic and our
21168 "attach this stream to one of the available circuits" logic.
21169 - Improve log messages related to excluded nodes.
21172 - Fix a spurious warning when moving from a short month to a long
21173 month on relays with month-based BandwidthAccounting. Bugfix on
21174 0.2.2.17-alpha; fixes bug 3020.
21175 - When a client finds that an origin circuit has run out of 16-bit
21176 stream IDs, we now mark it as unusable for new streams. Previously,
21177 we would try to close the entire circuit. Bugfix on 0.0.6.
21178 - Add a forgotten cast that caused a compile warning on OS X 10.6.
21179 Bugfix on 0.2.2.24-alpha.
21180 - Be more careful about reporting the correct error from a failed
21181 connect() system call. Under some circumstances, it was possible to
21182 look at an incorrect value for errno when sending the end reason.
21183 Bugfix on 0.1.0.1-rc.
21184 - Correctly handle an "impossible" overflow cases in connection byte
21185 counting, where we write or read more than 4GB on an edge connection
21186 in a single second. Bugfix on 0.1.2.8-beta.
21187 - Correct the warning displayed when a rendezvous descriptor exceeds
21188 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21190 - Clients and hidden services now use HSDir-flagged relays for hidden
21191 service descriptor downloads and uploads even if the relays have no
21192 DirPort set and the client has disabled TunnelDirConns. This will
21193 eventually allow us to give the HSDir flag to relays with no
21194 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
21195 - Downgrade "no current certificates known for authority" message from
21196 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
21197 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
21198 2917. Bugfix on 0.1.1.1-alpha.
21199 - Only limit the lengths of single HS descriptors, even when multiple
21200 HS descriptors are published to an HSDir relay in a single POST
21201 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
21202 - Write the current time into the LastWritten line in our state file,
21203 rather than the time from the previous write attempt. Also, stop
21204 trying to use a time of -1 in our log statements. Fixes bug 3039;
21205 bugfix on 0.2.2.14-alpha.
21206 - Be more consistent in our treatment of file system paths. "~" should
21207 get expanded to the user's home directory in the Log config option.
21208 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
21209 feature for the -f and --DataDirectory options.
21212 - Make sure every relay writes a state file at least every 12 hours.
21213 Previously, a relay could go for weeks without writing its state
21214 file, and on a crash could lose its bandwidth history, capacity
21215 estimates, client country statistics, and so on. Addresses bug 3012.
21216 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
21217 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
21218 clients are already deprecated because of security bugs.
21219 - Don't allow v0 hidden service authorities to act as clients.
21220 Required by fix for bug 3000.
21221 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
21222 by fix for bug 3000.
21223 - Ensure that no empty [dirreq-](read|write)-history lines are added
21224 to an extrainfo document. Implements ticket 2497.
21226 o Code simplification and refactoring:
21227 - Remove workaround code to handle directory responses from servers
21228 that had bug 539 (they would send HTTP status 503 responses _and_
21229 send a body too). Since only server versions before
21230 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
21231 keep the workaround in place.
21232 - Remove the old 'fuzzy time' logic. It was supposed to be used for
21233 handling calculations where we have a known amount of clock skew and
21234 an allowed amount of unknown skew. But we only used it in three
21235 places, and we never adjusted the known/unknown skew values. This is
21236 still something we might want to do someday, but if we do, we'll
21237 want to do it differently.
21238 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
21239 None of the cases where we did this before were wrong, but by making
21240 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
21241 - Use GetTempDir to find the proper temporary directory location on
21242 Windows when generating temporary files for the unit tests. Patch by
21246 Changes in version 0.2.2.24-alpha - 2011-04-08
21247 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
21248 prevented Tor clients from effectively using "multihomed" bridges,
21249 that is, bridges that listen on multiple ports or IP addresses so users
21250 can continue to use some of their addresses even if others get blocked.
21253 - Fix a bug where bridge users who configure the non-canonical
21254 address of a bridge automatically switch to its canonical
21255 address. If a bridge listens at more than one address, it should be
21256 able to advertise those addresses independently and any non-blocked
21257 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
21259 - If you configured Tor to use bridge A, and then quit and
21260 configured Tor to use bridge B instead, it would happily continue
21261 to use bridge A if it's still reachable. While this behavior is
21262 a feature if your goal is connectivity, in some scenarios it's a
21263 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
21264 - Directory authorities now use data collected from their own
21265 uptime observations when choosing whether to assign the HSDir flag
21266 to relays, instead of trusting the uptime value the relay reports in
21267 its descriptor. This change helps prevent an attack where a small
21268 set of nodes with frequently-changing identity keys can blackhole
21269 a hidden service. (Only authorities need upgrade; others will be
21270 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
21273 - When we restart our relay, we might get a successful connection
21274 from the outside before we've started our reachability tests,
21275 triggering a warning: "ORPort found reachable, but I have no
21276 routerinfo yet. Failing to inform controller of success." This
21277 bug was harmless unless Tor is running under a controller
21278 like Vidalia, in which case the controller would never get a
21279 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
21281 - Make directory authorities more accurate at recording when
21282 relays that have failed several reachability tests became
21283 unreachable, so we can provide more accuracy at assigning Stable,
21284 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
21285 - Fix an issue that prevented static linking of libevent on
21286 some platforms (notably Linux). Fixes bug 2698; bugfix on
21287 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
21288 the --with-static-libevent configure option).
21289 - We now ask the other side of a stream (the client or the exit)
21290 for more data on that stream when the amount of queued data on
21291 that stream dips low enough. Previously, we wouldn't ask the
21292 other side for more data until either it sent us more data (which
21293 it wasn't supposed to do if it had exhausted its window!) or we
21294 had completely flushed all our queued data. This flow control fix
21295 should improve throughput. Fixes bug 2756; bugfix on the earliest
21296 released versions of Tor (svn commit r152).
21297 - Avoid a double-mark-for-free warning when failing to attach a
21298 transparent proxy connection. (We thought we had fixed this in
21299 0.2.2.23-alpha, but it turns out our fix was checking the wrong
21300 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
21301 bug) and 0.2.2.23-alpha (the incorrect fix).
21302 - When warning about missing zlib development packages during compile,
21303 give the correct package names. Bugfix on 0.2.0.1-alpha.
21306 - Directory authorities now log the source of a rejected POSTed v3
21307 networkstatus vote.
21308 - Make compilation with clang possible when using
21309 --enable-gcc-warnings by removing two warning options that clang
21310 hasn't implemented yet and by fixing a few warnings. Implements
21312 - When expiring circuits, use microsecond timers rather than
21313 one-second timers. This can avoid an unpleasant situation where a
21314 circuit is launched near the end of one second and expired right
21315 near the beginning of the next, and prevent fluctuations in circuit
21317 - Use computed circuit-build timeouts to decide when to launch
21318 parallel introduction circuits for hidden services. (Previously,
21319 we would retry after 15 seconds.)
21320 - Update to the April 1 2011 Maxmind GeoLite Country database.
21323 - Create the /var/run/tor directory on startup on OpenSUSE if it is
21324 not already created. Patch from Andreas Stieger. Fixes bug 2573.
21326 o Documentation changes:
21327 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
21328 - Resolve all doxygen warnings except those for missing documentation.
21330 - Add doxygen documentation for more functions, fields, and types.
21333 Changes in version 0.2.2.23-alpha - 2011-03-08
21334 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
21335 they restart they don't lose their bandwidth capacity estimate. This
21336 release also fixes a diverse set of user-facing bugs, ranging from
21337 relays overrunning their rate limiting to clients falsely warning about
21338 clock skew to bridge descriptor leaks by our bridge directory authority.
21341 - Stop sending a CLOCK_SKEW controller status event whenever
21342 we fetch directory information from a relay that has a wrong clock.
21343 Instead, only inform the controller when it's a trusted authority
21344 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
21345 the rest of bug 1074.
21346 - Fix an assert in parsing router descriptors containing IPv6
21347 addresses. This one took down the directory authorities when
21348 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
21349 - Make the bridge directory authority refuse to answer directory
21350 requests for "all" descriptors. It used to include bridge
21351 descriptors in its answer, which was a major information leak.
21352 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
21353 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
21354 Tor would ignore their RelayBandwidthBurst setting,
21355 potentially using more bandwidth than expected. Bugfix on
21356 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
21357 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
21358 hidserv" in her torrc. The 'hidserv' argument never controlled
21359 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
21362 - Relays now save observed peak bandwidth throughput rates to their
21363 state file (along with total usage, which was already saved)
21364 so that they can determine their correct estimated bandwidth on
21365 restart. Resolves bug 1863, where Tor relays would reset their
21366 estimated bandwidth to 0 after restarting.
21367 - Directory authorities now take changes in router IP address and
21368 ORPort into account when determining router stability. Previously,
21369 if a router changed its IP or ORPort, the authorities would not
21370 treat it as having any downtime for the purposes of stability
21371 calculation, whereas clients would experience downtime since the
21372 change could take a while to propagate to them. Resolves issue 1035.
21373 - Enable Address Space Layout Randomization (ASLR) and Data Execution
21374 Prevention (DEP) by default on Windows to make it harder for
21375 attackers to exploit vulnerabilities. Patch from John Brooks.
21377 o Minor bugfixes (on 0.2.1.x and earlier):
21378 - Fix a rare crash bug that could occur when a client was configured
21379 with a large number of bridges. Fixes bug 2629; bugfix on
21380 0.2.1.2-alpha. Bugfix by trac user "shitlei".
21381 - Avoid a double mark-for-free warning when failing to attach a
21382 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
21384 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
21385 found by "cypherpunks". This bug was introduced before the first
21386 Tor release, in svn commit r110.
21387 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
21388 don't mention them in the manpage. Fixes bug 2450; issue
21389 spotted by keb and G-Lo.
21390 - Fix a bug in bandwidth history state parsing that could have been
21391 triggered if a future version of Tor ever changed the timing
21392 granularity at which bandwidth history is measured. Bugfix on
21393 Tor 0.1.1.11-alpha.
21394 - When a relay decides that its DNS is too broken for it to serve
21395 as an exit server, it advertised itself as a non-exit, but
21396 continued to act as an exit. This could create accidental
21397 partitioning opportunities for users. Instead, if a relay is
21398 going to advertise reject *:* as its exit policy, it should
21399 really act with exit policy "reject *:*". Fixes bug 2366.
21400 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
21401 - In the special case where you configure a public exit relay as your
21402 bridge, Tor would be willing to use that exit relay as the last
21403 hop in your circuit as well. Now we fail that circuit instead.
21404 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
21405 - Fix a bug with our locking implementation on Windows that couldn't
21406 correctly detect when a file was already locked. Fixes bug 2504,
21407 bugfix on 0.2.1.6-alpha.
21408 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
21409 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
21411 - Set target port in get_interface_address6() correctly. Bugfix
21412 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
21413 - Directory authorities are now more robust to hops back in time
21414 when calculating router stability. Previously, if a run of uptime
21415 or downtime appeared to be negative, the calculation could give
21416 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
21418 - Fix an assert that got triggered when using the TestingTorNetwork
21419 configuration option and then issuing a GETINFO config-text control
21420 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
21422 o Minor bugfixes (on 0.2.2.x):
21423 - Clients should not weight BadExit nodes as Exits in their node
21424 selection. Similarly, directory authorities should not count BadExit
21425 bandwidth as Exit bandwidth when computing bandwidth-weights.
21426 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
21427 - Correctly clear our dir_read/dir_write history when there is an
21428 error parsing any bw history value from the state file. Bugfix on
21429 Tor 0.2.2.15-alpha.
21430 - Resolve a bug in verifying signatures of directory objects
21431 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
21432 Fixes bug 2409. Found by "piebeer".
21433 - Bridge authorities no longer crash on SIGHUP when they try to
21434 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
21438 - Log less aggressively about circuit timeout changes, and improve
21439 some other circuit timeout messages. Resolves bug 2004.
21440 - Log a little more clearly about the times at which we're no longer
21441 accepting new connections. Resolves bug 2181.
21442 - Reject attempts at the client side to open connections to private
21443 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
21444 a randomly chosen exit node. Attempts to do so are always
21445 ill-defined, generally prevented by exit policies, and usually
21446 in error. This will also help to detect loops in transparent
21447 proxy configurations. You can disable this feature by setting
21448 "ClientRejectInternalAddresses 0" in your torrc.
21449 - Always treat failure to allocate an RSA key as an unrecoverable
21451 - Update to the March 1 2011 Maxmind GeoLite Country database.
21453 o Minor features (log subsystem):
21454 - Add documentation for configuring logging at different severities in
21455 different log domains. We've had this feature since 0.2.1.1-alpha,
21456 but for some reason it never made it into the manpage. Fixes
21458 - Make it simpler to specify "All log domains except for A and B".
21459 Previously you needed to say "[*,~A,~B]". Now you can just say
21461 - Add a "LogMessageDomains 1" option to include the domains of log
21462 messages along with the messages. Without this, there's no way
21463 to use log domains without reading the source or doing a lot
21466 o Packaging changes:
21467 - Stop shipping the Tor specs files and development proposal documents
21468 in the tarball. They are now in a separate git repository at
21469 git://git.torproject.org/torspec.git
21472 Changes in version 0.2.1.30 - 2011-02-23
21473 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
21474 change is a slight tweak to Tor's TLS handshake that makes relays
21475 and bridges that run this new version reachable from Iran again.
21476 We don't expect this tweak will win the arms race long-term, but it
21477 buys us time until we roll out a better solution.
21480 - Stop sending a CLOCK_SKEW controller status event whenever
21481 we fetch directory information from a relay that has a wrong clock.
21482 Instead, only inform the controller when it's a trusted authority
21483 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
21484 the rest of bug 1074.
21485 - Fix a bounds-checking error that could allow an attacker to
21486 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
21487 Found by "piebeer".
21488 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
21489 Tor would ignore their RelayBandwidthBurst setting,
21490 potentially using more bandwidth than expected. Bugfix on
21491 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
21492 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
21493 hidserv" in her torrc. The 'hidserv' argument never controlled
21494 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
21497 - Adjust our TLS Diffie-Hellman parameters to match those used by
21499 - Update to the February 1 2011 Maxmind GeoLite Country database.
21502 - Check for and reject overly long directory certificates and
21503 directory tokens before they have a chance to hit any assertions.
21504 Bugfix on 0.2.1.28. Found by "doorss".
21505 - Bring the logic that gathers routerinfos and assesses the
21506 acceptability of circuits into line. This prevents a Tor OP from
21507 getting locked in a cycle of choosing its local OR as an exit for a
21508 path (due to a .exit request) and then rejecting the circuit because
21509 its OR is not listed yet. It also prevents Tor clients from using an
21510 OR running in the same instance as an exit (due to a .exit request)
21511 if the OR does not meet the same requirements expected of an OR
21512 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
21514 o Packaging changes:
21515 - Stop shipping the Tor specs files and development proposal documents
21516 in the tarball. They are now in a separate git repository at
21517 git://git.torproject.org/torspec.git
21518 - Do not include Git version tags as though they are SVN tags when
21519 generating a tarball from inside a repository that has switched
21520 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
21523 Changes in version 0.2.2.22-alpha - 2011-01-25
21524 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
21525 main other change is a slight tweak to Tor's TLS handshake that makes
21526 relays and bridges that run this new version reachable from Iran again.
21527 We don't expect this tweak will win the arms race long-term, but it
21528 will buy us a bit more time until we roll out a better solution.
21531 - Fix a bounds-checking error that could allow an attacker to
21532 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
21533 Found by "piebeer".
21534 - Don't assert when changing from bridge to relay or vice versa
21535 via the controller. The assert happened because we didn't properly
21536 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
21537 bug 2433. Reported by bastik.
21540 - Adjust our TLS Diffie-Hellman parameters to match those used by
21542 - Provide a log message stating which geoip file we're parsing
21543 instead of just stating that we're parsing the geoip file.
21544 Implements ticket 2432.
21547 - Check for and reject overly long directory certificates and
21548 directory tokens before they have a chance to hit any assertions.
21549 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
21552 Changes in version 0.2.2.21-alpha - 2011-01-15
21553 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
21554 continues our recent code security audit work. The main fix resolves
21555 a remote heap overflow vulnerability that can allow remote code
21556 execution (CVE-2011-0427). Other fixes address a variety of assert
21557 and crash bugs, most of which we think are hard to exploit remotely.
21559 o Major bugfixes (security), also included in 0.2.1.29:
21560 - Fix a heap overflow bug where an adversary could cause heap
21561 corruption. This bug probably allows remote code execution
21562 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
21564 - Prevent a denial-of-service attack by disallowing any
21565 zlib-compressed data whose compression factor is implausibly
21566 high. Fixes part of bug 2324; reported by "doorss".
21567 - Zero out a few more keys in memory before freeing them. Fixes
21568 bug 2384 and part of bug 2385. These key instances found by
21569 "cypherpunks", based on Andrew Case's report about being able
21570 to find sensitive data in Tor's memory space if you have enough
21571 permissions. Bugfix on 0.0.2pre9.
21573 o Major bugfixes (crashes), also included in 0.2.1.29:
21574 - Prevent calls to Libevent from inside Libevent log handlers.
21575 This had potential to cause a nasty set of crashes, especially
21576 if running Libevent with debug logging enabled, and running
21577 Tor with a controller watching for low-severity log messages.
21578 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
21579 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
21580 underflow errors there too. Fixes the other part of bug 2324.
21581 - Fix a bug where we would assert if we ever had a
21582 cached-descriptors.new file (or another file read directly into
21583 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
21584 on 0.2.1.25. Found by doorss.
21585 - Fix some potential asserts and parsing issues with grossly
21586 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
21589 o Minor bugfixes (other), also included in 0.2.1.29:
21590 - Fix a bug with handling misformed replies to reverse DNS lookup
21591 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
21592 bug reported by doorss.
21593 - Fix compilation on mingw when a pthreads compatibility library
21594 has been installed. (We don't want to use it, so we shouldn't
21595 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
21596 - Fix a bug where we would declare that we had run out of virtual
21597 addresses when the address space was only half-exhausted. Bugfix
21599 - Correctly handle the case where AutomapHostsOnResolve is set but
21600 no virtual addresses are available. Fixes bug 2328; bugfix on
21601 0.1.2.1-alpha. Bug found by doorss.
21602 - Correctly handle wrapping around when we run out of virtual
21603 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
21605 o Minor features, also included in 0.2.1.29:
21606 - Update to the January 1 2011 Maxmind GeoLite Country database.
21607 - Introduce output size checks on all of our decryption functions.
21609 o Build changes, also included in 0.2.1.29:
21610 - Tor does not build packages correctly with Automake 1.6 and earlier;
21611 added a check to Makefile.am to make sure that we're building with
21612 Automake 1.7 or later.
21613 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
21614 because we built it with a too-old version of automake. Thus that
21615 release broke ./configure --enable-openbsd-malloc, which is popular
21616 among really fast exit relays on Linux.
21618 o Major bugfixes, new in 0.2.2.21-alpha:
21619 - Prevent crash/heap corruption when the cbtnummodes consensus
21620 parameter is set to 0 or large values. Fixes bug 2317; bugfix
21623 o Major features, new in 0.2.2.21-alpha:
21624 - Introduce minimum/maximum values that clients will believe
21625 from the consensus. Now we'll have a better chance to avoid crashes
21626 or worse when a consensus param has a weird value.
21628 o Minor features, new in 0.2.2.21-alpha:
21629 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
21630 used on bridges, and it makes bridge scanning somewhat easier.
21631 - If writing the state file to disk fails, wait up to an hour before
21632 retrying again, rather than trying again each second. Fixes bug
21633 2346; bugfix on Tor 0.1.1.3-alpha.
21634 - Make Libevent log messages get delivered to controllers later,
21635 and not from inside the Libevent log handler. This prevents unsafe
21636 reentrant Libevent calls while still letting the log messages
21638 - Detect platforms that brokenly use a signed size_t, and refuse to
21639 build there. Found and analyzed by doorss and rransom.
21640 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
21643 o Minor bugfixes, new in 0.2.2.21-alpha:
21644 - Handle SOCKS messages longer than 128 bytes long correctly, rather
21645 than waiting forever for them to finish. Fixes bug 2330; bugfix
21646 on 0.2.0.16-alpha. Found by doorss.
21647 - Add assertions to check for overflow in arguments to
21648 base32_encode() and base32_decode(); fix a signed-unsigned
21649 comparison there too. These bugs are not actually reachable in Tor,
21650 but it's good to prevent future errors too. Found by doorss.
21651 - Correctly detect failures to create DNS requests when using Libevent
21652 versions before v2. (Before Libevent 2, we used our own evdns
21653 implementation. Its return values for Libevent's evdns_resolve_*()
21654 functions are not consistent with those from Libevent.) Fixes bug
21655 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
21657 o Documentation, new in 0.2.2.21-alpha:
21658 - Document the default socks host and port (127.0.0.1:9050) for
21662 Changes in version 0.2.1.29 - 2011-01-15
21663 Tor 0.2.1.29 continues our recent code security audit work. The main
21664 fix resolves a remote heap overflow vulnerability that can allow remote
21665 code execution. Other fixes address a variety of assert and crash bugs,
21666 most of which we think are hard to exploit remotely.
21668 o Major bugfixes (security):
21669 - Fix a heap overflow bug where an adversary could cause heap
21670 corruption. This bug probably allows remote code execution
21671 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
21673 - Prevent a denial-of-service attack by disallowing any
21674 zlib-compressed data whose compression factor is implausibly
21675 high. Fixes part of bug 2324; reported by "doorss".
21676 - Zero out a few more keys in memory before freeing them. Fixes
21677 bug 2384 and part of bug 2385. These key instances found by
21678 "cypherpunks", based on Andrew Case's report about being able
21679 to find sensitive data in Tor's memory space if you have enough
21680 permissions. Bugfix on 0.0.2pre9.
21682 o Major bugfixes (crashes):
21683 - Prevent calls to Libevent from inside Libevent log handlers.
21684 This had potential to cause a nasty set of crashes, especially
21685 if running Libevent with debug logging enabled, and running
21686 Tor with a controller watching for low-severity log messages.
21687 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
21688 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
21689 underflow errors there too. Fixes the other part of bug 2324.
21690 - Fix a bug where we would assert if we ever had a
21691 cached-descriptors.new file (or another file read directly into
21692 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
21693 on 0.2.1.25. Found by doorss.
21694 - Fix some potential asserts and parsing issues with grossly
21695 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
21698 o Minor bugfixes (other):
21699 - Fix a bug with handling misformed replies to reverse DNS lookup
21700 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
21701 bug reported by doorss.
21702 - Fix compilation on mingw when a pthreads compatibility library
21703 has been installed. (We don't want to use it, so we shouldn't
21704 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
21705 - Fix a bug where we would declare that we had run out of virtual
21706 addresses when the address space was only half-exhausted. Bugfix
21708 - Correctly handle the case where AutomapHostsOnResolve is set but
21709 no virtual addresses are available. Fixes bug 2328; bugfix on
21710 0.1.2.1-alpha. Bug found by doorss.
21711 - Correctly handle wrapping around to when we run out of virtual
21712 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
21713 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
21714 because we built it with a too-old version of automake. Thus that
21715 release broke ./configure --enable-openbsd-malloc, which is popular
21716 among really fast exit relays on Linux.
21719 - Update to the January 1 2011 Maxmind GeoLite Country database.
21720 - Introduce output size checks on all of our decryption functions.
21723 - Tor does not build packages correctly with Automake 1.6 and earlier;
21724 added a check to Makefile.am to make sure that we're building with
21725 Automake 1.7 or later.
21728 Changes in version 0.2.2.20-alpha - 2010-12-17
21729 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
21730 exploitable bugs. We also fix a variety of other significant bugs,
21731 change the IP address for one of our directory authorities, and update
21732 the minimum version that Tor relays must run to join the network.
21735 - Fix a remotely exploitable bug that could be used to crash instances
21736 of Tor remotely by overflowing on the heap. Remote-code execution
21737 hasn't been confirmed, but can't be ruled out. Everyone should
21738 upgrade. Bugfix on the 0.1.1 series and later.
21739 - Fix a bug that could break accounting on 64-bit systems with large
21740 time_t values, making them hibernate for impossibly long intervals.
21741 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
21742 - Fix a logic error in directory_fetches_from_authorities() that
21743 would cause all _non_-exits refusing single-hop-like circuits
21744 to fetch from authorities, when we wanted to have _exits_ fetch
21745 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
21747 - Fix a stream fairness bug that would cause newer streams on a given
21748 circuit to get preference when reading bytes from the origin or
21749 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
21750 introduced before the first Tor release, in svn revision r152.
21752 o Directory authority changes:
21753 - Change IP address and ports for gabelmoo (v3 directory authority).
21756 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
21757 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
21758 - Fix an off-by-one error in calculating some controller command
21759 argument lengths. Fortunately, this mistake is harmless since
21760 the controller code does redundant NUL termination too. Found by
21761 boboper. Bugfix on 0.1.1.1-alpha.
21762 - Do not dereference NULL if a bridge fails to build its
21763 extra-info descriptor. Found by an anonymous commenter on
21764 Trac. Bugfix on 0.2.2.19-alpha.
21767 - Update to the December 1 2010 Maxmind GeoLite Country database.
21768 - Directory authorities now reject relays running any versions of
21769 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
21770 known bugs that keep RELAY_EARLY cells from working on rendezvous
21771 circuits. Followup to fix for bug 2081.
21772 - Directory authorities now reject relays running any version of Tor
21773 older than 0.2.0.26-rc. That version is the earliest that fetches
21774 current directory information correctly. Fixes bug 2156.
21775 - Report only the top 10 ports in exit-port stats in order not to
21776 exceed the maximum extra-info descriptor length of 50 KB. Implements
21780 Changes in version 0.2.1.28 - 2010-12-17
21781 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
21782 exploitable bugs. We also took this opportunity to change the IP address
21783 for one of our directory authorities, and to update the geoip database
21787 - Fix a remotely exploitable bug that could be used to crash instances
21788 of Tor remotely by overflowing on the heap. Remote-code execution
21789 hasn't been confirmed, but can't be ruled out. Everyone should
21790 upgrade. Bugfix on the 0.1.1 series and later.
21792 o Directory authority changes:
21793 - Change IP address and ports for gabelmoo (v3 directory authority).
21796 - Update to the December 1 2010 Maxmind GeoLite Country database.
21799 Changes in version 0.2.1.27 - 2010-11-23
21800 Yet another OpenSSL security patch broke its compatibility with Tor:
21801 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
21802 also took this opportunity to fix several crash bugs, integrate a new
21803 directory authority, and update the bundled GeoIP database.
21806 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
21807 No longer set the tlsext_host_name extension on server SSL objects;
21808 but continue to set it on client SSL objects. Our goal in setting
21809 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
21810 bugfix on 0.2.1.1-alpha.
21811 - Do not log messages to the controller while shrinking buffer
21812 freelists. Doing so would sometimes make the controller connection
21813 try to allocate a buffer chunk, which would mess up the internals
21814 of the freelist and cause an assertion failure. Fixes bug 1125;
21815 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
21816 - Learn our external IP address when we're a relay or bridge, even if
21817 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
21818 where we introduced bridge relays that don't need to publish to
21819 be useful. Fixes bug 2050.
21820 - Do even more to reject (and not just ignore) annotations on
21821 router descriptors received anywhere but from the cache. Previously
21822 we would ignore such annotations at first, but cache them to disk
21823 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
21824 - When you're using bridges and your network goes away and your
21825 bridges get marked as down, recover when you attempt a new socks
21826 connection (if the network is back), rather than waiting up to an
21827 hour to try fetching new descriptors for your bridges. Bugfix on
21828 0.2.0.3-alpha; fixes bug 1981.
21831 - Move to the November 2010 Maxmind GeoLite country db (rather
21832 than the June 2009 ip-to-country GeoIP db) for our statistics that
21833 count how many users relays are seeing from each country. Now we'll
21834 have more accurate data, especially for many African countries.
21836 o New directory authorities:
21837 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
21841 - Fix an assertion failure that could occur in directory caches or
21842 bridge users when using a very short voting interval on a testing
21843 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
21845 - Enforce multiplicity rules when parsing annotations. Bugfix on
21846 0.2.0.8-alpha. Found by piebeer.
21847 - Allow handshaking OR connections to take a full KeepalivePeriod
21848 seconds to handshake. Previously, we would close them after
21849 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
21850 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
21852 - When building with --enable-gcc-warnings on OpenBSD, disable
21853 warnings in system headers. This makes --enable-gcc-warnings
21854 pass on OpenBSD 4.8.
21857 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
21858 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
21859 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
21860 Servers can start sending this code when enough clients recognize
21861 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
21862 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
21863 Patch from mingw-san.
21866 - Remove the old debian/ directory from the main Tor distribution.
21867 The official Tor-for-debian git repository lives at the URL
21868 https://git.torproject.org/debian/tor.git
21869 - Stop shipping the old doc/website/ directory in the tarball. We
21870 changed the website format in late 2010, and what we shipped in
21871 0.2.1.26 really wasn't that useful anyway.
21874 Changes in version 0.2.2.19-alpha - 2010-11-22
21875 Yet another OpenSSL security patch broke its compatibility with Tor:
21876 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
21879 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
21880 No longer set the tlsext_host_name extension on server SSL objects;
21881 but continue to set it on client SSL objects. Our goal in setting
21882 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
21883 bugfix on 0.2.1.1-alpha.
21886 - Try harder not to exceed the maximum length of 50 KB when writing
21887 statistics to extra-info descriptors. This bug was triggered by very
21888 fast relays reporting exit-port, entry, and dirreq statistics.
21889 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
21890 - Publish a router descriptor even if generating an extra-info
21891 descriptor fails. Previously we would not publish a router
21892 descriptor without an extra-info descriptor; this can cause fast
21893 exit relays collecting exit-port statistics to drop from the
21894 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
21897 Changes in version 0.2.2.18-alpha - 2010-11-16
21898 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
21899 us lately, makes unpublished bridge relays able to detect their IP
21900 address, and fixes a wide variety of other bugs to get us much closer
21901 to a stable release.
21904 - Do even more to reject (and not just ignore) annotations on
21905 router descriptors received anywhere but from the cache. Previously
21906 we would ignore such annotations at first, but cache them to disk
21907 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
21908 - Do not log messages to the controller while shrinking buffer
21909 freelists. Doing so would sometimes make the controller connection
21910 try to allocate a buffer chunk, which would mess up the internals
21911 of the freelist and cause an assertion failure. Fixes bug 1125;
21912 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
21913 - Learn our external IP address when we're a relay or bridge, even if
21914 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
21915 where we introduced bridge relays that don't need to publish to
21916 be useful. Fixes bug 2050.
21917 - Maintain separate TLS contexts and certificates for incoming and
21918 outgoing connections in bridge relays. Previously we would use the
21919 same TLS contexts and certs for incoming and outgoing connections.
21920 Bugfix on 0.2.0.3-alpha; addresses bug 988.
21921 - Maintain separate identity keys for incoming and outgoing TLS
21922 contexts in bridge relays. Previously we would use the same
21923 identity keys for incoming and outgoing TLS contexts. Bugfix on
21924 0.2.0.3-alpha; addresses the other half of bug 988.
21925 - Avoid an assertion failure when we as an authority receive a
21926 duplicate upload of a router descriptor that we already have,
21927 but which we previously considered an obsolete descriptor.
21928 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
21929 - Avoid a crash bug triggered by looking at a dangling pointer while
21930 setting the network status consensus. Found by Robert Ransom.
21931 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
21932 - Fix a logic error where servers that _didn't_ act as exits would
21933 try to keep their server lists more aggressively up to date than
21934 exits, when it was supposed to be the other way around. Bugfix
21937 o Minor bugfixes (on Tor 0.2.1.x and earlier):
21938 - When we're trying to guess whether we know our IP address as
21939 a relay, we would log various ways that we failed to guess
21940 our address, but never log that we ended up guessing it
21941 successfully. Now add a log line to help confused and anxious
21942 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
21943 - Bring the logic that gathers routerinfos and assesses the
21944 acceptability of circuits into line. This prevents a Tor OP from
21945 getting locked in a cycle of choosing its local OR as an exit for a
21946 path (due to a .exit request) and then rejecting the circuit because
21947 its OR is not listed yet. It also prevents Tor clients from using an
21948 OR running in the same instance as an exit (due to a .exit request)
21949 if the OR does not meet the same requirements expected of an OR
21950 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
21951 - Correctly describe errors that occur when generating a TLS object.
21952 Previously we would attribute them to a failure while generating a
21953 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
21955 - Enforce multiplicity rules when parsing annotations. Bugfix on
21956 0.2.0.8-alpha. Found by piebeer.
21957 - Fix warnings that newer versions of autoconf produced during
21958 ./autogen.sh. These warnings appear to be harmless in our case,
21959 but they were extremely verbose. Fixes bug 2020.
21961 o Minor bugfixes (on Tor 0.2.2.x):
21962 - Enable protection of small arrays whenever we build with gcc
21963 hardening features, not only when also building with warnings
21964 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
21967 - Make hidden services work better in private Tor networks by not
21968 requiring any uptime to join the hidden service descriptor
21969 DHT. Implements ticket 2088.
21970 - Rate-limit the "your application is giving Tor only an IP address"
21971 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
21972 - When AllowSingleHopExits is set, print a warning to explain to the
21973 relay operator why most clients are avoiding her relay.
21974 - Update to the November 1 2010 Maxmind GeoLite Country database.
21976 o Code simplifications and refactoring:
21977 - When we fixed bug 1038 we had to put in a restriction not to send
21978 RELAY_EARLY cells on rend circuits. This was necessary as long
21979 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
21980 active. Now remove this obsolete check. Resolves bug 2081.
21981 - Some options used different conventions for uppercasing of acronyms
21982 when comparing manpage and source. Fix those in favor of the
21983 manpage, as it makes sense to capitalize acronyms.
21984 - Remove the torrc.complete file. It hasn't been kept up to date
21985 and users will have better luck checking out the manpage.
21986 - Remove the obsolete "NoPublish" option; it has been flagged
21987 as obsolete and has produced a warning since 0.1.1.18-rc.
21988 - Remove everything related to building the expert bundle for OS X.
21989 It has confused many users, doesn't work right on OS X 10.6,
21990 and is hard to get rid of once installed. Resolves bug 1274.
21993 Changes in version 0.2.2.17-alpha - 2010-09-30
21994 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
21995 to use one-hop circuits (which can put the exit relays at higher risk,
21996 plus unbalance the network); fixes a big bug in bandwidth accounting
21997 for relays that want to limit their monthly bandwidth use; fixes a
21998 big pile of bugs in how clients tolerate temporary network failure;
21999 and makes our adaptive circuit build timeout feature (which improves
22000 client performance if your network is fast while not breaking things
22001 if your network is slow) better handle bad networks.
22004 - Exit relays now try harder to block exit attempts from unknown
22005 relays, to make it harder for people to use them as one-hop proxies
22006 a la tortunnel. Controlled by the refuseunknownexits consensus
22007 parameter (currently enabled), or you can override it on your
22008 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
22010 o Major bugfixes (0.2.1.x and earlier):
22011 - Fix a bug in bandwidth accounting that could make us use twice
22012 the intended bandwidth when our interval start changes due to
22013 daylight saving time. Now we tolerate skew in stored vs computed
22014 interval starts: if the start of the period changes by no more than
22015 50% of the period's duration, we remember bytes that we transferred
22016 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
22017 - Always search the Windows system directory for system DLLs, and
22018 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
22019 - When you're using bridges and your network goes away and your
22020 bridges get marked as down, recover when you attempt a new socks
22021 connection (if the network is back), rather than waiting up to an
22022 hour to try fetching new descriptors for your bridges. Bugfix on
22023 0.2.0.3-alpha; fixes bug 1981.
22025 o Major bugfixes (on 0.2.2.x):
22026 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
22028 - Fix a segfault that could happen when operating a bridge relay with
22029 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
22030 - The consensus bandwidth-weights (used by clients to choose fast
22031 relays) entered an unexpected edge case in September where
22032 Exits were much scarcer than Guards, resulting in bad weight
22033 recommendations. Now we compute them using new constraints that
22034 should succeed in all cases. Also alter directory authorities to
22035 not include the bandwidth-weights line if they fail to produce
22036 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
22037 - When weighting bridges during path selection, we used to trust
22038 the bandwidths they provided in their descriptor, only capping them
22039 at 10MB/s. This turned out to be problematic for two reasons:
22040 Bridges could claim to handle a lot more traffic then they
22041 actually would, thus making more clients pick them and have a
22042 pretty effective DoS attack. The other issue is that new bridges
22043 that might not have a good estimate for their bw capacity yet
22044 would not get used at all unless no other bridges are available
22045 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
22047 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
22048 - Ignore cannibalized circuits when recording circuit build times.
22049 This should provide for a minor performance improvement for hidden
22050 service users using 0.2.2.14-alpha, and should remove two spurious
22051 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
22052 - Simplify the logic that causes us to decide if the network is
22053 unavailable for purposes of recording circuit build times. If we
22054 receive no cells whatsoever for the entire duration of a circuit's
22055 full measured lifetime, the network is probably down. Also ignore
22056 one-hop directory fetching circuit timeouts when calculating our
22057 circuit build times. These changes should hopefully reduce the
22058 cases where we see ridiculous circuit build timeouts for people
22059 with spotty wireless connections. Fixes part of bug 1772; bugfix
22061 - Prevent the circuit build timeout from becoming larger than
22062 the maximum build time we have ever seen. Also, prevent the time
22063 period for measurement circuits from becoming larger than twice that
22064 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
22067 - When we run out of directory information such that we can't build
22068 circuits, but then get enough that we can build circuits, log when
22069 we actually construct a circuit, so the user has a better chance of
22070 knowing what's going on. Fixes bug 1362.
22071 - Be more generous with how much bandwidth we'd use up (with
22072 accounting enabled) before entering "soft hibernation". Previously,
22073 we'd refuse new connections and circuits once we'd used up 95% of
22074 our allotment. Now, we use up 95% of our allotment, AND make sure
22075 that we have no more than 500MB (or 3 hours of expected traffic,
22076 whichever is lower) remaining before we enter soft hibernation.
22077 - If we've configured EntryNodes and our network goes away and/or all
22078 our entrynodes get marked down, optimistically retry them all when
22079 a new socks application request appears. Fixes bug 1882.
22080 - Add some more defensive programming for architectures that can't
22081 handle unaligned integer accesses. We don't know of any actual bugs
22082 right now, but that's the best time to fix them. Fixes bug 1943.
22083 - Support line continuations in the torrc config file. If a line
22084 ends with a single backslash character, the newline is ignored, and
22085 the configuration value is treated as continuing on the next line.
22088 o Minor bugfixes (on 0.2.1.x and earlier):
22089 - For bandwidth accounting, calculate our expected bandwidth rate
22090 based on the time during which we were active and not in
22091 soft-hibernation during the last interval. Previously, we were
22092 also considering the time spent in soft-hibernation. If this
22093 was a long time, we would wind up underestimating our bandwidth
22094 by a lot, and skewing our wakeup time towards the start of the
22095 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
22097 o Minor bugfixes (on 0.2.2.x):
22098 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
22099 which were disabled by the circuit build timeout changes in
22100 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
22101 - Make sure we don't warn about missing bandwidth weights when
22102 choosing bridges or other relays not in the consensus. Bugfix on
22103 0.2.2.10-alpha; fixes bug 1805.
22104 - In our logs, do not double-report signatures from unrecognized
22105 authorities both as "from unknown authority" and "not
22106 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
22109 Changes in version 0.2.2.16-alpha - 2010-09-17
22110 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
22111 evident at exit relays), and also continues to resolve all the little
22112 bugs that have been filling up trac lately.
22114 o Major bugfixes (stream-level fairness):
22115 - When receiving a circuit-level SENDME for a blocked circuit, try
22116 to package cells fairly from all the streams that had previously
22117 been blocked on that circuit. Previously, we had started with the
22118 oldest stream, and allowed each stream to potentially exhaust
22119 the circuit's package window. This gave older streams on any
22120 given circuit priority over newer ones. Fixes bug 1937. Detected
22121 originally by Camilo Viecco. This bug was introduced before the
22122 first Tor release, in svn commit r152: it is the new winner of
22123 the longest-lived bug prize.
22124 - When the exit relay got a circuit-level sendme cell, it started
22125 reading on the exit streams, even if had 500 cells queued in the
22126 circuit queue already, so the circuit queue just grew and grew in
22127 some cases. We fix this by not re-enabling reading on receipt of a
22128 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
22129 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
22131 - Newly created streams were allowed to read cells onto circuits,
22132 even if the circuit's cell queue was blocked and waiting to drain.
22133 This created potential unfairness, as older streams would be
22134 blocked, but newer streams would gladly fill the queue completely.
22135 We add code to detect this situation and prevent any stream from
22136 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
22140 - Update to the September 1 2010 Maxmind GeoLite Country database.
22141 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
22142 not. This would lead to a cookie that is still not group readable.
22143 Closes bug 1843. Suggested by katmagic.
22144 - When logging a rate-limited warning, we now mention how many messages
22145 got suppressed since the last warning.
22146 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
22147 do individual connection-level rate limiting of clients. The torrc
22148 config options with the same names trump the consensus params, if
22149 both are present. Replaces the old "bwconnrate" and "bwconnburst"
22150 consensus params which were broken from 0.2.2.7-alpha through
22151 0.2.2.14-alpha. Closes bug 1947.
22152 - When a router changes IP address or port, authorities now launch
22153 a new reachability test for it. Implements ticket 1899.
22154 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
22155 2 no signature, 4 required" messages about consensus signatures
22156 easier to read, and make sure they get logged at the same severity
22157 as the messages explaining which keys are which. Fixes bug 1290.
22158 - Don't warn when we have a consensus that we can't verify because
22159 of missing certificates, unless those certificates are ones
22160 that we have been trying and failing to download. Fixes bug 1145.
22161 - If you configure your bridge with a known identity fingerprint,
22162 and the bridge authority is unreachable (as it is in at least
22163 one country now), fall back to directly requesting the descriptor
22164 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
22166 - When building with --enable-gcc-warnings on OpenBSD, disable
22167 warnings in system headers. This makes --enable-gcc-warnings
22168 pass on OpenBSD 4.8.
22170 o Minor bugfixes (on 0.2.1.x and earlier):
22171 - Authorities will now attempt to download consensuses if their
22172 own efforts to make a live consensus have failed. This change
22173 means authorities that restart will fetch a valid consensus, and
22174 it means authorities that didn't agree with the current consensus
22175 will still fetch and serve it if it has enough signatures. Bugfix
22176 on 0.2.0.9-alpha; fixes bug 1300.
22177 - Ensure DNS requests launched by "RESOLVE" commands from the
22178 controller respect the __LeaveStreamsUnattached setconf options. The
22179 same goes for requests launched via DNSPort or transparent
22180 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
22181 - Allow handshaking OR connections to take a full KeepalivePeriod
22182 seconds to handshake. Previously, we would close them after
22183 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22184 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22186 - Rate-limit "Failed to hand off onionskin" warnings.
22187 - Never relay a cell for a circuit we have already destroyed.
22188 Between marking a circuit as closeable and finally closing it,
22189 it may have been possible for a few queued cells to get relayed,
22190 even though they would have been immediately dropped by the next
22191 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
22192 - Never queue a cell for a circuit that's already been marked
22194 - Never vote for a server as "Running" if we have a descriptor for
22195 it claiming to be hibernating, and that descriptor was published
22196 more recently than our last contact with the server. Bugfix on
22197 0.2.0.3-alpha; fixes bug 911.
22198 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
22201 o Minor bugfixes (on 0.2.2.x):
22202 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
22203 down if a directory fetch fails and you've configured either
22204 bridges or EntryNodes. The intent was to mark the relay as down
22205 _unless_ you're using bridges or EntryNodes, since if you are
22206 then you could quickly run out of entry points.
22207 - Fix the Windows directory-listing code. A bug introduced in
22208 0.2.2.14-alpha could make Windows directory servers forget to load
22209 some of their cached v2 networkstatus files.
22210 - Really allow clients to use relays as bridges. Fixes bug 1776;
22211 bugfix on 0.2.2.15-alpha.
22212 - Demote a warn to info that happens when the CellStatistics option
22213 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
22214 Reported by Moritz Bartl.
22215 - On Windows, build correctly either with or without Unicode support.
22216 This is necessary so that Tor can support fringe platforms like
22217 Windows 98 (which has no Unicode), or Windows CE (which has no
22218 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
22221 - Add a unit test for cross-platform directory-listing code.
22224 Changes in version 0.2.2.15-alpha - 2010-08-18
22225 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
22226 fixes a variety of other bugs that were preventing performance
22227 experiments from moving forward, fixes several bothersome memory leaks,
22228 and generally closes a lot of smaller bugs that have been filling up
22232 - Stop assigning the HSDir flag to relays that disable their
22233 DirPort (and thus will refuse to answer directory requests). This
22234 fix should dramatically improve the reachability of hidden services:
22235 hidden services and hidden service clients pick six HSDir relays
22236 to store and retrieve the hidden service descriptor, and currently
22237 about half of the HSDir relays will refuse to work. Bugfix on
22238 0.2.0.10-alpha; fixes part of bug 1693.
22239 - The PerConnBWRate and Burst config options, along with the
22240 bwconnrate and bwconnburst consensus params, initialized each conn's
22241 token bucket values only when the connection is established. Now we
22242 update them if the config options change, and update them every time
22243 we get a new consensus. Otherwise we can encounter an ugly edge
22244 case where we initialize an OR conn to client-level bandwidth,
22245 but then later the relay joins the consensus and we leave it
22246 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
22247 - Fix a regression that caused Tor to rebind its ports if it receives
22248 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
22251 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
22252 should give us approximately 40-50% more Guard-flagged nodes,
22253 improving the anonymity the Tor network can provide and also
22254 decreasing the dropoff in throughput that relays experience when
22255 they first get the Guard flag.
22256 - Allow enabling or disabling the *Statistics config options while
22260 - Update to the August 1 2010 Maxmind GeoLite Country database.
22261 - Have the controller interface give a more useful message than
22262 "Internal Error" in response to failed GETINFO requests.
22263 - Warn when the same option is provided more than once in a torrc
22264 file, on the command line, or in a single SETCONF statement, and
22265 the option is one that only accepts a single line. Closes bug 1384.
22266 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22267 Patch from mingw-san.
22268 - Add support for the country code "{??}" in torrc options like
22269 ExcludeNodes, to indicate all routers of unknown country. Closes
22271 - Relays report the number of bytes spent on answering directory
22272 requests in extra-info descriptors similar to {read,write}-history.
22273 Implements enhancement 1790.
22275 o Minor bugfixes (on 0.2.1.x and earlier):
22276 - Complain if PublishServerDescriptor is given multiple arguments that
22277 include 0 or 1. This configuration will be rejected in the future.
22278 Bugfix on 0.2.0.1-alpha; closes bug 1107.
22279 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
22280 Bugfix on 0.2.0.13-alpha; closes bug 928.
22281 - Change "Application request when we're believed to be offline."
22282 notice to "Application request when we haven't used client
22283 functionality lately.", to clarify that it's not an error. Bugfix
22284 on 0.0.9.3; fixes bug 1222.
22285 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
22286 would return "551 Internal error" rather than "552 Unrecognized key
22287 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
22288 - Users can't configure a regular relay to be their bridge. It didn't
22289 work because when Tor fetched the bridge descriptor, it found
22290 that it already had it, and didn't realize that the purpose of the
22291 descriptor had changed. Now we replace routers with a purpose other
22292 than bridge with bridge descriptors when fetching them. Bugfix on
22293 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
22294 refetch the descriptor with router purpose 'general', disabling
22296 - Fix a rare bug in rend_fn unit tests: we would fail a test when
22297 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
22298 on 0.2.0.10-alpha; fixes bug 1808.
22299 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22300 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22301 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22302 Servers can start sending this code when enough clients recognize
22303 it. Also update the spec to reflect this new reason. Bugfix on
22304 0.1.0.1-rc; fixes part of bug 1793.
22305 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
22306 when we switch from being a public relay to a bridge. Otherwise
22307 there will still be clients that see the relay in their consensus,
22308 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
22310 - Instead of giving an assertion failure on an internal mismatch
22311 on estimated freelist size, just log a BUG warning and try later.
22312 Mitigates but does not fix bug 1125.
22313 - Fix an assertion failure that could occur in caches or bridge users
22314 when using a very short voting interval on a testing network.
22315 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
22317 o Minor bugfixes (on 0.2.2.x):
22318 - Alter directory authorities to always consider Exit-flagged nodes
22319 as potential Guard nodes in their votes. The actual decision to
22320 use Exits as Guards is done in the consensus bandwidth weights.
22321 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
22322 - When the controller is reporting the purpose of circuits that
22323 didn't finish building before the circuit build timeout, it was
22324 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
22325 - Our libevent version parsing code couldn't handle versions like
22326 1.4.14b-stable and incorrectly warned the user about using an
22327 old and broken version of libevent. Treat 1.4.14b-stable like
22328 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
22330 - Don't use substitution references like $(VAR:MOD) when
22331 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
22332 '$(:x)' to 'x' rather than the empty string. This bites us in
22333 doc/ when configured with --disable-asciidoc. Bugfix on
22334 0.2.2.9-alpha; fixes bug 1773.
22335 - Remove a spurious hidden service server-side log notice about
22336 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
22338 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
22340 - Correctly report written bytes on linked connections. Found while
22341 implementing 1790. Bugfix on 0.2.2.4-alpha.
22342 - Fix three memory leaks: one in circuit_build_times_parse_state(),
22343 one in dirvote_add_signatures_to_pending_consensus(), and one every
22344 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
22345 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
22347 o Code simplifications and refactoring:
22348 - Take a first step towards making or.h smaller by splitting out
22349 function definitions for all source files in src/or/. Leave
22350 structures and defines in or.h for now.
22351 - Remove a bunch of unused function declarations as well as a block of
22352 #if 0'd code from the unit tests. Closes bug 1824.
22353 - New unit tests for exit-port history statistics; refactored exit
22354 statistics code to be more easily tested.
22355 - Remove the old debian/ directory from the main Tor distribution.
22356 The official Tor-for-debian git repository lives at the URL
22357 https://git.torproject.org/debian/tor.git
22360 Changes in version 0.2.2.14-alpha - 2010-07-12
22361 Tor 0.2.2.14-alpha greatly improves client-side handling of
22362 circuit build timeouts, which are used to estimate speed and improve
22363 performance. We also move to a much better GeoIP database, port Tor to
22364 Windows CE, introduce new compile flags that improve code security,
22365 add an eighth v3 directory authority, and address a lot of more
22369 - Tor directory authorities no longer crash when started with a
22370 cached-microdesc-consensus file in their data directory. Bugfix
22371 on 0.2.2.6-alpha; fixes bug 1532.
22372 - Treat an unset $HOME like an empty $HOME rather than triggering an
22373 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
22374 - Ignore negative and large circuit build timeout values that can
22375 happen during a suspend or hibernate. These values caused various
22376 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
22377 - Alter calculation of Pareto distribution parameter 'Xm' for
22378 Circuit Build Timeout learning to use the weighted average of the
22379 top N=3 modes (because we have three entry guards). Considering
22380 multiple modes should improve the timeout calculation in some cases,
22381 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
22383 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
22384 right censored distribution model. This approach improves over the
22385 synthetic timeout generation approach that was producing insanely
22386 high timeout values. Now we calculate build timeouts using truncated
22387 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
22388 - Do not close circuits that are under construction when they reach
22389 the circuit build timeout. Instead, leave them building (but do not
22390 use them) for up until the time corresponding to the 95th percentile
22391 on the Pareto CDF or 60 seconds, whichever is greater. This is done
22392 to provide better data for the new Pareto model. This percentile
22393 can be controlled by the consensus.
22396 - Move to the June 2010 Maxmind GeoLite country db (rather than the
22397 June 2009 ip-to-country GeoIP db) for our statistics that count
22398 how many users relays are seeing from each country. Now we have
22399 more accurate data for many African countries.
22400 - Port Tor to build and run correctly on Windows CE systems, using
22401 the wcecompat library. Contributed by Valerio Lupi.
22402 - New "--enable-gcc-hardening" ./configure flag (off by default)
22403 to turn on gcc compile time hardening options. It ensures
22404 that signed ints have defined behavior (-fwrapv), enables
22405 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
22406 with canaries (-fstack-protector-all), turns on ASLR protection if
22407 supported by the kernel (-fPIE, -pie), and adds additional security
22408 related warnings. Verified to work on Mac OS X and Debian Lenny.
22409 - New "--enable-linker-hardening" ./configure flag (off by default)
22410 to turn on ELF specific hardening features (relro, now). This does
22411 not work with Mac OS X or any other non-ELF binary format.
22413 o New directory authorities:
22414 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22418 - New config option "WarnUnsafeSocks 0" disables the warning that
22419 occurs whenever Tor receives a socks handshake using a version of
22420 the socks protocol that can only provide an IP address (rather
22421 than a hostname). Setups that do DNS locally over Tor are fine,
22422 and we shouldn't spam the logs in that case.
22423 - Convert the HACKING file to asciidoc, and add a few new sections
22424 to it, explaining how we use Git, how we make changelogs, and
22425 what should go in a patch.
22426 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
22427 event, to give information on the current rate of circuit timeouts
22428 over our stored history.
22429 - Add ability to disable circuit build time learning via consensus
22430 parameter and via a LearnCircuitBuildTimeout config option. Also
22431 automatically disable circuit build time calculation if we are
22432 either a AuthoritativeDirectory, or if we fail to write our state
22433 file. Fixes bug 1296.
22434 - More gracefully handle corrupt state files, removing asserts
22435 in favor of saving a backup and resetting state.
22436 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
22440 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
22442 - When a2x fails, mention that the user could disable manpages instead
22443 of trying to fix their asciidoc installation.
22444 - Where available, use Libevent 2.0's periodic timers so that our
22445 once-per-second cleanup code gets called even more closely to
22446 once per second than it would otherwise. Fixes bug 943.
22447 - If you run a bridge that listens on multiple IP addresses, and
22448 some user configures a bridge address that uses a different IP
22449 address than your bridge writes in its router descriptor, and the
22450 user doesn't specify an identity key, their Tor would discard the
22451 descriptor because "it isn't one of our configured bridges", and
22452 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
22453 Bugfix on 0.2.0.3-alpha.
22454 - If OpenSSL fails to make a duplicate of a private or public key, log
22455 an error message and try to exit cleanly. May help with debugging
22456 if bug 1209 ever remanifests.
22457 - Save a couple bytes in memory allocation every time we escape
22458 certain characters in a string. Patch from Florian Zumbiehl.
22459 - Make it explicit that we don't cannibalize one-hop circuits. This
22460 happens in the wild, but doesn't turn out to be a problem because
22461 we fortunately don't use those circuits. Many thanks to outofwords
22462 for the initial analysis and to swissknife who confirmed that
22463 two-hop circuits are actually created.
22464 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
22465 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
22466 - Eliminate a case where a circuit build time warning was displayed
22467 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
22470 Changes in version 0.2.1.26 - 2010-05-02
22471 Tor 0.2.1.26 addresses the recent connection and memory overload
22472 problems we've been seeing on relays, especially relays with their
22473 DirPort open. If your relay has been crashing, or you turned it off
22474 because it used too many resources, give this release a try.
22476 This release also fixes yet another instance of broken OpenSSL libraries
22477 that was causing some relays to drop out of the consensus.
22480 - Teach relays to defend themselves from connection overload. Relays
22481 now close idle circuits early if it looks like they were intended
22482 for directory fetches. Relays are also more aggressive about closing
22483 TLS connections that have no circuits on them. Such circuits are
22484 unlikely to be re-used, and tens of thousands of them were piling
22485 up at the fast relays, causing the relays to run out of sockets
22486 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
22487 their directory fetches over TLS).
22488 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
22489 that claim to be earlier than 0.9.8m, but which have in reality
22490 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
22491 behavior. Possible fix for some cases of bug 1346.
22492 - Directory mirrors were fetching relay descriptors only from v2
22493 directory authorities, rather than v3 authorities like they should.
22494 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
22495 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
22498 - Finally get rid of the deprecated and now harmful notion of "clique
22499 mode", where directory authorities maintain TLS connections to
22503 - In the util/threads test, no longer free the test_mutex before all
22504 worker threads have finished. Bugfix on 0.2.1.6-alpha.
22505 - The master thread could starve the worker threads quite badly on
22506 certain systems, causing them to run only partially in the allowed
22507 window. This resulted in test failures. Now the master thread sleeps
22508 occasionally for a few microseconds while the two worker-threads
22509 compete for the mutex. Bugfix on 0.2.0.1-alpha.
22512 Changes in version 0.2.2.13-alpha - 2010-04-24
22513 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
22514 problems we've been seeing on relays, especially relays with their
22515 DirPort open. If your relay has been crashing, or you turned it off
22516 because it used too many resources, give this release a try.
22519 - Teach relays to defend themselves from connection overload. Relays
22520 now close idle circuits early if it looks like they were intended
22521 for directory fetches. Relays are also more aggressive about closing
22522 TLS connections that have no circuits on them. Such circuits are
22523 unlikely to be re-used, and tens of thousands of them were piling
22524 up at the fast relays, causing the relays to run out of sockets
22525 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
22526 their directory fetches over TLS).
22529 - Finally get rid of the deprecated and now harmful notion of "clique
22530 mode", where directory authorities maintain TLS connections to
22532 - Directory authorities now do an immediate reachability check as soon
22533 as they hear about a new relay. This change should slightly reduce
22534 the time between setting up a relay and getting listed as running
22535 in the consensus. It should also improve the time between setting
22536 up a bridge and seeing use by bridge users.
22537 - Directory authorities no longer launch a TLS connection to every
22538 relay as they startup. Now that we have 2k+ descriptors cached,
22539 the resulting network hiccup is becoming a burden. Besides,
22540 authorities already avoid voting about Running for the first half
22541 hour of their uptime.
22544 Changes in version 0.2.2.12-alpha - 2010-04-20
22545 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
22546 handle and vote on descriptors. It was causing relays to drop out of
22550 - Many relays have been falling out of the consensus lately because
22551 not enough authorities know about their descriptor for them to get
22552 a majority of votes. When we deprecated the v2 directory protocol,
22553 we got rid of the only way that v3 authorities can hear from each
22554 other about other descriptors. Now authorities examine every v3
22555 vote for new descriptors, and fetch them from that authority. Bugfix
22557 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
22558 and a warning in or.h related to bandwidth_weight_rule_t that
22559 prevented clean compile on OS X. Fixes bug 1363; bugfix on
22561 - Fix a segfault on relays when DirReqStatistics is enabled
22562 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
22566 - Demote a confusing TLS warning that relay operators might get when
22567 someone tries to talk to their OrPort. It is neither the operator's
22568 fault nor can they do anything about it. Fixes bug 1364; bugfix
22572 Changes in version 0.2.2.11-alpha - 2010-04-15
22573 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
22574 libraries that was causing some relays to drop out of the consensus.
22577 - Directory mirrors were fetching relay descriptors only from v2
22578 directory authorities, rather than v3 authorities like they should.
22579 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
22580 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
22581 - Fix a parsing error that made every possible value of
22582 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
22583 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
22584 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
22585 about the option without breaking older ones.
22586 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
22587 that claim to be earlier than 0.9.8m, but which have in reality
22588 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
22589 behavior. Possible fix for some cases of bug 1346.
22592 - Experiment with a more aggressive approach to preventing clients
22593 from making one-hop exit streams. Exit relays who want to try it
22594 out can set "RefuseUnknownExits 1" in their torrc, and then look
22595 for "Attempt by %s to open a stream" log messages. Let us know
22597 - Add support for statically linking zlib by specifying
22598 --enable-static-zlib, to go with our support for statically linking
22599 openssl and libevent. Resolves bug 1358.
22602 - Fix a segfault that happens whenever a Tor client that is using
22603 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
22605 - When we cleaned up the contrib/tor-exit-notice.html file, we left
22606 out the first line. Fixes bug 1295.
22607 - When building the manpage from a tarball, we required asciidoc, but
22608 the asciidoc -> roff/html conversion was already done for the
22609 tarball. Make 'make' complain only when we need asciidoc (either
22610 because we're compiling directly from git, or because we altered
22611 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
22612 - When none of the directory authorities vote on any params, Tor
22613 segfaulted when trying to make the consensus from the votes. We
22614 didn't trigger the bug in practice, because authorities do include
22615 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
22618 - In the util/threads test, no longer free the test_mutex before all
22619 worker threads have finished. Bugfix on 0.2.1.6-alpha.
22620 - The master thread could starve the worker threads quite badly on
22621 certain systems, causing them to run only partially in the allowed
22622 window. This resulted in test failures. Now the master thread sleeps
22623 occasionally for a few microseconds while the two worker-threads
22624 compete for the mutex. Bugfix on 0.2.0.1-alpha.
22627 Changes in version 0.2.2.10-alpha - 2010-03-07
22628 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
22629 could prevent relays from guessing their IP address correctly. It also
22630 starts the groundwork for another client-side performance boost, since
22631 currently we're not making efficient use of relays that have both the
22632 Guard flag and the Exit flag.
22635 - Fix a regression from our patch for bug 1244 that caused relays
22636 to guess their IP address incorrectly if they didn't set Address
22637 in their torrc and/or their address fails to resolve. Bugfix on
22638 0.2.2.9-alpha; fixes bug 1269.
22640 o Major features (performance):
22641 - Directory authorities now compute consensus weightings that instruct
22642 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
22643 and no flag. Clients that use these weightings will distribute
22644 network load more evenly across these different relay types. The
22645 weightings are in the consensus so we can change them globally in
22646 the future. Extra thanks to "outofwords" for finding some nasty
22647 security bugs in the first implementation of this feature.
22649 o Minor features (performance):
22650 - Always perform router selections using weighted relay bandwidth,
22651 even if we don't need a high capacity circuit at the time. Non-fast
22652 circuits now only differ from fast ones in that they can use relays
22653 not marked with the Fast flag. This "feature" could turn out to
22654 be a horrible bug; we should investigate more before it goes into
22658 - Allow disabling building of the manpages. Skipping the manpage
22659 speeds up the build considerably.
22661 o Minor bugfixes (on 0.2.2.x):
22662 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
22663 Bugfix on 0.2.2.9-alpha.
22664 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
22665 config option. Bugfix on 0.2.2.7-alpha.
22666 - Ship the asciidoc-helper file in the tarball, so that people can
22667 build from source if they want to, and touching the .1.txt files
22668 doesn't break the build. Bugfix on 0.2.2.9-alpha.
22670 o Minor bugfixes (on 0.2.1.x or earlier):
22671 - Fix a dereference-then-NULL-check sequence when publishing
22672 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
22674 - Fix another dereference-then-NULL-check sequence. Bugfix on
22675 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
22676 - Make sure we treat potentially not NUL-terminated strings correctly.
22677 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
22679 o Code simplifications and refactoring:
22680 - Fix some urls in the exit notice file and make it XHTML1.1 strict
22681 compliant. Based on a patch from Christian Kujau.
22682 - Don't use sed in asciidoc-helper anymore.
22683 - Make the build process fail if asciidoc cannot be found and
22684 building with asciidoc isn't disabled.
22687 Changes in version 0.2.2.9-alpha - 2010-02-22
22688 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
22689 location of a directory authority, and cleans up a bunch of small bugs.
22691 o Directory authority changes:
22692 - Change IP address for dannenberg (v3 directory authority), and
22693 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
22694 service directory authority) from the list.
22697 - Make Tor work again on the latest OS X: when deciding whether to
22698 use strange flags to turn TLS renegotiation on, detect the OpenSSL
22699 version at run-time, not compile time. We need to do this because
22700 Apple doesn't update its dev-tools headers when it updates its
22701 libraries in a security patch.
22702 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
22703 that could happen on 32-bit platforms with 64-bit time_t. Also fix
22704 a memory leak when requesting a hidden service descriptor we've
22705 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
22707 - Authorities could be tricked into giving out the Exit flag to relays
22708 that didn't allow exiting to any ports. This bug could screw
22709 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
22710 1238. Bug discovered by Martin Kowalczyk.
22711 - When freeing a session key, zero it out completely. We only zeroed
22712 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
22713 patched by ekir. Fixes bug 1254.
22716 - Fix static compilation by listing the openssl libraries in the right
22717 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
22718 - Resume handling .exit hostnames in a special way: originally we
22719 stripped the .exit part and used the requested exit relay. In
22720 0.2.2.1-alpha we stopped treating them in any special way, meaning
22721 if you use a .exit address then Tor will pass it on to the exit
22722 relay. Now we reject the .exit stream outright, since that behavior
22723 might be more expected by the user. Found and diagnosed by Scott
22724 Bennett and Downie on or-talk.
22725 - Don't spam the controller with events when we have no file
22726 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
22727 for log messages was already solved from bug 748.)
22728 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
22730 - Make the DNSPort option work with libevent 2.x. Don't alter the
22731 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
22732 - Emit a GUARD DROPPED controller event for a case we missed.
22733 - Make more fields in the controller protocol case-insensitive, since
22734 control-spec.txt said they were.
22735 - Refactor resolve_my_address() to not use gethostbyname() anymore.
22736 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
22737 - Fix a spec conformance issue: the network-status-version token
22738 must be the first token in a v3 consensus or vote. Discovered by
22739 parakeep. Bugfix on 0.2.0.3-alpha.
22741 o Code simplifications and refactoring:
22742 - Generate our manpage and HTML documentation using Asciidoc. This
22743 change should make it easier to maintain the documentation, and
22744 produce nicer HTML.
22745 - Remove the --enable-iphone option. According to reports from Marco
22746 Bonetti, Tor builds fine without any special tweaking on recent
22747 iPhone SDK versions.
22748 - Removed some unnecessary files from the source distribution. The
22749 AUTHORS file has now been merged into the people page on the
22750 website. The roadmaps and design doc can now be found in the
22751 projects directory in svn.
22752 - Enabled various circuit build timeout constants to be controlled
22753 by consensus parameters. Also set better defaults for these
22754 parameters based on experimentation on broadband and simulated
22755 high latency links.
22758 - The 'EXTENDCIRCUIT' control port command can now be used with
22759 a circ id of 0 and no path. This feature will cause Tor to build
22760 a new 'fast' general purpose circuit using its own path selection
22762 - Added a BUILDTIMEOUT_SET controller event to describe changes
22763 to the circuit build timeout.
22764 - Future-proof the controller protocol a bit by ignoring keyword
22765 arguments we do not recognize.
22766 - Expand homedirs passed to tor-checkkey. This should silence a
22767 coverity complaint about passing a user-supplied string into
22768 open() without checking it.
22771 Changes in version 0.2.1.25 - 2010-03-16
22772 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
22773 prevent relays from guessing their IP address correctly. It also fixes
22774 several minor potential security bugs.
22777 - Fix a regression from our patch for bug 1244 that caused relays
22778 to guess their IP address incorrectly if they didn't set Address
22779 in their torrc and/or their address fails to resolve. Bugfix on
22780 0.2.1.23; fixes bug 1269.
22781 - When freeing a session key, zero it out completely. We only zeroed
22782 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
22783 patched by ekir. Fixes bug 1254.
22786 - Fix a dereference-then-NULL-check sequence when publishing
22787 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
22789 - Fix another dereference-then-NULL-check sequence. Bugfix on
22790 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
22791 - Make sure we treat potentially not NUL-terminated strings correctly.
22792 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
22796 Changes in version 0.2.1.24 - 2010-02-21
22797 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
22801 - Work correctly out-of-the-box with even more vendor-patched versions
22802 of OpenSSL. In particular, make it so Debian and OS X don't need
22803 customized patches to run/build.
22806 Changes in version 0.2.1.23 - 2010-02-13
22807 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
22808 again on the latest OS X, and updates the location of a directory
22811 o Major bugfixes (performance):
22812 - We were selecting our guards uniformly at random, and then weighting
22813 which of our guards we'd use uniformly at random. This imbalance
22814 meant that Tor clients were severely limited on throughput (and
22815 probably latency too) by the first hop in their circuit. Now we
22816 select guards weighted by currently advertised bandwidth. We also
22817 automatically discard guards picked using the old algorithm. Fixes
22818 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
22821 - Make Tor work again on the latest OS X: when deciding whether to
22822 use strange flags to turn TLS renegotiation on, detect the OpenSSL
22823 version at run-time, not compile time. We need to do this because
22824 Apple doesn't update its dev-tools headers when it updates its
22825 libraries in a security patch.
22826 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
22827 that could happen on 32-bit platforms with 64-bit time_t. Also fix
22828 a memory leak when requesting a hidden service descriptor we've
22829 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
22832 o Directory authority changes:
22833 - Change IP address for dannenberg (v3 directory authority), and
22834 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
22835 service directory authority) from the list.
22838 - Refactor resolve_my_address() to not use gethostbyname() anymore.
22839 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
22842 - Avoid a mad rush at the beginning of each month when each client
22843 rotates half of its guards. Instead we spread the rotation out
22844 throughout the month, but we still avoid leaving a precise timestamp
22845 in the state file about when we first picked the guard. Improves
22846 over the behavior introduced in 0.1.2.17.
22849 Changes in version 0.2.2.8-alpha - 2010-01-26
22850 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
22851 causing bridge relays to disappear. If you're running a bridge,
22855 - Fix a memory corruption bug on bridges that occurred during the
22856 inclusion of stats data in extra-info descriptors. Also fix the
22857 interface for geoip_get_bridge_stats* to prevent similar bugs in
22858 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
22859 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
22862 - Ignore OutboundBindAddress when connecting to localhost.
22863 Connections to localhost need to come _from_ localhost, or else
22864 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
22868 Changes in version 0.2.2.7-alpha - 2010-01-19
22869 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
22870 as laying the groundwork for further relay-side performance fixes. It
22871 also starts cleaning up client behavior with respect to the EntryNodes,
22872 ExitNodes, and StrictNodes config options.
22874 This release also rotates two directory authority keys, due to a
22875 security breach of some of the Torproject servers.
22877 o Directory authority changes:
22878 - Rotate keys (both v3 identity and relay identity) for moria1
22881 o Major features (performance):
22882 - We were selecting our guards uniformly at random, and then weighting
22883 which of our guards we'd use uniformly at random. This imbalance
22884 meant that Tor clients were severely limited on throughput (and
22885 probably latency too) by the first hop in their circuit. Now we
22886 select guards weighted by currently advertised bandwidth. We also
22887 automatically discard guards picked using the old algorithm. Fixes
22888 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
22889 - When choosing which cells to relay first, relays can now favor
22890 circuits that have been quiet recently, to provide lower latency
22891 for low-volume circuits. By default, relays enable or disable this
22892 feature based on a setting in the consensus. You can override
22893 this default by using the new "CircuitPriorityHalflife" config
22894 option. Design and code by Ian Goldberg, Can Tang, and Chris
22896 - Add separate per-conn write limiting to go with the per-conn read
22897 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
22898 but never per-conn write limits.
22899 - New consensus params "bwconnrate" and "bwconnburst" to let us
22900 rate-limit client connections as they enter the network. It's
22901 controlled in the consensus so we can turn it on and off for
22902 experiments. It's starting out off. Based on proposal 163.
22904 o Major features (relay selection options):
22905 - Switch to a StrictNodes config option, rather than the previous
22906 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
22907 "StrictExcludeNodes" option.
22908 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
22909 change during a config reload, mark and discard all our origin
22910 circuits. This fix should address edge cases where we change the
22911 config options and but then choose a circuit that we created before
22913 - If EntryNodes or ExitNodes are set, be more willing to use an
22914 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
22916 - Make EntryNodes config option much more aggressive even when
22917 StrictNodes is not set. Before it would prepend your requested
22918 entrynodes to your list of guard nodes, but feel free to use others
22919 after that. Now it chooses only from your EntryNodes if any of
22920 those are available, and only falls back to others if a) they're
22921 all down and b) StrictNodes is not set.
22922 - Now we refresh your entry guards from EntryNodes at each consensus
22923 fetch -- rather than just at startup and then they slowly rot as
22924 the network changes.
22927 - Stop bridge directory authorities from answering dbg-stability.txt
22928 directory queries, which would let people fetch a list of all
22929 bridge identities they track. Bugfix on 0.2.1.6-alpha.
22932 - Log a notice when we get a new control connection. Now it's easier
22933 for security-conscious users to recognize when a local application
22934 is knocking on their controller door. Suggested by bug 1196.
22935 - New config option "CircuitStreamTimeout" to override our internal
22936 timeout schedule for how many seconds until we detach a stream from
22937 a circuit and try a new circuit. If your network is particularly
22938 slow, you might want to set this to a number like 60.
22939 - New controller command "getinfo config-text". It returns the
22940 contents that Tor would write if you send it a SAVECONF command,
22941 so the controller can write the file to disk itself.
22942 - New options for SafeLogging to allow scrubbing only log messages
22943 generated while acting as a relay.
22944 - Ship the bridges spec file in the tarball too.
22945 - Avoid a mad rush at the beginning of each month when each client
22946 rotates half of its guards. Instead we spread the rotation out
22947 throughout the month, but we still avoid leaving a precise timestamp
22948 in the state file about when we first picked the guard. Improves
22949 over the behavior introduced in 0.1.2.17.
22951 o Minor bugfixes (compiling):
22952 - Fix compilation on OS X 10.3, which has a stub mlockall() but
22953 hides it. Bugfix on 0.2.2.6-alpha.
22954 - Fix compilation on Solaris by removing support for the
22955 DisableAllSwap config option. Solaris doesn't have an rlimit for
22956 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
22959 o Minor bugfixes (crashes):
22960 - Do not segfault when writing buffer stats when we haven't observed
22961 a single circuit to report about. Found by Fabian Lanze. Bugfix on
22963 - If we're in the pathological case where there's no exit bandwidth
22964 but there is non-exit bandwidth, or no guard bandwidth but there
22965 is non-guard bandwidth, don't crash during path selection. Bugfix
22967 - Fix an impossible-to-actually-trigger buffer overflow in relay
22968 descriptor generation. Bugfix on 0.1.0.15.
22970 o Minor bugfixes (privacy):
22971 - Fix an instance where a Tor directory mirror might accidentally
22972 log the IP address of a misbehaving Tor client. Bugfix on
22974 - Don't list Windows capabilities in relay descriptors. We never made
22975 use of them, and maybe it's a bad idea to publish them. Bugfix
22978 o Minor bugfixes (other):
22979 - Resolve an edge case in path weighting that could make us misweight
22980 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
22981 - Fix statistics on client numbers by country as seen by bridges that
22982 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
22983 intervals instead of variable 12-to-48-hour intervals.
22984 - After we free an internal connection structure, overwrite it
22985 with a different memory value than we use for overwriting a freed
22986 internal circuit structure. Should help with debugging. Suggested
22988 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
22991 o Removed features:
22992 - Remove the HSAuthorityRecordStats option that version 0 hidden
22993 service authorities could have used to track statistics of overall
22994 hidden service usage.
22997 Changes in version 0.2.1.22 - 2010-01-19
22998 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
22999 authorities -- it would tell you its whole history of bridge descriptors
23000 if you make the right directory request. This stable update also
23001 rotates two of the seven v3 directory authority keys and locations.
23003 o Directory authority changes:
23004 - Rotate keys (both v3 identity and relay identity) for moria1
23008 - Stop bridge directory authorities from answering dbg-stability.txt
23009 directory queries, which would let people fetch a list of all
23010 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23013 Changes in version 0.2.1.21 - 2009-12-21
23014 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
23015 library. If you use Tor on Linux / Unix and you're getting SSL
23016 renegotiation errors, upgrading should help. We also recommend an
23017 upgrade if you're an exit relay.
23020 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23021 handshake from working unless we explicitly tell OpenSSL that we
23022 are using SSL renegotiation safely. We are, of course, but OpenSSL
23023 0.9.8l won't work unless we say we are.
23024 - Avoid crashing if the client is trying to upload many bytes and the
23025 circuit gets torn down at the same time, or if the flip side
23026 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
23029 - Do not refuse to learn about authority certs and v2 networkstatus
23030 documents that are older than the latest consensus. This bug might
23031 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23032 Spotted and fixed by xmux.
23033 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
23034 trigger platform-specific option misparsing case found by Coverity
23036 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
23037 trigger assert. Fixes bug 1173.
23040 Changes in version 0.2.2.6-alpha - 2009-11-19
23041 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
23042 support for the new lower-footprint "microdescriptor" directory design,
23043 future-proofing our consensus format against new hash functions or
23044 other changes, and an Android port. It also makes Tor compatible with
23045 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
23048 - Directory authorities can now create, vote on, and serve multiple
23049 parallel formats of directory data as part of their voting process.
23050 Partially implements Proposal 162: "Publish the consensus in
23052 - Directory authorities can now agree on and publish small summaries
23053 of router information that clients can use in place of regular
23054 server descriptors. This transition will eventually allow clients
23055 to use far less bandwidth for downloading information about the
23056 network. Begins the implementation of Proposal 158: "Clients
23057 download consensus + microdescriptors".
23058 - The directory voting system is now extensible to use multiple hash
23059 algorithms for signatures and resource selection. Newer formats
23060 are signed with SHA256, with a possibility for moving to a better
23061 hash algorithm in the future.
23062 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
23063 current and future memory pages via mlockall(). On supported
23064 platforms (modern Linux and probably BSD but not Windows or OS X),
23065 this should effectively disable any and all attempts to page out
23066 memory. This option requires that you start your Tor as root --
23067 if you use DisableAllSwap, please consider using the User option
23068 to properly reduce the privileges of your Tor.
23069 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
23070 to help Tor build correctly for Android phones.
23073 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23074 handshake from working unless we explicitly tell OpenSSL that we
23075 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
23076 won't work unless we say we are.
23079 - Fix a crash bug when trying to initialize the evdns module in
23080 Libevent 2. Bugfix on 0.2.1.16-rc.
23081 - Stop logging at severity 'warn' when some other Tor client tries
23082 to establish a circuit with us using weak DH keys. It's a protocol
23083 violation, but that doesn't mean ordinary users need to hear about
23084 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
23085 - Do not refuse to learn about authority certs and v2 networkstatus
23086 documents that are older than the latest consensus. This bug might
23087 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23088 Spotted and fixed by xmux.
23089 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
23090 - If all authorities restart at once right before a consensus vote,
23091 nobody will vote about "Running", and clients will get a consensus
23092 with no usable relays. Instead, authorities refuse to build a
23093 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
23094 - If your relay can't keep up with the number of incoming create
23095 cells, it would log one warning per failure into your logs. Limit
23096 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
23097 - Bridges now use "reject *:*" as their default exit policy. Bugfix
23098 on 0.2.0.3-alpha; fixes bug 1113.
23099 - Fix a memory leak on directory authorities during voting that was
23100 introduced in 0.2.2.1-alpha. Found via valgrind.
23103 Changes in version 0.2.1.20 - 2009-10-15
23104 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
23105 services at once, prepares for more performance improvements, and
23106 fixes a bunch of smaller bugs.
23108 The Windows and OS X bundles also include a more recent Vidalia,
23109 and switch from Privoxy to Polipo.
23111 The OS X installers are now drag and drop. It's best to un-install
23112 Tor/Vidalia and then install this new bundle, rather than upgrade. If
23113 you want to upgrade, you'll need to update the paths for Tor and Polipo
23114 in the Vidalia Settings window.
23117 - Send circuit or stream sendme cells when our window has decreased
23118 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
23119 by Karsten when testing the "reduce circuit window" performance
23120 patch. Bugfix on the 54th commit on Tor -- from July 2002,
23121 before the release of Tor 0.0.0. This is the new winner of the
23123 - Fix a remotely triggerable memory leak when a consensus document
23124 contains more than one signature from the same voter. Bugfix on
23126 - Avoid segfault in rare cases when finishing an introduction circuit
23127 as a client and finding out that we don't have an introduction key
23128 for it. Fixes bug 1073. Reported by Aaron Swartz.
23131 - Tor now reads the "circwindow" parameter out of the consensus,
23132 and uses that value for its circuit package window rather than the
23133 default of 1000 cells. Begins the implementation of proposal 168.
23135 o New directory authorities:
23136 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
23138 - Move moria1 and tonga to alternate IP addresses.
23141 - Fix a signed/unsigned compile warning in 0.2.1.19.
23142 - Fix possible segmentation fault on directory authorities. Bugfix on
23144 - Fix an extremely rare infinite recursion bug that could occur if
23145 we tried to log a message after shutting down the log subsystem.
23146 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
23147 - Fix an obscure bug where hidden services on 64-bit big-endian
23148 systems might mis-read the timestamp in v3 introduce cells, and
23149 refuse to connect back to the client. Discovered by "rotor".
23150 Bugfix on 0.2.1.6-alpha.
23151 - We were triggering a CLOCK_SKEW controller status event whenever
23152 we connect via the v2 connection protocol to any relay that has
23153 a wrong clock. Instead, we should only inform the controller when
23154 it's a trusted authority that claims our clock is wrong. Bugfix
23155 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
23156 - We were telling the controller about CHECKING_REACHABILITY and
23157 REACHABILITY_FAILED status events whenever we launch a testing
23158 circuit or notice that one has failed. Instead, only tell the
23159 controller when we want to inform the user of overall success or
23160 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
23162 - Don't warn when we're using a circuit that ends with a node
23163 excluded in ExcludeExitNodes, but the circuit is not used to access
23164 the outside world. This should help fix bug 1090. Bugfix on
23166 - Work around a small memory leak in some versions of OpenSSL that
23167 stopped the memory used by the hostname TLS extension from being
23171 - Add a "getinfo status/accepted-server-descriptor" controller
23172 command, which is the recommended way for controllers to learn
23173 whether our server descriptor has been successfully received by at
23174 least on directory authority. Un-recommend good-server-descriptor
23175 getinfo and status events until we have a better design for them.
23178 Changes in version 0.2.2.5-alpha - 2009-10-11
23179 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
23182 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
23184 o Directory authorities:
23185 - Temporarily (just for this release) move dizum to an alternate
23189 Changes in version 0.2.2.4-alpha - 2009-10-10
23190 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
23191 introduces a new unit test framework, shifts directry authority
23192 addresses around to reduce the impact from recent blocking events,
23193 and fixes a few smaller bugs.
23196 - Fix several more asserts in the circuit_build_times code, for
23197 example one that causes Tor to fail to start once we have
23198 accumulated 5000 build times in the state file. Bugfixes on
23199 0.2.2.2-alpha; fixes bug 1108.
23201 o New directory authorities:
23202 - Move moria1 and Tonga to alternate IP addresses.
23205 - Log SSL state transitions at debug level during handshake, and
23206 include SSL states in error messages. This may help debug future
23207 SSL handshake issues.
23208 - Add a new "Handshake" log domain for activities that happen
23209 during the TLS handshake.
23210 - Revert to the "June 3 2009" ip-to-country file. The September one
23211 seems to have removed most US IP addresses.
23212 - Directory authorities now reject Tor relays with versions less than
23213 0.1.2.14. This step cuts out four relays from the current network,
23214 none of which are very big.
23217 - Fix a couple of smaller issues with gathering statistics. Bugfixes
23219 - Fix two memory leaks in the error case of
23220 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
23221 - Don't count one-hop circuits when we're estimating how long it
23222 takes circuits to build on average. Otherwise we'll set our circuit
23223 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
23224 - Directory authorities no longer change their opinion of, or vote on,
23225 whether a router is Running, unless they have themselves been
23226 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
23229 o Code simplifications and refactoring:
23230 - Revise our unit tests to use the "tinytest" framework, so we
23231 can run tests in their own processes, have smarter setup/teardown
23232 code, and so on. The unit test code has moved to its own
23233 subdirectory, and has been split into multiple modules.
23236 Changes in version 0.2.2.3-alpha - 2009-09-23
23237 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
23240 - Fix an overzealous assert in our new circuit build timeout code.
23241 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
23244 - If the networkstatus consensus tells us that we should use a
23245 negative circuit package window, ignore it. Otherwise we'll
23246 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
23249 Changes in version 0.2.2.2-alpha - 2009-09-21
23250 Tor 0.2.2.2-alpha introduces our latest performance improvement for
23251 clients: Tor tracks the average time it takes to build a circuit, and
23252 avoids using circuits that take too long to build. For fast connections,
23253 this feature can cut your expected latency in half. For slow or flaky
23254 connections, it could ruin your Tor experience. Let us know if it does!
23257 - Tor now tracks how long it takes to build client-side circuits
23258 over time, and adapts its timeout to local network performance.
23259 Since a circuit that takes a long time to build will also provide
23260 bad performance, we get significant latency improvements by
23261 discarding the slowest 20% of circuits. Specifically, Tor creates
23262 circuits more aggressively than usual until it has enough data
23263 points for a good timeout estimate. Implements proposal 151.
23264 We are especially looking for reports (good and bad) from users with
23265 both EDGE and broadband connections that can move from broadband
23266 to EDGE and find out if the build-time data in the .tor/state gets
23267 reset without loss of Tor usability. You should also see a notice
23268 log message telling you that Tor has reset its timeout.
23269 - Directory authorities can now vote on arbitrary integer values as
23270 part of the consensus process. This is designed to help set
23271 network-wide parameters. Implements proposal 167.
23272 - Tor now reads the "circwindow" parameter out of the consensus,
23273 and uses that value for its circuit package window rather than the
23274 default of 1000 cells. Begins the implementation of proposal 168.
23277 - Fix a remotely triggerable memory leak when a consensus document
23278 contains more than one signature from the same voter. Bugfix on
23282 - Fix an extremely rare infinite recursion bug that could occur if
23283 we tried to log a message after shutting down the log subsystem.
23284 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
23285 - Fix parsing for memory or time units given without a space between
23286 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
23287 - A networkstatus vote must contain exactly one signature. Spec
23288 conformance issue. Bugfix on 0.2.0.3-alpha.
23289 - Fix an obscure bug where hidden services on 64-bit big-endian
23290 systems might mis-read the timestamp in v3 introduce cells, and
23291 refuse to connect back to the client. Discovered by "rotor".
23292 Bugfix on 0.2.1.6-alpha.
23293 - We were triggering a CLOCK_SKEW controller status event whenever
23294 we connect via the v2 connection protocol to any relay that has
23295 a wrong clock. Instead, we should only inform the controller when
23296 it's a trusted authority that claims our clock is wrong. Bugfix
23297 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
23298 - We were telling the controller about CHECKING_REACHABILITY and
23299 REACHABILITY_FAILED status events whenever we launch a testing
23300 circuit or notice that one has failed. Instead, only tell the
23301 controller when we want to inform the user of overall success or
23302 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
23304 - Don't warn when we're using a circuit that ends with a node
23305 excluded in ExcludeExitNodes, but the circuit is not used to access
23306 the outside world. This should help fix bug 1090, but more problems
23307 remain. Bugfix on 0.2.1.6-alpha.
23308 - Work around a small memory leak in some versions of OpenSSL that
23309 stopped the memory used by the hostname TLS extension from being
23311 - Make our 'torify' script more portable; if we have only one of
23312 'torsocks' or 'tsocks' installed, don't complain to the user;
23313 and explain our warning about tsocks better.
23316 - Add a "getinfo status/accepted-server-descriptor" controller
23317 command, which is the recommended way for controllers to learn
23318 whether our server descriptor has been successfully received by at
23319 least on directory authority. Un-recommend good-server-descriptor
23320 getinfo and status events until we have a better design for them.
23321 - Update to the "September 4 2009" ip-to-country file.
23324 Changes in version 0.2.2.1-alpha - 2009-08-26
23325 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
23326 Tor clients to bootstrap on networks where only port 80 is reachable,
23327 makes it more straightforward to support hardware crypto accelerators,
23328 and starts the groundwork for gathering stats safely at relays.
23331 - Start the process of disabling ".exit" address notation, since it
23332 can be used for a variety of esoteric application-level attacks
23333 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
23336 o New directory authorities:
23337 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
23341 - New AccelName and AccelDir options add support for dynamic OpenSSL
23342 hardware crypto acceleration engines.
23343 - Tor now supports tunneling all of its outgoing connections over
23344 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
23345 configuration options. Code by Christopher Davis.
23348 - Send circuit or stream sendme cells when our window has decreased
23349 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
23350 by Karsten when testing the "reduce circuit window" performance
23351 patch. Bugfix on the 54th commit on Tor -- from July 2002,
23352 before the release of Tor 0.0.0. This is the new winner of the
23355 o New options for gathering stats safely:
23356 - Directory mirrors that set "DirReqStatistics 1" write statistics
23357 about directory requests to disk every 24 hours. As compared to the
23358 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
23359 1) stats are written to disk exactly every 24 hours; 2) estimated
23360 shares of v2 and v3 requests are determined as mean values, not at
23361 the end of a measurement period; 3) unresolved requests are listed
23362 with country code '??'; 4) directories also measure download times.
23363 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
23364 number of exit streams and transferred bytes per port to disk every
23366 - Relays that set "CellStatistics 1" write statistics on how long
23367 cells spend in their circuit queues to disk every 24 hours.
23368 - Entry nodes that set "EntryStatistics 1" write statistics on the
23369 rough number and origins of connecting clients to disk every 24
23371 - Relays that write any of the above statistics to disk and set
23372 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
23373 their extra-info documents.
23376 - New --digests command-line switch to output the digests of the
23377 source files Tor was built with.
23378 - The "torify" script now uses torsocks where available.
23379 - The memarea code now uses a sentinel value at the end of each area
23380 to make sure nothing writes beyond the end of an area. This might
23381 help debug some conceivable causes of bug 930.
23382 - Time and memory units in the configuration file can now be set to
23383 fractional units. For example, "2.5 GB" is now a valid value for
23385 - Certain Tor clients (such as those behind check.torproject.org) may
23386 want to fetch the consensus in an extra early manner. To enable this
23387 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
23388 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
23389 as only certain clients who must have this information sooner should
23391 - Instead of adding the svn revision to the Tor version string, report
23392 the git commit (when we're building from a git checkout).
23395 - If any of the v3 certs we download are unparseable, we should
23396 actually notice the failure so we don't retry indefinitely. Bugfix
23397 on 0.2.0.x; reported by "rotator".
23398 - If the cached cert file is unparseable, warn but don't exit.
23399 - Fix possible segmentation fault on directory authorities. Bugfix on
23401 - When Tor fails to parse a descriptor of any kind, dump it to disk.
23402 Might help diagnosing bug 1051.
23404 o Deprecated and removed features:
23405 - The controller no longer accepts the old obsolete "addr-mappings/"
23406 or "unregistered-servers-" GETINFO values.
23407 - Hidden services no longer publish version 0 descriptors, and clients
23408 do not request or use version 0 descriptors. However, the old hidden
23409 service authorities still accept and serve version 0 descriptors
23410 when contacted by older hidden services/clients.
23411 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
23412 always on; using them is necessary for correct forward-compatible
23414 - Remove support for .noconnect style addresses. Nobody was using
23415 them, and they provided another avenue for detecting Tor users
23416 via application-level web tricks.
23418 o Packaging changes:
23419 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
23420 installer bundles. See
23421 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
23422 for details of what's new in Vidalia 0.2.3.
23423 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
23424 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
23425 configuration file, rather than the old Privoxy.
23426 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
23427 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
23428 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
23429 better compatibility with OS X 10.6, aka Snow Leopard.
23430 - OS X Vidalia Bundle: The multi-package installer is now replaced
23431 by a simple drag and drop to the /Applications folder. This change
23432 occurred with the upgrade to Vidalia 0.2.3.
23435 Changes in version 0.2.1.19 - 2009-07-28
23436 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
23437 services on Tor 0.2.1.3-alpha through 0.2.1.18.
23440 - Make accessing hidden services on 0.2.1.x work right again.
23441 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
23442 part of patch provided by "optimist".
23445 - When a relay/bridge is writing out its identity key fingerprint to
23446 the "fingerprint" file and to its logs, write it without spaces. Now
23447 it will look like the fingerprints in our bridges documentation,
23448 and confuse fewer users.
23451 - Relays no longer publish a new server descriptor if they change
23452 their MaxAdvertisedBandwidth config option but it doesn't end up
23453 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
23454 fixes bug 1026. Patch from Sebastian.
23455 - Avoid leaking memory every time we get a create cell but we have
23456 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
23457 fixes bug 1034. Reported by BarkerJr.
23460 Changes in version 0.2.1.18 - 2009-07-24
23461 Tor 0.2.1.18 lays the foundations for performance improvements,
23462 adds status events to help users diagnose bootstrap problems, adds
23463 optional authentication/authorization for hidden services, fixes a
23464 variety of potential anonymity problems, and includes a huge pile of
23465 other features and bug fixes.
23468 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
23471 Changes in version 0.2.1.17-rc - 2009-07-07
23472 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
23473 candidate for the 0.2.1.x series. It lays the groundwork for further
23474 client performance improvements, and also fixes a big bug with directory
23475 authorities that were causing them to assign Guard and Stable flags
23478 The Windows bundles also finally include the geoip database that we
23479 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
23480 should actually install Torbutton rather than giving you a cryptic
23481 failure message (oops).
23484 - Clients now use the bandwidth values in the consensus, rather than
23485 the bandwidth values in each relay descriptor. This approach opens
23486 the door to more accurate bandwidth estimates once the directory
23487 authorities start doing active measurements. Implements more of
23491 - When Tor clients restart after 1-5 days, they discard all their
23492 cached descriptors as too old, but they still use the cached
23493 consensus document. This approach is good for robustness, but
23494 bad for performance: since they don't know any bandwidths, they
23495 end up choosing at random rather than weighting their choice by
23496 speed. Fixed by the above feature of putting bandwidths in the
23497 consensus. Bugfix on 0.2.0.x.
23498 - Directory authorities were neglecting to mark relays down in their
23499 internal histories if the relays fall off the routerlist without
23500 ever being found unreachable. So there were relays in the histories
23501 that haven't been seen for eight months, and are listed as being
23502 up for eight months. This wreaked havoc on the "median wfu"
23503 and "median mtbf" calculations, in turn making Guard and Stable
23504 flags very wrong, hurting network performance. Fixes bugs 696 and
23505 969. Bugfix on 0.2.0.6-alpha.
23508 - Serve the DirPortFrontPage page even when we have been approaching
23509 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
23510 - The control port would close the connection before flushing long
23511 replies, such as the network consensus, if a QUIT command was issued
23512 before the reply had completed. Now, the control port flushes all
23513 pending replies before closing the connection. Also fixed a spurious
23514 warning when a QUIT command is issued after a malformed or rejected
23515 AUTHENTICATE command, but before the connection was closed. Patch
23516 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
23517 - When we can't find an intro key for a v2 hidden service descriptor,
23518 fall back to the v0 hidden service descriptor and log a bug message.
23519 Workaround for bug 1024.
23520 - Fix a log message that did not respect the SafeLogging option.
23524 - If we're a relay and we change our IP address, be more verbose
23525 about the reason that made us change. Should help track down
23526 further bugs for relays on dynamic IP addresses.
23529 Changes in version 0.2.0.35 - 2009-06-24
23531 - Avoid crashing in the presence of certain malformed descriptors.
23532 Found by lark, and by automated fuzzing.
23533 - Fix an edge case where a malicious exit relay could convince a
23534 controller that the client's DNS question resolves to an internal IP
23535 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
23538 - Finally fix the bug where dynamic-IP relays disappear when their
23539 IP address changes: directory mirrors were mistakenly telling
23540 them their old address if they asked via begin_dir, so they
23541 never got an accurate answer about their new address, so they
23542 just vanished after a day. For belt-and-suspenders, relays that
23543 don't set Address in their config now avoid using begin_dir for
23544 all direct connections. Should fix bugs 827, 883, and 900.
23545 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
23546 that would occur on some exit nodes when DNS failures and timeouts
23547 occurred in certain patterns. Fix for bug 957.
23550 - When starting with a cache over a few days old, do not leak
23551 memory for the obsolete router descriptors in it. Bugfix on
23552 0.2.0.33; fixes bug 672.
23553 - Hidden service clients didn't use a cached service descriptor that
23554 was older than 15 minutes, but wouldn't fetch a new one either,
23555 because there was already one in the cache. Now, fetch a v2
23556 descriptor unless the same descriptor was added to the cache within
23557 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
23560 Changes in version 0.2.1.16-rc - 2009-06-20
23561 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
23562 a bunch of minor bugs.
23565 - Fix an edge case where a malicious exit relay could convince a
23566 controller that the client's DNS question resolves to an internal IP
23567 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
23569 o Major performance improvements (on 0.2.0.x):
23570 - Disable and refactor some debugging checks that forced a linear scan
23571 over the whole server-side DNS cache. These accounted for over 50%
23572 of CPU time on a relatively busy exit node's gprof profile. Found
23574 - Disable some debugging checks that appeared in exit node profile
23578 - Update to the "June 3 2009" ip-to-country file.
23579 - Do not have tor-resolve automatically refuse all .onion addresses;
23580 if AutomapHostsOnResolve is set in your torrc, this will work fine.
23582 o Minor bugfixes (on 0.2.0.x):
23583 - Log correct error messages for DNS-related network errors on
23585 - Fix a race condition that could cause crashes or memory corruption
23586 when running as a server with a controller listening for log
23588 - Avoid crashing when we have a policy specified in a DirPolicy or
23589 SocksPolicy or ReachableAddresses option with ports set on it,
23590 and we re-load the policy. May fix bug 996.
23591 - Hidden service clients didn't use a cached service descriptor that
23592 was older than 15 minutes, but wouldn't fetch a new one either,
23593 because there was already one in the cache. Now, fetch a v2
23594 descriptor unless the same descriptor was added to the cache within
23595 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
23597 o Minor bugfixes (on 0.2.1.x):
23598 - Don't warn users about low port and hibernation mix when they
23599 provide a *ListenAddress directive to fix that. Bugfix on
23601 - When switching back and forth between bridge mode, do not start
23602 gathering GeoIP data until two hours have passed.
23603 - Do not complain that the user has requested an excluded node as
23604 an exit when the node is not really an exit. This could happen
23605 because the circuit was for testing, or an introduction point.
23609 Changes in version 0.2.1.15-rc - 2009-05-25
23610 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
23611 series. It fixes a major bug on fast exit relays, as well as a variety
23612 of more minor bugs.
23614 o Major bugfixes (on 0.2.0.x):
23615 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
23616 that would occur on some exit nodes when DNS failures and timeouts
23617 occurred in certain patterns. Fix for bug 957.
23619 o Minor bugfixes (on 0.2.0.x):
23620 - Actually return -1 in the error case for read_bandwidth_usage().
23621 Harmless bug, since we currently don't care about the return value
23622 anywhere. Bugfix on 0.2.0.9-alpha.
23623 - Provide a more useful log message if bug 977 (related to buffer
23624 freelists) ever reappears, and do not crash right away.
23625 - Fix an assertion failure on 64-bit platforms when we allocated
23626 memory right up to the end of a memarea, then realigned the memory
23627 one step beyond the end. Fixes a possible cause of bug 930.
23628 - Protect the count of open sockets with a mutex, so we can't
23629 corrupt it when two threads are closing or opening sockets at once.
23630 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
23631 - Don't allow a bridge to publish its router descriptor to a
23632 non-bridge directory authority. Fixes part of bug 932.
23633 - When we change to or from being a bridge, reset our counts of
23634 client usage by country. Fixes bug 932.
23635 - Fix a bug that made stream bandwidth get misreported to the
23637 - Stop using malloc_usable_size() to use more area than we had
23638 actually allocated: it was safe, but made valgrind really unhappy.
23639 - Fix a memory leak when v3 directory authorities load their keys
23640 and cert from disk. Bugfix on 0.2.0.1-alpha.
23642 o Minor bugfixes (on 0.2.1.x):
23643 - Fix use of freed memory when deciding to mark a non-addable
23644 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
23647 Changes in version 0.2.1.14-rc - 2009-04-12
23648 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
23649 series. It begins fixing some major performance problems, and also
23650 finally addresses the bug that was causing relays on dynamic IP
23651 addresses to fall out of the directory.
23654 - Clients replace entry guards that were chosen more than a few months
23655 ago. This change should significantly improve client performance,
23656 especially once more people upgrade, since relays that have been
23657 a guard for a long time are currently overloaded.
23659 o Major bugfixes (on 0.2.0):
23660 - Finally fix the bug where dynamic-IP relays disappear when their
23661 IP address changes: directory mirrors were mistakenly telling
23662 them their old address if they asked via begin_dir, so they
23663 never got an accurate answer about their new address, so they
23664 just vanished after a day. For belt-and-suspenders, relays that
23665 don't set Address in their config now avoid using begin_dir for
23666 all direct connections. Should fix bugs 827, 883, and 900.
23667 - Relays were falling out of the networkstatus consensus for
23668 part of a day if they changed their local config but the
23669 authorities discarded their new descriptor as "not sufficiently
23670 different". Now directory authorities accept a descriptor as changed
23671 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
23672 patch by Sebastian.
23673 - Avoid crashing in the presence of certain malformed descriptors.
23674 Found by lark, and by automated fuzzing.
23677 - When generating circuit events with verbose nicknames for
23678 controllers, try harder to look up nicknames for routers on a
23679 circuit. (Previously, we would look in the router descriptors we had
23680 for nicknames, but not in the consensus.) Partial fix for bug 941.
23681 - If the bridge config line doesn't specify a port, assume 443.
23682 This makes bridge lines a bit smaller and easier for users to
23684 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
23685 bytes (aka 20KB/s), to match our documentation. Also update
23686 directory authorities so they always assign the Fast flag to relays
23687 with 20KB/s of capacity. Now people running relays won't suddenly
23688 find themselves not seeing any use, if the network gets faster
23690 - Update to the "April 3 2009" ip-to-country file.
23693 - Avoid trying to print raw memory to the logs when we decide to
23694 give up on downloading a given relay descriptor. Bugfix on
23696 - In tor-resolve, when the Tor client to use is specified by
23697 <hostname>:<port>, actually use the specified port rather than
23698 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
23699 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
23700 - When starting with a cache over a few days old, do not leak
23701 memory for the obsolete router descriptors in it. Bugfix on
23703 - Avoid double-free on list of successfully uploaded hidden
23704 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
23705 - Change memarea_strndup() implementation to work even when
23706 duplicating a string at the end of a page. This bug was
23707 harmless for now, but could have meant crashes later. Fix by
23708 lark. Bugfix on 0.2.1.1-alpha.
23709 - Limit uploaded directory documents to be 16M rather than 500K.
23710 The directory authorities were refusing v3 consensus votes from
23711 other authorities, since the votes are now 504K. Fixes bug 959;
23712 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
23713 - Directory authorities should never send a 503 "busy" response to
23714 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
23718 Changes in version 0.2.1.13-alpha - 2009-03-09
23719 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
23720 cleanups. We're finally getting close to a release candidate.
23723 - Correctly update the list of which countries we exclude as
23724 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
23725 lark. Bugfix on 0.2.1.6-alpha.
23727 o Minor bugfixes (on 0.2.0.x and earlier):
23728 - Automatically detect MacOSX versions earlier than 10.4.0, and
23729 disable kqueue from inside Tor when running with these versions.
23730 We previously did this from the startup script, but that was no
23731 help to people who didn't use the startup script. Resolves bug 863.
23732 - When we had picked an exit node for a connection, but marked it as
23733 "optional", and it turned out we had no onion key for the exit,
23734 stop wanting that exit and try again. This situation may not
23735 be possible now, but will probably become feasible with proposal
23736 158. Spotted by rovv. Fixes another case of bug 752.
23737 - Clients no longer cache certificates for authorities they do not
23738 recognize. Bugfix on 0.2.0.9-alpha.
23739 - When we can't transmit a DNS request due to a network error, retry
23740 it after a while, and eventually transmit a failing response to
23741 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
23742 - If the controller claimed responsibility for a stream, but that
23743 stream never finished making its connection, it would live
23744 forever in circuit_wait state. Now we close it after SocksTimeout
23745 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
23746 - Drop begin cells to a hidden service if they come from the middle
23747 of a circuit. Patch from lark.
23748 - When we erroneously receive two EXTEND cells for the same circuit
23749 ID on the same connection, drop the second. Patch from lark.
23750 - Fix a crash that occurs on exit nodes when a nameserver request
23751 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
23752 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
23754 - Do not assume that a stack-allocated character array will be
23755 64-bit aligned on platforms that demand that uint64_t access is
23756 aligned. Possible fix for bug 604.
23757 - Parse dates and IPv4 addresses in a locale- and libc-independent
23758 manner, to avoid platform-dependent behavior on malformed input.
23759 - Build correctly when configured to build outside the main source
23760 path. Patch from Michael Gold.
23761 - We were already rejecting relay begin cells with destination port
23762 of 0. Now also reject extend cells with destination port or address
23763 of 0. Suggested by lark.
23765 o Minor bugfixes (on 0.2.1.x):
23766 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
23767 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
23768 - If we're an exit node, scrub the IP address to which we are exiting
23769 in the logs. Bugfix on 0.2.1.8-alpha.
23772 - On Linux, use the prctl call to re-enable core dumps when the user
23774 - New controller event NEWCONSENSUS that lists the networkstatus
23775 lines for every recommended relay. Now controllers like Torflow
23776 can keep up-to-date on which relays they should be using.
23777 - Update to the "February 26 2009" ip-to-country file.
23780 Changes in version 0.2.0.34 - 2009-02-08
23781 Tor 0.2.0.34 features several more security-related fixes. You should
23782 upgrade, especially if you run an exit relay (remote crash) or a
23783 directory authority (remote infinite loop), or you're on an older
23784 (pre-XP) or not-recently-patched Windows (remote exploit).
23786 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
23787 have many known flaws, and nobody should be using them. You should
23788 upgrade. If you're using a Linux or BSD and its packages are obsolete,
23789 stop using those packages and upgrade anyway.
23792 - Fix an infinite-loop bug on handling corrupt votes under certain
23793 circumstances. Bugfix on 0.2.0.8-alpha.
23794 - Fix a temporary DoS vulnerability that could be performed by
23795 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
23796 - Avoid a potential crash on exit nodes when processing malformed
23797 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
23798 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
23799 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
23802 - Fix compilation on systems where time_t is a 64-bit integer.
23803 Patch from Matthias Drochner.
23804 - Don't consider expiring already-closed client connections. Fixes
23805 bug 893. Bugfix on 0.0.2pre20.
23808 Changes in version 0.2.1.12-alpha - 2009-02-08
23809 Tor 0.2.1.12-alpha features several more security-related fixes. You
23810 should upgrade, especially if you run an exit relay (remote crash) or
23811 a directory authority (remote infinite loop), or you're on an older
23812 (pre-XP) or not-recently-patched Windows (remote exploit). It also
23813 includes a big pile of minor bugfixes and cleanups.
23816 - Fix an infinite-loop bug on handling corrupt votes under certain
23817 circumstances. Bugfix on 0.2.0.8-alpha.
23818 - Fix a temporary DoS vulnerability that could be performed by
23819 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
23820 - Avoid a potential crash on exit nodes when processing malformed
23821 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
23824 - Let controllers actually ask for the "clients_seen" event for
23825 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
23826 reported by Matt Edman.
23827 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
23829 - Fix a bug in address parsing that was preventing bridges or hidden
23830 service targets from being at IPv6 addresses.
23831 - Solve a bug that kept hardware crypto acceleration from getting
23832 enabled when accounting was turned on. Fixes bug 907. Bugfix on
23834 - Remove a bash-ism from configure.in to build properly on non-Linux
23835 platforms. Bugfix on 0.2.1.1-alpha.
23836 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
23837 headers. Bugfix on 0.2.0.10-alpha.
23838 - Don't consider expiring already-closed client connections. Fixes
23839 bug 893. Bugfix on 0.0.2pre20.
23840 - Fix another interesting corner-case of bug 891 spotted by rovv:
23841 Previously, if two hosts had different amounts of clock drift, and
23842 one of them created a new connection with just the wrong timing,
23843 the other might decide to deprecate the new connection erroneously.
23844 Bugfix on 0.1.1.13-alpha.
23845 - Resolve a very rare crash bug that could occur when the user forced
23846 a nameserver reconfiguration during the middle of a nameserver
23847 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
23848 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
23849 Bugfix on 0.2.1.7-alpha.
23850 - If we're using bridges and our network goes away, be more willing
23851 to forgive our bridges and try again when we get an application
23852 request. Bugfix on 0.2.0.x.
23855 - Support platforms where time_t is 64 bits long. (Congratulations,
23856 NetBSD!) Patch from Matthias Drochner.
23857 - Add a 'getinfo status/clients-seen' controller command, in case
23858 controllers want to hear clients_seen events but connect late.
23861 - Disable GCC's strict alias optimization by default, to avoid the
23862 likelihood of its introducing subtle bugs whenever our code violates
23863 the letter of C99's alias rules.
23866 Changes in version 0.2.0.33 - 2009-01-21
23867 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
23868 useful to users. It also finally fixes a bug where a relay or client
23869 that's been off for many days would take a long time to bootstrap.
23871 This update also fixes an important security-related bug reported by
23872 Ilja van Sprundel. You should upgrade. (We'll send out more details
23873 about the bug once people have had some time to upgrade.)
23876 - Fix a heap-corruption bug that may be remotely triggerable on
23877 some platforms. Reported by Ilja van Sprundel.
23880 - When a stream at an exit relay is in state "resolving" or
23881 "connecting" and it receives an "end" relay cell, the exit relay
23882 would silently ignore the end cell and not close the stream. If
23883 the client never closes the circuit, then the exit relay never
23884 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
23885 reported by "wood".
23886 - When sending CREATED cells back for a given circuit, use a 64-bit
23887 connection ID to find the right connection, rather than an addr:port
23888 combination. Now that we can have multiple OR connections between
23889 the same ORs, it is no longer possible to use addr:port to uniquely
23890 identify a connection.
23891 - Bridge relays that had DirPort set to 0 would stop fetching
23892 descriptors shortly after startup, and then briefly resume
23893 after a new bandwidth test and/or after publishing a new bridge
23894 descriptor. Bridge users that try to bootstrap from them would
23895 get a recent networkstatus but would get descriptors from up to
23896 18 hours earlier, meaning most of the descriptors were obsolete
23897 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
23898 - Prevent bridge relays from serving their 'extrainfo' document
23899 to anybody who asks, now that extrainfo docs include potentially
23900 sensitive aggregated client geoip summaries. Bugfix on
23902 - If the cached networkstatus consensus is more than five days old,
23903 discard it rather than trying to use it. In theory it could be
23904 useful because it lists alternate directory mirrors, but in practice
23905 it just means we spend many minutes trying directory mirrors that
23906 are long gone from the network. Also discard router descriptors as
23907 we load them if they are more than five days old, since the onion
23908 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
23911 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
23912 could make gcc generate non-functional binary search code. Bugfix
23914 - Build correctly on platforms without socklen_t.
23915 - Compile without warnings on solaris.
23916 - Avoid potential crash on internal error during signature collection.
23917 Fixes bug 864. Patch from rovv.
23918 - Correct handling of possible malformed authority signing key
23919 certificates with internal signature types. Fixes bug 880.
23920 Bugfix on 0.2.0.3-alpha.
23921 - Fix a hard-to-trigger resource leak when logging credential status.
23923 - When we can't initialize DNS because the network is down, do not
23924 automatically stop Tor from starting. Instead, we retry failed
23925 dns_init() every 10 minutes, and change the exit policy to reject
23926 *:* until one succeeds. Fixes bug 691.
23927 - Use 64 bits instead of 32 bits for connection identifiers used with
23928 the controller protocol, to greatly reduce risk of identifier reuse.
23929 - When we're choosing an exit node for a circuit, and we have
23930 no pending streams, choose a good general exit rather than one that
23931 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
23932 - Fix another case of assuming, when a specific exit is requested,
23933 that we know more than the user about what hosts it allows.
23934 Fixes one case of bug 752. Patch from rovv.
23935 - Clip the MaxCircuitDirtiness config option to a minimum of 10
23936 seconds. Warn the user if lower values are given in the
23937 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
23938 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
23939 user if lower values are given in the configuration. Bugfix on
23940 0.1.1.17-rc. Patch by Sebastian.
23941 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
23942 the cache because we already had a v0 descriptor with the same ID.
23943 Bugfix on 0.2.0.18-alpha.
23944 - Fix a race condition when freeing keys shared between main thread
23945 and CPU workers that could result in a memory leak. Bugfix on
23946 0.1.0.1-rc. Fixes bug 889.
23947 - Send a valid END cell back when a client tries to connect to a
23948 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
23949 840. Patch from rovv.
23950 - Check which hops rendezvous stream cells are associated with to
23951 prevent possible guess-the-streamid injection attacks from
23952 intermediate hops. Fixes another case of bug 446. Based on patch
23954 - If a broken client asks a non-exit router to connect somewhere,
23955 do not even do the DNS lookup before rejecting the connection.
23956 Fixes another case of bug 619. Patch from rovv.
23957 - When a relay gets a create cell it can't decrypt (e.g. because it's
23958 using the wrong onion key), we were dropping it and letting the
23959 client time out. Now actually answer with a destroy cell. Fixes
23960 bug 904. Bugfix on 0.0.2pre8.
23962 o Minor bugfixes (hidden services):
23963 - Do not throw away existing introduction points on SIGHUP. Bugfix on
23964 0.0.6pre1. Patch by Karsten. Fixes bug 874.
23967 - Report the case where all signatures in a detached set are rejected
23968 differently than the case where there is an error handling the
23970 - When we realize that another process has modified our cached
23971 descriptors, print out a more useful error message rather than
23972 triggering an assertion. Fixes bug 885. Patch from Karsten.
23973 - Implement the 0x20 hack to better resist DNS poisoning: set the
23974 case on outgoing DNS requests randomly, and reject responses that do
23975 not match the case correctly. This logic can be disabled with the
23976 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
23977 of servers that do not reliably preserve case in replies. See
23978 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
23980 - Check DNS replies for more matching fields to better resist DNS
23982 - Never use OpenSSL compression: it wastes RAM and CPU trying to
23983 compress cells, which are basically all encrypted, compressed, or
23987 Changes in version 0.2.1.11-alpha - 2009-01-20
23988 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
23989 week it will take a long time to bootstrap again" bug. It also fixes
23990 an important security-related bug reported by Ilja van Sprundel. You
23991 should upgrade. (We'll send out more details about the bug once people
23992 have had some time to upgrade.)
23995 - Fix a heap-corruption bug that may be remotely triggerable on
23996 some platforms. Reported by Ilja van Sprundel.
23999 - Discard router descriptors as we load them if they are more than
24000 five days old. Otherwise if Tor is off for a long time and then
24001 starts with cached descriptors, it will try to use the onion
24002 keys in those obsolete descriptors when building circuits. Bugfix
24003 on 0.2.0.x. Fixes bug 887.
24006 - Try to make sure that the version of Libevent we're running with
24007 is binary-compatible with the one we built with. May address bug
24009 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
24010 for bug 905. Bugfix on 0.2.1.7-alpha.
24011 - Add a new --enable-local-appdata configuration switch to change
24012 the default location of the datadir on win32 from APPDATA to
24013 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
24014 entirely. Patch from coderman.
24017 - Make outbound DNS packets respect the OutboundBindAddress setting.
24018 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
24019 - When our circuit fails at the first hop (e.g. we get a destroy
24020 cell back), avoid using that OR connection anymore, and also
24021 tell all the one-hop directory requests waiting for it that they
24022 should fail. Bugfix on 0.2.1.3-alpha.
24023 - In the torify(1) manpage, mention that tsocks will leak your
24027 Changes in version 0.2.1.10-alpha - 2009-01-06
24028 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
24029 would make the bridge relay not so useful if it had DirPort set to 0,
24030 and one that could let an attacker learn a little bit of information
24031 about the bridge's users), and a bug that would cause your Tor relay
24032 to ignore a circuit create request it can't decrypt (rather than reply
24033 with an error). It also fixes a wide variety of other bugs.
24036 - If the cached networkstatus consensus is more than five days old,
24037 discard it rather than trying to use it. In theory it could
24038 be useful because it lists alternate directory mirrors, but in
24039 practice it just means we spend many minutes trying directory
24040 mirrors that are long gone from the network. Helps bug 887 a bit;
24042 - Bridge relays that had DirPort set to 0 would stop fetching
24043 descriptors shortly after startup, and then briefly resume
24044 after a new bandwidth test and/or after publishing a new bridge
24045 descriptor. Bridge users that try to bootstrap from them would
24046 get a recent networkstatus but would get descriptors from up to
24047 18 hours earlier, meaning most of the descriptors were obsolete
24048 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24049 - Prevent bridge relays from serving their 'extrainfo' document
24050 to anybody who asks, now that extrainfo docs include potentially
24051 sensitive aggregated client geoip summaries. Bugfix on
24055 - New controller event "clients_seen" to report a geoip-based summary
24056 of which countries we've seen clients from recently. Now controllers
24057 like Vidalia can show bridge operators that they're actually making
24059 - Build correctly against versions of OpenSSL 0.9.8 or later built
24060 without support for deprecated functions.
24061 - Update to the "December 19 2008" ip-to-country file.
24063 o Minor bugfixes (on 0.2.0.x):
24064 - Authorities now vote for the Stable flag for any router whose
24065 weighted MTBF is at least 5 days, regardless of the mean MTBF.
24066 - Do not remove routers as too old if we do not have any consensus
24067 document. Bugfix on 0.2.0.7-alpha.
24068 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24069 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24070 - When an exit relay resolves a stream address to a local IP address,
24071 do not just keep retrying that same exit relay over and
24072 over. Instead, just close the stream. Addresses bug 872. Bugfix
24073 on 0.2.0.32. Patch from rovv.
24074 - If a hidden service sends us an END cell, do not consider
24075 retrying the connection; just close it. Patch from rovv.
24076 - When we made bridge authorities stop serving bridge descriptors over
24077 unencrypted links, we also broke DirPort reachability testing for
24078 bridges. So bridges with a non-zero DirPort were printing spurious
24079 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
24080 - When a relay gets a create cell it can't decrypt (e.g. because it's
24081 using the wrong onion key), we were dropping it and letting the
24082 client time out. Now actually answer with a destroy cell. Fixes
24083 bug 904. Bugfix on 0.0.2pre8.
24084 - Squeeze 2-5% out of client performance (according to oprofile) by
24085 improving the implementation of some policy-manipulation functions.
24087 o Minor bugfixes (on 0.2.1.x):
24088 - Make get_interface_address() function work properly again; stop
24089 guessing the wrong parts of our address as our address.
24090 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
24091 send on that circuit. Otherwise we might violate the proposal-110
24092 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
24094 - When we're sending non-EXTEND cells to the first hop in a circuit,
24095 for example to use an encrypted directory connection, we don't need
24096 to use RELAY_EARLY cells: the first hop knows what kind of cell
24097 it is, and nobody else can even see the cell type. Conserving
24098 RELAY_EARLY cells makes it easier to cannibalize circuits like
24100 - Stop logging nameserver addresses in reverse order.
24101 - If we are retrying a directory download slowly over and over, do
24102 not automatically give up after the 254th failure. Bugfix on
24104 - Resume reporting accurate "stream end" reasons to the local control
24105 port. They were lost in the changes for Proposal 148. Bugfix on
24108 o Deprecated and removed features:
24109 - The old "tor --version --version" command, which would print out
24110 the subversion "Id" of most of the source files, is now removed. It
24111 turned out to be less useful than we'd expected, and harder to
24114 o Code simplifications and refactoring:
24115 - Change our header file guard macros to be less likely to conflict
24116 with system headers. Adam Langley noticed that we were conflicting
24117 with log.h on Android.
24118 - Tool-assisted documentation cleanup. Nearly every function or
24119 static variable in Tor should have its own documentation now.
24122 Changes in version 0.2.1.9-alpha - 2008-12-25
24123 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
24125 o New directory authorities:
24126 - gabelmoo (the authority run by Karsten Loesing) now has a new
24130 - Never use a connection with a mismatched address to extend a
24131 circuit, unless that connection is canonical. A canonical
24132 connection is one whose address is authenticated by the router's
24133 identity key, either in a NETINFO cell or in a router descriptor.
24134 - Avoid a possible memory corruption bug when receiving hidden service
24135 descriptors. Bugfix on 0.2.1.6-alpha.
24138 - Fix a logic error that would automatically reject all but the first
24139 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
24140 part of bug 813/868. Bug spotted by coderman.
24141 - When a stream at an exit relay is in state "resolving" or
24142 "connecting" and it receives an "end" relay cell, the exit relay
24143 would silently ignore the end cell and not close the stream. If
24144 the client never closes the circuit, then the exit relay never
24145 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
24146 reported by "wood".
24147 - When we can't initialize DNS because the network is down, do not
24148 automatically stop Tor from starting. Instead, retry failed
24149 dns_init() every 10 minutes, and change the exit policy to reject
24150 *:* until one succeeds. Fixes bug 691.
24153 - Give a better error message when an overzealous init script says
24154 "sudo -u username tor --user username". Makes Bug 882 easier for
24156 - When a directory authority gives us a new guess for our IP address,
24157 log which authority we used. Hopefully this will help us debug
24158 the recent complaints about bad IP address guesses.
24159 - Detect svn revision properly when we're using git-svn.
24160 - Try not to open more than one descriptor-downloading connection
24161 to an authority at once. This should reduce load on directory
24162 authorities. Fixes bug 366.
24163 - Add cross-certification to newly generated certificates, so that
24164 a signing key is enough information to look up a certificate.
24165 Partial implementation of proposal 157.
24166 - Start serving certificates by <identity digest, signing key digest>
24167 pairs. Partial implementation of proposal 157.
24168 - Clients now never report any stream end reason except 'MISC'.
24169 Implements proposal 148.
24170 - On platforms with a maximum syslog string length, truncate syslog
24171 messages to that length ourselves, rather than relying on the
24172 system to do it for us.
24173 - Optimize out calls to time(NULL) that occur for every IO operation,
24174 or for every cell. On systems where time() is a slow syscall,
24175 this fix will be slightly helpful.
24176 - Exit servers can now answer resolve requests for ip6.arpa addresses.
24177 - When we download a descriptor that we then immediately (as
24178 a directory authority) reject, do not retry downloading it right
24179 away. Should save some bandwidth on authorities. Fix for bug
24180 888. Patch by Sebastian Hahn.
24181 - When a download gets us zero good descriptors, do not notify
24182 Tor that new directory information has arrived.
24183 - Avoid some nasty corner cases in the logic for marking connections
24184 as too old or obsolete or noncanonical for circuits. Partial
24187 o Minor features (controller):
24188 - New CONSENSUS_ARRIVED event to note when a new consensus has
24189 been fetched and validated.
24190 - When we realize that another process has modified our cached
24191 descriptors file, print out a more useful error message rather
24192 than triggering an assertion. Fixes bug 885. Patch from Karsten.
24193 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
24194 controllers to prevent SIGHUP from reloading the
24195 configuration. Fixes bug 856.
24198 - Resume using the correct "REASON=" stream when telling the
24199 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
24200 - When a canonical connection appears later in our internal list
24201 than a noncanonical one for a given OR ID, always use the
24202 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
24204 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24205 seconds. Warn the user if lower values are given in the
24206 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24207 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24208 user if lower values are given in the configuration. Bugfix on
24209 0.1.1.17-rc. Patch by Sebastian.
24210 - Fix a race condition when freeing keys shared between main thread
24211 and CPU workers that could result in a memory leak. Bugfix on
24212 0.1.0.1-rc. Fixes bug 889.
24214 o Minor bugfixes (hidden services):
24215 - Do not throw away existing introduction points on SIGHUP (bugfix on
24216 0.0.6pre1); also, do not stall hidden services because we're
24217 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
24218 by John Brooks. Patch by Karsten. Fixes bug 874.
24219 - Fix a memory leak when we decline to add a v2 rendezvous
24220 descriptor to the cache because we already had a v0 descriptor
24221 with the same ID. Bugfix on 0.2.0.18-alpha.
24223 o Deprecated and removed features:
24224 - RedirectExits has been removed. It was deprecated since
24226 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
24227 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
24228 - Cell pools are now always enabled; --disable-cell-pools is ignored.
24230 o Code simplifications and refactoring:
24231 - Rename the confusing or_is_obsolete field to the more appropriate
24232 is_bad_for_new_circs, and move it to or_connection_t where it
24234 - Move edge-only flags from connection_t to edge_connection_t: not
24235 only is this better coding, but on machines of plausible alignment,
24236 it should save 4-8 bytes per connection_t. "Every little bit helps."
24237 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
24238 for consistency; keep old option working for backward compatibility.
24239 - Simplify the code for finding connections to use for a circuit.
24242 Changes in version 0.2.1.8-alpha - 2008-12-08
24243 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
24244 builds better on unusual platforms like Solaris and old OS X, and
24245 fixes a variety of other issues.
24248 - New DirPortFrontPage option that takes an html file and publishes
24249 it as "/" on the DirPort. Now relay operators can provide a
24250 disclaimer without needing to set up a separate webserver. There's
24251 a sample disclaimer in contrib/tor-exit-notice.html.
24254 - When the client is choosing entry guards, now it selects at most
24255 one guard from a given relay family. Otherwise we could end up with
24256 all of our entry points into the network run by the same operator.
24257 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
24260 - Fix a DOS opportunity during the voting signature collection process
24261 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
24262 - Fix a possible segfault when establishing an exit connection. Bugfix
24266 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
24268 - Made Tor a little less aggressive about deleting expired
24269 certificates. Partial fix for bug 854.
24270 - Stop doing unaligned memory access that generated bus errors on
24271 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
24272 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
24273 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
24274 - Make USR2 log-level switch take effect immediately. Bugfix on
24276 - If one win32 nameserver fails to get added, continue adding the
24277 rest, and don't automatically fail.
24278 - Use fcntl() for locking when flock() is not available. Should fix
24279 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
24280 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24281 could make gcc generate non-functional binary search code. Bugfix
24283 - Build correctly on platforms without socklen_t.
24284 - Avoid potential crash on internal error during signature collection.
24285 Fixes bug 864. Patch from rovv.
24286 - Do not use C's stdio library for writing to log files. This will
24287 improve logging performance by a minute amount, and will stop
24288 leaking fds when our disk is full. Fixes bug 861.
24289 - Stop erroneous use of O_APPEND in cases where we did not in fact
24290 want to re-seek to the end of a file before every last write().
24291 - Correct handling of possible malformed authority signing key
24292 certificates with internal signature types. Fixes bug 880. Bugfix
24294 - Fix a hard-to-trigger resource leak when logging credential status.
24298 - Directory mirrors no longer fetch the v1 directory or
24299 running-routers files. They are obsolete, and nobody asks for them
24300 anymore. This is the first step to making v1 authorities obsolete.
24302 o Minor features (controller):
24303 - Return circuit purposes in response to GETINFO circuit-status. Fixes
24307 Changes in version 0.2.0.32 - 2008-11-20
24308 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
24309 packages (and maybe other packages) noticed by Theo de Raadt, fixes
24310 a smaller security flaw that might allow an attacker to access local
24311 services, further improves hidden service performance, and fixes a
24312 variety of other issues.
24315 - The "User" and "Group" config options did not clear the
24316 supplementary group entries for the Tor process. The "User" option
24317 is now more robust, and we now set the groups to the specified
24318 user's primary group. The "Group" option is now ignored. For more
24319 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
24320 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
24321 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
24322 - The "ClientDNSRejectInternalAddresses" config option wasn't being
24323 consistently obeyed: if an exit relay refuses a stream because its
24324 exit policy doesn't allow it, we would remember what IP address
24325 the relay said the destination address resolves to, even if it's
24326 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
24329 - Fix a DOS opportunity during the voting signature collection process
24330 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
24332 o Major bugfixes (hidden services):
24333 - When fetching v0 and v2 rendezvous service descriptors in parallel,
24334 we were failing the whole hidden service request when the v0
24335 descriptor fetch fails, even if the v2 fetch is still pending and
24336 might succeed. Similarly, if the last v2 fetch fails, we were
24337 failing the whole hidden service request even if a v0 fetch is
24338 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
24339 - When extending a circuit to a hidden service directory to upload a
24340 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
24341 requests failed, because the router descriptor has not been
24342 downloaded yet. In these cases, do not attempt to upload the
24343 rendezvous descriptor, but wait until the router descriptor is
24344 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
24345 descriptor from a hidden service directory for which the router
24346 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
24350 - Fix several infrequent memory leaks spotted by Coverity.
24351 - When testing for libevent functions, set the LDFLAGS variable
24352 correctly. Found by Riastradh.
24353 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
24354 bootstrapping with tunneled directory connections. Bugfix on
24355 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
24356 - When asked to connect to A.B.exit:80, if we don't know the IP for A
24357 and we know that server B rejects most-but-not all connections to
24358 port 80, we would previously reject the connection. Now, we assume
24359 the user knows what they were asking for. Fixes bug 752. Bugfix
24360 on 0.0.9rc5. Diagnosed by BarkerJr.
24361 - If we overrun our per-second write limits a little, count this as
24362 having used up our write allocation for the second, and choke
24363 outgoing directory writes. Previously, we had only counted this when
24364 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
24365 Bugfix on 0.2.0.x (??).
24366 - Remove the old v2 directory authority 'lefkada' from the default
24367 list. It has been gone for many months.
24368 - Stop doing unaligned memory access that generated bus errors on
24369 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
24370 - Make USR2 log-level switch take effect immediately. Bugfix on
24373 o Minor bugfixes (controller):
24374 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
24375 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
24378 Changes in version 0.2.1.7-alpha - 2008-11-08
24379 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
24380 packages (and maybe other packages) noticed by Theo de Raadt, fixes
24381 a smaller security flaw that might allow an attacker to access local
24382 services, adds better defense against DNS poisoning attacks on exit
24383 relays, further improves hidden service performance, and fixes a
24384 variety of other issues.
24387 - The "ClientDNSRejectInternalAddresses" config option wasn't being
24388 consistently obeyed: if an exit relay refuses a stream because its
24389 exit policy doesn't allow it, we would remember what IP address
24390 the relay said the destination address resolves to, even if it's
24391 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
24392 - The "User" and "Group" config options did not clear the
24393 supplementary group entries for the Tor process. The "User" option
24394 is now more robust, and we now set the groups to the specified
24395 user's primary group. The "Group" option is now ignored. For more
24396 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
24397 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
24398 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
24399 - Do not use or believe expired v3 authority certificates. Patch
24400 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
24403 - Now NodeFamily and MyFamily config options allow spaces in
24404 identity fingerprints, so it's easier to paste them in.
24405 Suggested by Lucky Green.
24406 - Implement the 0x20 hack to better resist DNS poisoning: set the
24407 case on outgoing DNS requests randomly, and reject responses that do
24408 not match the case correctly. This logic can be disabled with the
24409 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
24410 of servers that do not reliably preserve case in replies. See
24411 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
24413 - Preserve case in replies to DNSPort requests in order to support
24414 the 0x20 hack for resisting DNS poisoning attacks.
24416 o Hidden service performance improvements:
24417 - When the client launches an introduction circuit, retry with a
24418 new circuit after 30 seconds rather than 60 seconds.
24419 - Launch a second client-side introduction circuit in parallel
24420 after a delay of 15 seconds (based on work by Christian Wilms).
24421 - Hidden services start out building five intro circuits rather
24422 than three, and when the first three finish they publish a service
24423 descriptor using those. Now we publish our service descriptor much
24424 faster after restart.
24427 - Minor fix in the warning messages when you're having problems
24428 bootstrapping; also, be more forgiving of bootstrap problems when
24429 we're still making incremental progress on a given bootstrap phase.
24430 - When we're choosing an exit node for a circuit, and we have
24431 no pending streams, choose a good general exit rather than one that
24432 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
24433 - Send a valid END cell back when a client tries to connect to a
24434 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
24435 840. Patch from rovv.
24436 - If a broken client asks a non-exit router to connect somewhere,
24437 do not even do the DNS lookup before rejecting the connection.
24438 Fixes another case of bug 619. Patch from rovv.
24439 - Fix another case of assuming, when a specific exit is requested,
24440 that we know more than the user about what hosts it allows.
24441 Fixes another case of bug 752. Patch from rovv.
24442 - Check which hops rendezvous stream cells are associated with to
24443 prevent possible guess-the-streamid injection attacks from
24444 intermediate hops. Fixes another case of bug 446. Based on patch
24446 - Avoid using a negative right-shift when comparing 32-bit
24447 addresses. Possible fix for bug 845 and bug 811.
24448 - Make the assert_circuit_ok() function work correctly on circuits that
24449 have already been marked for close.
24450 - Fix read-off-the-end-of-string error in unit tests when decoding
24451 introduction points.
24452 - Fix uninitialized size field for memory area allocation: may improve
24453 memory performance during directory parsing.
24454 - Treat duplicate certificate fetches as failures, so that we do
24455 not try to re-fetch an expired certificate over and over and over.
24456 - Do not say we're fetching a certificate when we'll in fact skip it
24457 because of a pending download.
24460 Changes in version 0.2.1.6-alpha - 2008-09-30
24461 Tor 0.2.1.6-alpha further improves performance and robustness of
24462 hidden services, starts work on supporting per-country relay selection,
24463 and fixes a variety of smaller issues.
24466 - Implement proposal 121: make it possible to build hidden services
24467 that only certain clients are allowed to connect to. This is
24468 enforced at several points, so that unauthorized clients are unable
24469 to send INTRODUCE cells to the service, or even (depending on the
24470 type of authentication) to learn introduction points. This feature
24471 raises the bar for certain kinds of active attacks against hidden
24472 services. Code by Karsten Loesing.
24473 - Relays now store and serve v2 hidden service descriptors by default,
24474 i.e., the new default value for HidServDirectoryV2 is 1. This is
24475 the last step in proposal 114, which aims to make hidden service
24476 lookups more reliable.
24477 - Start work to allow node restrictions to include country codes. The
24478 syntax to exclude nodes in a country with country code XX is
24479 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
24480 refinement to decide what config options should take priority if
24481 you ask to both use a particular node and exclude it.
24482 - Allow ExitNodes list to include IP ranges and country codes, just
24483 like the Exclude*Nodes lists. Patch from Robert Hogan.
24486 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
24487 Tor to fail to start if you had it configured to use a bridge
24488 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
24489 - When extending a circuit to a hidden service directory to upload a
24490 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
24491 requests failed, because the router descriptor had not been
24492 downloaded yet. In these cases, we now wait until the router
24493 descriptor is downloaded, and then retry. Likewise, clients
24494 now skip over a hidden service directory if they don't yet have
24495 its router descriptor, rather than futilely requesting it and
24496 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
24498 - When fetching v0 and v2 rendezvous service descriptors in parallel,
24499 we were failing the whole hidden service request when the v0
24500 descriptor fetch fails, even if the v2 fetch is still pending and
24501 might succeed. Similarly, if the last v2 fetch fails, we were
24502 failing the whole hidden service request even if a v0 fetch is
24503 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
24504 - DNS replies need to have names matching their requests, but
24505 these names should be in the questions section, not necessarily
24506 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
24509 - Update to the "September 1 2008" ip-to-country file.
24510 - Allow ports 465 and 587 in the default exit policy again. We had
24511 rejected them in 0.1.0.15, because back in 2005 they were commonly
24512 misconfigured and ended up as spam targets. We hear they are better
24513 locked down these days.
24514 - Use a lockfile to make sure that two Tor processes are not
24515 simultaneously running with the same datadir.
24516 - Serve the latest v3 networkstatus consensus via the control
24517 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
24518 - Better logging about stability/reliability calculations on directory
24520 - Drop the requirement to have an open dir port for storing and
24521 serving v2 hidden service descriptors.
24522 - Directory authorities now serve a /tor/dbg-stability.txt URL to
24523 help debug WFU and MTBF calculations.
24524 - Implement most of Proposal 152: allow specialized servers to permit
24525 single-hop circuits, and clients to use those servers to build
24526 single-hop circuits when using a specialized controller. Patch
24527 from Josh Albrecht. Resolves feature request 768.
24528 - Add a -p option to tor-resolve for specifying the SOCKS port: some
24529 people find host:port too confusing.
24530 - Make TrackHostExit mappings expire a while after their last use, not
24531 after their creation. Patch from Robert Hogan.
24532 - Provide circuit purposes along with circuit events to the controller.
24535 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
24537 - Fixed some memory leaks -- some quite frequent, some almost
24538 impossible to trigger -- based on results from Coverity.
24539 - When testing for libevent functions, set the LDFLAGS variable
24540 correctly. Found by Riastradh.
24541 - Fix an assertion bug in parsing policy-related options; possible fix
24543 - Catch and report a few more bootstrapping failure cases when Tor
24544 fails to establish a TCP connection. Cleanup on 0.2.1.x.
24545 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
24546 bootstrapping with tunneled directory connections. Bugfix on
24547 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
24548 - When asked to connect to A.B.exit:80, if we don't know the IP for A
24549 and we know that server B rejects most-but-not all connections to
24550 port 80, we would previously reject the connection. Now, we assume
24551 the user knows what they were asking for. Fixes bug 752. Bugfix
24552 on 0.0.9rc5. Diagnosed by BarkerJr.
24553 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
24554 service directories if they have no advertised dir port. Bugfix
24556 - If we overrun our per-second write limits a little, count this as
24557 having used up our write allocation for the second, and choke
24558 outgoing directory writes. Previously, we had only counted this when
24559 we had met our limits precisely. Fixes bug 824. Patch by rovv.
24560 Bugfix on 0.2.0.x (??).
24561 - Avoid a "0 divided by 0" calculation when calculating router uptime
24562 at directory authorities. Bugfix on 0.2.0.8-alpha.
24563 - Make DNS resolved controller events into "CLOSED", not
24564 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
24566 - Fix a bug where an unreachable relay would establish enough
24567 reachability testing circuits to do a bandwidth test -- if
24568 we already have a connection to the middle hop of the testing
24569 circuit, then it could establish the last hop by using the existing
24570 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
24571 circuits no longer use entry guards in 0.2.1.3-alpha.
24572 - If we have correct permissions on $datadir, we complain to stdout
24573 and fail to start. But dangerous permissions on
24574 $datadir/cached-status/ would cause us to open a log and complain
24575 there. Now complain to stdout and fail to start in both cases. Fixes
24576 bug 820, reported by seeess.
24577 - Remove the old v2 directory authority 'lefkada' from the default
24578 list. It has been gone for many months.
24580 o Code simplifications and refactoring:
24581 - Revise the connection_new functions so that a more typesafe variant
24582 exists. This will work better with Coverity, and let us find any
24583 actual mistakes we're making here.
24584 - Refactor unit testing logic so that dmalloc can be used sensibly
24585 with unit tests to check for memory leaks.
24586 - Move all hidden-service related fields from connection and circuit
24587 structure to substructures: this way they won't eat so much memory.
24590 Changes in version 0.2.0.31 - 2008-09-03
24591 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
24592 a big bug we're seeing where in rare cases traffic from one Tor stream
24593 gets mixed into another stream, and fixes a variety of smaller issues.
24596 - Make sure that two circuits can never exist on the same connection
24597 with the same circuit ID, even if one is marked for close. This
24598 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
24599 - Relays now reject risky extend cells: if the extend cell includes
24600 a digest of all zeroes, or asks to extend back to the relay that
24601 sent the extend cell, tear down the circuit. Ideas suggested
24603 - If not enough of our entry guards are available so we add a new
24604 one, we might use the new one even if it overlapped with the
24605 current circuit's exit relay (or its family). Anonymity bugfix
24606 pointed out by rovv.
24609 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
24610 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
24611 - Correctly detect the presence of the linux/netfilter_ipv4.h header
24612 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
24613 - Pick size of default geoip filename string correctly on windows.
24614 Fixes bug 806. Bugfix on 0.2.0.30.
24615 - Make the autoconf script accept the obsolete --with-ssl-dir
24616 option as an alias for the actually-working --with-openssl-dir
24617 option. Fix the help documentation to recommend --with-openssl-dir.
24618 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
24619 - When using the TransPort option on OpenBSD, and using the User
24620 option to change UID and drop privileges, make sure to open
24621 /dev/pf before dropping privileges. Fixes bug 782. Patch from
24622 Christopher Davis. Bugfix on 0.1.2.1-alpha.
24623 - Try to attach connections immediately upon receiving a RENDEZVOUS2
24624 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
24625 on the client side when connecting to a hidden service. Bugfix
24626 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
24627 - When closing an application-side connection because its circuit is
24628 getting torn down, generate the stream event correctly. Bugfix on
24629 0.1.2.x. Anonymous patch.
24632 Changes in version 0.2.1.5-alpha - 2008-08-31
24633 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
24634 in a lot of the infrastructure for adding authorization to hidden
24635 services, lays the groundwork for having clients read their load
24636 balancing information out of the networkstatus consensus rather than
24637 the individual router descriptors, addresses two potential anonymity
24638 issues, and fixes a variety of smaller issues.
24641 - Convert many internal address representations to optionally hold
24643 - Generate and accept IPv6 addresses in many protocol elements.
24644 - Make resolver code handle nameservers located at ipv6 addresses.
24645 - Begin implementation of proposal 121 ("Client authorization for
24646 hidden services"): configure hidden services with client
24647 authorization, publish descriptors for them, and configure
24648 authorization data for hidden services at clients. The next
24649 step is to actually access hidden services that perform client
24651 - More progress toward proposal 141: Network status consensus
24652 documents and votes now contain bandwidth information for each
24653 router and a summary of that router's exit policy. Eventually this
24654 will be used by clients so that they do not have to download every
24655 known descriptor before building circuits.
24657 o Major bugfixes (on 0.2.0.x and before):
24658 - When sending CREATED cells back for a given circuit, use a 64-bit
24659 connection ID to find the right connection, rather than an addr:port
24660 combination. Now that we can have multiple OR connections between
24661 the same ORs, it is no longer possible to use addr:port to uniquely
24662 identify a connection.
24663 - Relays now reject risky extend cells: if the extend cell includes
24664 a digest of all zeroes, or asks to extend back to the relay that
24665 sent the extend cell, tear down the circuit. Ideas suggested
24667 - If not enough of our entry guards are available so we add a new
24668 one, we might use the new one even if it overlapped with the
24669 current circuit's exit relay (or its family). Anonymity bugfix
24670 pointed out by rovv.
24673 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
24674 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
24675 - When using the TransPort option on OpenBSD, and using the User
24676 option to change UID and drop privileges, make sure to open /dev/pf
24677 before dropping privileges. Fixes bug 782. Patch from Christopher
24678 Davis. Bugfix on 0.1.2.1-alpha.
24679 - Correctly detect the presence of the linux/netfilter_ipv4.h header
24680 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
24681 - Add a missing safe_str() call for a debug log message.
24682 - Use 64 bits instead of 32 bits for connection identifiers used with
24683 the controller protocol, to greatly reduce risk of identifier reuse.
24684 - Make the autoconf script accept the obsolete --with-ssl-dir
24685 option as an alias for the actually-working --with-openssl-dir
24686 option. Fix the help documentation to recommend --with-openssl-dir.
24687 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
24690 - Rate-limit too-many-sockets messages: when they happen, they happen
24691 a lot. Resolves bug 748.
24692 - Resist DNS poisoning a little better by making sure that names in
24693 answer sections match.
24694 - Print the SOCKS5 error message string as well as the error code
24695 when a tor-resolve request fails. Patch from Jacob.
24698 Changes in version 0.2.1.4-alpha - 2008-08-04
24699 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
24702 - The address part of exit policies was not correctly written
24703 to router descriptors. This generated router descriptors that failed
24704 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
24706 - Tor triggered a false assert when extending a circuit to a relay
24707 but we already have a connection open to that relay. Noticed by
24708 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
24711 - Fix a hidden service logging bug: in some edge cases, the router
24712 descriptor of a previously picked introduction point becomes
24713 obsolete and we need to give up on it rather than continually
24714 complaining that it has become obsolete. Observed by xiando. Bugfix
24717 o Removed features:
24718 - Take out the TestVia config option, since it was a workaround for
24719 a bug that was fixed in Tor 0.1.1.21.
24722 Changes in version 0.2.1.3-alpha - 2008-08-03
24723 Tor 0.2.1.3-alpha implements most of the pieces to prevent
24724 infinite-length circuit attacks (see proposal 110); fixes a bug that
24725 might cause exit relays to corrupt streams they send back; allows
24726 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
24727 ExcludeExitNodes config options; and fixes a big pile of bugs.
24729 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
24730 - Send a bootstrap problem "warn" event on the first problem if the
24731 reason is NO_ROUTE (that is, our network is down).
24734 - Implement most of proposal 110: The first K cells to be sent
24735 along a circuit are marked as special "early" cells; only K "early"
24736 cells will be allowed. Once this code is universal, we can block
24737 certain kinds of DOS attack by requiring that EXTEND commands must
24738 be sent using an "early" cell.
24741 - Try to attach connections immediately upon receiving a RENDEZVOUS2
24742 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
24743 on the client side when connecting to a hidden service. Bugfix
24744 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
24745 - Ensure that two circuits can never exist on the same connection
24746 with the same circuit ID, even if one is marked for close. This
24747 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
24750 - When relays do their initial bandwidth measurement, don't limit
24751 to just our entry guards for the test circuits. Otherwise we tend
24752 to have multiple test circuits going through a single entry guard,
24753 which makes our bandwidth test less accurate. Fixes part of bug 654;
24754 patch contributed by Josh Albrecht.
24755 - Add an ExcludeExitNodes option so users can list a set of nodes
24756 that should be be excluded from the exit node position, but
24757 allowed elsewhere. Implements proposal 151.
24758 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
24759 ExcludeNodes and ExcludeExitNodes lists.
24760 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
24761 be more efficient. Formerly it was quadratic in the number of
24762 servers; now it should be linear. Fixes bug 509.
24763 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
24764 and n_conn_id_digest fields into a separate structure that's
24765 only needed when the circuit has not yet attached to an n_conn.
24768 - Change the contrib/tor.logrotate script so it makes the new
24769 logs as "_tor:_tor" rather than the default, which is generally
24770 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
24771 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
24772 warnings (occasionally), but it can also cause the compiler to
24773 eliminate error-checking code. Suggested by Peter Gutmann.
24774 - When a hidden service is giving up on an introduction point candidate
24775 that was not included in the last published rendezvous descriptor,
24776 don't reschedule publication of the next descriptor. Fixes bug 763.
24778 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
24779 HiddenServiceExcludeNodes as obsolete: they never worked properly,
24780 and nobody claims to be using them. Fixes bug 754. Bugfix on
24781 0.1.0.1-rc. Patch from Christian Wilms.
24782 - Fix a small alignment and memory-wasting bug on buffer chunks.
24785 o Minor bugfixes (controller):
24786 - When closing an application-side connection because its circuit
24787 is getting torn down, generate the stream event correctly.
24788 Bugfix on 0.1.2.x. Anonymous patch.
24790 o Removed features:
24791 - Remove all backward-compatibility code to support relays running
24792 versions of Tor so old that they no longer work at all on the
24796 Changes in version 0.2.0.30 - 2008-07-15
24798 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
24799 warnings (occasionally), but it can also cause the compiler to
24800 eliminate error-checking code. Suggested by Peter Gutmann.
24803 Changes in version 0.2.0.29-rc - 2008-07-08
24804 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
24805 hidden-service performance bugs, and fixes a bunch of smaller bugs.
24808 - If you have more than one bridge but don't know their keys,
24809 you would only launch a request for the descriptor of the first one
24810 on your list. (Tor considered launching requests for the others, but
24811 found that it already had a connection on the way for $0000...0000
24812 so it didn't open another.) Bugfix on 0.2.0.x.
24813 - If you have more than one bridge but don't know their keys, and the
24814 connection to one of the bridges failed, you would cancel all
24815 pending bridge connections. (After all, they all have the same
24816 digest.) Bugfix on 0.2.0.x.
24817 - When a hidden service was trying to establish an introduction point,
24818 and Tor had built circuits preemptively for such purposes, we
24819 were ignoring all the preemptive circuits and launching a new one
24820 instead. Bugfix on 0.2.0.14-alpha.
24821 - When a hidden service was trying to establish an introduction point,
24822 and Tor *did* manage to reuse one of the preemptively built
24823 circuits, it didn't correctly remember which one it used,
24824 so it asked for another one soon after, until there were no
24825 more preemptive circuits, at which point it launched one from
24826 scratch. Bugfix on 0.0.9.x.
24827 - Make directory servers include the X-Your-Address-Is: http header in
24828 their responses even for begin_dir conns. Now clients who only
24829 ever use begin_dir connections still have a way to learn their IP
24830 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
24833 - Fix a macro/CPP interaction that was confusing some compilers:
24834 some GCCs don't like #if/#endif pairs inside macro arguments.
24836 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
24837 Fixes bug 704; fix from Steven Murdoch.
24838 - When opening /dev/null in finish_daemonize(), do not pass the
24839 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
24840 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
24841 - Correctly detect transparent proxy support on Linux hosts that
24842 require in.h to be included before netfilter_ipv4.h. Patch
24844 - Disallow session resumption attempts during the renegotiation
24845 stage of the v2 handshake protocol. Clients should never be trying
24846 session resumption at this point, but apparently some did, in
24847 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
24848 found by Geoff Goodell.
24851 Changes in version 0.2.1.2-alpha - 2008-06-20
24852 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
24853 make it easier to set up your own private Tor network; fixes several
24854 big bugs with using more than one bridge relay; fixes a big bug with
24855 offering hidden services quickly after Tor starts; and uses a better
24856 API for reporting potential bootstrapping problems to the controller.
24859 - New TestingTorNetwork config option to allow adjustment of
24860 previously constant values that, while reasonable, could slow
24861 bootstrapping. Implements proposal 135. Patch from Karsten.
24864 - If you have more than one bridge but don't know their digests,
24865 you would only learn a request for the descriptor of the first one
24866 on your list. (Tor considered launching requests for the others, but
24867 found that it already had a connection on the way for $0000...0000
24868 so it didn't open another.) Bugfix on 0.2.0.x.
24869 - If you have more than one bridge but don't know their digests,
24870 and the connection to one of the bridges failed, you would cancel
24871 all pending bridge connections. (After all, they all have the
24872 same digest.) Bugfix on 0.2.0.x.
24873 - When establishing a hidden service, introduction points that
24874 originate from cannibalized circuits are completely ignored and not
24875 included in rendezvous service descriptors. This might be another
24876 reason for delay in making a hidden service available. Bugfix
24877 from long ago (0.0.9.x?)
24880 - Allow OpenSSL to use dynamic locks if it wants.
24881 - When building a consensus, do not include routers that are down.
24882 This will cut down 30% to 40% on consensus size. Implements
24884 - In directory authorities' approved-routers files, allow
24885 fingerprints with or without space.
24886 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
24887 controller can query our current bootstrap state in case it attaches
24888 partway through and wants to catch up.
24889 - Send an initial "Starting" bootstrap status event, so we have a
24890 state to start out in.
24893 - Asking for a conditional consensus at .../consensus/<fingerprints>
24894 would crash a dirserver if it did not already have a
24895 consensus. Bugfix on 0.2.1.1-alpha.
24896 - Clean up some macro/CPP interactions: some GCC versions don't like
24897 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
24900 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
24901 - Directory authorities shouldn't complain about bootstrapping
24902 problems just because they do a lot of reachability testing and
24903 some of the connection attempts fail.
24904 - Start sending "count" and "recommendation" key/value pairs in
24905 bootstrap problem status events, so the controller can hear about
24906 problems even before Tor decides they're worth reporting for sure.
24907 - If you're using bridges, generate "bootstrap problem" warnings
24908 as soon as you run out of working bridges, rather than waiting
24909 for ten failures -- which will never happen if you have less than
24911 - If we close our OR connection because there's been a circuit
24912 pending on it for too long, we were telling our bootstrap status
24913 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
24916 Changes in version 0.2.1.1-alpha - 2008-06-13
24917 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
24918 were making the Tor process bloat especially on Linux; makes our TLS
24919 handshake blend in better; sends "bootstrap phase" status events to
24920 the controller, so it can keep the user informed of progress (and
24921 problems) fetching directory information and establishing circuits;
24922 and adds a variety of smaller features.
24925 - More work on making our TLS handshake blend in: modify the list
24926 of ciphers advertised by OpenSSL in client mode to even more
24927 closely resemble a common web browser. We cheat a little so that
24928 we can advertise ciphers that the locally installed OpenSSL doesn't
24930 - Start sending "bootstrap phase" status events to the controller,
24931 so it can keep the user informed of progress fetching directory
24932 information and establishing circuits. Also inform the controller
24933 if we think we're stuck at a particular bootstrap phase. Implements
24935 - Resume using OpenSSL's RAND_poll() for better (and more portable)
24936 cross-platform entropy collection again. We used to use it, then
24937 stopped using it because of a bug that could crash systems that
24938 called RAND_poll when they had a lot of fds open. It looks like the
24939 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
24940 at startup, and to call RAND_poll() when we reseed later only if
24941 we have a non-buggy OpenSSL version.
24944 - When we choose to abandon a new entry guard because we think our
24945 older ones might be better, close any circuits pending on that
24946 new entry guard connection. This fix should make us recover much
24947 faster when our network is down and then comes back. Bugfix on
24948 0.1.2.8-beta; found by lodger.
24950 o Memory fixes and improvements:
24951 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
24952 to avoid unused RAM in buffer chunks and memory pools.
24953 - Speed up parsing and cut down on memory fragmentation by using
24954 stack-style allocations for parsing directory objects. Previously,
24955 this accounted for over 40% of allocations from within Tor's code
24956 on a typical directory cache.
24957 - Use a Bloom filter rather than a digest-based set to track which
24958 descriptors we need to keep around when we're cleaning out old
24959 router descriptors. This speeds up the computation significantly,
24960 and may reduce fragmentation.
24961 - Reduce the default smartlist size from 32 to 16; it turns out that
24962 most smartlists hold around 8-12 elements tops.
24963 - Make dumpstats() log the fullness and size of openssl-internal
24965 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
24966 patch to their OpenSSL, turn it on to save memory on servers. This
24967 patch will (with any luck) get included in a mainline distribution
24969 - Never use OpenSSL compression: it wastes RAM and CPU trying to
24970 compress cells, which are basically all encrypted, compressed,
24974 - Stop reloading the router list from disk for no reason when we
24975 run out of reachable directory mirrors. Once upon a time reloading
24976 it would set the 'is_running' flag back to 1 for them. It hasn't
24977 done that for a long time.
24978 - In very rare situations new hidden service descriptors were
24979 published earlier than 30 seconds after the last change to the
24980 service. (We currently think that a hidden service descriptor
24981 that's been stable for 30 seconds is worth publishing.)
24984 - Allow separate log levels to be configured for different logging
24985 domains. For example, this allows one to log all notices, warnings,
24986 or errors, plus all memory management messages of level debug or
24987 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
24988 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
24989 and stop using a warning that had become unfixably verbose under
24991 - New --hush command-line option similar to --quiet. While --quiet
24992 disables all logging to the console on startup, --hush limits the
24993 output to messages of warning and error severity.
24994 - Servers support a new URL scheme for consensus downloads that
24995 allows the client to specify which authorities are trusted.
24996 The server then only sends the consensus if the client will trust
24997 it. Otherwise a 404 error is sent back. Clients use this
24998 new scheme when the server supports it (meaning it's running
24999 0.2.1.1-alpha or later). Implements proposal 134.
25000 - New configure/torrc options (--enable-geoip-stats,
25001 DirRecordUsageByCountry) to record how many IPs we've served
25002 directory info to in each country code, how many status documents
25003 total we've sent to each country code, and what share of the total
25004 directory requests we should expect to see.
25005 - Use the TLS1 hostname extension to more closely resemble browser
25007 - Lots of new unit tests.
25008 - Add a macro to implement the common pattern of iterating through
25009 two parallel lists in lockstep.
25012 Changes in version 0.2.0.28-rc - 2008-06-13
25013 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
25014 performance bug, and fixes a bunch of smaller bugs.
25017 - Fix a bug where, when we were choosing the 'end stream reason' to
25018 put in our relay end cell that we send to the exit relay, Tor
25019 clients on Windows were sometimes sending the wrong 'reason'. The
25020 anonymity problem is that exit relays may be able to guess whether
25021 the client is running Windows, thus helping partition the anonymity
25022 set. Down the road we should stop sending reasons to exit relays,
25023 or otherwise prevent future versions of this bug.
25026 - While setting up a hidden service, some valid introduction circuits
25027 were overlooked and abandoned. This might be the reason for
25028 the long delay in making a hidden service available. Bugfix on
25032 - Update to the "June 9 2008" ip-to-country file.
25033 - Run 'make test' as part of 'make dist', so we stop releasing so
25034 many development snapshots that fail their unit tests.
25037 - When we're checking if we have enough dir info for each relay
25038 to begin establishing circuits, make sure that we actually have
25039 the descriptor listed in the consensus, not just any descriptor.
25041 - Bridge relays no longer print "xx=0" in their extrainfo document
25042 for every single country code in the geoip db. Bugfix on
25044 - Only warn when we fail to load the geoip file if we were planning to
25045 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
25046 - If we change our MaxAdvertisedBandwidth and then reload torrc,
25047 Tor won't realize it should publish a new relay descriptor. Fixes
25048 bug 688, reported by mfr. Bugfix on 0.1.2.x.
25049 - When we haven't had any application requests lately, don't bother
25050 logging that we have expired a bunch of descriptors. Bugfix
25052 - Make relay cells written on a connection count as non-padding when
25053 tracking how long a connection has been in use. Bugfix on
25054 0.2.0.1-alpha. Spotted by lodger.
25055 - Fix unit tests in 0.2.0.27-rc.
25056 - Fix compile on Windows.
25059 Changes in version 0.2.0.27-rc - 2008-06-03
25060 Tor 0.2.0.27-rc adds a few features we left out of the earlier
25061 release candidates. In particular, we now include an IP-to-country
25062 GeoIP database, so controllers can easily look up what country a
25063 given relay is in, and so bridge relays can give us some sanitized
25064 summaries about which countries are making use of bridges. (See proposal
25065 126-geoip-fetching.txt for details.)
25068 - Include an IP-to-country GeoIP file in the tarball, so bridge
25069 relays can report sanitized summaries of the usage they're seeing.
25072 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
25073 Robert Hogan. Fixes the first part of bug 681.
25074 - Make bridge authorities never serve extrainfo docs.
25075 - Add support to detect Libevent versions in the 1.4.x series
25077 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
25078 - Include a new contrib/tor-exit-notice.html file that exit relay
25079 operators can put on their website to help reduce abuse queries.
25082 - When tunneling an encrypted directory connection, and its first
25083 circuit fails, do not leave it unattached and ask the controller
25084 to deal. Fixes the second part of bug 681.
25085 - Make bridge authorities correctly expire old extrainfo documents
25089 Changes in version 0.2.0.26-rc - 2008-05-13
25090 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
25091 in Debian's OpenSSL packages. All users running any 0.2.0.x version
25092 should upgrade, whether they're running Debian or not.
25094 o Major security fixes:
25095 - Use new V3 directory authority keys on the tor26, gabelmoo, and
25096 moria1 V3 directory authorities. The old keys were generated with
25097 a vulnerable version of Debian's OpenSSL package, and must be
25098 considered compromised. Other authorities' keys were not generated
25099 with an affected version of OpenSSL.
25102 - List authority signatures as "unrecognized" based on DirServer
25103 lines, not on cert cache. Bugfix on 0.2.0.x.
25106 - Add a new V3AuthUseLegacyKey option to make it easier for
25107 authorities to change their identity keys if they have to.
25110 Changes in version 0.2.0.25-rc - 2008-04-23
25111 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
25114 - Remember to initialize threading before initializing logging.
25115 Otherwise, many BSD-family implementations will crash hard on
25116 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
25119 - Authorities correctly free policies on bad servers on
25120 exit. Fixes bug 672. Bugfix on 0.2.0.x.
25123 Changes in version 0.2.0.24-rc - 2008-04-22
25124 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
25125 v3 directory authority, makes relays with dynamic IP addresses and no
25126 DirPort notice more quickly when their IP address changes, fixes a few
25127 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
25129 o New directory authorities:
25130 - Take lefkada out of the list of v3 directory authorities, since
25131 it has been down for months.
25132 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
25136 - Detect address changes more quickly on non-directory mirror
25137 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
25139 o Minor features (security):
25140 - Reject requests for reverse-dns lookup of names that are in
25141 a private address space. Patch from lodger.
25142 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
25145 o Minor bugfixes (crashes):
25146 - Avoid a rare assert that can trigger when Tor doesn't have much
25147 directory information yet and it tries to fetch a v2 hidden
25148 service descriptor. Fixes bug 651, reported by nwf.
25149 - Initialize log mutex before initializing dmalloc. Otherwise,
25150 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
25151 - Use recursive pthread mutexes in order to avoid deadlock when
25152 logging debug-level messages to a controller. Bug spotted by nwf,
25153 bugfix on 0.2.0.16-alpha.
25155 o Minor bugfixes (resource management):
25156 - Keep address policies from leaking memory: start their refcount
25157 at 1, not 2. Bugfix on 0.2.0.16-alpha.
25158 - Free authority certificates on exit, so they don't look like memory
25159 leaks. Bugfix on 0.2.0.19-alpha.
25160 - Free static hashtables for policy maps and for TLS connections on
25161 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
25162 - Avoid allocating extra space when computing consensuses on 64-bit
25163 platforms. Bug spotted by aakova.
25165 o Minor bugfixes (misc):
25166 - Do not read the configuration file when we've only been told to
25167 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
25168 based on patch from Sebastian Hahn.
25169 - Exit relays that are used as a client can now reach themselves
25170 using the .exit notation, rather than just launching an infinite
25171 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
25172 - When attempting to open a logfile fails, tell us why.
25173 - Fix a dumb bug that was preventing us from knowing that we should
25174 preemptively build circuits to handle expected directory requests.
25175 Fixes bug 660. Bugfix on 0.1.2.x.
25176 - Warn less verbosely about clock skew from netinfo cells from
25177 untrusted sources. Fixes bug 663.
25178 - Make controller stream events for DNS requests more consistent,
25179 by adding "new stream" events for DNS requests, and removing
25180 spurious "stream closed" events" for cached reverse resolves.
25181 Patch from mwenge. Fixes bug 646.
25182 - Correctly notify one-hop connections when a circuit build has
25183 failed. Possible fix for bug 669. Found by lodger.
25186 Changes in version 0.2.0.23-rc - 2008-03-24
25187 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
25188 makes bootstrapping faster if the first directory mirror you contact
25189 is down. The bundles also include the new Vidalia 0.1.2 release.
25192 - When a tunneled directory request is made to a directory server
25193 that's down, notice after 30 seconds rather than 120 seconds. Also,
25194 fail any begindir streams that are pending on it, so they can
25195 retry elsewhere. This was causing multi-minute delays on bootstrap.
25198 Changes in version 0.2.0.22-rc - 2008-03-18
25199 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
25200 enables encrypted directory connections by default for non-relays, fixes
25201 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
25202 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
25205 - Enable encrypted directory connections by default for non-relays,
25206 so censor tools that block Tor directory connections based on their
25207 plaintext patterns will no longer work. This means Tor works in
25208 certain censored countries by default again.
25211 - Make sure servers always request certificates from clients during
25212 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
25213 - Do not enter a CPU-eating loop when a connection is closed in
25214 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
25215 diagnosed by lodger; bugfix on 0.2.0.20-rc.
25216 - Fix assertion failure that could occur when a blocked circuit
25217 became unblocked, and it had pending client DNS requests. Bugfix
25218 on 0.2.0.1-alpha. Fixes bug 632.
25220 o Minor bugfixes (on 0.1.2.x):
25221 - Generate "STATUS_SERVER" events rather than misspelled
25222 "STATUS_SEVER" events. Caught by mwenge.
25223 - When counting the number of bytes written on a TLS connection,
25224 look at the BIO actually used for writing to the network, not
25225 at the BIO used (sometimes) to buffer data for the network.
25226 Looking at different BIOs could result in write counts on the
25227 order of ULONG_MAX. Fixes bug 614.
25228 - On Windows, correctly detect errors when listing the contents of
25229 a directory. Fix from lodger.
25231 o Minor bugfixes (on 0.2.0.x):
25232 - Downgrade "sslv3 alert handshake failure" message to INFO.
25233 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
25234 left BandwidthRate and BandwidthBurst at the default, we would be
25235 silently limited by those defaults. Now raise them to match the
25236 RelayBandwidth* values.
25237 - Fix the SVK version detection logic to work correctly on a branch.
25238 - Make --enable-openbsd-malloc work correctly on Linux with alpha
25239 CPUs. Fixes bug 625.
25240 - Logging functions now check that the passed severity is sane.
25241 - Use proper log levels in the testsuite call of
25242 get_interface_address6().
25243 - When using a nonstandard malloc, do not use the platform values for
25244 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
25245 - Make the openbsd malloc code use 8k pages on alpha CPUs and
25247 - Detect mismatched page sizes when using --enable-openbsd-malloc.
25248 - Avoid double-marked-for-close warning when certain kinds of invalid
25249 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
25250 for bug 617. Bugfix on 0.2.0.1-alpha.
25251 - Make sure that the "NULL-means-reject *:*" convention is followed by
25252 all the policy manipulation functions, avoiding some possible crash
25253 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
25254 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
25255 actually works, and doesn't warn about every single reverse lookup.
25256 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
25259 - Only log guard node status when guard node status has changed.
25260 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
25261 make "INFO" 75% less verbose.
25264 Changes in version 0.2.0.21-rc - 2008-03-02
25265 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
25266 makes Tor work well with Vidalia again, fixes a rare assert bug,
25267 and fixes a pair of more minor bugs. The bundles also include Vidalia
25268 0.1.0 and Torbutton 1.1.16.
25271 - The control port should declare that it requires password auth
25272 when HashedControlSessionPassword is set too. Patch from Matt Edman;
25273 bugfix on 0.2.0.20-rc. Fixes bug 615.
25274 - Downgrade assert in connection_buckets_decrement() to a log message.
25275 This may help us solve bug 614, and in any case will make its
25276 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
25277 - We were sometimes miscounting the number of bytes read from the
25278 network, causing our rate limiting to not be followed exactly.
25279 Bugfix on 0.2.0.16-alpha. Reported by lodger.
25282 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
25283 OpenSSL versions should have been working fine. Diagnosis and patch
25284 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
25285 Bugfix on 0.2.0.20-rc.
25288 Changes in version 0.2.0.20-rc - 2008-02-24
25289 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
25290 makes more progress towards normalizing Tor's TLS handshake, makes
25291 hidden services work better again, helps relays bootstrap if they don't
25292 know their IP address, adds optional support for linking in openbsd's
25293 allocator or tcmalloc, allows really fast relays to scale past 15000
25294 sockets, and fixes a bunch of minor bugs reported by Veracode.
25297 - Enable the revised TLS handshake based on the one designed by
25298 Steven Murdoch in proposal 124, as revised in proposal 130. It
25299 includes version negotiation for OR connections as described in
25300 proposal 105. The new handshake is meant to be harder for censors
25301 to fingerprint, and it adds the ability to detect certain kinds of
25302 man-in-the-middle traffic analysis attacks. The version negotiation
25303 feature will allow us to improve Tor's link protocol more safely
25305 - Choose which bridge to use proportional to its advertised bandwidth,
25306 rather than uniformly at random. This should speed up Tor for
25307 bridge users. Also do this for people who set StrictEntryNodes.
25308 - When a TrackHostExits-chosen exit fails too many times in a row,
25309 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
25312 - Resolved problems with (re-)fetching hidden service descriptors.
25313 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
25314 and 0.2.0.19-alpha.
25315 - If we only ever used Tor for hidden service lookups or posts, we
25316 would stop building circuits and start refusing connections after
25317 24 hours, since we falsely believed that Tor was dormant. Reported
25318 by nwf; bugfix on 0.1.2.x.
25319 - Servers that don't know their own IP address should go to the
25320 authorities for their first directory fetch, even if their DirPort
25321 is off or if they don't know they're reachable yet. This will help
25322 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
25323 - When counting the number of open sockets, count not only the number
25324 of sockets we have received from the socket() call, but also
25325 the number we've gotten from accept() and socketpair(). This bug
25326 made us fail to count all sockets that we were using for incoming
25327 connections. Bugfix on 0.2.0.x.
25328 - Fix code used to find strings within buffers, when those strings
25329 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
25330 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
25331 - Add a new __HashedControlSessionPassword option for controllers
25332 to use for one-off session password hashes that shouldn't get
25333 saved to disk by SAVECONF --- Vidalia users were accumulating a
25334 pile of HashedControlPassword lines in their torrc files, one for
25335 each time they had restarted Tor and then clicked Save. Make Tor
25336 automatically convert "HashedControlPassword" to this new option but
25337 only when it's given on the command line. Partial fix for bug 586.
25339 o Minor features (performance):
25340 - Tune parameters for cell pool allocation to minimize amount of
25342 - Add OpenBSD malloc code from phk as an optional malloc
25343 replacement on Linux: some glibc libraries do very poorly
25344 with Tor's memory allocation patterns. Pass
25345 --enable-openbsd-malloc to get the replacement malloc code.
25346 - Add a --with-tcmalloc option to the configure script to link
25347 against tcmalloc (if present). Does not yet search for
25348 non-system include paths.
25349 - Stop imposing an arbitrary maximum on the number of file descriptors
25350 used for busy servers. Bug reported by Olaf Selke; patch from
25353 o Minor features (other):
25354 - When SafeLogging is disabled, log addresses along with all TLS
25356 - When building with --enable-gcc-warnings, check for whether Apple's
25357 warning "-Wshorten-64-to-32" is available.
25358 - Add a --passphrase-fd argument to the tor-gencert command for
25361 o Minor bugfixes (memory leaks and code problems):
25362 - We were leaking a file descriptor if Tor started with a zero-length
25363 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
25364 - Detect size overflow in zlib code. Reported by Justin Ferguson and
25366 - We were comparing the raw BridgePassword entry with a base64'ed
25367 version of it, when handling a "/tor/networkstatus-bridges"
25368 directory request. Now compare correctly. Noticed by Veracode.
25369 - Recover from bad tracked-since value in MTBF-history file.
25370 Should fix bug 537.
25371 - Alter the code that tries to recover from unhandled write
25372 errors, to not try to flush onto a socket that's given us
25373 unhandled errors. Bugfix on 0.1.2.x.
25374 - Make Unix controlsockets work correctly on OpenBSD. Patch from
25375 tup. Bugfix on 0.2.0.3-alpha.
25377 o Minor bugfixes (other):
25378 - If we have an extra-info document for our server, always make
25379 it available on the control port, even if we haven't gotten
25380 a copy of it from an authority yet. Patch from mwenge.
25381 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
25382 - Directory mirrors no longer include a guess at the client's IP
25383 address if the connection appears to be coming from the same /24
25384 network; it was producing too many wrong guesses.
25385 - Make the new hidden service code respect the SafeLogging setting.
25386 Bugfix on 0.2.0.x. Patch from Karsten.
25387 - When starting as an authority, do not overwrite all certificates
25388 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
25389 - If we're trying to flush the last bytes on a connection (for
25390 example, when answering a directory request), reset the
25391 time-to-give-up timeout every time we manage to write something
25392 on the socket. Bugfix on 0.1.2.x.
25393 - Change the behavior of "getinfo status/good-server-descriptor"
25394 so it doesn't return failure when any authority disappears.
25395 - Even though the man page said that "TrackHostExits ." should
25396 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
25397 - Report TLS "zero return" case as a "clean close" and "IO error"
25398 as a "close". Stop calling closes "unexpected closes": existing
25399 Tors don't use SSL_close(), so having a connection close without
25400 the TLS shutdown handshake is hardly unexpected.
25401 - Send NAMESERVER_STATUS messages for a single failed nameserver
25404 o Code simplifications and refactoring:
25405 - Remove the tor_strpartition function: its logic was confused,
25406 and it was only used for one thing that could be implemented far
25410 Changes in version 0.2.0.19-alpha - 2008-02-09
25411 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
25412 handshake, makes path selection for relays more secure and IP address
25413 guessing more robust, and generally fixes a lot of bugs in preparation
25414 for calling the 0.2.0 branch stable.
25417 - Do not include recognizeable strings in the commonname part of
25418 Tor's x509 certificates.
25421 - If we're a relay, avoid picking ourselves as an introduction point,
25422 a rendezvous point, or as the final hop for internal circuits. Bug
25423 reported by taranis and lodger. Bugfix on 0.1.2.x.
25424 - Patch from "Andrew S. Lists" to catch when we contact a directory
25425 mirror at IP address X and he says we look like we're coming from
25426 IP address X. Bugfix on 0.1.2.x.
25428 o Minor features (security):
25429 - Be more paranoid about overwriting sensitive memory on free(),
25430 as a defensive programming tactic to ensure forward secrecy.
25432 o Minor features (directory authority):
25433 - Actually validate the options passed to AuthDirReject,
25434 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
25435 - Reject router descriptors with out-of-range bandwidthcapacity or
25436 bandwidthburst values.
25438 o Minor features (controller):
25439 - Reject controller commands over 1MB in length. This keeps rogue
25440 processes from running us out of memory.
25442 o Minor features (misc):
25443 - Give more descriptive well-formedness errors for out-of-range
25444 hidden service descriptor/protocol versions.
25445 - Make memory debugging information describe more about history
25446 of cell allocation, so we can help reduce our memory use.
25448 o Deprecated features (controller):
25449 - The status/version/num-versioning and status/version/num-concurring
25450 GETINFO options are no longer useful in the v3 directory protocol:
25451 treat them as deprecated, and warn when they're used.
25454 - When our consensus networkstatus has been expired for a while, stop
25455 being willing to build circuits using it. Fixes bug 401. Bugfix
25457 - Directory caches now fetch certificates from all authorities
25458 listed in a networkstatus consensus, even when they do not
25459 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
25460 - When connecting to a bridge without specifying its key, insert
25461 the connection into the identity-to-connection map as soon as
25462 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
25463 - Detect versions of OS X where malloc_good_size() is present in the
25464 library but never actually declared. Resolves bug 587. Bugfix
25466 - Stop incorrectly truncating zlib responses to directory authority
25467 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
25468 - Stop recommending that every server operator send mail to tor-ops.
25469 Resolves bug 597. Bugfix on 0.1.2.x.
25470 - Don't trigger an assert if we start a directory authority with a
25471 private IP address (like 127.0.0.1).
25472 - Avoid possible failures when generating a directory with routers
25473 with over-long versions strings, or too many flags set. Bugfix
25475 - If an attempt to launch a DNS resolve request over the control
25476 port fails because we have overrun the limit on the number of
25477 connections, tell the controller that the request has failed.
25478 - Avoid using too little bandwidth when our clock skips a few
25479 seconds. Bugfix on 0.1.2.x.
25480 - Fix shell error when warning about missing packages in configure
25481 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
25482 - Do not become confused when receiving a spurious VERSIONS-like
25483 cell from a confused v1 client. Bugfix on 0.2.0.x.
25484 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
25485 introduction points for a hidden service have failed. Patch from
25486 Karsten Loesing. Bugfix on 0.2.0.x.
25488 o Code simplifications and refactoring:
25489 - Remove some needless generality from cpuworker code, for improved
25491 - Stop overloading the circuit_t.onionskin field for both "onionskin
25492 from a CREATE cell that we are waiting for a cpuworker to be
25493 assigned" and "onionskin from an EXTEND cell that we are going to
25494 send to an OR as soon as we are connected". Might help with bug 600.
25495 - Add an in-place version of aes_crypt() so that we can avoid doing a
25496 needless memcpy() call on each cell payload.
25499 Changes in version 0.2.0.18-alpha - 2008-01-25
25500 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
25501 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
25502 that can warn or reject connections to ports generally associated with
25503 vulnerable-plaintext protocols.
25505 o New directory authorities:
25506 - Set up dannenberg (run by CCC) as the sixth v3 directory
25510 - Fix a major memory leak when attempting to use the v2 TLS
25511 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
25512 - We accidentally enabled the under-development v2 TLS handshake
25513 code, which was causing log entries like "TLS error while
25514 renegotiating handshake". Disable it again. Resolves bug 590.
25515 - We were computing the wrong Content-Length: header for directory
25516 responses that need to be compressed on the fly, causing clients
25517 asking for those items to always fail. Bugfix on 0.2.0.x; partially
25521 - Avoid going directly to the directory authorities even if you're a
25522 relay, if you haven't found yourself reachable yet or if you've
25523 decided not to advertise your dirport yet. Addresses bug 556.
25524 - If we've gone 12 hours since our last bandwidth check, and we
25525 estimate we have less than 50KB bandwidth capacity but we could
25526 handle more, do another bandwidth test.
25527 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
25528 Tor can warn and/or refuse connections to ports commonly used with
25529 vulnerable-plaintext protocols. Currently we warn on ports 23,
25530 109, 110, and 143, but we don't reject any.
25533 - When we setconf ClientOnly to 1, close any current OR and Dir
25534 listeners. Reported by mwenge.
25535 - When we get a consensus that's been signed by more people than
25536 we expect, don't log about it; it's not a big deal. Reported
25540 - Don't answer "/tor/networkstatus-bridges" directory requests if
25541 the request isn't encrypted.
25542 - Make "ClientOnly 1" config option disable directory ports too.
25543 - Patches from Karsten Loesing to make v2 hidden services more
25544 robust: work even when there aren't enough HSDir relays available;
25545 retry when a v2 rend desc fetch fails; but don't retry if we
25546 already have a usable v0 rend desc.
25549 Changes in version 0.2.0.17-alpha - 2008-01-17
25550 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
25553 - Make the tor-gencert man page get included correctly in the tarball.
25556 Changes in version 0.2.0.16-alpha - 2008-01-17
25557 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
25558 Loesing, and generally cleans up a lot of features and minor bugs.
25560 o New directory authorities:
25561 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
25564 o Major performance improvements:
25565 - Switch our old ring buffer implementation for one more like that
25566 used by free Unix kernels. The wasted space in a buffer with 1mb
25567 of data will now be more like 8k than 1mb. The new implementation
25568 also avoids realloc();realloc(); patterns that can contribute to
25569 memory fragmentation.
25572 - Configuration files now accept C-style strings as values. This
25573 helps encode characters not allowed in the current configuration
25574 file format, such as newline or #. Addresses bug 557.
25575 - Although we fixed bug 539 (where servers would send HTTP status 503
25576 responses _and_ send a body too), there are still servers out
25577 there that haven't upgraded. Therefore, make clients parse such
25578 bodies when they receive them.
25579 - When we're not serving v2 directory information, there is no reason
25580 to actually keep any around. Remove the obsolete files and directory
25581 on startup if they are very old and we aren't going to serve them.
25583 o Minor performance improvements:
25584 - Reference-count and share copies of address policy entries; only 5%
25585 of them were actually distinct.
25586 - Never walk through the list of logs if we know that no log is
25587 interested in a given message.
25590 - When an authority has not signed a consensus, do not try to
25591 download a nonexistent "certificate with key 00000000". Bugfix
25592 on 0.2.0.x. Fixes bug 569.
25593 - Fix a rare assert error when we're closing one of our threads:
25594 use a mutex to protect the list of logs, so we never write to the
25595 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
25596 bug 575, which is kind of the revenge of bug 222.
25597 - Patch from Karsten Loesing to complain less at both the client
25598 and the relay when a relay used to have the HSDir flag but doesn't
25599 anymore, and we try to upload a hidden service descriptor.
25600 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
25602 - Do not try to download missing certificates until we have tried
25603 to check our fallback consensus. Fixes bug 583.
25604 - Make bridges round reported GeoIP stats info up to the nearest
25605 estimate, not down. Now we can distinguish between "0 people from
25606 this country" and "1 person from this country".
25607 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
25608 - Avoid possible segfault if key generation fails in
25609 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
25610 - Avoid segfault in the case where a badly behaved v2 versioning
25611 directory sends a signed networkstatus with missing client-versions.
25613 - Avoid segfaults on certain complex invocations of
25614 router_get_by_hexdigest(). Bugfix on 0.1.2.
25615 - Correct bad index on array access in parse_http_time(). Bugfix
25617 - Fix possible bug in vote generation when server versions are present
25618 but client versions are not.
25619 - Fix rare bug on REDIRECTSTREAM control command when called with no
25620 port set: it could erroneously report an error when none had
25622 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
25623 compressing large objects and find ourselves with more than 4k
25624 left over. Bugfix on 0.2.0.
25625 - Fix a small memory leak when setting up a hidden service.
25626 - Fix a few memory leaks that could in theory happen under bizarre
25628 - Fix an assert if we post a general-purpose descriptor via the
25629 control port but that descriptor isn't mentioned in our current
25630 network consensus. Bug reported by Jon McLachlan; bugfix on
25633 o Minor features (controller):
25634 - Get NS events working again. Patch from tup.
25635 - The GETCONF command now escapes and quotes configuration values
25636 that don't otherwise fit into the torrc file.
25637 - The SETCONF command now handles quoted values correctly.
25639 o Minor features (directory authorities):
25640 - New configuration options to override default maximum number of
25641 servers allowed on a single IP address. This is important for
25642 running a test network on a single host.
25643 - Actually implement the -s option to tor-gencert.
25644 - Add a manual page for tor-gencert.
25646 o Minor features (bridges):
25647 - Bridge authorities no longer serve bridge descriptors over
25648 unencrypted connections.
25650 o Minor features (other):
25651 - Add hidden services and DNSPorts to the list of things that make
25652 Tor accept that it has running ports. Change starting Tor with no
25653 ports from a fatal error to a warning; we might change it back if
25654 this turns out to confuse anybody. Fixes bug 579.
25657 Changes in version 0.1.2.19 - 2008-01-17
25658 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
25659 exit policy a little bit more conservative so it's safer to run an
25660 exit relay on a home system, and fixes a variety of smaller issues.
25663 - Exit policies now reject connections that are addressed to a
25664 relay's public (external) IP address too, unless
25665 ExitPolicyRejectPrivate is turned off. We do this because too
25666 many relays are running nearby to services that trust them based
25667 on network address.
25670 - When the clock jumps forward a lot, do not allow the bandwidth
25671 buckets to become negative. Fixes bug 544.
25672 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
25673 on every successful resolve. Reported by Mike Perry.
25674 - Purge old entries from the "rephist" database and the hidden
25675 service descriptor database even when DirPort is zero.
25676 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
25677 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
25678 crashing or mis-answering these requests.
25679 - When we decide to send a 503 response to a request for servers, do
25680 not then also send the server descriptors: this defeats the whole
25681 purpose. Fixes bug 539.
25684 - Changing the ExitPolicyRejectPrivate setting should cause us to
25685 rebuild our server descriptor.
25686 - Fix handling of hex nicknames when answering controller requests for
25687 networkstatus by name, or when deciding whether to warn about
25688 unknown routers in a config option. (Patch from mwenge.)
25689 - Fix a couple of hard-to-trigger autoconf problems that could result
25690 in really weird results on platforms whose sys/types.h files define
25691 nonstandard integer types.
25692 - Don't try to create the datadir when running --verify-config or
25693 --hash-password. Resolves bug 540.
25694 - If we were having problems getting a particular descriptor from the
25695 directory caches, and then we learned about a new descriptor for
25696 that router, we weren't resetting our failure count. Reported
25698 - Although we fixed bug 539 (where servers would send HTTP status 503
25699 responses _and_ send a body too), there are still servers out there
25700 that haven't upgraded. Therefore, make clients parse such bodies
25701 when they receive them.
25702 - Run correctly on systems where rlim_t is larger than unsigned long.
25703 This includes some 64-bit systems.
25704 - Run correctly on platforms (like some versions of OS X 10.5) where
25705 the real limit for number of open files is OPEN_FILES, not rlim_max
25706 from getrlimit(RLIMIT_NOFILES).
25707 - Avoid a spurious free on base64 failure.
25708 - Avoid segfaults on certain complex invocations of
25709 router_get_by_hexdigest().
25710 - Fix rare bug on REDIRECTSTREAM control command when called with no
25711 port set: it could erroneously report an error when none had
25715 Changes in version 0.2.0.15-alpha - 2007-12-25
25716 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
25717 features added in 0.2.0.13-alpha.
25720 - Fix several remotely triggerable asserts based on DirPort requests
25721 for a v2 or v3 networkstatus object before we were prepared. This
25722 was particularly bad for 0.2.0.13 and later bridge relays, who
25723 would never have a v2 networkstatus and would thus always crash
25724 when used. Bugfixes on 0.2.0.x.
25725 - Estimate the v3 networkstatus size more accurately, rather than
25726 estimating it at zero bytes and giving it artificially high priority
25727 compared to other directory requests. Bugfix on 0.2.0.x.
25730 - Fix configure.in logic for cross-compilation.
25731 - When we load a bridge descriptor from the cache, and it was
25732 previously unreachable, mark it as retriable so we won't just
25733 ignore it. Also, try fetching a new copy immediately. Bugfixes
25735 - The bridge GeoIP stats were counting other relays, for example
25736 self-reachability and authority-reachability tests.
25739 - Support compilation to target iPhone; patch from cjacker huang.
25740 To build for iPhone, pass the --enable-iphone option to configure.
25743 Changes in version 0.2.0.14-alpha - 2007-12-23
25745 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
25746 without a datadirectory from a previous Tor install. Reported
25748 - Fix a crash when we fetch a descriptor that turns out to be
25749 unexpected (it used to be in our networkstatus when we started
25750 fetching it, but it isn't in our current networkstatus), and we
25751 aren't using bridges. Bugfix on 0.2.0.x.
25752 - Fix a crash when accessing hidden services: it would work the first
25753 time you use a given introduction point for your service, but
25754 on subsequent requests we'd be using garbage memory. Fixed by
25755 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
25756 - Fix a crash when we load a bridge descriptor from disk but we don't
25757 currently have a Bridge line for it in our torrc. Bugfix on
25761 - If bridge authorities set BridgePassword, they will serve a
25762 snapshot of known bridge routerstatuses from their DirPort to
25763 anybody who knows that password. Unset by default.
25766 - Make the unit tests build again.
25767 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
25768 - Make PublishServerDescriptor default to 1, so the default doesn't
25769 have to change as we invent new directory protocol versions.
25770 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
25771 be included unless sys/time.h is already included. Fixes
25772 bug 553. Bugfix on 0.2.0.x.
25773 - If we receive a general-purpose descriptor and then receive an
25774 identical bridge-purpose descriptor soon after, don't discard
25775 the next one as a duplicate.
25778 - If BridgeRelay is set to 1, then the default for
25779 PublishServerDescriptor is now "bridge" rather than "v2,v3".
25780 - If the user sets RelayBandwidthRate but doesn't set
25781 RelayBandwidthBurst, then make them equal rather than erroring out.
25784 Changes in version 0.2.0.13-alpha - 2007-12-21
25785 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
25786 Goodell, fixes many more bugs, and adds a lot of infrastructure for
25789 o New directory authorities:
25790 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
25794 - Only update guard status (usable / not usable) once we have
25795 enough directory information. This was causing us to always pick
25796 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
25797 causing us to discard all our guards on startup if we hadn't been
25798 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
25799 - Purge old entries from the "rephist" database and the hidden
25800 service descriptor databases even when DirPort is zero. Bugfix
25802 - We were ignoring our RelayBandwidthRate for the first 30 seconds
25803 after opening a circuit -- even a relayed circuit. Bugfix on
25805 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
25806 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
25807 crashing or mis-answering these types of requests.
25808 - Relays were publishing their server descriptor to v1 and v2
25809 directory authorities, but they didn't try publishing to v3-only
25810 authorities. Fix this; and also stop publishing to v1 authorities.
25812 - When we were reading router descriptors from cache, we were ignoring
25813 the annotations -- so for example we were reading in bridge-purpose
25814 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
25815 - When we decided to send a 503 response to a request for servers, we
25816 were then also sending the server descriptors: this defeats the
25817 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
25820 - Bridge relays now behave like clients with respect to time
25821 intervals for downloading new consensus documents -- otherwise they
25822 stand out. Bridge users now wait until the end of the interval,
25823 so their bridge relay will be sure to have a new consensus document.
25824 - Three new config options (AlternateDirAuthority,
25825 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
25826 user selectively replace the default directory authorities by type,
25827 rather than the all-or-nothing replacement that DirServer offers.
25828 - Tor can now be configured to read a GeoIP file from disk in one
25829 of two formats. This can be used by controllers to map IP addresses
25830 to countries. Eventually, it may support exit-by-country.
25831 - When possible, bridge relays remember which countries users
25832 are coming from, and report aggregate information in their
25833 extra-info documents, so that the bridge authorities can learn
25834 where Tor is blocked.
25835 - Bridge directory authorities now do reachability testing on the
25836 bridges they know. They provide router status summaries to the
25837 controller via "getinfo ns/purpose/bridge", and also dump summaries
25838 to a file periodically.
25839 - Stop fetching directory info so aggressively if your DirPort is
25840 on but your ORPort is off; stop fetching v2 dir info entirely.
25841 You can override these choices with the new FetchDirInfoEarly
25845 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
25846 consensus documents when there are too many relays at a single
25847 IP address. Now clear it in v2 network status documents too, and
25848 also clear it in routerinfo_t when the relay is no longer listed
25849 in the relevant networkstatus document.
25850 - Don't crash if we get an unexpected value for the
25851 PublishServerDescriptor config option. Reported by Matt Edman;
25852 bugfix on 0.2.0.9-alpha.
25853 - Our new v2 hidden service descriptor format allows descriptors
25854 that have no introduction points. But Tor crashed when we tried
25855 to build a descriptor with no intro points (and it would have
25856 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
25857 by Karsten Loesing.
25858 - Fix building with dmalloc 5.5.2 with glibc.
25859 - Reject uploaded descriptors and extrainfo documents if they're
25860 huge. Otherwise we'll cache them all over the network and it'll
25861 clog everything up. Reported by Aljosha Judmayer.
25862 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
25863 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
25864 - When the DANGEROUS_VERSION controller status event told us we're
25865 running an obsolete version, it used the string "OLD" to describe
25866 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
25867 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
25868 - If we can't expand our list of entry guards (e.g. because we're
25869 using bridges or we have StrictEntryNodes set), don't mark relays
25870 down when they fail a directory request. Otherwise we're too quick
25871 to mark all our entry points down. Bugfix on 0.1.2.x.
25872 - Fix handling of hex nicknames when answering controller requests for
25873 networkstatus by name, or when deciding whether to warn about unknown
25874 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
25875 - Fix a couple of hard-to-trigger autoconf problems that could result
25876 in really weird results on platforms whose sys/types.h files define
25877 nonstandard integer types. Bugfix on 0.1.2.x.
25878 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
25879 - Don't crash on name lookup when we have no current consensus. Fixes
25880 bug 538; bugfix on 0.2.0.x.
25881 - Only Tors that want to mirror the v2 directory info should
25882 create the "cached-status" directory in their datadir. (All Tors
25883 used to create it.) Bugfix on 0.2.0.9-alpha.
25884 - Directory authorities should only automatically download Extra Info
25885 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
25888 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
25889 consumers. (We already do this on HUP.)
25890 - Authorities and caches fetch the v2 networkstatus documents
25891 less often, now that v3 is encouraged.
25892 - Add a new config option BridgeRelay that specifies you want to
25893 be a bridge relay. Right now the only difference is that it makes
25894 you answer begin_dir requests, and it makes you cache dir info,
25895 even if your DirPort isn't on.
25896 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
25897 ask about source, timestamp of arrival, purpose, etc. We need
25898 something like this to help Vidalia not do GeoIP lookups on bridge
25900 - Allow multiple HashedControlPassword config lines, to support
25901 multiple controller passwords.
25902 - Authorities now decide whether they're authoritative for a given
25903 router based on the router's purpose.
25904 - New config options AuthDirBadDir and AuthDirListBadDirs for
25905 authorities to mark certain relays as "bad directories" in the
25906 networkstatus documents. Also supports the "!baddir" directive in
25907 the approved-routers file.
25910 Changes in version 0.2.0.12-alpha - 2007-11-16
25911 This twelfth development snapshot fixes some more build problems as
25912 well as a few minor bugs.
25915 - Make it build on OpenBSD again. Patch from tup.
25916 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
25917 package-building for Red Hat, OS X, etc.
25919 o Minor bugfixes (on 0.1.2.x):
25920 - Changing the ExitPolicyRejectPrivate setting should cause us to
25921 rebuild our server descriptor.
25923 o Minor bugfixes (on 0.2.0.x):
25924 - When we're lacking a consensus, don't try to perform rendezvous
25925 operations. Reported by Karsten Loesing.
25926 - Fix a small memory leak whenever we decide against using a
25927 newly picked entry guard. Reported by Mike Perry.
25928 - When authorities detected more than two relays running on the same
25929 IP address, they were clearing all the status flags but forgetting
25930 to clear the "hsdir" flag. So clients were being told that a
25931 given relay was the right choice for a v2 hsdir lookup, yet they
25932 never had its descriptor because it was marked as 'not running'
25934 - If we're trying to fetch a bridge descriptor and there's no way
25935 the bridge authority could help us (for example, we don't know
25936 a digest, or there is no bridge authority), don't be so eager to
25937 fall back to asking the bridge authority.
25938 - If we're using bridges or have strictentrynodes set, and our
25939 chosen exit is in the same family as all our bridges/entry guards,
25940 then be flexible about families.
25943 - When we negotiate a v2 link-layer connection (not yet implemented),
25944 accept RELAY_EARLY cells and turn them into RELAY cells if we've
25945 negotiated a v1 connection for their next step. Initial code for
25949 Changes in version 0.2.0.11-alpha - 2007-11-12
25950 This eleventh development snapshot fixes some build problems with
25951 the previous snapshot. It also includes a more secure-by-default exit
25952 policy for relays, fixes an enormous memory leak for exit relays, and
25953 fixes another bug where servers were falling out of the directory list.
25956 - Exit policies now reject connections that are addressed to a
25957 relay's public (external) IP address too, unless
25958 ExitPolicyRejectPrivate is turned off. We do this because too
25959 many relays are running nearby to services that trust them based
25960 on network address. Bugfix on 0.1.2.x.
25963 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
25964 on every successful resolve. Reported by Mike Perry; bugfix
25966 - On authorities, never downgrade to old router descriptors simply
25967 because they're listed in the consensus. This created a catch-22
25968 where we wouldn't list a new descriptor because there was an
25969 old one in the consensus, and we couldn't get the new one in the
25970 consensus because we wouldn't list it. Possible fix for bug 548.
25971 Also, this might cause bug 543 to appear on authorities; if so,
25972 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
25974 o Packaging fixes on 0.2.0.10-alpha:
25975 - We were including instructions about what to do with the
25976 src/config/fallback-consensus file, but we weren't actually
25977 including it in the tarball. Disable all of that for now.
25980 - Allow people to say PreferTunnelledDirConns rather than
25981 PreferTunneledDirConns, for those alternate-spellers out there.
25984 - Don't reevaluate all the information from our consensus document
25985 just because we've downloaded a v2 networkstatus that we intend
25986 to cache. Fixes bug 545; bugfix on 0.2.0.x.
25989 Changes in version 0.2.0.10-alpha - 2007-11-10
25990 This tenth development snapshot adds a third v3 directory authority
25991 run by Mike Perry, adds most of Karsten Loesing's new hidden service
25992 descriptor format, fixes a bad crash bug and new bridge bugs introduced
25993 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
25994 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
25995 addresses many more minor issues.
25997 o New directory authorities:
25998 - Set up ides (run by Mike Perry) as the third v3 directory authority.
26001 - Allow tunnelled directory connections to ask for an encrypted
26002 "begin_dir" connection or an anonymized "uses a full Tor circuit"
26003 connection independently. Now we can make anonymized begin_dir
26004 connections for (e.g.) more secure hidden service posting and
26006 - More progress on proposal 114: code from Karsten Loesing to
26007 implement new hidden service descriptor format.
26008 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
26009 accommodate the growing number of servers that use the default
26010 and are reaching it.
26011 - Directory authorities use a new formula for selecting which nodes
26012 to advertise as Guards: they must be in the top 7/8 in terms of
26013 how long we have known about them, and above the median of those
26014 nodes in terms of weighted fractional uptime.
26015 - Make "not enough dir info yet" warnings describe *why* Tor feels
26016 it doesn't have enough directory info yet.
26019 - Stop servers from crashing if they set a Family option (or
26020 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
26022 - Make bridge users work again -- the move to v3 directories in
26023 0.2.0.9-alpha had introduced a number of bugs that made bridges
26024 no longer work for clients.
26025 - When the clock jumps forward a lot, do not allow the bandwidth
26026 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
26028 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
26029 - When the consensus lists a router descriptor that we previously were
26030 mirroring, but that we considered non-canonical, reload the
26031 descriptor as canonical. This fixes bug 543 where Tor servers
26032 would start complaining after a few days that they don't have
26033 enough directory information to build a circuit.
26034 - Consider replacing the current consensus when certificates arrive
26035 that make the pending consensus valid. Previously, we were only
26036 considering replacement when the new certs _didn't_ help.
26037 - Fix an assert error on startup if we didn't already have the
26038 consensus and certs cached in our datadirectory: we were caching
26039 the consensus in consensus_waiting_for_certs but then free'ing it
26041 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
26042 Request) if we need more v3 certs but we've already got pending
26043 requests for all of them.
26044 - Correctly back off from failing certificate downloads. Fixes
26046 - Authorities don't vote on the Running flag if they have been running
26047 for less than 30 minutes themselves. Fixes bug 547, where a newly
26048 started authority would vote that everyone was down.
26050 o New requirements:
26051 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
26052 it, it had no AES, and it hasn't seen any security patches since
26056 - Clients now hold circuitless TLS connections open for 1.5 times
26057 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
26058 rebuild a new circuit over them within that timeframe. Previously,
26059 they held them open only for KeepalivePeriod (5 minutes).
26060 - Use "If-Modified-Since" to avoid retrieving consensus
26061 networkstatuses that we already have.
26062 - When we have no consensus, check FallbackNetworkstatusFile (defaults
26063 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
26064 we start knowing some directory caches.
26065 - When we receive a consensus from the future, warn about skew.
26066 - Improve skew reporting: try to give the user a better log message
26067 about how skewed they are, and how much this matters.
26068 - When we have a certificate for an authority, believe that
26069 certificate's claims about the authority's IP address.
26070 - New --quiet command-line option to suppress the default console log.
26071 Good in combination with --hash-password.
26072 - Authorities send back an X-Descriptor-Not-New header in response to
26073 an accepted-but-discarded descriptor upload. Partially implements
26075 - Make the log message for "tls error. breaking." more useful.
26076 - Better log messages about certificate downloads, to attempt to
26077 track down the second incarnation of bug 546.
26079 o Minor features (bridges):
26080 - If bridge users set UpdateBridgesFromAuthority, but the digest
26081 they ask for is a 404 from the bridge authority, they now fall
26082 back to trying the bridge directly.
26083 - Bridges now use begin_dir to publish their server descriptor to
26084 the bridge authority, even when they haven't set TunnelDirConns.
26086 o Minor features (controller):
26087 - When reporting clock skew, and we know that the clock is _at least
26088 as skewed_ as some value, but we don't know the actual value,
26089 report the value as a "minimum skew."
26092 - Update linux-tor-prio.sh script to allow QoS based on the uid of
26093 the Tor process. Patch from Marco Bonetti with tweaks from Mike
26097 - Refuse to start if both ORPort and UseBridges are set. Bugfix
26098 on 0.2.0.x, suggested by Matt Edman.
26099 - Don't stop fetching descriptors when FetchUselessDescriptors is
26100 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
26101 reported by tup and ioerror.
26102 - Better log message on vote from unknown authority.
26103 - Don't log "Launching 0 request for 0 router" message.
26105 o Minor bugfixes (memory leaks):
26106 - Stop leaking memory every time we parse a v3 certificate. Bugfix
26108 - Stop leaking memory every time we load a v3 certificate. Bugfix
26109 on 0.2.0.1-alpha. Fixes bug 536.
26110 - Stop leaking a cached networkstatus on exit. Bugfix on
26112 - Stop leaking voter information every time we free a consensus.
26113 Bugfix on 0.2.0.3-alpha.
26114 - Stop leaking signed data every time we check a voter signature.
26115 Bugfix on 0.2.0.3-alpha.
26116 - Stop leaking a signature every time we fail to parse a consensus or
26117 a vote. Bugfix on 0.2.0.3-alpha.
26118 - Stop leaking v2_download_status_map on shutdown. Bugfix on
26120 - Stop leaking conn->nickname every time we make a connection to a
26121 Tor relay without knowing its expected identity digest (e.g. when
26122 using bridges). Bugfix on 0.2.0.3-alpha.
26124 - Minor bugfixes (portability):
26125 - Run correctly on platforms where rlim_t is larger than unsigned
26126 long, and/or where the real limit for number of open files is
26127 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
26128 particular, these may be needed for OS X 10.5.
26131 Changes in version 0.1.2.18 - 2007-10-28
26132 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
26133 hidden service introduction that were causing huge delays, and a big
26134 bug that was causing some servers to disappear from the network status
26135 lists for a few hours each day.
26137 o Major bugfixes (crashes):
26138 - If a connection is shut down abruptly because of something that
26139 happened inside connection_flushed_some(), do not call
26140 connection_finished_flushing(). Should fix bug 451:
26141 "connection_stop_writing: Assertion conn->write_event failed"
26142 Bugfix on 0.1.2.7-alpha.
26143 - Fix possible segfaults in functions called from
26144 rend_process_relay_cell().
26146 o Major bugfixes (hidden services):
26147 - Hidden services were choosing introduction points uniquely by
26148 hexdigest, but when constructing the hidden service descriptor
26149 they merely wrote the (potentially ambiguous) nickname.
26150 - Clients now use the v2 intro format for hidden service
26151 connections: they specify their chosen rendezvous point by identity
26152 digest rather than by (potentially ambiguous) nickname. These
26153 changes could speed up hidden service connections dramatically.
26155 o Major bugfixes (other):
26156 - Stop publishing a new server descriptor just because we get a
26157 HUP signal. This led (in a roundabout way) to some servers getting
26158 dropped from the networkstatus lists for a few hours each day.
26159 - When looking for a circuit to cannibalize, consider family as well
26160 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
26161 circuit cannibalization).
26162 - When a router wasn't listed in a new networkstatus, we were leaving
26163 the flags for that router alone -- meaning it remained Named,
26164 Running, etc -- even though absence from the networkstatus means
26165 that it shouldn't be considered to exist at all anymore. Now we
26166 clear all the flags for routers that fall out of the networkstatus
26167 consensus. Fixes bug 529.
26170 - Don't try to access (or alter) the state file when running
26171 --list-fingerprint or --verify-config or --hash-password. Resolves
26173 - When generating information telling us how to extend to a given
26174 router, do not try to include the nickname if it is
26175 absent. Resolves bug 467.
26176 - Fix a user-triggerable segfault in expand_filename(). (There isn't
26177 a way to trigger this remotely.)
26178 - When sending a status event to the controller telling it that an
26179 OR address is reachable, set the port correctly. (Previously we
26180 were reporting the dir port.)
26181 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
26182 command. Bugfix on 0.1.2.17.
26183 - When loading bandwidth history, do not believe any information in
26184 the future. Fixes bug 434.
26185 - When loading entry guard information, do not believe any information
26187 - When we have our clock set far in the future and generate an
26188 onion key, then re-set our clock to be correct, we should not stop
26189 the onion key from getting rotated.
26190 - On some platforms, accept() can return a broken address. Detect
26191 this more quietly, and deal accordingly. Fixes bug 483.
26192 - It's not actually an error to find a non-pending entry in the DNS
26193 cache when canceling a pending resolve. Don't log unless stuff
26194 is fishy. Resolves bug 463.
26195 - Don't reset trusted dir server list when we set a configuration
26196 option. Patch from Robert Hogan.
26197 - Don't try to create the datadir when running --verify-config or
26198 --hash-password. Resolves bug 540.
26201 Changes in version 0.2.0.9-alpha - 2007-10-24
26202 This ninth development snapshot switches clients to the new v3 directory
26203 system; allows servers to be listed in the network status even when they
26204 have the same nickname as a registered server; and fixes many other
26205 bugs including a big one that was causing some servers to disappear
26206 from the network status lists for a few hours each day.
26208 o Major features (directory system):
26209 - Clients now download v3 consensus networkstatus documents instead
26210 of v2 networkstatus documents. Clients and caches now base their
26211 opinions about routers on these consensus documents. Clients only
26212 download router descriptors listed in the consensus.
26213 - Authorities now list servers who have the same nickname as
26214 a different named server, but list them with a new flag,
26215 "Unnamed". Now we can list servers that happen to pick the same
26216 nickname as a server that registered two years ago and then
26217 disappeared. Partially implements proposal 122.
26218 - If the consensus lists a router as "Unnamed", the name is assigned
26219 to a different router: do not identify the router by that name.
26220 Partially implements proposal 122.
26221 - Authorities can now come to a consensus on which method to use to
26222 compute the consensus. This gives us forward compatibility.
26225 - Stop publishing a new server descriptor just because we HUP or
26226 when we find our DirPort to be reachable but won't actually publish
26227 it. New descriptors without any real changes are dropped by the
26228 authorities, and can screw up our "publish every 18 hours" schedule.
26230 - When a router wasn't listed in a new networkstatus, we were leaving
26231 the flags for that router alone -- meaning it remained Named,
26232 Running, etc -- even though absence from the networkstatus means
26233 that it shouldn't be considered to exist at all anymore. Now we
26234 clear all the flags for routers that fall out of the networkstatus
26235 consensus. Fixes bug 529; bugfix on 0.1.2.x.
26236 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
26237 extrainfo documents and then discard them immediately for not
26238 matching the latest router. Bugfix on 0.2.0.1-alpha.
26240 o Minor features (v3 directory protocol):
26241 - Allow tor-gencert to generate a new certificate without replacing
26243 - Allow certificates to include an address.
26244 - When we change our directory-cache settings, reschedule all voting
26245 and download operations.
26246 - Reattempt certificate downloads immediately on failure, as long as
26247 we haven't failed a threshold number of times yet.
26248 - Delay retrying consensus downloads while we're downloading
26249 certificates to verify the one we just got. Also, count getting a
26250 consensus that we already have (or one that isn't valid) as a failure,
26251 and count failing to get the certificates after 20 minutes as a
26253 - Build circuits and download descriptors even if our consensus is a
26254 little expired. (This feature will go away once authorities are
26257 o Minor features (router descriptor cache):
26258 - If we find a cached-routers file that's been sitting around for more
26259 than 28 days unmodified, then most likely it's a leftover from
26260 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
26262 - When we (as a cache) download a descriptor because it was listed
26263 in a consensus, remember when the consensus was supposed to expire,
26264 and don't expire the descriptor until then.
26266 o Minor features (performance):
26267 - Call routerlist_remove_old_routers() much less often. This should
26268 speed startup, especially on directory caches.
26269 - Don't try to launch new descriptor downloads quite so often when we
26270 already have enough directory information to build circuits.
26271 - Base64 decoding was actually showing up on our profile when parsing
26272 the initial descriptor file; switch to an in-process all-at-once
26273 implementation that's about 3.5x times faster than calling out to
26276 o Minor features (compilation):
26277 - Detect non-ASCII platforms (if any still exist) and refuse to
26278 build there: some of our code assumes that 'A' is 65 and so on.
26280 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
26281 - Make the "next period" votes into "current period" votes immediately
26282 after publishing the consensus; avoid a heisenbug that made them
26283 stick around indefinitely.
26284 - When we discard a vote as a duplicate, do not report this as
26286 - Treat missing v3 keys or certificates as an error when running as a
26287 v3 directory authority.
26288 - When we're configured to be a v3 authority, but we're only listed
26289 as a non-v3 authority in our DirServer line for ourself, correct
26291 - If an authority doesn't have a qualified hostname, just put
26292 its address in the vote. This fixes the problem where we referred to
26293 "moria on moria:9031."
26294 - Distinguish between detached signatures for the wrong period, and
26295 detached signatures for a divergent vote.
26296 - Fix a small memory leak when computing a consensus.
26297 - When there's no consensus, we were forming a vote every 30
26298 minutes, but writing the "valid-after" line in our vote based
26299 on our configured V3AuthVotingInterval: so unless the intervals
26300 matched up, we immediately rejected our own vote because it didn't
26301 start at the voting interval that caused us to construct a vote.
26303 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
26304 - Delete unverified-consensus when the real consensus is set.
26305 - Consider retrying a consensus networkstatus fetch immediately
26306 after one fails: don't wait 60 seconds to notice.
26307 - When fetching a consensus as a cache, wait until a newer consensus
26308 should exist before trying to replace the current one.
26309 - Use a more forgiving schedule for retrying failed consensus
26310 downloads than for other types.
26312 o Minor bugfixes (other directory issues):
26313 - Correct the implementation of "download votes by digest." Bugfix on
26315 - Authorities no longer send back "400 you're unreachable please fix
26316 it" errors to Tor servers that aren't online all the time. We're
26317 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
26319 o Minor bugfixes (controller):
26320 - Don't reset trusted dir server list when we set a configuration
26321 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
26322 - Respond to INT and TERM SIGNAL commands before we execute the
26323 signal, in case the signal shuts us down. We had a patch in
26324 0.1.2.1-alpha that tried to do this by queueing the response on
26325 the connection's buffer before shutting down, but that really
26326 isn't the same thing at all. Bug located by Matt Edman.
26328 o Minor bugfixes (misc):
26329 - Correctly check for bad options to the "PublishServerDescriptor"
26330 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
26331 - Stop leaking memory on failing case of base32_decode, and make
26332 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
26333 - Don't try to download extrainfo documents when we're trying to
26334 fetch enough directory info to build a circuit: having enough
26335 info should get priority. Bugfix on 0.2.0.x.
26336 - Don't complain that "your server has not managed to confirm that its
26337 ports are reachable" if we haven't been able to build any circuits
26338 yet. Bug found by spending four hours without a v3 consensus. Bugfix
26340 - Detect the reason for failing to mmap a descriptor file we just
26341 wrote, and give a more useful log message. Fixes bug 533. Bugfix
26344 o Code simplifications and refactoring:
26345 - Remove support for the old bw_accounting file: we've been storing
26346 bandwidth accounting information in the state file since
26347 0.1.2.5-alpha. This may result in bandwidth accounting errors
26348 if you try to upgrade from 0.1.1.x or earlier, or if you try to
26349 downgrade to 0.1.1.x or earlier.
26350 - New convenience code to locate a file within the DataDirectory.
26351 - Move non-authority functionality out of dirvote.c.
26352 - Refactor the arguments for router_pick_{directory_|trusteddir}server
26353 so that they all take the same named flags.
26356 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
26357 Unix users an easy way to script their Tor process (e.g. by
26358 adjusting bandwidth based on the time of the day).
26361 Changes in version 0.2.0.8-alpha - 2007-10-12
26362 This eighth development snapshot fixes a crash bug that's been bothering
26363 us since February 2007, lets bridge authorities store a list of bridge
26364 descriptors they've seen, gets v3 directory voting closer to working,
26365 starts caching v3 directory consensus documents on directory mirrors,
26366 and fixes a variety of smaller issues including some minor memory leaks.
26368 o Major features (router descriptor cache):
26369 - Store routers in a file called cached-descriptors instead of in
26370 cached-routers. Initialize cached-descriptors from cached-routers
26371 if the old format is around. The new format allows us to store
26372 annotations along with descriptors.
26373 - Use annotations to record the time we received each descriptor, its
26374 source, and its purpose.
26375 - Disable the SETROUTERPURPOSE controller command: it is now
26377 - Controllers should now specify cache=no or cache=yes when using
26378 the +POSTDESCRIPTOR command.
26379 - Bridge authorities now write bridge descriptors to disk, meaning
26380 we can export them to other programs and begin distributing them
26383 o Major features (directory authorities):
26384 - When a v3 authority is missing votes or signatures, it now tries
26386 - Directory authorities track weighted fractional uptime as well as
26387 weighted mean-time-between failures. WFU is suitable for deciding
26388 whether a node is "usually up", while MTBF is suitable for deciding
26389 whether a node is "likely to stay up." We need both, because
26390 "usually up" is a good requirement for guards, while "likely to
26391 stay up" is a good requirement for long-lived connections.
26393 o Major features (v3 directory system):
26394 - Caches now download v3 network status documents as needed,
26395 and download the descriptors listed in them.
26396 - All hosts now attempt to download and keep fresh v3 authority
26397 certificates, and re-attempt after failures.
26398 - More internal-consistency checks for vote parsing.
26400 o Major bugfixes (crashes):
26401 - If a connection is shut down abruptly because of something that
26402 happened inside connection_flushed_some(), do not call
26403 connection_finished_flushing(). Should fix bug 451. Bugfix on
26406 o Major bugfixes (performance):
26407 - Fix really bad O(n^2) performance when parsing a long list of
26408 routers: Instead of searching the entire list for an "extra-info "
26409 string which usually wasn't there, once for every routerinfo
26410 we read, just scan lines forward until we find one we like.
26412 - When we add data to a write buffer in response to the data on that
26413 write buffer getting low because of a flush, do not consider the
26414 newly added data as a candidate for immediate flushing, but rather
26415 make it wait until the next round of writing. Otherwise, we flush
26416 and refill recursively, and a single greedy TLS connection can
26417 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
26419 o Minor features (v3 authority system):
26420 - Add more ways for tools to download the votes that lead to the
26422 - Send a 503 when low on bandwidth and a vote, consensus, or
26423 certificate is requested.
26424 - If-modified-since is now implemented properly for all kinds of
26425 certificate requests.
26427 o Minor bugfixes (network statuses):
26428 - Tweak the implementation of proposal 109 slightly: allow at most
26429 two Tor servers on the same IP address, except if it's the location
26430 of a directory authority, in which case allow five. Bugfix on
26433 o Minor bugfixes (controller):
26434 - When sending a status event to the controller telling it that an
26435 OR address is reachable, set the port correctly. (Previously we
26436 were reporting the dir port.) Bugfix on 0.1.2.x.
26438 o Minor bugfixes (v3 directory system):
26439 - Fix logic to look up a cert by its signing key digest. Bugfix on
26441 - Only change the reply to a vote to "OK" if it's not already
26442 set. This gets rid of annoying "400 OK" log messages, which may
26443 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
26444 - When we get a valid consensus, recompute the voting schedule.
26445 - Base the valid-after time of a vote on the consensus voting
26446 schedule, not on our preferred schedule.
26447 - Make the return values and messages from signature uploads and
26448 downloads more sensible.
26449 - Fix a memory leak when serving votes and consensus documents, and
26450 another when serving certificates.
26452 o Minor bugfixes (performance):
26453 - Use a slightly simpler string hashing algorithm (copying Python's
26454 instead of Java's) and optimize our digest hashing algorithm to take
26455 advantage of 64-bit platforms and to remove some possibly-costly
26457 - Fix a minor memory leak whenever we parse guards from our state
26458 file. Bugfix on 0.2.0.7-alpha.
26459 - Fix a minor memory leak whenever we write out a file. Bugfix on
26461 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
26462 command. Bugfix on 0.2.0.5-alpha.
26464 o Minor bugfixes (portability):
26465 - On some platforms, accept() can return a broken address. Detect
26466 this more quietly, and deal accordingly. Fixes bug 483.
26467 - Stop calling tor_strlower() on uninitialized memory in some cases.
26468 Bugfix in 0.2.0.7-alpha.
26470 o Minor bugfixes (usability):
26471 - Treat some 403 responses from directory servers as INFO rather than
26472 WARN-severity events.
26473 - It's not actually an error to find a non-pending entry in the DNS
26474 cache when canceling a pending resolve. Don't log unless stuff is
26475 fishy. Resolves bug 463.
26477 o Minor bugfixes (anonymity):
26478 - Never report that we've used more bandwidth than we're willing to
26479 relay: it leaks how much non-relay traffic we're using. Resolves
26481 - When looking for a circuit to cannibalize, consider family as well
26482 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
26483 circuit cannibalization).
26485 o Code simplifications and refactoring:
26486 - Make a bunch of functions static. Remove some dead code.
26487 - Pull out about a third of the really big routerlist.c; put it in a
26488 new module, networkstatus.c.
26489 - Merge the extra fields in local_routerstatus_t back into
26490 routerstatus_t: we used to need one routerstatus_t for each
26491 authority's opinion, plus a local_routerstatus_t for the locally
26492 computed consensus opinion. To save space, we put the locally
26493 modified fields into local_routerstatus_t, and only the common
26494 stuff into routerstatus_t. But once v3 directories are in use,
26495 clients and caches will no longer need to hold authority opinions;
26496 thus, the rationale for keeping the types separate is now gone.
26497 - Make the code used to reschedule and reattempt downloads more
26499 - Turn all 'Are we a directory server/mirror?' logic into a call to
26501 - Remove the code to generate the oldest (v1) directory format.
26502 The code has been disabled since 0.2.0.5-alpha.
26505 Changes in version 0.2.0.7-alpha - 2007-09-21
26506 This seventh development snapshot makes bridges work again, makes bridge
26507 authorities work for the first time, fixes two huge performance flaws
26508 in hidden services, and fixes a variety of minor issues.
26510 o New directory authorities:
26511 - Set up moria1 and tor26 as the first v3 directory authorities. See
26512 doc/spec/dir-spec.txt for details on the new directory design.
26514 o Major bugfixes (crashes):
26515 - Fix possible segfaults in functions called from
26516 rend_process_relay_cell(). Bugfix on 0.1.2.x.
26518 o Major bugfixes (bridges):
26519 - Fix a bug that made servers send a "404 Not found" in response to
26520 attempts to fetch their server descriptor. This caused Tor servers
26521 to take many minutes to establish reachability for their DirPort,
26522 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
26523 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
26524 users configure that and specify a bridge with an identity
26525 fingerprint, now they will lookup the bridge descriptor at the
26526 default bridge authority via a one-hop tunnel, but once circuits
26527 are established they will switch to a three-hop tunnel for later
26528 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
26530 o Major bugfixes (hidden services):
26531 - Hidden services were choosing introduction points uniquely by
26532 hexdigest, but when constructing the hidden service descriptor
26533 they merely wrote the (potentially ambiguous) nickname.
26534 - Clients now use the v2 intro format for hidden service
26535 connections: they specify their chosen rendezvous point by identity
26536 digest rather than by (potentially ambiguous) nickname. Both
26537 are bugfixes on 0.1.2.x, and they could speed up hidden service
26538 connections dramatically. Thanks to Karsten Loesing.
26540 o Minor features (security):
26541 - As a client, do not believe any server that tells us that an
26542 address maps to an internal address space.
26543 - Make it possible to enable HashedControlPassword and
26544 CookieAuthentication at the same time.
26546 o Minor features (guard nodes):
26547 - Tag every guard node in our state file with the version that
26548 we believe added it, or with our own version if we add it. This way,
26549 if a user temporarily runs an old version of Tor and then switches
26550 back to a new one, she doesn't automatically lose her guards.
26552 o Minor features (speed):
26553 - When implementing AES counter mode, update only the portions of the
26554 counter buffer that need to change, and don't keep separate
26555 network-order and host-order counters when they are the same (i.e.,
26556 on big-endian hosts.)
26558 o Minor features (controller):
26559 - Accept LF instead of CRLF on controller, since some software has a
26560 hard time generating real Internet newlines.
26561 - Add GETINFO values for the server status events
26562 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
26565 o Removed features:
26566 - Routers no longer include bandwidth-history lines in their
26567 descriptors; this information is already available in extra-info
26568 documents, and including it in router descriptors took up 60%
26569 (!) of compressed router descriptor downloads. Completes
26570 implementation of proposal 104.
26571 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
26572 and TorControl.py, as they use the old v0 controller protocol,
26573 and are obsoleted by TorFlow anyway.
26574 - Drop support for v1 rendezvous descriptors, since we never used
26575 them anyway, and the code has probably rotted by now. Based on
26576 patch from Karsten Loesing.
26577 - On OSX, stop warning the user that kqueue support in libevent is
26578 "experimental", since it seems to have worked fine for ages.
26581 - When generating information telling us how to extend to a given
26582 router, do not try to include the nickname if it is absent. Fixes
26583 bug 467. Bugfix on 0.2.0.3-alpha.
26584 - Fix a user-triggerable (but not remotely-triggerable) segfault
26585 in expand_filename(). Bugfix on 0.1.2.x.
26586 - Fix a memory leak when freeing incomplete requests from DNSPort.
26587 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
26588 - Don't try to access (or alter) the state file when running
26589 --list-fingerprint or --verify-config or --hash-password. (Resolves
26590 bug 499.) Bugfix on 0.1.2.x.
26591 - Servers used to decline to publish their DirPort if their
26592 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
26593 were below a threshold. Now they only look at BandwidthRate and
26594 RelayBandwidthRate. Bugfix on 0.1.2.x.
26595 - Remove an optimization in the AES counter-mode code that assumed
26596 that the counter never exceeded 2^68. When the counter can be set
26597 arbitrarily as an IV (as it is by Karsten's new hidden services
26598 code), this assumption no longer holds. Bugfix on 0.1.2.x.
26599 - Resume listing "AUTHORITY" flag for authorities in network status.
26600 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
26602 o Code simplifications and refactoring:
26603 - Revamp file-writing logic so we don't need to have the entire
26604 contents of a file in memory at once before we write to disk. Tor,
26606 - Turn "descriptor store" into a full-fledged type.
26607 - Move all NT services code into a separate source file.
26608 - Unify all code that computes medians, percentile elements, etc.
26609 - Get rid of a needless malloc when parsing address policies.
26612 Changes in version 0.1.2.17 - 2007-08-30
26613 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
26614 X bundles. Vidalia 0.0.14 makes authentication required for the
26615 ControlPort in the default configuration, which addresses important
26616 security risks. Everybody who uses Vidalia (or another controller)
26619 In addition, this Tor update fixes major load balancing problems with
26620 path selection, which should speed things up a lot once many people
26623 o Major bugfixes (security):
26624 - We removed support for the old (v0) control protocol. It has been
26625 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
26626 become more of a headache than it's worth.
26628 o Major bugfixes (load balancing):
26629 - When choosing nodes for non-guard positions, weight guards
26630 proportionally less, since they already have enough load. Patch
26632 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
26633 will allow fast Tor servers to get more attention.
26634 - When we're upgrading from an old Tor version, forget our current
26635 guards and pick new ones according to the new weightings. These
26636 three load balancing patches could raise effective network capacity
26637 by a factor of four. Thanks to Mike Perry for measurements.
26639 o Major bugfixes (stream expiration):
26640 - Expire not-yet-successful application streams in all cases if
26641 they've been around longer than SocksTimeout. Right now there are
26642 some cases where the stream will live forever, demanding a new
26643 circuit every 15 seconds. Fixes bug 454; reported by lodger.
26645 o Minor features (controller):
26646 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
26647 is valid before any authentication has been received. It tells
26648 a controller what kind of authentication is expected, and what
26649 protocol is spoken. Implements proposal 119.
26651 o Minor bugfixes (performance):
26652 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
26653 greatly speeding up loading cached-routers from disk on startup.
26654 - Disable sentinel-based debugging for buffer code: we squashed all
26655 the bugs that this was supposed to detect a long time ago, and now
26656 its only effect is to change our buffer sizes from nice powers of
26657 two (which platform mallocs tend to like) to values slightly over
26658 powers of two (which make some platform mallocs sad).
26660 o Minor bugfixes (misc):
26661 - If exit bandwidth ever exceeds one third of total bandwidth, then
26662 use the correct formula to weight exit nodes when choosing paths.
26663 Based on patch from Mike Perry.
26664 - Choose perfectly fairly among routers when choosing by bandwidth and
26665 weighting by fraction of bandwidth provided by exits. Previously, we
26666 would choose with only approximate fairness, and correct ourselves
26667 if we ran off the end of the list.
26668 - If we require CookieAuthentication but we fail to write the
26669 cookie file, we would warn but not exit, and end up in a state
26670 where no controller could authenticate. Now we exit.
26671 - If we require CookieAuthentication, stop generating a new cookie
26672 every time we change any piece of our config.
26673 - Refuse to start with certain directory authority keys, and
26674 encourage people using them to stop.
26675 - Terminate multi-line control events properly. Original patch
26677 - Fix a minor memory leak when we fail to find enough suitable
26678 servers to choose a circuit.
26679 - Stop leaking part of the descriptor when we run into a particularly
26680 unparseable piece of it.
26683 Changes in version 0.2.0.6-alpha - 2007-08-26
26684 This sixth development snapshot features a new Vidalia version in the
26685 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
26686 the ControlPort in the default configuration, which addresses important
26689 In addition, this snapshot fixes major load balancing problems
26690 with path selection, which should speed things up a lot once many
26691 people have upgraded. The directory authorities also use a new
26692 mean-time-between-failure approach to tracking which servers are stable,
26693 rather than just looking at the most recent uptime.
26695 o New directory authorities:
26696 - Set up Tonga as the default bridge directory authority.
26699 - Directory authorities now track servers by weighted
26700 mean-times-between-failures. When we have 4 or more days of data,
26701 use measured MTBF rather than declared uptime to decide whether
26702 to call a router Stable. Implements proposal 108.
26704 o Major bugfixes (load balancing):
26705 - When choosing nodes for non-guard positions, weight guards
26706 proportionally less, since they already have enough load. Patch
26708 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
26709 will allow fast Tor servers to get more attention.
26710 - When we're upgrading from an old Tor version, forget our current
26711 guards and pick new ones according to the new weightings. These
26712 three load balancing patches could raise effective network capacity
26713 by a factor of four. Thanks to Mike Perry for measurements.
26715 o Major bugfixes (descriptor parsing):
26716 - Handle unexpected whitespace better in malformed descriptors. Bug
26717 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
26720 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
26721 GETINFO for Torstat to use until it can switch to using extrainfos.
26722 - Optionally (if built with -DEXPORTMALLINFO) export the output
26723 of mallinfo via http, as tor/mallinfo.txt. Only accessible
26727 - Do not intermix bridge routers with controller-added
26728 routers. (Bugfix on 0.2.0.x)
26729 - Do not fail with an assert when accept() returns an unexpected
26730 address family. Addresses but does not wholly fix bug 483. (Bugfix
26732 - Let directory authorities startup even when they can't generate
26733 a descriptor immediately, e.g. because they don't know their
26735 - Stop putting the authentication cookie in a file called "0"
26736 in your working directory if you don't specify anything for the
26737 new CookieAuthFile option. Reported by Matt Edman.
26738 - Make it possible to read the PROTOCOLINFO response in a way that
26739 conforms to our control-spec. Reported by Matt Edman.
26740 - Fix a minor memory leak when we fail to find enough suitable
26741 servers to choose a circuit. Bugfix on 0.1.2.x.
26742 - Stop leaking part of the descriptor when we run into a particularly
26743 unparseable piece of it. Bugfix on 0.1.2.x.
26744 - Unmap the extrainfo cache file on exit.
26747 Changes in version 0.2.0.5-alpha - 2007-08-19
26748 This fifth development snapshot fixes compilation on Windows again;
26749 fixes an obnoxious client-side bug that slowed things down and put
26750 extra load on the network; gets us closer to using the v3 directory
26751 voting scheme; makes it easier for Tor controllers to use cookie-based
26752 authentication; and fixes a variety of other bugs.
26754 o Removed features:
26755 - Version 1 directories are no longer generated in full. Instead,
26756 authorities generate and serve "stub" v1 directories that list
26757 no servers. This will stop Tor versions 0.1.0.x and earlier from
26758 working, but (for security reasons) nobody should be running those
26761 o Major bugfixes (compilation, 0.2.0.x):
26762 - Try to fix Win32 compilation again: improve checking for IPv6 types.
26763 - Try to fix MSVC compilation: build correctly on platforms that do
26764 not define s6_addr16 or s6_addr32.
26765 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
26768 o Major bugfixes (stream expiration):
26769 - Expire not-yet-successful application streams in all cases if
26770 they've been around longer than SocksTimeout. Right now there are
26771 some cases where the stream will live forever, demanding a new
26772 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
26773 reported by lodger.
26775 o Minor features (directory servers):
26776 - When somebody requests a list of statuses or servers, and we have
26777 none of those, return a 404 rather than an empty 200.
26779 o Minor features (directory voting):
26780 - Store v3 consensus status consensuses on disk, and reload them
26783 o Minor features (security):
26784 - Warn about unsafe ControlPort configurations.
26785 - Refuse to start with certain directory authority keys, and
26786 encourage people using them to stop.
26788 o Minor features (controller):
26789 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
26790 is valid before any authentication has been received. It tells
26791 a controller what kind of authentication is expected, and what
26792 protocol is spoken. Implements proposal 119.
26793 - New config option CookieAuthFile to choose a new location for the
26794 cookie authentication file, and config option
26795 CookieAuthFileGroupReadable to make it group-readable.
26797 o Minor features (unit testing):
26798 - Add command-line arguments to unit-test executable so that we can
26799 invoke any chosen test from the command line rather than having
26800 to run the whole test suite at once; and so that we can turn on
26801 logging for the unit tests.
26803 o Minor bugfixes (on 0.1.2.x):
26804 - If we require CookieAuthentication but we fail to write the
26805 cookie file, we would warn but not exit, and end up in a state
26806 where no controller could authenticate. Now we exit.
26807 - If we require CookieAuthentication, stop generating a new cookie
26808 every time we change any piece of our config.
26809 - When loading bandwidth history, do not believe any information in
26810 the future. Fixes bug 434.
26811 - When loading entry guard information, do not believe any information
26813 - When we have our clock set far in the future and generate an
26814 onion key, then re-set our clock to be correct, we should not stop
26815 the onion key from getting rotated.
26816 - Clean up torrc sample config file.
26817 - Do not automatically run configure from autogen.sh. This
26818 non-standard behavior tended to annoy people who have built other
26821 o Minor bugfixes (on 0.2.0.x):
26822 - Fix a bug with AutomapHostsOnResolve that would always cause
26823 the second request to fail. Bug reported by Kate. Bugfix on
26825 - Fix a bug in ADDRMAP controller replies that would sometimes
26826 try to print a NULL. Patch from tup.
26827 - Read v3 directory authority keys from the right location.
26828 - Numerous bugfixes to directory voting code.
26831 Changes in version 0.1.2.16 - 2007-08-01
26832 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
26833 remote attacker in certain situations to rewrite the user's torrc
26834 configuration file. This can completely compromise anonymity of users
26835 in most configurations, including those running the Vidalia bundles,
26836 TorK, etc. Or worse.
26838 o Major security fixes:
26839 - Close immediately after missing authentication on control port;
26840 do not allow multiple authentication attempts.
26843 Changes in version 0.2.0.4-alpha - 2007-08-01
26844 This fourth development snapshot fixes a critical security vulnerability
26845 for most users, specifically those running Vidalia, TorK, etc. Everybody
26846 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
26848 o Major security fixes:
26849 - Close immediately after missing authentication on control port;
26850 do not allow multiple authentication attempts.
26852 o Major bugfixes (compilation):
26853 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
26856 o Minor features (performance):
26857 - Be even more aggressive about releasing RAM from small
26858 empty buffers. Thanks to our free-list code, this shouldn't be too
26859 performance-intensive.
26860 - Disable sentinel-based debugging for buffer code: we squashed all
26861 the bugs that this was supposed to detect a long time ago, and
26862 now its only effect is to change our buffer sizes from nice
26863 powers of two (which platform mallocs tend to like) to values
26864 slightly over powers of two (which make some platform mallocs sad).
26865 - Log malloc statistics from mallinfo() on platforms where it
26869 Changes in version 0.2.0.3-alpha - 2007-07-29
26870 This third development snapshot introduces new experimental
26871 blocking-resistance features and a preliminary version of the v3
26872 directory voting design, and includes many other smaller features
26876 - The first pieces of our "bridge" design for blocking-resistance
26877 are implemented. People can run bridge directory authorities;
26878 people can run bridges; and people can configure their Tor clients
26879 with a set of bridges to use as the first hop into the Tor network.
26880 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
26882 - Create listener connections before we setuid to the configured
26883 User and Group. Now non-Windows users can choose port values
26884 under 1024, start Tor as root, and have Tor bind those ports
26885 before it changes to another UID. (Windows users could already
26887 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
26888 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
26889 on "vserver" accounts. (Patch from coderman.)
26890 - Be even more aggressive about separating local traffic from relayed
26891 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
26893 o Major features (experimental):
26894 - First cut of code for "v3 dir voting": directory authorities will
26895 vote on a common network status document rather than each publishing
26896 their own opinion. This code needs more testing and more corner-case
26897 handling before it's ready for use.
26900 - Directory authorities now call routers Fast if their bandwidth is
26901 at least 100KB/s, and consider their bandwidth adequate to be a
26902 Guard if it is at least 250KB/s, no matter the medians. This fix
26903 complements proposal 107. [Bugfix on 0.1.2.x]
26904 - Directory authorities now never mark more than 3 servers per IP as
26905 Valid and Running. (Implements proposal 109, by Kevin Bauer and
26907 - Minor change to organizationName and commonName generation
26908 procedures in TLS certificates during Tor handshakes, to invalidate
26909 some earlier censorware approaches. This is not a long-term
26910 solution, but applying it will give us a bit of time to look into
26911 the epidemiology of countermeasures as they spread.
26913 o Major bugfixes (directory):
26914 - Rewrite directory tokenization code to never run off the end of
26915 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
26917 o Minor features (controller):
26918 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
26919 match requests to applications. (Patch from Robert Hogan.)
26920 - Report address and port correctly on connections to DNSPort. (Patch
26921 from Robert Hogan.)
26922 - Add a RESOLVE command to launch hostname lookups. (Original patch
26923 from Robert Hogan.)
26924 - Add GETINFO status/enough-dir-info to let controllers tell whether
26925 Tor has downloaded sufficient directory information. (Patch
26927 - You can now use the ControlSocket option to tell Tor to listen for
26928 controller connections on Unix domain sockets on systems that
26929 support them. (Patch from Peter Palfrader.)
26930 - STREAM NEW events are generated for DNSPort requests and for
26931 tunneled directory connections. (Patch from Robert Hogan.)
26932 - New "GETINFO address-mappings/*" command to get address mappings
26933 with expiry information. "addr-mappings/*" is now deprecated.
26936 o Minor features (misc):
26937 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
26939 - The tor-gencert tool for v3 directory authorities now creates all
26940 files as readable to the file creator only, and write-protects
26941 the authority identity key.
26942 - When dumping memory usage, list bytes used in buffer memory
26944 - When running with dmalloc, dump more stats on hup and on exit.
26945 - Directory authorities now fail quickly and (relatively) harmlessly
26946 if they generate a network status document that is somehow
26949 o Traffic load balancing improvements:
26950 - If exit bandwidth ever exceeds one third of total bandwidth, then
26951 use the correct formula to weight exit nodes when choosing paths.
26952 (Based on patch from Mike Perry.)
26953 - Choose perfectly fairly among routers when choosing by bandwidth and
26954 weighting by fraction of bandwidth provided by exits. Previously, we
26955 would choose with only approximate fairness, and correct ourselves
26956 if we ran off the end of the list. [Bugfix on 0.1.2.x]
26958 o Performance improvements:
26959 - Be more aggressive with freeing buffer RAM or putting it on the
26961 - Use Critical Sections rather than Mutexes for synchronizing threads
26962 on win32; Mutexes are heavier-weight, and designed for synchronizing
26965 o Deprecated and removed features:
26966 - RedirectExits is now deprecated.
26967 - Stop allowing address masks that do not correspond to bit prefixes.
26968 We have warned about these for a really long time; now it's time
26969 to reject them. (Patch from croup.)
26971 o Minor bugfixes (directory):
26972 - Fix another crash bug related to extra-info caching. (Bug found by
26973 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
26974 - Directories no longer return a "304 not modified" when they don't
26975 have the networkstatus the client asked for. Also fix a memory
26976 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
26977 - We had accidentally labelled 0.1.2.x directory servers as not
26978 suitable for begin_dir requests, and had labelled no directory
26979 servers as suitable for uploading extra-info documents. [Bugfix
26982 o Minor bugfixes (dns):
26983 - Fix a crash when DNSPort is set more than once. (Patch from Robert
26984 Hogan.) [Bugfix on 0.2.0.2-alpha]
26985 - Add DNSPort connections to the global connection list, so that we
26986 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
26988 - Fix a dangling reference that could lead to a crash when DNSPort is
26989 changed or closed (Patch from Robert Hogan.) [Bugfix on
26992 o Minor bugfixes (controller):
26993 - Provide DNS expiry times in GMT, not in local time. For backward
26994 compatibility, ADDRMAP events only provide GMT expiry in an extended
26995 field. "GETINFO address-mappings" always does the right thing.
26996 - Use CRLF line endings properly in NS events.
26997 - Terminate multi-line control events properly. (Original patch
26998 from tup.) [Bugfix on 0.1.2.x-alpha]
26999 - Do not include spaces in SOURCE_ADDR fields in STREAM
27000 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
27003 Changes in version 0.1.2.15 - 2007-07-17
27004 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
27005 problems, fixes compilation on BSD, and fixes a variety of other
27006 bugs. Everybody should upgrade.
27008 o Major bugfixes (compilation):
27009 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
27011 o Major bugfixes (crashes):
27012 - Try even harder not to dereference the first character after
27013 an mmap(). Reported by lodger.
27014 - Fix a crash bug in directory authorities when we re-number the
27015 routerlist while inserting a new router.
27016 - When the cached-routers file is an even multiple of the page size,
27017 don't run off the end and crash. (Fixes bug 455; based on idea
27019 - Fix eventdns.c behavior on Solaris: It is critical to include
27020 orconfig.h _before_ sys/types.h, so that we can get the expected
27021 definition of _FILE_OFFSET_BITS.
27023 o Major bugfixes (security):
27024 - Fix a possible buffer overrun when using BSD natd support. Bug
27026 - When sending destroy cells from a circuit's origin, don't include
27027 the reason for tearing down the circuit. The spec says we didn't,
27028 and now we actually don't. Reported by lodger.
27029 - Keep streamids from different exits on a circuit separate. This
27030 bug may have allowed other routers on a given circuit to inject
27031 cells into streams. Reported by lodger; fixes bug 446.
27032 - If there's a never-before-connected-to guard node in our list,
27033 never choose any guards past it. This way we don't expand our
27034 guard list unless we need to.
27036 o Minor bugfixes (guard nodes):
27037 - Weight guard selection by bandwidth, so that low-bandwidth nodes
27038 don't get overused as guards.
27040 o Minor bugfixes (directory):
27041 - Correctly count the number of authorities that recommend each
27042 version. Previously, we were under-counting by 1.
27043 - Fix a potential crash bug when we load many server descriptors at
27044 once and some of them make others of them obsolete. Fixes bug 458.
27046 o Minor bugfixes (hidden services):
27047 - Stop tearing down the whole circuit when the user asks for a
27048 connection to a port that the hidden service didn't configure.
27051 o Minor bugfixes (misc):
27052 - On Windows, we were preventing other processes from reading
27053 cached-routers while Tor was running. Reported by janbar.
27054 - Fix a possible (but very unlikely) bug in picking routers by
27055 bandwidth. Add a log message to confirm that it is in fact
27056 unlikely. Patch from lodger.
27057 - Backport a couple of memory leak fixes.
27058 - Backport miscellaneous cosmetic bugfixes.
27061 Changes in version 0.2.0.2-alpha - 2007-06-02
27062 o Major bugfixes on 0.2.0.1-alpha:
27063 - Fix an assertion failure related to servers without extra-info digests.
27064 Resolves bugs 441 and 442.
27066 o Minor features (directory):
27067 - Support "If-Modified-Since" when answering HTTP requests for
27068 directories, running-routers documents, and network-status documents.
27069 (There's no need to support it for router descriptors, since those
27070 are downloaded by descriptor digest.)
27072 o Minor build issues:
27073 - Clear up some MIPSPro compiler warnings.
27074 - When building from a tarball on a machine that happens to have SVK
27075 installed, report the micro-revision as whatever version existed
27076 in the tarball, not as "x".
27079 Changes in version 0.2.0.1-alpha - 2007-06-01
27080 This early development snapshot provides new features for people running
27081 Tor as both a client and a server (check out the new RelayBandwidth
27082 config options); lets Tor run as a DNS proxy; and generally moves us
27083 forward on a lot of fronts.
27085 o Major features, server usability:
27086 - New config options RelayBandwidthRate and RelayBandwidthBurst:
27087 a separate set of token buckets for relayed traffic. Right now
27088 relayed traffic is defined as answers to directory requests, and
27089 OR connections that don't have any local circuits on them.
27091 o Major features, client usability:
27092 - A client-side DNS proxy feature to replace the need for
27093 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
27094 for DNS requests on port 9999, use the Tor network to resolve them
27095 anonymously, and send the reply back like a regular DNS server.
27096 The code still only implements a subset of DNS.
27097 - Make PreferTunneledDirConns and TunnelDirConns work even when
27098 we have no cached directory info. This means Tor clients can now
27099 do all of their connections protected by TLS.
27101 o Major features, performance and efficiency:
27102 - Directory authorities accept and serve "extra info" documents for
27103 routers. These documents contain fields from router descriptors
27104 that aren't usually needed, and that use a lot of excess
27105 bandwidth. Once these fields are removed from router descriptors,
27106 the bandwidth savings should be about 60%. [Partially implements
27108 - Servers upload extra-info documents to any authority that accepts
27109 them. Authorities (and caches that have been configured to download
27110 extra-info documents) download them as needed. [Partially implements
27112 - Change the way that Tor buffers data that it is waiting to write.
27113 Instead of queueing data cells in an enormous ring buffer for each
27114 client->OR or OR->OR connection, we now queue cells on a separate
27115 queue for each circuit. This lets us use less slack memory, and
27116 will eventually let us be smarter about prioritizing different kinds
27118 - Use memory pools to allocate cells with better speed and memory
27119 efficiency, especially on platforms where malloc() is inefficient.
27120 - Stop reading on edge connections when their corresponding circuit
27121 buffers are full; start again as the circuits empty out.
27123 o Major features, other:
27124 - Add an HSAuthorityRecordStats option that hidden service authorities
27125 can use to track statistics of overall hidden service usage without
27126 logging information that would be very useful to an attacker.
27127 - Start work implementing multi-level keys for directory authorities:
27128 Add a standalone tool to generate key certificates. (Proposal 103.)
27131 - Directory authorities now call routers Stable if they have an
27132 uptime of at least 30 days, even if that's not the median uptime
27133 in the network. Implements proposal 107, suggested by Kevin Bauer
27136 o Minor fixes (resource management):
27137 - Count the number of open sockets separately from the number
27138 of active connection_t objects. This will let us avoid underusing
27139 our allocated connection limit.
27140 - We no longer use socket pairs to link an edge connection to an
27141 anonymous directory connection or a DirPort test connection.
27142 Instead, we track the link internally and transfer the data
27143 in-process. This saves two sockets per "linked" connection (at the
27144 client and at the server), and avoids the nasty Windows socketpair()
27146 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
27147 for every single inactive connection_t. Free items from the
27148 4k/16k-buffer free lists when they haven't been used for a while.
27150 o Minor features (build):
27151 - Make autoconf search for libevent, openssl, and zlib consistently.
27152 - Update deprecated macros in configure.in.
27153 - When warning about missing headers, tell the user to let us
27154 know if the compile succeeds anyway, so we can downgrade the
27156 - Include the current subversion revision as part of the version
27157 string: either fetch it directly if we're in an SVN checkout, do
27158 some magic to guess it if we're in an SVK checkout, or use
27159 the last-detected version if we're building from a .tar.gz.
27160 Use this version consistently in log messages.
27162 o Minor features (logging):
27163 - Always prepend "Bug: " to any log message about a bug.
27164 - Put a platform string (e.g. "Linux i686") in the startup log
27165 message, so when people paste just their logs, we know if it's
27166 OpenBSD or Windows or what.
27167 - When logging memory usage, break down memory used in buffers by
27170 o Minor features (directory system):
27171 - New config option V2AuthoritativeDirectory that all directory
27172 authorities should set. This will let future authorities choose
27173 not to serve V2 directory information.
27174 - Directory authorities allow multiple router descriptors and/or extra
27175 info documents to be uploaded in a single go. This will make
27176 implementing proposal 104 simpler.
27178 o Minor features (controller):
27179 - Add a new config option __DisablePredictedCircuits designed for
27180 use by the controller, when we don't want Tor to build any circuits
27182 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
27183 so we can exit from the middle of the circuit.
27184 - Implement "getinfo status/circuit-established".
27185 - Implement "getinfo status/version/..." so a controller can tell
27186 whether the current version is recommended, and whether any versions
27187 are good, and how many authorities agree. (Patch from shibz.)
27189 o Minor features (hidden services):
27190 - Allow multiple HiddenServicePort directives with the same virtual
27191 port; when they occur, the user is sent round-robin to one
27192 of the target ports chosen at random. Partially fixes bug 393 by
27193 adding limited ad-hoc round-robining.
27195 o Minor features (other):
27197 - Add a new AutomapHostsOnResolve option: when it is enabled, any
27198 resolve request for hosts matching a given pattern causes Tor to
27199 generate an internal virtual address mapping for that host. This
27200 allows DNSPort to work sensibly with hidden service users. By
27201 default, .exit and .onion addresses are remapped; the list of
27202 patterns can be reconfigured with AutomapHostsSuffixes.
27203 - Add an "-F" option to tor-resolve to force a resolve for a .onion
27204 address. Thanks to the AutomapHostsOnResolve option, this is no
27205 longer a completely silly thing to do.
27206 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
27207 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
27208 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
27209 minus 1 byte: the actual maximum declared bandwidth.
27211 o Removed features:
27212 - Removed support for the old binary "version 0" controller protocol.
27213 This has been deprecated since 0.1.1, and warnings have been issued
27214 since 0.1.2. When we encounter a v0 control message, we now send
27215 back an error and close the connection.
27216 - Remove the old "dns worker" server DNS code: it hasn't been default
27217 since 0.1.2.2-alpha, and all the servers seem to be using the new
27220 o Minor bugfixes (portability):
27221 - Even though Windows is equally happy with / and \ as path separators,
27222 try to use \ consistently on Windows and / consistently on Unix: it
27223 makes the log messages nicer.
27224 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
27225 - Read resolv.conf files correctly on platforms where read() returns
27226 partial results on small file reads.
27228 o Minor bugfixes (directory):
27229 - Correctly enforce that elements of directory objects do not appear
27230 more often than they are allowed to appear.
27231 - When we are reporting the DirServer line we just parsed, we were
27232 logging the second stanza of the key fingerprint, not the first.
27234 o Minor bugfixes (logging):
27235 - When we hit an EOF on a log (probably because we're shutting down),
27236 don't try to remove the log from the list: just mark it as
27237 unusable. (Bulletproofs against bug 222.)
27239 o Minor bugfixes (other):
27240 - In the exitlist script, only consider the most recently published
27241 server descriptor for each server. Also, when the user requests
27242 a list of servers that _reject_ connections to a given address,
27243 explicitly exclude the IPs that also have servers that accept
27244 connections to that address. (Resolves bug 405.)
27245 - Stop allowing hibernating servers to be "stable" or "fast".
27246 - On Windows, we were preventing other processes from reading
27247 cached-routers while Tor was running. (Reported by janbar)
27248 - Make the NodeFamilies config option work. (Reported by
27249 lodger -- it has never actually worked, even though we added it
27251 - Check return values from pthread_mutex functions.
27252 - Don't save non-general-purpose router descriptors to the disk cache,
27253 because we have no way of remembering what their purpose was when
27255 - Add even more asserts to hunt down bug 417.
27256 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
27257 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
27258 Add a log message to confirm that it is in fact unlikely.
27260 o Minor bugfixes (controller):
27261 - Make 'getinfo fingerprint' return a 551 error if we're not a
27262 server, so we match what the control spec claims we do. Reported
27264 - Fix a typo in an error message when extendcircuit fails that
27265 caused us to not follow the \r\n-based delimiter protocol. Reported
27268 o Code simplifications and refactoring:
27269 - Stop passing around circuit_t and crypt_path_t pointers that are
27270 implicit in other procedure arguments.
27271 - Drop the old code to choke directory connections when the
27272 corresponding OR connections got full: thanks to the cell queue
27273 feature, OR conns don't get full any more.
27274 - Make dns_resolve() handle attaching connections to circuits
27275 properly, so the caller doesn't have to.
27276 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
27277 - Keep the connection array as a dynamic smartlist_t, rather than as
27278 a fixed-sized array. This is important, as the number of connections
27279 is becoming increasingly decoupled from the number of sockets.
27282 Changes in version 0.1.2.14 - 2007-05-25
27283 Tor 0.1.2.14 changes the addresses of two directory authorities (this
27284 change especially affects those who serve or use hidden services),
27285 and fixes several other crash- and security-related bugs.
27287 o Directory authority changes:
27288 - Two directory authorities (moria1 and moria2) just moved to new
27289 IP addresses. This change will particularly affect those who serve
27290 or use hidden services.
27292 o Major bugfixes (crashes):
27293 - If a directory server runs out of space in the connection table
27294 as it's processing a begin_dir request, it will free the exit stream
27295 but leave it attached to the circuit, leading to unpredictable
27296 behavior. (Reported by seeess, fixes bug 425.)
27297 - Fix a bug in dirserv_remove_invalid() that would cause authorities
27298 to corrupt memory under some really unlikely scenarios.
27299 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
27300 - Avoid segfaults when reading from mmaped descriptor file. (Reported
27303 o Major bugfixes (security):
27304 - When choosing an entry guard for a circuit, avoid using guards
27305 that are in the same family as the chosen exit -- not just guards
27306 that are exactly the chosen exit. (Reported by lodger.)
27308 o Major bugfixes (resource management):
27309 - If a directory authority is down, skip it when deciding where to get
27310 networkstatus objects or descriptors. Otherwise we keep asking
27311 every 10 seconds forever. Fixes bug 384.
27312 - Count it as a failure if we fetch a valid network-status but we
27313 don't want to keep it. Otherwise we'll keep fetching it and keep
27314 not wanting to keep it. Fixes part of bug 422.
27315 - If all of our dirservers have given us bad or no networkstatuses
27316 lately, then stop hammering them once per minute even when we
27317 think they're failed. Fixes another part of bug 422.
27320 - Actually set the purpose correctly for descriptors inserted with
27321 purpose=controller.
27322 - When we have k non-v2 authorities in our DirServer config,
27323 we ignored the last k authorities in the list when updating our
27325 - Correctly back-off from requesting router descriptors that we are
27326 having a hard time downloading.
27327 - Read resolv.conf files correctly on platforms where read() returns
27328 partial results on small file reads.
27329 - Don't rebuild the entire router store every time we get 32K of
27330 routers: rebuild it when the journal gets very large, or when
27331 the gaps in the store get very large.
27334 - When routers publish SVN revisions in their router descriptors,
27335 authorities now include those versions correctly in networkstatus
27337 - Warn when using a version of libevent before 1.3b to run a server on
27338 OSX or BSD: these versions interact badly with userspace threads.
27341 Changes in version 0.1.2.13 - 2007-04-24
27342 This release features some major anonymity fixes, such as safer path
27343 selection; better client performance; faster bootstrapping, better
27344 address detection, and better DNS support for servers; write limiting as
27345 well as read limiting to make servers easier to run; and a huge pile of
27346 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
27348 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
27349 of the Freenode IRC network, remembering his patience and vision for
27350 free speech on the Internet.
27353 - Fix a memory leak when we ask for "all" networkstatuses and we
27354 get one we don't recognize.
27355 - Add more asserts to hunt down bug 417.
27356 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
27359 Changes in version 0.1.2.12-rc - 2007-03-16
27361 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
27362 directory information requested inside Tor connections (i.e. via
27363 begin_dir cells). It only triggered when the same connection was
27364 serving other data at the same time. Reported by seeess.
27367 - When creating a circuit via the controller, send a 'launched'
27368 event when we're done, so we follow the spec better.
27371 Changes in version 0.1.2.11-rc - 2007-03-15
27372 o Minor bugfixes (controller), reported by daejees:
27373 - Correct the control spec to match how the code actually responds
27374 to 'getinfo addr-mappings/*'.
27375 - The control spec described a GUARDS event, but the code
27376 implemented a GUARD event. Standardize on GUARD, but let people
27377 ask for GUARDS too.
27380 Changes in version 0.1.2.10-rc - 2007-03-07
27381 o Major bugfixes (Windows):
27382 - Do not load the NT services library functions (which may not exist)
27383 just to detect if we're a service trying to shut down. Now we run
27384 on Win98 and friends again.
27386 o Minor bugfixes (other):
27387 - Clarify a couple of log messages.
27388 - Fix a misleading socks5 error number.
27391 Changes in version 0.1.2.9-rc - 2007-03-02
27392 o Major bugfixes (Windows):
27393 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
27394 of the usual GCC "%llu". This prevents a bug when saving 64-bit
27395 int configuration values: the high-order 32 bits would get
27396 truncated. In particular, we were being bitten by the default
27397 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
27398 and maybe also bug 397.)
27400 o Minor bugfixes (performance):
27401 - Use OpenSSL's AES implementation on platforms where it's faster.
27402 This could save us as much as 10% CPU usage.
27404 o Minor bugfixes (server):
27405 - Do not rotate onion key immediately after setting it for the first
27408 o Minor bugfixes (directory authorities):
27409 - Stop calling servers that have been hibernating for a long time
27410 "stable". Also, stop letting hibernating or obsolete servers affect
27411 uptime and bandwidth cutoffs.
27412 - Stop listing hibernating servers in the v1 directory.
27414 o Minor bugfixes (hidden services):
27415 - Upload hidden service descriptors slightly less often, to reduce
27416 load on authorities.
27418 o Minor bugfixes (other):
27419 - Fix an assert that could trigger if a controller quickly set then
27420 cleared EntryNodes. Bug found by Udo van den Heuvel.
27421 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
27423 - Fix a potential race condition in the rpm installer. Found by
27425 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
27426 of 2 as indicating that the server is completely bad; it sometimes
27427 means that the server is just bad for the request in question. (may fix
27428 the last of bug 326.)
27429 - Disable encrypted directory connections when we don't have a server
27430 descriptor for the destination. We'll get this working again in
27434 Changes in version 0.1.2.8-beta - 2007-02-26
27435 o Major bugfixes (crashes):
27436 - Stop crashing when the controller asks us to resetconf more than
27437 one config option at once. (Vidalia 0.0.11 does this.)
27438 - Fix a crash that happened on Win98 when we're given command-line
27439 arguments: don't try to load NT service functions from advapi32.dll
27440 except when we need them. (Bug introduced in 0.1.2.7-alpha;
27442 - Fix a longstanding obscure crash bug that could occur when
27443 we run out of DNS worker processes. (Resolves bug 390.)
27445 o Major bugfixes (hidden services):
27446 - Correctly detect whether hidden service descriptor downloads are
27447 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
27449 o Major bugfixes (accounting):
27450 - When we start during an accounting interval before it's time to wake
27451 up, remember to wake up at the correct time. (May fix bug 342.)
27453 o Minor bugfixes (controller):
27454 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
27455 clear the corresponding on_circuit variable, and remember later
27456 that we don't need to send a redundant CLOSED event. Resolves part
27458 - Report events where a resolve succeeded or where we got a socks
27459 protocol error correctly, rather than calling both of them
27461 - Change reported stream target addresses to IP consistently when
27462 we finally get the IP from an exit node.
27463 - Send log messages to the controller even if they happen to be very
27466 o Minor bugfixes (other):
27467 - Display correct results when reporting which versions are
27468 recommended, and how recommended they are. (Resolves bug 383.)
27469 - Improve our estimates for directory bandwidth to be less random:
27470 guess that an unrecognized directory will have the average bandwidth
27471 from all known directories, not that it will have the average
27472 bandwidth from those directories earlier than it on the list.
27473 - If we start a server with ClientOnly 1, then set ClientOnly to 0
27474 and hup, stop triggering an assert based on an empty onion_key.
27475 - On platforms with no working mmap() equivalent, don't warn the
27476 user when cached-routers doesn't exist.
27477 - Warn the user when mmap() [or its equivalent] fails for some reason
27478 other than file-not-found.
27479 - Don't warn the user when cached-routers.new doesn't exist: that's
27480 perfectly fine when starting up for the first time.
27481 - When EntryNodes are configured, rebuild the guard list to contain,
27482 in order: the EntryNodes that were guards before; the rest of the
27483 EntryNodes; the nodes that were guards before.
27484 - Mask out all signals in sub-threads; only the libevent signal
27485 handler should be processing them. This should prevent some crashes
27486 on some machines using pthreads. (Patch from coderman.)
27487 - Fix switched arguments on memset in the implementation of
27488 tor_munmap() for systems with no mmap() call.
27489 - When Tor receives a router descriptor that it asked for, but
27490 no longer wants (because it has received fresh networkstatuses
27491 in the meantime), do not warn the user. Cache the descriptor if
27492 we're a cache; drop it if we aren't.
27493 - Make earlier entry guards _really_ get retried when the network
27495 - On a malformed DNS reply, always give an error to the corresponding
27497 - Build with recent libevents on platforms that do not define the
27498 nonstandard types "u_int8_t" and friends.
27500 o Minor features (controller):
27501 - Warn the user when an application uses the obsolete binary v0
27502 control protocol. We're planning to remove support for it during
27503 the next development series, so it's good to give people some
27505 - Add STREAM_BW events to report per-entry-stream bandwidth
27506 use. (Patch from Robert Hogan.)
27507 - Rate-limit SIGNEWNYM signals in response to controllers that
27508 impolitely generate them for every single stream. (Patch from
27509 mwenge; closes bug 394.)
27510 - Make REMAP stream events have a SOURCE (cache or exit), and
27511 make them generated in every case where we get a successful
27512 connected or resolved cell.
27514 o Minor bugfixes (performance):
27515 - Call router_have_min_dir_info half as often. (This is showing up in
27516 some profiles, but not others.)
27517 - When using GCC, make log_debug never get called at all, and its
27518 arguments never get evaluated, when no debug logs are configured.
27519 (This is showing up in some profiles, but not others.)
27522 - Remove some never-implemented options. Mark PathlenCoinWeight as
27524 - Implement proposal 106: Stop requiring clients to have well-formed
27525 certificates; stop checking nicknames in certificates. (Clients
27526 have certificates so that they can look like Tor servers, but in
27527 the future we might want to allow them to look like regular TLS
27528 clients instead. Nicknames in certificates serve no purpose other
27529 than making our protocol easier to recognize on the wire.)
27530 - Revise messages on handshake failure again to be even more clear about
27531 which are incoming connections and which are outgoing.
27532 - Discard any v1 directory info that's over 1 month old (for
27533 directories) or over 1 week old (for running-routers lists).
27534 - Do not warn when individual nodes in the configuration's EntryNodes,
27535 ExitNodes, etc are down: warn only when all possible nodes
27536 are down. (Fixes bug 348.)
27537 - Always remove expired routers and networkstatus docs before checking
27538 whether we have enough information to build circuits. (Fixes
27540 - Put a lower-bound on MaxAdvertisedBandwidth.
27543 Changes in version 0.1.2.7-alpha - 2007-02-06
27544 o Major bugfixes (rate limiting):
27545 - Servers decline directory requests much more aggressively when
27546 they're low on bandwidth. Otherwise they end up queueing more and
27547 more directory responses, which can't be good for latency.
27548 - But never refuse directory requests from local addresses.
27549 - Fix a memory leak when sending a 503 response for a networkstatus
27551 - Be willing to read or write on local connections (e.g. controller
27552 connections) even when the global rate limiting buckets are empty.
27553 - If our system clock jumps back in time, don't publish a negative
27554 uptime in the descriptor. Also, don't let the global rate limiting
27555 buckets go absurdly negative.
27556 - Flush local controller connection buffers periodically as we're
27557 writing to them, so we avoid queueing 4+ megabytes of data before
27560 o Major bugfixes (NT services):
27561 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
27562 command-line flag so that admins can override the default by saying
27563 "tor --service install --user "SomeUser"". This will not affect
27564 existing installed services. Also, warn the user that the service
27565 will look for its configuration file in the service user's
27566 %appdata% directory. (We can't do the 'hardwire the user's appdata
27567 directory' trick any more, since we may not have read access to that
27570 o Major bugfixes (other):
27571 - Previously, we would cache up to 16 old networkstatus documents
27572 indefinitely, if they came from nontrusted authorities. Now we
27573 discard them if they are more than 10 days old.
27574 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
27576 - Detect and reject malformed DNS responses containing circular
27578 - If exits are rare enough that we're not marking exits as guards,
27579 ignore exit bandwidth when we're deciding the required bandwidth
27581 - When we're handling a directory connection tunneled over Tor,
27582 don't fill up internal memory buffers with all the data we want
27583 to tunnel; instead, only add it if the OR connection that will
27584 eventually receive it has some room for it. (This can lead to
27585 slowdowns in tunneled dir connections; a better solution will have
27586 to wait for 0.2.0.)
27588 o Minor bugfixes (dns):
27589 - Add some defensive programming to eventdns.c in an attempt to catch
27590 possible memory-stomping bugs.
27591 - Detect and reject DNS replies containing IPv4 or IPv6 records with
27592 an incorrect number of bytes. (Previously, we would ignore the
27594 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
27595 in the correct order, and doesn't crash.
27596 - Free memory held in recently-completed DNS lookup attempts on exit.
27597 This was not a memory leak, but may have been hiding memory leaks.
27598 - Handle TTL values correctly on reverse DNS lookups.
27599 - Treat failure to parse resolv.conf as an error.
27601 o Minor bugfixes (other):
27602 - Fix crash with "tor --list-fingerprint" (reported by seeess).
27603 - When computing clock skew from directory HTTP headers, consider what
27604 time it was when we finished asking for the directory, not what
27606 - Expire socks connections if they spend too long waiting for the
27607 handshake to finish. Previously we would let them sit around for
27608 days, if the connecting application didn't close them either.
27609 - And if the socks handshake hasn't started, don't send a
27610 "DNS resolve socks failed" handshake reply; just close it.
27611 - Stop using C functions that OpenBSD's linker doesn't like.
27612 - Don't launch requests for descriptors unless we have networkstatuses
27613 from at least half of the authorities. This delays the first
27614 download slightly under pathological circumstances, but can prevent
27615 us from downloading a bunch of descriptors we don't need.
27616 - Do not log IPs with TLS failures for incoming TLS
27617 connections. (Fixes bug 382.)
27618 - If the user asks to use invalid exit nodes, be willing to use
27620 - Stop using the reserved ac_cv namespace in our configure script.
27621 - Call stat() slightly less often; use fstat() when possible.
27622 - Refactor the way we handle pending circuits when an OR connection
27623 completes or fails, in an attempt to fix a rare crash bug.
27624 - Only rewrite a conn's address based on X-Forwarded-For: headers
27625 if it's a parseable public IP address; and stop adding extra quotes
27626 to the resulting address.
27629 - Weight directory requests by advertised bandwidth. Now we can
27630 let servers enable write limiting but still allow most clients to
27631 succeed at their directory requests. (We still ignore weights when
27632 choosing a directory authority; I hope this is a feature.)
27635 - Create a new file ReleaseNotes which was the old ChangeLog. The
27636 new ChangeLog file now includes the summaries for all development
27638 - Check for addresses with invalid characters at the exit as well
27639 as at the client, and warn less verbosely when they fail. You can
27640 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
27641 - Adapt a patch from goodell to let the contrib/exitlist script
27642 take arguments rather than require direct editing.
27643 - Inform the server operator when we decide not to advertise a
27644 DirPort due to AccountingMax enabled or a low BandwidthRate. It
27645 was confusing Zax, so now we're hopefully more helpful.
27646 - Bring us one step closer to being able to establish an encrypted
27647 directory tunnel without knowing a descriptor first. Still not
27648 ready yet. As part of the change, now assume we can use a
27649 create_fast cell if we don't know anything about a router.
27650 - Allow exit nodes to use nameservers running on ports other than 53.
27651 - Servers now cache reverse DNS replies.
27652 - Add an --ignore-missing-torrc command-line option so that we can
27653 get the "use sensible defaults if the configuration file doesn't
27654 exist" behavior even when specifying a torrc location on the command
27657 o Minor features (controller):
27658 - Track reasons for OR connection failure; make these reasons
27659 available via the controller interface. (Patch from Mike Perry.)
27660 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
27661 can learn when clients are sending malformed hostnames to Tor.
27662 - Clean up documentation for controller status events.
27663 - Add a REMAP status to stream events to note that a stream's
27664 address has changed because of a cached address or a MapAddress
27668 Changes in version 0.1.2.6-alpha - 2007-01-09
27670 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
27671 connection handles more than 4 gigs in either direction, we crash.
27672 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
27673 advertised exit node, somebody might try to exit from us when
27674 we're bootstrapping and before we've built our descriptor yet.
27675 Refuse the connection rather than crashing.
27678 - Warn if we (as a server) find that we've resolved an address that we
27679 weren't planning to resolve.
27680 - Warn that using select() on any libevent version before 1.1 will be
27681 unnecessarily slow (even for select()).
27682 - Flush ERR-level controller status events just like we currently
27683 flush ERR-level log events, so that a Tor shutdown doesn't prevent
27684 the controller from learning about current events.
27686 o Minor features (more controller status events):
27687 - Implement EXTERNAL_ADDRESS server status event so controllers can
27688 learn when our address changes.
27689 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
27690 can learn when directories reject our descriptor.
27691 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
27692 can learn when a client application is speaking a non-socks protocol
27694 - Implement DANGEROUS_SOCKS client status event so controllers
27695 can learn when a client application is leaking DNS addresses.
27696 - Implement BUG general status event so controllers can learn when
27697 Tor is unhappy about its internal invariants.
27698 - Implement CLOCK_SKEW general status event so controllers can learn
27699 when Tor thinks the system clock is set incorrectly.
27700 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
27701 server status events so controllers can learn when their descriptors
27702 are accepted by a directory.
27703 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
27704 server status events so controllers can learn about Tor's progress in
27705 deciding whether it's reachable from the outside.
27706 - Implement BAD_LIBEVENT general status event so controllers can learn
27707 when we have a version/method combination in libevent that needs to
27709 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
27710 and DNS_USELESS server status events so controllers can learn
27711 about changes to DNS server status.
27713 o Minor features (directory):
27714 - Authorities no longer recommend exits as guards if this would shift
27715 too much load to the exit nodes.
27718 Changes in version 0.1.2.5-alpha - 2007-01-06
27720 - Enable write limiting as well as read limiting. Now we sacrifice
27721 capacity if we're pushing out lots of directory traffic, rather
27722 than overrunning the user's intended bandwidth limits.
27723 - Include TLS overhead when counting bandwidth usage; previously, we
27724 would count only the bytes sent over TLS, but not the bytes used
27726 - Support running the Tor service with a torrc not in the same
27727 directory as tor.exe and default to using the torrc located in
27728 the %appdata%\Tor\ of the user who installed the service. Patch
27730 - Servers now check for the case when common DNS requests are going to
27731 wildcarded addresses (i.e. all getting the same answer), and change
27732 their exit policy to reject *:* if it's happening.
27733 - Implement BEGIN_DIR cells, so we can connect to the directory
27734 server via TLS to do encrypted directory requests rather than
27735 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
27736 config options if you like.
27738 o Minor features (config and docs):
27739 - Start using the state file to store bandwidth accounting data:
27740 the bw_accounting file is now obsolete. We'll keep generating it
27741 for a while for people who are still using 0.1.2.4-alpha.
27742 - Try to batch changes to the state file so that we do as few
27743 disk writes as possible while still storing important things in
27745 - The state file and the bw_accounting file get saved less often when
27746 the AvoidDiskWrites config option is set.
27747 - Make PIDFile work on Windows (untested).
27748 - Add internal descriptions for a bunch of configuration options:
27749 accessible via controller interface and in comments in saved
27751 - Reject *:563 (NNTPS) in the default exit policy. We already reject
27752 NNTP by default, so this seems like a sensible addition.
27753 - Clients now reject hostnames with invalid characters. This should
27754 avoid some inadvertent info leaks. Add an option
27755 AllowNonRFC953Hostnames to disable this behavior, in case somebody
27756 is running a private network with hosts called @, !, and #.
27757 - Add a maintainer script to tell us which options are missing
27758 documentation: "make check-docs".
27759 - Add a new address-spec.txt document to describe our special-case
27760 addresses: .exit, .onion, and .noconnnect.
27762 o Minor features (DNS):
27763 - Ongoing work on eventdns infrastructure: now it has dns server
27764 and ipv6 support. One day Tor will make use of it.
27765 - Add client-side caching for reverse DNS lookups.
27766 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
27767 - When we change nameservers or IP addresses, reset and re-launch
27768 our tests for DNS hijacking.
27770 o Minor features (directory):
27771 - Authorities now specify server versions in networkstatus. This adds
27772 about 2% to the size of compressed networkstatus docs, and allows
27773 clients to tell which servers support BEGIN_DIR and which don't.
27774 The implementation is forward-compatible with a proposed future
27775 protocol version scheme not tied to Tor versions.
27776 - DirServer configuration lines now have an orport= option so
27777 clients can open encrypted tunnels to the authorities without
27778 having downloaded their descriptors yet. Enabled for moria1,
27779 moria2, tor26, and lefkada now in the default configuration.
27780 - Directory servers are more willing to send a 503 "busy" if they
27781 are near their write limit, especially for v1 directory requests.
27782 Now they can use their limited bandwidth for actual Tor traffic.
27783 - Clients track responses with status 503 from dirservers. After a
27784 dirserver has given us a 503, we try not to use it until an hour has
27785 gone by, or until we have no dirservers that haven't given us a 503.
27786 - When we get a 503 from a directory, and we're not a server, we don't
27787 count the failure against the total number of failures allowed
27788 for the thing we're trying to download.
27789 - Report X-Your-Address-Is correctly from tunneled directory
27790 connections; don't report X-Your-Address-Is when it's an internal
27791 address; and never believe reported remote addresses when they're
27793 - Protect against an unlikely DoS attack on directory servers.
27794 - Add a BadDirectory flag to network status docs so that authorities
27795 can (eventually) tell clients about caches they believe to be
27798 o Minor features (controller):
27799 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
27800 - Reimplement GETINFO so that info/names stays in sync with the
27802 - Implement "GETINFO fingerprint".
27803 - Implement "SETEVENTS GUARD" so controllers can get updates on
27804 entry guard status as it changes.
27806 o Minor features (clean up obsolete pieces):
27807 - Remove some options that have been deprecated since at least
27808 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
27809 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
27810 to set log options.
27811 - We no longer look for identity and onion keys in "identity.key" and
27812 "onion.key" -- these were replaced by secret_id_key and
27813 secret_onion_key in 0.0.8pre1.
27814 - We no longer require unrecognized directory entries to be
27817 o Major bugfixes (security):
27818 - Stop sending the HttpProxyAuthenticator string to directory
27819 servers when directory connections are tunnelled through Tor.
27820 - Clients no longer store bandwidth history in the state file.
27821 - Do not log introduction points for hidden services if SafeLogging
27823 - When generating bandwidth history, round down to the nearest
27824 1k. When storing accounting data, round up to the nearest 1k.
27825 - When we're running as a server, remember when we last rotated onion
27826 keys, so that we will rotate keys once they're a week old even if
27827 we never stay up for a week ourselves.
27829 o Major bugfixes (other):
27830 - Fix a longstanding bug in eventdns that prevented the count of
27831 timed-out resolves from ever being reset. This bug caused us to
27832 give up on a nameserver the third time it timed out, and try it
27833 10 seconds later... and to give up on it every time it timed out
27835 - Take out the '5 second' timeout from the connection retry
27836 schedule. Now the first connect attempt will wait a full 10
27837 seconds before switching to a new circuit. Perhaps this will help
27838 a lot. Based on observations from Mike Perry.
27839 - Fix a bug on the Windows implementation of tor_mmap_file() that
27840 would prevent the cached-routers file from ever loading. Reported
27844 - Fix an assert failure when a directory authority sets
27845 AuthDirRejectUnlisted and then receives a descriptor from an
27846 unlisted router. Reported by seeess.
27847 - Avoid a double-free when parsing malformed DirServer lines.
27848 - Fix a bug when a BSD-style PF socket is first used. Patch from
27850 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
27851 to resolve an address at a given exit node even when they ask for
27853 - Servers no longer ever list themselves in their "family" line,
27854 even if configured to do so. This makes it easier to configure
27855 family lists conveniently.
27856 - When running as a server, don't fall back to 127.0.0.1 when no
27857 nameservers are configured in /etc/resolv.conf; instead, make the
27858 user fix resolv.conf or specify nameservers explicitly. (Resolves
27860 - Stop accepting certain malformed ports in configured exit policies.
27861 - Don't re-write the fingerprint file every restart, unless it has
27863 - Stop warning when a single nameserver fails: only warn when _all_ of
27864 our nameservers have failed. Also, when we only have one nameserver,
27865 raise the threshold for deciding that the nameserver is dead.
27866 - Directory authorities now only decide that routers are reachable
27867 if their identity keys are as expected.
27868 - When the user uses bad syntax in the Log config line, stop
27869 suggesting other bad syntax as a replacement.
27870 - Correctly detect ipv6 DNS capability on OpenBSD.
27872 o Minor bugfixes (controller):
27873 - Report the circuit number correctly in STREAM CLOSED events. Bug
27874 reported by Mike Perry.
27875 - Do not report bizarre values for results of accounting GETINFOs
27876 when the last second's write or read exceeds the allotted bandwidth.
27877 - Report "unrecognized key" rather than an empty string when the
27878 controller tries to fetch a networkstatus that doesn't exist.
27881 Changes in version 0.1.1.26 - 2006-12-14
27882 o Security bugfixes:
27883 - Stop sending the HttpProxyAuthenticator string to directory
27884 servers when directory connections are tunnelled through Tor.
27885 - Clients no longer store bandwidth history in the state file.
27886 - Do not log introduction points for hidden services if SafeLogging
27890 - Fix an assert failure when a directory authority sets
27891 AuthDirRejectUnlisted and then receives a descriptor from an
27892 unlisted router (reported by seeess).
27895 Changes in version 0.1.2.4-alpha - 2006-12-03
27897 - Add support for using natd; this allows FreeBSDs earlier than
27898 5.1.2 to have ipfw send connections through Tor without using
27899 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
27902 - Make all connections to addresses of the form ".noconnect"
27903 immediately get closed. This lets application/controller combos
27904 successfully test whether they're talking to the same Tor by
27905 watching for STREAM events.
27906 - Make cross.sh cross-compilation script work even when autogen.sh
27907 hasn't been run. (Patch from Michael Mohr.)
27908 - Statistics dumped by -USR2 now include a breakdown of public key
27909 operations, for profiling.
27912 - Fix a major leak when directory authorities parse their
27913 approved-routers list, a minor memory leak when we fail to pick
27914 an exit node, and a few rare leaks on errors.
27915 - Handle TransPort connections even when the server sends data before
27916 the client sends data. Previously, the connection would just hang
27917 until the client sent data. (Patch from tup based on patch from
27919 - Avoid assert failure when our cached-routers file is empty on
27923 - Don't log spurious warnings when we see a circuit close reason we
27924 don't recognize; it's probably just from a newer version of Tor.
27925 - Have directory authorities allow larger amounts of drift in uptime
27926 without replacing the server descriptor: previously, a server that
27927 restarted every 30 minutes could have 48 "interesting" descriptors
27929 - Start linking to the Tor specification and Tor reference manual
27930 correctly in the Windows installer.
27931 - Add Vidalia to the OS X uninstaller script, so when we uninstall
27932 Tor/Privoxy we also uninstall Vidalia.
27933 - Resume building on Irix64, and fix a lot of warnings from its
27934 MIPSpro C compiler.
27935 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
27936 when we're running as a client.
27939 Changes in version 0.1.1.25 - 2006-11-04
27941 - When a client asks us to resolve (rather than connect to)
27942 an address, and we have a cached answer, give them the cached
27943 answer. Previously, we would give them no answer at all.
27944 - We were building exactly the wrong circuits when we predict
27945 hidden service requirements, meaning Tor would have to build all
27946 its circuits on demand.
27947 - If none of our live entry guards have a high uptime, but we
27948 require a guard with a high uptime, try adding a new guard before
27949 we give up on the requirement. This patch should make long-lived
27950 connections more stable on average.
27951 - When testing reachability of our DirPort, don't launch new
27952 tests when there's already one in progress -- unreachable
27953 servers were stacking up dozens of testing streams.
27955 o Security bugfixes:
27956 - When the user sends a NEWNYM signal, clear the client-side DNS
27957 cache too. Otherwise we continue to act on previous information.
27960 - Avoid a memory corruption bug when creating a hash table for
27962 - Avoid possibility of controller-triggered crash when misusing
27963 certain commands from a v0 controller on platforms that do not
27964 handle printf("%s",NULL) gracefully.
27965 - Avoid infinite loop on unexpected controller input.
27966 - Don't log spurious warnings when we see a circuit close reason we
27967 don't recognize; it's probably just from a newer version of Tor.
27968 - Add Vidalia to the OS X uninstaller script, so when we uninstall
27969 Tor/Privoxy we also uninstall Vidalia.
27972 Changes in version 0.1.2.3-alpha - 2006-10-29
27974 - Prepare for servers to publish descriptors less often: never
27975 discard a descriptor simply for being too old until either it is
27976 recommended by no authorities, or until we get a better one for
27977 the same router. Make caches consider retaining old recommended
27978 routers for even longer.
27979 - If most authorities set a BadExit flag for a server, clients
27980 don't think of it as a general-purpose exit. Clients only consider
27981 authorities that advertise themselves as listing bad exits.
27982 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
27983 headers for content, so that we can work better in the presence of
27984 caching HTTP proxies.
27985 - Allow authorities to list nodes as bad exits by fingerprint or by
27988 o Minor features, controller:
27989 - Add a REASON field to CIRC events; for backward compatibility, this
27990 field is sent only to controllers that have enabled the extended
27991 event format. Also, add additional reason codes to explain why
27992 a given circuit has been destroyed or truncated. (Patches from
27994 - Add a REMOTE_REASON field to extended CIRC events to tell the
27995 controller about why a remote OR told us to close a circuit.
27996 - Stream events also now have REASON and REMOTE_REASON fields,
27997 working much like those for circuit events.
27998 - There's now a GETINFO ns/... field so that controllers can ask Tor
27999 about the current status of a router.
28000 - A new event type "NS" to inform a controller when our opinion of
28001 a router's status has changed.
28002 - Add a GETINFO events/names and GETINFO features/names so controllers
28003 can tell which events and features are supported.
28004 - A new CLEARDNSCACHE signal to allow controllers to clear the
28005 client-side DNS cache without expiring circuits.
28007 o Security bugfixes:
28008 - When the user sends a NEWNYM signal, clear the client-side DNS
28009 cache too. Otherwise we continue to act on previous information.
28012 - Avoid sending junk to controllers or segfaulting when a controller
28013 uses EVENT_NEW_DESC with verbose nicknames.
28014 - Stop triggering asserts if the controller tries to extend hidden
28015 service circuits (reported by mwenge).
28016 - Avoid infinite loop on unexpected controller input.
28017 - When the controller does a "GETINFO network-status", tell it
28018 about even those routers whose descriptors are very old, and use
28019 long nicknames where appropriate.
28020 - Change NT service functions to be loaded on demand. This lets us
28021 build with MinGW without breaking Tor for Windows 98 users.
28022 - Do DirPort reachability tests less often, since a single test
28023 chews through many circuits before giving up.
28024 - In the hidden service example in torrc.sample, stop recommending
28025 esoteric and discouraged hidden service options.
28026 - When stopping an NT service, wait up to 10 sec for it to actually
28027 stop. Patch from Matt Edman; resolves bug 295.
28028 - Fix handling of verbose nicknames with ORCONN controller events:
28029 make them show up exactly when requested, rather than exactly when
28031 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
28032 printing a duplicate "$" in the keys we send (reported by mwenge).
28033 - Correctly set maximum connection limit on Cygwin. (This time
28035 - Try to detect Windows correctly when cross-compiling.
28036 - Detect the size of the routers file correctly even if it is
28037 corrupted (on systems without mmap) or not page-aligned (on systems
28038 with mmap). This bug was harmless.
28039 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
28040 to open a stream fails; now we do in more cases. This should
28041 make clients able to find a good exit faster in some cases, since
28042 unhandleable requests will now get an error rather than timing out.
28043 - Resolve two memory leaks when rebuilding the on-disk router cache
28044 (reported by fookoowa).
28045 - Clean up minor code warnings suggested by the MIPSpro C compiler,
28046 and reported by some Centos users.
28047 - Controller signals now work on non-Unix platforms that don't define
28048 SIGUSR1 and SIGUSR2 the way we expect.
28049 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
28050 values before failing, and always enables eventdns.
28051 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
28052 Try to fix this in configure.in by checking for most functions
28053 before we check for libevent.
28056 Changes in version 0.1.2.2-alpha - 2006-10-07
28058 - Make our async eventdns library on-by-default for Tor servers,
28059 and plan to deprecate the separate dnsworker threads.
28060 - Add server-side support for "reverse" DNS lookups (using PTR
28061 records so clients can determine the canonical hostname for a given
28062 IPv4 address). Only supported by servers using eventdns; servers
28063 now announce in their descriptors whether they support eventdns.
28064 - Specify and implement client-side SOCKS5 interface for reverse DNS
28065 lookups (see doc/socks-extensions.txt).
28066 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
28067 connect to directory servers through Tor. Previously, clients needed
28068 to find Tor exits to make private connections to directory servers.
28069 - Avoid choosing Exit nodes for entry or middle hops when the
28070 total bandwidth available from non-Exit nodes is much higher than
28071 the total bandwidth available from Exit nodes.
28072 - Workaround for name servers (like Earthlink's) that hijack failing
28073 DNS requests and replace the no-such-server answer with a "helpful"
28074 redirect to an advertising-driven search portal. Also work around
28075 DNS hijackers who "helpfully" decline to hijack known-invalid
28076 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
28077 lets you turn it off.
28078 - Send out a burst of long-range padding cells once we've established
28079 that we're reachable. Spread them over 4 circuits, so hopefully
28080 a few will be fast. This exercises our bandwidth and bootstraps
28081 us into the directory more quickly.
28083 o New/improved config options:
28084 - Add new config option "ResolvConf" to let the server operator
28085 choose an alternate resolve.conf file when using eventdns.
28086 - Add an "EnforceDistinctSubnets" option to control our "exclude
28087 servers on the same /16" behavior. It's still on by default; this
28088 is mostly for people who want to operate private test networks with
28089 all the machines on the same subnet.
28090 - If one of our entry guards is on the ExcludeNodes list, or the
28091 directory authorities don't think it's a good guard, treat it as
28092 if it were unlisted: stop using it as a guard, and throw it off
28093 the guards list if it stays that way for a long time.
28094 - Allow directory authorities to be marked separately as authorities
28095 for the v1 directory protocol, the v2 directory protocol, and
28096 as hidden service directories, to make it easier to retire old
28097 authorities. V1 authorities should set "HSAuthoritativeDir 1"
28098 to continue being hidden service authorities too.
28099 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
28101 o Minor features, controller:
28102 - Fix CIRC controller events so that controllers can learn the
28103 identity digests of non-Named servers used in circuit paths.
28104 - Let controllers ask for more useful identifiers for servers. Instead
28105 of learning identity digests for un-Named servers and nicknames
28106 for Named servers, the new identifiers include digest, nickname,
28107 and indication of Named status. Off by default; see control-spec.txt
28108 for more information.
28109 - Add a "getinfo address" controller command so it can display Tor's
28110 best guess to the user.
28111 - New controller event to alert the controller when our server
28112 descriptor has changed.
28113 - Give more meaningful errors on controller authentication failure.
28115 o Minor features, other:
28116 - When asked to resolve a hostname, don't use non-exit servers unless
28117 requested to do so. This allows servers with broken DNS to be
28118 useful to the network.
28119 - Divide eventdns log messages into warn and info messages.
28120 - Reserve the nickname "Unnamed" for routers that can't pick
28121 a hostname: any router can call itself Unnamed; directory
28122 authorities will never allocate Unnamed to any particular router;
28123 clients won't believe that any router is the canonical Unnamed.
28124 - Only include function names in log messages for info/debug messages.
28125 For notice/warn/err, the content of the message should be clear on
28126 its own, and printing the function name only confuses users.
28127 - Avoid some false positives during reachability testing: don't try
28128 to test via a server that's on the same /24 as us.
28129 - If we fail to build a circuit to an intended enclave, and it's
28130 not mandatory that we use that enclave, stop wanting it.
28131 - When eventdns is enabled, allow multithreaded builds on NetBSD and
28132 OpenBSD. (We had previously disabled threads on these platforms
28133 because they didn't have working thread-safe resolver functions.)
28135 o Major bugfixes, anonymity/security:
28136 - If a client asked for a server by name, and there's a named server
28137 in our network-status but we don't have its descriptor yet, we
28138 could return an unnamed server instead.
28139 - Fix NetBSD bug that could allow someone to force uninitialized RAM
28140 to be sent to a server's DNS resolver. This only affects NetBSD
28141 and other platforms that do not bounds-check tolower().
28142 - Reject (most) attempts to use Tor circuits with length one. (If
28143 many people start using Tor as a one-hop proxy, exit nodes become
28144 a more attractive target for compromise.)
28145 - Just because your DirPort is open doesn't mean people should be
28146 able to remotely teach you about hidden service descriptors. Now
28147 only accept rendezvous posts if you've got HSAuthoritativeDir set.
28149 o Major bugfixes, other:
28150 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
28151 - When a client asks the server to resolve (not connect to)
28152 an address, and it has a cached answer, give them the cached answer.
28153 Previously, the server would give them no answer at all.
28154 - Allow really slow clients to not hang up five minutes into their
28155 directory downloads (suggested by Adam J. Richter).
28156 - We were building exactly the wrong circuits when we anticipated
28157 hidden service requirements, meaning Tor would have to build all
28158 its circuits on demand.
28159 - Avoid crashing when we mmap a router cache file of size 0.
28160 - When testing reachability of our DirPort, don't launch new
28161 tests when there's already one in progress -- unreachable
28162 servers were stacking up dozens of testing streams.
28164 o Minor bugfixes, correctness:
28165 - If we're a directory mirror and we ask for "all" network status
28166 documents, we would discard status documents from authorities
28167 we don't recognize.
28168 - Avoid a memory corruption bug when creating a hash table for
28170 - Avoid controller-triggered crash when misusing certain commands
28171 from a v0 controller on platforms that do not handle
28172 printf("%s",NULL) gracefully.
28173 - Don't crash when a controller sends a third argument to an
28174 "extendcircuit" request.
28175 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
28176 response; fix error code when "getinfo dir/status/" fails.
28177 - Avoid crash when telling controller stream-status and a stream
28179 - Patch from Adam Langley to fix assert() in eventdns.c.
28180 - Fix a debug log message in eventdns to say "X resolved to Y"
28181 instead of "X resolved to X".
28182 - Make eventdns give strings for DNS errors, not just error numbers.
28183 - Track unreachable entry guards correctly: don't conflate
28184 'unreachable by us right now' with 'listed as down by the directory
28185 authorities'. With the old code, if a guard was unreachable by
28186 us but listed as running, it would clog our guard list forever.
28187 - Behave correctly in case we ever have a network with more than
28188 2GB/s total advertised capacity.
28189 - Make TrackExitHosts case-insensitive, and fix the behavior of
28190 ".suffix" TrackExitHosts items to avoid matching in the middle of
28192 - Finally fix the openssl warnings from newer gccs that believe that
28193 ignoring a return value is okay, but casting a return value and
28194 then ignoring it is a sign of madness.
28195 - Prevent the contrib/exitlist script from printing the same
28196 result more than once.
28197 - Patch from Steve Hildrey: Generate network status correctly on
28198 non-versioning dirservers.
28199 - Don't listen to the X-Your-Address-Is hint if you did the lookup
28200 via Tor; otherwise you'll think you're the exit node's IP address.
28202 o Minor bugfixes, performance:
28203 - Two small performance improvements on parsing descriptors.
28204 - Major performance improvement on inserting descriptors: change
28205 algorithm from O(n^2) to O(n).
28206 - Make the common memory allocation path faster on machines where
28207 malloc(0) returns a pointer.
28208 - Start remembering X-Your-Address-Is directory hints even if you're
28209 a client, so you can become a server more smoothly.
28210 - Avoid duplicate entries on MyFamily line in server descriptor.
28212 o Packaging, features:
28213 - Remove architecture from OS X builds. The official builds are
28214 now universal binaries.
28215 - The Debian package now uses --verify-config when (re)starting,
28216 to distinguish configuration errors from other errors.
28217 - Update RPMs to require libevent 1.1b.
28219 o Packaging, bugfixes:
28220 - Patches so Tor builds with MinGW on Windows.
28221 - Patches so Tor might run on Cygwin again.
28222 - Resume building on non-gcc compilers and ancient gcc. Resume
28223 building with the -O0 compile flag. Resume building cleanly on
28225 - Run correctly on OS X platforms with case-sensitive filesystems.
28226 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
28227 - Add autoconf checks so Tor can build on Solaris x86 again.
28230 - Documented (and renamed) ServerDNSSearchDomains and
28231 ServerDNSResolvConfFile options.
28232 - Be clearer that the *ListenAddress directives can be repeated
28236 Changes in version 0.1.1.24 - 2006-09-29
28238 - Allow really slow clients to not hang up five minutes into their
28239 directory downloads (suggested by Adam J. Richter).
28240 - Fix major performance regression from 0.1.0.x: instead of checking
28241 whether we have enough directory information every time we want to
28242 do something, only check when the directory information has changed.
28243 This should improve client CPU usage by 25-50%.
28244 - Don't crash if, after a server has been running for a while,
28245 it can't resolve its hostname.
28248 - Allow Tor to start when RunAsDaemon is set but no logs are set.
28249 - Don't crash when the controller receives a third argument to an
28250 "extendcircuit" request.
28251 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
28252 response; fix error code when "getinfo dir/status/" fails.
28253 - Fix configure.in to not produce broken configure files with
28254 more recent versions of autoconf. Thanks to Clint for his auto*
28256 - Fix security bug on NetBSD that could allow someone to force
28257 uninitialized RAM to be sent to a server's DNS resolver. This
28258 only affects NetBSD and other platforms that do not bounds-check
28260 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
28261 methods: these are known to be buggy.
28262 - If we're a directory mirror and we ask for "all" network status
28263 documents, we would discard status documents from authorities
28264 we don't recognize.
28267 Changes in version 0.1.2.1-alpha - 2006-08-27
28269 - Add "eventdns" async dns library from Adam Langley, tweaked to
28270 build on OSX and Windows. Only enabled if you pass the
28271 --enable-eventdns argument to configure.
28272 - Allow servers with no hostname or IP address to learn their
28273 IP address by asking the directory authorities. This code only
28274 kicks in when you would normally have exited with a "no address"
28275 error. Nothing's authenticated, so use with care.
28276 - Rather than waiting a fixed amount of time between retrying
28277 application connections, we wait only 5 seconds for the first,
28278 10 seconds for the second, and 15 seconds for each retry after
28279 that. Hopefully this will improve the expected user experience.
28280 - Patch from Tup to add support for transparent AP connections:
28281 this basically bundles the functionality of trans-proxy-tor
28282 into the Tor mainline. Now hosts with compliant pf/netfilter
28283 implementations can redirect TCP connections straight to Tor
28284 without diverting through SOCKS. Needs docs.
28285 - Busy directory servers save lots of memory by spooling server
28286 descriptors, v1 directories, and v2 networkstatus docs to buffers
28287 as needed rather than en masse. Also mmap the cached-routers
28288 files, so we don't need to keep the whole thing in memory too.
28289 - Automatically avoid picking more than one node from the same
28290 /16 network when constructing a circuit.
28291 - Revise and clean up the torrc.sample that we ship with; add
28292 a section for BandwidthRate and BandwidthBurst.
28295 - Split circuit_t into origin_circuit_t and or_circuit_t, and
28296 split connection_t into edge, or, dir, control, and base structs.
28297 These will save quite a bit of memory on busy servers, and they'll
28298 also help us track down bugs in the code and bugs in the spec.
28299 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
28300 or later. Log when we are doing this, so we can diagnose it when
28301 it fails. (Also, recommend libevent 1.1b for kqueue and
28302 win32 methods; deprecate libevent 1.0b harder; make libevent
28303 recommendation system saner.)
28304 - Start being able to build universal binaries on OS X (thanks
28306 - Export the default exit policy via the control port, so controllers
28307 don't need to guess what it is / will be later.
28308 - Add a man page entry for ProtocolWarnings.
28309 - Add TestVia config option to the man page.
28310 - Remove even more protocol-related warnings from Tor server logs,
28311 such as bad TLS handshakes and malformed begin cells.
28312 - Stop fetching descriptors if you're not a dir mirror and you
28313 haven't tried to establish any circuits lately. [This currently
28314 causes some dangerous behavior, because when you start up again
28315 you'll use your ancient server descriptors.]
28316 - New DirPort behavior: if you have your dirport set, you download
28317 descriptors aggressively like a directory mirror, whether or not
28318 your ORPort is set.
28319 - Get rid of the router_retry_connections notion. Now routers
28320 no longer try to rebuild long-term connections to directory
28321 authorities, and directory authorities no longer try to rebuild
28322 long-term connections to all servers. We still don't hang up
28323 connections in these two cases though -- we need to look at it
28324 more carefully to avoid flapping, and we likely need to wait til
28325 0.1.1.x is obsolete.
28326 - Drop compatibility with obsolete Tors that permit create cells
28327 to have the wrong circ_id_type.
28328 - Re-enable per-connection rate limiting. Get rid of the "OP
28329 bandwidth" concept. Lay groundwork for "bandwidth classes" --
28330 separate global buckets that apply depending on what sort of conn
28332 - Start publishing one minute or so after we find our ORPort
28333 to be reachable. This will help reduce the number of descriptors
28334 we have for ourselves floating around, since it's quite likely
28335 other things (e.g. DirPort) will change during that minute too.
28336 - Fork the v1 directory protocol into its own spec document,
28337 and mark dir-spec.txt as the currently correct (v2) spec.
28340 - When we find our DirPort to be reachable, publish a new descriptor
28341 so we'll tell the world (reported by pnx).
28342 - Publish a new descriptor after we hup/reload. This is important
28343 if our config has changed such that we'll want to start advertising
28344 our DirPort now, etc.
28345 - Allow Tor to start when RunAsDaemon is set but no logs are set.
28346 - When we have a state file we cannot parse, tell the user and
28347 move it aside. Now we avoid situations where the user starts
28348 Tor in 1904, Tor writes a state file with that timestamp in it,
28349 the user fixes her clock, and Tor refuses to start.
28350 - Fix configure.in to not produce broken configure files with
28351 more recent versions of autoconf. Thanks to Clint for his auto*
28353 - "tor --verify-config" now exits with -1(255) or 0 depending on
28354 whether the config options are bad or good.
28355 - Resolve bug 321 when using dnsworkers: append a period to every
28356 address we resolve at the exit node, so that we do not accidentally
28357 pick up local addresses, and so that failing searches are retried
28358 in the resolver search domains. (This is already solved for
28359 eventdns.) (This breaks Blossom servers for now.)
28360 - If we are using an exit enclave and we can't connect, e.g. because
28361 its webserver is misconfigured to not listen on localhost, then
28362 back off and try connecting from somewhere else before we fail.
28365 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
28366 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
28367 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
28368 when the IP address is mapped through MapAddress to a hostname.
28369 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
28370 useless IPv6 DNS resolves.
28371 - Patch suggested by Karsten Loesing: respond to SIGNAL command
28372 before we execute the signal, in case the signal shuts us down.
28373 - Clean up AllowInvalidNodes man page entry.
28374 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
28375 - Add more asserts to track down an assert error on a windows Tor
28376 server with connection_add being called with socket == -1.
28377 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
28378 - Fix misleading log messages: an entry guard that is "unlisted",
28379 as well as not known to be "down" (because we've never heard
28380 of it), is not therefore "up".
28381 - Remove code to special-case "-cvs" ending, since it has not
28382 actually mattered since 0.0.9.
28383 - Make our socks5 handling more robust to broken socks clients:
28384 throw out everything waiting on the buffer in between socks
28385 handshake phases, since they can't possibly (so the theory
28386 goes) have predicted what we plan to respond to them.
28389 Changes in version 0.1.1.23 - 2006-07-30
28391 - Fast Tor servers, especially exit nodes, were triggering asserts
28392 due to a bug in handling the list of pending DNS resolves. Some
28393 bugs still remain here; we're hunting them.
28394 - Entry guards could crash clients by sending unexpected input.
28395 - More fixes on reachability testing: if you find yourself reachable,
28396 then don't ever make any client requests (so you stop predicting
28397 circuits), then hup or have your clock jump, then later your IP
28398 changes, you won't think circuits are working, so you won't try to
28399 test reachability, so you won't publish.
28402 - Avoid a crash if the controller does a resetconf firewallports
28403 and then a setconf fascistfirewall=1.
28404 - Avoid an integer underflow when the dir authority decides whether
28405 a router is stable: we might wrongly label it stable, and compute
28406 a slightly wrong median stability, when a descriptor is published
28408 - Fix a place where we might trigger an assert if we can't build our
28409 own server descriptor yet.
28412 Changes in version 0.1.1.22 - 2006-07-05
28414 - Fix a big bug that was causing servers to not find themselves
28415 reachable if they changed IP addresses. Since only 0.1.1.22+
28416 servers can do reachability testing correctly, now we automatically
28417 make sure to test via one of these.
28418 - Fix to allow clients and mirrors to learn directory info from
28419 descriptor downloads that get cut off partway through.
28420 - Directory authorities had a bug in deciding if a newly published
28421 descriptor was novel enough to make everybody want a copy -- a few
28422 servers seem to be publishing new descriptors many times a minute.
28424 - Fix a rare bug that was causing some servers to complain about
28425 "closing wedged cpuworkers" and skip some circuit create requests.
28426 - Make the Exit flag in directory status documents actually work.
28429 Changes in version 0.1.1.21 - 2006-06-10
28430 o Crash and assert fixes from 0.1.1.20:
28431 - Fix a rare crash on Tor servers that have enabled hibernation.
28432 - Fix a seg fault on startup for Tor networks that use only one
28433 directory authority.
28434 - Fix an assert from a race condition that occurs on Tor servers
28435 while exiting, where various threads are trying to log that they're
28436 exiting, and delete the logs, at the same time.
28437 - Make our unit tests pass again on certain obscure platforms.
28440 - Add support for building SUSE RPM packages.
28441 - Speed up initial bootstrapping for clients: if we are making our
28442 first ever connection to any entry guard, then don't mark it down
28444 - When only one Tor server in the network is labelled as a guard,
28445 and we've already picked him, we would cycle endlessly picking him
28446 again, being unhappy about it, etc. Now we specifically exclude
28447 current guards when picking a new guard.
28448 - Servers send create cells more reliably after the TLS connection
28449 is established: we were sometimes forgetting to send half of them
28450 when we had more than one pending.
28451 - If we get a create cell that asks us to extend somewhere, but the
28452 Tor server there doesn't match the expected digest, we now send
28453 a destroy cell back, rather than silently doing nothing.
28454 - Make options->RedirectExit work again.
28455 - Make cookie authentication for the controller work again.
28456 - Stop being picky about unusual characters in the arguments to
28457 mapaddress. It's none of our business.
28458 - Add a new config option "TestVia" that lets you specify preferred
28459 middle hops to use for test circuits. Perhaps this will let me
28460 debug the reachability problems better.
28462 o Log / documentation fixes:
28463 - If we're a server and some peer has a broken TLS certificate, don't
28464 log about it unless ProtocolWarnings is set, i.e., we want to hear
28465 about protocol violations by others.
28466 - Fix spelling of VirtualAddrNetwork in man page.
28467 - Add a better explanation at the top of the autogenerated torrc file
28468 about what happened to our old torrc.
28471 Changes in version 0.1.1.20 - 2006-05-23
28473 - Downgrade a log severity where servers complain that they're
28475 - Avoid a compile warning on FreeBSD.
28476 - Remove string size limit on NEWDESC messages; solve bug 291.
28477 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
28478 more thoroughly when we're running on windows.
28481 Changes in version 0.1.1.19-rc - 2006-05-03
28483 - Regenerate our local descriptor if it's dirty and we try to use
28484 it locally (e.g. if it changes during reachability detection).
28485 - If we setconf our ORPort to 0, we continued to listen on the
28486 old ORPort and receive connections.
28487 - Avoid a second warning about machine/limits.h on Debian
28489 - Be willing to add our own routerinfo into the routerlist.
28490 Now authorities will include themselves in their directories
28491 and network-statuses.
28492 - Stop trying to upload rendezvous descriptors to every
28493 directory authority: only try the v1 authorities.
28494 - Servers no longer complain when they think they're not
28495 registered with the directory authorities. There were too many
28497 - Backport dist-rpm changes so rpms can be built without errors.
28500 - Implement an option, VirtualAddrMask, to set which addresses
28501 get handed out in response to mapaddress requests. This works
28502 around a bug in tsocks where 127.0.0.0/8 is never socksified.
28505 Changes in version 0.1.1.18-rc - 2006-04-10
28507 - Work harder to download live network-statuses from all the
28508 directory authorities we know about. Improve the threshold
28509 decision logic so we're more robust to edge cases.
28510 - When fetching rendezvous descriptors, we were willing to ask
28511 v2 authorities too, which would always return 404.
28514 - Stop listing down or invalid nodes in the v1 directory. This will
28515 reduce its bulk by about 1/3, and reduce load on directory
28517 - When deciding whether a router is Fast or Guard-worthy, consider
28518 his advertised BandwidthRate and not just the BandwidthCapacity.
28519 - No longer ship INSTALL and README files -- they are useless now.
28520 - Force rpmbuild to behave and honor target_cpu.
28521 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
28522 - Start to include translated versions of the tor-doc-*.html
28523 files, along with the screenshots. Still needs more work.
28524 - Start sending back 512 and 451 errors if mapaddress fails,
28525 rather than not sending anything back at all.
28526 - When we fail to bind or listen on an incoming or outgoing
28527 socket, we should close it before failing. otherwise we just
28528 leak it. (thanks to weasel for finding.)
28529 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
28530 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
28531 - Make NoPublish (even though deprecated) work again.
28532 - Fix a minor security flaw where a versioning auth dirserver
28533 could list a recommended version many times in a row to make
28534 clients more convinced that it's recommended.
28535 - Fix crash bug if there are two unregistered servers running
28536 with the same nickname, one of them is down, and you ask for
28537 them by nickname in your EntryNodes or ExitNodes. Also, try
28538 to pick the one that's running rather than an arbitrary one.
28539 - Fix an infinite loop we could hit if we go offline for too long.
28540 - Complain when we hit WSAENOBUFS on recv() or write() too.
28541 Perhaps this will help us hunt the bug.
28542 - If you're not a versioning dirserver, don't put the string
28543 "client-versions \nserver-versions \n" in your network-status.
28544 - Lower the minimum required number of file descriptors to 1000,
28545 so we can have some overhead for Valgrind on Linux, where the
28546 default ulimit -n is 1024.
28549 - Add tor.dizum.com as the fifth authoritative directory server.
28550 - Add a new config option FetchUselessDescriptors, off by default,
28551 for when you plan to run "exitlist" on your client and you want
28552 to know about even the non-running descriptors.
28555 Changes in version 0.1.1.17-rc - 2006-03-28
28557 - Clients and servers since 0.1.1.10-alpha have been expiring
28558 connections whenever they are idle for 5 minutes and they *do*
28559 have circuits on them. Oops. With this new version, clients will
28560 discard their previous entry guard choices and avoid choosing
28561 entry guards running these flawed versions.
28562 - Fix memory leak when uncompressing concatenated zlib streams. This
28563 was causing substantial leaks over time on Tor servers.
28564 - The v1 directory was including servers as much as 48 hours old,
28565 because that's how the new routerlist->routers works. Now only
28566 include them if they're 20 hours old or less.
28569 - Resume building on irix64, netbsd 2.0, etc.
28570 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
28572 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
28573 and it is confusing some users.
28574 - Mirrors stop caching the v1 directory so often.
28575 - Make the max number of old descriptors that a cache will hold
28576 rise with the number of directory authorities, so we can scale.
28577 - Change our win32 uname() hack to be more forgiving about what
28578 win32 versions it thinks it's found.
28581 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
28583 - When the controller's *setconf commands fail, collect an error
28584 message in a string and hand it back to the controller.
28585 - Make the v2 dir's "Fast" flag based on relative capacity, just
28586 like "Stable" is based on median uptime. Name everything in the
28587 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
28588 - Log server fingerprint on startup, so new server operators don't
28589 have to go hunting around their filesystem for it.
28590 - Return a robots.txt on our dirport to discourage google indexing.
28591 - Let the controller ask for GETINFO dir/status/foo so it can ask
28592 directly rather than connecting to the dir port. Only works when
28593 dirport is set for now.
28595 o New config options rather than constants in the code:
28596 - SocksTimeout: How long do we let a socks connection wait
28597 unattached before we fail it?
28598 - CircuitBuildTimeout: Cull non-open circuits that were born
28599 at least this many seconds ago.
28600 - CircuitIdleTimeout: Cull open clean circuits that were born
28601 at least this many seconds ago.
28604 Changes in version 0.1.1.16-rc - 2006-03-18
28605 o Bugfixes on 0.1.1.15-rc:
28606 - Fix assert when the controller asks to attachstream a connect-wait
28607 or resolve-wait stream.
28608 - Now do address rewriting when the controller asks us to attach
28609 to a particular circuit too. This will let Blossom specify
28610 "moria2.exit" without having to learn what moria2's IP address is.
28611 - Make the "tor --verify-config" command-line work again, so people
28612 can automatically check if their torrc will parse.
28613 - Authoritative dirservers no longer require an open connection from
28614 a server to consider him "reachable". We need this change because
28615 when we add new auth dirservers, old servers won't know not to
28617 - Let Tor build on Sun CC again.
28618 - Fix an off-by-one buffer size in dirserv.c that magically never
28619 hit our three authorities but broke sjmurdoch's own tor network.
28620 - If we as a directory mirror don't know of any v1 directory
28621 authorities, then don't try to cache any v1 directories.
28622 - Stop warning about unknown servers in our family when they are
28623 given as hex digests.
28624 - Stop complaining as quickly to the server operator that he
28625 hasn't registered his nickname/key binding.
28626 - Various cleanups so we can add new V2 Auth Dirservers.
28627 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
28628 reflect the updated flags in our v2 dir protocol.
28629 - Resume allowing non-printable characters for exit streams (both
28630 for connecting and for resolving). Now we tolerate applications
28631 that don't follow the RFCs. But continue to block malformed names
28634 o Bugfixes on 0.1.0.x:
28635 - Fix assert bug in close_logs(): when we close and delete logs,
28636 remove them all from the global "logfiles" list.
28637 - Fix minor integer overflow in calculating when we expect to use up
28638 our bandwidth allocation before hibernating.
28639 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
28640 there are multiple SSLs installed with different versions.
28641 - When we try to be a server and Address is not explicitly set and
28642 our hostname resolves to a private IP address, try to use an
28643 interface address if it has a public address. Now Windows machines
28644 that think of themselves as localhost can work by default.
28647 - Let the controller ask for GETINFO dir/server/foo so it can ask
28648 directly rather than connecting to the dir port.
28649 - Let the controller tell us about certain router descriptors
28650 that it doesn't want Tor to use in circuits. Implement
28651 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
28652 - New config option SafeSocks to reject all application connections
28653 using unsafe socks protocols. Defaults to off.
28656 Changes in version 0.1.1.15-rc - 2006-03-11
28657 o Bugfixes and cleanups:
28658 - When we're printing strings from the network, don't try to print
28659 non-printable characters. This protects us against shell escape
28660 sequence exploits, and also against attacks to fool humans into
28661 misreading their logs.
28662 - Fix a bug where Tor would fail to establish any connections if you
28663 left it off for 24 hours and then started it: we were happy with
28664 the obsolete network statuses, but they all referred to router
28665 descriptors that were too old to fetch, so we ended up with no
28666 valid router descriptors.
28667 - Fix a seg fault in the controller's "getinfo orconn-status"
28668 command while listing status on incoming handshaking connections.
28669 Introduce a status name "NEW" for these connections.
28670 - If we get a linelist or linelist_s config option from the torrc
28671 (e.g. ExitPolicy) and it has no value, warn and skip rather than
28672 silently resetting it to its default.
28673 - Don't abandon entry guards until they've been down or gone for
28675 - Cleaner and quieter log messages.
28678 - New controller signal NEWNYM that makes new application requests
28679 use clean circuits.
28680 - Add a new circuit purpose 'controller' to let the controller ask
28681 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
28682 controller command to let you specify the purpose if you're
28683 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
28684 command to let you change a circuit's purpose after it's been
28686 - Accept "private:*" in routerdesc exit policies; not generated yet
28687 because older Tors do not understand it.
28688 - Add BSD-style contributed startup script "rc.subr" from Peter
28692 Changes in version 0.1.1.14-alpha - 2006-02-20
28693 o Bugfixes on 0.1.1.x:
28694 - Don't die if we ask for a stdout or stderr log (even implicitly)
28695 and we're set to RunAsDaemon -- just warn.
28696 - We still had a few bugs in the OR connection rotation code that
28697 caused directory servers to slowly aggregate connections to other
28698 fast Tor servers. This time for sure!
28699 - Make log entries on Win32 include the name of the function again.
28700 - We were treating a pair of exit policies if they were equal even
28701 if one said accept and the other said reject -- causing us to
28702 not always publish a new descriptor since we thought nothing
28704 - Retry pending server downloads as well as pending networkstatus
28705 downloads when we unexpectedly get a socks request.
28706 - We were ignoring the IS_FAST flag in the directory status,
28707 meaning we were willing to pick trivial-bandwidth nodes for "fast"
28709 - If the controller's SAVECONF command fails (e.g. due to file
28710 permissions), let the controller know that it failed.
28713 - If we're trying to be a Tor server and running Windows 95/98/ME
28714 as a server, explain that we'll likely crash.
28715 - When we're a server, a client asks for an old-style directory,
28716 and our write bucket is empty, don't give it to him. This way
28717 small servers can continue to serve the directory *sometimes*,
28718 without getting overloaded.
28719 - Compress exit policies even more -- look for duplicate lines
28721 - Clients now honor the "guard" flag in the router status when
28722 picking entry guards, rather than looking at is_fast or is_stable.
28723 - Retain unrecognized lines in $DATADIR/state file, so that we can
28724 be forward-compatible.
28725 - Generate 18.0.0.0/8 address policy format in descs when we can;
28726 warn when the mask is not reducible to a bit-prefix.
28727 - Let the user set ControlListenAddress in the torrc. This can be
28728 dangerous, but there are some cases (like a secured LAN) where it
28730 - Split ReachableAddresses into ReachableDirAddresses and
28731 ReachableORAddresses, so we can restrict Dir conns to port 80
28732 and OR conns to port 443.
28733 - Now we can target arch and OS in rpm builds (contributed by
28734 Phobos). Also make the resulting dist-rpm filename match the
28736 - New config options to help controllers: FetchServerDescriptors
28737 and FetchHidServDescriptors for whether to fetch server
28738 info and hidserv info or let the controller do it, and
28739 PublishServerDescriptor and PublishHidServDescriptors.
28740 - Also let the controller set the __AllDirActionsPrivate config
28741 option if you want all directory fetches/publishes to happen via
28742 Tor (it assumes your controller bootstraps your circuits).
28745 Changes in version 0.1.0.17 - 2006-02-17
28746 o Crash bugfixes on 0.1.0.x:
28747 - When servers with a non-zero DirPort came out of hibernation,
28748 sometimes they would trigger an assert.
28750 o Other important bugfixes:
28751 - On platforms that don't have getrlimit (like Windows), we were
28752 artificially constraining ourselves to a max of 1024
28753 connections. Now just assume that we can handle as many as 15000
28754 connections. Hopefully this won't cause other problems.
28756 o Backported features:
28757 - When we're a server, a client asks for an old-style directory,
28758 and our write bucket is empty, don't give it to him. This way
28759 small servers can continue to serve the directory *sometimes*,
28760 without getting overloaded.
28761 - Whenever you get a 503 in response to a directory fetch, try
28762 once more. This will become important once servers start sending
28763 503's whenever they feel busy.
28764 - Fetch a new directory every 120 minutes, not every 40 minutes.
28765 Now that we have hundreds of thousands of users running the old
28766 directory algorithm, it's starting to hurt a lot.
28767 - Bump up the period for forcing a hidden service descriptor upload
28768 from 20 minutes to 1 hour.
28771 Changes in version 0.1.1.13-alpha - 2006-02-09
28772 o Crashes in 0.1.1.x:
28773 - When you tried to setconf ORPort via the controller, Tor would
28774 crash. So people using TorCP to become a server were sad.
28775 - Solve (I hope) the stack-smashing bug that we were seeing on fast
28776 servers. The problem appears to be something do with OpenSSL's
28777 random number generation, or how we call it, or something. Let me
28778 know if the crashes continue.
28779 - Turn crypto hardware acceleration off by default, until we find
28780 somebody smart who can test it for us. (It appears to produce
28781 seg faults in at least some cases.)
28782 - Fix a rare assert error when we've tried all intro points for
28783 a hidden service and we try fetching the service descriptor again:
28784 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
28787 - Fix a major load balance bug: we were round-robining in 16 KB
28788 chunks, and servers with bandwidthrate of 20 KB, while downloading
28789 a 600 KB directory, would starve their other connections. Now we
28790 try to be a bit more fair.
28791 - Dir authorities and mirrors were never expiring the newest
28792 descriptor for each server, causing memory and directory bloat.
28793 - Fix memory-bloating and connection-bloating bug on servers: We
28794 were never closing any connection that had ever had a circuit on
28795 it, because we were checking conn->n_circuits == 0, yet we had a
28796 bug that let it go negative.
28797 - Make Tor work using squid as your http proxy again -- squid
28798 returns an error if you ask for a URL that's too long, and it uses
28799 a really generic error message. Plus, many people are behind a
28800 transparent squid so they don't even realize it.
28801 - On platforms that don't have getrlimit (like Windows), we were
28802 artificially constraining ourselves to a max of 1024
28803 connections. Now just assume that we can handle as many as 15000
28804 connections. Hopefully this won't cause other problems.
28805 - Add a new config option ExitPolicyRejectPrivate which defaults to
28806 1. This means all exit policies will begin with rejecting private
28807 addresses, unless the server operator explicitly turns it off.
28810 - Clients no longer download descriptors for non-running
28812 - Before we add new directory authorities, we should make it
28813 clear that only v1 authorities should receive/publish hidden
28814 service descriptors.
28817 - As soon as we've fetched some more directory info, immediately
28818 try to download more server descriptors. This way we don't have
28819 a 10 second pause during initial bootstrapping.
28820 - Remove even more loud log messages that the server operator can't
28822 - When we're running an obsolete or un-recommended version, make
28823 the log message more clear about what the problem is and what
28824 versions *are* still recommended.
28825 - Provide a more useful warn message when our onion queue gets full:
28826 the CPU is too slow or the exit policy is too liberal.
28827 - Don't warn when we receive a 503 from a dirserver/cache -- this
28828 will pave the way for them being able to refuse if they're busy.
28829 - When we fail to bind a listener, try to provide a more useful
28830 log message: e.g., "Is Tor already running?"
28831 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
28832 Goldberg can prove things about our handshake protocol more
28834 - MaxConn has been obsolete for a while now. Document the ConnLimit
28835 config option, which is a *minimum* number of file descriptors
28836 that must be available else Tor refuses to start.
28837 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
28838 if you log to syslog and want something other than LOG_DAEMON.
28839 - Make dirservers generate a separate "guard" flag to mean,
28840 "would make a good entry guard". Make clients parse it and vote
28841 on it. Not used by clients yet.
28842 - Implement --with-libevent-dir option to ./configure. Also, improve
28843 search techniques to find libevent, and use those for openssl too.
28844 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
28845 - Only start testing reachability once we've established a
28846 circuit. This will make startup on dirservers less noisy.
28847 - Don't try to upload hidden service descriptors until we have
28848 established a circuit.
28849 - Fix the controller's "attachstream 0" command to treat conn like
28850 it just connected, doing address remapping, handling .exit and
28851 .onion idioms, and so on. Now we're more uniform in making sure
28852 that the controller hears about new and closing connections.
28855 Changes in version 0.1.1.12-alpha - 2006-01-11
28856 o Bugfixes on 0.1.1.x:
28857 - The fix to close duplicate server connections was closing all
28858 Tor client connections if they didn't establish a circuit
28859 quickly enough. Oops.
28860 - Fix minor memory issue (double-free) that happened on exit.
28862 o Bugfixes on 0.1.0.x:
28863 - Tor didn't warn when it failed to open a log file.
28866 Changes in version 0.1.1.11-alpha - 2006-01-10
28867 o Crashes in 0.1.1.x:
28868 - Include all the assert/crash fixes from 0.1.0.16.
28869 - If you start Tor and then quit very quickly, there were some
28870 races that tried to free things that weren't allocated yet.
28871 - Fix a rare memory stomp if you're running hidden services.
28872 - Fix segfault when specifying DirServer in config without nickname.
28873 - Fix a seg fault when you finish connecting to a server but at
28874 that moment you dump his server descriptor.
28875 - Extendcircuit and Attachstream controller commands would
28876 assert/crash if you don't give them enough arguments.
28877 - Fix an assert error when we're out of space in the connection_list
28878 and we try to post a hidden service descriptor (reported by weasel).
28879 - If you specify a relative torrc path and you set RunAsDaemon in
28880 your torrc, then it chdir()'s to the new directory. If you HUP,
28881 it tries to load the new torrc location, fails, and exits.
28882 The fix: no longer allow a relative path to torrc using -f.
28885 - Implement "entry guards": automatically choose a handful of entry
28886 nodes and stick with them for all circuits. Only pick new guards
28887 when the ones you have are unsuitable, and if the old guards
28888 become suitable again, switch back. This will increase security
28889 dramatically against certain end-point attacks. The EntryNodes
28890 config option now provides some hints about which entry guards you
28891 want to use most; and StrictEntryNodes means to only use those.
28892 - New directory logic: download by descriptor digest, not by
28893 fingerprint. Caches try to download all listed digests from
28894 authorities; clients try to download "best" digests from caches.
28895 This avoids partitioning and isolating attacks better.
28896 - Make the "stable" router flag in network-status be the median of
28897 the uptimes of running valid servers, and make clients pay
28898 attention to the network-status flags. Thus the cutoff adapts
28899 to the stability of the network as a whole, making IRC, IM, etc
28900 connections more reliable.
28903 - Tor servers with dynamic IP addresses were needing to wait 18
28904 hours before they could start doing reachability testing using
28905 the new IP address and ports. This is because they were using
28906 the internal descriptor to learn what to test, yet they were only
28907 rebuilding the descriptor once they decided they were reachable.
28908 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
28909 to download certain server descriptors, throw them away, and then
28910 fetch them again after 30 minutes. Now mirrors throw away these
28911 server descriptors so clients can't get them.
28912 - We were leaving duplicate connections to other ORs open for a week,
28913 rather than closing them once we detect a duplicate. This only
28914 really affected authdirservers, but it affected them a lot.
28915 - Spread the authdirservers' reachability testing over the entire
28916 testing interval, so we don't try to do 500 TLS's at once every
28920 - If the network is down, and we try to connect to a conn because
28921 we have a circuit in mind, and we timeout (30 seconds) because the
28922 network never answers, we were expiring the circuit, but we weren't
28923 obsoleting the connection or telling the entry_guards functions.
28924 - Some Tor servers process billions of cells per day. These statistics
28925 need to be uint64_t's.
28926 - Check for integer overflows in more places, when adding elements
28927 to smartlists. This could possibly prevent a buffer overflow
28928 on malicious huge inputs. I don't see any, but I haven't looked
28930 - ReachableAddresses kept growing new "reject *:*" lines on every
28932 - When you "setconf log" via the controller, it should remove all
28933 logs. We were automatically adding back in a "log notice stdout".
28934 - Newly bootstrapped Tor networks couldn't establish hidden service
28935 circuits until they had nodes with high uptime. Be more tolerant.
28936 - We were marking servers down when they could not answer every piece
28937 of the directory request we sent them. This was far too harsh.
28938 - Fix the torify (tsocks) config file to not use Tor for localhost
28940 - Directory authorities now go to the proper authority when asking for
28941 a networkstatus, even when they want a compressed one.
28942 - Fix a harmless bug that was causing Tor servers to log
28943 "Got an end because of misc error, but we're not an AP. Closing."
28944 - Authorities were treating their own descriptor changes as cosmetic,
28945 meaning the descriptor available in the network-status and the
28946 descriptor that clients downloaded were different.
28947 - The OS X installer was adding a symlink for tor_resolve but
28948 the binary was called tor-resolve (reported by Thomas Hardly).
28949 - Workaround a problem with some http proxies where they refuse GET
28950 requests that specify "Content-Length: 0" (reported by Adrian).
28951 - Fix wrong log message when you add a "HiddenServiceNodes" config
28952 line without any HiddenServiceDir line (reported by Chris Thomas).
28955 - Write the TorVersion into the state file so we have a prayer of
28956 keeping forward and backward compatibility.
28957 - Revive the FascistFirewall config option rather than eliminating it:
28958 now it's a synonym for ReachableAddresses *:80,*:443.
28959 - Clients choose directory servers from the network status lists,
28960 not from their internal list of router descriptors. Now they can
28961 go to caches directly rather than needing to go to authorities
28963 - Directory authorities ignore router descriptors that have only
28964 cosmetic differences: do this for 0.1.0.x servers now too.
28965 - Add a new flag to network-status indicating whether the server
28966 can answer v2 directory requests too.
28967 - Authdirs now stop whining so loudly about bad descriptors that
28968 they fetch from other dirservers. So when there's a log complaint,
28969 it's for sure from a freshly uploaded descriptor.
28970 - Reduce memory requirements in our structs by changing the order
28972 - There used to be two ways to specify your listening ports in a
28973 server descriptor: on the "router" line and with a separate "ports"
28974 line. Remove support for the "ports" line.
28975 - New config option "AuthDirRejectUnlisted" for auth dirservers as
28976 a panic button: if we get flooded with unusable servers we can
28977 revert to only listing servers in the approved-routers file.
28978 - Auth dir servers can now mark a fingerprint as "!reject" or
28979 "!invalid" in the approved-routers file (as its nickname), to
28980 refuse descriptors outright or include them but marked as invalid.
28981 - Servers store bandwidth history across restarts/crashes.
28982 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
28983 get a better idea of why their circuits failed. Not used yet.
28984 - Directory mirrors now cache up to 16 unrecognized network-status
28985 docs. Now we can add new authdirservers and they'll be cached too.
28986 - When picking a random directory, prefer non-authorities if any
28988 - New controller option "getinfo desc/all-recent" to fetch the
28989 latest server descriptor for every router that Tor knows about.
28992 Changes in version 0.1.0.16 - 2006-01-02
28993 o Crash bugfixes on 0.1.0.x:
28994 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
28995 corrupting the heap, losing FDs, or crashing when we need to resize
28996 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
28997 - It turns out sparc64 platforms crash on unaligned memory access
28998 too -- so detect and avoid this.
28999 - Handle truncated compressed data correctly (by detecting it and
29001 - Fix possible-but-unlikely free(NULL) in control.c.
29002 - When we were closing connections, there was a rare case that
29003 stomped on memory, triggering seg faults and asserts.
29004 - Avoid potential infinite recursion when building a descriptor. (We
29005 don't know that it ever happened, but better to fix it anyway.)
29006 - We were neglecting to unlink marked circuits from soon-to-close OR
29007 connections, which caused some rare scribbling on freed memory.
29008 - Fix a memory stomping race bug when closing the joining point of two
29009 rendezvous circuits.
29010 - Fix an assert in time parsing found by Steven Murdoch.
29012 o Other bugfixes on 0.1.0.x:
29013 - When we're doing reachability testing, provide more useful log
29014 messages so the operator knows what to expect.
29015 - Do not check whether DirPort is reachable when we are suppressing
29016 advertising it because of hibernation.
29017 - When building with -static or on Solaris, we sometimes needed -ldl.
29018 - When we're deciding whether a stream has enough circuits around
29019 that can handle it, count the freshly dirty ones and not the ones
29020 that are so dirty they won't be able to handle it.
29021 - When we're expiring old circuits, we had a logic error that caused
29022 us to close new rendezvous circuits rather than old ones.
29023 - Give a more helpful log message when you try to change ORPort via
29024 the controller: you should upgrade Tor if you want that to work.
29025 - We were failing to parse Tor versions that start with "Tor ".
29026 - Tolerate faulty streams better: when a stream fails for reason
29027 exitpolicy, stop assuming that the router is lying about his exit
29028 policy. When a stream fails for reason misc, allow it to retry just
29029 as if it was resolvefailed. When a stream has failed three times,
29030 reset its failure count so we can try again and get all three tries.
29033 Changes in version 0.1.1.10-alpha - 2005-12-11
29034 o Correctness bugfixes on 0.1.0.x:
29035 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29036 corrupting the heap, losing FDs, or crashing when we need to resize
29037 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29038 - Stop doing the complex voodoo overkill checking for insecure
29039 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
29040 - When we were closing connections, there was a rare case that
29041 stomped on memory, triggering seg faults and asserts.
29042 - We were neglecting to unlink marked circuits from soon-to-close OR
29043 connections, which caused some rare scribbling on freed memory.
29044 - When we're deciding whether a stream has enough circuits around
29045 that can handle it, count the freshly dirty ones and not the ones
29046 that are so dirty they won't be able to handle it.
29047 - Recover better from TCP connections to Tor servers that are
29048 broken but don't tell you (it happens!); and rotate TLS
29049 connections once a week.
29050 - When we're expiring old circuits, we had a logic error that caused
29051 us to close new rendezvous circuits rather than old ones.
29052 - Fix a scary-looking but apparently harmless bug where circuits
29053 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
29054 servers, and never switch to state CIRCUIT_STATE_OPEN.
29055 - When building with -static or on Solaris, we sometimes needed to
29057 - Give a useful message when people run Tor as the wrong user,
29058 rather than telling them to start chowning random directories.
29059 - We were failing to inform the controller about new .onion streams.
29061 o Security bugfixes on 0.1.0.x:
29062 - Refuse server descriptors if the fingerprint line doesn't match
29063 the included identity key. Tor doesn't care, but other apps (and
29064 humans) might actually be trusting the fingerprint line.
29065 - We used to kill the circuit when we receive a relay command we
29066 don't recognize. Now we just drop it.
29067 - Start obeying our firewall options more rigorously:
29068 . If we can't get to a dirserver directly, try going via Tor.
29069 . Don't ever try to connect (as a client) to a place our
29070 firewall options forbid.
29071 . If we specify a proxy and also firewall options, obey the
29072 firewall options even when we're using the proxy: some proxies
29073 can only proxy to certain destinations.
29074 - Fix a bug found by Lasse Overlier: when we were making internal
29075 circuits (intended to be cannibalized later for rendezvous and
29076 introduction circuits), we were picking them so that they had
29077 useful exit nodes. There was no need for this, and it actually
29078 aids some statistical attacks.
29079 - Start treating internal circuits and exit circuits separately.
29080 It's important to keep them separate because internal circuits
29081 have their last hops picked like middle hops, rather than like
29082 exit hops. So exiting on them will break the user's expectations.
29084 o Bugfixes on 0.1.1.x:
29085 - Take out the mis-feature where we tried to detect IP address
29086 flapping for people with DynDNS, and chose not to upload a new
29087 server descriptor sometimes.
29088 - Try to be compatible with OpenSSL 0.9.6 again.
29089 - Log fix: when the controller is logging about .onion addresses,
29090 sometimes it didn't include the ".onion" part of the address.
29091 - Don't try to modify options->DirServers internally -- if the
29092 user didn't specify any, just add the default ones directly to
29093 the trusted dirserver list. This fixes a bug where people running
29094 controllers would use SETCONF on some totally unrelated config
29095 option, and Tor would start yelling at them about changing their
29097 - Let the controller's redirectstream command specify a port, in
29098 case the controller wants to change that too.
29099 - When we requested a pile of server descriptors, we sometimes
29100 accidentally launched a duplicate request for the first one.
29101 - Bugfix for trackhostexits: write down the fingerprint of the
29102 chosen exit, not its nickname, because the chosen exit might not
29104 - When parsing foo.exit, if foo is unknown, and we are leaving
29105 circuits unattached, set the chosen_exit field and leave the
29106 address empty. This matters because controllers got confused
29108 - Directory authorities no longer try to download server
29109 descriptors that they know they will reject.
29111 o Features and updates:
29112 - Replace balanced trees with hash tables: this should make stuff
29113 significantly faster.
29114 - Resume using the AES counter-mode implementation that we ship,
29115 rather than OpenSSL's. Ours is significantly faster.
29116 - Many other CPU and memory improvements.
29117 - Add a new config option FastFirstHopPK (on by default) so clients
29118 do a trivial crypto handshake for their first hop, since TLS has
29119 already taken care of confidentiality and authentication.
29120 - Add a new config option TestSocks so people can see if their
29121 applications are using socks4, socks4a, socks5-with-ip, or
29122 socks5-with-hostname. This way they don't have to keep mucking
29123 with tcpdump and wondering if something got cached somewhere.
29124 - Warn when listening on a public address for socks. I suspect a
29125 lot of people are setting themselves up as open socks proxies,
29126 and they have no idea that jerks on the Internet are using them,
29127 since they simply proxy the traffic into the Tor network.
29128 - Add "private:*" as an alias in configuration for policies. Now
29129 you can simplify your exit policy rather than needing to list
29130 every single internal or nonroutable network space.
29131 - Add a new controller event type that allows controllers to get
29132 all server descriptors that were uploaded to a router in its role
29133 as authoritative dirserver.
29134 - Start shipping socks-extensions.txt, tor-doc-unix.html,
29135 tor-doc-server.html, and stylesheet.css in the tarball.
29136 - Stop shipping tor-doc.html in the tarball.
29139 Changes in version 0.1.1.9-alpha - 2005-11-15
29140 o Usability improvements:
29141 - Start calling it FooListenAddress rather than FooBindAddress,
29142 since few of our users know what it means to bind an address
29144 - Reduce clutter in server logs. We're going to try to make
29145 them actually usable now. New config option ProtocolWarnings that
29146 lets you hear about how _other Tors_ are breaking the protocol. Off
29148 - Divide log messages into logging domains. Once we put some sort
29149 of interface on this, it will let people looking at more verbose
29150 log levels specify the topics they want to hear more about.
29151 - Make directory servers return better http 404 error messages
29152 instead of a generic "Servers unavailable".
29153 - Check for even more Windows version flags when writing the platform
29154 string in server descriptors, and note any we don't recognize.
29155 - Clean up more of the OpenSSL memory when exiting, so we can detect
29156 memory leaks better.
29157 - Make directory authorities be non-versioning, non-naming by
29158 default. Now we can add new directory servers without requiring
29159 their operators to pay close attention.
29160 - When logging via syslog, include the pid whenever we provide
29161 a log entry. Suggested by Todd Fries.
29163 o Performance improvements:
29164 - Directory servers now silently throw away new descriptors that
29165 haven't changed much if the timestamps are similar. We do this to
29166 tolerate older Tor servers that upload a new descriptor every 15
29167 minutes. (It seemed like a good idea at the time.)
29168 - Inline bottleneck smartlist functions; use fast versions by default.
29169 - Add a "Map from digest to void*" abstraction digestmap_t so we
29170 can do less hex encoding/decoding. Use it in router_get_by_digest()
29171 to resolve a performance bottleneck.
29172 - Allow tor_gzip_uncompress to extract as much as possible from
29173 truncated compressed data. Try to extract as many
29174 descriptors as possible from truncated http responses (when
29175 DIR_PURPOSE_FETCH_ROUTERDESC).
29176 - Make circ->onionskin a pointer, not a static array. moria2 was using
29177 125000 circuit_t's after it had been up for a few weeks, which
29178 translates to 20+ megs of wasted space.
29179 - The private half of our EDH handshake keys are now chosen out
29180 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
29182 o Security improvements:
29183 - Start making directory caches retain old routerinfos, so soon
29184 clients can start asking by digest of descriptor rather than by
29185 fingerprint of server.
29186 - Add half our entropy from RAND_poll in OpenSSL. This knows how
29187 to use egd (if present), openbsd weirdness (if present), vms/os2
29188 weirdness (if we ever port there), and more in the future.
29190 o Bugfixes on 0.1.0.x:
29191 - Do round-robin writes of at most 16 kB per write. This might be
29192 more fair on loaded Tor servers, and it might resolve our Windows
29193 crash bug. It might also slow things down.
29194 - Our TLS handshakes were generating a single public/private
29195 keypair for the TLS context, rather than making a new one for
29196 each new connections. Oops. (But we were still rotating them
29197 periodically, so it's not so bad.)
29198 - When we were cannibalizing a circuit with a particular exit
29199 node in mind, we weren't checking to see if that exit node was
29200 already present earlier in the circuit. Oops.
29201 - When a Tor server's IP changes (e.g. from a dyndns address),
29202 upload a new descriptor so clients will learn too.
29203 - Really busy servers were keeping enough circuits open on stable
29204 connections that they were wrapping around the circuit_id
29205 space. (It's only two bytes.) This exposed a bug where we would
29206 feel free to reuse a circuit_id even if it still exists but has
29207 been marked for close. Try to fix this bug. Some bug remains.
29208 - If we would close a stream early (e.g. it asks for a .exit that
29209 we know would refuse it) but the LeaveStreamsUnattached config
29210 option is set by the controller, then don't close it.
29212 o Bugfixes on 0.1.1.8-alpha:
29213 - Fix a big pile of memory leaks, some of them serious.
29214 - Do not try to download a routerdesc if we would immediately reject
29216 - Resume inserting a newline between all router descriptors when
29217 generating (old style) signed directories, since our spec says
29219 - When providing content-type application/octet-stream for
29220 server descriptors using .z, we were leaving out the
29221 content-encoding header. Oops. (Everything tolerated this just
29222 fine, but that doesn't mean we need to be part of the problem.)
29223 - Fix a potential seg fault in getconf and getinfo using version 1
29224 of the controller protocol.
29225 - Avoid crash: do not check whether DirPort is reachable when we
29226 are suppressing it because of hibernation.
29227 - Make --hash-password not crash on exit.
29230 Changes in version 0.1.1.8-alpha - 2005-10-07
29231 o New features (major):
29232 - Clients don't download or use the directory anymore. Now they
29233 download and use network-statuses from the trusted dirservers,
29234 and fetch individual server descriptors as needed from mirrors.
29235 See dir-spec.txt for all the gory details.
29236 - Be more conservative about whether to advertise our DirPort.
29237 The main change is to not advertise if we're running at capacity
29238 and either a) we could hibernate or b) our capacity is low and
29239 we're using a default DirPort.
29240 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
29242 o New features (minor):
29243 - Try to be smart about when to retry network-status and
29244 server-descriptor fetches. Still needs some tuning.
29245 - Stop parsing, storing, or using running-routers output (but
29246 mirrors still cache and serve it).
29247 - Consider a threshold of versioning dirservers (dirservers who have
29248 an opinion about which Tor versions are still recommended) before
29249 deciding whether to warn the user that he's obsolete.
29250 - Dirservers can now reject/invalidate by key and IP, with the
29251 config options "AuthDirInvalid" and "AuthDirReject". This is
29252 useful since currently we automatically list servers as running
29253 and usable even if we know they're jerks.
29254 - Provide dire warnings to any users who set DirServer; move it out
29255 of torrc.sample and into torrc.complete.
29256 - Add MyFamily to torrc.sample in the server section.
29257 - Add nicknames to the DirServer line, so we can refer to them
29258 without requiring all our users to memorize their IP addresses.
29259 - When we get an EOF or a timeout on a directory connection, note
29260 how many bytes of serverdesc we are dropping. This will help
29261 us determine whether it is smart to parse incomplete serverdesc
29263 - Add a new function to "change pseudonyms" -- that is, to stop
29264 using any currently-dirty circuits for new streams, so we don't
29265 link new actions to old actions. Currently it's only called on
29266 HUP (or SIGNAL RELOAD).
29267 - On sighup, if UseHelperNodes changed to 1, use new circuits.
29268 - Start using RAND_bytes rather than RAND_pseudo_bytes from
29269 OpenSSL. Also, reseed our entropy every hour, not just at
29270 startup. And entropy in 512-bit chunks, not 160-bit chunks.
29272 o Fixes on 0.1.1.7-alpha:
29273 - Nobody ever implemented EVENT_ADDRMAP for control protocol
29274 version 0, so don't let version 0 controllers ask for it.
29275 - If you requested something with too many newlines via the
29276 v1 controller protocol, you could crash tor.
29277 - Fix a number of memory leaks, including some pretty serious ones.
29278 - Re-enable DirPort testing again, so Tor servers will be willing
29279 to advertise their DirPort if it's reachable.
29280 - On TLS handshake, only check the other router's nickname against
29281 its expected nickname if is_named is set.
29283 o Fixes forward-ported from 0.1.0.15:
29284 - Don't crash when we don't have any spare file descriptors and we
29285 try to spawn a dns or cpu worker.
29286 - Make the numbers in read-history and write-history into uint64s,
29287 so they don't overflow and publish negatives in the descriptor.
29289 o Fixes on 0.1.0.x:
29290 - For the OS X package's modified privoxy config file, comment
29291 out the "logfile" line so we don't log everything passed
29293 - We were whining about using socks4 or socks5-with-local-lookup
29294 even when it's an IP in the "virtual" range we designed exactly
29296 - We were leaking some memory every time the client changes IPs.
29297 - Never call free() on tor_malloc()d memory. This will help us
29298 use dmalloc to detect memory leaks.
29299 - Check for named servers when looking them up by nickname;
29300 warn when we'recalling a non-named server by its nickname;
29301 don't warn twice about the same name.
29302 - Try to list MyFamily elements by key, not by nickname, and warn
29303 if we've not heard of the server.
29304 - Make windows platform detection (uname equivalent) smarter.
29305 - It turns out sparc64 doesn't like unaligned access either.
29308 Changes in version 0.1.0.15 - 2005-09-23
29309 o Bugfixes on 0.1.0.x:
29310 - Reject ports 465 and 587 (spam targets) in default exit policy.
29311 - Don't crash when we don't have any spare file descriptors and we
29312 try to spawn a dns or cpu worker.
29313 - Get rid of IgnoreVersion undocumented config option, and make us
29314 only warn, never exit, when we're running an obsolete version.
29315 - Don't try to print a null string when your server finds itself to
29316 be unreachable and the Address config option is empty.
29317 - Make the numbers in read-history and write-history into uint64s,
29318 so they don't overflow and publish negatives in the descriptor.
29319 - Fix a minor memory leak in smartlist_string_remove().
29320 - We were only allowing ourselves to upload a server descriptor at
29321 most every 20 minutes, even if it changed earlier than that.
29322 - Clean up log entries that pointed to old URLs.
29325 Changes in version 0.1.1.7-alpha - 2005-09-14
29326 o Fixes on 0.1.1.6-alpha:
29327 - Exit servers were crashing when people asked them to make a
29328 connection to an address not in their exit policy.
29329 - Looking up a non-existent stream for a v1 control connection would
29331 - Fix a seg fault if we ask a dirserver for a descriptor by
29332 fingerprint but he doesn't know about him.
29333 - SETCONF was appending items to linelists, not clearing them.
29334 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
29335 out and refuse the setconf if it would fail.
29336 - Downgrade the dirserver log messages when whining about
29340 - Add Peter Palfrader's check-tor script to tor/contrib/
29341 It lets you easily check whether a given server (referenced by
29342 nickname) is reachable by you.
29343 - Numerous changes to move towards client-side v2 directories. Not
29346 o Fixes on 0.1.0.x:
29347 - If the user gave tor an odd number of command-line arguments,
29348 we were silently ignoring the last one. Now we complain and fail.
29349 [This wins the oldest-bug prize -- this bug has been present since
29350 November 2002, as released in Tor 0.0.0.]
29351 - Do not use unaligned memory access on alpha, mips, or mipsel.
29352 It *works*, but is very slow, so we treat them as if it doesn't.
29353 - Retry directory requests if we fail to get an answer we like
29354 from a given dirserver (we were retrying before, but only if
29355 we fail to connect).
29356 - When writing the RecommendedVersions line, sort them first.
29357 - When the client asked for a rendezvous port that the hidden
29358 service didn't want to provide, we were sending an IP address
29359 back along with the end cell. Fortunately, it was zero. But stop
29361 - Correct "your server is reachable" log entries to indicate that
29362 it was self-testing that told us so.
29365 Changes in version 0.1.1.6-alpha - 2005-09-09
29366 o Fixes on 0.1.1.5-alpha:
29367 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
29368 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
29369 - Fix bug with tor_memmem finding a match at the end of the string.
29370 - Make unit tests run without segfaulting.
29371 - Resolve some solaris x86 compile warnings.
29372 - Handle duplicate lines in approved-routers files without warning.
29373 - Fix bug where as soon as a server refused any requests due to his
29374 exit policy (e.g. when we ask for localhost and he tells us that's
29375 127.0.0.1 and he won't do it), we decided he wasn't obeying his
29376 exit policy using him for any exits.
29377 - Only do openssl hardware accelerator stuff if openssl version is
29380 o New controller features/fixes:
29381 - Add a "RESETCONF" command so you can set config options like
29382 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
29383 a config option in the torrc with no value, then it clears it
29384 entirely (rather than setting it to its default).
29385 - Add a "GETINFO config-file" to tell us where torrc is.
29386 - Avoid sending blank lines when GETINFO replies should be empty.
29387 - Add a QUIT command for the controller (for using it manually).
29388 - Fix a bug in SAVECONF that was adding default dirservers and
29389 other redundant entries to the torrc file.
29391 o Start on the new directory design:
29392 - Generate, publish, cache, serve new network-status format.
29393 - Publish individual descriptors (by fingerprint, by "all", and by
29395 - Publish client and server recommended versions separately.
29396 - Allow tor_gzip_uncompress() to handle multiple concatenated
29397 compressed strings. Serve compressed groups of router
29398 descriptors. The compression logic here could be more
29400 - Distinguish v1 authorities (all currently trusted directories)
29401 from v2 authorities (all trusted directories).
29402 - Change DirServers config line to note which dirs are v1 authorities.
29403 - Add configuration option "V1AuthoritativeDirectory 1" which
29404 moria1, moria2, and tor26 should set.
29405 - Remove option when getting directory cache to see whether they
29406 support running-routers; they all do now. Replace it with one
29407 to see whether caches support v2 stuff.
29410 - Dirservers now do their own external reachability testing of each
29411 Tor server, and only list them as running if they've been found to
29412 be reachable. We also send back warnings to the server's logs if
29413 it uploads a descriptor that we already believe is unreachable.
29414 - Implement exit enclaves: if we know an IP address for the
29415 destination, and there's a running Tor server at that address
29416 which allows exit to the destination, then extend the circuit to
29417 that exit first. This provides end-to-end encryption and end-to-end
29418 authentication. Also, if the user wants a .exit address or enclave,
29419 use 4 hops rather than 3, and cannibalize a general circ for it
29421 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
29422 controller. Also, rotate dns and cpu workers if the controller
29423 changes options that will affect them; and initialize the dns
29424 worker cache tree whether or not we start out as a server.
29425 - Only upload a new server descriptor when options change, 18
29426 hours have passed, uptime is reset, or bandwidth changes a lot.
29427 - Check [X-]Forwarded-For headers in HTTP requests when generating
29428 log messages. This lets people run dirservers (and caches) behind
29429 Apache but still know which IP addresses are causing warnings.
29431 o Config option changes:
29432 - Replace (Fascist)Firewall* config options with a new
29433 ReachableAddresses option that understands address policies.
29434 For example, "ReachableAddresses *:80,*:443"
29435 - Get rid of IgnoreVersion undocumented config option, and make us
29436 only warn, never exit, when we're running an obsolete version.
29437 - Make MonthlyAccountingStart config option truly obsolete now.
29439 o Fixes on 0.1.0.x:
29440 - Reject ports 465 and 587 in the default exit policy, since
29441 people have started using them for spam too.
29442 - It turns out we couldn't bootstrap a network since we added
29443 reachability detection in 0.1.0.1-rc. Good thing the Tor network
29444 has never gone down. Add an AssumeReachable config option to let
29445 servers and dirservers bootstrap. When we're trying to build a
29446 high-uptime or high-bandwidth circuit but there aren't enough
29447 suitable servers, try being less picky rather than simply failing.
29448 - Our logic to decide if the OR we connected to was the right guy
29449 was brittle and maybe open to a mitm for unverified routers.
29450 - We weren't cannibalizing circuits correctly for
29451 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
29452 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
29453 build those from scratch. This should make hidden services faster.
29454 - Predict required circuits better, with an eye toward making hidden
29455 services faster on the service end.
29456 - Retry streams if the exit node sends back a 'misc' failure. This
29457 should result in fewer random failures. Also, after failing
29458 from resolve failed or misc, reset the num failures, so we give
29459 it a fair shake next time we try.
29460 - Clean up the rendezvous warn log msgs, and downgrade some to info.
29461 - Reduce severity on logs about dns worker spawning and culling.
29462 - When we're shutting down and we do something like try to post a
29463 server descriptor or rendezvous descriptor, don't complain that
29464 we seem to be unreachable. Of course we are, we're shutting down.
29465 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
29466 We don't use them yet, but maybe one day our DNS resolver will be
29467 able to discover them.
29468 - Make ContactInfo mandatory for authoritative directory servers.
29469 - Require server descriptors to list IPv4 addresses -- hostnames
29470 are no longer allowed. This also fixes some potential security
29471 problems with people providing hostnames as their address and then
29472 preferentially resolving them to partition users.
29473 - Change log line for unreachability to explicitly suggest /etc/hosts
29474 as the culprit. Also make it clearer what IP address and ports we're
29475 testing for reachability.
29476 - Put quotes around user-supplied strings when logging so users are
29477 more likely to realize if they add bad characters (like quotes)
29479 - Let auth dir servers start without specifying an Address config
29481 - Make unit tests (and other invocations that aren't the real Tor)
29482 run without launching listeners, creating subdirectories, and so on.
29485 Changes in version 0.1.1.5-alpha - 2005-08-08
29486 o Bugfixes included in 0.1.0.14.
29488 o Bugfixes on 0.1.0.x:
29489 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
29490 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
29491 it would silently using ignore the 6668.
29494 Changes in version 0.1.0.14 - 2005-08-08
29495 o Bugfixes on 0.1.0.x:
29496 - Fix the other half of the bug with crypto handshakes
29498 - Fix an assert trigger if you send a 'signal term' via the
29499 controller when it's listening for 'event info' messages.
29502 Changes in version 0.1.1.4-alpha - 2005-08-04
29503 o Bugfixes included in 0.1.0.13.
29506 - Improve tor_gettimeofday() granularity on windows.
29507 - Make clients regenerate their keys when their IP address changes.
29508 - Implement some more GETINFO goodness: expose helper nodes, config
29509 options, getinfo keys.
29512 Changes in version 0.1.0.13 - 2005-08-04
29513 o Bugfixes on 0.1.0.x:
29514 - Fix a critical bug in the security of our crypto handshakes.
29515 - Fix a size_t underflow in smartlist_join_strings2() that made
29516 it do bad things when you hand it an empty smartlist.
29517 - Fix Windows installer to ship Tor license (thanks to Aphex for
29518 pointing out this oversight) and put a link to the doc directory
29520 - Explicitly set no-unaligned-access for sparc: it turns out the
29521 new gcc's let you compile broken code, but that doesn't make it
29525 Changes in version 0.1.1.3-alpha - 2005-07-23
29526 o Bugfixes on 0.1.1.2-alpha:
29527 - Fix a bug in handling the controller's "post descriptor"
29529 - Fix several bugs in handling the controller's "extend circuit"
29531 - Fix a bug in handling the controller's "stream status" event.
29532 - Fix an assert failure if we have a controller listening for
29533 circuit events and we go offline.
29534 - Re-allow hidden service descriptors to publish 0 intro points.
29535 - Fix a crash when generating your hidden service descriptor if
29536 you don't have enough intro points already.
29538 o New features on 0.1.1.2-alpha:
29539 - New controller function "getinfo accounting", to ask how
29540 many bytes we've used in this time period.
29541 - Experimental support for helper nodes: a lot of the risk from
29542 a small static adversary comes because users pick new random
29543 nodes every time they rebuild a circuit. Now users will try to
29544 stick to the same small set of entry nodes if they can. Not
29545 enabled by default yet.
29547 o Bugfixes on 0.1.0.12:
29548 - If you're an auth dir server, always publish your dirport,
29549 even if you haven't yet found yourself to be reachable.
29550 - Fix a size_t underflow in smartlist_join_strings2() that made
29551 it do bad things when you hand it an empty smartlist.
29554 Changes in version 0.1.0.12 - 2005-07-18
29555 o New directory servers:
29556 - tor26 has changed IP address.
29558 o Bugfixes on 0.1.0.x:
29559 - Fix a possible double-free in tor_gzip_uncompress().
29560 - When --disable-threads is set, do not search for or link against
29561 pthreads libraries.
29562 - Don't trigger an assert if an authoritative directory server
29563 claims its dirport is 0.
29564 - Fix bug with removing Tor as an NT service: some people were
29565 getting "The service did not return an error." Thanks to Matt
29569 Changes in version 0.1.1.2-alpha - 2005-07-15
29570 o New directory servers:
29571 - tor26 has changed IP address.
29573 o Bugfixes on 0.1.0.x, crashes/leaks:
29574 - Port the servers-not-obeying-their-exit-policies fix from
29576 - Fix an fd leak in start_daemon().
29577 - On Windows, you can't always reopen a port right after you've
29578 closed it. So change retry_listeners() to only close and re-open
29579 ports that have changed.
29580 - Fix a possible double-free in tor_gzip_uncompress().
29582 o Bugfixes on 0.1.0.x, usability:
29583 - When tor_socketpair() fails in Windows, give a reasonable
29584 Windows-style errno back.
29585 - Let people type "tor --install" as well as "tor -install" when
29587 want to make it an NT service.
29588 - NT service patch from Matt Edman to improve error messages.
29589 - When the controller asks for a config option with an abbreviated
29590 name, give the full name in our response.
29591 - Correct the man page entry on TrackHostExitsExpire.
29592 - Looks like we were never delivering deflated (i.e. compressed)
29593 running-routers lists, even when asked. Oops.
29594 - When --disable-threads is set, do not search for or link against
29595 pthreads libraries.
29597 o Bugfixes on 0.1.1.x:
29598 - Fix a seg fault with autodetecting which controller version is
29602 - New hidden service descriptor format: put a version in it, and
29603 let people specify introduction/rendezvous points that aren't
29604 in "the directory" (which is subjective anyway).
29605 - Allow the DEBUG controller event to work again. Mark certain log
29606 entries as "don't tell this to controllers", so we avoid cycles.
29609 Changes in version 0.1.0.11 - 2005-06-30
29610 o Bugfixes on 0.1.0.x:
29611 - Fix major security bug: servers were disregarding their
29612 exit policies if clients behaved unexpectedly.
29613 - Make OS X init script check for missing argument, so we don't
29614 confuse users who invoke it incorrectly.
29615 - Fix a seg fault in "tor --hash-password foo".
29616 - The MAPADDRESS control command was broken.
29619 Changes in version 0.1.1.1-alpha - 2005-06-29
29621 - Make OS X init script check for missing argument, so we don't
29622 confuse users who invoke it incorrectly.
29623 - Fix a seg fault in "tor --hash-password foo".
29624 - Fix a possible way to DoS dirservers.
29625 - When we complain that your exit policy implicitly allows local or
29626 private address spaces, name them explicitly so operators can
29628 - Make the log message less scary when all the dirservers are
29629 temporarily unreachable.
29630 - We were printing the number of idle dns workers incorrectly when
29634 - Revised controller protocol (version 1) that uses ascii rather
29635 than binary. Add supporting libraries in python and java so you
29636 can use the controller from your applications without caring how
29637 our protocol works.
29638 - Spiffy new support for crypto hardware accelerators. Can somebody
29642 Changes in version 0.0.9.10 - 2005-06-16
29643 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
29644 - Refuse relay cells that claim to have a length larger than the
29645 maximum allowed. This prevents a potential attack that could read
29646 arbitrary memory (e.g. keys) from an exit server's process
29650 Changes in version 0.1.0.10 - 2005-06-14
29651 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
29652 libevent before 1.1a.
29655 Changes in version 0.1.0.9-rc - 2005-06-09
29657 - Reset buf->highwater every time buf_shrink() is called, not just on
29658 a successful shrink. This was causing significant memory bloat.
29659 - Fix buffer overflow when checking hashed passwords.
29660 - Security fix: if seeding the RNG on Win32 fails, quit.
29661 - Allow seeding the RNG on Win32 even when you're not running as
29663 - Disable threading on Solaris too. Something is wonky with it,
29664 cpuworkers, and reentrant libs.
29665 - Reenable the part of the code that tries to flush as soon as an
29666 OR outbuf has a full TLS record available. Perhaps this will make
29667 OR outbufs not grow as huge except in rare cases, thus saving lots
29668 of CPU time plus memory.
29669 - Reject malformed .onion addresses rather then passing them on as
29670 normal web requests.
29671 - Adapt patch from Adam Langley: fix possible memory leak in
29672 tor_lookup_hostname().
29673 - Initialize libevent later in the startup process, so the logs are
29674 already established by the time we start logging libevent warns.
29675 - Use correct errno on win32 if libevent fails.
29676 - Check and warn about known-bad/slow libevent versions.
29677 - Pay more attention to the ClientOnly config option.
29678 - Have torctl.in/tor.sh.in check for location of su binary (needed
29680 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
29681 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
29682 HttpProxyAuthenticator
29683 - Stop warning about sigpipes in the logs. We're going to
29684 pretend that getting these occasionally is normal and fine.
29685 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
29687 installer screens; and don't put stuff into StartupItems unless
29688 the user asks you to.
29689 - Require servers that use the default dirservers to have public IP
29690 addresses. We have too many servers that are configured with private
29691 IPs and their admins never notice the log entries complaining that
29692 their descriptors are being rejected.
29693 - Add OSX uninstall instructions. An actual uninstall script will
29697 Changes in version 0.1.0.8-rc - 2005-05-23
29699 - It turns out that kqueue on OS X 10.3.9 was causing kernel
29700 panics. Disable kqueue on all OS X Tors.
29701 - Fix RPM: remove duplicate line accidentally added to the rpm
29703 - Disable threads on openbsd too, since its gethostaddr is not
29705 - Tolerate libevent 0.8 since it still works, even though it's
29707 - Enable building on Red Hat 9.0 again.
29708 - Allow the middle hop of the testing circuit to be running any
29709 version, now that most of them have the bugfix to let them connect
29710 to unknown servers. This will allow reachability testing to work
29711 even when 0.0.9.7-0.0.9.9 become obsolete.
29712 - Handle relay cells with rh.length too large. This prevents
29713 a potential attack that could read arbitrary memory (maybe even
29714 keys) from the exit server's process.
29715 - We screwed up the dirport reachability testing when we don't yet
29716 have a cached version of the directory. Hopefully now fixed.
29717 - Clean up router_load_single_router() (used by the controller),
29718 so it doesn't seg fault on error.
29719 - Fix a minor memory leak when somebody establishes an introduction
29720 point at your Tor server.
29721 - If a socks connection ends because read fails, don't warn that
29722 you're not sending a socks reply back.
29725 - Add HttpProxyAuthenticator config option too, that works like
29726 the HttpsProxyAuthenticator config option.
29727 - Encode hashed controller passwords in hex instead of base64,
29728 to make it easier to write controllers.
29731 Changes in version 0.1.0.7-rc - 2005-05-17
29733 - Fix a bug in the OS X package installer that prevented it from
29734 installing on Tiger.
29735 - Fix a script bug in the OS X package installer that made it
29736 complain during installation.
29737 - Find libevent even if it's hiding in /usr/local/ and your
29738 CFLAGS and LDFLAGS don't tell you to look there.
29739 - Be able to link with libevent as a shared library (the default
29740 after 1.0d), even if it's hiding in /usr/local/lib and even
29741 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
29742 assuming you're running gcc. Otherwise fail and give a useful
29744 - Fix a bug in the RPM packager: set home directory for _tor to
29745 something more reasonable when first installing.
29746 - Free a minor amount of memory that is still reachable on exit.
29749 Changes in version 0.1.0.6-rc - 2005-05-14
29751 - Implement --disable-threads configure option. Disable threads on
29752 netbsd by default, because it appears to have no reentrant resolver
29754 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
29755 release (1.1) detects and disables kqueue if it's broken.
29756 - Append default exit policy before checking for implicit internal
29757 addresses. Now we don't log a bunch of complaints on startup
29758 when using the default exit policy.
29759 - Some people were putting "Address " in their torrc, and they had
29760 a buggy resolver that resolved " " to 0.0.0.0. Oops.
29761 - If DataDir is ~/.tor, and that expands to /.tor, then default to
29762 LOCALSTATEDIR/tor instead.
29763 - Fix fragmented-message bug in TorControl.py.
29764 - Resolve a minor bug which would prevent unreachable dirports
29765 from getting suppressed in the published descriptor.
29766 - When the controller gave us a new descriptor, we weren't resolving
29767 it immediately, so Tor would think its address was 0.0.0.0 until
29768 we fetched a new directory.
29769 - Fix an uppercase/lowercase case error in suppressing a bogus
29770 libevent warning on some Linuxes.
29773 - Begin scrubbing sensitive strings from logs by default. Turn off
29774 the config option SafeLogging if you need to do debugging.
29775 - Switch to a new buffer management algorithm, which tries to avoid
29776 reallocing and copying quite as much. In first tests it looks like
29777 it uses *more* memory on average, but less cpu.
29778 - First cut at support for "create-fast" cells. Clients can use
29779 these when extending to their first hop, since the TLS already
29780 provides forward secrecy and authentication. Not enabled on
29782 - When dirservers refuse a router descriptor, we now log its
29783 contactinfo, platform, and the poster's IP address.
29784 - Call tor_free_all instead of connections_free_all after forking, to
29785 save memory on systems that need to fork.
29786 - Whine at you if you're a server and you don't set your contactinfo.
29787 - Implement --verify-config command-line option to check if your torrc
29788 is valid without actually launching Tor.
29789 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
29790 rather than just rejecting it.
29793 Changes in version 0.1.0.5-rc - 2005-04-27
29795 - Stop trying to print a null pointer if an OR conn fails because
29796 we didn't like its cert.
29798 - Switch our internal buffers implementation to use a ring buffer,
29799 to hopefully improve performance for fast servers a lot.
29800 - Add HttpsProxyAuthenticator support (basic auth only), based
29801 on patch from Adam Langley.
29802 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
29803 the fast servers that have been joining lately.
29804 - Give hidden service accesses extra time on the first attempt,
29805 since 60 seconds is often only barely enough. This might improve
29807 - Improve performance for dirservers: stop re-parsing the whole
29808 directory every time you regenerate it.
29809 - Add more debugging info to help us find the weird dns freebsd
29810 pthreads bug; cleaner debug messages to help track future issues.
29813 Changes in version 0.0.9.9 - 2005-04-23
29814 o Bugfixes on 0.0.9.x:
29815 - If unofficial Tor clients connect and send weird TLS certs, our
29816 Tor server triggers an assert. This release contains a minimal
29817 backport from the broader fix that we put into 0.1.0.4-rc.
29820 Changes in version 0.1.0.4-rc - 2005-04-23
29822 - If unofficial Tor clients connect and send weird TLS certs, our
29823 Tor server triggers an assert. Stop asserting, and start handling
29824 TLS errors better in other situations too.
29825 - When the controller asks us to tell it about all the debug-level
29826 logs, it turns out we were generating debug-level logs while
29827 telling it about them, which turns into a bad loop. Now keep
29828 track of whether you're sending a debug log to the controller,
29829 and don't log when you are.
29830 - Fix the "postdescriptor" feature of the controller interface: on
29831 non-complete success, only say "done" once.
29833 - Clients are now willing to load balance over up to 2mB, not 1mB,
29834 of advertised bandwidth capacity.
29835 - Add a NoPublish config option, so you can be a server (e.g. for
29836 testing running Tor servers in other Tor networks) without
29837 publishing your descriptor to the primary dirservers.
29840 Changes in version 0.1.0.3-rc - 2005-04-08
29841 o Improvements on 0.1.0.2-rc:
29842 - Client now retries when streams end early for 'hibernating' or
29843 'resource limit' reasons, rather than failing them.
29844 - More automated handling for dirserver operators:
29845 - Automatically approve nodes running 0.1.0.2-rc or later,
29846 now that the the reachability detection stuff is working.
29847 - Now we allow two unverified servers with the same nickname
29848 but different keys. But if a nickname is verified, only that
29849 nickname+key are allowed.
29850 - If you're an authdirserver connecting to an address:port,
29851 and it's not the OR you were expecting, forget about that
29852 descriptor. If he *was* the one you were expecting, then forget
29853 about all other descriptors for that address:port.
29854 - Allow servers to publish descriptors from 12 hours in the future.
29855 Corollary: only whine about clock skew from the dirserver if
29856 he's a trusted dirserver (since now even verified servers could
29857 have quite wrong clocks).
29858 - Adjust maximum skew and age for rendezvous descriptors: let skew
29859 be 48 hours rather than 90 minutes.
29860 - Efficiency improvements:
29861 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
29862 it much faster to look up a circuit for each relay cell.
29863 - Remove most calls to assert_all_pending_dns_resolves_ok(),
29864 since they're eating our cpu on exit nodes.
29865 - Stop wasting time doing a case insensitive comparison for every
29866 dns name every time we do any lookup. Canonicalize the names to
29867 lowercase and be done with it.
29868 - Start sending 'truncated' cells back rather than destroy cells,
29869 if the circuit closes in front of you. This means we won't have
29870 to abandon partially built circuits.
29871 - Only warn once per nickname from add_nickname_list_to_smartlist
29872 per failure, so an entrynode or exitnode choice that's down won't
29874 - Put a note in the torrc about abuse potential with the default
29876 - Revise control spec and implementation to allow all log messages to
29877 be sent to controller with their severities intact (suggested by
29878 Matt Edman). Update TorControl to handle new log event types.
29879 - Provide better explanation messages when controller's POSTDESCRIPTOR
29881 - Stop putting nodename in the Platform string in server descriptors.
29882 It doesn't actually help, and it is confusing/upsetting some people.
29884 o Bugfixes on 0.1.0.2-rc:
29885 - We were printing the host mask wrong in exit policies in server
29886 descriptors. This isn't a critical bug though, since we were still
29887 obeying the exit policy internally.
29888 - Fix Tor when compiled with libevent but without pthreads: move
29889 connection_unregister() from _connection_free() to
29891 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
29892 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
29893 when we look through the connection array, we'll find any of the
29894 cpu/dnsworkers. This is no good.
29896 o Bugfixes on 0.0.9.8:
29897 - Fix possible bug on threading platforms (e.g. win32) which was
29898 leaking a file descriptor whenever a cpuworker or dnsworker died.
29899 - When using preferred entry or exit nodes, ignore whether the
29900 circuit wants uptime or capacity. They asked for the nodes, they
29902 - chdir() to your datadirectory at the *end* of the daemonize process,
29903 not the beginning. This was a problem because the first time you
29904 run tor, if your datadir isn't there, and you have runasdaemon set
29905 to 1, it will try to chdir to it before it tries to create it. Oops.
29906 - Handle changed router status correctly when dirserver reloads
29907 fingerprint file. We used to be dropping all unverified descriptors
29908 right then. The bug was hidden because we would immediately
29909 fetch a directory from another dirserver, which would include the
29910 descriptors we just dropped.
29911 - When we're connecting to an OR and he's got a different nickname/key
29912 than we were expecting, only complain loudly if we're an OP or a
29913 dirserver. Complaining loudly to the OR admins just confuses them.
29914 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
29915 artificially capped at 500kB.
29918 Changes in version 0.0.9.8 - 2005-04-07
29919 o Bugfixes on 0.0.9.x:
29920 - We have a bug that I haven't found yet. Sometimes, very rarely,
29921 cpuworkers get stuck in the 'busy' state, even though the cpuworker
29922 thinks of itself as idle. This meant that no new circuits ever got
29923 established. Here's a workaround to kill any cpuworker that's been
29924 busy for more than 100 seconds.
29927 Changes in version 0.1.0.2-rc - 2005-04-01
29928 o Bugfixes on 0.1.0.1-rc:
29929 - Fixes on reachability detection:
29930 - Don't check for reachability while hibernating.
29931 - If ORPort is reachable but DirPort isn't, still publish the
29932 descriptor, but zero out DirPort until it's found reachable.
29933 - When building testing circs for ORPort testing, use only
29934 high-bandwidth nodes, so fewer circuits fail.
29935 - Complain about unreachable ORPort separately from unreachable
29936 DirPort, so the user knows what's going on.
29937 - Make sure we only conclude ORPort reachability if we didn't
29938 initiate the conn. Otherwise we could falsely conclude that
29939 we're reachable just because we connected to the guy earlier
29940 and he used that same pipe to extend to us.
29941 - Authdirservers shouldn't do ORPort reachability detection,
29942 since they're in clique mode, so it will be rare to find a
29943 server not already connected to them.
29944 - When building testing circuits, always pick middle hops running
29945 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
29946 bug. (This is a kludge; it will go away when 0.0.9.x becomes
29948 - When we decide we're reachable, actually publish our descriptor
29950 - Fix bug in redirectstream in the controller.
29951 - Fix the state descriptor strings so logs don't claim edge streams
29952 are in a different state than they actually are.
29953 - Use recent libevent features when possible (this only really affects
29954 win32 and osx right now, because the new libevent with these
29955 features hasn't been released yet). Add code to suppress spurious
29957 - Prevent possible segfault in connection_close_unattached_ap().
29958 - Fix newlines on torrc in win32.
29959 - Improve error msgs when tor-resolve fails.
29961 o Improvements on 0.0.9.x:
29962 - New experimental script tor/contrib/ExerciseServer.py (needs more
29963 work) that uses the controller interface to build circuits and
29964 fetch pages over them. This will help us bootstrap servers that
29965 have lots of capacity but haven't noticed it yet.
29966 - New experimental script tor/contrib/PathDemo.py (needs more work)
29967 that uses the controller interface to let you choose whole paths
29969 "<hostname>.<path,separated by dots>.<length of path>.path"
29970 - When we've connected to an OR and handshaked but didn't like
29971 the result, we were closing the conn without sending destroy
29972 cells back for pending circuits. Now send those destroys.
29975 Changes in version 0.0.9.7 - 2005-04-01
29976 o Bugfixes on 0.0.9.x:
29977 - Fix another race crash bug (thanks to Glenn Fink for reporting).
29978 - Compare identity to identity, not to nickname, when extending to
29979 a router not already in the directory. This was preventing us from
29980 extending to unknown routers. Oops.
29981 - Make sure to create OS X Tor user in <500 range, so we aren't
29982 creating actual system users.
29983 - Note where connection-that-hasn't-sent-end was marked, and fix
29984 a few really loud instances of this harmless bug (it's fixed more
29988 Changes in version 0.1.0.1-rc - 2005-03-28
29990 - Add reachability testing. Your Tor server will automatically try
29991 to see if its ORPort and DirPort are reachable from the outside,
29992 and it won't upload its descriptor until it decides they are.
29993 - Handle unavailable hidden services better. Handle slow or busy
29994 hidden services better.
29995 - Add support for CONNECTing through https proxies, with "HttpsProxy"
29997 - New exit policy: accept most low-numbered ports, rather than
29998 rejecting most low-numbered ports.
29999 - More Tor controller support (still experimental). See
30000 http://tor.eff.org/doc/control-spec.txt for all the new features,
30001 including signals to emulate unix signals from any platform;
30002 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
30003 closestream; closecircuit; etc.
30004 - Make nt services work and start on startup on win32 (based on
30005 patch by Matt Edman).
30006 - Add a new AddressMap config directive to rewrite incoming socks
30007 addresses. This lets you, for example, declare an implicit
30008 required exit node for certain sites.
30009 - Add a new TrackHostExits config directive to trigger addressmaps
30010 for certain incoming socks addresses -- for sites that break when
30011 your exit keeps changing (based on patch by Mike Perry).
30012 - Redo the client-side dns cache so it's just an addressmap too.
30013 - Notice when our IP changes, and reset stats/uptime/reachability.
30014 - When an application is using socks5, give him the whole variety of
30015 potential socks5 responses (connect refused, host unreachable, etc),
30016 rather than just "success" or "failure".
30017 - A more sane version numbering system. See
30018 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
30019 - New contributed script "exitlist": a simple python script to
30020 parse directories and find Tor nodes that exit to listed
30022 - New contributed script "privoxy-tor-toggle" to toggle whether
30023 Privoxy uses Tor. Seems to be configured for Debian by default.
30024 - Report HTTP reasons to client when getting a response from directory
30025 servers -- so you can actually know what went wrong.
30026 - New config option MaxAdvertisedBandwidth which lets you advertise
30027 a low bandwidthrate (to not attract as many circuits) while still
30028 allowing a higher bandwidthrate in reality.
30030 o Robustness/stability fixes:
30031 - Make Tor use Niels Provos's libevent instead of its current
30032 poll-but-sometimes-select mess. This will let us use faster async
30033 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
30035 - pthread support now too. This was forced because when we forked,
30036 we ended up wasting a lot of duplicate ram over time. Also switch
30037 to foo_r versions of some library calls to allow reentry and
30039 - Better handling for heterogeneous / unreliable nodes:
30040 - Annotate circuits w/ whether they aim to contain high uptime nodes
30041 and/or high capacity nodes. When building circuits, choose
30043 - This means that every single node in an intro rend circuit,
30044 not just the last one, will have a minimum uptime.
30045 - New config option LongLivedPorts to indicate application streams
30046 that will want high uptime circuits.
30047 - Servers reset uptime when a dir fetch entirely fails. This
30048 hopefully reflects stability of the server's network connectivity.
30049 - If somebody starts his tor server in Jan 2004 and then fixes his
30050 clock, don't make his published uptime be a year.
30051 - Reset published uptime when you wake up from hibernation.
30052 - Introduce a notion of 'internal' circs, which are chosen without
30053 regard to the exit policy of the last hop. Intro and rendezvous
30054 circs must be internal circs, to avoid leaking information. Resolve
30055 and connect streams can use internal circs if they want.
30056 - New circuit pooling algorithm: make sure to have enough circs around
30057 to satisfy any predicted ports, and also make sure to have 2 internal
30058 circs around if we've required internal circs lately (and with high
30059 uptime if we've seen that lately too).
30060 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
30061 which describes how often we retry making new circuits if current
30062 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
30063 how long we're willing to make use of an already-dirty circuit.
30064 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
30065 circ as necessary, if there are any completed ones lying around
30066 when we try to launch one.
30067 - Make hidden services try to establish a rendezvous for 30 seconds,
30068 rather than for n (where n=3) attempts to build a circuit.
30069 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
30070 "ShutdownWaitLength".
30071 - Try to be more zealous about calling connection_edge_end when
30072 things go bad with edge conns in connection.c.
30073 - Revise tor-spec to add more/better stream end reasons.
30074 - Revise all calls to connection_edge_end to avoid sending "misc",
30075 and to take errno into account where possible.
30078 - Fix a race condition that can trigger an assert, when we have a
30079 pending create cell and an OR connection fails right then.
30080 - Fix several double-mark-for-close bugs, e.g. where we were finding
30081 a conn for a cell even if that conn is already marked for close.
30082 - Make sequence of log messages when starting on win32 with no config
30083 file more reasonable.
30084 - When choosing an exit node for a new non-internal circ, don't take
30085 into account whether it'll be useful for any pending x.onion
30086 addresses -- it won't.
30087 - Turn addr_policy_compare from a tristate to a quadstate; this should
30088 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
30089 for google.com" problem.
30090 - Make "platform" string in descriptor more accurate for Win32 servers,
30091 so it's not just "unknown platform".
30092 - Fix an edge case in parsing config options (thanks weasel).
30093 If they say "--" on the commandline, it's not an option.
30094 - Reject odd-looking addresses at the client (e.g. addresses that
30095 contain a colon), rather than having the server drop them because
30097 - tor-resolve requests were ignoring .exit if there was a working circuit
30098 they could use instead.
30099 - REUSEADDR on normal platforms means you can rebind to the port
30100 right after somebody else has let it go. But REUSEADDR on win32
30101 means to let you bind to the port _even when somebody else
30102 already has it bound_! So, don't do that on Win32.
30103 - Change version parsing logic: a version is "obsolete" if it is not
30104 recommended and (1) there is a newer recommended version in the
30105 same series, or (2) there are no recommended versions in the same
30106 series, but there are some recommended versions in a newer series.
30107 A version is "new" if it is newer than any recommended version in
30109 - Stop most cases of hanging up on a socks connection without sending
30113 - Require BandwidthRate to be at least 20kB/s for servers.
30114 - When a dirserver causes you to give a warn, mention which dirserver
30116 - New config option DirAllowPrivateAddresses for authdirservers.
30117 Now by default they refuse router descriptors that have non-IP or
30118 private-IP addresses.
30119 - Stop publishing socksport in the directory, since it's not
30120 actually meant to be public. For compatibility, publish a 0 there
30122 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
30123 smart" value, that is low for servers and high for clients.
30124 - If our clock jumps forward by 100 seconds or more, assume something
30125 has gone wrong with our network and abandon all not-yet-used circs.
30126 - Warn when exit policy implicitly allows local addresses.
30127 - If we get an incredibly skewed timestamp from a dirserver mirror
30128 that isn't a verified OR, don't warn -- it's probably him that's
30130 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
30131 cookies to disk and doesn't log each web request to disk. (Thanks
30132 to Brett Carrington for pointing this out.)
30133 - When a client asks us for a dir mirror and we don't have one,
30134 launch an attempt to get a fresh one.
30135 - If we're hibernating and we get a SIGINT, exit immediately.
30136 - Add --with-dmalloc ./configure option, to track memory leaks.
30137 - And try to free all memory on closing, so we can detect what
30139 - Cache local dns resolves correctly even when they're .exit
30141 - Give a better warning when some other server advertises an
30142 ORPort that is actually an apache running ssl.
30143 - Add "opt hibernating 1" to server descriptor to make it clearer
30144 whether the server is hibernating.
30147 Changes in version 0.0.9.6 - 2005-03-24
30148 o Bugfixes on 0.0.9.x (crashes and asserts):
30149 - Add new end stream reasons to maintenance branch. Fix bug where
30150 reason (8) could trigger an assert. Prevent bug from recurring.
30151 - Apparently win32 stat wants paths to not end with a slash.
30152 - Fix assert triggers in assert_cpath_layer_ok(), where we were
30153 blowing away the circuit that conn->cpath_layer points to, then
30154 checking to see if the circ is well-formed. Backport check to make
30155 sure we dont use the cpath on a closed connection.
30156 - Prevent circuit_resume_edge_reading_helper() from trying to package
30157 inbufs for marked-for-close streams.
30158 - Don't crash on hup if your options->address has become unresolvable.
30159 - Some systems (like OS X) sometimes accept() a connection and tell
30160 you the remote host is 0.0.0.0:0. If this happens, due to some
30161 other mis-features, we get confused; so refuse the conn for now.
30163 o Bugfixes on 0.0.9.x (other):
30164 - Fix harmless but scary "Unrecognized content encoding" warn message.
30165 - Add new stream error reason: TORPROTOCOL reason means "you are not
30166 speaking a version of Tor I understand; say bye-bye to your stream."
30167 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
30168 into the future, now that we are more tolerant of skew. This
30169 resolves a bug where a Tor server would refuse to cache a directory
30170 because all the directories it gets are too far in the future;
30171 yet the Tor server never logs any complaints about clock skew.
30172 - Mac packaging magic: make man pages useable, and do not overwrite
30173 existing torrc files.
30174 - Make OS X log happily to /var/log/tor/tor.log
30177 Changes in version 0.0.9.5 - 2005-02-22
30178 o Bugfixes on 0.0.9.x:
30179 - Fix an assert race at exit nodes when resolve requests fail.
30180 - Stop picking unverified dir mirrors--it only leads to misery.
30181 - Patch from Matt Edman to make NT services work better. Service
30182 support is still not compiled into the executable by default.
30183 - Patch from Dmitri Bely so the Tor service runs better under
30184 the win32 SYSTEM account.
30185 - Make tor-resolve actually work (?) on Win32.
30186 - Fix a sign bug when getrlimit claims to have 4+ billion
30187 file descriptors available.
30188 - Stop refusing to start when bandwidthburst == bandwidthrate.
30189 - When create cells have been on the onion queue more than five
30190 seconds, just send back a destroy and take them off the list.
30193 Changes in version 0.0.9.4 - 2005-02-03
30194 o Bugfixes on 0.0.9:
30195 - Fix an assert bug that took down most of our servers: when
30196 a server claims to have 1 GB of bandwidthburst, don't
30198 - Don't crash as badly if we have spawned the max allowed number
30199 of dnsworkers, or we're out of file descriptors.
30200 - Block more file-sharing ports in the default exit policy.
30201 - MaxConn is now automatically set to the hard limit of max
30202 file descriptors we're allowed (ulimit -n), minus a few for
30204 - Give a clearer message when servers need to raise their
30205 ulimit -n when they start running out of file descriptors.
30206 - SGI Compatibility patches from Jan Schaumann.
30207 - Tolerate a corrupt cached directory better.
30208 - When a dirserver hasn't approved your server, list which one.
30209 - Go into soft hibernation after 95% of the bandwidth is used,
30210 not 99%. This is especially important for daily hibernators who
30211 have a small accounting max. Hopefully it will result in fewer
30212 cut connections when the hard hibernation starts.
30213 - Load-balance better when using servers that claim more than
30214 800kB/s of capacity.
30215 - Make NT services work (experimental, only used if compiled in).
30218 Changes in version 0.0.9.3 - 2005-01-21
30219 o Bugfixes on 0.0.9:
30220 - Backport the cpu use fixes from main branch, so busy servers won't
30221 need as much processor time.
30222 - Work better when we go offline and then come back, or when we
30223 run Tor at boot before the network is up. We do this by
30224 optimistically trying to fetch a new directory whenever an
30225 application request comes in and we think we're offline -- the
30226 human is hopefully a good measure of when the network is back.
30227 - Backport some minimal hidserv bugfixes: keep rend circuits open as
30228 long as you keep using them; actually publish hidserv descriptors
30229 shortly after they change, rather than waiting 20-40 minutes.
30230 - Enable Mac startup script by default.
30231 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
30232 - When you update AllowUnverifiedNodes or FirewallPorts via the
30233 controller's setconf feature, we were always appending, never
30235 - When you update HiddenServiceDir via setconf, it was screwing up
30236 the order of reading the lines, making it fail.
30237 - Do not rewrite a cached directory back to the cache; otherwise we
30238 will think it is recent and not fetch a newer one on startup.
30239 - Workaround for webservers that lie about Content-Encoding: Tor
30240 now tries to autodetect compressed directories and compression
30241 itself. This lets us Proxypass dir fetches through apache.
30244 Changes in version 0.0.9.2 - 2005-01-04
30245 o Bugfixes on 0.0.9 (crashes and asserts):
30246 - Fix an assert on startup when the disk is full and you're logging
30248 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
30249 style address, then we'd crash.
30250 - Fix an assert trigger when the running-routers string we get from
30251 a dirserver is broken.
30252 - Make worker threads start and run on win32. Now win32 servers
30254 - Bandaid (not actually fix, but now it doesn't crash) an assert
30255 where the dns worker dies mysteriously and the main Tor process
30256 doesn't remember anything about the address it was resolving.
30258 o Bugfixes on 0.0.9 (Win32):
30259 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
30260 name out of the warning/assert messages.
30261 - Fix a superficial "unhandled error on read" bug on win32.
30262 - The win32 installer no longer requires a click-through for our
30263 license, since our Free Software license grants rights but does not
30265 - Win32: When connecting to a dirserver fails, try another one
30266 immediately. (This was already working for non-win32 Tors.)
30267 - Stop trying to parse $HOME on win32 when hunting for default
30269 - Make tor-resolve.c work on win32 by calling network_init().
30271 o Bugfixes on 0.0.9 (other):
30272 - Make 0.0.9.x build on Solaris again.
30273 - Due to a fencepost error, we were blowing away the \n when reporting
30274 confvalue items in the controller. So asking for multiple config
30275 values at once couldn't work.
30276 - When listing circuits that are pending on an opening OR connection,
30277 if we're an OR we were listing circuits that *end* at us as
30278 being pending on every listener, dns/cpu worker, etc. Stop that.
30279 - Dirservers were failing to create 'running-routers' or 'directory'
30280 strings if we had more than some threshold of routers. Fix them so
30281 they can handle any number of routers.
30282 - Fix a superficial "Duplicate mark for close" bug.
30283 - Stop checking for clock skew for OR connections, even for servers.
30284 - Fix a fencepost error that was chopping off the last letter of any
30285 nickname that is the maximum allowed nickname length.
30286 - Update URLs in log messages so they point to the new website.
30287 - Fix a potential problem in mangling server private keys while
30288 writing to disk (not triggered yet, as far as we know).
30289 - Include the licenses for other free software we include in Tor,
30290 now that we're shipping binary distributions more regularly.
30293 Changes in version 0.0.9.1 - 2004-12-15
30294 o Bugfixes on 0.0.9:
30295 - Make hibernation actually work.
30296 - Make HashedControlPassword config option work.
30297 - When we're reporting event circuit status to a controller,
30298 don't use the stream status code.
30301 Changes in version 0.0.9 - 2004-12-12
30303 - Clean up manpage and torrc.sample file.
30304 - Clean up severities and text of log warnings.
30306 - Make servers trigger an assert when they enter hibernation.
30309 Changes in version 0.0.9rc7 - 2004-12-08
30310 o Bugfixes on 0.0.9rc:
30311 - Fix a stack-trashing crash when an exit node begins hibernating.
30312 - Avoid looking at unallocated memory while considering which
30313 ports we need to build circuits to cover.
30314 - Stop a sigpipe: when an 'end' cell races with eof from the app,
30315 we shouldn't hold-open-until-flush if the eof arrived first.
30316 - Fix a bug with init_cookie_authentication() in the controller.
30317 - When recommending new-format log lines, if the upper bound is
30318 LOG_ERR, leave it implicit.
30320 o Bugfixes on 0.0.8.1:
30321 - Fix a whole slew of memory leaks.
30322 - Fix isspace() and friends so they still make Solaris happy
30323 but also so they don't trigger asserts on win32.
30324 - Fix parse_iso_time on platforms without strptime (eg win32).
30325 - win32: tolerate extra "readable" events better.
30326 - win32: when being multithreaded, leave parent fdarray open.
30327 - Make unit tests work on win32.
30330 Changes in version 0.0.9rc6 - 2004-12-06
30331 o Bugfixes on 0.0.9pre:
30332 - Clean up some more integer underflow opportunities (not exploitable
30334 - While hibernating, hup should not regrow our listeners.
30335 - Send an end to the streams we close when we hibernate, rather
30336 than just chopping them off.
30337 - React to eof immediately on non-open edge connections.
30339 o Bugfixes on 0.0.8.1:
30340 - Calculate timeout for waiting for a connected cell from the time
30341 we sent the begin cell, not from the time the stream started. If
30342 it took a long time to establish the circuit, we would time out
30343 right after sending the begin cell.
30344 - Fix router_compare_addr_to_addr_policy: it was not treating a port
30345 of * as always matching, so we were picking reject *:* nodes as
30346 exit nodes too. Oops.
30349 - New circuit building strategy: keep a list of ports that we've
30350 used in the past 6 hours, and always try to have 2 circuits open
30351 or on the way that will handle each such port. Seed us with port
30352 80 so web users won't complain that Tor is "slow to start up".
30353 - Make kill -USR1 dump more useful stats about circuits.
30354 - When warning about retrying or giving up, print the address, so
30355 the user knows which one it's talking about.
30356 - If you haven't used a clean circuit in an hour, throw it away,
30357 just to be on the safe side. (This means after 6 hours a totally
30358 unused Tor client will have no circuits open.)
30361 Changes in version 0.0.9rc5 - 2004-12-01
30362 o Bugfixes on 0.0.8.1:
30363 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
30364 - Let resolve conns retry/expire also, rather than sticking around
30366 - If we are using select, make sure we stay within FD_SETSIZE.
30368 o Bugfixes on 0.0.9pre:
30369 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
30370 but doesn't seem to be currently; thanks to Ilja van Sprundel for
30372 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
30373 instead. Impose minima and maxima for all *Period options; impose
30374 even tighter maxima for fetching if we are a caching dirserver.
30375 Clip rather than rejecting.
30376 - Fetch cached running-routers from servers that serve it (that is,
30377 authdirservers and servers running 0.0.9rc5-cvs or later.)
30380 - Accept *:706 (silc) in default exit policy.
30381 - Implement new versioning format for post 0.1.
30382 - Support "foo.nickname.exit" addresses, to let Alice request the
30383 address "foo" as viewed by exit node "nickname". Based on a patch
30385 - Make tor --version --version dump the cvs Id of every file.
30388 Changes in version 0.0.9rc4 - 2004-11-28
30389 o Bugfixes on 0.0.8.1:
30390 - Make windows sockets actually non-blocking (oops), and handle
30391 win32 socket errors better.
30393 o Bugfixes on 0.0.9rc1:
30394 - Actually catch the -USR2 signal.
30397 Changes in version 0.0.9rc3 - 2004-11-25
30398 o Bugfixes on 0.0.8.1:
30399 - Flush the log file descriptor after we print "Tor opening log file",
30400 so we don't see those messages days later.
30402 o Bugfixes on 0.0.9rc1:
30403 - Make tor-resolve work again.
30404 - Avoid infinite loop in tor-resolve if tor hangs up on it.
30405 - Fix an assert trigger for clients/servers handling resolves.
30408 Changes in version 0.0.9rc2 - 2004-11-24
30409 o Bugfixes on 0.0.9rc1:
30410 - I broke socks5 support while fixing the eof bug.
30411 - Allow unitless bandwidths and intervals; they default to bytes
30413 - New servers don't start out hibernating; they are active until
30414 they run out of bytes, so they have a better estimate of how
30415 long it takes, and so their operators can know they're working.
30418 Changes in version 0.0.9rc1 - 2004-11-23
30419 o Bugfixes on 0.0.8.1:
30420 - Finally fix a bug that's been plaguing us for a year:
30421 With high load, circuit package window was reaching 0. Whenever
30422 we got a circuit-level sendme, we were reading a lot on each
30423 socket, but only writing out a bit. So we would eventually reach
30424 eof. This would be noticed and acted on even when there were still
30425 bytes sitting in the inbuf.
30426 - When poll() is interrupted, we shouldn't believe the revents values.
30428 o Bugfixes on 0.0.9pre6:
30429 - Fix hibernate bug that caused pre6 to be broken.
30430 - Don't keep rephist info for routers that haven't had activity for
30431 24 hours. (This matters now that clients have keys, since we track
30433 - Never call close_temp_logs while validating log options.
30434 - Fix backslash-escaping on tor.sh.in and torctl.in.
30437 - Implement weekly/monthly/daily accounting: now you specify your
30438 hibernation properties by
30439 AccountingMax N bytes|KB|MB|GB|TB
30440 AccountingStart day|week|month [day] HH:MM
30441 Defaults to "month 1 0:00".
30442 - Let bandwidth and interval config options be specified as 5 bytes,
30443 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
30444 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
30445 get back to normal.)
30446 - If your requested entry or exit node has advertised bandwidth 0,
30448 - Be more greedy about filling up relay cells -- we try reading again
30449 once we've processed the stuff we read, in case enough has arrived
30450 to fill the last cell completely.
30451 - Apply NT service patch from Osamu Fujino. Still needs more work.
30454 Changes in version 0.0.9pre6 - 2004-11-15
30455 o Bugfixes on 0.0.8.1:
30456 - Fix assert failure on malformed socks4a requests.
30457 - Use identity comparison, not nickname comparison, to choose which
30458 half of circuit-ID-space each side gets to use. This is needed
30459 because sometimes we think of a router as a nickname, and sometimes
30460 as a hex ID, and we can't predict what the other side will do.
30461 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
30462 write() call will fail and we handle it there.
30463 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
30464 and smartlist_len, which are two major profiling offenders.
30466 o Bugfixes on 0.0.9pre5:
30467 - Fix a bug in read_all that was corrupting config files on windows.
30468 - When we're raising the max number of open file descriptors to
30469 'unlimited', don't log that we just raised it to '-1'.
30470 - Include event code with events, as required by control-spec.txt.
30471 - Don't give a fingerprint when clients do --list-fingerprint:
30472 it's misleading, because it will never be the same again.
30473 - Stop using strlcpy in tor_strndup, since it was slowing us
30475 - Remove warn on startup about missing cached-directory file.
30476 - Make kill -USR1 work again.
30477 - Hibernate if we start tor during the "wait for wakeup-time" phase
30478 of an accounting interval. Log our hibernation plans better.
30479 - Authoritative dirservers now also cache their directory, so they
30480 have it on start-up.
30483 - Fetch running-routers; cache running-routers; compress
30484 running-routers; serve compressed running-routers.z
30485 - Add NSI installer script contributed by J Doe.
30486 - Commit VC6 and VC7 workspace/project files.
30487 - Commit a tor.spec for making RPM files, with help from jbash.
30488 - Add contrib/torctl.in contributed by Glenn Fink.
30489 - Implement the control-spec's SAVECONF command, to write your
30490 configuration to torrc.
30491 - Get cookie authentication for the controller closer to working.
30492 - Include control-spec.txt in the tarball.
30493 - When set_conf changes our server descriptor, upload a new copy.
30494 But don't upload it too often if there are frequent changes.
30495 - Document authentication config in man page, and document signals
30497 - Clean up confusing parts of man page and torrc.sample.
30498 - Make expand_filename handle ~ and ~username.
30499 - Use autoconf to enable largefile support where necessary. Use
30500 ftello where available, since ftell can fail at 2GB.
30501 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
30502 log more informatively.
30503 - Give a slightly more useful output for "tor -h".
30504 - Refuse application socks connections to port 0.
30505 - Check clock skew for verified servers, but allow unverified
30506 servers and clients to have any clock skew.
30507 - Break DirFetchPostPeriod into:
30508 - DirFetchPeriod for fetching full directory,
30509 - StatusFetchPeriod for fetching running-routers,
30510 - DirPostPeriod for posting server descriptor,
30511 - RendPostPeriod for posting hidden service descriptors.
30512 - Make sure the hidden service descriptors are at a random offset
30513 from each other, to hinder linkability.
30516 Changes in version 0.0.9pre5 - 2004-11-09
30517 o Bugfixes on 0.0.9pre4:
30518 - Fix a seg fault in unit tests (doesn't affect main program).
30519 - Fix an assert bug where a hidden service provider would fail if
30520 the first hop of his rendezvous circuit was down.
30521 - Hidden service operators now correctly handle version 1 style
30522 INTRODUCE1 cells (nobody generates them still, so not a critical
30524 - If do_hup fails, actually notice.
30525 - Handle more errnos from accept() without closing the listener.
30526 Some OpenBSD machines were closing their listeners because
30527 they ran out of file descriptors.
30528 - Send resolve cells to exit routers that are running a new
30529 enough version of the resolve code to work right.
30530 - Better handling of winsock includes on non-MSV win32 compilers.
30531 - Some people had wrapped their tor client/server in a script
30532 that would restart it whenever it died. This did not play well
30533 with our "shut down if your version is obsolete" code. Now people
30534 don't fetch a new directory if their local cached version is
30536 - Make our autogen.sh work on ksh as well as bash.
30539 - Hibernation: New config option "AccountingMaxKB" lets you
30540 set how many KBytes per month you want to allow your server to
30541 consume. Rather than spreading those bytes out evenly over the
30542 month, we instead hibernate for some of the month and pop up
30543 at a deterministic time, work until the bytes are consumed, then
30544 hibernate again. Config option "MonthlyAccountingStart" lets you
30545 specify which day of the month your billing cycle starts on.
30546 - Control interface: a separate program can now talk to your
30547 client/server over a socket, and get/set config options, receive
30548 notifications of circuits and streams starting/finishing/dying,
30549 bandwidth used, etc. The next step is to get some GUIs working.
30550 Let us know if you want to help out. See doc/control-spec.txt .
30551 - Ship a contrib/tor-control.py as an example script to interact
30552 with the control port.
30553 - "tor --hash-password zzyxz" will output a salted password for
30554 use in authenticating to the control interface.
30555 - New log format in config:
30556 "Log minsev[-maxsev] stdout|stderr|syslog" or
30557 "Log minsev[-maxsev] file /var/foo"
30560 - DirPolicy config option, to let people reject incoming addresses
30561 from their dirserver.
30562 - "tor --list-fingerprint" will list your identity key fingerprint
30564 - Add "pass" target for RedirectExit, to make it easier to break
30565 out of a sequence of RedirectExit rules.
30566 - Clients now generate a TLS cert too, in preparation for having
30567 them act more like real nodes.
30568 - Ship src/win32/ in the tarball, so people can use it to build.
30569 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
30571 - New "router-status" line in directory, to better bind each verified
30572 nickname to its identity key.
30573 - Deprecate unofficial config option abbreviations, and abbreviations
30574 not on the command line.
30575 - Add a pure-C tor-resolve implementation.
30576 - Use getrlimit and friends to ensure we can reach MaxConn (currently
30577 1024) file descriptors.
30579 o Code security improvements, inspired by Ilja:
30580 - Replace sprintf with snprintf. (I think they were all safe, but
30582 - Replace strcpy/strncpy with strlcpy in more places.
30583 - Avoid strcat; use snprintf or strlcat instead.
30584 - snprintf wrapper with consistent (though not C99) overflow behavior.
30587 Changes in version 0.0.9pre4 - 2004-10-17
30588 o Bugfixes on 0.0.9pre3:
30589 - If the server doesn't specify an exit policy, use the real default
30590 exit policy, not reject *:*.
30591 - Ignore fascistfirewall when uploading/downloading hidden service
30592 descriptors, since we go through Tor for those; and when using
30593 an HttpProxy, since we assume it can reach them all.
30594 - When looking for an authoritative dirserver, use only the ones
30595 configured at boot. Don't bother looking in the directory.
30596 - The rest of the fix for get_default_conf_file() on older win32.
30597 - Make 'Routerfile' config option obsolete.
30600 - New 'MyFamily nick1,...' config option for a server to
30601 specify other servers that shouldn't be used in the same circuit
30602 with it. Only believed if nick1 also specifies us.
30603 - New 'NodeFamily nick1,nick2,...' config option for a client to
30604 specify nodes that it doesn't want to use in the same circuit.
30605 - New 'Redirectexit pattern address:port' config option for a
30606 server to redirect exit connections, e.g. to a local squid.
30609 Changes in version 0.0.9pre3 - 2004-10-13
30610 o Bugfixes on 0.0.8.1:
30611 - Better torrc example lines for dirbindaddress and orbindaddress.
30612 - Improved bounds checking on parsed ints (e.g. config options and
30613 the ones we find in directories.)
30614 - Better handling of size_t vs int, so we're more robust on 64
30616 - Fix the rest of the bug where a newly started OR would appear
30617 as unverified even after we've added his fingerprint and hupped
30619 - Fix a bug from 0.0.7: when read() failed on a stream, we would
30620 close it without sending back an end. So 'connection refused'
30621 would simply be ignored and the user would get no response.
30623 o Bugfixes on 0.0.9pre2:
30624 - Serving the cached-on-disk directory to people is bad. We now
30625 provide no directory until we've fetched a fresh one.
30626 - Workaround for bug on windows where cached-directories get crlf
30628 - Make get_default_conf_file() work on older windows too.
30629 - If we write a *:* exit policy line in the descriptor, don't write
30630 any more exit policy lines.
30633 - Use only 0.0.9pre1 and later servers for resolve cells.
30634 - Make the dirservers file obsolete.
30635 - Include a dir-signing-key token in directories to tell the
30636 parsing entity which key is being used to sign.
30637 - Remove the built-in bulky default dirservers string.
30638 - New config option "Dirserver %s:%d [fingerprint]", which can be
30639 repeated as many times as needed. If no dirservers specified,
30640 default to moria1,moria2,tor26.
30641 - Make moria2 advertise a dirport of 80, so people behind firewalls
30642 will be able to get a directory.
30643 - Http proxy support
30644 - Dirservers translate requests for http://%s:%d/x to /x
30645 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
30646 be routed through this host.
30647 - Clients ask for /tor/x rather than /x for new enough dirservers.
30648 This way we can one day coexist peacefully with apache.
30649 - Clients specify a "Host: %s%d" http header, to be compatible
30650 with more proxies, and so running squid on an exit node can work.
30653 Changes in version 0.0.8.1 - 2004-10-13
30655 - Fix a seg fault that can be triggered remotely for Tor
30656 clients/servers with an open dirport.
30657 - Fix a rare assert trigger, where routerinfos for entries in
30658 our cpath would expire while we're building the path.
30659 - Fix a bug in OutboundBindAddress so it (hopefully) works.
30660 - Fix a rare seg fault for people running hidden services on
30661 intermittent connections.
30662 - Fix a bug in parsing opt keywords with objects.
30663 - Fix a stale pointer assert bug when a stream detaches and
30665 - Fix a string format vulnerability (probably not exploitable)
30666 in reporting stats locally.
30667 - Fix an assert trigger: sometimes launching circuits can fail
30668 immediately, e.g. because too many circuits have failed recently.
30669 - Fix a compile warning on 64 bit platforms.
30672 Changes in version 0.0.9pre2 - 2004-10-03
30674 - Make fetching a cached directory work for 64-bit platforms too.
30675 - Make zlib.h a required header, not an optional header.
30678 Changes in version 0.0.9pre1 - 2004-10-01
30680 - Stop using separate defaults for no-config-file and
30681 empty-config-file. Now you have to explicitly turn off SocksPort,
30682 if you don't want it open.
30683 - Fix a bug in OutboundBindAddress so it (hopefully) works.
30684 - Improve man page to mention more of the 0.0.8 features.
30685 - Fix a rare seg fault for people running hidden services on
30686 intermittent connections.
30687 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
30689 - Fix more dns related bugs: send back resolve_failed and end cells
30690 more reliably when the resolve fails, rather than closing the
30691 circuit and then trying to send the cell. Also attach dummy resolve
30692 connections to a circuit *before* calling dns_resolve(), to fix
30693 a bug where cached answers would never be sent in RESOLVED cells.
30694 - When we run out of disk space, or other log writing error, don't
30695 crash. Just stop logging to that log and continue.
30696 - We were starting to daemonize before we opened our logs, so if
30697 there were any problems opening logs, we would complain to stderr,
30698 which wouldn't work, and then mysteriously exit.
30699 - Fix a rare bug where sometimes a verified OR would connect to us
30700 before he'd uploaded his descriptor, which would cause us to
30701 assign conn->nickname as though he's unverified. Now we look through
30702 the fingerprint list to see if he's there.
30703 - Fix a rare assert trigger, where routerinfos for entries in
30704 our cpath would expire while we're building the path.
30707 - Clients can ask dirservers for /dir.z to get a compressed version
30708 of the directory. Only works for servers running 0.0.9, of course.
30709 - Make clients cache directories and use them to seed their router
30710 lists at startup. This means clients have a datadir again.
30711 - Configuration infrastructure support for warning on obsolete
30713 - Respond to content-encoding headers by trying to uncompress as
30715 - Reply with a deflated directory when a client asks for "dir.z".
30716 We could use allow-encodings instead, but allow-encodings isn't
30717 specified in HTTP 1.0.
30718 - Raise the max dns workers from 50 to 100.
30719 - Discourage people from setting their dirfetchpostperiod more often
30720 than once per minute.
30721 - Protect dirservers from overzealous descriptor uploading -- wait
30722 10 seconds after directory gets dirty, before regenerating.
30725 Changes in version 0.0.8 - 2004-08-25
30726 o Port it to SunOS 5.9 / Athena
30729 Changes in version 0.0.8rc2 - 2004-08-20
30730 o Make it compile on cygwin again.
30731 o When picking unverified routers, skip those with low uptime and/or
30732 low bandwidth, depending on what properties you care about.
30735 Changes in version 0.0.8rc1 - 2004-08-18
30736 o Changes from 0.0.7.3:
30738 - Fix assert triggers: if the other side returns an address 0.0.0.0,
30739 don't put it into the client dns cache.
30740 - If a begin failed due to exit policy, but we believe the IP address
30741 should have been allowed, switch that router to exitpolicy reject *:*
30742 until we get our next directory.
30744 - Clients choose nodes proportional to advertised bandwidth.
30745 - Avoid using nodes with low uptime as introduction points.
30746 - Handle servers with dynamic IP addresses: don't replace
30747 options->Address with the resolved one at startup, and
30748 detect our address right before we make a routerinfo each time.
30749 - 'FascistFirewall' option to pick dirservers and ORs on specific
30750 ports; plus 'FirewallPorts' config option to tell FascistFirewall
30751 which ports are open. (Defaults to 80,443)
30752 - Be more aggressive about trying to make circuits when the network
30753 has changed (e.g. when you unsuspend your laptop).
30754 - Check for time skew on http headers; report date in response to
30756 - If the entrynode config line has only one node, don't pick it as
30758 - Add strict{entry|exit}nodes config options. If set to 1, then
30759 we refuse to build circuits that don't include the specified entry
30761 - OutboundBindAddress config option, to bind to a specific
30762 IP address for outgoing connect()s.
30763 - End truncated log entries (e.g. directories) with "[truncated]".
30765 o Patches to 0.0.8preX:
30767 - Patches to compile and run on win32 again (maybe)?
30768 - Fix crash when looking for ~/.torrc with no $HOME set.
30769 - Fix a race bug in the unit tests.
30770 - Handle verified/unverified name collisions better when new
30771 routerinfo's arrive in a directory.
30772 - Sometimes routers were getting entered into the stats before
30773 we'd assigned their identity_digest. Oops.
30774 - Only pick and establish intro points after we've gotten a
30777 - AllowUnverifiedNodes config option to let circuits choose no-name
30778 routers in entry,middle,exit,introduction,rendezvous positions.
30779 Allow middle and rendezvous positions by default.
30780 - Add a man page for tor-resolve.
30783 Changes in version 0.0.7.3 - 2004-08-12
30784 o Stop dnsworkers from triggering an assert failure when you
30785 ask them to resolve the host "".
30788 Changes in version 0.0.8pre3 - 2004-08-09
30789 o Changes from 0.0.7.2:
30790 - Allow multiple ORs with same nickname in routerlist -- now when
30791 people give us one identity key for a nickname, then later
30792 another, we don't constantly complain until the first expires.
30793 - Remember used bandwidth (both in and out), and publish 15-minute
30794 snapshots for the past day into our descriptor.
30795 - You can now fetch $DIRURL/running-routers to get just the
30796 running-routers line, not the whole descriptor list. (But
30797 clients don't use this yet.)
30798 - When people mistakenly use Tor as an http proxy, point them
30799 at the tor-doc.html rather than the INSTALL.
30800 - Remove our mostly unused -- and broken -- hex_encode()
30801 function. Use base16_encode() instead. (Thanks to Timo Lindfors
30802 for pointing out this bug.)
30803 - Rotate onion keys every 12 hours, not every 2 hours, so we have
30804 fewer problems with people using the wrong key.
30805 - Change the default exit policy to reject the default edonkey,
30806 kazaa, gnutella ports.
30807 - Add replace_file() to util.[ch] to handle win32's rename().
30809 o Changes from 0.0.8preX:
30810 - Fix two bugs in saving onion keys to disk when rotating, so
30811 hopefully we'll get fewer people using old onion keys.
30812 - Fix an assert error that was making SocksPolicy not work.
30813 - Be willing to expire routers that have an open dirport -- it's
30814 just the authoritative dirservers we want to not forget.
30815 - Reject tor-resolve requests for .onion addresses early, so we
30816 don't build a whole rendezvous circuit and then fail.
30817 - When you're warning a server that he's unverified, don't cry
30818 wolf unpredictably.
30819 - Fix a race condition: don't try to extend onto a connection
30820 that's still handshaking.
30821 - For servers in clique mode, require the conn to be open before
30822 you'll choose it for your path.
30823 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
30824 end relay cell, etc.
30825 - Measure bandwidth capacity over the last 24 hours, not just 12
30826 - Bugfix: authoritative dirservers were making and signing a new
30827 directory for each client, rather than reusing the cached one.
30830 Changes in version 0.0.8pre2 - 2004-08-04
30831 o Changes from 0.0.7.2:
30833 - Check directory signature _before_ you decide whether you're
30834 you're running an obsolete version and should exit.
30835 - Check directory signature _before_ you parse the running-routers
30836 list to decide who's running or verified.
30837 - Bugfixes and features:
30838 - Check return value of fclose while writing to disk, so we don't
30839 end up with broken files when servers run out of disk space.
30840 - Log a warning if the user uses an unsafe socks variant, so people
30841 are more likely to learn about privoxy or socat.
30842 - Dirservers now include RFC1123-style dates in the HTTP headers,
30843 which one day we will use to better detect clock skew.
30845 o Changes from 0.0.8pre1:
30846 - Make it compile without warnings again on win32.
30847 - Log a warning if you're running an unverified server, to let you
30848 know you might want to get it verified.
30849 - Only pick a default nickname if you plan to be a server.
30852 Changes in version 0.0.8pre1 - 2004-07-23
30854 - Made our unit tests compile again on OpenBSD 3.5, and tor
30855 itself compile again on OpenBSD on a sparc64.
30856 - We were neglecting milliseconds when logging on win32, so
30857 everything appeared to happen at the beginning of each second.
30859 o Protocol changes:
30860 - 'Extend' relay cell payloads now include the digest of the
30861 intended next hop's identity key. Now we can verify that we're
30862 extending to the right router, and also extend to routers we
30863 hadn't heard of before.
30866 - Tor nodes can now act as relays (with an advertised ORPort)
30867 without being manually verified by the dirserver operators.
30868 - Uploaded descriptors of unverified routers are now accepted
30869 by the dirservers, and included in the directory.
30870 - Verified routers are listed by nickname in the running-routers
30871 list; unverified routers are listed as "$<fingerprint>".
30872 - We now use hash-of-identity-key in most places rather than
30873 nickname or addr:port, for improved security/flexibility.
30874 - To avoid Sybil attacks, paths still use only verified servers.
30875 But now we have a chance to play around with hybrid approaches.
30876 - Nodes track bandwidth usage to estimate capacity (not used yet).
30877 - ClientOnly option for nodes that never want to become servers.
30878 - Directory caching.
30879 - "AuthoritativeDir 1" option for the official dirservers.
30880 - Now other nodes (clients and servers) will cache the latest
30881 directory they've pulled down.
30882 - They can enable their DirPort to serve it to others.
30883 - Clients will pull down a directory from any node with an open
30884 DirPort, and check the signature/timestamp correctly.
30885 - Authoritative dirservers now fetch directories from other
30886 authdirservers, to stay better synced.
30887 - Running-routers list tells who's down also, along with noting
30888 if they're verified (listed by nickname) or unverified (listed
30890 - Allow dirservers to serve running-router list separately.
30891 This isn't used yet.
30892 - ORs connect-on-demand to other ORs
30893 - If you get an extend cell to an OR you're not connected to,
30894 connect, handshake, and forward the create cell.
30895 - The authoritative dirservers stay connected to everybody,
30896 and everybody stays connected to 0.0.7 servers, but otherwise
30897 clients/servers expire unused connections after 5 minutes.
30898 - When servers get a sigint, they delay 30 seconds (refusing new
30899 connections) then exit. A second sigint causes immediate exit.
30900 - File and name management:
30901 - Look for .torrc if no CONFDIR "torrc" is found.
30902 - If no datadir is defined, then choose, make, and secure ~/.tor
30904 - If torrc not found, exitpolicy reject *:*.
30905 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
30906 - If no nickname is defined, derive default from hostname.
30907 - Rename secret key files, e.g. identity.key -> secret_id_key,
30908 to discourage people from mailing their identity key to tor-ops.
30909 - Refuse to build a circuit before the directory has arrived --
30910 it won't work anyway, since you won't know the right onion keys
30912 - Try other dirservers immediately if the one you try is down. This
30913 should tolerate down dirservers better now.
30914 - Parse tor version numbers so we can do an is-newer-than check
30915 rather than an is-in-the-list check.
30916 - New socks command 'resolve', to let us shim gethostbyname()
30918 - A 'tor_resolve' script to access the socks resolve functionality.
30919 - A new socks-extensions.txt doc file to describe our
30920 interpretation and extensions to the socks protocols.
30921 - Add a ContactInfo option, which gets published in descriptor.
30922 - Publish OR uptime in descriptor (and thus in directory) too.
30923 - Write tor version at the top of each log file
30924 - New docs in the tarball:
30926 - Document that you should proxy your SSL traffic too.
30929 Changes in version 0.0.7.2 - 2004-07-07
30930 o A better fix for the 0.0.0.0 problem, that will hopefully
30931 eliminate the remaining related assertion failures.
30934 Changes in version 0.0.7.1 - 2004-07-04
30935 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
30936 since internally we use 0.0.0.0 to signify "not yet resolved".
30939 Changes in version 0.0.7 - 2004-06-07
30940 o Updated the man page to reflect the new features.
30943 Changes in version 0.0.7rc2 - 2004-06-06
30944 o Changes from 0.0.7rc1:
30945 - Make it build on Win32 again.
30946 o Changes from 0.0.6.2:
30947 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
30951 Changes in version 0.0.7rc1 - 2004-06-02
30953 - On sighup, we were adding another log without removing the first
30954 one. So log messages would get duplicated n times for n sighups.
30955 - Several cases of using a connection after we'd freed it. The
30956 problem was that connections that are pending resolve are in both
30957 the pending_resolve tree, and also the circuit's resolving_streams
30958 list. When you want to remove one, you must remove it from both.
30959 - Fix a double-mark-for-close where an end cell arrived for a
30960 resolving stream, and then the resolve failed.
30961 - Check directory signatures based on name of signer, not on whom
30962 we got the directory from. This will let us cache directories more
30965 - Crank up some of our constants to handle more users.
30968 Changes in version 0.0.7pre1 - 2004-06-02
30969 o Fixes for crashes and other obnoxious bugs:
30970 - Fix an epipe bug: sometimes when directory connections failed
30971 to connect, we would give them a chance to flush before closing
30973 - When we detached from a circuit because of resolvefailed, we
30974 would immediately try the same circuit twice more, and then
30975 give up on the resolve thinking we'd tried three different
30977 - Limit the number of intro circuits we'll attempt to build for a
30978 hidden service per 15-minute period.
30979 - Check recommended-software string *early*, before actually parsing
30980 the directory. Thus we can detect an obsolete version and exit,
30981 even if the new directory format doesn't parse.
30982 o Fixes for security bugs:
30983 - Remember which nodes are dirservers when you startup, and if a
30984 random OR enables his dirport, don't automatically assume he's
30985 a trusted dirserver.
30987 - Directory connections were asking the wrong poll socket to
30988 start writing, and not asking themselves to start writing.
30989 - When we detached from a circuit because we sent a begin but
30990 didn't get a connected, we would use it again the first time;
30991 but after that we would correctly switch to a different one.
30992 - Stop warning when the first onion decrypt attempt fails; they
30993 will sometimes legitimately fail now that we rotate keys.
30994 - Override unaligned-access-ok check when $host_cpu is ia64 or
30995 arm. Apparently they allow it but the kernel whines.
30996 - Dirservers try to reconnect periodically too, in case connections
30998 - Fix some memory leaks in directory servers.
30999 - Allow backslash in Win32 filenames.
31000 - Made Tor build complain-free on FreeBSD, hopefully without
31001 breaking other BSD builds. We'll see.
31003 - Doxygen markup on all functions and global variables.
31004 - Make directory functions update routerlist, not replace it. So
31005 now directory disagreements are not so critical a problem.
31006 - Remove the upper limit on number of descriptors in a dirserver's
31007 directory (not that we were anywhere close).
31008 - Allow multiple logfiles at different severity ranges.
31009 - Allow *BindAddress to specify ":port" rather than setting *Port
31010 separately. Allow multiple instances of each BindAddress config
31011 option, so you can bind to multiple interfaces if you want.
31012 - Allow multiple exit policy lines, which are processed in order.
31013 Now we don't need that huge line with all the commas in it.
31014 - Enable accept/reject policies on SOCKS connections, so you can bind
31015 to 0.0.0.0 but still control who can use your OP.
31018 Changes in version 0.0.6.2 - 2004-05-16
31019 o Our integrity-checking digest was checking only the most recent cell,
31020 not the previous cells like we'd thought.
31021 Thanks to Stefan Mark for finding the flaw!
31024 Changes in version 0.0.6.1 - 2004-05-06
31025 o Fix two bugs in our AES counter-mode implementation (this affected
31026 onion-level stream encryption, but not TLS-level). It turns
31027 out we were doing something much more akin to a 16-character
31028 polyalphabetic cipher. Oops.
31029 Thanks to Stefan Mark for finding the flaw!
31030 o Retire moria3 as a directory server, and add tor26 as a directory
31034 Changes in version 0.0.6 - 2004-05-02
31035 [version bump only]
31038 Changes in version 0.0.6rc4 - 2004-05-01
31039 o Update the built-in dirservers list to use the new directory format
31040 o Fix a rare seg fault: if a node offering a hidden service attempts
31041 to build a circuit to Alice's rendezvous point and fails before it
31042 reaches the last hop, it retries with a different circuit, but
31044 o Handle windows socket errors correctly.
31047 Changes in version 0.0.6rc3 - 2004-04-28
31048 o Don't expire non-general excess circuits (if we had enough
31049 circuits open, we were expiring rendezvous circuits -- even
31050 when they had a stream attached. oops.)
31051 o Fetch randomness from /dev/urandom better (not via fopen/fread)
31052 o Better debugging for tls errors
31053 o Some versions of openssl have an SSL_pending function that erroneously
31054 returns bytes when there is a non-application record pending.
31055 o Set Content-Type on the directory and hidserv descriptor.
31056 o Remove IVs from cipher code, since AES-ctr has none.
31057 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
31058 o We were using an array of length zero in a few places.
31059 o win32's gethostbyname can't resolve an IP to an IP.
31060 o win32's close can't close a socket.
31063 Changes in version 0.0.6rc2 - 2004-04-26
31064 o Fix a bug where we were closing tls connections intermittently.
31065 It turns out openssl keeps its errors around -- so if an error
31066 happens, and you don't ask about it, and then another openssl
31067 operation happens and succeeds, and you ask if there was an error,
31068 it tells you about the first error. Fun fun.
31069 o Fix a bug that's been lurking since 27 may 03 (!)
31070 When passing back a destroy cell, we would use the wrong circ id.
31071 'Mostly harmless', but still worth fixing.
31072 o Since we don't support truncateds much, don't bother sending them;
31073 just close the circ.
31074 o check for <machine/limits.h> so we build on NetBSD again (I hope).
31075 o don't crash if a conn that sent a begin has suddenly lost its circuit
31076 (this was quite rare).
31079 Changes in version 0.0.6rc1 - 2004-04-25
31080 o We now rotate link (tls context) keys and onion keys.
31081 o CREATE cells now include oaep padding, so you can tell
31082 if you decrypted them correctly.
31083 o Add bandwidthburst to server descriptor.
31084 o Directories now say which dirserver signed them.
31085 o Use a tor_assert macro that logs failed assertions too.
31088 Changes in version 0.0.6pre5 - 2004-04-18
31089 o changes from 0.0.6pre4:
31090 - make tor build on broken freebsd 5.2 installs
31091 - fix a failed assert when you try an intro point, get a nack, and try
31092 a second one and it works.
31093 - when alice uses a port that the hidden service doesn't accept,
31094 it now sends back an end cell (denied by exit policy). otherwise
31095 alice would just have to wait to time out.
31096 - fix another rare bug: when we had tried all the intro
31097 points for a hidden service, we fetched the descriptor
31098 again, but we left our introcirc thinking it had already
31099 sent an intro, so it kept waiting for a response...
31100 - bugfix: when you sleep your hidden-service laptop, as soon
31101 as it wakes up it tries to upload a service descriptor, but
31102 socketpair fails for some reason (localhost not up yet?).
31103 now we simply give up on that upload, and we'll try again later.
31104 i'd still like to find the bug though.
31105 - if an intro circ waiting for an ack dies before getting one, then
31107 - we were reusing stale service descriptors and refetching usable
31111 Changes in version 0.0.6pre4 - 2004-04-14
31112 o changes from 0.0.6pre3:
31113 - when bob fails to connect to the rendezvous point, and his
31114 circ didn't fail because of the rendezvous point itself, then
31115 he retries a couple of times
31116 - we expire introduction and rendezvous circs more thoroughly
31117 (sometimes they were hanging around forever)
31118 - we expire unattached rendezvous streams that have been around
31119 too long (they were sticking around forever).
31120 - fix a measly fencepost error that was crashing everybody with
31124 Changes in version 0.0.6pre3 - 2004-04-14
31125 o changes from 0.0.6pre2:
31126 - make hup work again
31127 - fix some memory leaks for dirservers
31128 - allow more skew in rendezvous descriptor timestamps, to help
31129 handle people like blanu who don't know what time it is
31130 - normal circs are 3 hops, but some rend/intro circs are 4, if
31131 the initiator doesn't get to choose the last hop
31132 - send acks for introductions, so alice can know whether to try
31134 - bob publishes intro points more correctly
31135 o changes from 0.0.5:
31136 - fix an assert trigger that's been plaguing us since the days
31137 of 0.0.2prexx (thanks weasel!)
31138 - retry stream correctly when we fail to connect because of
31139 exit-policy-reject (should try another) or can't-resolve-address
31140 (also should try another, because dns on random internet servers
31142 - when we hup a dirserver and we've *removed* a server from the
31143 approved-routers list, now we remove that server from the
31144 in-memory directories too
31147 Changes in version 0.0.6pre2 - 2004-04-08
31148 o We fixed our base32 implementation. Now it works on all architectures.
31151 Changes in version 0.0.6pre1 - 2004-04-08
31153 - Hidden services and rendezvous points are implemented. Go to
31154 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
31155 hidden services. (This only works via a socks4a proxy such as
31156 Privoxy, and currently it's quite slow.)
31159 Changes in version 0.0.5 - 2004-03-30
31160 [version bump only]
31163 Changes in version 0.0.5rc3 - 2004-03-29
31164 o Install torrc as torrc.sample -- we no longer clobber your
31166 o Re-enable recommendedversion checking (we broke it in rc2, oops)
31167 o Add in a 'notice' log level for things the operator should hear
31168 but that aren't warnings
31171 Changes in version 0.0.5rc2 - 2004-03-29
31172 o Hold socks connection open until reply is flushed (if possible)
31173 o Make exit nodes resolve IPs to IPs immediately, rather than asking
31174 the dns farm to do it.
31175 o Fix c99 aliasing warnings in rephist.c
31176 o Don't include server descriptors that are older than 24 hours in the
31178 o Give socks 'reject' replies their whole 15s to attempt to flush,
31179 rather than seeing the 60s timeout and assuming the flush had failed.
31180 o Clean automake droppings from the cvs repository
31183 Changes in version 0.0.5rc1 - 2004-03-28
31184 o Fix mangled-state bug in directory fetching (was causing sigpipes).
31185 o Only build circuits after we've fetched the directory: clients were
31186 using only the directory servers before they'd fetched a directory.
31187 This also means longer startup time; so it goes.
31188 o Fix an assert trigger where an OP would fail to handshake, and we'd
31189 expect it to have a nickname.
31190 o Work around a tsocks bug: do a socks reject when AP connection dies
31191 early, else tsocks goes into an infinite loop.
31194 Changes in version 0.0.4 - 2004-03-26
31195 o When connecting to a dirserver or OR and the network is down,
31199 Changes in version 0.0.3 - 2004-03-26
31200 o Warn and fail if server chose a nickname with illegal characters
31201 o Port to Solaris and Sparc:
31202 - include missing header fcntl.h
31203 - have autoconf find -lsocket -lnsl automatically
31204 - deal with hardware word alignment
31205 - make uname() work (solaris has a different return convention)
31206 - switch from using signal() to sigaction()
31207 o Preliminary work on reputation system:
31208 - Keep statistics on success/fail of connect attempts; they're published
31209 by kill -USR1 currently.
31210 - Add a RunTesting option to try to learn link state by creating test
31211 circuits, even when SocksPort is off.
31212 - Remove unused open circuits when there are too many.
31215 Changes in version 0.0.2 - 2004-03-19
31216 - Include strlcpy and strlcat for safer string ops
31217 - define INADDR_NONE so we compile (but still not run) on solaris
31220 Changes in version 0.0.2pre27 - 2004-03-14
31222 - Allow internal tor networks (we were rejecting internal IPs,
31223 now we allow them if they're set explicitly).
31224 - And fix a few endian issues.
31227 Changes in version 0.0.2pre26 - 2004-03-14
31229 - If a stream times out after 15s without a connected cell, don't
31230 try that circuit again: try a new one.
31231 - Retry streams at most 4 times. Then give up.
31232 - When a dirserver gets a descriptor from an unknown router, it
31233 logs its fingerprint (so the dirserver operator can choose to
31234 accept it even without mail from the server operator).
31235 - Inform unapproved servers when we reject their descriptors.
31236 - Make tor build on Windows again. It works as a client, who knows
31238 - Clearer instructions in the torrc for how to set up a server.
31239 - Be more efficient about reading fd's when our global token bucket
31240 (used for rate limiting) becomes empty.
31242 - Stop asserting that computers always go forward in time. It's
31244 - When we sent a cell (e.g. destroy) and then marked an OR connection
31245 expired, we might close it before finishing a flush if the other
31246 side isn't reading right then.
31247 - Don't allow dirservers to start if they haven't defined
31248 RecommendedVersions
31249 - We were caching transient dns failures. Oops.
31250 - Prevent servers from publishing an internal IP as their address.
31251 - Address a strcat vulnerability in circuit.c
31254 Changes in version 0.0.2pre25 - 2004-03-04
31256 - Put the OR's IP in its router descriptor, not its fqdn. That way
31257 we'll stop being stalled by gethostbyname for nodes with flaky dns,
31260 - If the user typed in an address that didn't resolve, the server
31264 Changes in version 0.0.2pre24 - 2004-03-03
31266 - Fix an assertion failure in dns.c, where we were trying to dequeue
31267 a pending dns resolve even if it wasn't pending
31268 - Fix a spurious socks5 warning about still trying to write after the
31269 connection is finished.
31270 - Hold certain marked_for_close connections open until they're finished
31271 flushing, rather than losing bytes by closing them too early.
31272 - Correctly report the reason for ending a stream
31273 - Remove some duplicate calls to connection_mark_for_close
31274 - Put switch_id and start_daemon earlier in the boot sequence, so it
31275 will actually try to chdir() to options.DataDirectory
31276 - Make 'make test' exit(1) if a test fails; fix some unit tests
31277 - Make tor fail when you use a config option it doesn't know about,
31278 rather than warn and continue.
31279 - Make --version work
31280 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
31283 Changes in version 0.0.2pre23 - 2004-02-29
31285 - Print a statement when the first circ is finished, so the user
31286 knows it's working.
31287 - If a relay cell is unrecognized at the end of the circuit,
31288 send back a destroy. (So attacks to mutate cells are more
31290 - New config option 'excludenodes' to avoid certain nodes for circuits.
31291 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
31292 so you can collect coredumps there.
31294 - Fix a bug in tls flushing where sometimes data got wedged and
31295 didn't flush until more data got sent. Hopefully this bug was
31296 a big factor in the random delays we were seeing.
31297 - Make 'connected' cells include the resolved IP, so the client
31298 dns cache actually gets populated.
31299 - Disallow changing from ORPort=0 to ORPort>0 on hup.
31300 - When we time-out on a stream and detach from the circuit, send an
31301 end cell down it first.
31302 - Only warn about an unknown router (in exitnodes, entrynodes,
31303 excludenodes) after we've fetched a directory.
31306 Changes in version 0.0.2pre22 - 2004-02-26
31308 - Servers publish less revealing uname information in descriptors.
31309 - More memory tracking and assertions, to crash more usefully when
31311 - If the default torrc isn't there, just use some default defaults.
31312 Plus provide an internal dirservers file if they don't have one.
31313 - When the user tries to use Tor as an http proxy, give them an http
31314 501 failure explaining that we're a socks proxy.
31315 - Dump a new router.desc on hup, to help confused people who change
31316 their exit policies and then wonder why router.desc doesn't reflect
31318 - Clean up the generic tor.sh init script that we ship with.
31320 - If the exit stream is pending on the resolve, and a destroy arrives,
31321 then the stream wasn't getting removed from the pending list. I
31322 think this was the one causing recent server crashes.
31323 - Use a more robust poll on OSX 10.3, since their poll is flaky.
31324 - When it couldn't resolve any dirservers, it was useless from then on.
31325 Now it reloads the RouterFile (or default dirservers) if it has no
31327 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
31328 many users don't even *have* a /usr/local/sbin/.
31331 Changes in version 0.0.2pre21 - 2004-02-18
31333 - There's a ChangeLog file that actually reflects the changelog.
31334 - There's a 'torify' wrapper script, with an accompanying
31335 tor-tsocks.conf, that simplifies the process of using tsocks for
31336 tor. It even has a man page.
31337 - The tor binary gets installed to sbin rather than bin now.
31338 - Retry streams where the connected cell hasn't arrived in 15 seconds
31339 - Clean up exit policy handling -- get the default out of the torrc,
31340 so we can update it without forcing each server operator to fix
31342 - Allow imaps and pop3s in default exit policy
31344 - Prevent picking middleman nodes as the last node in the circuit
31347 Changes in version 0.0.2pre20 - 2004-01-30
31349 - We now have a deb package, and it's in debian unstable. Go to
31350 it, apt-getters. :)
31351 - I've split the TotalBandwidth option into BandwidthRate (how many
31352 bytes per second you want to allow, long-term) and
31353 BandwidthBurst (how many bytes you will allow at once before the cap
31354 kicks in). This better token bucket approach lets you, say, set
31355 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
31356 performance while not exceeding your monthly bandwidth quota.
31357 - Push out a tls record's worth of data once you've got it, rather
31358 than waiting until you've read everything waiting to be read. This
31359 may improve performance by pipelining better. We'll see.
31360 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
31361 from failed circuits (if they haven't been connected yet) and attach
31363 - Expire old streams that haven't managed to connect. Some day we'll
31364 have them reattach to new circuits instead.
31367 - Fix several memory leaks that were causing servers to become bloated
31369 - Fix a few very rare assert triggers. A few more remain.
31370 - Setuid to User _before_ complaining about running as root.
31373 Changes in version 0.0.2pre19 - 2004-01-07
31375 - Fix deadlock condition in dns farm. We were telling a child to die by
31376 closing the parent's file descriptor to him. But newer children were
31377 inheriting the open file descriptor from the parent, and since they
31378 weren't closing it, the socket never closed, so the child never read
31379 eof, so he never knew to exit. Similarly, dns workers were holding
31380 open other sockets, leading to all sorts of chaos.
31381 - New cleaner daemon() code for forking and backgrounding.
31382 - If you log to a file, it now prints an entry at the top of the
31383 logfile so you know it's working.
31384 - The onionskin challenge length was 30 bytes longer than necessary.
31385 - Started to patch up the spec so it's not quite so out of date.
31388 Changes in version 0.0.2pre18 - 2004-01-02
31390 - Fix endian issues with the 'integrity' field in the relay header.
31391 - Fix a potential bug where connections in state
31392 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
31395 Changes in version 0.0.2pre17 - 2003-12-30
31397 - Made --debuglogfile (or any second log file, actually) work.
31398 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
31399 adversary could force us into an infinite loop.
31402 - Each onionskin handshake now includes a hash of the computed key,
31403 to prove the server's identity and help perfect forward secrecy.
31404 - Changed cell size from 256 to 512 bytes (working toward compatibility
31406 - Changed cell length to 2 bytes, and moved it to the relay header.
31407 - Implemented end-to-end integrity checking for the payloads of
31409 - Separated streamid from 'recognized' (otherwise circuits will get
31410 messed up when we try to have streams exit from the middle). We
31411 use the integrity-checking to confirm that a cell is addressed to
31413 - Randomize the initial circid and streamid values, so an adversary who
31414 breaks into a node can't learn how many circuits or streams have
31418 Changes in version 0.0.2pre16 - 2003-12-14
31420 - Fixed a bug that made HUP trigger an assert
31421 - Fixed a bug where a circuit that immediately failed wasn't being
31422 counted as a failed circuit in counting retries.
31425 - Now we close the circuit when we get a truncated cell: otherwise we're
31426 open to an anonymity attack where a bad node in the path truncates
31427 the circuit and then we open streams at him.
31428 - Add port ranges to exit policies
31429 - Add a conservative default exit policy
31430 - Warn if you're running tor as root
31431 - on HUP, retry OR connections and close/rebind listeners
31432 - options.EntryNodes: try these nodes first when picking the first node
31433 - options.ExitNodes: if your best choices happen to include any of
31434 your preferred exit nodes, you choose among just those preferred
31436 - options.ExcludedNodes: nodes that are never picked in path building
31439 Changes in version 0.0.2pre15 - 2003-12-03
31440 o Robustness and bugfixes:
31441 - Sometimes clients would cache incorrect DNS resolves, which would
31442 really screw things up.
31443 - An OP that goes offline would slowly leak all its sockets and stop
31445 - A wide variety of bugfixes in exit node selection, exit policy
31446 handling, and processing pending streams when a new circuit is
31448 - Pick nodes for a path only from those the directory says are up
31449 - Choose randomly from all running dirservers, not always the first one
31450 - Increase allowed http header size for directory fetch.
31451 - Stop writing to stderr (if we're daemonized it will be closed).
31452 - Enable -g always, so cores will be more useful to me.
31453 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
31456 - Wrote a man page. It lists commonly used options.
31459 - Change default loglevel to warn.
31460 - Make PidFile default to null rather than littering in your CWD.
31461 - OnionRouter config option is now obsolete. Instead it just checks
31463 - Moved to a single unified torrc file for both clients and servers.
31466 Changes in version 0.0.2pre14 - 2003-11-29
31467 o Robustness and bugfixes:
31468 - Force the admin to make the DataDirectory himself
31469 - to get ownership/permissions right
31470 - so clients no longer make a DataDirectory and then never use it
31471 - fix bug where a client who was offline for 45 minutes would never
31472 pull down a directory again
31473 - fix (or at least hide really well) the dns assert bug that was
31474 causing server crashes
31475 - warnings and improved robustness wrt clockskew for certs
31476 - use the native daemon(3) to daemonize, when available
31477 - exit if bind() fails
31478 - exit if neither socksport nor orport is defined
31479 - include our own tor_timegm (Win32 doesn't have its own)
31480 - bugfix for win32 with lots of connections
31481 - fix minor bias in PRNG
31482 - make dirserver more robust to corrupt cached directory
31485 - Wrote the design document (woo)
31487 o Circuit building and exit policies:
31488 - Circuits no longer try to use nodes that the directory has told them
31490 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
31491 bitcounts (18.0.0.0/8).
31492 - Make AP connections standby for a circuit if no suitable circuit
31493 exists, rather than failing
31494 - Circuits choose exit node based on addr/port, exit policies, and
31495 which AP connections are standing by
31496 - Bump min pathlen from 2 to 3
31497 - Relay end cells have a payload to describe why the stream ended.
31498 - If the stream failed because of exit policy, try again with a new
31500 - Clients have a dns cache to remember resolved addresses.
31501 - Notice more quickly when we have no working circuits
31504 - APPort is now called SocksPort
31505 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
31507 - RecommendedVersions is now a config variable rather than
31508 hardcoded (for dirservers)
31509 - Reloads config on HUP
31510 - Usage info on -h or --help
31511 - If you set User and Group config vars, it'll setu/gid to them.
31514 Changes in version 0.0.2pre13 - 2003-10-19
31515 o General stability:
31516 - SSL_write no longer fails when it returns WANTWRITE and the number
31517 of bytes in the buf has changed by the next SSL_write call.
31518 - Fix segfault fetching directory when network is down
31519 - Fix a variety of minor memory leaks
31520 - Dirservers reload the fingerprints file on HUP, so I don't have
31521 to take down the network when I approve a new router
31522 - Default server config file has explicit Address line to specify fqdn
31525 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
31526 - Make listener connections not ever alloc bufs
31528 o Autoconf improvements:
31529 - don't clobber an external CFLAGS in ./configure
31530 - Make install now works
31531 - create var/lib/tor on make install
31532 - autocreate a tor.sh initscript to help distribs
31533 - autocreate the torrc and sample-server-torrc with correct paths
31535 o Log files and Daemonizing now work:
31536 - If --DebugLogFile is specified, log to it at -l debug
31537 - If --LogFile is specified, use it instead of commandline
31538 - If --RunAsDaemon is set, tor forks and backgrounds on startup