1 This document summarizes new features and bugfixes in each stable
2 release of Tor. If you want to see more detailed descriptions of the
3 changes in each development snapshot, see the ChangeLog file.
5 Changes in version 0.4.1.6 - 2019-09-19
6 This release backports several bugfixes to improve stability and
7 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
8 or experiencing reliability issues with single onion services, should
11 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
12 - Tolerate systems (including some Android installations) where
13 madvise and MADV_DONTDUMP are available at build-time, but not at
14 run time. Previously, these systems would notice a failed syscall
15 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
16 - Tolerate systems (including some Linux installations) where
17 madvise and/or MADV_DONTFORK are available at build-time, but not
18 at run time. Previously, these systems would notice a failed
19 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
21 o Minor features (stem tests, backport from 0.4.2.1-alpha):
22 - Change "make test-stem" so it only runs the stem tests that use
23 tor. This change makes test-stem faster and more reliable. Closes
26 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
27 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
28 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
30 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
31 - Add more stub functions to fix compilation on Android with link-
32 time optimization when --disable-module-dirauth is used.
33 Previously, these compilation settings would make the compiler
34 look for functions that didn't exist. Fixes bug 31552; bugfix
36 - Suppress spurious float-conversion warnings from GCC when calling
37 floating-point classifier functions on FreeBSD. Fixes part of bug
38 31687; bugfix on 0.3.1.5-alpha.
40 o Minor bugfixes (controller protocol):
41 - Fix the MAPADDRESS controller command to accept one or more
42 arguments. Previously, it required two or more arguments, and ignored
43 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
45 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
46 - When tor is missing descriptors for some primary entry guards,
47 make the log message less alarming. It's normal for descriptors to
48 expire, as long as tor fetches new ones soon after. Fixes bug
49 31657; bugfix on 0.3.3.1-alpha.
51 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
52 - Change log level of message "Hash of session info was not as
53 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
56 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
57 - Correctly exclude a redundant rust build job in Travis. Fixes bug
58 31463; bugfix on 0.3.5.4-alpha.
60 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
61 - Always retry v2 single onion service intro and rend circuits with
62 a 3-hop path. Previously, v2 single onion services used a 3-hop
63 path when rendezvous circuits were retried after a remote or
64 delayed failure, but a 1-hop path for immediate retries. Fixes bug
65 23818; bugfix on 0.2.9.3-alpha.
67 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
68 - Always retry v3 single onion service intro and rend circuits with
69 a 3-hop path. Previously, v3 single onion services used a 3-hop
70 path when rend circuits were retried after a remote or delayed
71 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
72 bugfix on 0.3.2.1-alpha.
73 - Make v3 single onion services fall back to a 3-hop intro, when all
74 intro points are unreachable via a 1-hop path. Previously, v3
75 single onion services failed when all intro nodes were unreachable
76 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
78 o Documentation (backport from 0.4.2.1-alpha):
79 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
80 notice.html so that operators no longer have to host it
81 themselves. Closes ticket 31089.
84 Changes in version 0.4.1.5 - 2019-08-20
85 This is the first stable release in the 0.4.1.x series. This series
86 adds experimental circuit-level padding, authenticated SENDME cells to
87 defend against certain attacks, and several performance improvements
88 to save on CPU consumption. It fixes bugs in bootstrapping and v3
89 onion services. It also includes numerous smaller features and
90 bugfixes on earlier versions.
92 Per our support policy, we will support the 0.4.1.x series for nine
93 months, or until three months after the release of a stable 0.4.2.x:
94 whichever is longer. If you need longer-term support, please stick
95 with 0.3.5.x, which will we plan to support until Feb 2022.
97 Below are the changes since 0.4.0.5. For a list of only the changes
98 since 0.4.1.4-rc, see the ChangeLog file.
100 o Directory authority changes:
101 - The directory authority "dizum" has a new IP address. Closes
104 o Major features (circuit padding):
105 - Onion service clients now add padding cells at the start of their
106 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
107 look more like general purpose Exit traffic. The overhead for this
108 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
109 extra upstream cell and 10 downstream cells for INTRODUCE
110 circuits. This feature is only enabled when also supported by the
111 circuit's middle node. (Clients may specify fixed middle nodes
112 with the MiddleNodes option, and may force-disable this feature
113 with the CircuitPadding option.) Closes ticket 28634.
115 o Major features (code organization):
116 - Tor now includes a generic publish-subscribe message-passing
117 subsystem that we can use to organize intermodule dependencies. We
118 hope to use this to reduce dependencies between modules that don't
119 need to be related, and to generally simplify our codebase. Closes
122 o Major features (controller protocol):
123 - Controller commands are now parsed using a generalized parsing
124 subsystem. Previously, each controller command was responsible for
125 parsing its own input, which led to strange inconsistencies.
128 o Major features (flow control):
129 - Implement authenticated SENDMEs as detailed in proposal 289. A
130 SENDME cell now includes the digest of the traffic that it
131 acknowledges, so that once an end point receives the SENDME, it
132 can confirm the other side's knowledge of the previous cells that
133 were sent, and prevent certain types of denial-of-service attacks.
134 This behavior is controlled by two new consensus parameters: see
135 the proposal for more details. Fixes ticket 26288.
137 o Major features (performance):
138 - Our node selection algorithm now excludes nodes in linear time.
139 Previously, the algorithm was quadratic, which could slow down
140 heavily used onion services. Closes ticket 30307.
142 o Major features (performance, RNG):
143 - Tor now constructs a fast secure pseudorandom number generator for
144 each thread, to use when performance is critical. This PRNG is
145 based on AES-CTR, using a buffering construction similar to
146 libottery and the (newer) OpenBSD arc4random() code. It
147 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
148 small outputs. Although we believe it to be cryptographically
149 strong, we are only using it when necessary for performance.
150 Implements tickets 29023 and 29536.
152 o Major bugfixes (bridges):
153 - Consider our directory information to have changed when our list
154 of bridges changes. Previously, Tor would not re-compute the
155 status of its directory information when bridges changed, and
156 therefore would not realize that it was no longer able to build
157 circuits. Fixes part of bug 29875.
158 - Do not count previously configured working bridges towards our
159 total of working bridges. Previously, when Tor's list of bridges
160 changed, it would think that the old bridges were still usable,
161 and delay fetching router descriptors for the new ones. Fixes part
162 of bug 29875; bugfix on 0.3.0.1-alpha.
164 o Major bugfixes (circuit build, guard):
165 - On relays, properly check that a padding machine is absent before
166 logging a warning about it being absent. Fixes bug 30649; bugfix
168 - When considering upgrading circuits from "waiting for guard" to
169 "open", always ignore circuits that are marked for close. Otherwise,
170 we can end up in the situation where a subsystem is notified that
171 a closing circuit has just opened, leading to undesirable
172 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
174 o Major bugfixes (onion service reachability):
175 - Properly clean up the introduction point map when circuits change
176 purpose from onion service circuits to pathbias, measurement, or
177 other circuit types. This should fix some service-side instances
178 of introduction point failure. Fixes bug 29034; bugfix
181 o Major bugfixes (onion service v3):
182 - Fix an unreachable bug in which an introduction point could try to
183 send an INTRODUCE_ACK with a status code that Trunnel would refuse
184 to encode, leading the relay to assert(). We've consolidated the
185 ABI values into Trunnel now. Fixes bug 30454; bugfix
187 - Clients can now handle unknown status codes from INTRODUCE_ACK
188 cells. (The NACK behavior will stay the same.) This will allow us
189 to extend status codes in the future without breaking the normal
190 client behavior. Fixes another part of bug 30454; bugfix
193 o Minor features (authenticated SENDME):
194 - Ensure that there is enough randomness on every circuit to prevent
195 an attacker from successfully predicting the hashes they will need
196 to include in authenticated SENDME cells. At a random interval, if
197 we have not sent randomness already, we now leave some extra space
198 at the end of a cell that we can fill with random bytes. Closes
201 o Minor features (circuit padding logging):
202 - Demote noisy client-side warn logs about circuit padding to protocol
203 warnings. Add additional log messages and circuit ID fields to help
204 with bug 30992 and any other future issues.
206 o Minor features (circuit padding):
207 - We now use a fast PRNG when scheduling circuit padding. Part of
209 - Allow the padding machine designer to pick the edges of their
210 histogram instead of trying to compute them automatically using an
211 exponential formula. Resolves some undefined behavior in the case
212 of small histograms and allows greater flexibility on machine
213 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
214 - Allow circuit padding machines to hold a circuit open until they
215 are done padding it. Closes ticket 28780.
217 o Minor features (compile-time modules):
218 - Add a "--list-modules" command to print a list of which compile-
219 time modules are enabled. Closes ticket 30452.
221 o Minor features (continuous integration):
222 - Our Travis configuration now uses Chutney to run some network
223 integration tests automatically. Closes ticket 29280.
224 - When running coverage builds on Travis, we now set
225 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
227 - Remove sudo configuration lines from .travis.yml as they are no
228 longer needed with current Travis build environment. Resolves
230 - In Travis, show stem's tor log after failure. Closes ticket 30234.
232 o Minor features (controller):
233 - Add onion service version 3 support to the HSFETCH command.
234 Previously, only version 2 onion services were supported. Closes
235 ticket 25417. Patch by Neel Chauhan.
237 o Minor features (debugging):
238 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
239 logging of additional information during assert failure. Now we
240 can use format strings to include information for trouble
241 shooting. Resolves ticket 29662.
243 o Minor features (defense in depth):
244 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
245 case a bug causes them to be used later. Closes ticket 30176.
246 Patch from Tobias Stoeckmann.
247 - Tor now uses a cryptographically strong PRNG even for decisions
248 that we do not believe are security-sensitive. Previously, for
249 performance reasons, we had used a trivially predictable linear
250 congruential generator algorithm for certain load-balancing and
251 statistical sampling decisions. Now we use our fast RNG in those
252 cases. Closes ticket 29542.
254 o Minor features (developer tools):
255 - Tor's "practracker" test script now checks for files and functions
256 that seem too long and complicated. Existing overlong functions
257 and files are accepted for now, but should eventually be
258 refactored. Closes ticket 29221.
259 - Add some scripts used for git maintenance to scripts/git. Closes
261 - Call practracker from pre-push and pre-commit git hooks to let
262 developers know if they made any code style violations. Closes
264 - Add a script to check that each header has a well-formed and
265 unique guard macro. Closes ticket 29756.
267 o Minor features (fallback directory list):
268 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
269 in December 2018 (of which ~122 were still functional), with a
270 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
271 in June 2019. Closes ticket 28795.
273 o Minor features (geoip):
274 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
275 Country database. Closes ticket 30852.
276 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
277 Country database. Closes ticket 30522.
279 o Minor features (HTTP tunnel):
280 - Return an informative web page when the HTTPTunnelPort is used as
281 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
283 o Minor features (IPv6, v3 onion services):
284 - Make v3 onion services put IPv6 addresses in service descriptors.
285 Before this change, service descriptors only contained IPv4
286 addresses. Implements 26992.
288 o Minor features (logging):
289 - Give a more useful assertion failure message if we think we have
290 minherit() but we fail to make a region non-inheritable. Give a
291 compile-time warning if our support for minherit() is incomplete.
294 o Minor features (maintenance):
295 - Add a new "make autostyle" target that developers can use to apply
296 all automatic Tor style and consistency conversions to the
297 codebase. Closes ticket 30539.
299 o Minor features (modularity):
300 - The "--disable-module-dirauth" compile-time option now disables
301 even more dirauth-only code. Closes ticket 30345.
303 o Minor features (performance):
304 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
305 1.1.1 and later), since they tend to be faster than tiny-keccak.
308 o Minor features (testing):
309 - The circuitpadding tests now use a reproducible RNG implementation,
310 so that if a test fails, we can learn why. Part of ticket 28878.
311 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
312 to set the RNG seed for tests that use a reproducible RNG. Part of
314 - When running tests in coverage mode, take additional care to make
315 our coverage deterministic, so that we can accurately track
316 changes in code coverage. Closes ticket 30519.
317 - Tor's unit test code now contains helper functions to replace the
318 PRNG with a deterministic or reproducible version for testing.
319 Previously, various tests implemented this in various ways.
320 Implements ticket 29732.
321 - We now have a script, cov-test-determinism.sh, to identify places
322 where our unit test coverage has become nondeterministic. Closes
324 - Check that representative subsets of values of `int` and `unsigned
325 int` can be represented by `void *`. Resolves issue 29537.
327 o Minor bugfixes (bridge authority):
328 - Bridge authorities now set bridges as running or non-running when
329 about to dump their status to a file. Previously, they set bridges
330 as running in response to a GETINFO command, but those shouldn't
331 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
332 Patch by Neel Chauhan.
334 o Minor bugfixes (channel padding statistics):
335 - Channel padding write totals and padding-enabled totals are now
336 counted properly in relay extrainfo descriptors. Fixes bug 29231;
337 bugfix on 0.3.1.1-alpha.
339 o Minor bugfixes (circuit isolation):
340 - Fix a logic error that prevented the SessionGroup sub-option from
341 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
343 o Minor bugfixes (circuit padding):
344 - Add a "CircuitPadding" torrc option to disable circuit padding.
345 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
346 - Allow circuit padding machines to specify that they do not
347 contribute much overhead, and provide consensus flags and torrc
348 options to force clients to only use these low overhead machines.
349 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
350 - Provide a consensus parameter to fully disable circuit padding, to
351 be used in emergency network overload situations. Fixes bug 30173;
352 bugfix on 0.4.0.1-alpha.
353 - The circuit padding subsystem will no longer schedule padding if
354 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
355 - Inspect a circuit-level cell queue before sending padding, to
356 avoid sending padding while too much data is already queued. Fixes
357 bug 29204; bugfix on 0.4.0.1-alpha.
358 - Avoid calling monotime_absolute_usec() in circuit padding machines
359 that do not use token removal or circuit RTT estimation. Fixes bug
360 29085; bugfix on 0.4.0.1-alpha.
362 o Minor bugfixes (clock skew detection):
363 - Don't believe clock skew results from NETINFO cells that appear to
364 arrive before we sent the VERSIONS cells they are responding to.
365 Previously, we would accept them up to 3 minutes "in the past".
366 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
368 o Minor bugfixes (compatibility, standards compliance):
369 - Fix a bug that would invoke undefined behavior on certain
370 operating systems when trying to asprintf() a string exactly
371 INT_MAX bytes long. We don't believe this is exploitable, but it's
372 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
373 Found and fixed by Tobias Stoeckmann.
375 o Minor bugfixes (compilation warning):
376 - Fix a compilation warning on Windows about casting a function
377 pointer for GetTickCount64(). Fixes bug 31374; bugfix on
380 o Minor bugfixes (compilation):
381 - Avoid using labs() on time_t, which can cause compilation warnings
382 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
384 o Minor bugfixes (compilation, unusual configurations):
385 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
386 due to missing declarations of abort(), and prevent other such
387 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
389 o Minor bugfixes (configuration, proxies):
390 - Fix a bug that prevented us from supporting SOCKS5 proxies that
391 want authentication along with configured (but unused!)
392 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
394 o Minor bugfixes (continuous integration):
395 - Allow the test-stem job to fail in Travis, because it sometimes
396 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
397 - Skip test_rebind on macOS in Travis, because it is unreliable on
398 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
399 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
400 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
402 o Minor bugfixes (controller protocol):
403 - Teach the controller parser to distinguish an object preceded by
404 an argument list from one without. Previously, it couldn't
405 distinguish an argument list from the first line of a multiline
406 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
408 o Minor bugfixes (crash on exit):
409 - Avoid a set of possible code paths that could try to use freed
410 memory in routerlist_free() while Tor was exiting. Fixes bug
411 31003; bugfix on 0.1.2.2-alpha.
413 o Minor bugfixes (developer tooling):
414 - Fix pre-push hook to allow fixup and squash commits when pushing
415 to non-upstream git remote. Fixes bug 30286; bugfix
418 o Minor bugfixes (directory authorities):
419 - Stop crashing after parsing an unknown descriptor purpose
420 annotation. We think this bug can only be triggered by modifying a
421 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
422 - Move the "bandwidth-file-headers" line in directory authority
423 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
425 - Directory authorities with IPv6 support now always mark themselves
426 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
427 Patch by Neel Chauhan.
429 o Minor bugfixes (documentation):
430 - Improve the documentation for using MapAddress with ".exit". Fixes
431 bug 30109; bugfix on 0.1.0.1-rc.
432 - Improve the monotonic time module and function documentation to
433 explain what "monotonic" actually means, and document some results
434 that have surprised people. Fixes bug 29640; bugfix
436 - Use proper formatting when providing an example on quoting options
437 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
439 o Minor bugfixes (logging):
440 - Do not log a warning when running with an OpenSSL version other
441 than the one Tor was compiled with, if the two versions should be
442 compatible. Previously, we would warn whenever the version was
443 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
444 - Warn operators when the MyFamily option is set but ContactInfo is
445 missing, as the latter should be set too. Fixes bug 25110; bugfix
448 o Minor bugfixes (memory leaks):
449 - Avoid a minor memory leak that could occur on relays when failing
450 to create a "keys" directory. Fixes bug 30148; bugfix
452 - Fix a trivial memory leak when parsing an invalid value from a
453 download schedule in the configuration. Fixes bug 30894; bugfix
456 o Minor bugfixes (NetBSD):
457 - Fix usage of minherit() on NetBSD and other platforms that define
458 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
459 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
461 o Minor bugfixes (onion services):
462 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
463 implemenation) when failing to load an onion service client
464 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
465 - When refusing to launch a controller's HSFETCH request because of
466 rate-limiting, respond to the controller with a new response,
467 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
468 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
470 - When relaunching a circuit to a rendezvous service, mark the
471 circuit as needing high-uptime routers as appropriate. Fixes bug
472 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
473 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
474 (IPv6 support for v3 onion services is still incomplete: see
475 ticket 23493 for details.) Fixes bug 23588; bugfix on
476 0.3.2.1-alpha. Patch by Neel Chauhan.
478 o Minor bugfixes (onion services, performance):
479 - When building circuits to onion services, call tor_addr_parse()
480 less often. Previously, we called tor_addr_parse() in
481 circuit_is_acceptable() even if its output wasn't used. This
482 change should improve performance when building circuits. Fixes
483 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
485 o Minor bugfixes (out-of-memory handler):
486 - When purging the DNS cache because of an out-of-memory condition,
487 try purging just the older entries at first. Previously, we would
488 always purge the whole thing. Fixes bug 29617; bugfix
491 o Minor bugfixes (performance):
492 - When checking whether a node is a bridge, use a fast check to make
493 sure that its identity is set. Previously, we used a constant-time
494 check, which is not necessary in this case. Fixes bug 30308;
495 bugfix on 0.3.5.1-alpha.
497 o Minor bugfixes (pluggable transports):
498 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
499 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
501 o Minor bugfixes (portability):
502 - Avoid crashing in our tor_vasprintf() implementation on systems
503 that define neither vasprintf() nor _vscprintf(). (This bug has
504 been here long enough that we question whether people are running
505 Tor on such systems, but we're applying the fix out of caution.)
506 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
509 o Minor bugfixes (probability distributions):
510 - Refactor and improve parts of the probability distribution code
511 that made Coverity complain. Fixes bug 29805; bugfix
514 o Minor bugfixes (python):
515 - Stop assuming that /usr/bin/python3 exists. For scripts that work
516 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
517 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
519 o Minor bugfixes (relay):
520 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
521 is auto, act as if ExitRelay is 1. Previously, we would ignore
522 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
523 0.3.5.1-alpha. Patch by Neel Chauhan.
525 o Minor bugfixes (static analysis):
526 - Fix several spurious Coverity warnings about the unit tests, to
527 lower our chances of missing real warnings in the future. Fixes
528 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
530 o Minor bugfixes (stats):
531 - When ExtraInfoStatistics is 0, stop including bandwidth usage
532 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
533 bridge statistics by country in extra-info documents. Fixes bug
534 29018; bugfix on 0.2.4.1-alpha.
536 o Minor bugfixes (testing):
537 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
538 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
539 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
540 - Fix some incorrect code in the v3 onion service unit tests. Fixes
541 bug 29243; bugfix on 0.3.2.1-alpha.
542 - In the "routerkeys/*" tests, check the return values of mkdir()
543 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
544 Found by Coverity as CID 1444254.
545 - Split test_utils_general() into several smaller test functions.
546 This makes it easier to perform resource deallocation on assert
547 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
548 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
550 o Minor bugfixes (tor-resolve):
551 - Fix a memory leak in tor-resolve that could happen if Tor gave it
552 a malformed SOCKS response. (Memory leaks in tor-resolve don't
553 actually matter, but it's good to fix them anyway.) Fixes bug
554 30151; bugfix on 0.4.0.1-alpha.
556 o Code simplification and refactoring:
557 - Abstract out the low-level formatting of replies on the control
558 port. Implements ticket 30007.
559 - Add several assertions in an attempt to fix some Coverity
560 warnings. Closes ticket 30149.
561 - Introduce a connection_dir_buf_add() helper function that checks
562 for compress_state of dir_connection_t and automatically writes a
563 string to directory connection with or without compression.
564 Resolves issue 28816.
565 - Make the base32_decode() API return the number of bytes written,
566 for consistency with base64_decode(). Closes ticket 28913.
567 - Move most relay-only periodic events out of mainloop.c into the
568 relay subsystem. Closes ticket 30414.
569 - Refactor and encapsulate parts of the codebase that manipulate
570 crypt_path_t objects. Resolves issue 30236.
571 - Refactor several places in our code that Coverity incorrectly
572 believed might have memory leaks. Closes ticket 30147.
573 - Remove redundant return values in crypto_format, and the
574 associated return value checks elsewhere in the code. Make the
575 implementations in crypto_format consistent, and remove redundant
576 code. Resolves ticket 29660.
577 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
578 it is not a constant-time function. Closes ticket 30309.
579 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
580 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
581 bugfix on 0.3.2.1-alpha.
582 - Simplify v3 onion service link specifier handling code. Fixes bug
583 23576; bugfix on 0.3.2.1-alpha.
584 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
585 code. Resolves ticket 29108.
586 - Split control.c into several submodules, in preparation for
587 distributing its current responsibilities throughout the codebase.
589 - Start to move responsibility for knowing about periodic events to
590 the appropriate subsystems, so that the mainloop doesn't need to
591 know all the periodic events in the rest of the codebase.
592 Implements tickets 30293 and 30294.
595 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
597 - Document how to find git commits and tags for bug fixes in
598 CodingStandards.md. Update some file documentation. Closes
602 - Remove the linux-tor-prio.sh script from contrib/operator-tools
603 directory. Resolves issue 29434.
604 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
605 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
609 - Specify torrc paths (with empty files) when launching tor in
610 integration tests; refrain from reading user and system torrcs.
611 Resolves issue 29702.
613 o Code simplification and refactoring (shell scripts):
614 - Clean up many of our shell scripts to fix shellcheck warnings.
615 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
616 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
617 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
618 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
619 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
620 nagios-check-tor-authority-cert (ticket 29071),
621 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
622 (ticket 29060), test_key_expiration.sh (ticket 30002),
623 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
627 - In "make test-network-all", test IPv6-only v3 single onion
628 services, using the chutney network single-onion-v23-ipv6-md.
631 o Testing (continuous integration):
632 - In Travis, make stem log a controller trace to the console, and tail
633 stem's tor log after failure. Closes ticket 30591.
634 - In Travis, only run the stem tests that use a tor binary.
638 Changes in version 0.4.0.5 - 2019-05-02
639 This is the first stable release in the 0.4.0.x series. It contains
640 improvements for power management and bootstrap reporting, as well as
641 preliminary backend support for circuit padding to prevent some kinds
642 of traffic analysis. It also continues our work in refactoring Tor for
643 long-term maintainability.
645 Per our support policy, we will support the 0.4.0.x series for nine
646 months, or until three months after the release of a stable 0.4.1.x:
647 whichever is longer. If you need longer-term support, please stick
648 with 0.3.5.x, which will we plan to support until Feb 2022.
650 Below are the changes since 0.3.5.7. For a complete list of changes
651 since 0.4.0.4-rc, see the ChangeLog file.
653 o Major features (battery management, client, dormant mode):
654 - When Tor is running as a client, and it is unused for a long time,
655 it can now enter a "dormant" state. When Tor is dormant, it avoids
656 network and CPU activity until it is reawoken either by a user
657 request or by a controller command. For more information, see the
658 configuration options starting with "Dormant". Implements tickets
660 - The client's memory of whether it is "dormant", and how long it
661 has spent idle, persists across invocations. Implements
663 - There is a DormantOnFirstStartup option that integrators can use
664 if they expect that in many cases, Tor will be installed but
667 o Major features (bootstrap reporting):
668 - When reporting bootstrap progress, report the first connection
669 uniformly, regardless of whether it's a connection for building
670 application circuits. This allows finer-grained reporting of early
671 progress than previously possible, with the improvements of ticket
672 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
673 - When reporting bootstrap progress, treat connecting to a proxy or
674 pluggable transport as separate from having successfully used that
675 proxy or pluggable transport to connect to a relay. Closes tickets
678 o Major features (circuit padding):
679 - Implement preliminary support for the circuit padding portion of
680 Proposal 254. The implementation supports Adaptive Padding (aka
681 WTF-PAD) state machines for use between experimental clients and
682 relays. Support is also provided for APE-style state machines that
683 use probability distributions instead of histograms to specify
684 inter-packet delay. At the moment, Tor does not provide any
685 padding state machines that are used in normal operation: for now,
686 this feature exists solely for experimentation. Closes
689 o Major features (refactoring):
690 - Tor now uses an explicit list of its own subsystems when
691 initializing and shutting down. Previously, these systems were
692 managed implicitly in various places throughout the codebase.
693 (There may still be some subsystems using the old system.) Closes
696 o Major bugfixes (cell scheduler, KIST, security):
697 - Make KIST consider the outbuf length when computing what it can
698 put in the outbuf. Previously, KIST acted as though the outbuf
699 were empty, which could lead to the outbuf becoming too full. It
700 is possible that an attacker could exploit this bug to cause a Tor
701 client or relay to run out of memory and crash. Fixes bug 29168;
702 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
703 TROVE-2019-001 and CVE-2019-8955.
705 o Major bugfixes (networking):
706 - Gracefully handle empty username/password fields in SOCKS5
707 username/password auth message and allow SOCKS5 handshake to
708 continue. Previously, we had rejected these handshakes, breaking
709 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
711 o Major bugfixes (NSS, relay):
712 - When running with NSS, disable TLS 1.2 ciphersuites that use
713 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
714 these ciphersuites don't work -- which caused relays to fail to
715 handshake with one another when these ciphersuites were enabled.
716 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
718 o Major bugfixes (windows, startup):
719 - When reading a consensus file from disk, detect whether it was
720 written in text mode, and re-read it in text mode if so. Always
721 write consensus files in binary mode so that we can map them into
722 memory later. Previously, we had written in text mode, which
723 confused us when we tried to map the file on windows. Fixes bug
724 28614; bugfix on 0.4.0.1-alpha.
726 o Minor features (address selection):
727 - Treat the subnet 100.64.0.0/10 as public for some purposes;
728 private for others. This subnet is the RFC 6598 (Carrier Grade
729 NAT) IP range, and is deployed by many ISPs as an alternative to
730 RFC 1918 that does not break existing internal networks. Tor now
731 blocks SOCKS and control ports on these addresses and warns users
732 if client ports or ExtORPorts are listening on a RFC 6598 address.
733 Closes ticket 28525. Patch by Neel Chauhan.
735 o Minor features (bandwidth authority):
736 - Make bandwidth authorities ignore relays that are reported in the
737 bandwidth file with the flag "vote=0". This change allows us to
738 report unmeasured relays for diagnostic reasons without including
739 their bandwidth in the bandwidth authorities' vote. Closes
741 - When a directory authority is using a bandwidth file to obtain the
742 bandwidth values that will be included in the next vote, serve
743 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
746 o Minor features (bootstrap reporting):
747 - When reporting bootstrap progress, stop distinguishing between
748 situations where only internal paths are available and situations
749 where external paths are available. Previously, Tor would often
750 erroneously report that it had only internal paths. Closes
753 o Minor features (compilation):
754 - Compile correctly when OpenSSL is built with engine support
755 disabled, or with deprecated APIs disabled. Closes ticket 29026.
756 Patches from "Mangix".
758 o Minor features (continuous integration):
759 - On Travis Rust builds, cleanup Rust registry and refrain from
760 caching the "target/" directory to speed up builds. Resolves
762 - Log Python version during each Travis CI job. Resolves
764 - In Travis, tell timelimit to use stem's backtrace signals, and
765 launch python directly from timelimit, so python receives the
766 signals from timelimit, rather than make. Closes ticket 30117.
768 o Minor features (controller):
769 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
770 Implements ticket 28843.
772 o Minor features (developer tooling):
773 - Check that bugfix versions in changes files look like Tor versions
774 from the versions spec. Warn when bugfixes claim to be on a future
775 release. Closes ticket 27761.
776 - Provide a git pre-commit hook that disallows committing if we have
777 any failures in our code and changelog formatting checks. It is
778 now available in scripts/maint/pre-commit.git-hook. Implements
780 - Provide a git hook script to prevent "fixup!" and "squash!"
781 commits from ending up in the master branch, as scripts/main/pre-
782 push.git-hook. Closes ticket 27993.
784 o Minor features (diagnostic):
785 - Add more diagnostic log messages in an attempt to solve the issue
786 of NUL bytes appearing in a microdescriptor cache. Related to
789 o Minor features (directory authority):
790 - When a directory authority is using a bandwidth file to obtain
791 bandwidth values, include the digest of that file in the vote.
793 - Directory authorities support a new consensus algorithm, under
794 which the family lines in microdescriptors are encoded in a
795 canonical form. This change makes family lines more compressible
796 in transit, and on the client. Closes ticket 28266; implements
799 o Minor features (directory authority, relay):
800 - Authorities now vote on a "StaleDesc" flag to indicate that a
801 relay's descriptor is so old that the relay should upload again
802 soon. Relays treat this flag as a signal to upload a new
803 descriptor. This flag will eventually let us remove the
804 'published' date from routerstatus entries, and make our consensus
805 diffs much smaller. Closes ticket 26770; implements proposal 293.
807 o Minor features (dormant mode):
808 - Add a DormantCanceledByStartup option to tell Tor that it should
809 treat a startup event as cancelling any previous dormant state.
810 Integrators should use this option with caution: it should only be
811 used if Tor is being started because of something that the user
812 did, and not if Tor is being automatically started in the
813 background. Closes ticket 29357.
815 o Minor features (fallback directory mirrors):
816 - Update the fallback whitelist based on operator opt-ins and opt-
817 outs. Closes ticket 24805, patch by Phoul.
819 o Minor features (FreeBSD):
820 - On FreeBSD-based systems, warn relay operators if the
821 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
824 o Minor features (geoip):
825 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
826 Country database. Closes ticket 29992.
828 o Minor features (HTTP standards compliance):
829 - Stop sending the header "Content-type: application/octet-stream"
830 along with transparently compressed documents: this confused
831 browsers. Closes ticket 28100.
833 o Minor features (IPv6):
834 - We add an option ClientAutoIPv6ORPort, to make clients randomly
835 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
836 every time a node is loaded from a new consensus or bridge config.
837 We expect that this option will enable clients to bootstrap more
838 quickly without having to determine whether they support IPv4,
839 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
840 - When using addrs_in_same_network_family(), avoid choosing circuit
841 paths that pass through the same IPv6 subnet more than once.
842 Previously, we only checked IPv4 subnets. Closes ticket 24393.
843 Patch by Neel Chauhan.
845 o Minor features (log messages):
846 - Improve log message in v3 onion services that could print out
847 negative revision counters. Closes ticket 27707. Patch
850 o Minor features (memory usage):
851 - Save memory by storing microdescriptor family lists with a more
852 compact representation. Closes ticket 27359.
853 - Tor clients now use mmap() to read consensus files from disk, so
854 that they no longer need keep the full text of a consensus in
855 memory when parsing it or applying a diff. Closes ticket 27244.
857 o Minor features (NSS, diagnostic):
858 - Try to log an error from NSS (if there is any) and a more useful
859 description of our situation if we are using NSS and a call to
860 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
862 o Minor features (parsing):
863 - Directory authorities now validate that router descriptors and
864 ExtraInfo documents are in a valid subset of UTF-8, and reject
865 them if they are not. Closes ticket 27367.
867 o Minor features (performance):
868 - Cache the results of summarize_protocol_flags(), so that we don't
869 have to parse the same protocol-versions string over and over.
870 This should save us a huge number of malloc calls on startup, and
871 may reduce memory fragmentation with some allocators. Closes
873 - Remove a needless memset() call from get_token_arguments, thereby
874 speeding up the tokenization of directory objects by about 20%.
876 - Replace parse_short_policy() with a faster implementation, to
877 improve microdescriptor parsing time. Closes ticket 28853.
878 - Speed up directory parsing a little by avoiding use of the non-
879 inlined strcmp_len() function. Closes ticket 28856.
880 - Speed up microdescriptor parsing by about 30%, to help improve
881 startup time. Closes ticket 28839.
883 o Minor features (pluggable transports):
884 - Add support for emitting STATUS updates to Tor's control port from
885 a pluggable transport process. Closes ticket 28846.
886 - Add support for logging to Tor's logging subsystem from a
887 pluggable transport process. Closes ticket 28180.
889 o Minor features (process management):
890 - Add a new process API for handling child processes. This new API
891 allows Tor to have bi-directional communication with child
892 processes on both Unix and Windows. Closes ticket 28179.
893 - Use the subsystem manager to initialize and shut down the process
894 module. Closes ticket 28847.
896 o Minor features (relay):
897 - When listing relay families, list them in canonical form including
898 the relay's own identity, and try to give a more useful set of
899 warnings. Part of ticket 28266 and proposal 298.
901 o Minor features (required protocols):
902 - Before exiting because of a missing required protocol, Tor will
903 now check the publication time of the consensus, and not exit
904 unless the consensus is newer than the Tor program's own release
905 date. Previously, Tor would not check the consensus publication
906 time, and so might exit because of a missing protocol that might
907 no longer be required in a current consensus. Implements proposal
908 297; closes ticket 27735.
910 o Minor features (testing):
911 - Treat all unexpected ERR and BUG messages as test failures. Closes
913 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
914 networks. Closes ticket 28840. Patch by Rob Jansen.
915 - Use the approx_time() function when setting the "Expires" header
916 in directory replies, to make them more testable. Needed for
919 o Minor bugfixes (security):
920 - Fix a potential double free bug when reading huge bandwidth files.
921 The issue is not exploitable in the current Tor network because
922 the vulnerable code is only reached when directory authorities
923 read bandwidth files, but bandwidth files come from a trusted
924 source (usually the authorities themselves). Furthermore, the
925 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
926 which are not used by any of the current authorities. Fixes bug
927 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
929 - Verify in more places that we are not about to create a buffer
930 with more than INT_MAX bytes, to avoid possible OOB access in the
931 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
932 fixed by Tobias Stoeckmann.
934 o Minor bugfix (continuous integration):
935 - Reset coverage state on disk after Travis CI has finished. This
936 should prevent future coverage merge errors from causing the test
937 suite for the "process" subsystem to fail. The process subsystem
938 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
940 - Terminate test-stem if it takes more than 9.5 minutes to run.
941 (Travis terminates the job after 10 minutes of no output.)
942 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
944 o Minor bugfixes (build, compatibility, rust):
945 - Update Cargo.lock file to match the version made by the latest
946 version of Rust, so that "make distcheck" will pass again. Fixes
947 bug 29244; bugfix on 0.3.3.4-alpha.
949 o Minor bugfixes (C correctness):
950 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
951 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
954 o Minor bugfixes (client, clock skew):
955 - Bootstrap successfully even when Tor's clock is behind the clocks
956 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
957 - Select guards even if the consensus has expired, as long as the
958 consensus is still reasonably live. Fixes bug 24661; bugfix
961 o Minor bugfixes (compilation):
962 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
963 29169; bugfix on 0.4.0.1-alpha.
964 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
965 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
966 - Compile correctly on OpenBSD; previously, we were missing some
967 headers required in order to detect it properly. Fixes bug 28938;
968 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
970 o Minor bugfixes (directory clients):
971 - Mark outdated dirservers when Tor only has a reasonably live
972 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
974 o Minor bugfixes (directory mirrors):
975 - Even when a directory mirror's clock is behind the clocks on the
976 authorities, we now allow the mirror to serve "future"
977 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
979 o Minor bugfixes (DNS):
980 - Gracefully handle an empty or absent resolve.conf file by falling
981 back to using "localhost" as a DNS server (and hoping it works).
982 Previously, we would just stop running as an exit. Fixes bug
983 21900; bugfix on 0.2.1.10-alpha.
985 o Minor bugfixes (documentation):
986 - Describe the contents of the v3 onion service client authorization
987 files correctly: They hold public keys, not private keys. Fixes
988 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
990 o Minor bugfixes (guards):
991 - In count_acceptable_nodes(), the minimum number is now one bridge
992 or guard node, and two non-guard nodes for a circuit. Previously,
993 we had added up the sum of all nodes with a descriptor, but that
994 could cause us to build failing circuits when we had either too
995 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
996 0.2.3.1-alpha. Patch by Neel Chauhan.
998 o Minor bugfixes (IPv6):
999 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
1000 IPv6 socket was bound using an address family of AF_INET instead
1001 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
1004 o Minor bugfixes (linux seccomp sandbox):
1005 - Fix startup crash when experimental sandbox support is enabled.
1006 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
1008 o Minor bugfixes (logging):
1009 - Correct a misleading error message when IPv4Only or IPv6Only is
1010 used but the resolved address can not be interpreted as an address
1011 of the specified IP version. Fixes bug 13221; bugfix on
1012 0.2.3.9-alpha. Patch from Kris Katterjohn.
1013 - Log the correct port number for listening sockets when "auto" is
1014 used to let Tor pick the port number. Previously, port 0 was
1015 logged instead of the actual port number. Fixes bug 29144; bugfix
1016 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1017 - Stop logging a BUG() warning when Tor is waiting for exit
1018 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
1019 - Avoid logging that we are relaxing a circuit timeout when that
1020 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
1021 - Log more information at "warning" level when unable to read a
1022 private key; log more information at "info" level when unable to
1023 read a public key. We had warnings here before, but they were lost
1024 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
1025 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1026 link protocol versions when logging incoming/outgoing connection
1027 counts. Tor no longer skips version 5, and we won't have to
1028 remember to update this function when new link protocol version is
1029 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1031 o Minor bugfixes (memory management):
1032 - Refactor the shared random state's memory management so that it
1033 actually takes ownership of the shared random value pointers.
1034 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
1035 - Stop leaking parts of the shared random state in the shared-random
1036 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
1038 o Minor bugfixes (misc):
1039 - The amount of total available physical memory is now determined
1040 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
1041 when it is defined and a 64-bit variant is not available. Fixes
1042 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
1044 o Minor bugfixes (networking):
1045 - Introduce additional checks into tor_addr_parse() to reject
1046 certain incorrect inputs that previously were not detected. Fixes
1047 bug 23082; bugfix on 0.2.0.10-alpha.
1049 o Minor bugfixes (onion service v3, client):
1050 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
1051 connection waiting for a descriptor that we actually have in the
1052 cache. It turns out that this can actually happen, though it is
1053 rare. Now, tor will recover and retry the descriptor. Fixes bug
1054 28669; bugfix on 0.3.2.4-alpha.
1056 o Minor bugfixes (onion services):
1057 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
1058 than one private key for a hidden service. Fixes bug 29040; bugfix
1060 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
1061 "debug" level. Tor used to log it as a warning, which caused very
1062 long log lines to appear for some users. Fixes bug 29135; bugfix
1064 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1065 as a warning. Instead, log it as a protocol warning, because there
1066 is nothing that relay operators can do to fix it. Fixes bug 29029;
1067 bugfix on 0.2.5.7-rc.
1069 o Minor bugfixes (periodic events):
1070 - Refrain from calling routerlist_remove_old_routers() from
1071 check_descriptor_callback(). Instead, create a new hourly periodic
1072 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
1074 o Minor bugfixes (pluggable transports):
1075 - Make sure that data is continously read from standard output and
1076 standard error pipes of a pluggable transport child-process, to
1077 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
1078 bugfix on 0.2.3.6-alpha.
1080 o Minor bugfixes (rust):
1081 - Abort on panic in all build profiles, instead of potentially
1082 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
1084 o Minor bugfixes (scheduler):
1085 - When re-adding channels to the pending list, check the correct
1086 channel's sched_heap_idx. This issue has had no effect in mainline
1087 Tor, but could have led to bugs down the road in improved versions
1088 of our circuit scheduling code. Fixes bug 29508; bugfix
1091 o Minor bugfixes (shellcheck):
1092 - Look for scripts in their correct locations during "make
1093 shellcheck". Previously we had looked in the wrong place during
1094 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
1096 o Minor bugfixes (single onion services):
1097 - Allow connections to single onion services to remain idle without
1098 being disconnected. Previously, relays acting as rendezvous points
1099 for single onion services were mistakenly closing idle rendezvous
1100 circuits after 60 seconds, thinking that they were unused
1101 directory-fetching circuits that had served their purpose. Fixes
1102 bug 29665; bugfix on 0.2.1.26.
1104 o Minor bugfixes (stats):
1105 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
1106 relay and bridge extra-info documents. Fixes bug 29017; bugfix
1109 o Minor bugfixes (testing):
1110 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
1111 recent test-network.sh to use new chutney features in CI. Fixes
1112 bug 29703; bugfix on 0.2.9.1-alpha.
1113 - Fix a test failure on Windows caused by an unexpected "BUG"
1114 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
1116 - Downgrade some LOG_ERR messages in the address/* tests to
1117 warnings. The LOG_ERR messages were occurring when we had no
1118 configured network. We were failing the unit tests, because we
1119 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
1120 29530; bugfix on 0.3.5.8.
1121 - Fix our gcov wrapper script to look for object files at the
1122 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
1123 - Decrease the false positive rate of stochastic probability
1124 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
1125 - Fix intermittent failures on an adaptive padding test. Fixes one
1126 case of bug 29122; bugfix on 0.4.0.1-alpha.
1127 - Disable an unstable circuit-padding test that was failing
1128 intermittently because of an ill-defined small histogram. Such
1129 histograms will be allowed again after 29298 is implemented. Fixes
1130 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
1131 - Detect and suppress "bug" warnings from the util/time test on
1132 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
1133 - Do not log an error-level message if we fail to find an IPv6
1134 network interface from the unit tests. Fixes bug 29160; bugfix
1136 - Instead of relying on hs_free_all() to clean up all onion service
1137 objects in test_build_descriptors(), we now deallocate them one by
1138 one. This lets Coverity know that we are not leaking memory there
1139 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
1140 - Check the time in the "Expires" header using approx_time(). Fixes
1141 bug 30001; bugfix on 0.4.0.4-rc.
1143 o Minor bugfixes (TLS protocol):
1144 - When classifying a client's selection of TLS ciphers, if the
1145 client ciphers are not yet available, do not cache the result.
1146 Previously, we had cached the unavailability of the cipher list
1147 and never looked again, which in turn led us to assume that the
1148 client only supported the ancient V1 link protocol. This, in turn,
1149 was causing Stem integration tests to stall in some cases. Fixes
1150 bug 30021; bugfix on 0.2.4.8-alpha.
1152 o Minor bugfixes (UI):
1153 - Lower log level of unlink() errors during bootstrap. Fixes bug
1154 29930; bugfix on 0.4.0.1-alpha.
1156 o Minor bugfixes (usability):
1157 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1158 Some users took this phrasing to mean that the mentioned guard was
1159 under their control or responsibility, which it is not. Fixes bug
1160 28895; bugfix on Tor 0.3.0.1-alpha.
1162 o Minor bugfixes (Windows, CI):
1163 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
1164 Windows Server 2012 R2 job. The remaining 2 jobs still provide
1165 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
1166 fast_finish, so failed jobs terminate the build immediately. Fixes
1167 bug 29601; bugfix on 0.3.5.4-alpha.
1169 o Code simplification and refactoring:
1170 - Introduce a connection_dir_buf_add() helper function that detects
1171 whether compression is in use, and adds a string accordingly.
1172 Resolves issue 28816.
1173 - Refactor handle_get_next_bandwidth() to use
1174 connection_dir_buf_add(). Implements ticket 29897.
1175 - Reimplement NETINFO cell parsing and generation to rely on
1176 trunnel-generated wire format handling code. Closes ticket 27325.
1177 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
1179 - Rework SOCKS wire format handling to rely on trunnel-generated
1180 parsing/generation code. Resolves ticket 27620.
1181 - Split out bootstrap progress reporting from control.c into a
1182 separate file. Part of ticket 27402.
1183 - The .may_include files that we use to describe our directory-by-
1184 directory dependency structure now describe a noncircular
1185 dependency graph over the directories that they cover. Our
1186 checkIncludes.py tool now enforces this noncircularity. Closes
1190 - Clarify that Tor performs stream isolation among *Port listeners
1191 by default. Resolves issue 29121.
1192 - In the manpage entry describing MapAddress torrc setting, use
1193 example IP addresses from ranges specified for use in documentation
1194 by RFC 5737. Resolves issue 28623.
1195 - Mention that you cannot add a new onion service if Tor is already
1196 running with Sandbox enabled. Closes ticket 28560.
1197 - Improve ControlPort documentation. Mention that it accepts
1198 address:port pairs, and can be used multiple times. Closes
1200 - Document the exact output of "tor --version". Closes ticket 28889.
1203 - Remove the old check-tor script. Resolves issue 29072.
1204 - Stop responding to the 'GETINFO status/version/num-concurring' and
1205 'GETINFO status/version/num-versioning' control port commands, as
1206 those were deprecated back in 0.2.0.30. Also stop listing them in
1207 output of 'GETINFO info/names'. Resolves ticket 28757.
1208 - The scripts used to generate and maintain the list of fallback
1209 directories have been extracted into a new "fallback-scripts"
1210 repository. Closes ticket 27914.
1213 - Run shellcheck for scripts in the in scripts/ directory. Closes
1215 - Add unit tests for tokenize_string() and get_next_token()
1216 functions. Resolves ticket 27625.
1218 o Code simplification and refactoring (onion service v3):
1219 - Consolidate the authorized client descriptor cookie computation
1220 code from client and service into one function. Closes
1223 o Code simplification and refactoring (shell scripts):
1224 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
1226 - Fix issues that shellcheck found in chutney-git-bisect.sh.
1227 Resolves ticket 28006.
1228 - Fix issues that shellcheck found in updateRustDependencies.sh.
1229 Resolves ticket 28012.
1230 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
1231 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
1232 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
1233 - Fix shellcheck warnings in scripts/test/coverage. Resolves
1237 Changes in version 0.3.5.8 - 2019-02-21
1238 Tor 0.3.5.8 backports several fixes from later releases, including fixes
1239 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
1242 It also includes a fix for a medium-severity security bug affecting Tor
1243 0.3.2.1-alpha and later. All Tor instances running an affected release
1244 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1246 o Major bugfixes (cell scheduler, KIST, security):
1247 - Make KIST consider the outbuf length when computing what it can
1248 put in the outbuf. Previously, KIST acted as though the outbuf
1249 were empty, which could lead to the outbuf becoming too full. It
1250 is possible that an attacker could exploit this bug to cause a Tor
1251 client or relay to run out of memory and crash. Fixes bug 29168;
1252 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1253 TROVE-2019-001 and CVE-2019-8955.
1255 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
1256 - Gracefully handle empty username/password fields in SOCKS5
1257 username/password auth messsage and allow SOCKS5 handshake to
1258 continue. Previously, we had rejected these handshakes, breaking
1259 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
1261 o Minor features (compilation, backport from 0.4.0.2-alpha):
1262 - Compile correctly when OpenSSL is built with engine support
1263 disabled, or with deprecated APIs disabled. Closes ticket 29026.
1264 Patches from "Mangix".
1266 o Minor features (geoip):
1267 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1268 Country database. Closes ticket 29478.
1270 o Minor features (testing, backport from 0.4.0.2-alpha):
1271 - Treat all unexpected ERR and BUG messages as test failures. Closes
1274 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
1275 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
1276 connection waiting for a descriptor that we actually have in the
1277 cache. It turns out that this can actually happen, though it is
1278 rare. Now, tor will recover and retry the descriptor. Fixes bug
1279 28669; bugfix on 0.3.2.4-alpha.
1281 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
1282 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
1283 IPv6 socket was bound using an address family of AF_INET instead
1284 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
1287 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
1288 - Update Cargo.lock file to match the version made by the latest
1289 version of Rust, so that "make distcheck" will pass again. Fixes
1290 bug 29244; bugfix on 0.3.3.4-alpha.
1292 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
1293 - Select guards even if the consensus has expired, as long as the
1294 consensus is still reasonably live. Fixes bug 24661; bugfix
1297 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
1298 - Compile correctly on OpenBSD; previously, we were missing some
1299 headers required in order to detect it properly. Fixes bug 28938;
1300 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1302 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
1303 - Describe the contents of the v3 onion service client authorization
1304 files correctly: They hold public keys, not private keys. Fixes
1305 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
1307 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
1308 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1309 link protocol versions when logging incoming/outgoing connection
1310 counts. Tor no longer skips version 5, and we won't have to
1311 remember to update this function when new link protocol version is
1312 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1314 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
1315 - Log more information at "warning" level when unable to read a
1316 private key; log more information at "info" level when unable to
1317 read a public key. We had warnings here before, but they were lost
1318 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
1320 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
1321 - The amount of total available physical memory is now determined
1322 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
1323 when it is defined and a 64-bit variant is not available. Fixes
1324 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
1326 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1327 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
1328 than one private key for a hidden service. Fixes bug 29040; bugfix
1330 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
1331 "debug" level. Tor used to log it as a warning, which caused very
1332 long log lines to appear for some users. Fixes bug 29135; bugfix
1334 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1335 as a warning. Instead, log it as a protocol warning, because there
1336 is nothing that relay operators can do to fix it. Fixes bug 29029;
1337 bugfix on 0.2.5.7-rc.
1339 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
1340 - Mark outdated dirservers when Tor only has a reasonably live
1341 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
1343 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
1344 - Detect and suppress "bug" warnings from the util/time test on
1345 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
1346 - Do not log an error-level message if we fail to find an IPv6
1347 network interface from the unit tests. Fixes bug 29160; bugfix
1350 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
1351 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1352 Some users took this phrasing to mean that the mentioned guard was
1353 under their control or responsibility, which it is not. Fixes bug
1354 28895; bugfix on Tor 0.3.0.1-alpha.
1357 Changes in version 0.3.4.11 - 2019-02-21
1358 Tor 0.3.4.11 is the third stable release in its series. It includes
1359 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
1360 later. All Tor instances running an affected release should upgrade to
1361 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1363 o Major bugfixes (cell scheduler, KIST, security):
1364 - Make KIST consider the outbuf length when computing what it can
1365 put in the outbuf. Previously, KIST acted as though the outbuf
1366 were empty, which could lead to the outbuf becoming too full. It
1367 is possible that an attacker could exploit this bug to cause a Tor
1368 client or relay to run out of memory and crash. Fixes bug 29168;
1369 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1370 TROVE-2019-001 and CVE-2019-8955.
1372 o Minor features (geoip):
1373 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1374 Country database. Closes ticket 29478.
1376 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
1377 - Update Cargo.lock file to match the version made by the latest
1378 version of Rust, so that "make distcheck" will pass again. Fixes
1379 bug 29244; bugfix on 0.3.3.4-alpha.
1381 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1382 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1383 as a warning. Instead, log it as a protocol warning, because there
1384 is nothing that relay operators can do to fix it. Fixes bug 29029;
1385 bugfix on 0.2.5.7-rc.
1388 Changes in version 0.3.3.12 - 2019-02-21
1389 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
1390 0.3.2.1-alpha and later. All Tor instances running an affected release
1391 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1393 This release marks the end of support for the Tor 0.3.3.x series. We
1394 recommend that users switch to either the Tor 0.3.4 series (supported
1395 until at least 10 June 2019), or the Tor 0.3.5 series, which will
1396 receive long-term support until at least 1 Feb 2022.
1398 o Major bugfixes (cell scheduler, KIST, security):
1399 - Make KIST consider the outbuf length when computing what it can
1400 put in the outbuf. Previously, KIST acted as though the outbuf
1401 were empty, which could lead to the outbuf becoming too full. It
1402 is possible that an attacker could exploit this bug to cause a Tor
1403 client or relay to run out of memory and crash. Fixes bug 29168;
1404 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1405 TROVE-2019-001 and CVE-2019-8955.
1407 o Minor features (geoip):
1408 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1409 Country database. Closes ticket 29478.
1411 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
1412 - Update Cargo.lock file to match the version made by the latest
1413 version of Rust, so that "make distcheck" will pass again. Fixes
1414 bug 29244; bugfix on 0.3.3.4-alpha.
1416 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1417 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1418 as a warning. Instead, log it as a protocol warning, because there
1419 is nothing that relay operators can do to fix it. Fixes bug 29029;
1420 bugfix on 0.2.5.7-rc.
1423 Changes in version 0.3.3.11 - 2019-01-07
1424 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
1425 numerous fixes, including an important fix for anyone using OpenSSL
1426 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
1427 to this version, or to a later series.
1429 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
1430 We anticipate that this will be the last release of Tor 0.3.3, unless
1431 some major bug is before then. Some time between now and then, users
1432 should switch to either the Tor 0.3.4 series (supported until at least
1433 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
1434 support until at least 1 Feb 2022.
1436 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1437 - Fix our usage of named groups when running as a TLS 1.3 client in
1438 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1439 running as a relay, which caused clients to fail to negotiate TLS
1440 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1443 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1444 - Fix a use-after-free error that could be caused by passing Tor an
1445 impossible set of options that would fail during options_act().
1446 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1448 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1449 - Only run one online rust build in Travis, to reduce network
1450 errors. Skip offline rust builds on Travis for Linux gcc, because
1451 they're redundant. Implements ticket 27252.
1452 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1453 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1454 Linux with default settings, because all the non-default builds
1455 use gcc on Linux. Implements ticket 27252.
1457 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1458 - Use the Travis Homebrew addon to install packages on macOS during
1459 Travis CI. The package list is the same, but the Homebrew addon
1460 does not do a `brew update` by default. Implements ticket 27738.
1462 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1463 - Replace the 150 fallbacks originally introduced in Tor
1464 0.3.3.1-alpha in January 2018 (of which ~115 were still
1465 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1466 removed) generated in December 2018. Closes ticket 24803.
1468 o Minor features (geoip):
1469 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1470 Country database. Closes ticket 29012.
1472 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1473 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1474 key export function from handling long labels. When this bug is
1475 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1476 version of OpenSSL without this bug when it becomes available.
1477 Closes ticket 28973.
1479 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1480 - Update relay descriptor on bandwidth changes only when the uptime
1481 is smaller than 24h, in order to reduce the efficiency of guard
1482 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1484 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
1485 - Avoid undefined behavior in an end-of-string check when parsing
1486 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1489 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1490 - Rewrite our assertion macros so that they no longer suppress the
1491 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1493 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1494 - Initialize a variable unconditionally in aes_new_cipher(), since
1495 some compilers cannot tell that we always initialize it before
1496 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1498 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
1499 - Log additional info when we get a relay that shares an ed25519 ID
1500 with a different relay, instead making a BUG() warning. Fixes bug
1501 27800; bugfix on 0.3.2.1-alpha.
1503 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1504 - When a user requests a group-readable DataDirectory, give it to
1505 them. Previously, when the DataDirectory and the CacheDirectory
1506 were the same, the default setting (0) for
1507 CacheDirectoryGroupReadable would override the setting for
1508 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1511 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1512 - When the onion service directory can't be created or has the wrong
1513 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1516 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1517 - Close all SOCKS request (for the same .onion) if the newly fetched
1518 descriptor is unusable. Before that, we would close only the first
1519 one leaving the other hanging and let to time out by themselves.
1520 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1522 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1523 - Don't warn so loudly when Tor is unable to decode an onion
1524 descriptor. This can now happen as a normal use case if a client
1525 gets a descriptor with client authorization but the client is not
1526 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1528 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1529 - When deleting an ephemeral onion service (DEL_ONION), do not close
1530 any rendezvous circuits in order to let the existing client
1531 connections finish by themselves or closed by the application. The
1532 HS v2 is doing that already so now we have the same behavior for
1533 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1535 o Minor bugfixes (HTTP tunnel):
1536 - Fix a bug warning when closing an HTTP tunnel connection due to
1537 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
1540 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1541 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1542 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1544 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1545 - Ensure circuitmux queues are empty before scheduling or sending
1546 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1548 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1549 - Reject protocol names containing bytes other than alphanumeric
1550 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1553 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1554 - Compute protover votes correctly in the rust version of the
1555 protover code. Previously, the protover rewrite in 24031 allowed
1556 repeated votes from the same voter for the same protocol version
1557 to be counted multiple times in protover_compute_vote(). Fixes bug
1558 27649; bugfix on 0.3.3.5-rc.
1559 - Reject protover names that contain invalid characters. Fixes bug
1560 27687; bugfix on 0.3.3.1-alpha.
1562 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1563 - protover_all_supported() would attempt to allocate up to 16GB on
1564 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1565 bugfix on 0.3.3.5-rc.
1567 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
1568 - Fix a potential null dereference in protover_all_supported(). Add
1569 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1570 - Return a string that can be safely freed by C code, not one
1571 created by the rust allocator, in protover_all_supported(). Fixes
1572 bug 27740; bugfix on 0.3.3.1-alpha.
1573 - Fix an API mismatch in the rust implementation of
1574 protover_compute_vote(). This bug could have caused crashes on any
1575 directory authorities running Tor with Rust (which we do not yet
1576 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1578 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1579 - If a unit test running in a subprocess exits abnormally or with a
1580 nonzero status code, treat the test as having failed, even if the
1581 test reported success. Without this fix, memory leaks don't cause
1582 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1583 bugfix on 0.2.2.4-alpha.
1585 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
1586 - Treat backtrace test failures as expected on BSD-derived systems
1587 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1588 (FreeBSD failures have been treated as expected since 18204 in
1589 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1591 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1592 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1593 bugfix on 0.3.0.1-alpha.
1596 Changes in version 0.3.4.10 - 2019-01-07
1597 Tor 0.3.4.9 is the second stable release in its series; it backports
1598 numerous fixes, including an important fix for relays, and for anyone
1599 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
1602 As a reminder, the Tor 0.3.4 series will be supported until 10 June
1603 2019. Some time between now and then, users should switch to the Tor
1604 0.3.5 series, which will receive long-term support until at least 1
1607 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1608 - Fix our usage of named groups when running as a TLS 1.3 client in
1609 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1610 running as a relay, which caused clients to fail to negotiate TLS
1611 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1614 o Major bugfixes (relay, directory, backport from 0.3.5.7):
1615 - Always reactivate linked connections in the main loop so long as
1616 any linked connection has been active. Previously, connections
1617 serving directory information wouldn't get reactivated after the
1618 first chunk of data was sent (usually 32KB), which would prevent
1619 clients from bootstrapping. Fixes bug 28912; bugfix on
1620 0.3.4.1-alpha. Patch by "cypherpunks3".
1622 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
1623 - Always show the configure and test logs, and upload them as build
1624 artifacts, when building for Windows using Appveyor CI.
1627 o Minor features (controller, backport from 0.3.5.1-alpha):
1628 - For purposes of CIRC_BW-based dropped cell detection, track half-
1629 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1630 bias check cells to arrive without counting it as dropped until
1631 either the END arrives, or the windows are empty. Closes
1634 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1635 - Replace the 150 fallbacks originally introduced in Tor
1636 0.3.3.1-alpha in January 2018 (of which ~115 were still
1637 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1638 removed) generated in December 2018. Closes ticket 24803.
1640 o Minor features (geoip):
1641 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1642 Country database. Closes ticket 28395.
1644 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1645 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1646 key export function from handling long labels. When this bug is
1647 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1648 version of OpenSSL without this bug when it becomes available.
1649 Closes ticket 28973.
1651 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1652 - Initialize a variable unconditionally in aes_new_cipher(), since
1653 some compilers cannot tell that we always initialize it before
1654 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1656 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
1657 - Avoid a logging a BUG() stacktrace when closing connection held
1658 open because the write side is rate limited but not the read side.
1659 Now, the connection read side is simply shut down until Tor is
1660 able to flush the connection and close it. Fixes bug 27750; bugfix
1663 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
1664 - Manually configure the zstd compiler options, when building using
1665 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1666 not come with a pkg-config file. Fixes bug 28454; bugfix
1668 - Stop using an external OpenSSL install, and stop installing MSYS2
1669 packages, when building using mingw on Appveyor Windows CI. Fixes
1670 bug 28399; bugfix on 0.3.4.1-alpha.
1672 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
1673 - Explicitly specify the path to the OpenSSL library and do not
1674 download OpenSSL from Pacman, but instead use the library that is
1675 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1677 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1678 - When a user requests a group-readable DataDirectory, give it to
1679 them. Previously, when the DataDirectory and the CacheDirectory
1680 were the same, the default setting (0) for
1681 CacheDirectoryGroupReadable would override the setting for
1682 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1685 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1686 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1687 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1689 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1690 - Don't warn so loudly when Tor is unable to decode an onion
1691 descriptor. This can now happen as a normal use case if a client
1692 gets a descriptor with client authorization but the client is not
1693 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1695 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1696 - When deleting an ephemeral onion service (DEL_ONION), do not close
1697 any rendezvous circuits in order to let the existing client
1698 connections finish by themselves or closed by the application. The
1699 HS v2 is doing that already so now we have the same behavior for
1700 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1702 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1703 - Update relay descriptor on bandwidth changes only when the uptime
1704 is smaller than 24h, in order to reduce the efficiency of guard
1705 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1707 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1708 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1709 bugfix on 0.3.0.1-alpha.
1712 Changes in version 0.3.5.7 - 2019-01-07
1713 Tor 0.3.5.7 is the first stable release in its series; it includes
1714 compilation and portability fixes, and a fix for a severe problem
1715 affecting directory caches.
1717 The Tor 0.3.5 series includes several new features and performance
1718 improvements, including client authorization for v3 onion services,
1719 cleanups to bootstrap reporting, support for improved bandwidth-
1720 measurement tools, experimental support for NSS in place of OpenSSL,
1721 and much more. It also begins a full reorganization of Tor's code
1722 layout, for improved modularity and maintainability in the future.
1723 Finally, there is the usual set of performance improvements and
1724 bugfixes that we try to do in every release series.
1726 There are a couple of changes in the 0.3.5 that may affect
1727 compatibility. First, the default version for newly created onion
1728 services is now v3. Use the HiddenServiceVersion option if you want to
1729 override this. Second, some log messages related to bootstrapping have
1730 changed; if you use stem, you may need to update to the latest version
1731 so it will recognize them.
1733 We have designated 0.3.5 as a "long-term support" (LTS) series: we
1734 will continue to patch major bugs in typical configurations of 0.3.5
1735 until at least 1 Feb 2022. (We do not plan to provide long-term
1736 support for embedding, Rust support, NSS support, running a directory
1737 authority, or unsupported platforms. For these, you will need to stick
1738 with the latest stable release.)
1740 Below are the changes since 0.3.4.9. For a complete list of changes
1741 since 0.3.5.6-rc, see the ChangeLog file.
1743 o Major features (bootstrap):
1744 - Don't report directory progress until after a connection to a
1745 relay or bridge has succeeded. Previously, we'd report 80%
1746 progress based on cached directory information when we couldn't
1747 even connect to the network. Closes ticket 27169.
1749 o Major features (new code layout):
1750 - Nearly all of Tor's source code has been moved around into more
1751 logical places. The "common" directory is now divided into a set
1752 of libraries in "lib", and files in the "or" directory have been
1753 split into "core" (logic absolutely needed for onion routing),
1754 "feature" (independent modules in Tor), and "app" (to configure
1755 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
1756 more information. Closes ticket 26481.
1758 This refactoring is not complete: although the libraries have been
1759 refactored to be acyclic, the main body of Tor is still too
1760 interconnected. We will attempt to improve this in the future.
1762 o Major features (onion services v3):
1763 - Implement onion service client authorization at the descriptor
1764 level: only authorized clients can decrypt a service's descriptor
1765 to find out how to contact it. A new torrc option was added to
1766 control this client side: ClientOnionAuthDir <path>. On the
1767 service side, if the "authorized_clients/" directory exists in the
1768 onion service directory path, client configurations are read from
1769 the files within. See the manpage for more details. Closes ticket
1770 27547. Patch done by Suphanat Chunhapanya (haxxpop).
1771 - Improve revision counter generation in next-gen onion services.
1772 Onion services can now scale by hosting multiple instances on
1773 different hosts without synchronization between them, which was
1774 previously impossible because descriptors would get rejected by
1775 HSDirs. Addresses ticket 25552.
1776 - Version 3 onion services can now use the per-service
1777 HiddenServiceExportCircuitID option to differentiate client
1778 circuits. It communicates with the service by using the HAProxy
1779 protocol to assign virtual IP addresses to inbound client
1780 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
1782 o Major features (onion services, UI change):
1783 - For a newly created onion service, the default version is now 3.
1784 Tor still supports existing version 2 services, but the operator
1785 now needs to set "HiddenServiceVersion 2" in order to create a new
1786 version 2 service. For existing services, Tor now learns the
1787 version by reading the key file. Closes ticket 27215.
1789 o Major features (portability, cryptography, experimental, TLS):
1790 - Tor now has the option to compile with the NSS library instead of
1791 OpenSSL. This feature is experimental, and we expect that bugs may
1792 remain. It is mainly intended for environments where Tor's
1793 performance is not CPU-bound, and where NSS is already known to be
1794 installed. To try it out, configure Tor with the --enable-nss
1795 flag. Closes tickets 26631, 26815, and 26816.
1797 If you are experimenting with this option and using an old cached
1798 consensus, Tor may fail to start. To solve this, delete your
1799 "cached-consensus" and "cached-microdesc-consensus" files,
1800 (if present), and restart Tor.
1802 o Major features (relay, UI change):
1803 - Relays no longer run as exits by default. If the "ExitRelay"
1804 option is auto (or unset), and no exit policy is specified with
1805 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
1806 Previously in this case, we allowed exit traffic and logged a
1807 warning message. Closes ticket 21530. Patch by Neel Chauhan.
1808 - Tor now validates that the ContactInfo config option is valid UTF-
1809 8 when parsing torrc. Closes ticket 27428.
1811 o Major bugfixes (compilation):
1812 - Fix compilation on ARM (and other less-used CPUs) when compiling
1813 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1815 o Major bugfixes (compilation, rust):
1816 - Rust tests can now build and run successfully with the
1817 --enable-fragile-hardening option enabled. Doing this currently
1818 requires the rust beta channel; it will be possible with stable
1819 rust once Rust version 1.31 is released. Patch from Alex Crichton.
1820 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
1822 o Major bugfixes (directory authority):
1823 - Actually check that the address we get from DirAuthority
1824 configuration line is valid IPv4. Explicitly disallow DirAuthority
1825 address to be a DNS hostname. Fixes bug 26488; bugfix
1828 o Major bugfixes (embedding, main loop):
1829 - When DisableNetwork becomes set, actually disable periodic events
1830 that are already enabled. (Previously, we would refrain from
1831 enabling new ones, but we would leave the old ones turned on.)
1832 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
1834 o Major bugfixes (main loop, bootstrap):
1835 - Make sure Tor bootstraps and works properly if only the
1836 ControlPort is set. Prior to this fix, Tor would only bootstrap
1837 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1838 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1840 o Major bugfixes (onion service v3):
1841 - On an intro point for a version 3 onion service, stop closing
1842 introduction circuits on a NACK. This lets the client decide
1843 whether to reuse the circuit or discard it. Previously, we closed
1844 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
1845 0.3.2.1-alpha. Patch by Neel Chaunan.
1847 o Major bugfixes (OpenSSL, portability):
1848 - Fix our usage of named groups when running as a TLS 1.3 client in
1849 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1850 running as a relay, which caused clients to fail to negotiate TLS
1851 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1854 o Major bugfixes (relay bandwidth statistics):
1855 - When we close relayed circuits, report the data in the circuit
1856 queues as being written in our relay bandwidth stats. This
1857 mitigates guard discovery and other attacks that close circuits
1858 for the explicit purpose of noticing this discrepancy in
1859 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
1861 o Major bugfixes (relay):
1862 - When our write bandwidth limit is exhausted, stop writing on the
1863 connection. Previously, we had a typo in the code that would make
1864 us stop reading instead, leading to relay connections being stuck
1865 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1867 - Always reactivate linked connections in the main loop so long as
1868 any linked connection has been active. Previously, connections
1869 serving directory information wouldn't get reactivated after the
1870 first chunk of data was sent (usually 32KB), which would prevent
1871 clients from bootstrapping. Fixes bug 28912; bugfix on
1872 0.3.4.1-alpha. Patch by "cypherpunks3".
1874 o Major bugfixes (restart-in-process):
1875 - Fix a use-after-free error that could be caused by passing Tor an
1876 impossible set of options that would fail during options_act().
1877 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1879 o Minor features (admin tools):
1880 - Add a new --key-expiration option to print the expiration date of
1881 the signing cert in an ed25519_signing_cert file. Resolves
1884 o Minor features (build):
1885 - If you pass the "--enable-pic" option to configure, Tor will try
1886 to tell the compiler to build position-independent code suitable
1887 to link into a dynamic library. (The default remains -fPIE, for
1888 code suitable for a relocatable executable.) Closes ticket 23846.
1890 o Minor features (code correctness, testing):
1891 - Tor's build process now includes a "check-includes" make target to
1892 verify that no module of Tor relies on any headers from a higher-
1893 level module. We hope to use this feature over time to help
1894 refactor our codebase. Closes ticket 26447.
1896 o Minor features (code layout):
1897 - We have a new "lowest-level" error-handling API for use by code
1898 invoked from within the logging module. With this interface, the
1899 logging code is no longer at risk of calling into itself if a
1900 failure occurs while it is trying to log something. Closes
1903 o Minor features (compilation):
1904 - When possible, place our warning flags in a separate file, to
1905 avoid flooding verbose build logs. Closes ticket 28924.
1906 - Tor's configure script now supports a --with-malloc= option to
1907 select your malloc implementation. Supported options are
1908 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
1909 default). Addresses part of ticket 20424. Based on a patch from
1912 o Minor features (config):
1913 - The "auto" keyword in torrc is now case-insensitive. Closes
1916 o Minor features (continuous integration):
1917 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
1919 - Add new CI job to Travis configuration to run stem-based
1920 integration tests. Closes ticket 27913.
1921 - Use the Travis Homebrew addon to install packages on macOS during
1922 Travis CI. The package list is the same, but the Homebrew addon
1923 does not do a `brew update` by default. Implements ticket 27738.
1924 - Report what program produced the mysterious core file that we
1925 occasionally see on Travis CI during make distcheck. Closes
1927 - Don't do a distcheck with --disable-module-dirauth in Travis.
1928 Implements ticket 27252.
1929 - Install libcap-dev and libseccomp2-dev so these optional
1930 dependencies get tested on Travis CI. Closes ticket 26560.
1931 - Only run one online rust build in Travis, to reduce network
1932 errors. Skip offline rust builds on Travis for Linux gcc, because
1933 they're redundant. Implements ticket 27252.
1934 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1935 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1936 Linux with default settings, because all the non-default builds
1937 use gcc on Linux. Implements ticket 27252.
1939 o Minor features (continuous integration, Windows):
1940 - Always show the configure and test logs, and upload them as build
1941 artifacts, when building for Windows using Appveyor CI.
1943 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
1944 Appveyor's CI. Closes ticket 28318.
1946 o Minor features (controller):
1947 - Emit CIRC_BW events as soon as we detect that we processed an
1948 invalid or otherwise dropped cell on a circuit. This allows
1949 vanguards and other controllers to react more quickly to dropped
1950 cells. Closes ticket 27678.
1951 - For purposes of CIRC_BW-based dropped cell detection, track half-
1952 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1953 bias check cells to arrive without counting it as dropped until
1954 either the END arrives, or the windows are empty. Closes
1956 - Implement a 'GETINFO md/all' controller command to enable getting
1957 all known microdescriptors. Closes ticket 8323.
1958 - The GETINFO command now support an "uptime" argument, to return
1959 Tor's uptime in seconds. Closes ticket 25132.
1961 o Minor features (denial-of-service avoidance):
1962 - Make our OOM handler aware of the DNS cache so that it doesn't
1963 fill up the memory. This check is important for our DoS mitigation
1964 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
1966 o Minor features (development):
1967 - Tor's makefile now supports running the "clippy" Rust style tool
1968 on our Rust code. Closes ticket 22156.
1970 o Minor features (directory authority):
1971 - There is no longer an artificial upper limit on the length of
1972 bandwidth lines. Closes ticket 26223.
1973 - When a bandwidth file is used to obtain the bandwidth measurements,
1974 include this bandwidth file headers in the votes. Closes
1976 - Improved support for networks with only a single authority or a
1977 single fallback directory. Patch from Gabriel Somlo. Closes
1980 o Minor features (embedding API):
1981 - The Tor controller API now supports a function to launch Tor with
1982 a preconstructed owning controller FD, so that embedding
1983 applications don't need to manage controller ports and
1984 authentication. Closes ticket 24204.
1985 - The Tor controller API now has a function that returns the name
1986 and version of the backend implementing the API. Closes
1989 o Minor features (fallback directory list):
1990 - Replace the 150 fallbacks originally introduced in Tor
1991 0.3.3.1-alpha in January 2018 (of which ~115 were still
1992 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1993 removed) generated in December 2018. Closes ticket 24803.
1995 o Minor features (geoip):
1996 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1997 Country database. Closes ticket 29012.
1999 o Minor features (memory management):
2000 - Get Libevent to use the same memory allocator as Tor, by calling
2001 event_set_mem_functions() during initialization. Resolves
2004 o Minor features (memory usage):
2005 - When not using them, store legacy TAP public onion keys in DER-
2006 encoded format, rather than as expanded public keys. This should
2007 save several megabytes on typical clients. Closes ticket 27246.
2009 o Minor features (OpenSSL bug workaround):
2010 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
2011 key export function from handling long labels. When this bug is
2012 detected, Tor will disable TLS 1.3. We recommend upgrading to a
2013 version of OpenSSL without this bug when it becomes available.
2014 Closes ticket 28973.
2016 o Minor features (OpenSSL):
2017 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
2018 than our own. Resolves ticket 19979.
2020 o Minor features (performance):
2021 - Remove about 96% of the work from the function that we run at
2022 startup to test our curve25519_basepoint implementation. Since
2023 this function has yet to find an actual failure, we now only run
2024 it for 8 iterations instead of 200. Based on our profile
2025 information, this change should save around 8% of our startup time
2026 on typical desktops, and may have a similar effect on other
2027 platforms. Closes ticket 28838.
2028 - Stop re-validating our hardcoded Diffie-Hellman parameters on
2029 every startup. Doing this wasted time and cycles, especially on
2030 low-powered devices. Closes ticket 28851.
2032 o Minor features (Rust, code quality):
2033 - Improve rust code quality in the rust protover implementation by
2034 making it more idiomatic. Includes changing an internal API to
2035 take &str instead of &String. Closes ticket 26492.
2037 o Minor features (testing):
2038 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
2039 chutney. Implements ticket 27211.
2041 o Minor features (tor-resolve):
2042 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
2043 Side-effect of the refactoring for ticket 26526.
2045 o Minor features (UI):
2046 - Log each included configuration file or directory as we read it,
2047 to provide more visibility about where Tor is reading from. Patch
2048 from Unto Sten; closes ticket 27186.
2049 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
2050 Closes ticket 26703.
2052 o Minor bugfixes (32-bit OSX and iOS, timing):
2053 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2054 difference algorithm for 32-bit Apple platforms. Previously, it
2055 would overflow when calculating the difference between two times
2056 more than 47 days apart. Fixes part of bug 27139; bugfix
2058 - Improve the precision of our 32-bit millisecond difference
2059 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2060 bugfix on 0.3.4.1-alpha.
2061 - Relax the tolerance on the mainloop/update_time_jumps test when
2062 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2065 o Minor bugfixes (bootstrap):
2066 - Try harder to get descriptors in non-exit test networks, by using
2067 the mid weight for the third hop when there are no exits. Fixes
2068 bug 27237; bugfix on 0.2.6.2-alpha.
2070 o Minor bugfixes (C correctness):
2071 - Avoid casting smartlist index to int implicitly, as it may trigger
2072 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
2073 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
2074 - Use time_t for all values in
2075 predicted_ports_prediction_time_remaining(). Rework the code that
2076 computes difference between durations/timestamps. Fixes bug 27165;
2077 bugfix on 0.3.1.1-alpha.
2079 o Minor bugfixes (client, memory usage):
2080 - When not running as a directory cache, there is no need to store
2081 the text of the current consensus networkstatus in RAM.
2082 Previously, however, clients would store it anyway, at a cost of
2083 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
2086 o Minor bugfixes (client, ReachableAddresses):
2087 - Instead of adding a "reject *:*" line to ReachableAddresses when
2088 loading the configuration, add one to the policy after parsing it
2089 in parse_reachable_addresses(). This prevents extra "reject *.*"
2090 lines from accumulating on reloads. Fixes bug 20874; bugfix on
2091 0.1.1.5-alpha. Patch by Neel Chauhan.
2093 o Minor bugfixes (code quality):
2094 - Rename sandbox_getaddrinfo() and other functions to no longer
2095 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
2096 bugfix on 0.2.7.1-alpha.
2098 o Minor bugfixes (code safety):
2099 - Rewrite our assertion macros so that they no longer suppress the
2100 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2103 o Minor bugfixes (compilation):
2104 - Initialize a variable unconditionally in aes_new_cipher(), since
2105 some compilers cannot tell that we always initialize it before
2106 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
2108 o Minor bugfixes (configuration):
2109 - Refuse to start with relative file paths and RunAsDaemon set
2110 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
2113 o Minor bugfixes (configuration, Onion Services):
2114 - In rend_service_parse_port_config(), disallow any input to remain
2115 after address-port pair was parsed. This will catch address and
2116 port being whitespace-separated by mistake of the user. Fixes bug
2117 27044; bugfix on 0.2.9.10.
2119 o Minor bugfixes (connection, relay):
2120 - Avoid a logging a BUG() stacktrace when closing connection held
2121 open because the write side is rate limited but not the read side.
2122 Now, the connection read side is simply shut down until Tor is
2123 able to flush the connection and close it. Fixes bug 27750; bugfix
2126 o Minor bugfixes (continuous integration, Windows):
2127 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2128 27464; bugfix on 0.3.4.1-alpha.
2129 - Install only the necessary mingw packages during our appveyor
2130 builds. This change makes the build a little faster, and prevents
2131 a conflict with a preinstalled mingw openssl that appveyor now
2132 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
2133 - Explicitly specify the path to the OpenSSL library and do not
2134 download OpenSSL from Pacman, but instead use the library that is
2135 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
2136 - Manually configure the zstd compiler options, when building using
2137 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
2138 not come with a pkg-config file. Fixes bug 28454; bugfix
2140 - Stop using an external OpenSSL install, and stop installing MSYS2
2141 packages, when building using mingw on Appveyor Windows CI. Fixes
2142 bug 28399; bugfix on 0.3.4.1-alpha.
2144 o Minor bugfixes (controller):
2145 - Consider all routerinfo errors other than "not a server" to be
2146 transient for the purpose of "GETINFO exit-policy/*" controller
2147 request. Print stacktrace in the unlikely case of failing to
2148 recompute routerinfo digest. Fixes bug 27034; bugfix
2151 o Minor bugfixes (correctness):
2152 - Fix an unreached code path where we checked the value of
2153 "hostname" inside send_resolved_hostname_cell(). Previously, we
2154 used it before checking it; now we check it first. Fixes bug
2155 28879; bugfix on 0.1.2.7-alpha.
2157 o Minor bugfixes (directory connection shutdown):
2158 - Avoid a double-close when shutting down a stalled directory
2159 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2161 o Minor bugfixes (directory permissions):
2162 - When a user requests a group-readable DataDirectory, give it to
2163 them. Previously, when the DataDirectory and the CacheDirectory
2164 were the same, the default setting (0) for
2165 CacheDirectoryGroupReadable would override the setting for
2166 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
2169 o Minor bugfixes (HTTP tunnel):
2170 - Fix a bug warning when closing an HTTP tunnel connection due to an
2171 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2174 o Minor bugfixes (ipv6):
2175 - In addrs_in_same_network_family(), we choose the subnet size based
2176 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
2177 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
2178 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
2180 o Minor bugfixes (Linux seccomp2 sandbox):
2181 - Permit the "shutdown()" system call, which is apparently used by
2182 OpenSSL under some circumstances. Fixes bug 28183; bugfix
2185 o Minor bugfixes (logging):
2186 - Stop talking about the Named flag in log messages. Clients have
2187 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
2189 - As a precaution, do an early return from log_addr_has_changed() if
2190 Tor is running as client. Also, log a stack trace for debugging as
2191 this function should only be called when Tor runs as server. Fixes
2192 bug 26892; bugfix on 0.1.1.9-alpha.
2193 - Refrain from mentioning bug 21018 in the logs, as it is already
2194 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
2196 o Minor bugfixes (logging, documentation):
2197 - When SafeLogging is enabled, scrub IP address in
2198 channel_tls_process_netinfo_cell(). Also, add a note to manpage
2199 that scrubbing is not guaranteed on loglevels below Notice. Fixes
2200 bug 26882; bugfix on 0.2.4.10-alpha.
2202 o Minor bugfixes (memory leaks):
2203 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
2204 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
2205 - Fix a small memory leak when calling Tor with --dump-config. Fixes
2206 bug 27893; bugfix on 0.3.2.1-alpha.
2208 o Minor bugfixes (netflow padding):
2209 - Ensure circuitmux queues are empty before scheduling or sending
2210 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2212 o Minor bugfixes (onion service v2):
2213 - Log at level "info", not "warning", in the case that we do not
2214 have a consensus when a .onion request comes in. This can happen
2215 normally while bootstrapping. Fixes bug 27040; bugfix
2218 o Minor bugfixes (onion service v3):
2219 - When deleting an ephemeral onion service (DEL_ONION), do not close
2220 any rendezvous circuits in order to let the existing client
2221 connections finish by themselves or closed by the application. The
2222 HS v2 is doing that already so now we have the same behavior for
2223 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
2224 - Build the service descriptor's signing key certificate before
2225 uploading, so we always have a fresh one: leaving no chances for
2226 it to expire service side. Fixes bug 27838; bugfix
2228 - Stop dumping a stack trace when trying to connect to an intro
2229 point without having a descriptor for it. Fixes bug 27774; bugfix
2231 - When selecting a v3 rendezvous point, don't only look at the
2232 protover, but also check whether the curve25519 onion key is
2233 present. This way we avoid picking a relay that supports the v3
2234 rendezvous but for which we don't have the microdescriptor. Fixes
2235 bug 27797; bugfix on 0.3.2.1-alpha.
2236 - Close all SOCKS request (for the same .onion) if the newly fetched
2237 descriptor is unusable. Before that, we would close only the first
2238 one leaving the other hanging and let to time out by themselves.
2239 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2240 - When the onion service directory can't be created or has the wrong
2241 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2243 - When replacing a descriptor in the client cache, make sure to
2244 close all client introduction circuits for the old descriptor, so
2245 we don't end up with unusable leftover circuits. Fixes bug 27471;
2246 bugfix on 0.3.2.1-alpha.
2248 o Minor bugfixes (OS compatibility):
2249 - Properly handle configuration changes that move a listener to/from
2250 wildcard IP address. If the first attempt to bind a socket fails,
2251 close the old listener and try binding the socket again. Fixes bug
2252 17873; bugfix on 0.0.8pre-1.
2254 o Minor bugfixes (performance)::
2255 - Rework node_is_a_configured_bridge() to no longer call
2256 node_get_all_orports(), which was performing too many memory
2257 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
2259 o Minor bugfixes (protover):
2260 - Reject protocol names containing bytes other than alphanumeric
2261 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2264 o Minor bugfixes (protover, rust):
2265 - Reject extra commas in version strings. Fixes bug 27197; bugfix
2267 - protover_all_supported() would attempt to allocate up to 16GB on
2268 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2269 bugfix on 0.3.3.5-rc.
2270 - Compute protover votes correctly in the rust version of the
2271 protover code. Previously, the protover rewrite in 24031 allowed
2272 repeated votes from the same voter for the same protocol version
2273 to be counted multiple times in protover_compute_vote(). Fixes bug
2274 27649; bugfix on 0.3.3.5-rc.
2275 - Reject protover names that contain invalid characters. Fixes bug
2276 27687; bugfix on 0.3.3.1-alpha.
2278 o Minor bugfixes (relay shutdown, systemd):
2279 - Notify systemd of ShutdownWaitLength so it can be set to longer
2280 than systemd's TimeoutStopSec. In Tor's systemd service file, set
2281 TimeoutSec to 60 seconds to allow Tor some time to shut down.
2282 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
2284 o Minor bugfixes (relay statistics):
2285 - Update relay descriptor on bandwidth changes only when the uptime
2286 is smaller than 24h, in order to reduce the efficiency of guard
2287 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
2289 o Minor bugfixes (relay):
2290 - Consider the fact that we'll be making direct connections to our
2291 entry and guard nodes when computing the fraction of nodes that
2292 have their descriptors. Also, if we are using bridges and there is
2293 at least one bridge with a full descriptor, treat the fraction of
2294 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
2295 Patch by Neel Chauhan.
2296 - Update the message logged on relays when DirCache is disabled.
2297 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
2298 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
2300 o Minor bugfixes (testing):
2301 - Stop running stem's unit tests as part of "make test-stem", but
2302 continue to run stem's unit and online tests during "make test-
2303 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
2304 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
2305 bugfix on 0.3.0.1-alpha.
2306 - Make the hs_service tests use the same time source when creating
2307 the introduction point and when testing it. Now tests work better
2308 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2310 - Revise the "conditionvar_timeout" test so that it succeeds even on
2311 heavily loaded systems where the test threads are not scheduled
2312 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
2313 - Fix two unit tests to work when HOME environment variable is not
2314 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
2315 - If a unit test running in a subprocess exits abnormally or with a
2316 nonzero status code, treat the test as having failed, even if the
2317 test reported success. Without this fix, memory leaks don't cause
2318 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2319 bugfix on 0.2.2.4-alpha.
2320 - When logging a version mismatch in our openssl_version tests,
2321 report the actual offending version strings. Fixes bug 26152;
2322 bugfix on 0.2.9.1-alpha.
2323 - Fix forking tests on Windows when there is a space somewhere in
2324 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
2326 o Minor bugfixes (Windows):
2327 - Correctly identify Windows 8.1, Windows 10, and Windows Server
2328 2008 and later from their NT versions. Fixes bug 28096; bugfix on
2329 0.2.2.34; reported by Keifer Bly.
2330 - On recent Windows versions, the GetVersionEx() function may report
2331 an earlier Windows version than the running OS. To avoid user
2332 confusion, add "[or later]" to Tor's version string on affected
2333 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
2335 - Remove Windows versions that were never supported by the
2336 GetVersionEx() function. Stop duplicating the latest Windows
2337 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
2338 reported by Keifer Bly.
2340 o Code simplification and refactoring:
2341 - When parsing a port configuration, make it more obvious to static
2342 analyzer tools that we always initialize the address. Closes
2344 - Divide more large Tor source files -- especially ones that span
2345 multiple areas of functionality -- into smaller parts, including
2346 onion.c and main.c. Closes ticket 26747.
2347 - Divide the "routerparse.c" module into separate modules for each
2348 group of parsed objects. Closes ticket 27924.
2349 - Move protover_rust.c to the same place protover.c was moved to.
2350 Closes ticket 27814.
2351 - Split directory.c into separate pieces for client, server, and
2352 common functionality. Closes ticket 26744.
2353 - Split the non-statistics-related parts from the rephist.c and
2354 geoip.c modules. Closes ticket 27892.
2355 - Split the router.c file into relay-only and shared components, to
2356 help with future modularization. Closes ticket 27864.
2357 - Divide the routerlist.c and dirserv.c modules into smaller parts.
2358 Closes ticket 27799.
2359 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
2360 longer needed. Closes ticket 26502.
2361 - Include paths to header files within Tor are now qualified by
2362 directory within the top-level src directory.
2363 - Many structures have been removed from the centralized "or.h"
2364 header, and moved into their own headers. This will allow us to
2365 reduce the number of places in the code that rely on each
2366 structure's contents and layout. Closes ticket 26383.
2367 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
2368 - Remove GetAdaptersAddresses_fn_t. The code that used it was
2369 removed as part of the 26481 refactor. Closes ticket 27467.
2370 - Rework Tor SOCKS server code to use Trunnel and benefit from
2371 autogenerated functions for parsing and generating SOCKS wire
2372 format. New implementation is cleaner, more maintainable and
2373 should be less prone to heartbleed-style vulnerabilities.
2374 Implements a significant fraction of ticket 3569.
2375 - Split sampled_guards_update_from_consensus() and
2376 select_entry_guard_for_circuit() into subfunctions. In
2377 entry_guards_update_primary() unite three smartlist enumerations
2378 into one and move smartlist comparison code out of the function.
2379 Closes ticket 21349.
2380 - Tor now assumes that you have standards-conformant stdint.h and
2381 inttypes.h headers when compiling. Closes ticket 26626.
2382 - Unify our bloom filter logic. Previously we had two copies of this
2383 code: one for routerlist filtering, and one for address set
2384 calculations. Closes ticket 26510.
2385 - Use the simpler strcmpstart() helper in
2386 rend_parse_v2_service_descriptor instead of strncmp(). Closes
2388 - Utility functions that can perform a DNS lookup are now wholly
2389 separated from those that can't, in separate headers and C
2390 modules. Closes ticket 26526.
2393 - In the tor-resolve(1) manpage, fix the reference to socks-
2394 extensions.txt by adding a web URL. Resolves ticket 27853.
2395 - Mention that we require Python to be 2.7 or newer for some
2396 integration tests that we ship with Tor. Resolves ticket 27677.
2397 - Copy paragraph and URL to Tor's code of conduct document from
2398 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
2399 - Remove old instructions from INSTALL document. Closes ticket 26588.
2400 - Warn users that they should not include MyFamily line(s) in their
2401 torrc when running Tor bridge. Closes ticket 26908.
2404 - Tor no longer supports building with the dmalloc library. For
2405 debugging memory issues, we suggest using gperftools or msan
2406 instead. Closes ticket 26426.
2407 - Tor no longer attempts to run on Windows environments without the
2408 GetAdaptersAddresses() function. This function has existed since
2409 Windows XP, which is itself already older than we support.
2410 - Remove Tor2web functionality for version 2 onion services. The
2411 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
2412 (This feature was never shipped in vanilla Tor and it was only
2413 possible to use this feature by building the support at compile
2414 time. Tor2webMode is not implemented for version 3 onion services.)
2415 Closes ticket 26367.
2418 - Increase logging and tag all log entries with timestamps in
2419 test_rebind.py. Provides diagnostics for issue 28229.
2421 o Code simplification and refactoring (shared random, dirauth):
2422 - Change many tor_assert() to use BUG() instead. The idea is to not
2423 crash a dirauth but rather scream loudly with a stacktrace and let
2424 it continue run. The shared random subsystem is very resilient and
2425 if anything wrong happens with it, at worst a non coherent value
2426 will be put in the vote and discarded by the other authorities.
2427 Closes ticket 19566.
2429 o Documentation (onion services):
2430 - Improve HSv3 client authorization by making some options more
2431 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
2432 - Document in the man page that changing ClientOnionAuthDir value or
2433 adding a new file in the directory will not work at runtime upon
2434 sending a HUP if Sandbox 1. Closes ticket 28128.
2435 - Note in the man page that the only real way to fully revoke an
2436 onion service v3 client authorization is by restarting the tor
2437 process. Closes ticket 28275.
2440 Changes in version 0.3.4.9 - 2018-11-02
2441 Tor 0.3.4.9 is the second stable release in its series; it backports
2442 numerous fixes, including a fix for a bandwidth management bug that
2443 was causing memory exhaustion on relays. Anyone running an earlier
2444 version of Tor 0.3.4.9 should upgrade.
2446 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
2447 - Fix compilation on ARM (and other less-used CPUs) when compiling
2448 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2450 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
2451 - Make sure Tor bootstraps and works properly if only the
2452 ControlPort is set. Prior to this fix, Tor would only bootstrap
2453 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2454 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2456 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
2457 - When our write bandwidth limit is exhausted, stop writing on the
2458 connection. Previously, we had a typo in the code that would make
2459 us stop reading instead, leading to relay connections being stuck
2460 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2463 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
2464 - Fix a use-after-free error that could be caused by passing Tor an
2465 impossible set of options that would fail during options_act().
2466 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2468 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
2469 - Don't do a distcheck with --disable-module-dirauth in Travis.
2470 Implements ticket 27252.
2471 - Only run one online rust build in Travis, to reduce network
2472 errors. Skip offline rust builds on Travis for Linux gcc, because
2473 they're redundant. Implements ticket 27252.
2474 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2475 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2476 Linux with default settings, because all the non-default builds
2477 use gcc on Linux. Implements ticket 27252.
2479 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
2480 - Use the Travis Homebrew addon to install packages on macOS during
2481 Travis CI. The package list is the same, but the Homebrew addon
2482 does not do a `brew update` by default. Implements ticket 27738.
2484 o Minor features (geoip):
2485 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2486 Country database. Closes ticket 27991.
2488 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
2489 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2490 difference algorithm for 32-bit Apple platforms. Previously, it
2491 would overflow when calculating the difference between two times
2492 more than 47 days apart. Fixes part of bug 27139; bugfix
2494 - Improve the precision of our 32-bit millisecond difference
2495 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2496 bugfix on 0.3.4.1-alpha.
2497 - Relax the tolerance on the mainloop/update_time_jumps test when
2498 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2501 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
2502 - Avoid undefined behavior in an end-of-string check when parsing
2503 the BEGIN line in a directory object. Fixes bug 28202; bugfix
2506 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
2507 - Only install the necessary mingw packages during our appveyor
2508 builds. This change makes the build a little faster, and prevents
2509 a conflict with a preinstalled mingw openssl that appveyor now
2510 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
2512 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
2513 - Rewrite our assertion macros so that they no longer suppress the
2514 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2516 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
2517 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2518 27464; bugfix on 0.3.4.1-alpha.
2520 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
2521 - Log additional info when we get a relay that shares an ed25519 ID
2522 with a different relay, instead making a BUG() warning. Fixes bug
2523 27800; bugfix on 0.3.2.1-alpha.
2525 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
2526 - Avoid a double-close when shutting down a stalled directory
2527 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2529 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
2530 - Fix a bug warning when closing an HTTP tunnel connection due to an
2531 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2534 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
2535 - Ensure circuitmux queues are empty before scheduling or sending
2536 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2538 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
2539 - When the onion service directory can't be created or has the wrong
2540 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2543 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
2544 - Close all SOCKS request (for the same .onion) if the newly fetched
2545 descriptor is unusable. Before that, we would close only the first
2546 one leaving the other hanging and let to time out by themselves.
2547 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2549 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
2550 - When selecting a v3 rendezvous point, don't only look at the
2551 protover, but also check whether the curve25519 onion key is
2552 present. This way we avoid picking a relay that supports the v3
2553 rendezvous but for which we don't have the microdescriptor. Fixes
2554 bug 27797; bugfix on 0.3.2.1-alpha.
2556 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
2557 - Reject protocol names containing bytes other than alphanumeric
2558 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2561 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
2562 - Compute protover votes correctly in the rust version of the
2563 protover code. Previously, the protover rewrite in 24031 allowed
2564 repeated votes from the same voter for the same protocol version
2565 to be counted multiple times in protover_compute_vote(). Fixes bug
2566 27649; bugfix on 0.3.3.5-rc.
2567 - Reject protover names that contain invalid characters. Fixes bug
2568 27687; bugfix on 0.3.3.1-alpha.
2570 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
2571 - protover_all_supported() would attempt to allocate up to 16GB on
2572 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2573 bugfix on 0.3.3.5-rc.
2575 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
2576 - Fix an API mismatch in the rust implementation of
2577 protover_compute_vote(). This bug could have caused crashes on any
2578 directory authorities running Tor with Rust (which we do not yet
2579 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2581 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
2582 - Fix a potential null dereference in protover_all_supported(). Add
2583 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2584 - Return a string that can be safely freed by C code, not one
2585 created by the rust allocator, in protover_all_supported(). Fixes
2586 bug 27740; bugfix on 0.3.3.1-alpha.
2588 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
2589 - If a unit test running in a subprocess exits abnormally or with a
2590 nonzero status code, treat the test as having failed, even if the
2591 test reported success. Without this fix, memory leaks don't cause
2592 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2593 bugfix on 0.2.2.4-alpha.
2595 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
2596 - Make the hs_service tests use the same time source when creating
2597 the introduction point and when testing it. Now tests work better
2598 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2601 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
2602 - Treat backtrace test failures as expected on BSD-derived systems
2603 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2604 (FreeBSD failures have been treated as expected since 18204 in
2605 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2608 Changes in version 0.2.9.17 - 2018-09-10
2609 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
2611 o Minor features (compatibility, backport from 0.3.4.8):
2612 - Tell OpenSSL to maintain backward compatibility with previous
2613 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2614 ciphers are disabled by default. Closes ticket 27344.
2616 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2617 - Enable macOS builds in our Travis CI configuration. Closes
2619 - Install libcap-dev and libseccomp2-dev so these optional
2620 dependencies get tested on Travis CI. Closes ticket 26560.
2621 - Run asciidoc during Travis CI. Implements ticket 27087.
2622 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2624 o Minor features (geoip):
2625 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2626 Country database. Closes ticket 27089.
2628 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2629 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2630 tell the compiler not to include the system malloc implementation.
2631 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2633 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2634 - Silence a spurious compiler warning on the GetAdaptersAddresses
2635 function pointer cast. This issue is already fixed by 26481 in
2636 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2637 bugfix on 0.2.3.11-alpha.
2638 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2639 supported, and always fails. Some compilers warn about the
2640 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2643 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2644 - Don't link or search for pthreads when building for Windows, even
2645 if we are using build environment (like mingw) that provides a
2646 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2648 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2649 - Skip a pair of unreliable key generation tests on Windows, until
2650 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2651 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2653 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2654 - Pass the module flags to distcheck configure, and log the flags
2655 before running configure. (Backported to 0.2.9 and later as a
2656 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2658 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2659 - When a Travis build fails, and showing a log fails, keep trying to
2660 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2661 - When we use echo in Travis, don't pass a --flag as the first
2662 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2664 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2665 - When voting for recommended versions, make sure that all of the
2666 versions are well-formed and parsable. Fixes bug 26485; bugfix
2669 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2670 - Fix a bug in out sandboxing rules for the openat() syscall.
2671 Previously, no openat() call would be permitted, which would break
2672 filesystem operations on recent glibc versions. Fixes bug 25440;
2673 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2675 o Minor bugfixes (onion services, backport from 0.3.4.8):
2676 - Silence a spurious compiler warning in
2677 rend_client_send_introduction(). Fixes bug 27463; bugfix
2680 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2681 - Log a protocol warning when single onion services or Tor2web clients
2682 fail to authenticate direct connections to relays.
2683 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2685 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2686 - Disable core dumps in test_bt.sh, to avoid failures in "make
2687 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2689 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2690 - Before running make test-network-all, delete old logs and test
2691 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2694 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2695 - Our "tortls/cert_matches_key" unit test no longer relies on
2696 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2697 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2698 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2700 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2701 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2702 27185; bugfix on 0.2.2.2-alpha.
2705 Changes in version 0.3.2.12 - 2018-09-10
2706 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
2708 o Minor features (compatibility, backport from 0.3.4.8):
2709 - Tell OpenSSL to maintain backward compatibility with previous
2710 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2711 ciphers are disabled by default. Closes ticket 27344.
2713 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2714 - Enable macOS builds in our Travis CI configuration. Closes
2716 - Install libcap-dev and libseccomp2-dev so these optional
2717 dependencies get tested on Travis CI. Closes ticket 26560.
2718 - Run asciidoc during Travis CI. Implements ticket 27087.
2719 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2721 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2722 - Use cargo cache in our Travis CI configuration. Closes
2725 o Minor features (controller, backport from 0.3.4.6-rc):
2726 - The control port now exposes the list of HTTPTunnelPorts and
2727 ExtOrPorts via GETINFO net/listeners/httptunnel and
2728 net/listeners/extor respectively. Closes ticket 26647.
2730 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2731 - Authorities no longer vote to make the subprotocol version
2732 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2733 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2735 o Minor features (geoip):
2736 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2737 Country database. Closes ticket 27089.
2739 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2740 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2741 tell the compiler not to include the system malloc implementation.
2742 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2743 - Don't try to use a pragma to temporarily disable the
2744 -Wunused-const-variable warning if the compiler doesn't support
2745 it. Fixes bug 26785; bugfix on 0.3.2.11.
2747 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2748 - Silence a spurious compiler warning on the GetAdaptersAddresses
2749 function pointer cast. This issue is already fixed by 26481 in
2750 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2751 bugfix on 0.2.3.11-alpha.
2752 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2753 supported, and always fails. Some compilers warn about the
2754 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2757 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2758 - Don't link or search for pthreads when building for Windows, even
2759 if we are using build environment (like mingw) that provides a
2760 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2762 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2763 - Skip a pair of unreliable key generation tests on Windows, until
2764 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2765 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2767 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2768 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2769 - Pass the module flags to distcheck configure, and log the flags
2770 before running configure. (Backported to 0.2.9 and later as a
2771 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2773 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2774 - When a Travis build fails, and showing a log fails, keep trying to
2775 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2776 - When we use echo in Travis, don't pass a --flag as the first
2777 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2779 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2780 - When voting for recommended versions, make sure that all of the
2781 versions are well-formed and parsable. Fixes bug 26485; bugfix
2784 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2785 - Fix a bug in out sandboxing rules for the openat() syscall.
2786 Previously, no openat() call would be permitted, which would break
2787 filesystem operations on recent glibc versions. Fixes bug 25440;
2788 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2790 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2791 - Improve the log message when connection initiators fail to
2792 authenticate direct connections to relays. Fixes bug 26927; bugfix
2795 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2796 - Fix bug that causes services to not ever rotate their descriptors
2797 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2800 o Minor bugfixes (onion services, backport from 0.3.4.8):
2801 - Silence a spurious compiler warning in
2802 rend_client_send_introduction(). Fixes bug 27463; bugfix
2805 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2806 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2808 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2809 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2810 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2811 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2813 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2814 - Log a protocol warning when single onion services or Tor2web clients
2815 fail to authenticate direct connections to relays.
2816 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2818 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2819 - Disable core dumps in test_bt.sh, to avoid failures in "make
2820 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2822 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2823 - When running make test-network-all, use the mixed+hs-v2 network.
2824 (A previous fix to chutney removed v3 onion services from the
2825 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2826 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2827 - Before running make test-network-all, delete old logs and test
2828 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2831 o Minor bugfixes (testing, openssl compatibility):
2832 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
2833 internals. Previously, it relied on unsupported OpenSSL behavior in
2834 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
2835 bugfix on 0.2.5.1-alpha.
2837 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2838 - Our "tortls/cert_matches_key" unit test no longer relies on
2839 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2840 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2841 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2843 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2844 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2845 27185; bugfix on 0.2.2.2-alpha.
2848 Changes in version 0.3.3.10 - 2018-09-10
2849 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
2851 o Minor features (bug workaround, backport from 0.3.4.7-rc):
2852 - Compile correctly on systems that provide the C11 stdatomic.h
2853 header, but where C11 atomic functions don't actually compile.
2854 Closes ticket 26779; workaround for Debian issue 903709.
2856 o Minor features (compatibility, backport from 0.3.4.8):
2857 - Tell OpenSSL to maintain backward compatibility with previous
2858 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2859 ciphers are disabled by default. Closes ticket 27344.
2861 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2862 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2863 - Enable macOS builds in our Travis CI configuration. Closes
2865 - Install libcap-dev and libseccomp2-dev so these optional
2866 dependencies get tested on Travis CI. Closes ticket 26560.
2867 - Run asciidoc during Travis CI. Implements ticket 27087.
2868 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2870 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2871 - Use cargo cache in our Travis CI configuration. Closes
2874 o Minor features (controller, backport from 0.3.4.6-rc):
2875 - The control port now exposes the list of HTTPTunnelPorts and
2876 ExtOrPorts via GETINFO net/listeners/httptunnel and
2877 net/listeners/extor respectively. Closes ticket 26647.
2879 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2880 - Authorities no longer vote to make the subprotocol version
2881 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2882 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2884 o Minor features (geoip):
2885 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2886 Country database. Closes ticket 27089.
2888 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2889 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2890 tell the compiler not to include the system malloc implementation.
2891 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2892 - Don't try to use a pragma to temporarily disable the
2893 -Wunused-const-variable warning if the compiler doesn't support
2894 it. Fixes bug 26785; bugfix on 0.3.2.11.
2896 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2897 - Silence a spurious compiler warning on the GetAdaptersAddresses
2898 function pointer cast. This issue is already fixed by 26481 in
2899 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2900 bugfix on 0.2.3.11-alpha.
2901 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2902 supported, and always fails. Some compilers warn about the
2903 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2906 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2907 - Don't link or search for pthreads when building for Windows, even
2908 if we are using build environment (like mingw) that provides a
2909 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2911 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2912 - Skip a pair of unreliable key generation tests on Windows, until
2913 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2914 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2916 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2917 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2918 - Pass the module flags to distcheck configure, and log the flags
2919 before running configure. (Backported to 0.2.9 and later as a
2920 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2922 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2923 - When a Travis build fails, and showing a log fails, keep trying to
2924 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2925 - When we use echo in Travis, don't pass a --flag as the first
2926 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2928 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2929 - When voting for recommended versions, make sure that all of the
2930 versions are well-formed and parsable. Fixes bug 26485; bugfix
2933 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
2934 - Always call tor_free_all() when leaving tor_run_main(). When we
2935 did not, restarting tor in-process would cause an assertion
2936 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
2938 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2939 - Fix a bug in our sandboxing rules for the openat() syscall.
2940 Previously, no openat() call would be permitted, which would break
2941 filesystem operations on recent glibc versions. Fixes bug 25440;
2942 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2944 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2945 - Improve the log message when connection initiators fail to
2946 authenticate direct connections to relays. Fixes bug 26927; bugfix
2949 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2950 - Fix bug that causes services to not ever rotate their descriptors
2951 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2954 o Minor bugfixes (onion services, backport from 0.3.4.8):
2955 - Silence a spurious compiler warning in
2956 rend_client_send_introduction(). Fixes bug 27463; bugfix
2959 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
2960 - Work around two different bugs in the OS X 10.10 and later SDKs
2961 that would prevent us from successfully targeting earlier versions
2962 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
2964 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
2965 - Fix compilation of the unit tests on GNU/Hurd, which does not
2966 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
2969 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2970 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2972 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2973 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2974 - Protover parsing was accepting the presence of whitespace in
2975 version strings, which the C implementation would choke on, e.g.
2976 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
2977 - Protover parsing was ignoring a 2nd hyphen and everything after
2978 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
2980 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2981 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2982 - cd to ${abs_top_builddir}/src/rust before running cargo in
2983 src/test/test_rust.sh. This makes the working directory consistent
2984 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
2986 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2987 - Log a protocol warning when single onion services or Tor2web clients
2988 fail to authenticate direct connections to relays.
2989 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2991 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2992 - Disable core dumps in test_bt.sh, to avoid failures in "make
2993 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2995 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2996 - When running make test-network-all, use the mixed+hs-v2 network.
2997 (A previous fix to chutney removed v3 onion services from the
2998 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2999 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3000 - Before running make test-network-all, delete old logs and test
3001 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3004 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3005 - Our "tortls/cert_matches_key" unit test no longer relies on
3006 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3007 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3008 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3010 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
3011 - Stop sending ed25519 link specifiers in v3 onion service introduce
3012 cells and descriptors, when the rendezvous or introduction point
3013 doesn't support ed25519 link authentication. Fixes bug 26627;
3014 bugfix on 0.3.2.4-alpha.
3016 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3017 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3018 27185; bugfix on 0.2.2.2-alpha.
3021 Changes in version 0.3.4.8 - 2018-09-10
3022 Tor 0.3.4.8 is the first stable release in its series; it includes
3023 compilation and portability fixes.
3025 The Tor 0.3.4 series includes improvements for running Tor in
3026 low-power and embedded environments, which should help performance in
3027 general. We've begun work on better modularity, and included preliminary
3028 changes on the directory authority side to accommodate a new bandwidth
3029 measurement system. We've also integrated more continuous-integration
3030 systems into our development process, and made corresponding changes to
3031 Tor's testing infrastructure. Finally, we've continued to refine
3032 our anti-denial-of-service code.
3034 Below are the changes since 0.3.3.9. For a list of only the changes
3035 since 0.3.4.7-rc, see the ChangeLog file.
3037 o New system requirements:
3038 - Tor no longer tries to support old operating systems without
3039 mmap() or some local equivalent. Apparently, compilation on such
3040 systems has been broken for some time, without anybody noticing or
3041 complaining. Closes ticket 25398.
3043 o Major features (directory authority, modularization):
3044 - The directory authority subsystem has been modularized. The code
3045 is now located in src/or/dirauth/, and is compiled in by default.
3046 To disable the module, the configure option
3047 --disable-module-dirauth has been added. This module may be
3048 disabled by default in some future release. Closes ticket 25610.
3050 o Major features (main loop, CPU usage):
3051 - When Tor is disabled (via DisableNetwork or via hibernation), it
3052 no longer needs to run any per-second events. This change should
3053 make it easier for mobile applications to disable Tor while the
3054 device is sleeping, or Tor is not running. Closes ticket 26063.
3055 - Tor no longer enables all of its periodic events by default.
3056 Previously, Tor would enable all possible main loop events,
3057 regardless of whether it needed them. Furthermore, many of these
3058 events are now disabled when Tor is hibernating or DisableNetwork
3059 is set. This is a big step towards reducing client CPU usage by
3060 reducing the amount of wake-ups the daemon does. Closes tickets
3062 - The bandwidth-limitation logic has been refactored so that
3063 bandwidth calculations are performed on-demand, rather than every
3064 TokenBucketRefillInterval milliseconds. This change should improve
3065 the granularity of our bandwidth calculations, and limit the
3066 number of times that the Tor process needs to wake up when it is
3067 idle. Closes ticket 25373.
3068 - Move responsibility for many operations from a once-per-second
3069 callback to a callback that is only scheduled as needed. Moving
3070 this functionality has allowed us to disable the callback when
3071 Tor's network is disabled. Once enough items are removed from our
3072 once-per-second callback, we can eliminate it entirely to conserve
3073 CPU when idle. The functionality removed includes: closing
3074 connections, circuits, and channels (ticket 25932); consensus
3075 voting (25937); flushing log callbacks (25951); honoring delayed
3076 SIGNEWNYM requests (25949); rescanning the consensus cache
3077 (25931); saving the state file to disk (25948); warning relay
3078 operators about unreachable ports (25952); and keeping track of
3079 Tor's uptime (26009).
3081 o Minor features (accounting):
3082 - When Tor becomes dormant, it now uses a scheduled event to wake up
3083 at the right time. Previously, we would use the per-second timer
3084 to check whether to wake up, but we no longer have any per-second
3085 timers enabled when the network is disabled. Closes ticket 26064.
3087 o Minor features (bug workaround):
3088 - Compile correctly on systems that provide the C11 stdatomic.h
3089 header, but where C11 atomic functions don't actually compile.
3090 Closes ticket 26779; workaround for Debian issue 903709.
3092 o Minor features (code quality):
3093 - Add optional spell-checking for the Tor codebase, using the
3094 "misspell" program. To use this feature, run "make check-typos".
3095 Closes ticket 25024.
3097 o Minor features (compatibility):
3098 - Tell OpenSSL to maintain backward compatibility with previous
3099 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3100 ciphers are disabled by default. Closes ticket 27344.
3101 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
3102 the no-deprecated option, and builds correctly with them. Closes
3103 tickets 19429, 19981, and 25353.
3105 o Minor features (compilation):
3106 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3107 tell the compiler not to include the system malloc implementation.
3108 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3109 - Don't try to use a pragma to temporarily disable the
3110 -Wunused-const-variable warning if the compiler doesn't support
3111 it. Fixes bug 26785; bugfix on 0.3.2.11.
3112 - When building Tor, prefer to use Python 3 over Python 2, and more
3113 recent (contemplated) versions over older ones. Closes
3116 o Minor features (compression, zstd):
3117 - When running with zstd, Tor now considers using advanced functions
3118 that the zstd maintainers have labeled as potentially unstable. To
3119 prevent breakage, Tor will only use this functionality when the
3120 runtime version of the zstd library matches the version with which
3121 Tor was compiled. Closes ticket 25162.
3123 o Minor features (configuration):
3124 - The "DownloadSchedule" options have been renamed to end with
3125 "DownloadInitialDelay". The old names are still allowed, but will
3126 produce a warning. Comma-separated lists are still permitted for
3127 these options, but all values after the first are ignored (as they
3128 have been since 0.2.9). Closes ticket 23354.
3130 o Minor features (continuous integration):
3131 - Log the compiler path and version during Appveyor builds.
3132 Implements ticket 27449.
3133 - Show config.log and test-suite.log after failed Appveyor builds.
3134 Also upload the zipped full logs as a build artifact. Implements
3136 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3137 - Enable macOS builds in our Travis CI configuration. Closes
3139 - Install libcap-dev and libseccomp2-dev so these optional
3140 dependencies get tested on Travis CI. Closes ticket 26560.
3141 - Only post Appveyor IRC notifications when the build fails.
3142 Implements ticket 27275.
3143 - Run asciidoc during Travis CI. Implements ticket 27087.
3144 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3145 - Add the necessary configuration files for continuous integration
3146 testing on Windows, via the Appveyor platform. Closes ticket
3147 25549. Patches from Marcin Cieślak and Isis Lovecruft.
3149 o Minor features (continuous integration, rust):
3150 - Use cargo cache in our Travis CI configuration. Closes
3153 o Minor features (control port):
3154 - Introduce GETINFO "current-time/{local,utc}" to return the local
3155 and UTC times respectively in ISO format. This helps a controller
3156 like Tor Browser detect a time-related error. Closes ticket 25511.
3157 Patch by Neel Chauhan.
3158 - Introduce new fields to the CIRC_BW event. There are two new
3159 fields in each of the read and written directions. The DELIVERED
3160 fields report the total valid data on the circuit, as measured by
3161 the payload sizes of verified and error-checked relay command
3162 cells. The OVERHEAD fields report the total unused bytes in each
3163 of these cells. Closes ticket 25903.
3165 o Minor features (controller):
3166 - The control port now exposes the list of HTTPTunnelPorts and
3167 ExtOrPorts via GETINFO net/listeners/httptunnel and
3168 net/listeners/extor respectively. Closes ticket 26647.
3170 o Minor features (directory authorities):
3171 - Stop warning about incomplete bw lines before the first complete
3172 bw line has been found, so that additional header lines can be
3173 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
3174 - Authorities no longer vote to make the subprotocol version
3175 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3176 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3178 o Minor features (directory authority):
3179 - Directory authorities now open their key-pinning files as O_SYNC,
3180 to limit their chances of accidentally writing partial lines.
3181 Closes ticket 23909.
3183 o Minor features (directory authority, forward compatibility):
3184 - Make the lines of the measured bandwidth file able to contain
3185 their entries in any order. Previously, the node_id entry needed
3186 to come first. Closes ticket 26004.
3188 o Minor features (entry guards):
3189 - Introduce a new torrc option NumPrimaryGuards for controlling the
3190 number of primary guards. Closes ticket 25843.
3192 o Minor features (geoip):
3193 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3194 Country database. Closes ticket 27089.
3196 o Minor features (performance):
3197 - Avoid a needless call to malloc() when processing an incoming
3198 relay cell. Closes ticket 24914.
3199 - Make our timing-wheel code run a tiny bit faster on 32-bit
3200 platforms, by preferring 32-bit math to 64-bit. Closes
3202 - Avoid a needless malloc()/free() pair every time we handle an ntor
3203 handshake. Closes ticket 25150.
3205 o Minor features (Rust, portability):
3206 - Rust cross-compilation is now supported. Closes ticket 25895.
3208 o Minor features (testing):
3209 - Add a unit test for voting_schedule_get_start_of_next_interval().
3210 Closes ticket 26014, and helps make unit test coverage
3212 - A new unittests module specifically for testing the functions in
3213 the (new-ish) bridges.c module has been created with new
3214 unittests, raising the code coverage percentages. Closes 25425.
3215 - We now have improved testing for addressmap_get_virtual_address()
3216 function. This should improve our test coverage, and make our test
3217 coverage more deterministic. Closes ticket 25993.
3219 o Minor features (timekeeping, circuit scheduling):
3220 - When keeping track of how busy each circuit have been recently on
3221 a given connection, use coarse-grained monotonic timers rather
3222 than gettimeofday(). This change should marginally increase
3223 accuracy and performance. Implements part of ticket 25927.
3225 o Minor features (unit tests):
3226 - Test complete bandwidth measurements files, and test that
3227 incomplete bandwidth lines only give warnings when the end of the
3228 header has not been detected. Fixes bug 25947; bugfix
3231 o Minor bugfixes (bandwidth management):
3232 - Consider ourselves "low on write bandwidth" if we have exhausted
3233 our write bandwidth some time in the last second. This was the
3234 documented behavior before, but the actual behavior was to change
3235 this value every TokenBucketRefillInterval. Fixes bug 25828;
3236 bugfix on 0.2.3.5-alpha.
3238 o Minor bugfixes (C correctness):
3239 - Add a missing lock acquisition in the shutdown code of the control
3240 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
3241 Coverity; this is CID 1433643.
3243 o Minor bugfixes (code style):
3244 - Fixed multiple includes of transports.h in src/or/connection.c
3245 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
3246 - Remove the unused variable n_possible from the function
3247 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
3249 o Minor bugfixes (compilation):
3250 - Silence a spurious compiler warning on the GetAdaptersAddresses
3251 function pointer cast. This issue is already fixed by 26481 in
3252 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3253 bugfix on 0.2.3.11-alpha.
3254 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3255 supported, and always fails. Some compilers warn about the
3256 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3258 - Fix a compilation warning on some versions of GCC when building
3259 code that calls routerinfo_get_my_routerinfo() twice, assuming
3260 that the second call will succeed if the first one did. Fixes bug
3261 26269; bugfix on 0.2.8.2-alpha.
3262 - Refrain from compiling unit testing related object files when
3263 --disable-unittests is set to configure script. Fixes bug 24891;
3264 bugfix on 0.2.5.1-alpha.
3265 - The --enable-fatal-warnings flag now affects Rust code as well.
3266 Closes ticket 26245.
3267 - Avoid a compiler warning when casting the return value of
3268 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
3269 26283; bugfix on 0.2.4.10-alpha.
3271 o Minor bugfixes (compilation, windows):
3272 - Don't link or search for pthreads when building for Windows, even
3273 if we are using build environment (like mingw) that provides a
3274 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3276 o Minor bugfixes (continuous integration):
3277 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3278 - Skip a pair of unreliable key generation tests on Windows, until
3279 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3280 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3282 o Minor bugfixes (control port):
3283 - Respond with more human-readable error messages to GETINFO exit-
3284 policy/* requests. Also, let controller know if an error is
3285 transient (response code 551) or not (response code 552). Fixes
3286 bug 25852; bugfix on 0.2.8.1-alpha.
3287 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
3288 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
3289 on 0.3.3.1-alpha. Patch by "akwizgran".
3290 - Make CIRC_BW event reflect the total of all data sent on a
3291 circuit, including padding and dropped cells. Also fix a mis-
3292 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
3293 bugfix on 0.2.5.2-alpha.
3295 o Minor bugfixes (correctness, flow control):
3296 - Upon receiving a stream-level SENDME cell, verify that our window
3297 has not grown too large. Fixes bug 26214; bugfix on svn
3300 o Minor bugfixes (directory authority):
3301 - When voting for recommended versions, make sure that all of the
3302 versions are well-formed and parsable. Fixes bug 26485; bugfix
3305 o Minor bugfixes (directory client):
3306 - When unverified-consensus is verified, rename it to cached-
3307 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
3308 - Fixed launching a certificate fetch always during the scheduled
3309 periodic consensus fetch by fetching only in those cases when
3310 consensus are waiting for certs. Fixes bug 24740; bugfix
3313 o Minor bugfixes (error reporting):
3314 - Improve tolerance for directory authorities with skewed clocks.
3315 Previously, an authority with a clock more than 60 seconds ahead
3316 could cause a client with a correct clock to warn that the
3317 client's clock was behind. Now the clocks of a majority of
3318 directory authorities have to be ahead of the client before this
3319 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
3321 o Minor bugfixes (in-process restart):
3322 - Always call tor_free_all() when leaving tor_run_main(). When we
3323 did not, restarting tor in-process would cause an assertion
3324 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3326 o Minor bugfixes (Linux seccomp2 sandbox):
3327 - Fix a bug in our sandboxing rules for the openat() syscall.
3328 Previously, no openat() call would be permitted, which would break
3329 filesystem operations on recent glibc versions. Fixes bug 25440;
3330 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3332 o Minor bugfixes (logging):
3333 - Improve the log message when connection initiators fail to
3334 authenticate direct connections to relays. Fixes bug 26927; bugfix
3337 o Minor bugfixes (onion services):
3338 - Silence a spurious compiler warning in
3339 rend_client_send_introduction(). Fixes bug 27463; bugfix
3341 - Fix bug that causes services to not ever rotate their descriptors
3342 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3344 - Recompute some consensus information after detecting a clock jump,
3345 or after transitioning from a non-live consensus to a live
3346 consensus. We do this to avoid having an outdated state, and
3347 miscalculating the index for next-generation onion services. Fixes
3348 bug 24977; bugfix on 0.3.2.1-alpha.
3350 o Minor bugfixes (portability):
3351 - Fix compilation of the unit tests on GNU/Hurd, which does not
3352 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3354 - Work around two different bugs in the OS X 10.10 and later SDKs
3355 that would prevent us from successfully targeting earlier versions
3356 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3357 - Do not align mmap length, as it is not required by POSIX, and the
3358 getpagesize function is deprecated. Fixes bug 25399; bugfix
3361 o Minor bugfixes (portability, FreeBSD):
3362 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
3363 does not stringify on FreeBSD, so we switch to tor_asprintf().
3364 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
3366 o Minor bugfixes (relay statistics):
3367 - When a relay is collecting internal statistics about how many
3368 create cell requests it has seen of each type, accurately count
3369 the requests from relays that temporarily fall out of the
3370 consensus. (To be extra conservative, we were already ignoring
3371 requests from clients in our counts, and we continue ignoring them
3372 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
3374 o Minor bugfixes (rust):
3375 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3377 - Protover parsing was accepting the presence of whitespace in
3378 version strings, which the C implementation would choke on, e.g.
3379 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3380 - Protover parsing was ignoring a 2nd hyphen and everything after
3381 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3383 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3384 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3385 - cd to ${abs_top_builddir}/src/rust before running cargo in
3386 src/test/test_rust.sh. This makes the working directory consistent
3387 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3389 o Minor bugfixes (single onion services, Tor2web):
3390 - Log a protocol warning when single onion services or Tor2web
3391 clients fail to authenticate direct connections to relays. Fixes
3392 bug 26924; bugfix on 0.2.9.1-alpha.
3394 o Minor bugfixes (test coverage tools):
3395 - Update our "cov-diff" script to handle output from the latest
3396 version of gcov, and to remove extraneous timestamp information
3397 from its output. Fixes bugs 26101 and 26102; bugfix
3400 o Minor bugfixes (testing):
3401 - Disable core dumps in test_bt.sh, to avoid failures in "make
3402 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3403 - When testing workqueue event-cancellation, make sure that we
3404 actually cancel an event, and that cancel each event with equal
3405 probability. (It was previously possible, though extremely
3406 unlikely, for our event-canceling test not to cancel any events.)
3407 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
3408 - Repeat part of the test in test_client_pick_intro() a number of
3409 times, to give it consistent coverage. Fixes bug 25996; bugfix
3411 - Remove randomness from the hs_common/responsible_hsdirs test, so
3412 that it always takes the same path through the function it tests.
3413 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
3414 - Change the behavior of the "channel/outbound" test so that it
3415 never causes a 10-second rollover for the EWMA circuitmux code.
3416 Previously, this behavior would happen randomly, and result in
3417 fluctuating test coverage. Fixes bug 25994; bugfix
3419 - Use X509_new() to allocate certificates that will be freed later
3420 with X509_free(). Previously, some parts of the unit tests had
3421 used tor_malloc_zero(), which is incorrect, and which caused test
3422 failures on Windows when they were built with extra hardening.
3423 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
3425 - While running the circuit_timeout test, fix the PRNG to a
3426 deterministic AES stream, so that the test coverage from this test
3427 will itself be deterministic. Fixes bug 25995; bugfix
3430 o Minor bugfixes (testing, bootstrap):
3431 - When calculating bootstrap progress, check exit policies and the
3432 exit flag. Previously, Tor would only check the exit flag, which
3433 caused race conditions in small and fast networks like chutney.
3434 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
3436 o Minor bugfixes (testing, chutney):
3437 - When running make test-network-all, use the mixed+hs-v2 network.
3438 (A previous fix to chutney removed v3 onion services from the
3439 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3440 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3441 - Before running make test-network-all, delete old logs and test
3442 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3445 o Minor bugfixes (testing, openssl compatibility):
3446 - Our "tortls/cert_matches_key" unit test no longer relies on
3447 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3448 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3449 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3451 o Minor bugfixes (v3 onion services):
3452 - Stop sending ed25519 link specifiers in v3 onion service introduce
3453 cells and descriptors, when the rendezvous or introduction point
3454 doesn't support ed25519 link authentication. Fixes bug 26627;
3455 bugfix on 0.3.2.4-alpha.
3457 o Minor bugfixes (vanguards):
3458 - Allow the last hop in a vanguard circuit to be the same as our
3459 first, to prevent the adversary from influencing guard node choice
3460 by choice of last hop. Also prevent the creation of A - B - A
3461 paths, or A - A paths, which are forbidden by relays. Fixes bug
3462 25870; bugfix on 0.3.3.1-alpha.
3464 o Minor bugfixes (Windows, compilation):
3465 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3466 27185; bugfix on 0.2.2.2-alpha.
3468 o Code simplification and refactoring:
3469 - Remove duplicate code in parse_{c,s}method_line and bootstrap
3470 their functionalities into a single function. Fixes bug 6236;
3471 bugfix on 0.2.3.6-alpha.
3472 - We remove the PortForwarding and PortForwardingHelper options,
3473 related functions, and the port_forwarding tests. These options
3474 were used by the now-deprecated Vidalia to help ordinary users
3475 become Tor relays or bridges. Closes ticket 25409. Patch by
3477 - In order to make the OR and dir checking function in router.c less
3478 confusing we renamed some functions and
3479 consider_testing_reachability() has been split into
3480 router_should_check_reachability() and
3481 router_do_reachability_checks(). Also we improved the documentation
3482 in some functions. Closes ticket 18918.
3483 - Initial work to isolate Libevent usage to a handful of modules in
3484 our codebase, to simplify our call structure, and so that we can
3485 more easily change event loops in the future if needed. Closes
3487 - Introduce a function to call getsockname() and return tor_addr_t,
3488 to save a little complexity throughout the codebase. Closes
3490 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
3491 as hsdir_index is always present. Also, we move hsdir_index_t into
3492 or.h. Closes ticket 23094. Patch by Neel Chauhan.
3493 - Merge functions used for describing nodes and suppress the
3494 functions that do not allocate memory for the output buffer
3495 string. NODE_DESC_BUF_LEN constant and format_node_description()
3496 function cannot be used externally from router.c module anymore.
3497 Closes ticket 25432. Patch by valentecaio.
3498 - Our main loop has been simplified so that all important operations
3499 happen inside events. Previously, some operations had to happen
3500 outside the event loop, to prevent infinite sequences of event
3501 activations. Closes ticket 25374.
3502 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
3503 it in register_intro_circ() and service_intro_point_new(). This
3504 prevents the digest from being re-calculated each time. Closes
3505 ticket 23107. Patch by Neel Chauhan.
3506 - Refactor token-bucket implementations to use a common backend.
3507 Closes ticket 25766.
3508 - Remove extern declaration of stats_n_seconds_working variable from
3509 main, protecting its accesses with get_uptime() and reset_uptime()
3510 functions. Closes ticket 25081, patch by “valentecaio”.
3511 - Remove our previous logic for "cached gettimeofday()" -- our
3512 coarse monotonic timers are fast enough for this purpose, and far
3513 less error-prone. Implements part of ticket 25927.
3514 - Remove the return value for fascist_firewall_choose_address_base(),
3515 and sister functions such as fascist_firewall_choose_address_node()
3516 and fascist_firewall_choose_address_rs(). Also, while we're here,
3517 initialize the ap argument as leaving it uninitialized can pose a
3518 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
3519 - Rename two fields of connection_t struct. timestamp_lastwritten is
3520 renamed to timestamp_last_write_allowed and timestamp_lastread is
3521 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
3523 - Since Tor requires C99, remove our old workaround code for libc
3524 implementations where free(NULL) doesn't work. Closes ticket 24484.
3525 - Use our standard rate-limiting code to deal with excessive
3526 libevent failures, rather than the hand-rolled logic we had
3527 before. Closes ticket 26016.
3528 - We remove the return value of node_get_prim_orport() and
3529 node_get_prim_dirport(), and introduce node_get_prim_orport() in
3530 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
3531 check for a null address. Closes ticket 23873. Patch by
3533 - We switch to should_record_bridge_info() in
3534 geoip_note_client_seen() and options_need_geoip_info() instead of
3535 accessing the configuration values directly. Fixes bug 25290;
3536 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
3538 o Deprecated features:
3539 - As we are not recommending 0.2.5 anymore, we require relays that
3540 once had an ed25519 key associated with their RSA key to always
3541 have that key, instead of allowing them to drop back to a version
3542 that didn't support ed25519. This means they need to use a new RSA
3543 key if they want to downgrade to an older version of tor without
3544 ed25519. Closes ticket 20522.
3547 - Directory authorities will no longer support voting according to
3548 any consensus method before consensus method 25. This keeps
3549 authorities compatible with all authorities running 0.2.9.8 and
3550 later, and does not break any clients or relays. Implements ticket
3551 24378 and proposal 290.
3552 - The PortForwarding and PortForwardingHelper features have been
3553 removed. The reasoning is, given that implementations of NAT
3554 traversal protocols within common consumer grade routers are
3555 frequently buggy, and that the target audience for a NAT punching
3556 feature is a perhaps less-technically-inclined relay operator,
3557 when the helper fails to setup traversal the problems are usually
3558 deep, ugly, and very router specific, making them horrendously
3559 impossible for technical support to reliable assist with, and thus
3560 resulting in frustration all around. Unfortunately, relay
3561 operators who would like to run relays behind NATs will need to
3562 become more familiar with the port forwarding configurations on
3563 their local router. Closes 25409.
3564 - The TestingEnableTbEmptyEvent option has been removed. It was used
3565 in testing simulations to measure how often connection buckets
3566 were emptied, in order to improve our scheduling, but it has not
3567 been actively used in years. Closes ticket 25760.
3568 - The old "round-robin" circuit multiplexer (circuitmux)
3569 implementation has been removed, along with a fairly large set of
3570 code that existed to support it. It has not been the default
3571 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
3572 but it still required an unreasonable amount of memory and CPU.
3573 Closes ticket 25268.
3576 Changes in version 0.3.3.9 - 2018-07-13
3577 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
3578 bridge relays should upgrade.
3580 o Directory authority changes:
3581 - The "Bifroest" bridge authority has been retired; the new bridge
3582 authority is "Serge", and it is operated by George from the
3583 TorBSD project. Closes ticket 26771.
3586 Changes in version 0.3.2.11 - 2018-07-13
3587 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
3588 bridge relays should upgrade. We also take this opportunity to backport
3591 o Directory authority changes:
3592 - The "Bifroest" bridge authority has been retired; the new bridge
3593 authority is "Serge", and it is operated by George from the
3594 TorBSD project. Closes ticket 26771.
3596 o Directory authority changes (backport from 0.3.3.7):
3597 - Add an IPv6 address for the "dannenberg" directory authority.
3598 Closes ticket 26343.
3600 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3601 - When directory authorities read a zero-byte bandwidth file, they
3602 would previously log a warning with the contents of an
3603 uninitialised buffer. They now log a warning about the empty file
3604 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3606 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3607 - Correctly detect when onion services get disabled after HUP. Fixes
3608 bug 25761; bugfix on 0.3.2.1.
3610 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3611 - Explicitly permit the poll() system call when the Linux
3612 seccomp2-based sandbox is enabled: apparently, some versions of
3613 libc use poll() when calling getpwnam(). Closes ticket 25313.
3615 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
3616 - Update the Travis CI configuration to use the stable Rust channel,
3617 now that we have decided to require that. Closes ticket 25714.
3619 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3620 - Our .travis.yml configuration now includes support for testing the
3621 results of "make distcheck". (It's not uncommon for "make check"
3622 to pass but "make distcheck" to fail.) Closes ticket 25814.
3623 - Our Travis CI configuration now integrates with the Coveralls
3624 coverage analysis tool. Closes ticket 25818.
3626 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3627 - Add several checks to detect whether Tor relays are uploading
3628 their descriptors without specifying why they regenerated them.
3629 Diagnostic for ticket 25686.
3631 o Minor features (compilation, backport from 0.3.4.4-rc):
3632 - When building Tor, prefer to use Python 3 over Python 2, and more
3633 recent (contemplated) versions over older ones. Closes
3636 o Minor features (geoip):
3637 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3638 Country database. Closes ticket 26674.
3640 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3641 - Upon receiving a malformed connected cell, stop processing the
3642 cell immediately. Previously we would mark the connection for
3643 close, but continue processing the cell as if the connection were
3644 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3646 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3647 - Allow the nanosleep() system call, which glibc uses to implement
3648 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3650 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3651 - When running the hs_ntor_ref.py test, make sure only to pass
3652 strings (rather than "bytes" objects) to the Python subprocess
3653 module. Python 3 on Windows seems to require this. Fixes bug
3654 26535; bugfix on 0.3.1.1-alpha.
3655 - When running the ntor_ref.py test, make sure only to pass strings
3656 (rather than "bytes" objects) to the Python subprocess module.
3657 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3660 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3661 - Work around a change in OpenSSL 1.1.1 where return values that
3662 would previously indicate "no password" now indicate an empty
3663 password. Without this workaround, Tor instances running with
3664 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3665 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3667 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
3668 - Document that the PerConnBW{Rate,Burst} options will fall back to
3669 their corresponding consensus parameters only if those parameters
3670 are set. Previously we had claimed that these values would always
3671 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3673 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3674 - Fix a compilation warning on some versions of GCC when building
3675 code that calls routerinfo_get_my_routerinfo() twice, assuming
3676 that the second call will succeed if the first one did. Fixes bug
3677 26269; bugfix on 0.2.8.2-alpha.
3679 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3680 - Don't consider Tor running as a client if the ControlPort is open,
3681 but no actual client ports are open. Fixes bug 26062; bugfix
3684 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3685 - Prevent a possible out-of-bounds smartlist read in
3686 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3688 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3689 - Fix a very unlikely (impossible, we believe) null pointer
3690 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3691 Coverity; this is CID 1430932.
3693 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3694 - Fix a memory leak when a v3 onion service is configured and gets a
3695 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3696 - When parsing the descriptor signature, look for the token plus an
3697 extra white-space at the end. This is more correct but also will
3698 allow us to support new fields that might start with "signature".
3699 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3701 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3702 - Relays now correctly block attempts to re-extend to the previous
3703 relay by Ed25519 identity. Previously they would warn in this
3704 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3707 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3708 - Avoid a crash when running with DirPort set but ORPort turned off.
3709 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3711 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3712 - Silence unused-const-variable warnings in zstd.h with some GCC
3713 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3715 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
3716 - Avoid intermittent test failures due to a test that had relied on
3717 onion service introduction point creation finishing within 5
3718 seconds of real clock time. Fixes bug 25450; bugfix
3721 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
3722 - Fix a C99 compliance issue in our configuration script that caused
3723 compilation issues when compiling Tor with certain versions of
3724 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3726 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3727 - Fix a number of small memory leaks identified by coverity. Fixes
3728 bug 26467; bugfix on numerous Tor versions.
3730 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3731 - Move the list of default directory authorities to its own file.
3732 Closes ticket 24854. Patch by "beastr0".
3735 Changes in version 0.2.9.16 - 2018-07-13
3736 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
3737 bridge relays should upgrade. We also take this opportunity to backport
3740 o Directory authority changes:
3741 - The "Bifroest" bridge authority has been retired; the new bridge
3742 authority is "Serge", and it is operated by George from the
3743 TorBSD project. Closes ticket 26771.
3745 o Directory authority changes (backport from 0.3.3.7):
3746 - Add an IPv6 address for the "dannenberg" directory authority.
3747 Closes ticket 26343.
3749 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3750 - When directory authorities read a zero-byte bandwidth file, they
3751 would previously log a warning with the contents of an
3752 uninitialised buffer. They now log a warning about the empty file
3753 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3755 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3756 - Explicitly permit the poll() system call when the Linux
3757 seccomp2-based sandbox is enabled: apparently, some versions of
3758 libc use poll() when calling getpwnam(). Closes ticket 25313.
3760 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3761 - Our .travis.yml configuration now includes support for testing the
3762 results of "make distcheck". (It's not uncommon for "make check"
3763 to pass but "make distcheck" to fail.) Closes ticket 25814.
3764 - Our Travis CI configuration now integrates with the Coveralls
3765 coverage analysis tool. Closes ticket 25818.
3767 o Minor features (compilation, backport from 0.3.4.4-rc):
3768 - When building Tor, prefer to use Python 3 over Python 2, and more
3769 recent (contemplated) versions over older ones. Closes
3772 o Minor features (geoip):
3773 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3774 Country database. Closes ticket 26674.
3776 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3777 - Upon receiving a malformed connected cell, stop processing the
3778 cell immediately. Previously we would mark the connection for
3779 close, but continue processing the cell as if the connection were
3780 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3782 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3783 - Allow the nanosleep() system call, which glibc uses to implement
3784 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3786 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3787 - When running the ntor_ref.py test, make sure only to pass strings
3788 (rather than "bytes" objects) to the Python subprocess module.
3789 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3792 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3793 - Work around a change in OpenSSL 1.1.1 where return values that
3794 would previously indicate "no password" now indicate an empty
3795 password. Without this workaround, Tor instances running with
3796 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3797 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3799 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3800 - Fix a compilation warning on some versions of GCC when building
3801 code that calls routerinfo_get_my_routerinfo() twice, assuming
3802 that the second call will succeed if the first one did. Fixes bug
3803 26269; bugfix on 0.2.8.2-alpha.
3805 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3806 - Don't consider Tor running as a client if the ControlPort is open,
3807 but no actual client ports are open. Fixes bug 26062; bugfix
3810 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3811 - Prevent a possible out-of-bounds smartlist read in
3812 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3814 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3815 - Fix a very unlikely (impossible, we believe) null pointer
3816 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3817 Coverity; this is CID 1430932.
3819 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3820 - Fix a number of small memory leaks identified by coverity. Fixes
3821 bug 26467; bugfix on numerous Tor versions.
3823 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3824 - Move the list of default directory authorities to its own file.
3825 Closes ticket 24854. Patch by "beastr0".
3828 Changes in version 0.3.3.8 - 2018-07-09
3829 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
3830 fixes for a memory leak affecting directory authorities.
3832 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
3833 - Stop leaking memory on directory authorities when planning to
3834 vote. This bug was crashing authorities by exhausting their
3835 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3837 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
3838 - Make sure that failing tests in Rust will actually cause the build
3839 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3842 o Minor features (compilation, backport from 0.3.4.4-rc):
3843 - When building Tor, prefer to use Python 3 over Python 2, and more
3844 recent (contemplated) versions over older ones. Closes
3847 o Minor features (geoip):
3848 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3849 Country database. Closes ticket 26674.
3851 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3852 - Add several checks to detect whether Tor relays are uploading
3853 their descriptors without specifying why they regenerated them.
3854 Diagnostic for ticket 25686.
3856 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
3857 - Don't count path selection failures as circuit build failures.
3858 This change should eliminate cases where Tor blames its guard or
3859 the network for situations like insufficient microdescriptors
3860 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
3863 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3864 - Fix a compilation warning on some versions of GCC when building
3865 code that calls routerinfo_get_my_routerinfo() twice, assuming
3866 that the second call will succeed if the first one did. Fixes bug
3867 26269; bugfix on 0.2.8.2-alpha.
3869 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
3870 - Handle the HSADDRESS= argument to the HSPOST command properly.
3871 (Previously, this argument was misparsed and thus ignored.) Fixes
3872 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3874 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3875 - Fix a number of small memory leaks identified by coverity. Fixes
3876 bug 26467; bugfix on numerous Tor versions.
3878 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3879 - Relays now correctly block attempts to re-extend to the previous
3880 relay by Ed25519 identity. Previously they would warn in this
3881 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3884 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
3885 - When shutting down, Tor now clears all the flags in the control.c
3886 module. This should prevent a bug where authentication cookies are
3887 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
3889 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3890 - When running the hs_ntor_ref.py test, make sure only to pass
3891 strings (rather than "bytes" objects) to the Python subprocess
3892 module. Python 3 on Windows seems to require this. Fixes bug
3893 26535; bugfix on 0.3.1.1-alpha.
3894 - When running the ntor_ref.py test, make sure only to pass strings
3895 (rather than "bytes" objects) to the Python subprocess module.
3896 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3900 Changes in version 0.3.3.7 - 2018-06-12
3901 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
3902 fixes for bugs affecting compatibility and stability.
3904 o Directory authority changes:
3905 - Add an IPv6 address for the "dannenberg" directory authority.
3906 Closes ticket 26343.
3908 o Minor features (geoip):
3909 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3910 Country database. Closes ticket 26351.
3912 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3913 - Work around a change in OpenSSL 1.1.1 where return values that
3914 would previously indicate "no password" now indicate an empty
3915 password. Without this workaround, Tor instances running with
3916 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3917 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3919 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3920 - Silence unused-const-variable warnings in zstd.h with some GCC
3921 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3923 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
3924 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3925 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3926 miscounting the total number of circuits for these field values.)
3927 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3929 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3930 - Prevent a possible out-of-bounds smartlist read in
3931 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3933 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
3934 - Only select relays when they have the descriptors we prefer to use
3935 for them. This change fixes a bug where we could select a relay
3936 because it had _some_ descriptor, but reject it later with a
3937 nonfatal assertion error because it didn't have the exact one we
3938 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3941 Changes in version 0.3.3.6 - 2018-05-22
3942 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
3943 backports several important fixes from the 0.3.4.1-alpha.
3945 The Tor 0.3.3 series includes controller support and other
3946 improvements for v3 onion services, official support for embedding Tor
3947 within other applications, and our first non-trivial module written in
3948 the Rust programming language. (Rust is still not enabled by default
3949 when building Tor.) And as usual, there are numerous other smaller
3950 bugfixes, features, and improvements.
3952 Below are the changes since 0.3.2.10. For a list of only the changes
3953 since 0.3.3.5-rc, see the ChangeLog file.
3955 o New system requirements:
3956 - When built with Rust, Tor now depends on version 0.2.39 of the
3957 libc crate. Closes tickets 25310 and 25664.
3959 o Major features (embedding):
3960 - There is now a documented stable API for programs that need to
3961 embed Tor. See tor_api.h for full documentation and known bugs.
3962 Closes ticket 23684.
3963 - Tor now has support for restarting in the same process.
3964 Controllers that run Tor using the "tor_api.h" interface can now
3965 restart Tor after Tor has exited. This support is incomplete,
3966 however: we fixed crash bugs that prevented it from working at
3967 all, but many bugs probably remain, including a possibility of
3968 security issues. Implements ticket 24581.
3970 o Major features (IPv6, directory documents):
3971 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
3972 consensus. This information makes it easier for IPv6 clients to
3973 bootstrap and choose reachable entry guards. Implements
3975 - Add consensus method 28, which removes IPv6 ORPorts from
3976 microdescriptors. Now that the consensus contains IPv6 ORPorts,
3977 they are redundant in microdescs. This change will be used by Tor
3978 clients on 0.2.8.x and later. (That is to say, with all Tor
3979 clients that have IPv6 bootstrap and guard support.) Implements
3981 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
3982 set by different numbers of authorities. Fixes 23870
3985 o Major features (onion service v3, control port):
3986 - The control port now supports commands and events for v3 onion
3987 services. It is now possible to create ephemeral v3 services using
3988 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
3989 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
3990 DEL_ONION) have been extended to support v3 onion services. Closes
3991 ticket 20699; implements proposal 284.
3993 o Major features (onion services):
3994 - Provide torrc options to pin the second and third hops of onion
3995 service circuits to a list of nodes. The option HSLayer2Guards
3996 pins the second hop, and the option HSLayer3Guards pins the third
3997 hop. These options are for use in conjunction with experiments
3998 with "vanguards" for preventing guard enumeration attacks. Closes
4000 - When v3 onion service clients send introduce cells, they now
4001 include the IPv6 address of the rendezvous point, if it has one.
4002 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
4003 in future Tor versions, IPv6-only v3 single onion services will be
4004 able to use IPv6 addresses to connect directly to the rendezvous
4005 point. Closes ticket 23577. Patch by Neel Chauhan.
4007 o Major features (relay):
4008 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
4009 operator to use a more reasonable ("reduced") exit policy, rather
4010 than the default one. If you want to run an exit node without
4011 thinking too hard about which ports to allow, this one is for you.
4012 Closes ticket 13605. Patch from Neel Chauhan.
4014 o Major features (rust, portability, experimental):
4015 - Tor now ships with an optional implementation of one of its
4016 smaller modules (protover.c) in the Rust programming language. To
4017 try it out, install a Rust build environment, and configure Tor
4018 with "--enable-rust --enable-cargo-online-mode". This should not
4019 cause any user-visible changes, but should help us gain more
4020 experience with Rust, and plan future Rust integration work.
4021 Implementation by Chelsea Komlo. Closes ticket 22840.
4023 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
4024 - When directory authorities read a zero-byte bandwidth file, they
4025 would previously log a warning with the contents of an
4026 uninitialised buffer. They now log a warning about the empty file
4027 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4029 o Major bugfixes (security, directory authority, denial-of-service):
4030 - Fix a bug that could have allowed an attacker to force a directory
4031 authority to use up all its RAM by passing it a maliciously
4032 crafted protocol versions string. Fixes bug 25517; bugfix on
4033 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4035 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
4036 - Avoid a rare assertion failure in the circuit build timeout code
4037 if we fail to allow any circuits to actually complete. Fixes bug
4038 25733; bugfix on 0.2.2.2-alpha.
4040 o Major bugfixes (netflow padding):
4041 - Stop adding unneeded channel padding right after we finish
4042 flushing to a connection that has been trying to flush for many
4043 seconds. Instead, treat all partial or complete flushes as
4044 activity on the channel, which will defer the time until we need
4045 to add padding. This fix should resolve confusing and scary log
4046 messages like "Channel padding timeout scheduled 221453ms in the
4047 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
4049 o Major bugfixes (networking):
4050 - Tor will no longer reject IPv6 address strings from Tor Browser
4051 when they are passed as hostnames in SOCKS5 requests. Fixes bug
4052 25036, bugfix on Tor 0.3.1.2.
4054 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
4055 - Correctly detect when onion services get disabled after HUP. Fixes
4056 bug 25761; bugfix on 0.3.2.1.
4058 o Major bugfixes (performance, load balancing):
4059 - Directory authorities no longer vote in favor of the Guard flag
4060 for relays without directory support. Starting in Tor
4061 0.3.0.1-alpha, clients have been avoiding using such relays in the
4062 Guard position, leading to increasingly broken load balancing for
4063 the 5%-or-so of Guards that don't advertise directory support.
4064 Fixes bug 22310; bugfix on 0.3.0.6.
4066 o Major bugfixes (relay):
4067 - If we have failed to connect to a relay and received a connection
4068 refused, timeout, or similar error (at the TCP level), do not try
4069 that same address/port again for 60 seconds after the failure has
4070 occurred. Fixes bug 24767; bugfix on 0.0.6.
4072 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
4073 - Impose a limit on circuit cell queue size. The limit can be
4074 controlled by a consensus parameter. Fixes bug 25226; bugfix
4077 o Minor features (cleanup):
4078 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
4079 when it stops. Closes ticket 23271.
4081 o Minor features (compatibility, backport from 0.3.4.1-alpha):
4082 - Avoid some compilation warnings with recent versions of LibreSSL.
4083 Closes ticket 26006.
4085 o Minor features (config options):
4086 - Change the way the default value for MaxMemInQueues is calculated.
4087 We now use 40% of the hardware RAM if the system has 8 GB RAM or
4088 more. Otherwise we use the former value of 75%. Closes
4091 o Minor features (continuous integration):
4092 - Update the Travis CI configuration to use the stable Rust channel,
4093 now that we have decided to require that. Closes ticket 25714.
4095 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
4096 - Our .travis.yml configuration now includes support for testing the
4097 results of "make distcheck". (It's not uncommon for "make check"
4098 to pass but "make distcheck" to fail.) Closes ticket 25814.
4099 - Our Travis CI configuration now integrates with the Coveralls
4100 coverage analysis tool. Closes ticket 25818.
4102 o Minor features (defensive programming):
4103 - Most of the functions in Tor that free objects have been replaced
4104 with macros that free the objects and set the corresponding
4105 pointers to NULL. This change should help prevent a large class of
4106 dangling pointer bugs. Closes ticket 24337.
4107 - Where possible, the tor_free() macro now only evaluates its input
4108 once. Part of ticket 24337.
4109 - Check that microdesc ed25519 ids are non-zero in
4110 node_get_ed25519_id() before returning them. Implements ticket
4111 24001, patch by "aruna1234".
4113 o Minor features (directory authority):
4114 - When directory authorities are unable to add signatures to a
4115 pending consensus, log the reason why. Closes ticket 24849.
4117 o Minor features (embedding):
4118 - Tor can now start with a preauthenticated control connection
4119 created by the process that launched it. This feature is meant for
4120 use by programs that want to launch and manage a Tor process
4121 without allowing other programs to manage it as well. For more
4122 information, see the __OwningControllerFD option documented in
4123 control-spec.txt. Closes ticket 23900.
4124 - On most errors that would cause Tor to exit, it now tries to
4125 return from the tor_main() function, rather than calling the
4126 system exit() function. Most users won't notice a difference here,
4127 but it should be significant for programs that run Tor inside a
4128 separate thread: they should now be able to survive Tor's exit
4129 conditions rather than having Tor shut down the entire process.
4130 Closes ticket 23848.
4131 - Applications that want to embed Tor can now tell Tor not to
4132 register any of its own POSIX signal handlers, using the
4133 __DisableSignalHandlers option. Closes ticket 24588.
4135 o Minor features (fallback directory list):
4136 - Avoid selecting fallbacks that change their IP addresses too
4137 often. Select more fallbacks by ignoring the Guard flag, and
4138 allowing lower cutoffs for the Running and V2Dir flags. Also allow
4139 a lower bandwidth, and a higher number of fallbacks per operator
4140 (5% of the list). Implements ticket 24785.
4141 - Update the fallback whitelist and blacklist based on opt-ins and
4142 relay changes. Closes tickets 22321, 24678, 22527, 24135,
4145 o Minor features (fallback directory mirror configuration):
4146 - Add a nickname to each fallback in a C comment. This makes it
4147 easier for operators to find their relays, and allows stem to use
4148 nicknames to identify fallbacks. Implements ticket 24600.
4149 - Add a type and version header to the fallback directory mirror
4150 file. Also add a delimiter to the end of each fallback entry. This
4151 helps external parsers like stem and Relay Search. Implements
4153 - Add an extrainfo cache flag for each fallback in a C comment. This
4154 allows stem to use fallbacks to fetch extra-info documents, rather
4155 than using authorities. Implements ticket 22759.
4156 - Add the generateFallbackDirLine.py script for automatically
4157 generating fallback directory mirror lines from relay fingerprints.
4158 No more typos! Add the lookupFallbackDirContact.py script for
4159 automatically looking up operator contact info from relay
4160 fingerprints. Implements ticket 24706, patch by teor and atagar.
4161 - Reject any fallback directory mirror that serves an expired
4162 consensus. Implements ticket 20942, patch by "minik".
4163 - Remove commas and equals signs from external string inputs to the
4164 fallback list. This avoids format confusion attacks. Implements
4166 - Remove the "weight=10" line from fallback directory mirror
4167 entries. Ticket 24681 will maintain the current fallback weights
4168 by changing Tor's default fallback weight to 10. Implements
4170 - Stop logging excessive information about fallback netblocks.
4171 Implements ticket 24791.
4173 o Minor features (forward-compatibility):
4174 - If a relay supports some link authentication protocol that we do
4175 not recognize, then include that relay's ed25519 key when telling
4176 other relays to extend to it. Previously, we treated future
4177 versions as if they were too old to support ed25519 link
4178 authentication. Closes ticket 20895.
4180 o Minor features (geoip):
4181 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4182 database. Closes ticket 26104.
4184 o Minor features (heartbeat):
4185 - Add onion service information to our heartbeat logs, displaying
4186 stats about the activity of configured onion services. Closes
4189 o Minor features (instrumentation, development):
4190 - Add the MainloopStats option to allow developers to get
4191 instrumentation information from the main event loop via the
4192 heartbeat messages. We hope to use this to improve Tor's behavior
4193 when it's trying to sleep. Closes ticket 24605.
4195 o Minor features (IPv6):
4196 - Make IPv6-only clients wait for microdescs for relays, even if we
4197 were previously using descriptors (or were using them as a bridge)
4198 and have a cached descriptor for them. Implements ticket 23827.
4199 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
4200 them, rather than waiting to download microdescriptors. Implements
4203 o Minor features (log messages):
4204 - Improve log message in the out-of-memory handler to include
4205 information about memory usage from the different compression
4206 backends. Closes ticket 25372.
4207 - Improve a warning message that happens when we fail to re-parse an
4208 old router because of an expired certificate. Closes ticket 20020.
4209 - Make the log more quantitative when we hit MaxMemInQueues
4210 threshold exposing some values. Closes ticket 24501.
4212 o Minor features (logging):
4213 - Clarify the log messages produced when getrandom() or a related
4214 entropy-generation mechanism gives an error. Closes ticket 25120.
4215 - Added support for the Android logging subsystem. Closes
4218 o Minor features (performance):
4219 - Support predictive circuit building for onion service circuits
4220 with multiple layers of guards. Closes ticket 23101.
4221 - Use stdatomic.h where available, rather than mutexes, to implement
4222 atomic_counter_t. Closes ticket 23953.
4224 o Minor features (performance, 32-bit):
4225 - Improve performance on 32-bit systems by avoiding 64-bit division
4226 when calculating the timestamp in milliseconds for channel padding
4227 computations. Implements ticket 24613.
4228 - Improve performance on 32-bit systems by avoiding 64-bit division
4229 when timestamping cells and buffer chunks for OOM calculations.
4230 Implements ticket 24374.
4232 o Minor features (performance, OSX, iOS):
4233 - Use the mach_approximate_time() function (when available) to
4234 implement coarse monotonic time. Having a coarse time function
4235 should avoid a large number of system calls, and improve
4236 performance slightly, especially under load. Closes ticket 24427.
4238 o Minor features (performance, windows):
4239 - Improve performance on Windows Vista and Windows 7 by adjusting
4240 TCP send window size according to the recommendation from
4241 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
4244 o Minor features (sandbox):
4245 - Explicitly permit the poll() system call when the Linux
4246 seccomp2-based sandbox is enabled: apparently, some versions of
4247 libc use poll() when calling getpwnam(). Closes ticket 25313.
4249 o Minor features (storage, configuration):
4250 - Users can store cached directory documents somewhere other than
4251 the DataDirectory by using the CacheDirectory option. Similarly,
4252 the storage location for relay's keys can be overridden with the
4253 KeyDirectory option. Closes ticket 22703.
4255 o Minor features (testing):
4256 - Add a "make test-rust" target to run the rust tests only. Closes
4259 o Minor features (testing, debugging, embedding):
4260 - For development purposes, Tor now has a mode in which it runs for
4261 a few seconds, then stops, and starts again without exiting the
4262 process. This mode is meant to help us debug various issues with
4263 ticket 23847. To use this feature, compile with
4264 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
4265 environment variable. This is expected to crash a lot, and is
4266 really meant for developers only. It will likely be removed in a
4267 future release. Implements ticket 24583.
4269 o Minor bugfixes (build, rust):
4270 - Fix output of autoconf checks to display success messages for Rust
4271 dependencies and a suitable rustc compiler version. Fixes bug
4272 24612; bugfix on 0.3.1.3-alpha.
4273 - Don't pass the --quiet option to cargo: it seems to suppress some
4274 errors, which is not what we want to do when building. Fixes bug
4275 24518; bugfix on 0.3.1.7.
4276 - Build correctly when building from outside Tor's source tree with
4277 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
4280 o Minor bugfixes (C correctness):
4281 - Fix a very unlikely (impossible, we believe) null pointer
4282 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
4283 Coverity; this is CID 1430932.
4285 o Minor bugfixes (channel, client):
4286 - Better identify client connection when reporting to the geoip
4287 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
4289 o Minor bugfixes (circuit, cannibalization):
4290 - Don't cannibalize preemptively-built circuits if we no longer
4291 recognize their first hop. This situation can happen if our Guard
4292 relay went off the consensus after the circuit was created. Fixes
4293 bug 24469; bugfix on 0.0.6.
4295 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
4296 - Don't consider Tor running as a client if the ControlPort is open,
4297 but no actual client ports are open. Fixes bug 26062; bugfix
4300 o Minor bugfixes (compilation):
4301 - Fix a C99 compliance issue in our configuration script that caused
4302 compilation issues when compiling Tor with certain versions of
4303 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
4305 o Minor bugfixes (controller):
4306 - Restore the correct operation of the RESOLVE command, which had
4307 been broken since we added the ability to enable/disable DNS on
4308 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
4309 - Avoid a (nonfatal) assertion failure when extending a one-hop
4310 circuit from the controller to become a multihop circuit. Fixes
4311 bug 24903; bugfix on 0.2.5.2-alpha.
4313 o Minor bugfixes (correctness):
4314 - Remove a nonworking, unnecessary check to see whether a circuit
4315 hop's identity digest was set when the circuit failed. Fixes bug
4316 24927; bugfix on 0.2.4.4-alpha.
4318 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
4319 - Upon receiving a malformed connected cell, stop processing the
4320 cell immediately. Previously we would mark the connection for
4321 close, but continue processing the cell as if the connection were
4322 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
4324 o Minor bugfixes (directory authorities, IPv6):
4325 - When creating a routerstatus (vote) from a routerinfo (descriptor),
4326 set the IPv6 address to the unspecified IPv6 address, and
4327 explicitly initialize the port to zero. Fixes bug 24488; bugfix
4330 o Minor bugfixes (documentation):
4331 - Document that the PerConnBW{Rate,Burst} options will fall back to
4332 their corresponding consensus parameters only if those parameters
4333 are set. Previously we had claimed that these values would always
4334 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
4336 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
4337 - Stop saying in the manual that clients cache ipv4 dns answers from
4338 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4339 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4340 we forgot to say so in the man page. Fixes bug 26052; bugfix
4343 o Minor bugfixes (exit relay DNS retries):
4344 - Re-attempt timed-out DNS queries 3 times before failure, since our
4345 timeout is 5 seconds for them, but clients wait 10-15. Also allow
4346 slightly more timeouts per resolver when an exit has multiple
4347 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
4349 o Minor bugfixes (fallback directory mirrors):
4350 - Make updateFallbackDirs.py search harder for python. (Some OSs
4351 don't put it in /usr/bin.) Fixes bug 24708; bugfix
4354 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
4355 - When hibernating, close connections normally and allow them to
4356 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
4358 - Do not attempt to launch self-reachability tests when entering
4359 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
4360 - Resolve several bugs related to descriptor fetching on bridge
4361 clients with bandwidth accounting enabled. (This combination is
4362 not recommended!) Fixes a case of bug 12062; bugfix
4364 - When hibernating, do not attempt to launch DNS checks. Fixes a
4365 case of bug 12062; bugfix on 0.1.2.2-alpha.
4366 - When hibernating, do not try to upload or download descriptors.
4367 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
4369 o Minor bugfixes (IPv6, bridges):
4370 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
4371 bugfix on 0.2.8.2-alpha.
4372 - Tor now sets IPv6 address in the routerstatus as well as in the
4373 router descriptors when updating addresses for a bridge. Closes
4374 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
4376 o Minor bugfixes (Linux seccomp2 sandbox):
4377 - When running with the sandbox enabled, reload configuration files
4378 correctly even when %include was used. Previously we would crash.
4379 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
4381 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
4382 - Allow the nanosleep() system call, which glibc uses to implement
4383 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4385 o Minor bugfixes (logging):
4386 - Fix a (mostly harmless) race condition when invoking
4387 LOG_PROTOCOL_WARN message from a subthread while the torrc options
4388 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
4390 o Minor bugfixes (man page, SocksPort):
4391 - Remove dead code from the old "SocksSocket" option, and rename
4392 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old
4393 option still works, but is deprecated. Fixes bug 24343; bugfix
4396 o Minor bugfixes (memory leaks):
4397 - Avoid possible at-exit memory leaks related to use of Libevent's
4398 event_base_once() function. (This function tends to leak memory if
4399 the event_base is closed before the event fires.) Fixes bug 24584;
4400 bugfix on 0.2.8.1-alpha.
4401 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
4404 o Minor bugfixes (network IPv6 test):
4405 - Tor's test scripts now check if "ping -6 ::1" works when the user
4406 runs "make test-network-all". Fixes bug 24677; bugfix on
4407 0.2.9.3-alpha. Patch by "ffmancera".
4409 o Minor bugfixes (networking):
4410 - string_is_valid_hostname() will not consider IP strings to be
4411 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
4413 o Minor bugfixes (onion service v3):
4414 - Avoid an assertion failure when the next onion service descriptor
4415 rotation type is out of sync with the consensus's valid-after
4416 time. Instead, log a warning message with extra information, so we
4417 can better hunt down the cause of this assertion. Fixes bug 25306;
4418 bugfix on 0.3.2.1-alpha.
4420 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
4421 - Fix a memory leak when a v3 onion service is configured and gets a
4422 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4423 - When parsing the descriptor signature, look for the token plus an
4424 extra white-space at the end. This is more correct but also will
4425 allow us to support new fields that might start with "signature".
4426 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4428 o Minor bugfixes (onion services):
4429 - If we are configured to offer a single onion service, don't log
4430 long-term established one hop rendezvous points in the heartbeat.
4431 Fixes bug 25116; bugfix on 0.2.9.6-rc.
4433 o Minor bugfixes (performance):
4434 - Reduce the number of circuits that will be opened at once during
4435 the circuit build timeout phase. This is done by increasing the
4436 idle timeout to 3 minutes, and lowering the maximum number of
4437 concurrent learning circuits to 10. Fixes bug 24769; bugfix
4439 - Avoid calling protocol_list_supports_protocol() from inside tight
4440 loops when running with cached routerinfo_t objects. Instead,
4441 summarize the relevant protocols as flags in the routerinfo_t, as
4442 we do for routerstatus_t objects. This change simplifies our code
4443 a little, and saves a large amount of short-term memory allocation
4444 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
4446 o Minor bugfixes (performance, timeouts):
4447 - Consider circuits for timeout as soon as they complete a hop. This
4448 is more accurate than applying the timeout in
4449 circuit_expire_building() because that function is only called
4450 once per second, which is now too slow for typical timeouts on the
4451 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
4452 - Use onion service circuits (and other circuits longer than 3 hops)
4453 to calculate a circuit build timeout. Previously, Tor only
4454 calculated its build timeout based on circuits that planned to be
4455 exactly 3 hops long. With this change, we include measurements
4456 from all circuits at the point where they complete their third
4457 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
4459 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
4460 - Avoid a crash when running with DirPort set but ORPort turned off.
4461 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4463 o Minor bugfixes (Rust FFI):
4464 - Fix a minor memory leak which would happen whenever the C code
4465 would call the Rust implementation of
4466 protover_get_supported_protocols(). This was due to the C version
4467 returning a static string, whereas the Rust version newly allocated
4468 a CString to pass across the FFI boundary. Consequently, the C
4469 code was not expecting to need to free() what it was given. Fixes
4470 bug 25127; bugfix on 0.3.2.1-alpha.
4472 o Minor bugfixes (spelling):
4473 - Use the "misspell" tool to detect and fix typos throughout the
4474 source code. Fixes bug 23650; bugfix on various versions of Tor.
4475 Patch from Deepesh Pathak.
4477 o Minor bugfixes (testing):
4478 - Avoid intermittent test failures due to a test that had relied on
4479 onion service introduction point creation finishing within 5
4480 seconds of real clock time. Fixes bug 25450; bugfix
4482 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
4483 bugfix on 0.2.3.1-alpha.
4485 o Minor bugfixes (unit test, monotonic time):
4486 - Increase a constant (1msec to 10msec) in the monotonic time test
4487 that makes sure the nsec/usec/msec times read are synchronized.
4488 This change was needed to accommodate slow systems like armel or
4489 when the clock_gettime() is not a VDSO on the running kernel.
4490 Fixes bug 25113; bugfix on 0.2.9.1.
4492 o Code simplification and refactoring:
4493 - Move the list of default directory authorities to its own file.
4494 Closes ticket 24854. Patch by "beastr0".
4495 - Remove the old (deterministic) directory retry logic entirely:
4496 We've used exponential backoff exclusively for some time. Closes
4498 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
4500 - Remove a series of counters used to track circuit extend attempts
4501 and connection status but that in reality we aren't using for
4502 anything other than stats logged by a SIGUSR1 signal. Closes
4504 - Remove /usr/athena from search path in configure.ac. Closes
4506 - Remove duplicate code in node_has_curve25519_onion_key() and
4507 node_get_curve25519_onion_key(), and add a check for a zero
4508 microdesc curve25519 onion key. Closes ticket 23966, patch by
4509 "aruna1234" and teor.
4510 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
4511 memory allocations with large numbers of OR connections (e.g.
4512 relays). Closes ticket 24119.
4513 - Separate the function that deletes ephemeral files when Tor
4515 - Small changes to Tor's buf_t API to make it suitable for use as a
4516 general-purpose safe string constructor. Closes ticket 22342.
4517 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
4518 avoid source code identifier confusion. Closes ticket 24467.
4519 - The tor_git_revision[] constant no longer needs to be redeclared
4520 by everything that links against the rest of Tor. Done as part of
4521 ticket 23845, to simplify our external API.
4522 - We make extend_info_from_node() use node_get_curve25519_onion_key()
4523 introduced in ticket 23577 to access the curve25519 public keys
4524 rather than accessing it directly. Closes ticket 23760. Patch by
4526 - Add a function to log channels' scheduler state changes to aid
4527 debugging efforts. Closes ticket 24531.
4530 - Improved the documentation of AccountingStart parameter. Closes
4532 - Update the documentation for "Log" to include the current list of
4533 logging domains. Closes ticket 25378.
4534 - Add documentation on how to build tor with Rust dependencies
4535 without having to be online. Closes ticket 22907; bugfix
4537 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
4538 traffic. Closes ticket 24318.
4539 - Document that OutboundBindAddress doesn't apply to DNS requests.
4540 Closes ticket 22145. Patch from Aruna Maurya.
4542 o Code simplification and refactoring (channels):
4543 - Remove the incoming and outgoing channel queues. These were never
4544 used, but still took up a step in our fast path.
4545 - The majority of the channel unit tests have been rewritten and the
4546 code coverage has now been raised to 83.6% for channel.c. Closes
4548 - Remove other dead code from the channel subsystem: All together,
4549 this cleanup has removed more than 1500 lines of code overall and
4550 adding very little except for unit test.
4552 o Code simplification and refactoring (circuit rendezvous):
4553 - Split the client-side rendezvous circuit lookup into two
4554 functions: one that returns only established circuits and another
4555 that returns all kinds of circuits. Closes ticket 23459.
4557 o Code simplification and refactoring (controller):
4558 - Make most of the variables in networkstatus_getinfo_by_purpose()
4559 const. Implements ticket 24489.
4561 o Documentation (backport from 0.3.4.1-alpha):
4562 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4563 ticket 25857. Patch from "CTassisF".
4565 o Documentation (man page):
4566 - The HiddenServiceVersion torrc option accepts only one number:
4567 either version 2 or 3. Closes ticket 25026; bugfix
4570 o Documentation (manpage, denial of service):
4571 - Provide more detail about the denial-of-service options, by
4572 listing each mitigation and explaining how they relate. Closes
4576 Changes in version 0.3.1.10 - 2018-03-03
4577 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
4580 It includes an important security fix for a remote crash attack
4581 against directory authorities, tracked as TROVE-2018-001.
4583 This release also backports our new system for improved resistance to
4584 denial-of-service attacks against relays.
4586 This release also fixes several minor bugs and annoyances from
4589 All directory authorities should upgrade to one of the versions
4590 released today. Relays running 0.3.1.x may wish to update to one of
4591 the versions released today, for the DoS mitigations.
4593 Please note: according to our release calendar, Tor 0.3.1 will no
4594 longer be supported after 1 July 2018. If you will be running Tor
4595 after that date, you should make sure to plan to upgrade to the latest
4596 stable version, or downgrade to 0.2.9 (which will receive long-term
4599 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4600 - Fix a protocol-list handling bug that could be used to remotely crash
4601 directory authorities with a null-pointer exception. Fixes bug 25074;
4602 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4605 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4606 - Give relays some defenses against the recent network overload. We
4607 start with three defenses (default parameters in parentheses).
4608 First: if a single client address makes too many concurrent
4609 connections (>100), hang up on further connections. Second: if a
4610 single client address makes circuits too quickly (more than 3 per
4611 second, with an allowed burst of 90) while also having too many
4612 connections open (3), refuse new create cells for the next while
4613 (1-2 hours). Third: if a client asks to establish a rendezvous
4614 point to you directly, ignore the request. These defenses can be
4615 manually controlled by new torrc options, but relays will also
4616 take guidance from consensus parameters, so there's no need to
4617 configure anything manually. Implements ticket 24902.
4619 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4620 - Update the sandbox rules so that they should now work correctly
4621 with Glibc 2.26. Closes ticket 24315.
4623 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4624 - Fix an "off by 2" error in counting rendezvous failures on the
4625 onion service side. While we thought we would stop the rendezvous
4626 attempt after one failed circuit, we were actually making three
4627 circuit attempts before giving up. Now switch to a default of 2,
4628 and allow the consensus parameter "hs_service_max_rdv_failures" to
4629 override. Fixes bug 24895; bugfix on 0.0.6.
4631 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4632 - Add Link protocol version 5 to the supported protocols list. Fixes
4633 bug 25070; bugfix on 0.3.1.1-alpha.
4635 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4636 - Fix a set of false positives where relays would consider
4637 connections to other relays as being client-only connections (and
4638 thus e.g. deserving different link padding schemes) if those
4639 relays fell out of the consensus briefly. Now we look only at the
4640 initial handshake and whether the connection authenticated as a
4641 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4643 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
4644 - Make our OOM handler aware of the geoip client history cache so it
4645 doesn't fill up the memory. This check is important for IPv6 and
4646 our DoS mitigation subsystem. Closes ticket 25122.
4648 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
4649 - Change relay bandwidth reporting stats interval from 4 hours to 24
4650 hours in order to reduce the efficiency of guard discovery
4651 attacks. Fixes ticket 23856.
4653 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4654 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4655 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4656 since they neither disabled TLS 1.3 nor enabled any of the
4657 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4658 Closes ticket 24978.
4660 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
4661 - The fallback directory list has been re-generated based on the
4662 current status of the network. Tor uses fallback directories to
4663 bootstrap when it doesn't yet have up-to-date directory
4664 information. Closes ticket 24801.
4665 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4666 prefer to bootstrap from fallback directory mirrors. This is a
4667 follow-up to 24679, which removed weights from the default
4668 fallbacks. Implements ticket 24681.
4670 o Minor features (geoip):
4671 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4674 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4675 - Use the actual observed address of an incoming relay connection,
4676 not the canonical address of the relay from its descriptor, when
4677 making decisions about how to handle the incoming connection.
4678 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4680 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4681 - Directory authorities, when refusing a descriptor from a rejected
4682 relay, now explicitly tell the relay (in its logs) to set a valid
4683 ContactInfo address and contact the bad-relays@ mailing list.
4684 Fixes bug 25170; bugfix on 0.2.9.1.
4686 o Minor bugfixes (address selection, backport from 0.3.2.9):
4687 - When the fascist_firewall_choose_address_ functions don't find a
4688 reachable address, set the returned address to the null address
4689 and port. This is a precautionary measure, because some callers do
4690 not check the return value. Fixes bug 24736; bugfix
4693 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
4694 - Fetch descriptors aggressively whenever we lack enough to build
4695 circuits, regardless of how many descriptors we are missing.
4696 Previously, we would delay launching the fetch when we had fewer
4697 than 15 missing descriptors, even if some of those descriptors
4698 were blocking circuits from building. Fixes bug 23985; bugfix on
4699 0.1.1.11-alpha. The effects of this bug became worse in
4700 0.3.0.3-alpha, when we began treating missing descriptors from our
4701 primary guards as a reason to delay circuits.
4702 - Don't try fetching microdescriptors from relays that have failed
4703 to deliver them in the past. Fixes bug 23817; bugfix
4706 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
4707 - Fix a signed/unsigned comparison warning introduced by our fix to
4708 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4710 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4711 - Avoid a crash when attempting to use the seccomp2 sandbox together
4712 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4715 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4716 - Fix a possible crash on malformed consensus. If a consensus had
4717 contained an unparseable protocol line, it could have made clients
4718 and relays crash with a null-pointer exception. To exploit this
4719 issue, however, an attacker would need to be able to subvert the
4720 directory authority system. Fixes bug 25251; bugfix on
4721 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4723 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
4724 - Recover better from empty or corrupt files in the consensus cache
4725 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4726 - When a consensus diff calculation is only partially successful,
4727 only record the successful parts as having succeeded. Partial
4728 success can happen if (for example) one compression method fails
4729 but the others succeed. Previously we misrecorded all the
4730 calculations as having succeeded, which would later cause a
4731 nonfatal assertion failure. Fixes bug 24086; bugfix
4734 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
4735 - Tor now updates its guard state when it reads a consensus
4736 regardless of whether it's missing descriptors. That makes tor use
4737 its primary guards to fetch descriptors in some edge cases where
4738 it would previously have used fallback directories. Fixes bug
4739 23862; bugfix on 0.3.0.1-alpha.
4741 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4742 - Don't treat inability to store a cached consensus object as a bug:
4743 it can happen normally when we are out of disk space. Fixes bug
4744 24859; bugfix on 0.3.1.1-alpha.
4746 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
4747 - When queuing DESTROY cells on a channel, only queue the circuit-id
4748 and reason fields: not the entire 514-byte cell. This fix should
4749 help mitigate any bugs or attacks that fill up these queues, and
4750 free more RAM for other uses. Fixes bug 24666; bugfix
4753 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
4754 - When closing a connection via close_connection_immediately(), we
4755 mark it as "not blocked on bandwidth", to prevent later calls from
4756 trying to unblock it, and give it permission to read. This fixes a
4757 backtrace warning that can happen on relays under various
4758 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4760 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
4761 - When selecting relays by bandwidth, avoid a rounding error that
4762 could sometimes cause load to be imbalanced incorrectly.
4763 Previously, we would always round upwards; now, we round towards
4764 the nearest integer. This had the biggest effect when a relay's
4765 weight adjustments should have given it weight 0, but it got
4766 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4767 - When calculating the fraction of nodes that have descriptors, and
4768 all nodes in the network have zero bandwidths, count the number of
4769 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4770 - Actually log the total bandwidth in compute_weighted_bandwidths().
4771 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4773 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4774 - Improve the performance of our consensus-diff application code
4775 when Tor is built with the --enable-fragile-hardening option set.
4776 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4778 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4779 - Don't exit the Tor process if setrlimit() fails to change the file
4780 limit (which can happen sometimes on some versions of OSX). Fixes
4781 bug 21074; bugfix on 0.0.9pre5.
4783 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
4784 - Fix a bug in the bit-counting parts of our timing-wheel code on
4785 MSVC. (Note that MSVC is still not a supported build platform, due
4786 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
4789 o Minor bugfixes (relay, partial backport):
4790 - Make the internal channel_is_client() function look at what sort
4791 of connection handshake the other side used, rather than whether
4792 the other side ever sent a create_fast cell to us. Backports part
4793 of the fixes from bugs 22805 and 24898.
4795 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4796 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4798 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4799 bugfix on 0.2.9.4-alpha.
4801 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4802 - Update the "rust dependencies" submodule to be a project-level
4803 repository, rather than a user repository. Closes ticket 25323.
4806 Changes in version 0.2.9.15 - 2018-03-03
4807 Tor 0.2.9.15 backports important security and stability bugfixes from
4810 It includes an important security fix for a remote crash attack
4811 against directory authorities, tracked as TROVE-2018-001.
4813 This release also backports our new system for improved resistance to
4814 denial-of-service attacks against relays.
4816 This release also fixes several minor bugs and annoyances from
4819 All directory authorities should upgrade to one of the versions
4820 released today. Relays running 0.2.9.x may wish to update to one of
4821 the versions released today, for the DoS mitigations.
4823 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4824 - Fix a protocol-list handling bug that could be used to remotely crash
4825 directory authorities with a null-pointer exception. Fixes bug 25074;
4826 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4829 o Major features (denial-of-service mitigation):
4830 - Give relays some defenses against the recent network overload. We
4831 start with three defenses (default parameters in parentheses).
4832 First: if a single client address makes too many concurrent
4833 connections (>100), hang up on further connections. Second: if a
4834 single client address makes circuits too quickly (more than 3 per
4835 second, with an allowed burst of 90) while also having too many
4836 connections open (3), refuse new create cells for the next while
4837 (1-2 hours). Third: if a client asks to establish a rendezvous
4838 point to you directly, ignore the request. These defenses can be
4839 manually controlled by new torrc options, but relays will also
4840 take guidance from consensus parameters, so there's no need to
4841 configure anything manually. Implements ticket 24902.
4843 o Major bugfixes (bootstrapping):
4844 - Fetch descriptors aggressively whenever we lack enough to build
4845 circuits, regardless of how many descriptors we are missing.
4846 Previously, we would delay launching the fetch when we had fewer
4847 than 15 missing descriptors, even if some of those descriptors
4848 were blocking circuits from building. Fixes bug 23985; bugfix on
4849 0.1.1.11-alpha. The effects of this bug became worse in
4850 0.3.0.3-alpha, when we began treating missing descriptors from our
4851 primary guards as a reason to delay circuits.
4853 o Major bugfixes (onion services, retry behavior):
4854 - Fix an "off by 2" error in counting rendezvous failures on the
4855 onion service side. While we thought we would stop the rendezvous
4856 attempt after one failed circuit, we were actually making three
4857 circuit attempts before giving up. Now switch to a default of 2,
4858 and allow the consensus parameter "hs_service_max_rdv_failures" to
4859 override. Fixes bug 24895; bugfix on 0.0.6.
4861 o Minor feature (relay statistics):
4862 - Change relay bandwidth reporting stats interval from 4 hours to 24
4863 hours in order to reduce the efficiency of guard discovery
4864 attacks. Fixes ticket 23856.
4866 o Minor features (compatibility, OpenSSL):
4867 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4868 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4869 since they neither disabled TLS 1.3 nor enabled any of the
4870 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4871 Closes ticket 24978.
4873 o Minor features (denial-of-service avoidance):
4874 - Make our OOM handler aware of the geoip client history cache so it
4875 doesn't fill up the memory. This check is important for IPv6 and
4876 our DoS mitigation subsystem. Closes ticket 25122.
4878 o Minor features (fallback directory mirrors):
4879 - The fallback directory list has been re-generated based on the
4880 current status of the network. Tor uses fallback directories to
4881 bootstrap when it doesn't yet have up-to-date directory
4882 information. Closes ticket 24801.
4883 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4884 prefer to bootstrap from fallback directory mirrors. This is a
4885 follow-up to 24679, which removed weights from the default
4886 fallbacks. Implements ticket 24681.
4888 o Minor features (geoip):
4889 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4892 o Minor features (linux seccomp2 sandbox):
4893 - Update the sandbox rules so that they should now work correctly
4894 with Glibc 2.26. Closes ticket 24315.
4896 o Minor bugfix (channel connection):
4897 - Use the actual observed address of an incoming relay connection,
4898 not the canonical address of the relay from its descriptor, when
4899 making decisions about how to handle the incoming connection.
4900 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4902 o Minor bugfix (directory authority):
4903 - Directory authorities, when refusing a descriptor from a rejected
4904 relay, now explicitly tell the relay (in its logs) to set a valid
4905 ContactInfo address and contact the bad-relays@ mailing list.
4906 Fixes bug 25170; bugfix on 0.2.9.1.
4908 o Minor bugfixes (address selection):
4909 - When the fascist_firewall_choose_address_ functions don't find a
4910 reachable address, set the returned address to the null address
4911 and port. This is a precautionary measure, because some callers do
4912 not check the return value. Fixes bug 24736; bugfix
4915 o Minor bugfixes (compilation):
4916 - Fix a signed/unsigned comparison warning introduced by our fix to
4917 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4919 o Minor bugfixes (control port, linux seccomp2 sandbox):
4920 - Avoid a crash when attempting to use the seccomp2 sandbox together
4921 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4924 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4925 - Fix a possible crash on malformed consensus. If a consensus had
4926 contained an unparseable protocol line, it could have made clients
4927 and relays crash with a null-pointer exception. To exploit this
4928 issue, however, an attacker would need to be able to subvert the
4929 directory authority system. Fixes bug 25251; bugfix on
4930 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4932 o Minor bugfixes (memory usage):
4933 - When queuing DESTROY cells on a channel, only queue the circuit-id
4934 and reason fields: not the entire 514-byte cell. This fix should
4935 help mitigate any bugs or attacks that fill up these queues, and
4936 free more RAM for other uses. Fixes bug 24666; bugfix
4939 o Minor bugfixes (network layer):
4940 - When closing a connection via close_connection_immediately(), we
4941 mark it as "not blocked on bandwidth", to prevent later calls from
4942 trying to unblock it, and give it permission to read. This fixes a
4943 backtrace warning that can happen on relays under various
4944 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4946 o Minor bugfixes (OSX):
4947 - Don't exit the Tor process if setrlimit() fails to change the file
4948 limit (which can happen sometimes on some versions of OSX). Fixes
4949 bug 21074; bugfix on 0.0.9pre5.
4951 o Minor bugfixes (path selection):
4952 - When selecting relays by bandwidth, avoid a rounding error that
4953 could sometimes cause load to be imbalanced incorrectly.
4954 Previously, we would always round upwards; now, we round towards
4955 the nearest integer. This had the biggest effect when a relay's
4956 weight adjustments should have given it weight 0, but it got
4957 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4958 - When calculating the fraction of nodes that have descriptors, and
4959 all nodes in the network have zero bandwidths, count the number of
4960 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4961 - Actually log the total bandwidth in compute_weighted_bandwidths().
4962 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4964 o Minor bugfixes (portability, msvc):
4965 - Fix a bug in the bit-counting parts of our timing-wheel code on
4966 MSVC. (Note that MSVC is still not a supported build platform, due
4967 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
4970 o Minor bugfixes (relay):
4971 - Make the internal channel_is_client() function look at what sort
4972 of connection handshake the other side used, rather than whether
4973 the other side ever sent a create_fast cell to us. Backports part
4974 of the fixes from bugs 22805 and 24898.
4976 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4977 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4979 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4980 bugfix on 0.2.9.4-alpha.
4983 Changes in version 0.3.2.10 - 2018-03-03
4984 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
4985 backports a number of bugfixes, including important fixes for security
4988 It includes an important security fix for a remote crash attack
4989 against directory authorities, tracked as TROVE-2018-001.
4991 Additionally, it backports a fix for a bug whose severity we have
4992 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
4993 triggered in order to crash relays with a use-after-free pattern. As
4994 such, we are now tracking that bug as TROVE-2018-002 and
4995 CVE-2018-0491, and backporting it to earlier releases. This bug
4996 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
4999 This release also backports our new system for improved resistance to
5000 denial-of-service attacks against relays.
5002 This release also fixes several minor bugs and annoyances from
5005 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
5006 today, for the fix to TROVE-2018-002. Directory authorities should
5007 also upgrade. (Relays on earlier versions might want to update too for
5008 the DoS mitigations.)
5010 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5011 - Fix a protocol-list handling bug that could be used to remotely crash
5012 directory authorities with a null-pointer exception. Fixes bug 25074;
5013 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5016 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
5017 - Avoid adding the same channel twice in the KIST scheduler pending
5018 list, which could lead to remote denial-of-service use-after-free
5019 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
5021 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
5022 - Give relays some defenses against the recent network overload. We
5023 start with three defenses (default parameters in parentheses).
5024 First: if a single client address makes too many concurrent
5025 connections (>100), hang up on further connections. Second: if a
5026 single client address makes circuits too quickly (more than 3 per
5027 second, with an allowed burst of 90) while also having too many
5028 connections open (3), refuse new create cells for the next while
5029 (1-2 hours). Third: if a client asks to establish a rendezvous
5030 point to you directly, ignore the request. These defenses can be
5031 manually controlled by new torrc options, but relays will also
5032 take guidance from consensus parameters, so there's no need to
5033 configure anything manually. Implements ticket 24902.
5035 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
5036 - Fix an "off by 2" error in counting rendezvous failures on the
5037 onion service side. While we thought we would stop the rendezvous
5038 attempt after one failed circuit, we were actually making three
5039 circuit attempts before giving up. Now switch to a default of 2,
5040 and allow the consensus parameter "hs_service_max_rdv_failures" to
5041 override. Fixes bug 24895; bugfix on 0.0.6.
5042 - New-style (v3) onion services now obey the "max rendezvous circuit
5043 attempts" logic. Previously they would make as many rendezvous
5044 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5045 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5047 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
5048 - Add Link protocol version 5 to the supported protocols list. Fixes
5049 bug 25070; bugfix on 0.3.1.1-alpha.
5051 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
5052 - Fix a set of false positives where relays would consider
5053 connections to other relays as being client-only connections (and
5054 thus e.g. deserving different link padding schemes) if those
5055 relays fell out of the consensus briefly. Now we look only at the
5056 initial handshake and whether the connection authenticated as a
5057 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5059 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
5060 - The scheduler subsystem was failing to promptly notice changes in
5061 consensus parameters, making it harder to switch schedulers
5062 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5064 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
5065 - Make our OOM handler aware of the geoip client history cache so it
5066 doesn't fill up the memory. This check is important for IPv6 and
5067 our DoS mitigation subsystem. Closes ticket 25122.
5069 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
5070 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5071 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5072 since they neither disabled TLS 1.3 nor enabled any of the
5073 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5074 Closes ticket 24978.
5076 o Minor features (geoip):
5077 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5080 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
5081 - When logging a failure to create an onion service's descriptor,
5082 also log what the problem with the descriptor was. Diagnostic
5085 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
5086 - Use the actual observed address of an incoming relay connection,
5087 not the canonical address of the relay from its descriptor, when
5088 making decisions about how to handle the incoming connection.
5089 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5091 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5092 - Fix a possible crash on malformed consensus. If a consensus had
5093 contained an unparseable protocol line, it could have made clients
5094 and relays crash with a null-pointer exception. To exploit this
5095 issue, however, an attacker would need to be able to subvert the
5096 directory authority system. Fixes bug 25251; bugfix on
5097 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5099 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
5100 - Directory authorities, when refusing a descriptor from a rejected
5101 relay, now explicitly tell the relay (in its logs) to set a valid
5102 ContactInfo address and contact the bad-relays@ mailing list.
5103 Fixes bug 25170; bugfix on 0.2.9.1.
5105 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
5106 - When building with Rust on OSX, link against libresolv, to work
5107 around the issue at https://github.com/rust-lang/rust/issues/46797.
5108 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5110 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
5111 - Remove a BUG() statement when a client fetches an onion descriptor
5112 that has a lower revision counter than the one in its cache. This
5113 can happen in normal circumstances due to HSDir desync. Fixes bug
5114 24976; bugfix on 0.3.2.1-alpha.
5116 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5117 - Don't treat inability to store a cached consensus object as a bug:
5118 it can happen normally when we are out of disk space. Fixes bug
5119 24859; bugfix on 0.3.1.1-alpha.
5121 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5122 - Improve the performance of our consensus-diff application code
5123 when Tor is built with the --enable-fragile-hardening option set.
5124 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5126 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5127 - Don't exit the Tor process if setrlimit() fails to change the file
5128 limit (which can happen sometimes on some versions of OSX). Fixes
5129 bug 21074; bugfix on 0.0.9pre5.
5131 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5132 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5134 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5135 bugfix on 0.2.9.4-alpha.
5137 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
5138 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5139 25005; bugfix on 0.3.2.7-rc.
5141 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
5142 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5143 version, when deciding whether a consensus entry can support the
5144 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5145 bugfix on 0.3.2.1-alpha.
5147 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5148 - Update the "rust dependencies" submodule to be a project-level
5149 repository, rather than a user repository. Closes ticket 25323.
5151 o Documentation (backport from 0.3.3.1-alpha)
5152 - Document that operators who run more than one relay or bridge are
5153 expected to set MyFamily and ContactInfo correctly. Closes
5157 Changes in version 0.3.2.9 - 2018-01-09
5158 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
5160 The 0.3.2 series includes our long-anticipated new onion service
5161 design, with numerous security features. (For more information, see
5162 our blog post at https://blog.torproject.org/fall-harvest.) We also
5163 have a new circuit scheduler algorithm for improved performance on
5164 relays everywhere (see https://blog.torproject.org/kist-and-tell),
5165 along with many smaller features and bugfixes.
5167 Per our stable release policy, we plan to support each stable release
5168 series for at least the next nine months, or for three months after
5169 the first stable release of the next series: whichever is longer. If
5170 you need a release with long-term support, we recommend that you stay
5171 with the 0.2.9 series.
5173 Below is a list of the changes since 0.3.1.7. For a list of all
5174 changes since 0.3.2.8-rc, see the ChangeLog file.
5176 o Directory authority changes:
5177 - Add "Bastet" as a ninth directory authority to the default list.
5178 Closes ticket 23910.
5179 - The directory authority "Longclaw" has changed its IP address.
5180 Closes ticket 23592.
5181 - Remove longclaw's IPv6 address, as it will soon change. Authority
5182 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
5183 3/8 directory authorities with IPv6 addresses, but there are also
5184 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
5185 - Add an IPv6 address for the "bastet" directory authority. Closes
5188 o Major features (next-generation onion services):
5189 - Tor now supports the next-generation onion services protocol for
5190 clients and services! As part of this release, the core of
5191 proposal 224 has been implemented and is available for
5192 experimentation and testing by our users. This newer version of
5193 onion services ("v3") features many improvements over the legacy
5196 a) Better crypto (replaced SHA1/DH/RSA1024
5197 with SHA3/ed25519/curve25519)
5199 b) Improved directory protocol, leaking much less information to
5202 c) Improved directory protocol, with smaller surface for
5205 d) Better onion address security against impersonation.
5207 e) More extensible introduction/rendezvous protocol.
5209 f) A cleaner and more modular codebase.
5211 You can identify a next-generation onion address by its length:
5212 they are 56 characters long, as in
5213 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
5215 In the future, we will release more options and features for v3
5216 onion services, but we first need a testing period, so that the
5217 current codebase matures and becomes more robust. Planned features
5218 include: offline keys, advanced client authorization, improved
5219 guard algorithms, and statistics. For full details, see
5222 Legacy ("v2") onion services will still work for the foreseeable
5223 future, and will remain the default until this new codebase gets
5224 tested and hardened. Service operators who want to experiment with
5225 the new system can use the 'HiddenServiceVersion 3' torrc
5226 directive along with the regular onion service configuration
5227 options. For more information, see our blog post at
5228 "https://blog.torproject.org/fall-harvest". Enjoy!
5230 o Major feature (scheduler, channel):
5231 - Tor now uses new schedulers to decide which circuits should
5232 deliver cells first, in order to improve congestion at relays. The
5233 first type is called "KIST" ("Kernel Informed Socket Transport"),
5234 and is only available on Linux-like systems: it uses feedback from
5235 the kernel to prevent the kernel's TCP buffers from growing too
5236 full. The second new scheduler type is called "KISTLite": it
5237 behaves the same as KIST, but runs on systems without kernel
5238 support for inspecting TCP implementation details. The old
5239 scheduler is still available, under the name "Vanilla". To change
5240 the default scheduler preference order, use the new "Schedulers"
5241 option. (The default preference order is "KIST,KISTLite,Vanilla".)
5243 Matt Traudt implemented KIST, based on research by Rob Jansen,
5244 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
5245 more information, see the design paper at
5246 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
5247 followup implementation paper at https://arxiv.org/abs/1709.01044.
5248 Closes ticket 12541. For more information, see our blog post at
5249 "https://blog.torproject.org/kist-and-tell".
5251 o Major bugfixes (security, general):
5252 - Fix a denial of service bug where an attacker could use a
5253 malformed directory object to cause a Tor instance to pause while
5254 OpenSSL would try to read a passphrase from the terminal. (Tor
5255 instances run without a terminal, which is the case for most Tor
5256 packages, are not impacted.) Fixes bug 24246; bugfix on every
5257 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5258 Found by OSS-Fuzz as testcase 6360145429790720.
5260 o Major bugfixes (security, directory authority):
5261 - Fix a denial of service issue where an attacker could crash a
5262 directory authority using a malformed router descriptor. Fixes bug
5263 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5266 o Major bugfixes (security, onion service v2):
5267 - Fix a use-after-free error that could crash v2 Tor onion services
5268 when they failed to open circuits while expiring introduction
5269 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5270 also tracked as TROVE-2017-013 and CVE-2017-8823.
5271 - When checking for replays in the INTRODUCE1 cell data for a
5272 (legacy) onion service, correctly detect replays in the RSA-
5273 encrypted part of the cell. We were previously checking for
5274 replays on the entire cell, but those can be circumvented due to
5275 the malleability of Tor's legacy hybrid encryption. This fix helps
5276 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5277 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5280 o Major bugfixes (security, relay):
5281 - When running as a relay, make sure that we never build a path
5282 through ourselves, even in the case where we have somehow lost the
5283 version of our descriptor appearing in the consensus. Fixes part
5284 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5285 as TROVE-2017-012 and CVE-2017-8822.
5286 - When running as a relay, make sure that we never choose ourselves
5287 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5288 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5290 o Major bugfixes (bootstrapping):
5291 - Fetch descriptors aggressively whenever we lack enough to build
5292 circuits, regardless of how many descriptors we are missing.
5293 Previously, we would delay launching the fetch when we had fewer
5294 than 15 missing descriptors, even if some of those descriptors
5295 were blocking circuits from building. Fixes bug 23985; bugfix on
5296 0.1.1.11-alpha. The effects of this bug became worse in
5297 0.3.0.3-alpha, when we began treating missing descriptors from our
5298 primary guards as a reason to delay circuits.
5299 - Don't try fetching microdescriptors from relays that have failed
5300 to deliver them in the past. Fixes bug 23817; bugfix
5303 o Major bugfixes (circuit prediction):
5304 - Fix circuit prediction logic so that a client doesn't treat a port
5305 as being "handled" by a circuit if that circuit already has
5306 isolation settings on it. This change should make Tor clients more
5307 responsive by improving their chances of having a pre-created
5308 circuit ready for use when a request arrives. Fixes bug 18859;
5309 bugfix on 0.2.3.3-alpha.
5311 o Major bugfixes (exit relays, DNS):
5312 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5313 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5314 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5315 identifying and finding a workaround to this bug and to Moritz,
5316 Arthur Edelstein, and Roger for helping to track it down and
5319 o Major bugfixes (relay, crash, assertion failure):
5320 - Fix a timing-based assertion failure that could occur when the
5321 circuit out-of-memory handler freed a connection's output buffer.
5322 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
5324 o Major bugfixes (usability, control port):
5325 - Report trusted clock skew indications as bootstrap errors, so
5326 controllers can more easily alert users when their clocks are
5327 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
5329 o Minor features (bridge):
5330 - Bridge relays can now set the BridgeDistribution config option to
5331 add a "bridge-distribution-request" line to their bridge
5332 descriptor, which tells BridgeDB how they'd like their bridge
5333 address to be given out. (Note that as of Oct 2017, BridgeDB does
5334 not yet implement this feature.) As a side benefit, this feature
5335 provides a way to distinguish bridge descriptors from non-bridge
5336 descriptors. Implements tickets 18329.
5337 - When handling the USERADDR command on an ExtOrPort, warn when the
5338 transports provides a USERADDR with no port. In a future version,
5339 USERADDR commands of this format may be rejected. Detects problems
5340 related to ticket 23080.
5342 o Minor features (bug detection):
5343 - Log a warning message with a stack trace for any attempt to call
5344 get_options() during option validation. This pattern has caused
5345 subtle bugs in the past. Closes ticket 22281.
5347 o Minor features (build, compilation):
5348 - The "check-changes" feature is now part of the "make check" tests;
5349 we'll use it to try to prevent misformed changes files from
5350 accumulating. Closes ticket 23564.
5351 - Tor builds should now fail if there are any mismatches between the
5352 C type representing a configuration variable and the C type the
5353 data-driven parser uses to store a value there. Previously, we
5354 needed to check these by hand, which sometimes led to mistakes.
5355 Closes ticket 23643.
5357 o Minor features (client):
5358 - You can now use Tor as a tunneled HTTP proxy: use the new
5359 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
5360 requests. Closes ticket 22407.
5361 - Add an extra check to make sure that we always use the newer guard
5362 selection code for picking our guards. Closes ticket 22779.
5363 - When downloading (micro)descriptors, don't split the list into
5364 multiple requests unless we want at least 32 descriptors.
5365 Previously, we split at 4, not 32, which led to significant
5366 overhead in HTTP request size and degradation in compression
5367 performance. Closes ticket 23220.
5368 - Improve log messages when missing descriptors for primary guards.
5369 Resolves ticket 23670.
5371 o Minor features (command line):
5372 - Add a new commandline option, --key-expiration, which prints when
5373 the current signing key is going to expire. Implements ticket
5374 17639; patch by Isis Lovecruft.
5376 o Minor features (control port):
5377 - If an application tries to use the control port as an HTTP proxy,
5378 respond with a meaningful "This is the Tor control port" message,
5379 and log the event. Closes ticket 1667. Patch from Ravi
5381 - Provide better error message for GETINFO desc/(id|name) when not
5382 fetching router descriptors. Closes ticket 5847. Patch by
5384 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
5385 whether Tor will try to download router descriptors and
5386 microdescriptors respectively. Closes ticket 22684.
5387 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
5388 so controllers can tell whether the geoip databases are loaded.
5389 Closes ticket 23237.
5390 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
5391 events. Closes ticket 19254. Patch by "DonnchaC".
5393 o Minor features (development support):
5394 - Developers can now generate a call-graph for Tor using the
5395 "calltool" python program, which post-processes object dumps. It
5396 should work okay on many Linux and OSX platforms, and might work
5397 elsewhere too. To run it, install calltool from
5398 https://gitweb.torproject.org/user/nickm/calltool.git and run
5399 "make callgraph". Closes ticket 19307.
5401 o Minor features (directory authority):
5402 - Make the "Exit" flag assignment only depend on whether the exit
5403 policy allows connections to ports 80 and 443. Previously relays
5404 would get the Exit flag if they allowed connections to one of
5405 these ports and also port 6667. Resolves ticket 23637.
5407 o Minor features (ed25519):
5408 - Add validation function to checks for torsion components in
5409 ed25519 public keys, used by prop224 client-side code. Closes
5410 ticket 22006. Math help by Ian Goldberg.
5412 o Minor features (exit relay, DNS):
5413 - Improve the clarity and safety of the log message from evdns when
5414 receiving an apparently spoofed DNS reply. Closes ticket 3056.
5416 o Minor features (fallback directory mirrors):
5417 - The fallback directory list has been re-generated based on the
5418 current status of the network. Tor uses fallback directories to
5419 bootstrap when it doesn't yet have up-to-date directory
5420 information. Closes ticket 24801.
5421 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5422 prefer to bootstrap from fallback directory mirrors. This is a
5423 follow-up to 24679, which removed weights from the default
5424 fallbacks. Implements ticket 24681.
5426 o Minor features (geoip):
5427 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
5430 o Minor features (integration, hardening):
5431 - Add a new NoExec option to prevent Tor from running other
5432 programs. When this option is set to 1, Tor will never try to run
5433 another program, regardless of the settings of
5434 PortForwardingHelper, ClientTransportPlugin, or
5435 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
5436 without restarting Tor. Closes ticket 22976.
5438 o Minor features (linux seccomp2 sandbox):
5439 - Update the sandbox rules so that they should now work correctly
5440 with Glibc 2.26. Closes ticket 24315.
5442 o Minor features (logging):
5443 - Provide better warnings when the getrandom() syscall fails. Closes
5445 - Downgrade a pair of log messages that could occur when an exit's
5446 resolver gave us an unusual (but not forbidden) response. Closes
5448 - Improve the message we log when re-enabling circuit build timeouts
5449 after having received a consensus. Closes ticket 20963.
5450 - Log more circuit information whenever we are about to try to
5451 package a relay cell on a circuit with a nonexistent n_chan.
5452 Attempt to diagnose ticket 8185.
5453 - Improve info-level log identification of particular circuits, to
5454 help with debugging. Closes ticket 23645.
5455 - Improve the warning message for specifying a relay by nickname.
5456 The previous message implied that nickname registration was still
5457 part of the Tor network design, which it isn't. Closes
5459 - If the sandbox filter fails to load, suggest to the user that
5460 their kernel might not support seccomp2. Closes ticket 23090.
5462 o Minor features (onion service, circuit, logging):
5463 - Improve logging of many callsite in the circuit subsystem to print
5464 the circuit identifier(s).
5465 - Log when we cleanup an intro point from a service so we know when
5466 and for what reason it happened. Closes ticket 23604.
5468 o Minor features (portability):
5469 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
5470 (It doesn't yet work with the sandbox enabled.) Closes
5472 - Check at configure time whether uint8_t is the same type as
5473 unsigned char. Lots of existing code already makes this
5474 assumption, and there could be strict aliasing issues if the
5475 assumption is violated. Closes ticket 22410.
5477 o Minor features (relay):
5478 - When choosing which circuits can be expired as unused, consider
5479 circuits from clients even if those clients used regular CREATE
5480 cells to make them; and do not consider circuits from relays even
5481 if they were made with CREATE_FAST. Part of ticket 22805.
5482 - Reject attempts to use relative file paths when RunAsDaemon is
5483 set. Previously, Tor would accept these, but the directory-
5484 changing step of RunAsDaemon would give strange and/or confusing
5485 results. Closes ticket 22731.
5487 o Minor features (relay statistics):
5488 - Change relay bandwidth reporting stats interval from 4 hours to 24
5489 hours in order to reduce the efficiency of guard discovery
5490 attacks. Fixes ticket 23856.
5492 o Minor features (reverted deprecations):
5493 - The ClientDNSRejectInternalAddresses flag can once again be set in
5494 non-testing Tor networks, so long as they do not use the default
5495 directory authorities. This change also removes the deprecation of
5496 this flag from 0.2.9.2-alpha. Closes ticket 21031.
5498 o Minor features (robustness):
5499 - Change several fatal assertions when flushing buffers into non-
5500 fatal assertions, to prevent any recurrence of 23690.
5502 o Minor features (startup, safety):
5503 - When configured to write a PID file, Tor now exits if it is unable
5504 to do so. Previously, it would warn and continue. Closes
5507 o Minor features (static analysis):
5508 - The BUG() macro has been changed slightly so that Coverity no
5509 longer complains about dead code if the bug is impossible. Closes
5512 o Minor features (testing):
5513 - Our fuzzing tests now test the encrypted portions of v3 onion
5514 service descriptors. Implements more of 21509.
5515 - Add a unit test to make sure that our own generated platform
5516 string will be accepted by directory authorities. Closes
5518 - The default chutney network tests now include tests for the v3
5519 onion service design. Make sure you have the latest version of
5520 chutney if you want to run these. Closes ticket 22437.
5521 - Add a unit test to verify that we can parse a hardcoded v2 onion
5522 service descriptor. Closes ticket 15554.
5524 o Minor bugfixes (address selection):
5525 - When the fascist_firewall_choose_address_ functions don't find a
5526 reachable address, set the returned address to the null address
5527 and port. This is a precautionary measure, because some callers do
5528 not check the return value. Fixes bug 24736; bugfix
5531 o Minor bugfixes (bootstrapping):
5532 - When warning about state file clock skew, report the correct
5533 direction for the detected skew. Fixes bug 23606; bugfix
5536 o Minor bugfixes (bridge clients, bootstrap):
5537 - Retry directory downloads when we get our first bridge descriptor
5538 during bootstrap or while reconnecting to the network. Keep
5539 retrying every time we get a bridge descriptor, until we have a
5540 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
5541 - Stop delaying bridge descriptor fetches when we have cached bridge
5542 descriptors. Instead, only delay bridge descriptor fetches when we
5543 have at least one reachable bridge. Fixes part of bug 24367;
5544 bugfix on 0.2.0.3-alpha.
5545 - Stop delaying directory fetches when we have cached bridge
5546 descriptors. Instead, only delay bridge descriptor fetches when
5547 all our bridges are definitely unreachable. Fixes part of bug
5548 24367; bugfix on 0.2.0.3-alpha.
5550 o Minor bugfixes (bridge):
5551 - Overwrite the bridge address earlier in the process of retrieving
5552 its descriptor, to make sure we reach it on the configured
5553 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
5555 o Minor bugfixes (build, compilation):
5556 - Fix a compilation warning when building with zstd support on
5557 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
5558 and fixed by Andreas Stieger.
5559 - When searching for OpenSSL, don't accept any OpenSSL library that
5560 lacks TLSv1_1_method(): Tor doesn't build with those versions.
5561 Additionally, look in /usr/local/opt/openssl, if it's present.
5562 These changes together repair the default build on OSX systems
5563 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
5564 - Fix a signed/unsigned comparison warning introduced by our fix to
5565 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5566 - Fix a memory leak warning in one of the libevent-related
5567 configuration tests that could occur when manually specifying
5568 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
5569 Found and patched by Alex Xu.
5570 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
5571 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5573 o Minor bugfixes (certificate handling):
5574 - Fix a time handling bug in Tor certificates set to expire after
5575 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
5576 Coverity as CID 1415728.
5578 o Minor bugfixes (client):
5579 - By default, do not enable storage of client-side DNS values. These
5580 values were unused by default previously, but they should not have
5581 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
5583 o Minor bugfixes (client, usability):
5584 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
5585 SOCKS4a requests that contain IP address strings, even when
5586 SafeSocks in enabled, as this prevents user from connecting to
5587 known IP addresses without relying on DNS for resolving. SafeSocks
5588 still rejects SOCKS connections that connect to IP addresses when
5589 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
5590 bugfix on Tor 0.2.6.2-alpha.
5592 o Minor bugfixes (code correctness):
5593 - Call htons() in extend_cell_format() for encoding a 16-bit value.
5594 Previously we used ntohs(), which happens to behave the same on
5595 all the platforms we support, but which isn't really correct.
5596 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
5597 - For defense-in-depth, make the controller's write_escaped_data()
5598 function robust to extremely long inputs. Fixes bug 19281; bugfix
5599 on 0.1.1.1-alpha. Reported by Guido Vranken.
5600 - Fix several places in our codebase where a C compiler would be
5601 likely to eliminate a check, based on assuming that undefined
5602 behavior had not happened elsewhere in the code. These cases are
5603 usually a sign of redundant checking or dubious arithmetic. Found
5604 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
5605 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
5608 o Minor bugfixes (compression):
5609 - Handle a pathological case when decompressing Zstandard data when
5610 the output buffer size is zero. Fixes bug 23551; bugfix
5613 o Minor bugfixes (consensus expiry):
5614 - Check for adequate directory information correctly. Previously, Tor
5615 would reconsider whether it had sufficient directory information
5616 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
5618 o Minor bugfixes (control port, linux seccomp2 sandbox):
5619 - Avoid a crash when attempting to use the seccomp2 sandbox together
5620 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5623 o Minor bugfixes (control port, onion services):
5624 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
5625 HS_DESC event when a service is not able to upload a descriptor.
5626 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
5628 o Minor bugfixes (directory cache):
5629 - Recover better from empty or corrupt files in the consensus cache
5630 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
5631 - When a consensus diff calculation is only partially successful,
5632 only record the successful parts as having succeeded. Partial
5633 success can happen if (for example) one compression method fails
5634 but the others succeed. Previously we misrecorded all the
5635 calculations as having succeeded, which would later cause a
5636 nonfatal assertion failure. Fixes bug 24086; bugfix
5639 o Minor bugfixes (directory client):
5640 - On failure to download directory information, delay retry attempts
5641 by a random amount based on the "decorrelated jitter" algorithm.
5642 Our previous delay algorithm tended to produce extra-long delays
5643 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
5645 o Minor bugfixes (directory protocol):
5646 - Directory servers now include a "Date:" http header for response
5647 codes other than 200. Clients starting with a skewed clock and a
5648 recent consensus were getting "304 Not modified" responses from
5649 directory authorities, so without the Date header, the client
5650 would never hear about a wrong clock. Fixes bug 23499; bugfix
5652 - Make clients wait for 6 seconds before trying to download a
5653 consensus from an authority. Fixes bug 17750; bugfix
5656 o Minor bugfixes (documentation):
5657 - Document better how to read gcov, and what our gcov postprocessing
5658 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
5659 - Fix manpage to not refer to the obsolete (and misspelled)
5660 UseEntryGuardsAsDirectoryGuards parameter in the description of
5661 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
5663 o Minor bugfixes (DoS-resistance):
5664 - If future code asks if there are any running bridges, without
5665 checking if bridges are enabled, log a BUG warning rather than
5666 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
5668 o Minor bugfixes (entry guards):
5669 - Tor now updates its guard state when it reads a consensus
5670 regardless of whether it's missing descriptors. That makes tor use
5671 its primary guards to fetch descriptors in some edge cases where
5672 it would previously have used fallback directories. Fixes bug
5673 23862; bugfix on 0.3.0.1-alpha.
5675 o Minor bugfixes (format strictness):
5676 - Restrict several data formats to decimal. Previously, the
5677 BuildTimeHistogram entries in the state file, the "bw=" entries in
5678 the bandwidth authority file, and the process IDs passed to the
5679 __OwningControllerProcess option could all be specified in hex or
5680 octal as well as in decimal. This was not an intentional feature.
5681 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
5684 o Minor bugfixes (heartbeat):
5685 - If we fail to write a heartbeat message, schedule a retry for the
5686 minimum heartbeat interval number of seconds in the future. Fixes
5687 bug 19476; bugfix on 0.2.3.1-alpha.
5689 o Minor bugfixes (logging):
5690 - Suppress a log notice when relay descriptors arrive. We already
5691 have a bootstrap progress for this so no need to log notice
5692 everytime tor receives relay descriptors. Microdescriptors behave
5693 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
5694 - Remove duplicate log messages regarding opening non-local
5695 SocksPorts upon parsing config and opening listeners at startup.
5696 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
5697 - Use a more comprehensible log message when telling the user
5698 they've excluded every running exit node. Fixes bug 7890; bugfix
5700 - When logging the number of descriptors we intend to download per
5701 directory request, do not log a number higher than then the number
5702 of descriptors we're fetching in total. Fixes bug 19648; bugfix
5704 - When warning about a directory owned by the wrong user, log the
5705 actual name of the user owning the directory. Previously, we'd log
5706 the name of the process owner twice. Fixes bug 23487; bugfix
5708 - Fix some messages on unexpected errors from the seccomp2 library.
5709 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
5710 - The tor specification says hop counts are 1-based, so fix two log
5711 messages that mistakenly logged 0-based hop counts. Fixes bug
5712 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
5713 Credit to Xiaofan Li for reporting this issue.
5715 o Minor bugfixes (logging, relay shutdown, annoyance):
5716 - When a circuit is marked for close, do not attempt to package any
5717 cells for channels on that circuit. Previously, we would detect
5718 this condition lower in the call stack, when we noticed that the
5719 circuit had no attached channel, and log an annoying message.
5720 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5722 o Minor bugfixes (memory safety, defensive programming):
5723 - Clear the target address when node_get_prim_orport() returns
5724 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
5726 o Minor bugfixes (memory usage):
5727 - When queuing DESTROY cells on a channel, only queue the circuit-id
5728 and reason fields: not the entire 514-byte cell. This fix should
5729 help mitigate any bugs or attacks that fill up these queues, and
5730 free more RAM for other uses. Fixes bug 24666; bugfix
5733 o Minor bugfixes (network layer):
5734 - When closing a connection via close_connection_immediately(), we
5735 mark it as "not blocked on bandwidth", to prevent later calls from
5736 trying to unblock it, and give it permission to read. This fixes a
5737 backtrace warning that can happen on relays under various
5738 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5740 o Minor bugfixes (onion services):
5741 - The introduction circuit was being timed out too quickly while
5742 waiting for the rendezvous circuit to complete. Keep the intro
5743 circuit around longer instead of timing out and reopening new ones
5744 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
5745 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
5746 so it matches dir-spec.txt. Fixes bug 24262; bugfix
5748 - When handling multiple SOCKS request for the same .onion address,
5749 only fetch the service descriptor once.
5750 - Avoid a possible double close of a circuit by the intro point on
5751 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
5752 bugfix on 0.3.0.1-alpha.
5753 - When reloading configured onion services, copy all information
5754 from the old service object. Previously, some data was omitted,
5755 causing delays in descriptor upload, and other bugs. Fixes bug
5756 23790; bugfix on 0.2.1.9-alpha.
5758 o Minor bugfixes (path selection):
5759 - When selecting relays by bandwidth, avoid a rounding error that
5760 could sometimes cause load to be imbalanced incorrectly.
5761 Previously, we would always round upwards; now, we round towards
5762 the nearest integer. This had the biggest effect when a relay's
5763 weight adjustments should have given it weight 0, but it got
5764 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5765 - When calculating the fraction of nodes that have descriptors, and
5766 all nodes in the network have zero bandwidths, count the number of
5767 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5768 - Actually log the total bandwidth in compute_weighted_bandwidths().
5769 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5771 o Minor bugfixes (portability):
5772 - Stop using the PATH_MAX variable, which is not defined on GNU
5773 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
5774 - Fix a bug in the bit-counting parts of our timing-wheel code on
5775 MSVC. (Note that MSVC is still not a supported build platform, due
5776 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5779 o Minor bugfixes (relay):
5780 - When uploading our descriptor for the first time after startup,
5781 report the reason for uploading as "Tor just started" rather than
5782 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
5783 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5784 relays, to prevent spurious address resolutions and descriptor
5785 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5786 bugfix on in 0.2.8.1-alpha.
5787 - Avoid a crash when transitioning from client mode to bridge mode.
5788 Previously, we would launch the worker threads whenever our
5789 "public server" mode changed, but not when our "server" mode
5790 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5792 o Minor bugfixes (testing):
5793 - Fix a spurious fuzzing-only use of an uninitialized value. Found
5794 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
5795 - Test that IPv6-only clients can use microdescriptors when running
5796 "make test-network-all". Requires chutney master 61c28b9 or later.
5797 Closes ticket 24109.
5798 - Prevent scripts/test/coverage from attempting to move gcov output
5799 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
5800 - Capture and detect several "Result does not fit" warnings in unit
5801 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
5803 - Fix additional channelpadding unit test failures by using mocked
5804 time instead of actual time for all tests. Fixes bug 23608; bugfix
5806 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
5807 to correctly handle cases where a caller gives it an RSA key of
5808 under 160 bits. (This is not actually a bug in Tor itself, but
5809 rather in our fuzzing code.) Fixes bug 24247; bugfix on
5810 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
5811 - Fix a broken unit test for the OutboundAddress option: the parsing
5812 function was never returning an error on failure. Fixes bug 23366;
5813 bugfix on 0.3.0.3-alpha.
5814 - Fix a signed-integer overflow in the unit tests for
5815 dir/download_status_random_backoff, which was untriggered until we
5816 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
5818 o Minor bugfixes (usability, control port):
5819 - Stop making an unnecessary routerlist check in NETINFO clock skew
5820 detection; this was preventing clients from reporting NETINFO clock
5821 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
5823 o Code simplification and refactoring:
5824 - Remove various ways of testing circuits and connections for
5825 "clientness"; instead, favor channel_is_client(). Part of
5827 - Extract the code for handling newly-open channels into a separate
5828 function from the general code to handle channel state
5829 transitions. This change simplifies our callgraph, reducing the
5830 size of the largest strongly connected component by roughly a
5831 factor of two. Closes ticket 22608.
5832 - Remove dead code for largely unused statistics on the number of
5833 times we've attempted various public key operations. Fixes bug
5834 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
5835 - Remove several now-obsolete functions for asking about old
5836 variants directory authority status. Closes ticket 22311; patch
5838 - Remove some of the code that once supported "Named" and "Unnamed"
5839 routers. Authorities no longer vote for these flags. Closes
5841 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
5842 and old hidden services, to indicate that they aren't suitable for
5843 new protocols or formats. Closes ticket 23026.
5844 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
5845 22521. Patch from Neel Chauhan.
5846 - Split the enormous circuit_send_next_onion_skin() function into
5847 multiple subfunctions. Closes ticket 22804.
5848 - Split the portions of the buffer.c module that handle particular
5849 protocols into separate modules. Part of ticket 23149.
5850 - Use our test macros more consistently, to produce more useful
5851 error messages when our unit tests fail. Add coccinelle patches to
5852 allow us to re-check for test macro uses. Closes ticket 22497.
5854 o Deprecated features:
5855 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
5856 now deprecated; they do not apply to relays, and they have had no
5857 effect on clients since 0.2.8.x. Closes ticket 19704.
5858 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
5859 only applies to direct unencrypted HTTP connections to your
5860 directory server, which your Tor probably isn't using. Closes
5864 - Add notes in man page regarding OS support for the various
5865 scheduler types. Attempt to use less jargon in the scheduler
5866 section. Closes ticket 24254.
5867 - Clarify that the Address option is entirely about setting an
5868 advertised IPv4 address. Closes ticket 18891.
5869 - Clarify the manpage's use of the term "address" to clarify what
5870 kind of address is intended. Closes ticket 21405.
5871 - Document that onion service subdomains are allowed, and ignored.
5872 Closes ticket 18736.
5873 - Clarify in the manual that "Sandbox 1" is only supported on Linux
5874 kernels. Closes ticket 22677.
5875 - Document all values of PublishServerDescriptor in the manpage.
5876 Closes ticket 15645.
5877 - Improve the documentation for the directory port part of the
5878 DirAuthority line. Closes ticket 20152.
5879 - Restore documentation for the authorities' "approved-routers"
5880 file. Closes ticket 21148.
5883 - The AllowDotExit option has been removed as unsafe. It has been
5884 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
5885 - The ClientDNSRejectInternalAddresses flag can no longer be set on
5886 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
5887 Closes ticket 21031.
5888 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
5889 nobody was using it any longer. Closes ticket 22377.
5892 Changes in version 0.3.1.9 - 2017-12-01:
5893 Tor 0.3.1.9 backports important security and stability fixes from the
5894 0.3.2 development series. All Tor users should upgrade to this
5895 release, or to another of the releases coming out today.
5897 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5898 - Fix a denial of service bug where an attacker could use a
5899 malformed directory object to cause a Tor instance to pause while
5900 OpenSSL would try to read a passphrase from the terminal. (Tor
5901 instances run without a terminal, which is the case for most Tor
5902 packages, are not impacted.) Fixes bug 24246; bugfix on every
5903 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
5904 Found by OSS-Fuzz as testcase 6360145429790720.
5905 - Fix a denial of service issue where an attacker could crash a
5906 directory authority using a malformed router descriptor. Fixes bug
5907 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
5909 - When checking for replays in the INTRODUCE1 cell data for a
5910 (legacy) onion service, correctly detect replays in the RSA-
5911 encrypted part of the cell. We were previously checking for
5912 replays on the entire cell, but those can be circumvented due to
5913 the malleability of Tor's legacy hybrid encryption. This fix helps
5914 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
5915 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
5918 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
5919 - Fix a use-after-free error that could crash v2 Tor onion services
5920 when they failed to open circuits while expiring introduction
5921 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
5922 also tracked as TROVE-2017-013 and CVE-2017-8823.
5924 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
5925 - When running as a relay, make sure that we never build a path
5926 through ourselves, even in the case where we have somehow lost the
5927 version of our descriptor appearing in the consensus. Fixes part
5928 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
5929 as TROVE-2017-012 and CVE-2017-8822.
5930 - When running as a relay, make sure that we never choose ourselves
5931 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
5932 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
5934 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
5935 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
5936 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
5937 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
5938 identifying and finding a workaround to this bug and to Moritz,
5939 Arthur Edelstein, and Roger for helping to track it down and
5942 o Minor features (bridge):
5943 - Bridges now include notice in their descriptors that they are
5944 bridges, and notice of their distribution status, based on their
5945 publication settings. Implements ticket 18329. For more fine-
5946 grained control of how a bridge is distributed, upgrade to 0.3.2.x
5949 o Minor features (directory authority, backport from 0.3.2.6-alpha):
5950 - Add an IPv6 address for the "bastet" directory authority. Closes
5953 o Minor features (geoip):
5954 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
5957 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
5958 - Avoid unnecessary calls to directory_fetches_from_authorities() on
5959 relays, to prevent spurious address resolutions and descriptor
5960 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
5961 bugfix on in 0.2.8.1-alpha.
5963 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
5964 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
5965 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
5967 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
5968 - When a circuit is marked for close, do not attempt to package any
5969 cells for channels on that circuit. Previously, we would detect
5970 this condition lower in the call stack, when we noticed that the
5971 circuit had no attached channel, and log an annoying message.
5972 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
5974 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
5975 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
5976 so it matches dir-spec.txt. Fixes bug 24262; bugfix
5979 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
5980 - Avoid a crash when transitioning from client mode to bridge mode.
5981 Previously, we would launch the worker threads whenever our
5982 "public server" mode changed, but not when our "server" mode
5983 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
5986 Changes in version 0.3.0.13 - 2017-12-01
5987 Tor 0.3.0.13 backports important security and stability bugfixes from
5988 later Tor releases. All Tor users should upgrade to this release, or
5989 to another of the releases coming out today.
5991 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
5992 2018. If you need a release with long-term support, please stick with
5993 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
5995 o Major bugfixes (security, backport from 0.3.2.6-alpha):
5996 - Fix a denial of service bug where an attacker could use a
5997 malformed directory object to cause a Tor instance to pause while
5998 OpenSSL would try to read a passphrase from the terminal. (Tor
5999 instances run without a terminal, which is the case for most Tor
6000 packages, are not impacted.) Fixes bug 24246; bugfix on every
6001 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6002 Found by OSS-Fuzz as testcase 6360145429790720.
6003 - Fix a denial of service issue where an attacker could crash a
6004 directory authority using a malformed router descriptor. Fixes bug
6005 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6007 - When checking for replays in the INTRODUCE1 cell data for a
6008 (legacy) onion service, correctly detect replays in the RSA-
6009 encrypted part of the cell. We were previously checking for
6010 replays on the entire cell, but those can be circumvented due to
6011 the malleability of Tor's legacy hybrid encryption. This fix helps
6012 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6013 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6016 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6017 - Fix a use-after-free error that could crash v2 Tor onion services
6018 when they failed to open circuits while expiring introduction
6019 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6020 also tracked as TROVE-2017-013 and CVE-2017-8823.
6022 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6023 - When running as a relay, make sure that we never build a path
6024 through ourselves, even in the case where we have somehow lost the
6025 version of our descriptor appearing in the consensus. Fixes part
6026 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6027 as TROVE-2017-012 and CVE-2017-8822.
6028 - When running as a relay, make sure that we never choose ourselves
6029 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6030 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6032 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6033 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6034 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6035 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6036 identifying and finding a workaround to this bug and to Moritz,
6037 Arthur Edelstein, and Roger for helping to track it down and
6040 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6041 - Enable a couple of pieces of Windows hardening: one
6042 (HeapEnableTerminationOnCorruption) that has been on-by-default
6043 since Windows 8, and unavailable before Windows 7; and one
6044 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6045 affect us, but shouldn't do any harm. Closes ticket 21953.
6047 o Minor features (bridge, backport from 0.3.1.9):
6048 - Bridges now include notice in their descriptors that they are
6049 bridges, and notice of their distribution status, based on their
6050 publication settings. Implements ticket 18329. For more fine-
6051 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6054 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6055 - Add an IPv6 address for the "bastet" directory authority. Closes
6058 o Minor features (geoip):
6059 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6062 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6063 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6064 relays, to prevent spurious address resolutions and descriptor
6065 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6066 bugfix on in 0.2.8.1-alpha.
6068 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6069 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6070 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6072 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6073 - When a circuit is marked for close, do not attempt to package any
6074 cells for channels on that circuit. Previously, we would detect
6075 this condition lower in the call stack, when we noticed that the
6076 circuit had no attached channel, and log an annoying message.
6077 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6079 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6080 - Avoid a crash when transitioning from client mode to bridge mode.
6081 Previously, we would launch the worker threads whenever our
6082 "public server" mode changed, but not when our "server" mode
6083 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6085 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6086 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6087 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6090 Changes in version 0.2.9.14 - 2017-12-01
6091 Tor 0.3.0.13 backports important security and stability bugfixes from
6092 later Tor releases. All Tor users should upgrade to this release, or
6093 to another of the releases coming out today.
6095 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6096 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6097 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6098 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6099 identifying and finding a workaround to this bug and to Moritz,
6100 Arthur Edelstein, and Roger for helping to track it down and
6103 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6104 - Fix a denial of service bug where an attacker could use a
6105 malformed directory object to cause a Tor instance to pause while
6106 OpenSSL would try to read a passphrase from the terminal. (Tor
6107 instances run without a terminal, which is the case for most Tor
6108 packages, are not impacted.) Fixes bug 24246; bugfix on every
6109 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6110 Found by OSS-Fuzz as testcase 6360145429790720.
6111 - Fix a denial of service issue where an attacker could crash a
6112 directory authority using a malformed router descriptor. Fixes bug
6113 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6115 - When checking for replays in the INTRODUCE1 cell data for a
6116 (legacy) onion service, correctly detect replays in the RSA-
6117 encrypted part of the cell. We were previously checking for
6118 replays on the entire cell, but those can be circumvented due to
6119 the malleability of Tor's legacy hybrid encryption. This fix helps
6120 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6121 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6124 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6125 - Fix a use-after-free error that could crash v2 Tor onion services
6126 when they failed to open circuits while expiring introduction
6127 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6128 also tracked as TROVE-2017-013 and CVE-2017-8823.
6130 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6131 - When running as a relay, make sure that we never build a path
6132 through ourselves, even in the case where we have somehow lost the
6133 version of our descriptor appearing in the consensus. Fixes part
6134 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6135 as TROVE-2017-012 and CVE-2017-8822.
6137 o Minor features (bridge, backport from 0.3.1.9):
6138 - Bridges now include notice in their descriptors that they are
6139 bridges, and notice of their distribution status, based on their
6140 publication settings. Implements ticket 18329. For more fine-
6141 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6144 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6145 - Add an IPv6 address for the "bastet" directory authority. Closes
6148 o Minor features (geoip):
6149 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6152 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6153 - Enable a couple of pieces of Windows hardening: one
6154 (HeapEnableTerminationOnCorruption) that has been on-by-default
6155 since Windows 8, and unavailable before Windows 7; and one
6156 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6157 affect us, but shouldn't do any harm. Closes ticket 21953.
6159 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6160 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6161 relays, to prevent spurious address resolutions and descriptor
6162 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6163 bugfix on in 0.2.8.1-alpha.
6165 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6166 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6167 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6169 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6170 - When a circuit is marked for close, do not attempt to package any
6171 cells for channels on that circuit. Previously, we would detect
6172 this condition lower in the call stack, when we noticed that the
6173 circuit had no attached channel, and log an annoying message.
6174 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6176 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6177 - Avoid a crash when transitioning from client mode to bridge mode.
6178 Previously, we would launch the worker threads whenever our
6179 "public server" mode changed, but not when our "server" mode
6180 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6182 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6183 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6184 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6187 Changes in version 0.2.8.17 - 2017-12-01
6188 Tor 0.2.8.17 backports important security and stability bugfixes from
6189 later Tor releases. All Tor users should upgrade to this release, or
6190 to another of the releases coming out today.
6192 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6193 2018. If you need a release with long-term support, please upgrade with
6194 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6196 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6197 - Fix a denial of service bug where an attacker could use a
6198 malformed directory object to cause a Tor instance to pause while
6199 OpenSSL would try to read a passphrase from the terminal. (Tor
6200 instances run without a terminal, which is the case for most Tor
6201 packages, are not impacted.) Fixes bug 24246; bugfix on every
6202 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6203 Found by OSS-Fuzz as testcase 6360145429790720.
6204 - When checking for replays in the INTRODUCE1 cell data for a
6205 (legacy) onion service, correctly detect replays in the RSA-
6206 encrypted part of the cell. We were previously checking for
6207 replays on the entire cell, but those can be circumvented due to
6208 the malleability of Tor's legacy hybrid encryption. This fix helps
6209 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6210 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6213 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6214 - Fix a use-after-free error that could crash v2 Tor onion services
6215 when they failed to open circuits while expiring introduction
6216 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6217 also tracked as TROVE-2017-013 and CVE-2017-8823.
6219 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6220 - When running as a relay, make sure that we never build a path through
6221 ourselves, even in the case where we have somehow lost the version of
6222 our descriptor appearing in the consensus. Fixes part of bug 21534;
6223 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
6226 o Minor features (bridge, backport from 0.3.1.9):
6227 - Bridges now include notice in their descriptors that they are
6228 bridges, and notice of their distribution status, based on their
6229 publication settings. Implements ticket 18329. For more fine-
6230 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6233 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6234 - Add an IPv6 address for the "bastet" directory authority. Closes
6237 o Minor features (geoip):
6238 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6241 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6242 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6243 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6246 Changes in version 0.2.5.16 - 2017-12-01
6247 Tor 0.2.5.13 backports important security and stability bugfixes from
6248 later Tor releases. All Tor users should upgrade to this release, or
6249 to another of the releases coming out today.
6251 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6252 2018. If you need a release with long-term support, please upgrade to
6253 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6255 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6256 - Fix a denial of service bug where an attacker could use a
6257 malformed directory object to cause a Tor instance to pause while
6258 OpenSSL would try to read a passphrase from the terminal. (Tor
6259 instances run without a terminal, which is the case for most Tor
6260 packages, are not impacted.) Fixes bug 24246; bugfix on every
6261 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6262 Found by OSS-Fuzz as testcase 6360145429790720.
6263 - When checking for replays in the INTRODUCE1 cell data for a
6264 (legacy) onion service, correctly detect replays in the RSA-
6265 encrypted part of the cell. We were previously checking for
6266 replays on the entire cell, but those can be circumvented due to
6267 the malleability of Tor's legacy hybrid encryption. This fix helps
6268 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6269 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6272 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6273 - When running as a relay, make sure that we never build a path
6274 through ourselves, even in the case where we have somehow lost the
6275 version of our descriptor appearing in the consensus. Fixes part
6276 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6277 as TROVE-2017-012 and CVE-2017-8822.
6279 o Minor features (bridge, backport from 0.3.1.9):
6280 - Bridges now include notice in their descriptors that they are
6281 bridges, and notice of their distribution status, based on their
6282 publication settings. Implements ticket 18329. For more fine-
6283 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6286 o Minor features (geoip):
6287 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6291 Changes in version 0.2.5.15 - 2017-10-25
6292 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
6293 series. It also adds a new directory authority, Bastet.
6295 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6296 2018. If you need a release with long-term support, please upgrade to
6297 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6299 o Directory authority changes:
6300 - Add "Bastet" as a ninth directory authority to the default list.
6301 Closes ticket 23910.
6302 - The directory authority "Longclaw" has changed its IP address.
6303 Closes ticket 23592.
6305 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6306 - Avoid an assertion failure bug affecting our implementation of
6307 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6308 handling of "0xx" differs from what we had expected. Fixes bug
6309 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6311 o Minor features (geoip):
6312 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6315 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6316 - Fix a memset() off the end of an array when packing cells. This
6317 bug should be harmless in practice, since the corrupted bytes are
6318 still in the same structure, and are always padding bytes,
6319 ignored, or immediately overwritten, depending on compiler
6320 behavior. Nevertheless, because the memset()'s purpose is to make
6321 sure that any other cell-handling bugs can't expose bytes to the
6322 network, we need to fix it. Fixes bug 22737; bugfix on
6323 0.2.4.11-alpha. Fixes CID 1401591.
6325 o Build features (backport from 0.3.1.5-alpha):
6326 - Tor's repository now includes a Travis Continuous Integration (CI)
6327 configuration file (.travis.yml). This is meant to help new
6328 developers and contributors who fork Tor to a Github repository be
6329 better able to test their changes, and understand what we expect
6330 to pass. To use this new build feature, you must fork Tor to your
6331 Github account, then go into the "Integrations" menu in the
6332 repository settings for your fork and enable Travis, then push
6333 your changes. Closes ticket 22636.
6336 Changes in version 0.2.8.16 - 2017-10-25
6337 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
6338 series, including a bugfix for a crash issue that had affected relays
6339 under memory pressure. It also adds a new directory authority, Bastet.
6341 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6342 2018. If you need a release with long-term support, please stick with
6343 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6345 o Directory authority changes:
6346 - Add "Bastet" as a ninth directory authority to the default list.
6347 Closes ticket 23910.
6348 - The directory authority "Longclaw" has changed its IP address.
6349 Closes ticket 23592.
6351 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6352 - Fix a timing-based assertion failure that could occur when the
6353 circuit out-of-memory handler freed a connection's output buffer.
6354 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6356 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6357 - Remove longclaw's IPv6 address, as it will soon change. Authority
6358 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6359 3/8 directory authorities with IPv6 addresses, but there are also
6360 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6362 o Minor features (geoip):
6363 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6367 Changes in version 0.2.9.13 - 2017-10-25
6368 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
6369 series, including a bugfix for a crash issue that had affected relays
6370 under memory pressure. It also adds a new directory authority, Bastet.
6372 o Directory authority changes:
6373 - Add "Bastet" as a ninth directory authority to the default list.
6374 Closes ticket 23910.
6375 - The directory authority "Longclaw" has changed its IP address.
6376 Closes ticket 23592.
6378 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6379 - Fix a timing-based assertion failure that could occur when the
6380 circuit out-of-memory handler freed a connection's output buffer.
6381 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6383 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6384 - Remove longclaw's IPv6 address, as it will soon change. Authority
6385 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6386 3/8 directory authorities with IPv6 addresses, but there are also
6387 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6389 o Minor features (geoip):
6390 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6393 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6394 - When a directory authority rejects a descriptor or extrainfo with
6395 a given digest, mark that digest as undownloadable, so that we do
6396 not attempt to download it again over and over. We previously
6397 tried to avoid downloading such descriptors by other means, but we
6398 didn't notice if we accidentally downloaded one anyway. This
6399 behavior became problematic in 0.2.7.2-alpha, when authorities
6400 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6403 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6404 - Clear the address when node_get_prim_orport() returns early.
6405 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6407 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6408 - When running as a Windows service, set the ID of the main thread
6409 correctly. Failure to do so made us fail to send log messages to
6410 the controller in 0.2.1.16-rc, slowed down controller event
6411 delivery in 0.2.7.3-rc and later, and crash with an assertion
6412 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6413 Patch and diagnosis from "Vort".
6416 Changes in version 0.3.0.12 - 2017-10-25
6417 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
6418 series, including a bugfix for a crash issue that had affected relays
6419 under memory pressure. It also adds a new directory authority, Bastet.
6421 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6422 2018. If you need a release with long-term support, please stick with
6423 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6425 o Directory authority changes:
6426 - Add "Bastet" as a ninth directory authority to the default list.
6427 Closes ticket 23910.
6428 - The directory authority "Longclaw" has changed its IP address.
6429 Closes ticket 23592.
6431 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6432 - Fix a timing-based assertion failure that could occur when the
6433 circuit out-of-memory handler freed a connection's output buffer.
6434 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6436 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6437 - Remove longclaw's IPv6 address, as it will soon change. Authority
6438 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6439 3/8 directory authorities with IPv6 addresses, but there are also
6440 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6442 o Minor features (geoip):
6443 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6446 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6447 - When a directory authority rejects a descriptor or extrainfo with
6448 a given digest, mark that digest as undownloadable, so that we do
6449 not attempt to download it again over and over. We previously
6450 tried to avoid downloading such descriptors by other means, but we
6451 didn't notice if we accidentally downloaded one anyway. This
6452 behavior became problematic in 0.2.7.2-alpha, when authorities
6453 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6456 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
6457 - Avoid a possible double close of a circuit by the intro point on
6458 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6459 bugfix on 0.3.0.1-alpha.
6461 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6462 - Clear the address when node_get_prim_orport() returns early.
6463 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6465 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6466 - When running as a Windows service, set the ID of the main thread
6467 correctly. Failure to do so made us fail to send log messages to
6468 the controller in 0.2.1.16-rc, slowed down controller event
6469 delivery in 0.2.7.3-rc and later, and crash with an assertion
6470 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6471 Patch and diagnosis from "Vort".
6474 Changes in version 0.3.1.8 - 2017-10-25
6475 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
6476 It includes several bugfixes, including a bugfix for a crash issue
6477 that had affected relays under memory pressure. It also adds
6478 a new directory authority, Bastet.
6480 o Directory authority changes:
6481 - Add "Bastet" as a ninth directory authority to the default list.
6482 Closes ticket 23910.
6483 - The directory authority "Longclaw" has changed its IP address.
6484 Closes ticket 23592.
6486 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6487 - Fix a timing-based assertion failure that could occur when the
6488 circuit out-of-memory handler freed a connection's output buffer.
6489 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6491 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6492 - Remove longclaw's IPv6 address, as it will soon change. Authority
6493 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6494 3/8 directory authorities with IPv6 addresses, but there are also
6495 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6497 o Minor features (geoip):
6498 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6501 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
6502 - Fix a compilation warning when building with zstd support on
6503 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
6504 and fixed by Andreas Stieger.
6506 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
6507 - Handle a pathological case when decompressing Zstandard data when
6508 the output buffer size is zero. Fixes bug 23551; bugfix
6511 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
6512 - Remove the length limit on HTTP status lines that authorities can
6513 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
6515 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
6516 - Avoid a possible double close of a circuit by the intro point on
6517 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
6518 bugfix on 0.3.0.1-alpha.
6520 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6521 - Clear the address when node_get_prim_orport() returns early.
6522 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6524 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
6525 - Fix additional channelpadding unit test failures by using mocked
6526 time instead of actual time for all tests. Fixes bug 23608; bugfix
6530 Changes in version 0.2.8.15 - 2017-09-18
6531 Tor 0.2.8.15 backports a collection of bugfixes from later
6534 Most significantly, it includes a fix for TROVE-2017-008, a
6535 security bug that affects hidden services running with the
6536 SafeLogging option disabled. For more information, see
6537 https://trac.torproject.org/projects/tor/ticket/23490
6539 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
6540 2018. We suggest that you upgrade to the latest stable release if
6541 possible. If you can't, we recommend that you upgrade at least to
6542 0.2.9, which will be supported until 2020.
6544 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6545 - Avoid an assertion failure bug affecting our implementation of
6546 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6547 handling of "0xx" differs from what we had expected. Fixes bug
6548 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6551 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6554 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6555 - Backport a fix for an "unused variable" warning that appeared
6556 in some versions of mingw. Fixes bug 22838; bugfix on
6559 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6560 - Fix a memset() off the end of an array when packing cells. This
6561 bug should be harmless in practice, since the corrupted bytes are
6562 still in the same structure, and are always padding bytes,
6563 ignored, or immediately overwritten, depending on compiler
6564 behavior. Nevertheless, because the memset()'s purpose is to make
6565 sure that any other cell-handling bugs can't expose bytes to the
6566 network, we need to fix it. Fixes bug 22737; bugfix on
6567 0.2.4.11-alpha. Fixes CID 1401591.
6569 o Build features (backport from 0.3.1.5-alpha):
6570 - Tor's repository now includes a Travis Continuous Integration (CI)
6571 configuration file (.travis.yml). This is meant to help new
6572 developers and contributors who fork Tor to a Github repository be
6573 better able to test their changes, and understand what we expect
6574 to pass. To use this new build feature, you must fork Tor to your
6575 Github account, then go into the "Integrations" menu in the
6576 repository settings for your fork and enable Travis, then push
6577 your changes. Closes ticket 22636.
6580 Changes in version 0.2.9.12 - 2017-09-18
6581 Tor 0.2.9.12 backports a collection of bugfixes from later
6584 Most significantly, it includes a fix for TROVE-2017-008, a
6585 security bug that affects hidden services running with the
6586 SafeLogging option disabled. For more information, see
6587 https://trac.torproject.org/projects/tor/ticket/23490
6589 o Major features (security, backport from 0.3.0.2-alpha):
6590 - Change the algorithm used to decide DNS TTLs on client and server
6591 side, to better resist DNS-based correlation attacks like the
6592 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
6593 Feamster. Now relays only return one of two possible DNS TTL
6594 values, and clients are willing to believe DNS TTL values up to 3
6595 hours long. Closes ticket 19769.
6597 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
6598 - Fix a rare crash when sending a begin cell on a circuit whose
6599 linked directory connection had already been closed. Fixes bug
6600 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
6602 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
6603 - Fix a bug that prevented exit nodes from caching DNS records for
6604 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
6606 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
6607 - Fix a typo that had prevented TPROXY-based transparent proxying
6608 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6609 Patch from "d4fq0fQAgoJ".
6611 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6612 - Avoid an assertion failure bug affecting our implementation of
6613 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6614 handling of "0xx" differs from what we had expected. Fixes bug
6615 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6617 o Minor features (code style, backport from 0.3.1.3-alpha):
6618 - Add "Falls through" comments to our codebase, in order to silence
6619 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6620 Stieger. Closes ticket 22446.
6622 o Minor features (geoip):
6623 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6626 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
6627 - Roll over monthly accounting at the configured hour and minute,
6628 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
6629 Found by Andrey Karpov with PVS-Studio.
6631 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
6632 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
6633 bugfix on 0.2.8.1-alpha.
6634 - Fix warnings when building with libscrypt and openssl scrypt support
6635 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
6636 - When building with certain versions the mingw C header files, avoid
6637 float-conversion warnings when calling the C functions isfinite(),
6638 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
6640 o Minor bugfixes (compilation, backport from 0.3.1.7):
6641 - Avoid compiler warnings in the unit tests for running tor_sscanf()
6642 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6644 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
6645 - Backport a fix for an "unused variable" warning that appeared
6646 in some versions of mingw. Fixes bug 22838; bugfix on
6649 o Minor bugfixes (controller, backport from 0.3.1.7):
6650 - Do not crash when receiving a HSPOST command with an empty body.
6651 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6652 - Do not crash when receiving a POSTDESCRIPTOR command with an
6653 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6655 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
6656 - Avoid Coverity build warnings related to our BUG() macro. By
6657 default, Coverity treats BUG() as the Linux kernel does: an
6658 instant abort(). We need to override that so our BUG() macro
6659 doesn't prevent Coverity from analyzing functions that use it.
6660 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
6662 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6663 - Fix a memset() off the end of an array when packing cells. This
6664 bug should be harmless in practice, since the corrupted bytes are
6665 still in the same structure, and are always padding bytes,
6666 ignored, or immediately overwritten, depending on compiler
6667 behavior. Nevertheless, because the memset()'s purpose is to make
6668 sure that any other cell-handling bugs can't expose bytes to the
6669 network, we need to fix it. Fixes bug 22737; bugfix on
6670 0.2.4.11-alpha. Fixes CID 1401591.
6672 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
6673 - When setting the maximum number of connections allowed by the OS,
6674 always allow some extra file descriptors for other files. Fixes
6675 bug 22797; bugfix on 0.2.0.10-alpha.
6677 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
6678 - Avoid a sandbox failure when trying to re-bind to a socket and
6679 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
6681 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
6682 - Permit the fchmod system call, to avoid crashing on startup when
6683 starting with the seccomp2 sandbox and an unexpected set of
6684 permissions on the data directory or its contents. Fixes bug
6685 22516; bugfix on 0.2.5.4-alpha.
6687 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
6688 - Avoid a double-marked-circuit warning that could happen when we
6689 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
6692 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
6693 - Reject version numbers with non-numeric prefixes (such as +, -, or
6694 whitespace). Disallowing whitespace prevents differential version
6695 parsing between POSIX-based and Windows platforms. Fixes bug 21507
6696 and part of 21508; bugfix on 0.0.8pre1.
6698 o Build features (backport from 0.3.1.5-alpha):
6699 - Tor's repository now includes a Travis Continuous Integration (CI)
6700 configuration file (.travis.yml). This is meant to help new
6701 developers and contributors who fork Tor to a Github repository be
6702 better able to test their changes, and understand what we expect
6703 to pass. To use this new build feature, you must fork Tor to your
6704 Github account, then go into the "Integrations" menu in the
6705 repository settings for your fork and enable Travis, then push
6706 your changes. Closes ticket 22636.
6709 Changes in version 0.3.0.11 - 2017-09-18
6710 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
6713 Most significantly, it includes a fix for TROVE-2017-008, a
6714 security bug that affects hidden services running with the
6715 SafeLogging option disabled. For more information, see
6716 https://trac.torproject.org/projects/tor/ticket/23490
6718 o Minor features (code style, backport from 0.3.1.7):
6719 - Add "Falls through" comments to our codebase, in order to silence
6720 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6721 Stieger. Closes ticket 22446.
6724 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
6727 o Minor bugfixes (compilation, backport from 0.3.1.7):
6728 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
6729 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
6731 o Minor bugfixes (controller, backport from 0.3.1.7):
6732 - Do not crash when receiving a HSPOST command with an empty body.
6733 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
6734 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
6735 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
6737 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
6738 - When setting the maximum number of connections allowed by the OS,
6739 always allow some extra file descriptors for other files. Fixes
6740 bug 22797; bugfix on 0.2.0.10-alpha.
6742 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
6743 - Remove a forgotten debugging message when an introduction point
6744 successfully establishes a hidden service prop224 circuit with
6746 - Change three other log_warn() for an introduction point to
6747 protocol warnings, because they can be failure from the network
6748 and are not relevant to the operator. Fixes bug 23078; bugfix on
6749 0.3.0.1-alpha and 0.3.0.2-alpha.
6752 Changes in version 0.3.1.7 - 2017-09-18
6753 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
6755 With the 0.3.1 series, Tor now serves and downloads directory
6756 information in more compact formats, to save on bandwidth overhead. It
6757 also contains a new padding system to resist netflow-based traffic
6758 analysis, and experimental support for building parts of Tor in Rust
6759 (though no parts of Tor are in Rust yet). There are also numerous
6760 small features, bugfixes on earlier release series, and groundwork for
6761 the hidden services revamp of 0.3.2.
6763 This release also includes a fix for TROVE-2017-008, a security bug
6764 that affects hidden services running with the SafeLogging option
6765 disabled. For more information, see
6766 https://trac.torproject.org/projects/tor/ticket/23490
6768 Per our stable release policy, we plan to support each stable release
6769 series for at least the next nine months, or for three months after
6770 the first stable release of the next series: whichever is longer. If
6771 you need a release with long-term support, we recommend that you stay
6772 with the 0.2.9 series.
6774 Below is a list of the changes since 0.3.0. For a list of all
6775 changes since 0.3.1.6-rc, see the ChangeLog file.
6778 - To build with zstd and lzma support, Tor now requires the
6779 pkg-config tool at build time.
6781 o Major bugfixes (security, hidden services, loggging):
6782 - Fix a bug where we could log uninitialized stack when a certain
6783 hidden service error occurred while SafeLogging was disabled.
6784 Fixes bug #23490; bugfix on 0.2.7.2-alpha.
6785 This is also tracked as TROVE-2017-008 and CVE-2017-0380.
6787 o Major features (build system, continuous integration):
6788 - Tor's repository now includes a Travis Continuous Integration (CI)
6789 configuration file (.travis.yml). This is meant to help new
6790 developers and contributors who fork Tor to a Github repository be
6791 better able to test their changes, and understand what we expect
6792 to pass. To use this new build feature, you must fork Tor to your
6793 Github account, then go into the "Integrations" menu in the
6794 repository settings for your fork and enable Travis, then push
6795 your changes. Closes ticket 22636.
6797 o Major features (directory protocol):
6798 - Tor relays and authorities can now serve clients an abbreviated
6799 version of the consensus document, containing only the changes
6800 since an older consensus document that the client holds. Clients
6801 now request these documents when available. When both client and
6802 server use this new protocol, they will use far less bandwidth (up
6803 to 94% less) to keep the client's consensus up-to-date. Implements
6804 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
6805 - Tor can now compress directory traffic with lzma or with zstd
6806 compression algorithms, which can deliver better bandwidth
6807 performance. Because lzma is computationally expensive, it's only
6808 used for documents that can be compressed once and served many
6809 times. Support for these algorithms requires that tor is built
6810 with the libzstd and/or liblzma libraries available. Implements
6811 proposal 278; closes ticket 21662.
6812 - Relays now perform the more expensive compression operations, and
6813 consensus diff generation, in worker threads. This separation
6814 avoids delaying the main thread when a new consensus arrives.
6816 o Major features (experimental):
6817 - Tor can now build modules written in Rust. To turn this on, pass
6818 the "--enable-rust" flag to the configure script. It's not time to
6819 get excited yet: currently, there is no actual Rust functionality
6820 beyond some simple glue code, and a notice at startup to tell you
6821 that Rust is running. Still, we hope that programmers and
6822 packagers will try building Tor with Rust support, so that we can
6823 find issues and solve portability problems. Closes ticket 22106.
6825 o Major features (traffic analysis resistance):
6826 - Connections between clients and relays now send a padding cell in
6827 each direction every 1.5 to 9.5 seconds (tunable via consensus
6828 parameters). This padding will not resist specialized
6829 eavesdroppers, but it should be enough to make many ISPs' routine
6830 network flow logging less useful in traffic analysis against
6833 Padding is negotiated using Tor's link protocol, so both relays
6834 and clients must upgrade for this to take effect. Clients may
6835 still send padding despite the relay's version by setting
6836 ConnectionPadding 1 in torrc, and may disable padding by setting
6837 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
6838 users with the torrc option ReducedConnectionPadding. Implements
6839 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
6840 - Relays will publish 24 hour totals of padding and non-padding cell
6841 counts to their extra-info descriptors, unless PaddingStatistics 0
6842 is set in torrc. These 24 hour totals are also rounded to
6845 o Major bugfixes (hidden service, relay, security):
6846 - Fix a remotely triggerable assertion failure when a hidden service
6847 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
6848 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
6849 - Fix a remotely triggerable assertion failure caused by receiving a
6850 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
6851 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
6854 o Major bugfixes (path selection, security):
6855 - When choosing which guard to use for a circuit, avoid the exit's
6856 family along with the exit itself. Previously, the new guard
6857 selection logic avoided the exit, but did not consider its family.
6858 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
6859 006 and CVE-2017-0377.
6861 o Major bugfixes (connection usage):
6862 - We use NETINFO cells to try to determine if both relays involved
6863 in a connection will agree on the canonical status of that
6864 connection. We prefer the connections where this is the case for
6865 extend cells, and try to close connections where relays disagree
6866 on their canonical status early. Also, we now prefer the oldest
6867 valid connection for extend cells. These two changes should reduce
6868 the number of long-term connections that are kept open between
6869 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
6870 - Relays now log hourly statistics (look for
6871 "channel_check_for_duplicates" lines) on the total number of
6872 connections to other relays. If the number of connections per
6873 relay is unexpectedly large, this log message is at notice level.
6874 Otherwise it is at info.
6876 o Major bugfixes (entry guards):
6877 - When starting with an old consensus, do not add new entry guards
6878 unless the consensus is "reasonably live" (under 1 day old). Fixes
6879 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
6880 - Don't block bootstrapping when a primary bridge is offline and we
6881 can't get its descriptor. Fixes bug 22325; fixes one case of bug
6882 21969; bugfix on 0.3.0.3-alpha.
6884 o Major bugfixes (linux TPROXY support):
6885 - Fix a typo that had prevented TPROXY-based transparent proxying
6886 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
6887 Patch from "d4fq0fQAgoJ".
6889 o Major bugfixes (openbsd, denial-of-service):
6890 - Avoid an assertion failure bug affecting our implementation of
6891 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6892 handling of "0xx" differs from what we had expected. Fixes bug
6893 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6895 o Major bugfixes (relay, link handshake):
6896 - When performing the v3 link handshake on a TLS connection, report
6897 that we have the x509 certificate that we actually used on that
6898 connection, even if we have changed certificates since that
6899 connection was first opened. Previously, we would claim to have
6900 used our most recent x509 link certificate, which would sometimes
6901 make the link handshake fail. Fixes one case of bug 22460; bugfix
6904 o Major bugfixes (relays, key management):
6905 - Regenerate link and authentication certificates whenever the key
6906 that signs them changes; also, regenerate link certificates
6907 whenever the signed key changes. Previously, these processes were
6908 only weakly coupled, and we relays could (for minutes to hours)
6909 wind up with an inconsistent set of keys and certificates, which
6910 other relays would not accept. Fixes two cases of bug 22460;
6911 bugfix on 0.3.0.1-alpha.
6912 - When sending an Ed25519 signing->link certificate in a CERTS cell,
6913 send the certificate that matches the x509 certificate that we
6914 used on the TLS connection. Previously, there was a race condition
6915 if the TLS context rotated after we began the TLS handshake but
6916 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
6919 o Minor features (security, windows):
6920 - Enable a couple of pieces of Windows hardening: one
6921 (HeapEnableTerminationOnCorruption) that has been on-by-default
6922 since Windows 8, and unavailable before Windows 7; and one
6923 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6924 affect us, but shouldn't do any harm. Closes ticket 21953.
6926 o Minor features (bridge authority):
6927 - Add "fingerprint" lines to the networkstatus-bridges file produced
6928 by bridge authorities. Closes ticket 22207.
6930 o Minor features (code style):
6931 - Add "Falls through" comments to our codebase, in order to silence
6932 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
6933 Stieger. Closes ticket 22446.
6935 o Minor features (config options):
6936 - Allow "%include" directives in torrc configuration files. These
6937 directives import the settings from other files, or from all the
6938 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
6939 - Make SAVECONF return an error when overwriting a torrc that has
6940 includes. Using SAVECONF with the FORCE option will allow it to
6941 overwrite torrc even if includes are used. Related to ticket 1922.
6942 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
6943 will work without the FORCE option. Related to ticket 1922.
6945 o Minor features (controller):
6946 - Warn the first time that a controller requests data in the long-
6947 deprecated 'GETINFO network-status' format. Closes ticket 21703.
6949 o Minor features (defaults):
6950 - The default value for UseCreateFast is now 0: clients which
6951 haven't yet received a consensus document will now use a proper
6952 ntor handshake to talk to their directory servers whenever they
6953 can. Closes ticket 21407.
6954 - Onion key rotation and expiry intervals are now defined as a
6955 network consensus parameter, per proposal 274. The default
6956 lifetime of an onion key is increased from 7 to 28 days. Old onion
6957 keys will expire after 7 days by default. This change will make
6958 consensus diffs much smaller, and save significant bandwidth.
6959 Closes ticket 21641.
6961 o Minor features (defensive programming):
6962 - Create a pair of consensus parameters, nf_pad_tor2web and
6963 nf_pad_single_onion, to disable netflow padding in the consensus
6964 for non-anonymous connections in case the overhead is high. Closes
6967 o Minor features (diagnostic):
6968 - Add a stack trace to the bug warnings that can be logged when
6969 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
6970 attempt for bug 23105.
6971 - Add logging messages to try to diagnose a rare bug that seems to
6972 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
6973 think this is happening because of incorrect system clocks, but
6974 we'd like to know for certain. Diagnostic for bug 22466.
6975 - Avoid an assertion failure, and log a better error message, when
6976 unable to remove a file from the consensus cache on Windows.
6977 Attempts to mitigate and diagnose bug 22752.
6979 o Minor features (directory authority):
6980 - Improve the message that authorities report to relays that present
6981 RSA/Ed25519 keypairs that conflict with previously pinned keys.
6982 Closes ticket 22348.
6984 o Minor features (directory cache, consensus diff):
6985 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
6986 operators with low-resource environments to adjust the number of
6987 consensuses they'll store and generate diffs from. Most cache
6988 operators should leave it unchanged. Helps to work around
6991 o Minor features (fallback directory list):
6992 - Update the fallback directory mirror whitelist and blacklist based
6993 on operator emails. Closes task 21121.
6994 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
6995 December 2016 (of which ~126 were still functional) with a list of
6996 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
6997 2017. Resolves ticket 21564.
6999 o Minor features (geoip):
7000 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7003 o Minor features (hidden services, logging):
7004 - Log a message when a hidden service descriptor has fewer
7005 introduction points than specified in
7006 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
7007 - Log a message when a hidden service reaches its introduction point
7008 circuit limit, and when that limit is reset. Follow up to ticket
7009 21594; closes ticket 21622.
7010 - Warn user if multiple entries in EntryNodes and at least one
7011 HiddenService are used together. Pinning EntryNodes along with a
7012 hidden service can be possibly harmful; for instance see ticket
7013 14917 or 21155. Closes ticket 21155.
7015 o Minor features (linux seccomp2 sandbox):
7016 - We now have a document storage backend compatible with the Linux
7017 seccomp2 sandbox. This backend is used for consensus documents and
7018 diffs between them; in the long term, we'd like to use it for
7019 unparseable directory material too. Closes ticket 21645
7020 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
7021 from 1MB to 16MB. This was necessary with the glibc allocator in
7022 order to allow worker threads to allocate more memory -- which in
7023 turn is necessary because of our new use of worker threads for
7024 compression. Closes ticket 22096.
7026 o Minor features (logging):
7027 - Log files are no longer created world-readable by default.
7028 (Previously, most distributors would store the logs in a non-
7029 world-readable location to prevent inappropriate access. This
7030 change is an extra precaution.) Closes ticket 21729; patch
7033 o Minor features (performance):
7034 - Our Keccak (SHA-3) implementation now accesses memory more
7035 efficiently, especially on little-endian systems. Closes
7037 - Add an O(1) implementation of channel_find_by_global_id(), to
7038 speed some controller functions.
7040 o Minor features (relay, configuration):
7041 - The MyFamily option may now be repeated as many times as desired,
7042 for relays that want to configure large families. Closes ticket
7043 4998; patch by Daniel Pinto.
7045 o Minor features (relay, performance):
7046 - Always start relays with at least two worker threads, to prevent
7047 priority inversion on slow tasks. Part of the fix for bug 22883.
7048 - Allow background work to be queued with different priorities, so
7049 that a big pile of slow low-priority jobs will not starve out
7050 higher priority jobs. This lays the groundwork for a fix for
7053 o Minor features (safety):
7054 - Add an explicit check to extrainfo_parse_entry_from_string() for
7055 NULL inputs. We don't believe this can actually happen, but it may
7056 help silence a warning from the Clang analyzer. Closes
7059 o Minor features (testing):
7060 - Add more tests for compression backend initialization. Closes
7062 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
7063 When Tor is compiled with this option, we disable a number of
7064 redundant memory-safety failsafes that are intended to stop bugs
7065 from becoming security issues. This makes it easier to hunt for
7066 bugs that would be security issues without the failsafes turned
7067 on. Closes ticket 21439.
7068 - Add a general event-tracing instrumentation support to Tor. This
7069 subsystem will enable developers and researchers to add fine-
7070 grained instrumentation to their Tor instances, for use when
7071 examining Tor network performance issues. There are no trace
7072 events yet, and event-tracing is off by default unless enabled at
7073 compile time. Implements ticket 13802.
7074 - Improve our version parsing tests: add tests for typical version
7075 components, add tests for invalid versions, including numeric
7076 range and non-numeric prefixes. Unit tests 21278, 21450, and
7077 21507. Partially implements 21470.
7079 o Minor bugfixes (bandwidth accounting):
7080 - Roll over monthly accounting at the configured hour and minute,
7081 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7082 Found by Andrey Karpov with PVS-Studio.
7084 o Minor bugfixes (code correctness):
7085 - Accurately identify client connections by their lack of peer
7086 authentication. This means that we bail out earlier if asked to
7087 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
7090 o Minor bugfixes (compilation warnings):
7091 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
7092 22915; bugfix on 0.2.8.1-alpha.
7093 - Fix warnings when building with libscrypt and openssl scrypt
7094 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7095 - When building with certain versions of the mingw C header files,
7096 avoid float-conversion warnings when calling the C functions
7097 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
7100 o Minor bugfixes (compilation):
7101 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7102 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7104 o Minor bugfixes (compression):
7105 - When spooling compressed data to an output buffer, don't try to
7106 spool more data when there is no more data to spool and we are not
7107 trying to flush the input. Previously, we would sometimes launch
7108 compression requests with nothing to do, which interferes with our
7109 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
7111 o Minor bugfixes (configuration):
7112 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
7113 bug 22252; bugfix on 0.2.9.3-alpha.
7115 o Minor bugfixes (connection lifespan):
7116 - Allow more control over how long TLS connections are kept open:
7117 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
7118 single option called CircuitsAvailableTimeout. Also, allow the
7119 consensus to control the default values for both this preference
7120 and the lifespan of relay-to-relay connections. Fixes bug 17592;
7121 bugfix on 0.2.5.5-alpha.
7122 - Increase the initial circuit build timeout testing frequency, to
7123 help ensure that ReducedConnectionPadding clients finish learning
7124 a timeout before their orconn would expire. The initial testing
7125 rate was set back in the days of TAP and before the Tor Browser
7126 updater, when we had to be much more careful about new clients
7127 making lots of circuits. With this change, a circuit build timeout
7128 is learned in about 15-20 minutes, instead of 100-120 minutes.
7130 o Minor bugfixes (controller):
7131 - Do not crash when receiving a HSPOST command with an empty body.
7132 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7133 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7134 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7135 - GETINFO onions/current and onions/detached no longer respond with
7136 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
7137 - Trigger HS descriptor events on the control port when the client
7138 fails to pick a hidden service directory for a hidden service.
7139 This can happen if all the hidden service directories are in
7140 ExcludeNodes, or they have all been queried within the last 15
7141 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
7143 o Minor bugfixes (correctness):
7144 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7145 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7147 o Minor bugfixes (coverity build support):
7148 - Avoid Coverity build warnings related to our BUG() macro. By
7149 default, Coverity treats BUG() as the Linux kernel does: an
7150 instant abort(). We need to override that so our BUG() macro
7151 doesn't prevent Coverity from analyzing functions that use it.
7152 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7154 o Minor bugfixes (defensive programming):
7155 - Detect and break out of infinite loops in our compression code. We
7156 don't think that any such loops exist now, but it's best to be
7157 safe. Closes ticket 22672.
7158 - Fix a memset() off the end of an array when packing cells. This
7159 bug should be harmless in practice, since the corrupted bytes are
7160 still in the same structure, and are always padding bytes,
7161 ignored, or immediately overwritten, depending on compiler
7162 behavior. Nevertheless, because the memset()'s purpose is to make
7163 sure that any other cell-handling bugs can't expose bytes to the
7164 network, we need to fix it. Fixes bug 22737; bugfix on
7165 0.2.4.11-alpha. Fixes CID 1401591.
7167 o Minor bugfixes (directory authority):
7168 - When a directory authority rejects a descriptor or extrainfo with
7169 a given digest, mark that digest as undownloadable, so that we do
7170 not attempt to download it again over and over. We previously
7171 tried to avoid downloading such descriptors by other means, but we
7172 didn't notice if we accidentally downloaded one anyway. This
7173 behavior became problematic in 0.2.7.2-alpha, when authorities
7174 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7176 - When rejecting a router descriptor for running an obsolete version
7177 of Tor without ntor support, warn about the obsolete tor version,
7178 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
7179 - Prevent the shared randomness subsystem from asserting when
7180 initialized by a bridge authority with an incomplete configuration
7181 file. Fixes bug 21586; bugfix on 0.2.9.8.
7183 o Minor bugfixes (error reporting, windows):
7184 - When formatting Windows error messages, use the English format to
7185 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
7188 o Minor bugfixes (exit-side DNS):
7189 - Fix an untriggerable assertion that checked the output of a
7190 libevent DNS error, so that the assertion actually behaves as
7191 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
7192 Karpov using PVS-Studio.
7194 o Minor bugfixes (fallback directories):
7195 - Make the usage example in updateFallbackDirs.py actually work, and
7196 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
7197 - Decrease the guard flag average required to be a fallback. This
7198 allows us to keep relays that have their guard flag removed when
7199 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
7200 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
7201 bugfix on 0.2.8.1-alpha.
7202 - Make sure fallback directory mirrors have the same address, port,
7203 and relay identity key for at least 30 days before they are
7204 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
7206 o Minor bugfixes (file limits, osx):
7207 - When setting the maximum number of connections allowed by the OS,
7208 always allow some extra file descriptors for other files. Fixes
7209 bug 22797; bugfix on 0.2.0.10-alpha.
7211 o Minor bugfixes (hidden services):
7212 - Increase the number of circuits that a service is allowed to
7213 open over a specific period of time. The value was lower than it
7214 should be (8 vs 12) in the normal case of 3 introduction points.
7215 Fixes bug 22159; bugfix on 0.3.0.5-rc.
7216 - Fix a BUG warning during HSv3 descriptor decoding that could be
7217 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
7218 on 0.3.0.1-alpha. Bug found by "haxxpop".
7219 - Stop printing a cryptic warning when a hidden service gets a
7220 request to connect to a virtual port that it hasn't configured.
7221 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
7222 - Simplify hidden service descriptor creation by using an existing
7223 flag to check if an introduction point is established. Fixes bug
7224 21599; bugfix on 0.2.7.2-alpha.
7226 o Minor bugfixes (link handshake):
7227 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
7228 months, and regenerate it when it is within one month of expiring.
7229 Previously, we had generated this certificate at startup with a
7230 ten-year lifetime, but that could lead to weird behavior when Tor
7231 was started with a grossly inaccurate clock. Mitigates bug 22466;
7232 mitigation on 0.3.0.1-alpha.
7234 o Minor bugfixes (linux seccomp2 sandbox):
7235 - Avoid a sandbox failure when trying to re-bind to a socket and
7236 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7237 - Permit the fchmod system call, to avoid crashing on startup when
7238 starting with the seccomp2 sandbox and an unexpected set of
7239 permissions on the data directory or its contents. Fixes bug
7240 22516; bugfix on 0.2.5.4-alpha.
7242 o Minor bugfixes (logging):
7243 - When decompressing, do not warn if we fail to decompress using a
7244 compression method that we merely guessed. Fixes part of bug
7245 22670; bugfix on 0.1.1.14-alpha.
7246 - When decompressing, treat mismatch between content-encoding and
7247 actual compression type as a protocol warning. Fixes part of bug
7248 22670; bugfix on 0.1.1.9-alpha.
7249 - Downgrade "assigned_to_cpuworker failed" message to info-level
7250 severity. In every case that can reach it, either a better warning
7251 has already been logged, or no warning is warranted. Fixes bug
7252 22356; bugfix on 0.2.6.3-alpha.
7253 - Log a better message when a directory authority replies to an
7254 upload with an unexpected status code. Fixes bug 11121; bugfix
7256 - Downgrade a log statement about unexpected relay cells from "bug"
7257 to "protocol warning", because there is at least one use case
7258 where it can be triggered by a buggy tor implementation. Fixes bug
7259 21293; bugfix on 0.1.1.14-alpha.
7261 o Minor bugfixes (logging, relay):
7262 - Remove a forgotten debugging message when an introduction point
7263 successfully establishes a hidden service prop224 circuit with
7265 - Change three other log_warn() for an introduction point to
7266 protocol warnings, because they can be failure from the network
7267 and are not relevant to the operator. Fixes bug 23078; bugfix on
7268 0.3.0.1-alpha and 0.3.0.2-alpha.
7270 o Minor bugfixes (relay):
7271 - Inform the geoip and rephist modules about all requests, even on
7272 relays that are only fetching microdescriptors. Fixes a bug
7273 related to 21585; bugfix on 0.3.0.1-alpha.
7275 o Minor bugfixes (memory leaks):
7276 - Fix a small memory leak at exit from the backtrace handler code.
7277 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
7278 - When directory authorities reject a router descriptor due to
7279 keypinning, free the router descriptor rather than leaking the
7280 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7281 - Fix a small memory leak when validating a configuration that uses
7282 two or more AF_UNIX sockets for the same port type. Fixes bug
7283 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
7285 o Minor bugfixes (process behavior):
7286 - When exiting because of an error, always exit with a nonzero exit
7287 status. Previously, we would fail to report an error in our exit
7288 status in cases related to __OwningControllerProcess failure,
7289 lockfile contention, and Ed25519 key initialization. Fixes bug
7290 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
7291 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
7294 o Minor bugfixes (robustness, error handling):
7295 - Improve our handling of the cases where OpenSSL encounters a
7296 memory error while encoding keys and certificates. We haven't
7297 observed these errors in the wild, but if they do happen, we now
7298 detect and respond better. Fixes bug 19418; bugfix on all versions
7299 of Tor. Reported by Guido Vranken.
7301 o Minor bugfixes (testing):
7302 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
7303 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
7304 - Use unbuffered I/O for utility functions around the
7305 process_handle_t type. This fixes unit test failures reported on
7306 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
7307 - Make display of captured unit test log messages consistent. Fixes
7308 bug 21510; bugfix on 0.2.9.3-alpha.
7309 - Make test-network.sh always call chutney's test-network.sh.
7310 Previously, this only worked on systems which had bash installed,
7311 due to some bash-specific code in the script. Fixes bug 19699;
7312 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
7313 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
7314 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
7315 - The unit tests now pass on systems where localhost is misconfigured
7316 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
7319 o Minor bugfixes (voting consistency):
7320 - Reject version numbers with non-numeric prefixes (such as +, -, or
7321 whitespace). Disallowing whitespace prevents differential version
7322 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7323 and part of 21508; bugfix on 0.0.8pre1.
7325 o Minor bugfixes (Windows service):
7326 - When running as a Windows service, set the ID of the main thread
7327 correctly. Failure to do so made us fail to send log messages to
7328 the controller in 0.2.1.16-rc, slowed down controller event
7329 delivery in 0.2.7.3-rc and later, and crash with an assertion
7330 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7331 Patch and diagnosis from "Vort".
7333 o Minor bugfixes (windows, relay):
7334 - Resolve "Failure from drain_fd: No error" warnings on Windows
7335 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
7337 o Code simplification and refactoring:
7338 - Break up the 630-line function connection_dir_client_reached_eof()
7339 into a dozen smaller functions. This change should help
7340 maintainability and readability of the client directory code.
7341 - Isolate our use of the openssl headers so that they are only
7342 included from our crypto wrapper modules, and from tests that
7343 examine those modules' internals. Closes ticket 21841.
7344 - Simplify our API to launch directory requests, making it more
7345 extensible and less error-prone. Now it's easier to add extra
7346 headers to directory requests. Closes ticket 21646.
7347 - Our base64 decoding functions no longer overestimate the output
7348 space that they need when parsing unpadded inputs. Closes
7350 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
7351 Resolves ticket 22213.
7352 - The logic that directory caches use to spool request to clients,
7353 serving them one part at a time so as not to allocate too much
7354 memory, has been refactored for consistency. Previously there was
7355 a separate spooling implementation per type of spoolable data. Now
7356 there is one common spooling implementation, with extensible data
7357 types. Closes ticket 21651.
7358 - Tor's compression module now supports multiple backends. Part of
7359 the implementation for proposal 278; closes ticket 21663.
7362 - Add a manpage description for the key-pinning-journal file. Closes
7364 - Correctly note that bandwidth accounting values are stored in the
7365 state file, and the bw_accounting file is now obsolete. Closes
7367 - Document more of the files in the Tor data directory, including
7368 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
7369 approved-routers, sr-random, and diff-cache. Found while fixing
7371 - Clarify the manpage for the (deprecated) torify script. Closes
7373 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
7374 Closes ticket 21873.
7375 - Correct documentation about the default DataDirectory value.
7376 Closes ticket 21151.
7377 - Document the default behavior of NumEntryGuards and
7378 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
7380 - Document key=value pluggable transport arguments for Bridge lines
7381 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
7382 - Note that bandwidth-limiting options don't affect TCP headers or
7383 DNS. Closes ticket 17170.
7385 o Removed features (configuration options, all in ticket 22060):
7386 - These configuration options are now marked Obsolete, and no longer
7387 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
7388 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
7389 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
7390 in 0.2.9.2-alpha and have now been removed. The previous default
7391 behavior is now always chosen; the previous (less secure) non-
7392 default behavior is now unavailable.
7393 - CloseHSClientCircuitsImmediatelyOnTimeout and
7394 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
7395 0.2.9.2-alpha and now have been removed. HS circuits never close
7396 on circuit build timeout; they have a longer timeout period.
7397 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
7398 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
7399 (and others) to configure listen-only and advertise-only addresses.
7401 o Removed features (tools):
7402 - We've removed the tor-checkkey tool from src/tools. Long ago, we
7403 used it to help people detect RSA keys that were generated by
7404 versions of Debian affected by CVE-2008-0166. But those keys have
7405 been out of circulation for ages, and this tool is no longer
7406 required. Closes ticket 21842.
7409 Changes in version 0.3.0.10 - 2017-08-02
7410 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
7411 from the current Tor alpha series. OpenBSD users and TPROXY users
7412 should upgrade; others are probably okay sticking with 0.3.0.9.
7414 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
7415 - Tor's repository now includes a Travis Continuous Integration (CI)
7416 configuration file (.travis.yml). This is meant to help new
7417 developers and contributors who fork Tor to a Github repository be
7418 better able to test their changes, and understand what we expect
7419 to pass. To use this new build feature, you must fork Tor to your
7420 Github account, then go into the "Integrations" menu in the
7421 repository settings for your fork and enable Travis, then push
7422 your changes. Closes ticket 22636.
7424 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7425 - Fix a typo that had prevented TPROXY-based transparent proxying
7426 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7427 Patch from "d4fq0fQAgoJ".
7429 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7430 - Avoid an assertion failure bug affecting our implementation of
7431 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7432 handling of "0xbar" differs from what we had expected. Fixes bug
7433 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7435 o Minor features (backport from 0.3.1.5-alpha):
7436 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
7439 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
7440 - Roll over monthly accounting at the configured hour and minute,
7441 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7442 Found by Andrey Karpov with PVS-Studio.
7444 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
7445 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7446 bugfix on 0.2.8.1-alpha.
7447 - Fix warnings when building with libscrypt and openssl scrypt
7448 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7449 - When building with certain versions of the mingw C header files,
7450 avoid float-conversion warnings when calling the C functions
7451 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
7454 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7455 - Backport a fix for an "unused variable" warning that appeared
7456 in some versions of mingw. Fixes bug 22838; bugfix on
7459 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
7460 - Avoid Coverity build warnings related to our BUG() macro. By
7461 default, Coverity treats BUG() as the Linux kernel does: an
7462 instant abort(). We need to override that so our BUG() macro
7463 doesn't prevent Coverity from analyzing functions that use it.
7464 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7466 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
7467 - When rejecting a router descriptor for running an obsolete version
7468 of Tor without ntor support, warn about the obsolete tor version,
7469 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
7471 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
7472 - Avoid a sandbox failure when trying to re-bind to a socket and
7473 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7475 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
7476 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
7477 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
7480 Changes in version 0.3.0.9 - 2017-06-29
7481 Tor 0.3.0.9 fixes a path selection bug that would allow a client
7482 to use a guard that was in the same network family as a chosen exit
7483 relay. This is a security regression; all clients running earlier
7484 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
7487 This release also backports several other bugfixes from the 0.3.1.x
7490 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
7491 - When choosing which guard to use for a circuit, avoid the exit's
7492 family along with the exit itself. Previously, the new guard
7493 selection logic avoided the exit, but did not consider its family.
7494 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
7495 006 and CVE-2017-0377.
7497 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
7498 - Don't block bootstrapping when a primary bridge is offline and we
7499 can't get its descriptor. Fixes bug 22325; fixes one case of bug
7500 21969; bugfix on 0.3.0.3-alpha.
7502 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
7503 - When starting with an old consensus, do not add new entry guards
7504 unless the consensus is "reasonably live" (under 1 day old). Fixes
7505 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
7507 o Minor features (geoip):
7508 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
7511 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
7512 - Reject version numbers with non-numeric prefixes (such as +, -, or
7513 whitespace). Disallowing whitespace prevents differential version
7514 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7515 and part of 21508; bugfix on 0.0.8pre1.
7517 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
7518 - Permit the fchmod system call, to avoid crashing on startup when
7519 starting with the seccomp2 sandbox and an unexpected set of
7520 permissions on the data directory or its contents. Fixes bug
7521 22516; bugfix on 0.2.5.4-alpha.
7523 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
7524 - Fix a memset() off the end of an array when packing cells. This
7525 bug should be harmless in practice, since the corrupted bytes are
7526 still in the same structure, and are always padding bytes,
7527 ignored, or immediately overwritten, depending on compiler
7528 behavior. Nevertheless, because the memset()'s purpose is to make
7529 sure that any other cell-handling bugs can't expose bytes to the
7530 network, we need to fix it. Fixes bug 22737; bugfix on
7531 0.2.4.11-alpha. Fixes CID 1401591.
7534 Changes in version 0.3.0.8 - 2017-06-08
7535 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
7536 remotely crash a hidden service with an assertion failure. Anyone
7537 running a hidden service should upgrade to this version, or to some
7538 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
7540 Tor 0.3.0.8 also includes fixes for several key management bugs
7541 that sometimes made relays unreliable, as well as several other
7542 bugfixes described below.
7544 o Major bugfixes (hidden service, relay, security, backport
7545 from 0.3.1.3-alpha):
7546 - Fix a remotely triggerable assertion failure when a hidden service
7547 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
7548 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
7549 - Fix a remotely triggerable assertion failure caused by receiving a
7550 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7551 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7554 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
7555 - When performing the v3 link handshake on a TLS connection, report
7556 that we have the x509 certificate that we actually used on that
7557 connection, even if we have changed certificates since that
7558 connection was first opened. Previously, we would claim to have
7559 used our most recent x509 link certificate, which would sometimes
7560 make the link handshake fail. Fixes one case of bug 22460; bugfix
7563 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
7564 - Regenerate link and authentication certificates whenever the key
7565 that signs them changes; also, regenerate link certificates
7566 whenever the signed key changes. Previously, these processes were
7567 only weakly coupled, and we relays could (for minutes to hours)
7568 wind up with an inconsistent set of keys and certificates, which
7569 other relays would not accept. Fixes two cases of bug 22460;
7570 bugfix on 0.3.0.1-alpha.
7571 - When sending an Ed25519 signing->link certificate in a CERTS cell,
7572 send the certificate that matches the x509 certificate that we
7573 used on the TLS connection. Previously, there was a race condition
7574 if the TLS context rotated after we began the TLS handshake but
7575 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
7578 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
7579 - Stop rejecting v3 hidden service descriptors because their size
7580 did not match an old padding rule. Fixes bug 22447; bugfix on
7583 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7584 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7585 December 2016 (of which ~126 were still functional) with a list of
7586 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7587 2017. Resolves ticket 21564.
7589 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
7590 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
7591 bug 22252; bugfix on 0.2.9.3-alpha.
7593 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
7594 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7595 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7597 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
7598 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
7599 months, and regenerate it when it is within one month of expiring.
7600 Previously, we had generated this certificate at startup with a
7601 ten-year lifetime, but that could lead to weird behavior when Tor
7602 was started with a grossly inaccurate clock. Mitigates bug 22466;
7603 mitigation on 0.3.0.1-alpha.
7605 o Minor bugfixes (memory leak, directory authority, backport from
7607 - When directory authorities reject a router descriptor due to
7608 keypinning, free the router descriptor rather than leaking the
7609 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7612 Changes in version 0.2.9.11 - 2017-06-08
7613 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
7614 remotely crash a hidden service with an assertion failure. Anyone
7615 running a hidden service should upgrade to this version, or to some
7616 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7617 are not affected by TROVE-2017-004.)
7619 Tor 0.2.9.11 also backports fixes for several key management bugs
7620 that sometimes made relays unreliable, as well as several other
7621 bugfixes described below.
7623 o Major bugfixes (hidden service, relay, security, backport
7624 from 0.3.1.3-alpha):
7625 - Fix a remotely triggerable assertion failure caused by receiving a
7626 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7627 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7630 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
7631 - When performing the v3 link handshake on a TLS connection, report
7632 that we have the x509 certificate that we actually used on that
7633 connection, even if we have changed certificates since that
7634 connection was first opened. Previously, we would claim to have
7635 used our most recent x509 link certificate, which would sometimes
7636 make the link handshake fail. Fixes one case of bug 22460; bugfix
7639 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7640 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7641 December 2016 (of which ~126 were still functional) with a list of
7642 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7643 2017. Resolves ticket 21564.
7645 o Minor features (future-proofing, backport from 0.3.0.7):
7646 - Tor no longer refuses to download microdescriptors or descriptors if
7647 they are listed as "published in the future". This change will
7648 eventually allow us to stop listing meaningful "published" dates
7649 in microdescriptor consensuses, and thereby allow us to reduce the
7650 resources required to download consensus diffs by over 50%.
7651 Implements part of ticket 21642; implements part of proposal 275.
7653 o Minor features (directory authorities, backport from 0.3.0.4-rc)
7654 - Directory authorities now reject relays running versions
7655 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
7656 suffer from bug 20499 and don't keep their consensus cache
7657 up-to-date. Resolves ticket 20509.
7659 o Minor features (geoip):
7660 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7663 o Minor bugfixes (control port, backport from 0.3.0.6):
7664 - The GETINFO extra-info/digest/<digest> command was broken because
7665 of a wrong base16 decode return value check, introduced when
7666 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
7668 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
7669 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7670 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7672 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
7673 - The getpid() system call is now permitted under the Linux seccomp2
7674 sandbox, to avoid crashing with versions of OpenSSL (and other
7675 libraries) that attempt to learn the process's PID by using the
7676 syscall rather than the VDSO code. Fixes bug 21943; bugfix
7679 o Minor bugfixes (memory leak, directory authority, backport
7680 from 0.3.1.2-alpha):
7681 - When directory authorities reject a router descriptor due to
7682 keypinning, free the router descriptor rather than leaking the
7683 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
7685 Changes in version 0.2.8.14 - 2017-06-08
7686 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
7687 remotely crash a hidden service with an assertion failure. Anyone
7688 running a hidden service should upgrade to this version, or to some
7689 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7690 are not affected by TROVE-2017-004.)
7692 o Major bugfixes (hidden service, relay, security):
7693 - Fix a remotely triggerable assertion failure caused by receiving a
7694 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7695 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7698 o Minor features (geoip):
7699 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7702 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
7703 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
7704 December 2016 (of which ~126 were still functional) with a list of
7705 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
7706 2017. Resolves ticket 21564.
7708 o Minor bugfixes (correctness):
7709 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7710 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7712 Changes in version 0.2.7.8 - 2017-06-08
7713 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
7714 remotely crash a hidden service with an assertion failure. Anyone
7715 running a hidden service should upgrade to this version, or to some
7716 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7717 are not affected by TROVE-2017-004.)
7719 o Major bugfixes (hidden service, relay, security):
7720 - Fix a remotely triggerable assertion failure caused by receiving a
7721 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7722 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7725 o Minor features (geoip):
7726 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7729 o Minor bugfixes (correctness):
7730 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7731 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7734 Changes in version 0.2.6.12 - 2017-06-08
7735 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
7736 remotely crash a hidden service with an assertion failure. Anyone
7737 running a hidden service should upgrade to this version, or to some
7738 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7739 are not affected by TROVE-2017-004.)
7741 o Major bugfixes (hidden service, relay, security):
7742 - Fix a remotely triggerable assertion failure caused by receiving a
7743 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7744 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7747 o Minor features (geoip):
7748 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7751 o Minor bugfixes (correctness):
7752 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7753 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7755 Changes in version 0.2.5.14 - 2017-06-08
7756 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
7757 remotely crash a hidden service with an assertion failure. Anyone
7758 running a hidden service should upgrade to this version, or to some
7759 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7760 are not affected by TROVE-2017-004.)
7762 o Major bugfixes (hidden service, relay, security):
7763 - Fix a remotely triggerable assertion failure caused by receiving a
7764 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7765 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7768 o Minor features (geoip):
7769 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7772 o Minor bugfixes (correctness):
7773 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7774 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7776 Changes in version 0.2.4.29 - 2017-06-08
7777 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
7778 remotely crash a hidden service with an assertion failure. Anyone
7779 running a hidden service should upgrade to this version, or to some
7780 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
7781 are not affected by TROVE-2017-004.)
7783 o Major bugfixes (hidden service, relay, security):
7784 - Fix a remotely triggerable assertion failure caused by receiving a
7785 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
7786 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
7789 o Minor features (geoip):
7790 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7793 o Minor bugfixes (correctness):
7794 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
7795 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
7798 Changes in version 0.3.0.7 - 2017-05-15
7799 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
7800 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
7801 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
7802 clients are not affected.
7804 o Major bugfixes (hidden service directory, security):
7805 - Fix an assertion failure in the hidden service directory code, which
7806 could be used by an attacker to remotely cause a Tor relay process to
7807 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
7808 should upgrade. This security issue is tracked as TROVE-2017-002.
7809 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
7812 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
7815 o Minor features (future-proofing):
7816 - Tor no longer refuses to download microdescriptors or descriptors
7817 if they are listed as "published in the future". This change will
7818 eventually allow us to stop listing meaningful "published" dates
7819 in microdescriptor consensuses, and thereby allow us to reduce the
7820 resources required to download consensus diffs by over 50%.
7821 Implements part of ticket 21642; implements part of proposal 275.
7823 o Minor bugfixes (Linux seccomp2 sandbox):
7824 - The getpid() system call is now permitted under the Linux seccomp2
7825 sandbox, to avoid crashing with versions of OpenSSL (and other
7826 libraries) that attempt to learn the process's PID by using the
7827 syscall rather than the VDSO code. Fixes bug 21943; bugfix
7831 Changes in version 0.3.0.6 - 2017-04-26
7832 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
7834 With the 0.3.0 series, clients and relays now use Ed25519 keys to
7835 authenticate their link connections to relays, rather than the old
7836 RSA1024 keys that they used before. (Circuit crypto has been
7837 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
7838 the guard selection and replacement algorithm to behave more robustly
7839 in the presence of unreliable networks, and to resist guard-
7842 This series also includes numerous other small features and bugfixes,
7843 along with more groundwork for the upcoming hidden-services revamp.
7845 Per our stable release policy, we plan to support the Tor 0.3.0
7846 release series for at least the next nine months, or for three months
7847 after the first stable release of the 0.3.1 series: whichever is
7848 longer. If you need a release with long-term support, we recommend
7849 that you stay with the 0.2.9 series.
7851 Below are the changes since 0.2.9.10. For a list of only the changes
7852 since 0.3.0.5-rc, see the ChangeLog file.
7854 o Major features (directory authority, security):
7855 - The default for AuthDirPinKeys is now 1: directory authorities
7856 will reject relays where the RSA identity key matches a previously
7857 seen value, but the Ed25519 key has changed. Closes ticket 18319.
7859 o Major features (guard selection algorithm):
7860 - Tor's guard selection algorithm has been redesigned from the
7861 ground up, to better support unreliable networks and restrictive
7862 sets of entry nodes, and to better resist guard-capture attacks by
7863 hostile local networks. Implements proposal 271; closes
7866 o Major features (next-generation hidden services):
7867 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
7868 prop224 aka "Next Generation Hidden Services". Service and clients
7869 don't use this functionality yet. Closes ticket 19043. Based on
7870 initial code by Alec Heifetz.
7871 - Relays now support the HSDir version 3 protocol, so that they can
7872 can store and serve v3 descriptors. This is part of the next-
7873 generation onion service work detailed in proposal 224. Closes
7876 o Major features (protocol, ed25519 identity keys):
7877 - Clients now support including Ed25519 identity keys in the EXTEND2
7878 cells they generate. By default, this is controlled by a consensus
7879 parameter, currently disabled. You can turn this feature on for
7880 testing by setting ExtendByEd25519ID in your configuration. This
7881 might make your traffic appear different than the traffic
7882 generated by other users, however. Implements part of ticket
7883 15056; part of proposal 220.
7884 - Relays now understand requests to extend to other relays by their
7885 Ed25519 identity keys. When an Ed25519 identity key is included in
7886 an EXTEND2 cell, the relay will only extend the circuit if the
7887 other relay can prove ownership of that identity. Implements part
7888 of ticket 15056; part of proposal 220.
7889 - Relays now use Ed25519 to prove their Ed25519 identities and to
7890 one another, and to clients. This algorithm is faster and more
7891 secure than the RSA-based handshake we've been doing until now.
7892 Implements the second big part of proposal 220; Closes
7895 o Major features (security):
7896 - Change the algorithm used to decide DNS TTLs on client and server
7897 side, to better resist DNS-based correlation attacks like the
7898 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
7899 Feamster. Now relays only return one of two possible DNS TTL
7900 values, and clients are willing to believe DNS TTL values up to 3
7901 hours long. Closes ticket 19769.
7903 o Major bugfixes (client, onion service, also in 0.2.9.9):
7904 - Fix a client-side onion service reachability bug, where multiple
7905 socks requests to an onion service (or a single slow request)
7906 could cause us to mistakenly mark some of the service's
7907 introduction points as failed, and we cache that failure so
7908 eventually we run out and can't reach the service. Also resolves a
7909 mysterious "Remote server sent bogus reason code 65021" log
7910 warning. The bug was introduced in ticket 17218, where we tried to
7911 remember the circuit end reason as a uint16_t, which mangled
7912 negative values. Partially fixes bug 21056 and fixes bug 20307;
7913 bugfix on 0.2.8.1-alpha.
7915 o Major bugfixes (crash, directory connections):
7916 - Fix a rare crash when sending a begin cell on a circuit whose
7917 linked directory connection had already been closed. Fixes bug
7918 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
7920 o Major bugfixes (directory authority):
7921 - During voting, when marking a relay as a probable sybil, do not
7922 clear its BadExit flag: sybils can still be bad in other ways
7923 too. (We still clear the other flags.) Fixes bug 21108; bugfix
7926 o Major bugfixes (DNS):
7927 - Fix a bug that prevented exit nodes from caching DNS records for
7928 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7930 o Major bugfixes (IPv6 Exits):
7931 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
7932 any IPv6 addresses. Instead, only reject a port over IPv6 if the
7933 exit policy rejects that port on more than an IPv6 /16 of
7934 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
7935 which rejected a relay's own IPv6 address by default. Fixes bug
7936 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
7938 o Major bugfixes (parsing):
7939 - Fix an integer underflow bug when comparing malformed Tor
7940 versions. This bug could crash Tor when built with
7941 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
7942 0.2.9.8, which were built with -ftrapv by default. In other cases
7943 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
7944 on 0.0.8pre1. Found by OSS-Fuzz.
7945 - When parsing a malformed content-length field from an HTTP
7946 message, do not read off the end of the buffer. This bug was a
7947 potential remote denial-of-service attack against Tor clients and
7948 relays. A workaround was released in October 2016, to prevent this
7949 bug from crashing Tor. This is a fix for the underlying issue,
7950 which should no longer matter (if you applied the earlier patch).
7951 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
7952 using AFL (http://lcamtuf.coredump.cx/afl/).
7954 o Major bugfixes (scheduler):
7955 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
7956 caused the channel scheduler to behave more or less randomly,
7957 rather than preferring channels with higher-priority circuits.
7958 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
7960 o Major bugfixes (security, also in 0.2.9.9):
7961 - Downgrade the "-ftrapv" option from "always on" to "only on when
7962 --enable-expensive-hardening is provided." This hardening option,
7963 like others, can turn survivable bugs into crashes--and having it
7964 on by default made a (relatively harmless) integer overflow bug
7965 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
7966 bugfix on 0.2.9.1-alpha.
7968 o Minor feature (client):
7969 - Enable IPv6 traffic on the SocksPort by default. To disable this,
7970 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
7972 o Minor feature (fallback scripts):
7973 - Add a check_existing mode to updateFallbackDirs.py, which checks
7974 if fallbacks in the hard-coded list are working. Closes ticket
7975 20174. Patch by haxxpop.
7977 o Minor feature (protocol versioning):
7978 - Add new protocol version for proposal 224. HSIntro now advertises
7979 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
7981 o Minor features (ciphersuite selection):
7982 - Allow relays to accept a wider range of ciphersuites, including
7983 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
7984 - Clients now advertise a list of ciphersuites closer to the ones
7985 preferred by Firefox. Closes part of ticket 15426.
7987 o Minor features (controller):
7988 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
7989 shared-random values to the controller. Closes ticket 19925.
7990 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
7991 rather than "unrecognized." Closes ticket 20389; patch from
7994 o Minor features (controller, configuration):
7995 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
7996 and so on, now comes with a __*Port variant that will not be saved
7997 to the torrc file by the controller's SAVECONF command. This
7998 change allows TorBrowser to set up a single-use domain socket for
7999 each time it launches Tor. Closes ticket 20956.
8000 - The GETCONF command can now query options that may only be
8001 meaningful in context-sensitive lists. This allows the controller
8002 to query the mixed SocksPort/__SocksPort style options introduced
8003 in feature 20956. Implements ticket 21300.
8005 o Minor features (diagnostic, directory client):
8006 - Warn when we find an unexpected inconsistency in directory
8007 download status objects. Prevents some negative consequences of
8010 o Minor features (directory authorities):
8011 - Directory authorities now reject descriptors that claim to be
8012 malformed versions of Tor. Helps prevent exploitation of
8014 - Reject version numbers with components that exceed INT32_MAX.
8015 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
8016 Fixes bug 21450; bugfix on 0.0.8pre1.
8018 o Minor features (directory authority):
8019 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
8020 default) to control whether authorities should try to probe relays
8021 by their Ed25519 link keys. This option will go away in a few
8022 releases--unless we encounter major trouble in our ed25519 link
8023 protocol rollout, in which case it will serve as a safety option.
8025 o Minor features (directory cache):
8026 - Relays and bridges will now refuse to serve the consensus they
8027 have if they know it is too old for a client to use. Closes
8030 o Minor features (ed25519 link handshake):
8031 - Advertise support for the ed25519 link handshake using the
8032 subprotocol-versions mechanism, so that clients can tell which
8033 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
8035 o Minor features (entry guards):
8036 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
8037 break regression tests.
8038 - Require UseEntryGuards when UseBridges is set, in order to make
8039 sure bridges aren't bypassed. Resolves ticket 20502.
8041 o Minor features (fallback directories):
8042 - Allow 3 fallback relays per operator, which is safe now that we
8043 are choosing 200 fallback relays. Closes ticket 20912.
8044 - Annotate updateFallbackDirs.py with the bandwidth and consensus
8045 weight for each candidate fallback. Closes ticket 20878.
8046 - Display the relay fingerprint when downloading consensuses from
8047 fallbacks. Closes ticket 20908.
8048 - Exclude relays affected by bug 20499 from the fallback list.
8049 Exclude relays from the fallback list if they are running versions
8050 known to be affected by bug 20499, or if in our tests they deliver
8051 a stale consensus (i.e. one that expired more than 24 hours ago).
8052 Closes ticket 20539.
8053 - Make it easier to change the output sort order of fallbacks.
8054 Closes ticket 20822.
8055 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
8057 - Require fallback directories to have the same address and port for
8058 7 days (now that we have enough relays with this stability).
8059 Relays whose OnionOO stability timer is reset on restart by bug
8060 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
8061 this issue. Closes ticket 20880; maintains short-term fix
8063 - Require fallbacks to have flags for 90% of the time (weighted
8064 decaying average), rather than 95%. This allows at least 73% of
8065 clients to bootstrap in the first 5 seconds without contacting an
8066 authority. Part of ticket 18828.
8067 - Select 200 fallback directories for each release. Closes
8070 o Minor features (fingerprinting resistance, authentication):
8071 - Extend the length of RSA keys used for TLS link authentication to
8072 2048 bits. (These weren't used for forward secrecy; for forward
8073 secrecy, we used P256.) Closes ticket 13752.
8075 o Minor features (geoip):
8076 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
8079 o Minor features (geoip, also in 0.2.9.9):
8080 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
8083 o Minor features (infrastructure):
8084 - Implement smartlist_add_strdup() function. Replaces the use of
8085 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
8087 o Minor features (linting):
8088 - Enhance the changes file linter to warn on Tor versions that are
8089 prefixed with "tor-". Closes ticket 21096.
8091 o Minor features (logging):
8092 - In several places, describe unset ed25519 keys as "<unset>",
8093 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
8095 o Minor features (portability, compilation):
8096 - Autoconf now checks to determine if OpenSSL structures are opaque,
8097 instead of explicitly checking for OpenSSL version numbers. Part
8099 - Support building with recent LibreSSL code that uses opaque
8100 structures. Closes ticket 21359.
8102 o Minor features (relay):
8103 - We now allow separation of exit and relay traffic to different
8104 source IP addresses, using the OutboundBindAddressExit and
8105 OutboundBindAddressOR options respectively. Closes ticket 17975.
8106 Written by Michael Sonntag.
8108 o Minor features (reliability, crash):
8109 - Try better to detect problems in buffers where they might grow (or
8110 think they have grown) over 2 GB in size. Diagnostic for
8113 o Minor features (testing):
8114 - During 'make test-network-all', if tor logs any warnings, ask
8115 chutney to output them. Requires a recent version of chutney with
8116 the 21572 patch. Implements 21570.
8118 o Minor bugfix (control protocol):
8119 - The reply to a "GETINFO config/names" request via the control
8120 protocol now spells the type "Dependent" correctly. This is a
8121 breaking change in the control protocol. (The field seems to be
8122 ignored by the most common known controllers.) Fixes bug 18146;
8123 bugfix on 0.1.1.4-alpha.
8124 - The GETINFO extra-info/digest/<digest> command was broken because
8125 of a wrong base16 decode return value check, introduced when
8126 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8128 o Minor bugfix (logging):
8129 - Don't recommend the use of Tor2web in non-anonymous mode.
8130 Recommending Tor2web is a bad idea because the client loses all
8131 anonymity. Tor2web should only be used in specific cases by users
8132 who *know* and understand the issues. Fixes bug 21294; bugfix
8135 o Minor bugfixes (bug resilience):
8136 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
8137 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
8138 Hans Jerry Illikainen.
8140 o Minor bugfixes (build):
8141 - Replace obsolete Autoconf macros with their modern equivalent and
8142 prevent similar issues in the future. Fixes bug 20990; bugfix
8145 o Minor bugfixes (certificate expiration time):
8146 - Avoid using link certificates that don't become valid till some
8147 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
8149 o Minor bugfixes (client):
8150 - Always recover from failures in extend_info_from_node(), in an
8151 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
8152 bugfix on 0.2.3.1-alpha.
8153 - When clients that use bridges start up with a cached consensus on
8154 disk, they were ignoring it and downloading a new one. Now they
8155 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
8157 o Minor bugfixes (code correctness):
8158 - Repair a couple of (unreachable or harmless) cases of the risky
8159 comparison-by-subtraction pattern that caused bug 21278.
8161 o Minor bugfixes (config):
8162 - Don't assert on startup when trying to get the options list and
8163 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
8164 options so of course they aren't ready yet. Fixes bug 21062;
8165 bugfix on 0.2.9.3-alpha.
8167 o Minor bugfixes (configuration):
8168 - Accept non-space whitespace characters after the severity level in
8169 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
8170 - Support "TByte" and "TBytes" units in options given in bytes.
8171 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
8172 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
8174 o Minor bugfixes (configure, autoconf):
8175 - Rename the configure option --enable-expensive-hardening to
8176 --enable-fragile-hardening. Expensive hardening makes the tor
8177 daemon abort when some kinds of issues are detected. Thus, it
8178 makes tor more at risk of remote crashes but safer against RCE or
8179 heartbleed bug category. We now try to explain this issue in a
8180 message from the configure script. Fixes bug 21290; bugfix
8183 o Minor bugfixes (consensus weight):
8184 - Add new consensus method that initializes bw weights to 1 instead
8185 of 0. This prevents a zero weight from making it all the way to
8186 the end (happens in small testing networks) and causing an error.
8187 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
8189 o Minor bugfixes (crash prevention):
8190 - Fix an (currently untriggerable, but potentially dangerous) crash
8191 bug when base32-encoding inputs whose sizes are not a multiple of
8192 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
8194 o Minor bugfixes (dead code):
8195 - Remove a redundant check for PidFile changes at runtime in
8196 options_transition_allowed(): this check is already performed
8197 regardless of whether the sandbox is active. Fixes bug 21123;
8198 bugfix on 0.2.5.4-alpha.
8200 o Minor bugfixes (descriptors):
8201 - Correctly recognise downloaded full descriptors as valid, even
8202 when using microdescriptors as circuits. This affects clients with
8203 FetchUselessDescriptors set, and may affect directory authorities.
8204 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
8206 o Minor bugfixes (directory mirrors):
8207 - Allow relays to use directory mirrors without a DirPort: these
8208 relays need to be contacted over their ORPorts using a begindir
8209 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
8210 - Clarify the message logged when a remote relay is unexpectedly
8211 missing an ORPort or DirPort: users were confusing this with a
8212 local port. Fixes another case of bug 20711; bugfix
8215 o Minor bugfixes (directory system):
8216 - Bridges and relays now use microdescriptors (like clients do)
8217 rather than old-style router descriptors. Now bridges will blend
8218 in with clients in terms of the circuits they build. Fixes bug
8219 6769; bugfix on 0.2.3.2-alpha.
8220 - Download all consensus flavors, descriptors, and authority
8221 certificates when FetchUselessDescriptors is set, regardless of
8222 whether tor is a directory cache or not. Fixes bug 20667; bugfix
8223 on all recent tor versions.
8225 o Minor bugfixes (documentation):
8226 - Update the tor manual page to document every option that can not
8227 be changed while tor is running. Fixes bug 21122.
8229 o Minor bugfixes (ed25519 certificates):
8230 - Correctly interpret ed25519 certificates that would expire some
8231 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
8233 o Minor bugfixes (fallback directories):
8234 - Avoid checking fallback candidates' DirPorts if they are down in
8235 OnionOO. When a relay operator has multiple relays, this
8236 prioritizes relays that are up over relays that are down. Fixes
8237 bug 20926; bugfix on 0.2.8.3-alpha.
8238 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
8239 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
8240 - Stop failing when a relay has no uptime data in
8241 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
8243 o Minor bugfixes (hidden service):
8244 - Clean up the code for expiring intro points with no associated
8245 circuits. It was causing, rarely, a service with some expiring
8246 introduction points to not open enough additional introduction
8247 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
8248 - Resolve two possible underflows which could lead to creating and
8249 closing a lot of introduction point circuits in a non-stop loop.
8250 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
8251 - Stop setting the torrc option HiddenServiceStatistics to "0" just
8252 because we're not a bridge or relay. Instead, we preserve whatever
8253 value the user set (or didn't set). Fixes bug 21150; bugfix
8256 o Minor bugfixes (hidden services):
8257 - Make hidden services check for failed intro point connections,
8258 even when they have exceeded their intro point creation limit.
8259 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
8260 - Make hidden services with 8 to 10 introduction points check for
8261 failed circuits immediately after startup. Previously, they would
8262 wait for 5 minutes before performing their first checks. Fixes bug
8263 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
8264 - Stop ignoring misconfigured hidden services. Instead, refuse to
8265 start tor until the misconfigurations have been corrected. Fixes
8266 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
8269 o Minor bugfixes (IPv6):
8270 - Make IPv6-using clients try harder to find an IPv6 directory
8271 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
8272 - When IPv6 addresses have not been downloaded yet (microdesc
8273 consensus documents don't list relay IPv6 addresses), use hard-
8274 coded addresses for authorities, fallbacks, and configured
8275 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
8276 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
8278 o Minor bugfixes (memory leak at exit):
8279 - Fix a small harmless memory leak at exit of the previously unused
8280 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
8283 o Minor bugfixes (onion services):
8284 - Allow the number of introduction points to be as low as 0, rather
8285 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
8287 o Minor bugfixes (portability):
8288 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
8289 It is supported by OpenBSD itself, and also by most OpenBSD
8290 variants (such as Bitrig). Fixes bug 20980; bugfix
8293 o Minor bugfixes (portability, also in 0.2.9.9):
8294 - Avoid crashing when Tor is built using headers that contain
8295 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
8296 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
8298 - Fix Libevent detection on platforms without Libevent 1 headers
8299 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
8301 o Minor bugfixes (relay):
8302 - Avoid a double-marked-circuit warning that could happen when we
8303 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
8305 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
8306 initializing the keys would reset the DataDirectory to 0700
8307 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
8308 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
8310 o Minor bugfixes (testing):
8311 - Fix Raspbian build issues related to missing socket errno in
8312 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch by "hein".
8313 - Remove undefined behavior from the backtrace generator by removing
8314 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
8315 - Use bash in src/test/test-network.sh. This ensures we reliably
8316 call chutney's newer tools/test-network.sh when available. Fixes
8317 bug 21562; bugfix on 0.2.9.1-alpha.
8319 o Minor bugfixes (tor-resolve):
8320 - The tor-resolve command line tool now rejects hostnames over 255
8321 characters in length. Previously, it would silently truncate them,
8322 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
8323 Patch by "junglefowl".
8325 o Minor bugfixes (unit tests):
8326 - Allow the unit tests to pass even when DNS lookups of bogus
8327 addresses do not fail as expected. Fixes bug 20862 and 20863;
8328 bugfix on unit tests introduced in 0.2.8.1-alpha
8329 through 0.2.9.4-alpha.
8331 o Minor bugfixes (util):
8332 - When finishing writing a file to disk, if we were about to replace
8333 the file with the temporary file created before and we fail to
8334 replace it, remove the temporary file so it doesn't stay on disk.
8335 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
8337 o Minor bugfixes (Windows services):
8338 - Be sure to initialize the monotonic time subsystem before using
8339 it, even when running as an NT service. Fixes bug 21356; bugfix
8342 o Minor bugfixes (Windows):
8343 - Check for getpagesize before using it to mmap files. This fixes
8344 compilation in some MinGW environments. Fixes bug 20530; bugfix on
8345 0.1.2.1-alpha. Reported by "ice".
8347 o Code simplification and refactoring:
8348 - Abolish all global guard context in entrynodes.c; replace with new
8349 guard_selection_t structure as preparation for proposal 271.
8350 Closes ticket 19858.
8351 - Extract magic numbers in circuituse.c into defined variables.
8352 - Introduce rend_service_is_ephemeral() that tells if given onion
8353 service is ephemeral. Replace unclear NULL-checkings for service
8354 directory with this function. Closes ticket 20526.
8355 - Refactor circuit_is_available_for_use to remove unnecessary check.
8356 - Refactor circuit_predict_and_launch_new for readability and
8357 testability. Closes ticket 18873.
8358 - Refactor code to manipulate global_origin_circuit_list into
8359 separate functions. Closes ticket 20921.
8360 - Refactor large if statement in purpose_needs_anonymity to use
8361 switch statement instead. Closes part of ticket 20077.
8362 - Refactor the hashing API to return negative values for errors, as
8363 is done as throughout the codebase. Closes ticket 20717.
8364 - Remove data structures that were used to index or_connection
8365 objects by their RSA identity digests. These structures are fully
8366 redundant with the similar structures used in the
8367 channel abstraction.
8368 - Remove duplicate code in the channel_write_*cell() functions.
8369 Closes ticket 13827; patch from Pingl.
8370 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
8371 use only purpose_needs_anonymity. Closes part of ticket 20077.
8372 - The code to generate and parse EXTEND and EXTEND2 cells has been
8373 replaced with code automatically generated by the
8376 o Documentation (formatting):
8377 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
8378 blocks were incorrectly appearing. Closes ticket 20885.
8380 o Documentation (man page):
8381 - Clarify many options in tor.1 and add some min/max values for
8382 HiddenService options. Closes ticket 21058.
8385 - Change '1' to 'weight_scale' in consensus bw weights calculation
8386 comments, as that is reality. Closes ticket 20273. Patch
8388 - Clarify that when ClientRejectInternalAddresses is enabled (which
8389 is the default), multicast DNS hostnames for machines on the local
8390 network (of the form *.local) are also rejected. Closes
8392 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
8393 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix on 0.2.5.6-alpha.
8394 - Include the "TBits" unit in Tor's man page. Fixes part of bug
8395 20622; bugfix on 0.2.5.1-alpha.
8396 - Small fixes to the fuzzing documentation. Closes ticket 21472.
8397 - Stop the man page from incorrectly stating that HiddenServiceDir
8398 must already exist. Fixes 20486.
8399 - Update the description of the directory server options in the
8400 manual page, to clarify that a relay no longer needs to set
8401 DirPort in order to be a directory cache. Closes ticket 21720.
8404 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
8405 limit for relays running on a single IP applies to authority IP
8406 addresses as well as to non-authority IP addresses. Closes
8408 - The UseDirectoryGuards torrc option no longer exists: all users
8409 that use entry guards will also use directory guards. Related to
8410 proposal 271; implements part of ticket 20831.
8413 - Add tests for networkstatus_compute_bw_weights_v10.
8414 - Add unit tests circuit_predict_and_launch_new.
8415 - Extract dummy_origin_circuit_new so it can be used by other
8417 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
8418 from "overcaffeinated".
8419 - Perform the coding style checks when running the tests and fail
8420 when coding style violations are found. Closes ticket 5500.
8423 Changes in version 0.2.8.13 - 2017-03-03
8424 Tor 0.2.8.13 backports a security fix from later Tor
8425 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
8426 this release, if for some reason they cannot upgrade to a later
8427 release series, and if they build Tor with the --enable-expensive-hardening
8430 Note that support for Tor 0.2.8.x is ending next year: we will not issue
8431 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
8432 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8434 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8435 - Fix an integer underflow bug when comparing malformed Tor
8436 versions. This bug could crash Tor when built with
8437 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8438 0.2.9.8, which were built with -ftrapv by default. In other cases
8439 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8440 on 0.0.8pre1. Found by OSS-Fuzz.
8442 o Minor features (geoip):
8443 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8447 Changes in version 0.2.7.7 - 2017-03-03
8448 Tor 0.2.7.7 backports a number of security fixes from later Tor
8449 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
8450 this release, if for some reason they cannot upgrade to a later
8453 Note that support for Tor 0.2.7.x is ending this year: we will not issue
8454 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
8455 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8457 o Directory authority changes (backport from 0.2.8.5-rc):
8458 - Urras is no longer a directory authority. Closes ticket 19271.
8460 o Directory authority changes (backport from 0.2.9.2-alpha):
8461 - The "Tonga" bridge authority has been retired; the new bridge
8462 authority is "Bifroest". Closes tickets 19728 and 19690.
8464 o Directory authority key updates (backport from 0.2.8.1-alpha):
8465 - Update the V3 identity key for the dannenberg directory authority:
8466 it was changed on 18 November 2015. Closes task 17906. Patch
8469 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8470 - Fix a bug in parsing that could cause clients to read a single
8471 byte past the end of an allocated region. This bug could be used
8472 to cause hardened clients (built with --enable-expensive-hardening)
8473 to crash if they tried to visit a hostile hidden service. Non-
8474 hardened clients are only affected depending on the details of
8475 their platform's memory allocator. Fixes bug 21018; bugfix on
8476 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8477 2016-12-002 and as CVE-2016-1254.
8479 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8480 - Stop a crash that could occur when a client running with DNSPort
8481 received a query with multiple address types, and the first
8482 address type was not supported. Found and fixed by Scott Dial.
8483 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8484 - Prevent a class of security bugs caused by treating the contents
8485 of a buffer chunk as if they were a NUL-terminated string. At
8486 least one such bug seems to be present in all currently used
8487 versions of Tor, and would allow an attacker to remotely crash
8488 most Tor instances, especially those compiled with extra compiler
8489 hardening. With this defense in place, such bugs can't crash Tor,
8490 though we should still fix them as they occur. Closes ticket
8491 20384 (TROVE-2016-10-001).
8493 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8494 - Avoid a difficult-to-trigger heap corruption attack when extending
8495 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8496 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8497 Reported by Guido Vranken.
8499 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8500 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8501 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8503 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8504 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8505 pointer to the previous (uninitialized) key value. The impact here
8506 should be limited to a difficult-to-trigger crash, if OpenSSL is
8507 running an engine that makes key generation failures possible, or
8508 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8509 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8512 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8513 - Fix an integer underflow bug when comparing malformed Tor
8514 versions. This bug could crash Tor when built with
8515 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8516 0.2.9.8, which were built with -ftrapv by default. In other cases
8517 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8518 on 0.0.8pre1. Found by OSS-Fuzz.
8520 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8521 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8522 zero size. Check size argument to memwipe() for underflow. Fixes
8523 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8526 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8527 - Make Tor survive errors involving connections without a
8528 corresponding event object. Previously we'd fail with an
8529 assertion; now we produce a log message. Related to bug 16248.
8531 o Minor features (geoip):
8532 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8536 Changes in version 0.2.6.11 - 2017-03-03
8537 Tor 0.2.6.11 backports a number of security fixes from later Tor
8538 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
8539 this release, if for some reason they cannot upgrade to a later
8542 Note that support for Tor 0.2.6.x is ending this year: we will not issue
8543 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
8544 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8546 o Directory authority changes (backport from 0.2.8.5-rc):
8547 - Urras is no longer a directory authority. Closes ticket 19271.
8549 o Directory authority changes (backport from 0.2.9.2-alpha):
8550 - The "Tonga" bridge authority has been retired; the new bridge
8551 authority is "Bifroest". Closes tickets 19728 and 19690.
8553 o Directory authority key updates (backport from 0.2.8.1-alpha):
8554 - Update the V3 identity key for the dannenberg directory authority:
8555 it was changed on 18 November 2015. Closes task 17906. Patch
8558 o Major features (security fixes, backport from 0.2.9.4-alpha):
8559 - Prevent a class of security bugs caused by treating the contents
8560 of a buffer chunk as if they were a NUL-terminated string. At
8561 least one such bug seems to be present in all currently used
8562 versions of Tor, and would allow an attacker to remotely crash
8563 most Tor instances, especially those compiled with extra compiler
8564 hardening. With this defense in place, such bugs can't crash Tor,
8565 though we should still fix them as they occur. Closes ticket
8566 20384 (TROVE-2016-10-001).
8568 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8569 - Fix a bug in parsing that could cause clients to read a single
8570 byte past the end of an allocated region. This bug could be used
8571 to cause hardened clients (built with --enable-expensive-hardening)
8572 to crash if they tried to visit a hostile hidden service. Non-
8573 hardened clients are only affected depending on the details of
8574 their platform's memory allocator. Fixes bug 21018; bugfix on
8575 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8576 2016-12-002 and as CVE-2016-1254.
8578 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8579 - Stop a crash that could occur when a client running with DNSPort
8580 received a query with multiple address types, and the first
8581 address type was not supported. Found and fixed by Scott Dial.
8582 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8584 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8585 - Fix an error that could cause us to read 4 bytes before the
8586 beginning of an openssl string. This bug could be used to cause
8587 Tor to crash on systems with unusual malloc implementations, or
8588 systems with unusual hardening installed. Fixes bug 17404; bugfix
8591 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8592 - Avoid a difficult-to-trigger heap corruption attack when extending
8593 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8594 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8595 Reported by Guido Vranken.
8597 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8598 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8599 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8601 o Major bugfixes (guard selection, backport from 0.2.7.6):
8602 - Actually look at the Guard flag when selecting a new directory
8603 guard. When we implemented the directory guard design, we
8604 accidentally started treating all relays as if they have the Guard
8605 flag during guard selection, leading to weaker anonymity and worse
8606 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8609 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8610 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8611 pointer to the previous (uninitialized) key value. The impact here
8612 should be limited to a difficult-to-trigger crash, if OpenSSL is
8613 running an engine that makes key generation failures possible, or
8614 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8615 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8618 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8619 - Fix an integer underflow bug when comparing malformed Tor
8620 versions. This bug could crash Tor when built with
8621 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8622 0.2.9.8, which were built with -ftrapv by default. In other cases
8623 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8624 on 0.0.8pre1. Found by OSS-Fuzz.
8626 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8627 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8628 zero size. Check size argument to memwipe() for underflow. Fixes
8629 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8632 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8633 - Make Tor survive errors involving connections without a
8634 corresponding event object. Previously we'd fail with an
8635 assertion; now we produce a log message. Related to bug 16248.
8637 o Minor features (geoip):
8638 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8641 o Minor bugfixes (compilation, backport from 0.2.7.6):
8642 - Fix a compilation warning with Clang 3.6: Do not check the
8643 presence of an address which can never be NULL. Fixes bug 17781.
8646 Changes in version 0.2.5.13 - 2017-03-03
8647 Tor 0.2.5.13 backports a number of security fixes from later Tor
8648 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
8649 this release, if for some reason they cannot upgrade to a later
8652 Note that support for Tor 0.2.5.x is ending next year: we will not issue
8653 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
8654 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
8656 o Directory authority changes (backport from 0.2.8.5-rc):
8657 - Urras is no longer a directory authority. Closes ticket 19271.
8659 o Directory authority changes (backport from 0.2.9.2-alpha):
8660 - The "Tonga" bridge authority has been retired; the new bridge
8661 authority is "Bifroest". Closes tickets 19728 and 19690.
8663 o Directory authority key updates (backport from 0.2.8.1-alpha):
8664 - Update the V3 identity key for the dannenberg directory authority:
8665 it was changed on 18 November 2015. Closes task 17906. Patch
8668 o Major features (security fixes, backport from 0.2.9.4-alpha):
8669 - Prevent a class of security bugs caused by treating the contents
8670 of a buffer chunk as if they were a NUL-terminated string. At
8671 least one such bug seems to be present in all currently used
8672 versions of Tor, and would allow an attacker to remotely crash
8673 most Tor instances, especially those compiled with extra compiler
8674 hardening. With this defense in place, such bugs can't crash Tor,
8675 though we should still fix them as they occur. Closes ticket
8676 20384 (TROVE-2016-10-001).
8678 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8679 - Fix a bug in parsing that could cause clients to read a single
8680 byte past the end of an allocated region. This bug could be used
8681 to cause hardened clients (built with --enable-expensive-hardening)
8682 to crash if they tried to visit a hostile hidden service. Non-
8683 hardened clients are only affected depending on the details of
8684 their platform's memory allocator. Fixes bug 21018; bugfix on
8685 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8686 2016-12-002 and as CVE-2016-1254.
8688 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
8689 - Stop a crash that could occur when a client running with DNSPort
8690 received a query with multiple address types, and the first
8691 address type was not supported. Found and fixed by Scott Dial.
8692 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
8694 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8695 - Fix an error that could cause us to read 4 bytes before the
8696 beginning of an openssl string. This bug could be used to cause
8697 Tor to crash on systems with unusual malloc implementations, or
8698 systems with unusual hardening installed. Fixes bug 17404; bugfix
8701 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8702 - Avoid a difficult-to-trigger heap corruption attack when extending
8703 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8704 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8705 Reported by Guido Vranken.
8707 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8708 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8709 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8711 o Major bugfixes (guard selection, backport from 0.2.7.6):
8712 - Actually look at the Guard flag when selecting a new directory
8713 guard. When we implemented the directory guard design, we
8714 accidentally started treating all relays as if they have the Guard
8715 flag during guard selection, leading to weaker anonymity and worse
8716 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8719 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8720 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8721 pointer to the previous (uninitialized) key value. The impact here
8722 should be limited to a difficult-to-trigger crash, if OpenSSL is
8723 running an engine that makes key generation failures possible, or
8724 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8725 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8728 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8729 - Fix an integer underflow bug when comparing malformed Tor
8730 versions. This bug could crash Tor when built with
8731 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8732 0.2.9.8, which were built with -ftrapv by default. In other cases
8733 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8734 on 0.0.8pre1. Found by OSS-Fuzz.
8736 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8737 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8738 zero size. Check size argument to memwipe() for underflow. Fixes
8739 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8742 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8743 - Make Tor survive errors involving connections without a
8744 corresponding event object. Previously we'd fail with an
8745 assertion; now we produce a log message. Related to bug 16248.
8747 o Minor features (geoip):
8748 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8751 o Minor bugfixes (compilation, backport from 0.2.7.6):
8752 - Fix a compilation warning with Clang 3.6: Do not check the
8753 presence of an address which can never be NULL. Fixes bug 17781.
8755 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
8756 - Check for failures from crypto_early_init, and refuse to continue.
8757 A previous typo meant that we could keep going with an
8758 uninitialized crypto library, and would have OpenSSL initialize
8759 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
8760 when implementing ticket 4900. Patch by "teor".
8762 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8763 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8764 a client authorized hidden service. Fixes bug 15823; bugfix
8768 Changes in version 0.2.4.28 - 2017-03-03
8769 Tor 0.2.4.28 backports a number of security fixes from later Tor
8770 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
8771 this release, if for some reason they cannot upgrade to a later
8774 Note that support for Tor 0.2.4.x is ending soon: we will not issue
8775 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
8776 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
8778 o Directory authority changes (backport from 0.2.8.5-rc):
8779 - Urras is no longer a directory authority. Closes ticket 19271.
8781 o Directory authority changes (backport from 0.2.9.2-alpha):
8782 - The "Tonga" bridge authority has been retired; the new bridge
8783 authority is "Bifroest". Closes tickets 19728 and 19690.
8785 o Directory authority key updates (backport from 0.2.8.1-alpha):
8786 - Update the V3 identity key for the dannenberg directory authority:
8787 it was changed on 18 November 2015. Closes task 17906. Patch
8790 o Major features (security fixes, backport from 0.2.9.4-alpha):
8791 - Prevent a class of security bugs caused by treating the contents
8792 of a buffer chunk as if they were a NUL-terminated string. At
8793 least one such bug seems to be present in all currently used
8794 versions of Tor, and would allow an attacker to remotely crash
8795 most Tor instances, especially those compiled with extra compiler
8796 hardening. With this defense in place, such bugs can't crash Tor,
8797 though we should still fix them as they occur. Closes ticket
8798 20384 (TROVE-2016-10-001).
8800 o Major bugfixes (parsing, security, backport from 0.2.9.8):
8801 - Fix a bug in parsing that could cause clients to read a single
8802 byte past the end of an allocated region. This bug could be used
8803 to cause hardened clients (built with --enable-expensive-hardening)
8804 to crash if they tried to visit a hostile hidden service. Non-
8805 hardened clients are only affected depending on the details of
8806 their platform's memory allocator. Fixes bug 21018; bugfix on
8807 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
8808 2016-12-002 and as CVE-2016-1254.
8810 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
8811 - Fix an error that could cause us to read 4 bytes before the
8812 beginning of an openssl string. This bug could be used to cause
8813 Tor to crash on systems with unusual malloc implementations, or
8814 systems with unusual hardening installed. Fixes bug 17404; bugfix
8817 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
8818 - Avoid a difficult-to-trigger heap corruption attack when extending
8819 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
8820 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
8821 Reported by Guido Vranken.
8823 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
8824 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
8825 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
8827 o Major bugfixes (guard selection, backport from 0.2.7.6):
8828 - Actually look at the Guard flag when selecting a new directory
8829 guard. When we implemented the directory guard design, we
8830 accidentally started treating all relays as if they have the Guard
8831 flag during guard selection, leading to weaker anonymity and worse
8832 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
8835 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
8836 - If OpenSSL fails to generate an RSA key, do not retain a dangling
8837 pointer to the previous (uninitialized) key value. The impact here
8838 should be limited to a difficult-to-trigger crash, if OpenSSL is
8839 running an engine that makes key generation failures possible, or
8840 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
8841 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
8844 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
8845 - Fix an integer underflow bug when comparing malformed Tor
8846 versions. This bug could crash Tor when built with
8847 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8848 0.2.9.8, which were built with -ftrapv by default. In other cases
8849 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8850 on 0.0.8pre1. Found by OSS-Fuzz.
8852 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
8853 - Make memwipe() do nothing when passed a NULL pointer or buffer of
8854 zero size. Check size argument to memwipe() for underflow. Fixes
8855 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
8858 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
8859 - Make Tor survive errors involving connections without a
8860 corresponding event object. Previously we'd fail with an
8861 assertion; now we produce a log message. Related to bug 16248.
8863 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
8864 - Make it harder for attackers to overload hidden services with
8865 introductions, by blocking multiple introduction requests on the
8866 same circuit. Resolves ticket 15515.
8868 o Minor features (geoip):
8869 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8872 o Minor bugfixes (compilation, backport from 0.2.7.6):
8873 - Fix a compilation warning with Clang 3.6: Do not check the
8874 presence of an address which can never be NULL. Fixes bug 17781.
8876 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
8877 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
8878 a client authorized hidden service. Fixes bug 15823; bugfix
8882 Changes in version 0.2.9.10 - 2017-03-01
8883 Tor 0.2.9.10 backports a security fix from later Tor release. It also
8884 includes fixes for some major issues affecting directory authorities,
8885 LibreSSL compatibility, and IPv6 correctness.
8887 The Tor 0.2.9.x release series is now marked as a long-term-support
8888 series. We intend to backport security fixes to 0.2.9.x until at
8889 least January of 2020.
8891 o Major bugfixes (directory authority, 0.3.0.3-alpha):
8892 - During voting, when marking a relay as a probable sybil, do not
8893 clear its BadExit flag: sybils can still be bad in other ways
8894 too. (We still clear the other flags.) Fixes bug 21108; bugfix
8897 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
8898 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
8899 any IPv6 addresses. Instead, only reject a port over IPv6 if the
8900 exit policy rejects that port on more than an IPv6 /16 of
8901 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
8902 which rejected a relay's own IPv6 address by default. Fixes bug
8903 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
8905 o Major bugfixes (parsing, also in 0.3.0.4-rc):
8906 - Fix an integer underflow bug when comparing malformed Tor
8907 versions. This bug could crash Tor when built with
8908 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
8909 0.2.9.8, which were built with -ftrapv by default. In other cases
8910 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
8911 on 0.0.8pre1. Found by OSS-Fuzz.
8913 o Minor features (directory authorities, also in 0.3.0.4-rc):
8914 - Directory authorities now reject descriptors that claim to be
8915 malformed versions of Tor. Helps prevent exploitation of
8917 - Reject version numbers with components that exceed INT32_MAX.
8918 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
8919 Fixes bug 21450; bugfix on 0.0.8pre1.
8921 o Minor features (geoip):
8922 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
8925 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
8926 - Autoconf now checks to determine if OpenSSL structures are opaque,
8927 instead of explicitly checking for OpenSSL version numbers. Part
8929 - Support building with recent LibreSSL code that uses opaque
8930 structures. Closes ticket 21359.
8932 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
8933 - Repair a couple of (unreachable or harmless) cases of the risky
8934 comparison-by-subtraction pattern that caused bug 21278.
8936 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
8937 - The tor-resolve command line tool now rejects hostnames over 255
8938 characters in length. Previously, it would silently truncate them,
8939 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
8940 Patch by "junglefowl".
8943 Changes in version 0.2.9.9 - 2017-01-23
8944 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
8945 cause relays and clients to crash, even if they were not built with
8946 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
8947 versions, and also affects 0.3.0.1-alpha: all relays running an affected
8948 version should upgrade.
8950 This release also resolves a client-side onion service reachability
8951 bug, and resolves a pair of small portability issues.
8953 o Major bugfixes (security):
8954 - Downgrade the "-ftrapv" option from "always on" to "only on when
8955 --enable-expensive-hardening is provided." This hardening option,
8956 like others, can turn survivable bugs into crashes -- and having
8957 it on by default made a (relatively harmless) integer overflow bug
8958 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
8959 bugfix on 0.2.9.1-alpha.
8961 o Major bugfixes (client, onion service):
8962 - Fix a client-side onion service reachability bug, where multiple
8963 socks requests to an onion service (or a single slow request)
8964 could cause us to mistakenly mark some of the service's
8965 introduction points as failed, and we cache that failure so
8966 eventually we run out and can't reach the service. Also resolves a
8967 mysterious "Remote server sent bogus reason code 65021" log
8968 warning. The bug was introduced in ticket 17218, where we tried to
8969 remember the circuit end reason as a uint16_t, which mangled
8970 negative values. Partially fixes bug 21056 and fixes bug 20307;
8971 bugfix on 0.2.8.1-alpha.
8973 o Minor features (geoip):
8974 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
8977 o Minor bugfixes (portability):
8978 - Avoid crashing when Tor is built using headers that contain
8979 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
8980 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
8982 - Fix Libevent detection on platforms without Libevent 1 headers
8983 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
8986 Changes in version 0.2.8.12 - 2016-12-19
8987 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
8988 below) where Tor clients could crash when attempting to visit a
8989 hostile hidden service. Clients are recommended to upgrade as packages
8990 become available for their systems.
8992 It also includes an updated list of fallback directories, backported
8995 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
8996 backported to 0.2.8 in the future.
8998 o Major bugfixes (parsing, security, backported from 0.2.9.8):
8999 - Fix a bug in parsing that could cause clients to read a single
9000 byte past the end of an allocated region. This bug could be used
9001 to cause hardened clients (built with --enable-expensive-hardening)
9002 to crash if they tried to visit a hostile hidden service. Non-
9003 hardened clients are only affected depending on the details of
9004 their platform's memory allocator. Fixes bug 21018; bugfix on
9005 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9006 2016-12-002 and as CVE-2016-1254.
9008 o Minor features (fallback directory list, backported from 0.2.9.8):
9009 - Replace the 81 remaining fallbacks of the 100 originally
9010 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
9011 fallbacks (123 new, 54 existing, 27 removed) generated in December
9012 2016. Resolves ticket 20170.
9014 o Minor features (geoip, backported from 0.2.9.7-rc):
9015 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
9019 Changes in version 0.2.9.8 - 2016-12-19
9020 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
9022 The Tor 0.2.9 series makes mandatory a number of security features
9023 that were formerly optional. It includes support for a new shared-
9024 randomness protocol that will form the basis for next generation
9025 hidden services, includes a single-hop hidden service mode for
9026 optimizing .onion services that don't actually want to be hidden,
9027 tries harder not to overload the directory authorities with excessive
9028 downloads, and supports a better protocol versioning scheme for
9029 improved compatibility with other implementations of the Tor protocol.
9031 And of course, there are numerous other bugfixes and improvements.
9033 This release also includes a fix for a medium-severity issue (bug
9034 21018 below) where Tor clients could crash when attempting to visit a
9035 hostile hidden service. Clients are recommended to upgrade as packages
9036 become available for their systems.
9038 Below are listed the changes since Tor 0.2.8.11. For a list of
9039 changes since 0.2.9.7-rc, see the ChangeLog file.
9041 o New system requirements:
9042 - When building with OpenSSL, Tor now requires version 1.0.1 or
9043 later. OpenSSL 1.0.0 and earlier are no longer supported by the
9044 OpenSSL team, and should not be used. Closes ticket 20303.
9045 - Tor now requires Libevent version 2.0.10-stable or later. Older
9046 versions of Libevent have less efficient backends for several
9047 platforms, and lack the DNS code that we use for our server-side
9048 DNS support. This implements ticket 19554.
9049 - Tor now requires zlib version 1.2 or later, for security,
9050 efficiency, and (eventually) gzip support. (Back when we started,
9051 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
9052 released in 2003. We recommend the latest version.)
9054 o Deprecated features:
9055 - A number of DNS-cache-related sub-options for client ports are now
9056 deprecated for security reasons, and may be removed in a future
9057 version of Tor. (We believe that client-side DNS caching is a bad
9058 idea for anonymity, and you should not turn it on.) The options
9059 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
9060 UseIPv4Cache, and UseIPv6Cache.
9061 - A number of options are deprecated for security reasons, and may
9062 be removed in a future version of Tor. The options are:
9063 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
9064 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
9065 CloseHSClientCircuitsImmediatelyOnTimeout,
9066 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
9067 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
9068 UseNTorHandshake, and WarnUnsafeSocks.
9069 - The *ListenAddress options are now deprecated as unnecessary: the
9070 corresponding *Port options should be used instead. These options
9071 may someday be removed. The affected options are:
9072 ControlListenAddress, DNSListenAddress, DirListenAddress,
9073 NATDListenAddress, ORListenAddress, SocksListenAddress,
9074 and TransListenAddress.
9076 o Major bugfixes (parsing, security, new since 0.2.9.7-rc):
9077 - Fix a bug in parsing that could cause clients to read a single
9078 byte past the end of an allocated region. This bug could be used
9079 to cause hardened clients (built with --enable-expensive-hardening)
9080 to crash if they tried to visit a hostile hidden service. Non-
9081 hardened clients are only affected depending on the details of
9082 their platform's memory allocator. Fixes bug 21018; bugfix on
9083 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9084 2016-12-002 and as CVE-2016-1254.
9086 o Major features (build, hardening):
9087 - Tor now builds with -ftrapv by default on compilers that support
9088 it. This option detects signed integer overflow (which C forbids),
9089 and turns it into a hard-failure. We do not apply this option to
9090 code that needs to run in constant time to avoid side-channels;
9091 instead, we use -fwrapv in that code. Closes ticket 17983.
9092 - When --enable-expensive-hardening is selected, stop applying the
9093 clang/gcc sanitizers to code that needs to run in constant time.
9094 Although we are aware of no introduced side-channels, we are not
9095 able to prove that there are none. Related to ticket 17983.
9097 o Major features (circuit building, security):
9098 - Authorities, relays, and clients now require ntor keys in all
9099 descriptors, for all hops (except for rare hidden service protocol
9100 cases), for all circuits, and for all other roles. Part of
9102 - Authorities, relays, and clients only use ntor, except for
9103 rare cases in the hidden service protocol. Part of ticket 19163.
9105 o Major features (compilation):
9106 - Our big list of extra GCC warnings is now enabled by default when
9107 building with GCC (or with anything like Clang that claims to be
9108 GCC-compatible). To make all warnings into fatal compilation
9109 errors, pass --enable-fatal-warnings to configure. Closes
9111 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
9112 turn on C and POSIX extensions. (Previously, we attempted to do
9113 this on an ad hoc basis.) Closes ticket 19139.
9115 o Major features (directory authorities, hidden services):
9116 - Directory authorities can now perform the shared randomness
9117 protocol specified by proposal 250. Using this protocol, directory
9118 authorities generate a global fresh random value every day. In the
9119 future, this value will be used by hidden services to select
9120 HSDirs. This release implements the directory authority feature;
9121 the hidden service side will be implemented in the future as part
9122 of proposal 224. Resolves ticket 16943; implements proposal 250.
9124 o Major features (downloading, random exponential backoff):
9125 - When we fail to download an object from a directory service, wait
9126 for an (exponentially increasing) randomized amount of time before
9127 retrying, rather than a fixed interval as we did before. This
9128 prevents a group of Tor instances from becoming too synchronized,
9129 or a single Tor instance from becoming too predictable, in its
9130 download schedule. Closes ticket 15942.
9132 o Major features (resource management):
9133 - Tor can now notice it is about to run out of sockets, and
9134 preemptively close connections of lower priority. (This feature is
9135 off by default for now, since the current prioritizing method is
9136 yet not mature enough. You can enable it by setting
9137 "DisableOOSCheck 0", but watch out: it might close some sockets
9138 you would rather have it keep.) Closes ticket 18640.
9140 o Major features (single-hop "hidden" services):
9141 - Add experimental HiddenServiceSingleHopMode and
9142 HiddenServiceNonAnonymousMode options. When both are set to 1,
9143 every hidden service on that Tor instance becomes a non-anonymous
9144 Single Onion Service. Single Onions make one-hop (direct)
9145 connections to their introduction and rendezvous points. One-hop
9146 circuits make Single Onion servers easily locatable, but clients
9147 remain location-anonymous. This is compatible with the existing
9148 hidden service implementation, and works on the current Tor
9149 network without any changes to older relays or clients. Implements
9150 proposal 260, completes ticket 17178. Patch by teor and asn.
9152 o Major features (subprotocol versions):
9153 - Tor directory authorities now vote on a set of recommended
9154 "subprotocol versions", and on a set of required subprotocol
9155 versions. Clients and relays that lack support for a _required_
9156 subprotocol version will not start; those that lack support for a
9157 _recommended_ subprotocol version will warn the user to upgrade.
9158 This change allows compatible implementations of the Tor protocol(s)
9159 to exist without pretending to be 100% bug-compatible with
9160 particular releases of Tor itself. Closes ticket 19958; implements
9161 part of proposal 264.
9163 o Major bugfixes (circuit building):
9164 - Hidden service client-to-intro-point and service-to-rendezvous-
9165 point circuits use the TAP key supplied by the protocol, to avoid
9166 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
9168 o Major bugfixes (download scheduling):
9169 - Avoid resetting download status for consensuses hourly, since we
9170 already have another, smarter retry mechanism. Fixes bug 8625;
9171 bugfix on 0.2.0.9-alpha.
9172 - If a consensus expires while we are waiting for certificates to
9173 download, stop waiting for certificates.
9174 - If we stop waiting for certificates less than a minute after we
9175 started downloading them, do not consider the certificate download
9176 failure a separate failure. Fixes bug 20533; bugfix
9178 - When using exponential backoff in test networks, use a lower
9179 exponent, so the delays do not vary as much. This helps test
9180 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
9182 o Major bugfixes (exit policies):
9183 - Avoid disclosing exit outbound bind addresses, configured port
9184 bind addresses, and local interface addresses in relay descriptors
9185 by default under ExitPolicyRejectPrivate. Instead, only reject
9186 these (otherwise unlisted) addresses if
9187 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
9188 0.2.7.2-alpha. Patch by teor.
9190 o Major bugfixes (hidden services):
9191 - Allow Tor clients with appropriate controllers to work with
9192 FetchHidServDescriptors set to 0. Previously, this option also
9193 disabled descriptor cache lookup, thus breaking hidden services
9194 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
9195 - Clients now require hidden services to include the TAP keys for
9196 their intro points in the hidden service descriptor. This prevents
9197 an inadvertent upgrade to ntor, which a malicious hidden service
9198 could use to distinguish clients by consensus version. Fixes bug
9199 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
9201 o Major bugfixes (relay, resolver, logging):
9202 - For relays that don't know their own address, avoid attempting a
9203 local hostname resolve for each descriptor we download. This
9204 will cut down on the number of "Success: chose address 'x.x.x.x'"
9205 log lines, and also avoid confusing clock jumps if the resolver
9206 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
9208 o Minor features (port flags):
9209 - Add new flags to the *Port options to give finer control over which
9210 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
9211 and the synthetic flag OnionTrafficOnly, which is equivalent to
9212 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
9213 18693; patch by "teor".
9215 o Minor features (build, hardening):
9216 - Detect and work around a libclang_rt problem that would prevent
9217 clang from finding __mulodi4() on some 32-bit platforms, and thus
9218 keep -ftrapv from linking on those systems. Closes ticket 19079.
9219 - When building on a system without runtime support for the runtime
9220 hardening options, try to log a useful warning at configuration
9221 time, rather than an incomprehensible warning at link time. If
9222 expensive hardening was requested, this warning becomes an error.
9223 Closes ticket 18895.
9225 o Minor features (client, directory):
9226 - Since authorities now omit all routers that lack the Running and
9227 Valid flags, we assume that any relay listed in the consensus must
9228 have those flags. Closes ticket 20001; implements part of
9231 o Minor features (code safety):
9232 - In our integer-parsing functions, ensure that the maximum value we
9233 allow is no smaller than the minimum value. Closes ticket 19063;
9234 patch from "U+039b".
9236 o Minor features (compilation, portability):
9237 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
9240 o Minor features (config):
9241 - Warn users when descriptor and port addresses are inconsistent.
9242 Mitigates bug 13953; patch by teor.
9244 o Minor features (controller):
9245 - Allow controllers to configure basic client authorization on
9246 hidden services when they create them with the ADD_ONION controller
9247 command. Implements ticket 15588. Patch by "special".
9248 - Fire a STATUS_SERVER controller event whenever the hibernation
9249 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
9250 - Implement new GETINFO queries for all downloads that use
9251 download_status_t to schedule retries. This allows controllers to
9252 examine the schedule for pending downloads. Closes ticket 19323.
9254 o Minor features (development tools, etags):
9255 - Teach the "make tags" Makefile target how to correctly find
9256 "MOCK_IMPL" function definitions. Patch from nherring; closes
9259 o Minor features (directory authority):
9260 - After voting, if the authorities decide that a relay is not
9261 "Valid", they no longer include it in the consensus at all. Closes
9262 ticket 20002; implements part of proposal 272.
9263 - Directory authorities now only give the Guard flag to a relay if
9264 they are also giving it the Stable flag. This change allows us to
9265 simplify path selection for clients. It should have minimal effect
9266 in practice, since >99% of Guards already have the Stable flag.
9267 Implements ticket 18624.
9268 - Directory authorities now write their v3-status-votes file out to
9269 disk earlier in the consensus process, so we have a record of the
9270 votes even if we abort the consensus process. Resolves
9273 o Minor features (fallback directory list, new since 0.2.9.7-rc):
9274 - Replace the 81 remaining fallbacks of the 100 originally
9275 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
9276 fallbacks (123 new, 54 existing, 27 removed) generated in December
9277 2016. Resolves ticket 20170.
9279 o Minor features (hidden service):
9280 - Stop being so strict about the payload length of "rendezvous1"
9281 cells. We used to be locked in to the "TAP" handshake length, and
9282 now we can handle better handshakes like "ntor". Resolves
9285 o Minor features (infrastructure, time):
9286 - Tor now includes an improved timer backend, so that we can
9287 efficiently support tens or hundreds of thousands of concurrent
9288 timers, as will be needed for some of our planned anti-traffic-
9289 analysis work. This code is based on William Ahern's "timeout.c"
9290 project, which implements a "tickless hierarchical timing wheel".
9291 Closes ticket 18365.
9292 - Tor now uses the operating system's monotonic timers (where
9293 available) for internal fine-grained timing. Previously we would
9294 look at the system clock, and then attempt to compensate for the
9295 clock running backwards. Closes ticket 18908.
9297 o Minor features (logging):
9298 - Add a set of macros to check nonfatal assertions, for internal
9299 use. Migrating more of our checks to these should help us avoid
9300 needless crash bugs. Closes ticket 18613.
9301 - Provide a more useful warning message when configured with an
9302 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
9303 - When dumping unparseable router descriptors, optionally store them
9304 in separate files, named by digest, up to a configurable size
9305 limit. You can change the size limit by setting the
9306 MaxUnparseableDescSizeToLog option, and disable this feature by
9307 setting that option to 0. Closes ticket 18322.
9309 o Minor features (performance):
9310 - Change the "optimistic data" extension from "off by default" to
9311 "on by default". The default was ordinarily overridden by a
9312 consensus option, but when clients were bootstrapping for the
9313 first time, they would not have a consensus to get the option
9314 from. Changing this default saves a round-trip during startup.
9315 Closes ticket 18815.
9317 o Minor features (relay, usability):
9318 - When the directory authorities refuse a bad relay's descriptor,
9319 encourage the relay operator to contact us. Many relay operators
9320 won't notice this line in their logs, but it's a win if even a few
9321 learn why we don't like what their relay was doing. Resolves
9324 o Minor features (security, TLS):
9325 - Servers no longer support clients that lack AES ciphersuites.
9326 (3DES is no longer considered an acceptable cipher.) We believe
9327 that no such Tor clients currently exist, since Tor has required
9328 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
9330 o Minor features (testing):
9331 - Disable memory protections on OpenBSD when performing our unit
9332 tests for memwipe(). The test deliberately invokes undefined
9333 behavior, and the OpenBSD protections interfere with this. Patch
9334 from "rubiate". Closes ticket 20066.
9335 - Move the test-network.sh script to chutney, and modify tor's test-
9336 network.sh to call the (newer) chutney version when available.
9337 Resolves ticket 19116. Patch by teor.
9338 - Use the lcov convention for marking lines as unreachable, so that
9339 we don't count them when we're generating test coverage data.
9340 Update our coverage tools to understand this convention. Closes
9342 - Our link-handshake unit tests now check that when invalid
9343 handshakes fail, they fail with the error messages we expected.
9344 - Our unit testing code that captures log messages no longer
9345 prevents them from being written out if the user asked for them
9346 (by passing --debug or --info or --notice or --warn to the "test"
9347 binary). This change prevents us from missing unexpected log
9348 messages simply because we were looking for others. Related to
9350 - The unit tests now log all warning messages with the "BUG" flag.
9351 Previously, they only logged errors by default. This change will
9352 help us make our testing code more correct, and make sure that we
9353 only hit this code when we mean to. In the meantime, however,
9354 there will be more warnings in the unit test logs than before.
9355 This is preparatory work for ticket 19999.
9356 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
9357 assertion as a test failure.
9358 - We've done significant work to make the unit tests run faster.
9360 o Minor features (testing, ipv6):
9361 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
9362 tests. Remove bridges+hs, as it's somewhat redundant. This
9363 requires a recent chutney version that supports IPv6 clients,
9364 relays, and authorities. Closes ticket 20069; patch by teor.
9365 - Add the single-onion and single-onion-ipv6 chutney targets to
9366 "make test-network-all". This requires a recent chutney version
9367 with the single onion network flavors (git c72a652 or later).
9368 Closes ticket 20072; patch by teor.
9370 o Minor features (Tor2web):
9371 - Make Tor2web clients respect ReachableAddresses. This feature was
9372 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
9373 0.2.8.7. Implements feature 20034. Patch by teor.
9375 o Minor features (unix domain sockets):
9376 - When configuring a unix domain socket for a SocksPort,
9377 ControlPort, or Hidden service, you can now wrap the address in
9378 quotes, using C-style escapes inside the quotes. This allows unix
9379 domain socket paths to contain spaces. Resolves ticket 18753.
9381 o Minor features (user interface):
9382 - Tor now supports the ability to declare options deprecated, so
9383 that we can recommend that people stop using them. Previously, this
9384 was done in an ad-hoc way. There is a new --list-deprecated-options
9385 command-line option to list all of the deprecated options. Closes
9388 o Minor features (virtual addresses):
9389 - Increase the maximum number of bits for the IPv6 virtual network
9390 prefix from 16 to 104. In this way, the condition for address
9391 allocation is less restrictive. Closes ticket 20151; feature
9394 o Minor bug fixes (circuits):
9395 - Use the CircuitBuildTimeout option whenever
9396 LearnCircuitBuildTimeout is disabled. Previously, we would respect
9397 the option when a user disabled it, but not when it was disabled
9398 because some other option was set. Fixes bug 20073; bugfix on
9399 0.2.4.12-alpha. Patch by teor.
9401 o Minor bugfixes (build):
9402 - The current Git revision when building from a local repository is
9403 now detected correctly when using git worktrees. Fixes bug 20492;
9404 bugfix on 0.2.3.9-alpha.
9406 o Minor bugfixes (relay address discovery):
9407 - Stop reordering IP addresses returned by the OS. This makes it
9408 more likely that Tor will guess the same relay IP address every
9409 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
9410 Reported by René Mayrhofer, patch by "cypherpunks".
9412 o Minor bugfixes (memory allocation):
9413 - Change how we allocate memory for large chunks on buffers, to
9414 avoid a (currently impossible) integer overflow, and to waste less
9415 space when allocating unusually large chunks. Fixes bug 20081;
9416 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
9418 o Minor bugfixes (bootstrap):
9419 - Remember the directory server we fetched the consensus or previous
9420 certificates from, and use it to fetch future authority
9421 certificates. This change improves bootstrapping performance.
9422 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
9424 o Minor bugfixes (circuits):
9425 - Make sure extend_info_from_router() is only called on servers.
9426 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
9428 o Minor bugfixes (client, fascistfirewall):
9429 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
9430 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
9432 o Minor bugfixes (client, unix domain sockets):
9433 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
9434 the client address is meaningless. Fixes bug 20261; bugfix
9437 o Minor bugfixes (code style):
9438 - Fix an integer signedness conversion issue in the case conversion
9439 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
9441 o Minor bugfixes (compilation):
9442 - Build correctly on versions of libevent2 without support for
9443 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
9445 - When building with Clang, use a full set of GCC warnings.
9446 (Previously, we included only a subset, because of the way we
9447 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
9448 - Detect Libevent2 functions correctly on systems that provide
9449 libevent2, but where libevent1 is linked with -levent. Fixes bug
9450 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
9451 - Run correctly when built on Windows build environments that
9452 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
9454 o Minor bugfixes (configuration):
9455 - When parsing quoted configuration values from the torrc file,
9456 handle Windows line endings correctly. Fixes bug 19167; bugfix on
9457 0.2.0.16-alpha. Patch from "Pingl".
9459 o Minor bugfixes (directory authority):
9460 - Authorities now sort the "package" lines in their votes, for ease
9461 of debugging. (They are already sorted in consensus documents.)
9462 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
9463 - Die with a more useful error when the operator forgets to place
9464 the authority_signing_key file into the keys directory. This
9465 avoids an uninformative assert & traceback about having an invalid
9466 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
9467 - When allowing private addresses, mark Exits that only exit to
9468 private locations as such. Fixes bug 20064; bugfix
9470 - When parsing a detached signature, make sure we use the length of
9471 the digest algorithm instead of a hardcoded DIGEST256_LEN in
9472 order to avoid comparing bytes out-of-bounds with a smaller digest
9473 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
9475 o Minor bugfixes (getpass):
9476 - Defensively fix a non-triggerable heap corruption at do_getpass()
9477 to protect ourselves from mistakes in the future. Fixes bug
9478 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
9481 o Minor bugfixes (guard selection):
9482 - Don't mark guards as unreachable if connection_connect() fails.
9483 That function fails for local reasons, so it shouldn't reveal
9484 anything about the status of the guard. Fixes bug 14334; bugfix
9486 - Use a single entry guard even if the NumEntryGuards consensus
9487 parameter is not provided. Fixes bug 17688; bugfix
9490 o Minor bugfixes (hidden services):
9491 - Increase the minimum number of internal circuits we preemptively
9492 build from 2 to 3, so a circuit is available when a client
9493 connects to another onion service. Fixes bug 13239; bugfix
9495 - Allow hidden services to run on IPv6 addresses even when the
9496 IPv6Exit option is not set. Fixes bug 18357; bugfix
9498 - Stop logging intro point details to the client log on certain
9499 error conditions. Fixed as part of bug 20012; bugfix on
9500 0.2.4.8-alpha. Patch by teor.
9501 - When deleting an ephemeral hidden service, close its intro points
9502 even if they are not completely open. Fixes bug 18604; bugfix
9504 - When configuring hidden services, check every hidden service
9505 directory's permissions. Previously, we only checked the last
9506 hidden service. Fixes bug 20529; bugfix on 0.2.6.2-alpha.
9508 o Minor bugfixes (IPv6, testing):
9509 - Check for IPv6 correctly on Linux when running test networks.
9510 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
9512 o Minor bugfixes (Linux seccomp2 sandbox):
9513 - Add permission to run the sched_yield() and sigaltstack() system
9514 calls, in order to support versions of Tor compiled with asan or
9515 ubsan code that use these calls. Now "sandbox 1" and
9516 "--enable-expensive-hardening" should be compatible on more
9517 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
9519 o Minor bugfixes (logging):
9520 - Downgrade a harmless log message about the
9521 pending_entry_connections list from "warn" to "info". Mitigates
9523 - Log a more accurate message when we fail to dump a microdescriptor.
9524 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
9525 - When logging a directory ownership mismatch, log the owning
9526 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
9527 - When we are unable to remove the bw_accounting file, do not warn
9528 if the reason we couldn't remove it was that it didn't exist.
9529 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from pastly.
9531 o Minor bugfixes (memory leak):
9532 - Fix a series of slow memory leaks related to parsing torrc files
9533 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
9534 - Avoid a small memory leak when informing worker threads about
9535 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
9536 - Fix a small memory leak when receiving AF_UNIX connections on a
9537 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
9538 - When moving a signed descriptor object from a source to an
9539 existing destination, free the allocated memory inside that
9540 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
9541 - Fix a memory leak and use-after-free error when removing entries
9542 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
9543 0.2.5.5-alpha. Patch from "cypherpunks".
9544 - Fix a small, uncommon memory leak that could occur when reading a
9545 truncated ed25519 key file. Fixes bug 18956; bugfix
9548 o Minor bugfixes (option parsing):
9549 - Count unix sockets when counting client listeners (SOCKS, Trans,
9550 NATD, and DNS). This has no user-visible behavior changes: these
9551 options are set once, and never read. Required for correct
9552 behavior in ticket 17178. Fixes bug 19677; bugfix on
9553 0.2.6.3-alpha. Patch by teor.
9555 o Minor bugfixes (options):
9556 - Check the consistency of UseEntryGuards and EntryNodes more
9557 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
9559 - Stop changing the configured value of UseEntryGuards on
9560 authorities and Tor2web clients. Fixes bug 20074; bugfix on
9561 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
9564 o Minor bugfixes (relay):
9565 - Ensure relays don't make multiple connections during bootstrap.
9566 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
9567 - Do not try to parallelize workers more than 16x without the user
9568 explicitly configuring us to do so, even if we do detect more than
9569 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
9571 o Minor bugfixes (testing):
9572 - The test-stem and test-network makefile targets now depend only on
9573 the tor binary that they are testing. Previously, they depended on
9574 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
9575 patch from "cypherpunks".
9576 - Allow clients to retry HSDirs much faster in test networks. Fixes
9577 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
9578 - Avoid a unit test failure on systems with over 16 detectable CPU
9579 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
9580 - Let backtrace tests work correctly under AddressSanitizer:
9581 disable ASAN's detection of segmentation faults while running
9582 test_bt.sh, so that we can make sure that our own backtrace
9583 generation code works. Fixes bug 18934; bugfix
9584 on 0.2.5.2-alpha. Patch from "cypherpunks".
9585 - Fix the test-network-all target on out-of-tree builds by using the
9586 correct path to the test driver script. Fixes bug 19421; bugfix
9588 - Stop spurious failures in the local interface address discovery
9589 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
9591 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
9592 removed the ECDH ciphers which caused the tests to fail on
9593 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
9594 - The tor_tls_server_info_callback unit test no longer crashes when
9595 debug-level logging is turned on. Fixes bug 20041; bugfix
9598 o Minor bugfixes (time):
9599 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
9600 bugfix on all released tor versions.
9601 - When computing the difference between two times in milliseconds,
9602 we now round to the nearest millisecond correctly. Previously, we
9603 could sometimes round in the wrong direction. Fixes bug 19428;
9604 bugfix on 0.2.2.2-alpha.
9606 o Minor bugfixes (Tor2web):
9607 - Prevent Tor2web clients from running hidden services: these services
9608 are not anonymous due to the one-hop client paths. Fixes bug
9609 19678. Patch by teor.
9611 o Minor bugfixes (user interface):
9612 - Display a more accurate number of suppressed messages in the log
9613 rate-limiter. Previously, there was a potential integer overflow
9614 in the counter. Now, if the number of messages hits a maximum, the
9615 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
9617 - Fix a typo in the passphrase prompt for the ed25519 identity key.
9618 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
9620 o Code simplification and refactoring:
9621 - Remove redundant declarations of the MIN macro. Closes
9623 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
9624 Closes ticket 18462; patch from "icanhasaccount".
9625 - Split the 600-line directory_handle_command_get function into
9626 separate functions for different URL types. Closes ticket 16698.
9629 - Add module-level internal documentation for 36 C files that
9630 previously didn't have a high-level overview. Closes ticket 20385.
9631 - Correct the IPv6 syntax in our documentation for the
9632 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
9633 - Correct the minimum bandwidth value in torrc.sample, and queue a
9634 corresponding change for torrc.minimal. Closes ticket 20085.
9635 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
9636 ticket 19153. Patch from "U+039b".
9637 - Module-level documentation for several more modules. Closes
9638 tickets 19287 and 19290.
9639 - Document the --passphrase-fd option in the tor manpage. Fixes bug
9640 19504; bugfix on 0.2.7.3-rc.
9641 - Document the default PathsNeededToBuildCircuits value that's used
9642 by clients when the directory authorities don't set
9643 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 0.2.4.10-alpha.
9644 Patch by teor, reported by Jesse V.
9645 - Fix manual for the User option: it takes a username, not a UID.
9646 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
9648 - Fix the description of the --passphrase-fd option in the
9649 tor-gencert manpage. The option is used to pass the number of a
9650 file descriptor to read the passphrase from, not to read the file
9651 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
9654 - We no longer include the (dead, deprecated) bufferevent code in
9655 Tor. Closes ticket 19450. Based on a patch from "U+039b".
9658 - Remove support for "GET /tor/bytes.txt" DirPort request, and
9659 "GETINFO dir-usage" controller request, which were only available
9660 via a compile-time option in Tor anyway. Feature was added in
9661 0.2.2.1-alpha. Resolves ticket 19035.
9662 - There is no longer a compile-time option to disable support for
9663 TransPort. (If you don't want TransPort, just don't use it.) Patch
9664 from "U+039b". Closes ticket 19449.
9667 - Run more workqueue tests as part of "make check". These had
9668 previously been implemented, but you needed to know special
9669 command-line options to enable them.
9670 - We now have unit tests for our code to reject zlib "compression
9671 bombs". (Fortunately, the code works fine.)
9674 Changes in version 0.2.8.11 - 2016-12-08
9675 Tor 0.2.8.11 backports fixes for additional portability issues that
9676 could prevent Tor from building correctly on OSX Sierra, or with
9677 OpenSSL 1.1. Affected users should upgrade; others can safely stay
9680 o Minor bugfixes (portability):
9681 - Avoid compilation errors when building on OSX Sierra. Sierra began
9682 to support the getentropy() and clock_gettime() APIs, but created
9683 a few problems in doing so. Tor 0.2.9 has a more thorough set of
9684 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
9685 monotonic time interfaces. Fixes bug 20865. Bugfix
9688 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
9689 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
9690 architectures. Closes ticket 20588.
9693 Changes in version 0.2.8.10 - 2016-12-02
9694 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
9695 unusable after they left standby mode. It also backports fixes for
9696 a few portability issues and a small but problematic memory leak.
9698 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
9699 - When Tor leaves standby because of a new application request, open
9700 circuits as needed to serve that request. Previously, we would
9701 potentially wait a very long time. Fixes part of bug 19969; bugfix
9704 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
9705 - Clients now respond to new application stream requests immediately
9706 when they arrive, rather than waiting up to one second before
9707 starting to handle them. Fixes part of bug 19969; bugfix
9710 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
9711 - Work around a bug in the OSX 10.12 SDK that would prevent us from
9712 successfully targeting earlier versions of OSX. Resolves
9715 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
9716 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
9717 20551; bugfix on 0.2.1.1-alpha.
9719 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
9720 - Work around a memory leak in OpenSSL 1.1 when encoding public
9721 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
9723 o Minor features (geoip):
9724 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
9728 Changes in version 0.2.8.9 - 2016-10-17
9729 Tor 0.2.8.9 backports a fix for a security hole in previous versions
9730 of Tor that would allow a remote attacker to crash a Tor client,
9731 hidden service, relay, or authority. All Tor users should upgrade to
9732 this version, or to 0.2.9.4-alpha. Patches will be released for older
9735 o Major features (security fixes, also in 0.2.9.4-alpha):
9736 - Prevent a class of security bugs caused by treating the contents
9737 of a buffer chunk as if they were a NUL-terminated string. At
9738 least one such bug seems to be present in all currently used
9739 versions of Tor, and would allow an attacker to remotely crash
9740 most Tor instances, especially those compiled with extra compiler
9741 hardening. With this defense in place, such bugs can't crash Tor,
9742 though we should still fix them as they occur. Closes ticket
9743 20384 (TROVE-2016-10-001).
9745 o Minor features (geoip):
9746 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
9750 Changes in version 0.2.8.8 - 2016-09-23
9751 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
9752 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
9753 who select public relays as their bridges.
9755 o Major bugfixes (crash):
9756 - Fix a complicated crash bug that could affect Tor clients
9757 configured to use bridges when replacing a networkstatus consensus
9758 in which one of their bridges was mentioned. OpenBSD users saw
9759 more crashes here, but all platforms were potentially affected.
9760 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
9762 o Major bugfixes (relay, OOM handler):
9763 - Fix a timing-dependent assertion failure that could occur when we
9764 tried to flush from a circuit after having freed its cells because
9765 of an out-of-memory condition. Fixes bug 20203; bugfix on
9766 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
9769 o Minor feature (fallback directories):
9770 - Remove broken fallbacks from the hard-coded fallback directory
9771 list. Closes ticket 20190; patch by teor.
9773 o Minor features (geoip):
9774 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
9778 Changes in version 0.2.8.7 - 2016-08-24
9779 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
9780 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
9781 who sets the ReachableAddresses option, and all bridges, are strongly
9782 encouraged to upgrade.
9784 o Directory authority changes:
9785 - The "Tonga" bridge authority has been retired; the new bridge
9786 authority is "Bifroest". Closes tickets 19728 and 19690.
9788 o Major bugfixes (client, security):
9789 - Only use the ReachableAddresses option to restrict the first hop
9790 in a path. In earlier versions of 0.2.8.x, it would apply to
9791 every hop in the path, with a possible degradation in anonymity
9792 for anyone using an uncommon ReachableAddress setting. Fixes bug
9793 19973; bugfix on 0.2.8.2-alpha.
9795 o Minor features (geoip):
9796 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
9799 o Minor bugfixes (compilation):
9800 - Remove an inappropriate "inline" in tortls.c that was causing
9801 warnings on older versions of GCC. Fixes bug 19903; bugfix
9804 o Minor bugfixes (fallback directories):
9805 - Avoid logging a NULL string pointer when loading fallback
9806 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
9807 and 0.2.8.1-alpha. Report and patch by "rubiate".
9810 Changes in version 0.2.8.6 - 2016-08-02
9812 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
9814 The Tor 0.2.8 series improves client bootstrapping performance,
9815 completes the authority-side implementation of improved identity
9816 keys for relays, and includes numerous bugfixes and performance
9817 improvements throughout the program. This release continues to
9818 improve the coverage of Tor's test suite. For a full list of
9819 changes since Tor 0.2.7, see the ReleaseNotes file.
9821 Below is a list of the changes since Tor 0.2.7.
9823 o New system requirements:
9824 - Tor no longer attempts to support platforms where the "time_t"
9825 type is unsigned. (To the best of our knowledge, only OpenVMS does
9826 this, and Tor has never actually built on OpenVMS.) Closes
9828 - Tor no longer supports versions of OpenSSL with a broken
9829 implementation of counter mode. (This bug was present in OpenSSL
9830 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
9831 longer runs with, these versions.
9832 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
9833 later (released in 2008 and 2009 respectively). If you are
9834 building Tor from the git repository instead of from the source
9835 distribution, and your tools are older than this, you will need to
9836 upgrade. Closes ticket 17732.
9838 o Directory authority changes:
9839 - Update the V3 identity key for the dannenberg directory authority:
9840 it was changed on 18 November 2015. Closes task 17906. Patch
9842 - Urras is no longer a directory authority. Closes ticket 19271.
9844 o Major features (directory system):
9845 - Include a trial list of default fallback directories, based on an
9846 opt-in survey of suitable relays. Doing this should make clients
9847 bootstrap more quickly and reliably, and reduce the load on the
9848 directory authorities. Closes ticket 15775. Patch by teor.
9849 Candidates identified using an OnionOO script by weasel, teor,
9850 gsathya, and karsten.
9851 - Previously only relays that explicitly opened a directory port
9852 (DirPort) accepted directory requests from clients. Now all
9853 relays, with and without a DirPort, accept and serve tunneled
9854 directory requests that they receive through their ORPort. You can
9855 disable this behavior using the new DirCache option. Closes
9857 - When bootstrapping multiple consensus downloads at a time, use the
9858 first one that starts downloading, and close the rest. This
9859 reduces failures when authorities or fallback directories are slow
9860 or down. Together with the code for feature 15775, this feature
9861 should reduces failures due to fallback churn. Implements ticket
9862 4483. Patch by teor. Implements IPv4 portions of proposal 210 by
9865 o Major features (security, Linux):
9866 - When Tor starts as root on Linux and is told to switch user ID, it
9867 can now retain the capability to bind to low ports. By default,
9868 Tor will do this only when it's switching user ID and some low
9869 ports have been configured. You can change this behavior with the
9870 new option KeepBindCapabilities. Closes ticket 8195.
9872 o Major bugfixes (client, bootstrapping):
9873 - Check if bootstrap consensus downloads are still needed when the
9874 linked connection attaches. This prevents tor making unnecessary
9875 begindir-style connections, which are the only directory
9876 connections tor clients make since the fix for 18483 was merged.
9877 - Fix some edge cases where consensus download connections may not
9878 have been closed, even though they were not needed. Related to fix
9880 - Make relays retry consensus downloads the correct number of times,
9881 rather than the more aggressive client retry count. Fixes part of
9884 o Major bugfixes (dns proxy mode, crash):
9885 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9886 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9888 o Major bugfixes (ed25519, voting):
9889 - Actually enable support for authorities to match routers by their
9890 Ed25519 identities. Previously, the code had been written, but
9891 some debugging code that had accidentally been left in the
9892 codebase made it stay turned off. Fixes bug 17702; bugfix
9894 - When collating votes by Ed25519 identities, authorities now
9895 include a "NoEdConsensus" flag if the ed25519 value (or lack
9896 thereof) for a server does not reflect the majority consensus.
9897 Related to bug 17668; bugfix on 0.2.7.2-alpha.
9898 - When generating a vote with keypinning disabled, never include two
9899 entries for the same ed25519 identity. This bug was causing
9900 authorities to generate votes that they could not parse when a
9901 router violated key pinning by changing its RSA identity but
9902 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
9903 18318. Bugfix on 0.2.7.2-alpha.
9905 o Major bugfixes (key management):
9906 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9907 pointer to the previous (uninitialized) key value. The impact here
9908 should be limited to a difficult-to-trigger crash, if OpenSSL is
9909 running an engine that makes key generation failures possible, or
9910 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9911 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9914 o Major bugfixes (security, client, DNS proxy):
9915 - Stop a crash that could occur when a client running with DNSPort
9916 received a query with multiple address types, and the first
9917 address type was not supported. Found and fixed by Scott Dial.
9918 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9920 o Major bugfixes (security, compilation):
9921 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
9922 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
9923 cause a compiler warning, thereby making other checks fail, and
9924 needlessly disabling compiler-hardening support. Fixes one case of
9925 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
9926 - Repair hardened builds under the clang compiler. Previously, our
9927 use of _FORTIFY_SOURCE would conflict with clang's address
9928 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
9930 o Major bugfixes (security, pointers):
9931 - Avoid a difficult-to-trigger heap corruption attack when extending
9932 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9933 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9934 Reported by Guido Vranken.
9936 o Major bugfixes (testing):
9937 - Fix a bug that would block 'make test-network-all' on systems where
9938 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
9940 o Major bugfixes (user interface):
9941 - Correctly give a warning in the cases where a relay is specified
9942 by nickname, and one such relay is found, but it is not officially
9943 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
9945 o Minor features (accounting):
9946 - Added two modes to the AccountingRule option: One for limiting
9947 only the number of bytes sent ("AccountingRule out"), and one for
9948 limiting only the number of bytes received ("AccountingRule in").
9949 Closes ticket 15989; patch from "unixninja92".
9951 o Minor features (bug-resistance):
9952 - Make Tor survive errors involving connections without a
9953 corresponding event object. Previously we'd fail with an
9954 assertion; now we produce a log message. Related to bug 16248.
9955 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
9956 level code, to harden against accidental failures to NUL-
9957 terminate. Part of ticket 17852. Patch from jsturgix. Found
9960 o Minor features (build):
9961 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
9962 as having possible IPFW support. Closes ticket 18448. Patch from
9964 - Since our build process now uses "make distcheck", we no longer
9965 force "make dist" to depend on "make check". Closes ticket 17893;
9966 patch from "cypherpunks".
9967 - Tor now builds once again with the recent OpenSSL 1.1 development
9968 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev). We have been
9969 tracking OpenSSL 1.1 development as it has progressed, and fixing
9970 numerous compatibility issues as they arose. See tickets
9971 17549, 17921, 17984, 19499, and 18286.
9972 - When building manual pages, set the timezone to "UTC", so that the
9973 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
9974 Patch from intrigeri.
9976 o Minor features (clients):
9977 - Make clients, onion services, and bridge relays always use an
9978 encrypted begindir connection for directory requests. Resolves
9979 ticket 18483. Patch by teor.
9981 o Minor features (controller):
9982 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
9983 controllers can examine the the reject rules added by
9984 ExitPolicyRejectPrivate. This makes it easier for stem to display
9986 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
9987 tickets 16774 and 17817. Patch by George Tankersley.
9988 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
9989 service descriptor from a service's local hidden service
9990 descriptor cache. Closes ticket 14846.
9992 o Minor features (crypto):
9993 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
9994 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
9996 - Improve performance when hashing non-multiple of 8 sized buffers,
9997 based on Andrew Moon's public domain SipHash-2-4 implementation.
9998 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
9999 - Validate the hard-coded Diffie-Hellman parameters and ensure that
10000 p is a safe prime, and g is a suitable generator. Closes
10002 - When allocating a digest state object, allocate no more space than
10003 we actually need. Previously, we would allocate as much space as
10004 the state for the largest algorithm would need. This change saves
10005 up to 672 bytes per circuit. Closes ticket 17796.
10007 o Minor features (directory downloads):
10008 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
10009 directory mirrors. The default is 1; set it to 0 to disable
10010 fallbacks. Implements ticket 17576. Patch by teor.
10011 - Wait for busy authorities and fallback directories to become non-
10012 busy when bootstrapping. (A similar change was made in 6c443e987d
10013 for directory caches chosen from the consensus.) Closes ticket
10014 17864; patch by teor.
10016 o Minor features (geoip):
10017 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
10020 o Minor features (hidden service directory):
10021 - Streamline relay-side hsdir handling: when relays consider whether
10022 to accept an uploaded hidden service descriptor, they no longer
10023 check whether they are one of the relays in the network that is
10024 "supposed" to handle that descriptor. Implements ticket 18332.
10026 o Minor features (IPv6):
10027 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
10028 to 1, tor prefers IPv6 directory addresses.
10029 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
10030 avoids using IPv4 for client OR and directory connections.
10031 - Add address policy assume_action support for IPv6 addresses.
10032 - Add an argument 'ipv6=address:orport' to the DirAuthority and
10033 FallbackDir torrc options, to specify an IPv6 address for an
10034 authority or fallback directory. Add hard-coded ipv6 addresses for
10035 directory authorities that have them. Closes ticket 17327; patch
10036 from Nick Mathewson and teor.
10037 - Allow users to configure directory authorities and fallback
10038 directory servers with IPv6 addresses and ORPorts. Resolves
10040 - Limit IPv6 mask bits to 128.
10041 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
10042 17638; bugfix on 0.0.2pre8. Patch by teor.
10043 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
10044 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
10045 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
10046 - Warn when comparing against an AF_UNSPEC address in a policy, it's
10047 almost always a bug. Closes ticket 17863; patch by teor.
10048 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
10049 17060; bugfix on 0.2.1.3-alpha. Patch by teor.
10051 o Minor features (Linux seccomp2 sandbox):
10052 - Reject attempts to change our Address with "Sandbox 1" enabled.
10053 Changing Address with Sandbox turned on would never actually work,
10054 but previously it would fail in strange and confusing ways. Found
10055 while fixing 18548.
10057 o Minor features (logging):
10058 - When logging to syslog, allow a tag to be added to the syslog
10059 identity (the string prepended to every log message). The tag can
10060 be configured with SyslogIdentityTag and defaults to none. Setting
10061 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
10064 o Minor features (portability):
10065 - Use timingsafe_memcmp() where available. Closes ticket 17944;
10066 patch from <logan@hackers.mu>.
10068 o Minor features (relay, address discovery):
10069 - Add a family argument to get_interface_addresses_raw() and
10070 subfunctions to make network interface address interogation more
10071 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
10072 types of interfaces from the operating system. Resolves
10074 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
10075 fails to enumerate interface addresses using the platform-specific
10076 API, have it rely on the UDP socket fallback technique to try and
10077 find out what IP addresses (both IPv4 and IPv6) our machine has.
10078 Resolves ticket 17951.
10080 o Minor features (replay cache):
10081 - The replay cache now uses SHA256 instead of SHA1. Implements
10082 feature 8961. Patch by teor, issue reported by rransom.
10084 o Minor features (robustness):
10085 - Exit immediately with an error message if the code attempts to use
10086 Libevent without having initialized it. This should resolve some
10087 frequently-made mistakes in our unit tests. Closes ticket 18241.
10089 o Minor features (security, clock):
10090 - Warn when the system clock appears to move back in time (when the
10091 state file was last written in the future). Tor doesn't know that
10092 consensuses have expired if the clock is in the past. Patch by
10093 teor. Implements ticket 17188.
10095 o Minor features (security, exit policies):
10096 - ExitPolicyRejectPrivate now rejects more private addresses by
10097 default. Specifically, it now rejects the relay's outbound bind
10098 addresses (if configured), and the relay's configured port
10099 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
10100 0.2.0.11-alpha. Patch by teor.
10102 o Minor features (security, memory erasure):
10103 - Make memwipe() do nothing when passed a NULL pointer or buffer of
10104 zero size. Check size argument to memwipe() for underflow. Fixes
10105 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
10107 - Set the unused entries in a smartlist to NULL. This helped catch
10108 a (harmless) bug, and shouldn't affect performance too much.
10109 Implements ticket 17026.
10110 - Use SecureMemoryWipe() function to securely clean memory on
10111 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
10112 Implements feature 17986.
10113 - Use explicit_bzero or memset_s when present. Previously, we'd use
10114 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
10115 from <logan@hackers.mu> and <selven@hackers.mu>.
10117 o Minor features (security, RNG):
10118 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
10119 positively are not allowed to fail. Previously we depended on
10120 internal details of OpenSSL's behavior. Closes ticket 17686.
10121 - Never use the system entropy output directly for anything besides
10122 seeding the PRNG. When we want to generate important keys, instead
10123 of using system entropy directly, we now hash it with the PRNG
10124 stream. This may help resist certain attacks based on broken OS
10125 entropy implementations. Closes part of ticket 17694.
10126 - Use modern system calls (like getentropy() or getrandom()) to
10127 generate strong entropy on platforms that have them. Closes
10130 o Minor features (security, win32):
10131 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
10132 attack. Fixes bug 18123; bugfix on all tor versions. Patch
10135 o Minor features (unix domain sockets):
10136 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
10137 Unix domain sockets without checking the permissions on the parent
10138 directory. (Tor checks permissions by default because some
10139 operating systems only check permissions on the parent directory.
10140 However, some operating systems do look at permissions on the
10141 socket, and tor's default check is unneeded.) Closes ticket 18458.
10144 o Minor features (unix file permissions):
10145 - Defer creation of Unix sockets until after setuid. This avoids
10146 needing CAP_CHOWN and CAP_FOWNER when using systemd's
10147 CapabilityBoundingSet, or chown and fowner when using SELinux.
10148 Implements part of ticket 17562. Patch from Jamie Nguyen.
10149 - If any directory created by Tor is marked as group readable, the
10150 filesystem group is allowed to be either the default GID or the
10151 root user. Allowing root to read the DataDirectory prevents the
10152 need for CAP_READ_SEARCH when using systemd's
10153 CapabilityBoundingSet, or dac_read_search when using SELinux.
10154 Implements part of ticket 17562. Patch from Jamie Nguyen.
10155 - Introduce a new DataDirectoryGroupReadable option. If it is set to
10156 1, the DataDirectory will be made readable by the default GID.
10157 Implements part of ticket 17562. Patch from Jamie Nguyen.
10159 o Minor bugfixes (accounting):
10160 - The max bandwidth when using 'AccountRule sum' is now correctly
10161 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
10162 from "unixninja92".
10164 o Minor bugfixes (assert, portability):
10165 - Fix an assertion failure in memarea.c on systems where "long" is
10166 shorter than the size of a pointer. Fixes bug 18716; bugfix
10169 o Minor bugfixes (bootstrap):
10170 - Consistently use the consensus download schedule for authority
10171 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
10173 o Minor bugfixes (build):
10174 - Avoid spurious failures from configure files related to calling
10175 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
10176 0.2.0.1-alpha. Patch from "cypherpunks".
10177 - Do not link the unit tests against both the testing and non-
10178 testing versions of the static libraries. Fixes bug 18490; bugfix
10180 - Resolve warnings when building on systems that are concerned with
10181 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
10183 - Silence spurious clang-scan warnings in the ed25519_donna code by
10184 explicitly initializing some objects. Fixes bug 18384; bugfix on
10185 0.2.7.2-alpha. Patch by teor.
10186 - When libscrypt.h is found, but no libscrypt library can be linked,
10187 treat libscrypt as absent. Fixes bug 19161; bugfix
10189 - Cause the unit tests to compile correctly on mingw64 versions that
10190 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
10191 - Don't try to use the pthread_condattr_setclock() function unless
10192 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
10193 17819; bugfix on 0.2.6.3-alpha.
10194 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
10196 - Fix search for libevent libraries on OpenBSD (and other systems
10197 that install libevent 1 and libevent 2 in parallel). Fixes bug
10198 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
10199 - Isolate environment variables meant for tests from the rest of the
10200 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
10201 - Mark all object files that include micro-revision.i as depending
10202 on it, so as to make parallel builds more reliable. Fixes bug
10203 17826; bugfix on 0.2.5.1-alpha.
10204 - Remove config.log only from make distclean, not from make clean.
10205 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
10206 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
10208 - Remove an #endif from configure.ac so that we correctly detect the
10209 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
10212 o Minor bugfixes (client, bootstrap):
10213 - Count receipt of new microdescriptors as progress towards
10214 bootstrapping. Previously, with EntryNodes set, Tor might not
10215 successfully repopulate the guard set on bootstrapping. Fixes bug
10216 16825; bugfix on 0.2.3.1-alpha.
10218 o Minor bugfixes (code correctness):
10219 - Fix a bad memory handling bug that would occur if we had queued a
10220 cell on a channel's incoming queue. Fortunately, we can't actually
10221 queue a cell like that as our code is constructed today, but it's
10222 best to avoid this kind of error, even if there isn't any code
10223 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
10224 - Assert that allocated memory held by the reputation code is freed
10225 according to its internal counters. Fixes bug 17753; bugfix
10227 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
10229 - Update to the latest version of Trunnel, which tries harder to
10230 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
10231 by clang address sanitizer. Fixes bug 18373; bugfix
10233 - When closing an entry connection, generate a warning if we should
10234 have sent an end cell for it but we haven't. Fixes bug 17876;
10235 bugfix on 0.2.3.2-alpha.
10237 o Minor bugfixes (configuration):
10238 - Fix a tiny memory leak when parsing a port configuration ending in
10239 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
10241 o Minor bugfixes (containers):
10242 - If we somehow attempt to construct a heap with more than
10243 1073741822 elements, avoid an integer overflow when maintaining
10244 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
10246 o Minor bugfixes (controller, microdescriptors):
10247 - Make GETINFO dir/status-vote/current/consensus conform to the
10248 control specification by returning "551 Could not open cached
10249 consensus..." when not caching consensuses. Fixes bug 18920;
10250 bugfix on 0.2.2.6-alpha.
10252 o Minor bugfixes (crypto):
10253 - Check the return value of HMAC() and assert on failure. Fixes bug
10254 17658; bugfix on 0.2.3.6-alpha. Patch by teor.
10256 o Minor bugfixes (directories):
10257 - When fetching extrainfo documents, compare their SHA256 digests
10258 and Ed25519 signing key certificates with the routerinfo that led
10259 us to fetch them, rather than with the most recent routerinfo.
10260 Otherwise we generate many spurious warnings about mismatches.
10261 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
10262 - When generating a URL for a directory server on an IPv6 address,
10263 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
10264 on 0.2.3.9-alpha. Patch from Malek.
10266 o Minor bugfixes (downloading):
10267 - Predict more correctly whether we'll be downloading over HTTP when
10268 we determine the maximum length of a URL. This should avoid a
10269 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
10272 o Minor bugfixes (exit policies, security):
10273 - Refresh an exit relay's exit policy when interface addresses
10274 change. Previously, tor only refreshed the exit policy when the
10275 configured external address changed. Fixes bug 18208; bugfix on
10276 0.2.7.3-rc. Patch by teor.
10278 o Minor bugfixes (fallback directories):
10279 - Mark fallbacks as "too busy" when they return a 503 response,
10280 rather than just marking authorities. Fixes bug 17572; bugfix on
10281 0.2.4.7-alpha. Patch by teor.
10282 - When requesting extrainfo descriptors from a trusted directory
10283 server, check whether it is an authority or a fallback directory
10284 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
10285 0.2.4.7-alpha. Reported by atagar, patch by teor.
10287 o Minor bugfixes (hidden service, client):
10288 - Handle the case where the user makes several fast consecutive
10289 requests to the same .onion address. Previously, the first six
10290 requests would each trigger a descriptor fetch, each picking a
10291 directory (there are 6 overall) and the seventh one would fail
10292 because no directories were left, thereby triggering a close on
10293 all current directory connections asking for the hidden service.
10294 The solution here is to not close the connections if we have
10295 pending directory fetches. Fixes bug 15937; bugfix
10298 o Minor bugfixes (hidden service, control port):
10299 - Add the onion address to the HS_DESC event for the UPLOADED action
10300 both on success or failure. It was previously hardcoded with
10301 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
10303 o Minor bugfixes (hidden service, directory):
10304 - Bridges now refuse "rendezvous2" (hidden service descriptor)
10305 publish attempts. Suggested by ticket 18332.
10307 o Minor bugfixes (IPv6):
10308 - Update the limits in max_dl_per_request for IPv6 address length.
10309 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
10311 o Minor bugfixes (Linux seccomp2 sandbox):
10312 - Allow more syscalls when running with "Sandbox 1" enabled:
10313 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
10314 some systems, these are required for Tor to start. Fixes bug
10315 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
10316 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
10317 so that get_interface_address6_via_udp_socket_hack() can work.
10318 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
10319 - Allow the setrlimit syscall, and the prlimit and prlimit64
10320 syscalls, which some libc implementations use under the hood.
10321 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
10322 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
10323 enabled and no DNS resolvers configured. This should help TAILS
10324 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
10325 - Fix a crash when using offline master ed25519 keys with the Linux
10326 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
10327 - Allow statistics to be written to disk when "Sandbox 1" is
10328 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
10329 0.2.6.1-alpha respectively.
10331 o Minor bugfixes (logging):
10332 - In log messages that include a function name, use __FUNCTION__
10333 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
10334 with clang __PRETTY_FUNCTION__ has extra information we don't
10335 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
10337 - Remove needless quotes from a log message about unparseable
10338 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
10339 - Scrub service name in "unrecognized service ID" log messages.
10340 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
10341 - When logging information about an unparsable networkstatus vote or
10342 consensus, do not say "vote" when we mean consensus. Fixes bug
10343 18368; bugfix on 0.2.0.8-alpha.
10344 - When we can't generate a signing key because OfflineMasterKey is
10345 set, do not imply that we should have been able to load it. Fixes
10346 bug 18133; bugfix on 0.2.7.2-alpha.
10347 - When logging a malformed hostname received through socks4, scrub
10348 it if SafeLogging says we should. Fixes bug 17419; bugfix
10351 o Minor bugfixes (memory safety):
10352 - Avoid freeing an uninitialized pointer when opening a socket fails
10353 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
10354 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
10356 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
10357 18672; bugfix on 0.2.5.1-alpha.
10358 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
10361 o Minor bugfixes (pluggable transports):
10362 - Avoid reporting a spurious error when we decide that we don't need
10363 to terminate a pluggable transport because it has already exited.
10364 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
10366 o Minor bugfixes (pointer arithmetic):
10367 - Fix a bug in memarea_alloc() that could have resulted in remote
10368 heap write access, if Tor had ever passed an unchecked size to
10369 memarea_alloc(). Fortunately, all the sizes we pass to
10370 memarea_alloc() are pre-checked to be less than 128 kilobytes.
10371 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
10374 o Minor bugfixes (private directory):
10375 - Prevent a race condition when creating private directories. Fixes
10376 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
10377 Patch from jsturgix. Found with Flawfinder.
10379 o Minor bugfixes (relays):
10380 - Check that both the ORPort and DirPort (if present) are reachable
10381 before publishing a relay descriptor. Otherwise, relays publish a
10382 descriptor with DirPort 0 when the DirPort reachability test takes
10383 longer than the ORPort reachability test. Fixes bug 18050; bugfix
10384 on 0.1.0.1-rc. Reported by "starlight", patch by teor.
10385 - Resolve some edge cases where we might launch an ORPort
10386 reachability check even when DisableNetwork is set. Noticed while
10387 fixing bug 18616; bugfix on 0.2.3.9-alpha.
10389 o Minor bugfixes (relays, hidden services):
10390 - Refuse connection requests to private OR addresses unless
10391 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
10392 then refuse to send any cells to a private address. Fixes bugs
10393 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by teor.
10395 o Minor bugfixes (security, hidden services):
10396 - Prevent hidden services connecting to client-supplied rendezvous
10397 addresses that are reserved as internal or multicast. Fixes bug
10398 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
10400 o Minor bugfixes (statistics):
10401 - Consistently check for overflow in round_*_to_next_multiple_of
10402 functions, and add unit tests with additional and maximal values.
10403 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
10404 - Handle edge cases in the laplace functions: avoid division by
10405 zero, avoid taking the log of zero, and silence clang type
10406 conversion warnings using round and trunc. Add unit tests for edge
10407 cases with maximal values. Fixes part of bug 13192; bugfix
10409 - We now include consensus downloads via IPv6 in our directory-
10410 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
10412 o Minor bugfixes (test networks, IPv6):
10413 - Allow internal IPv6 addresses in descriptors in test networks.
10414 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
10417 o Minor bugfixes (testing):
10418 - Check the full results of SHA256 and SHA512 digests in the unit
10419 tests. Bugfix on 0.2.2.4-alpha. Patch by teor.
10420 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
10422 - Fix a small memory leak that would occur when the
10423 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
10424 bugfix on 0.2.5.2-alpha.
10425 - Make unit tests pass on IPv6-only systems, and systems without
10426 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
10427 bugfix on 0.2.7.3-rc. Patch by teor.
10428 - The test for log_heartbeat was incorrectly failing in timezones
10429 with non-integer offsets. Instead of comparing the end of the time
10430 string against a constant, compare it to the output of
10431 format_local_iso_time when given the correct input. Fixes bug
10432 18039; bugfix on 0.2.5.4-alpha.
10433 - We no longer disable assertions in the unit tests when coverage is
10434 enabled. Instead, we require you to say --disable-asserts-in-tests
10435 to the configure script if you need assertions disabled in the
10436 unit tests (for example, if you want to perform branch coverage).
10437 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
10439 o Minor bugfixes (time handling):
10440 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
10441 field. Otherwise, our unit tests crash on Windows. Fixes bug
10442 18977; bugfix on 0.2.2.25-alpha.
10443 - Avoid overflow in tor_timegm when parsing dates in and after 2038
10444 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
10445 0.0.2pre14. Patch by teor.
10447 o Minor bugfixes (tor-gencert):
10448 - Correctly handle the case where an authority operator enters a
10449 passphrase but sends an EOF before sending a newline. Fixes bug
10450 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
10452 o Code simplification and refactoring:
10453 - Clean up a little duplicated code in
10454 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
10456 - Decouple the list of streams waiting to be attached to circuits
10457 from the overall connection list. This change makes it possible to
10458 attach streams quickly while simplifying Tor's callgraph and
10459 avoiding O(N) scans of the entire connection list. Closes
10461 - Extract the more complicated parts of circuit_mark_for_close()
10462 into a new function that we run periodically before circuits are
10463 freed. This change removes more than half of the functions
10464 currently in the "blob". Closes ticket 17218.
10465 - Move logging of redundant policy entries in
10466 policies_parse_exit_policy_internal into its own function. Closes
10467 ticket 17608; patch from "juce".
10468 - Quote all the string interpolations in configure.ac -- even those
10469 which we are pretty sure can't contain spaces. Closes ticket
10470 17744. Patch from zerosion.
10471 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
10472 use them. Closes ticket 17926.
10473 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
10474 inplace, so there's no need to have a separate implementation for
10475 the non-inplace code. Closes ticket 18258. Patch from Malek.
10476 - Simplify return types for some crypto functions that can't
10477 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
10478 - When a direct directory request fails immediately on launch,
10479 instead of relaunching that request from inside the code that
10480 launches it, instead mark the connection for teardown. This change
10481 simplifies Tor's callback and prevents the directory-request
10482 launching code from invoking itself recursively. Closes
10486 - Add a description of the correct use of the '--keygen' command-
10487 line option. Closes ticket 17583; based on text by 's7r'.
10488 - Change build messages to refer to "Fedora" instead of "Fedora
10489 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
10490 Patches from "icanhasaccount" and "cypherpunks".
10491 - Document the contents of the 'datadir/keys' subdirectory in the
10492 manual page. Closes ticket 17621.
10493 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
10494 - Explain actual minima for BandwidthRate. Closes ticket 16382.
10495 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
10496 - Mention torspec URL in the manpage and point the reader to it
10497 whenever we mention a document that belongs in torspce. Fixes
10499 - Stop recommending use of nicknames to identify relays in our
10500 MapAddress documentation. Closes ticket 18312.
10502 o Removed features:
10503 - Remove client-side support for connecting to Tor relays running
10504 versions of Tor before 0.2.3.6-alpha. These relays didn't support
10505 the v3 TLS handshake protocol, and are no longer allowed on the
10506 Tor network. Implements the client side of ticket 11150. Based on
10507 patches by Tom van der Woerdt.
10508 - We no longer maintain an internal freelist in memarea.c.
10509 Allocators should be good enough to make this code unnecessary,
10510 and it's doubtful that it ever had any performance benefit.
10513 - Add unit tests to check for common RNG failure modes, such as
10514 returning all zeroes, identical values, or incrementing values
10515 (OpenSSL's rand_predictable feature). Patch by teor.
10516 - Always test both ed25519 backends, so that we can be sure that our
10517 batch-open replacement code works. Part of ticket 16794.
10518 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
10519 portion of ticket 16831.
10520 - Fix several warnings from clang's address sanitizer produced in
10522 - Log more information when the backtrace tests fail. Closes ticket
10523 17892. Patch from "cypherpunks."
10524 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
10525 util_format.c, directory.c, and options_validate.c. Closes tickets
10526 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
10528 - Treat backtrace test failures as expected on FreeBSD until we
10529 solve bug 17808. Closes ticket 18204.
10530 - Unit tests for directory_handle_command_get. Closes ticket 17004.
10531 Patch from Reinaldo de Souza Jr.
10534 Changes in version 0.2.7.6 - 2015-12-10
10535 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
10536 well as a minor bug in hidden service reliability.
10538 o Major bugfixes (guard selection):
10539 - Actually look at the Guard flag when selecting a new directory
10540 guard. When we implemented the directory guard design, we
10541 accidentally started treating all relays as if they have the Guard
10542 flag during guard selection, leading to weaker anonymity and worse
10543 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
10546 o Minor features (geoip):
10547 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
10550 o Minor bugfixes (compilation):
10551 - When checking for net/pfvar.h, include netinet/in.h if possible.
10552 This fixes transparent proxy detection on OpenBSD. Fixes bug
10553 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
10554 - Fix a compilation warning with Clang 3.6: Do not check the
10555 presence of an address which can never be NULL. Fixes bug 17781.
10557 o Minor bugfixes (correctness):
10558 - When displaying an IPv6 exit policy, include the mask bits
10559 correctly even when the number is greater than 31. Fixes bug
10560 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
10561 - The wrong list was used when looking up expired intro points in a
10562 rend service object, causing what we think could be reachability
10563 issues for hidden services, and triggering a BUG log. Fixes bug
10564 16702; bugfix on 0.2.7.2-alpha.
10565 - Fix undefined behavior in the tor_cert_checksig function. Fixes
10566 bug 17722; bugfix on 0.2.7.2-alpha.
10569 Changes in version 0.2.7.5 - 2015-11-20
10570 The Tor 0.2.7 release series is dedicated to the memory of Tor user
10571 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
10572 tirelessly to advocate human rights regardless of national borders,
10573 and oppose the encroachments of mass surveillance. He opposed national
10574 exceptionalism, he brought clarity to legal and policy debates, he
10575 understood and predicted the impact of mass surveillance on the world,
10576 and he laid the groundwork for resisting it. While serving on the Tor
10577 Project's board of directors, he brought us his uncompromising focus
10578 on technical excellence in the service of humankind. Caspar was an
10579 inimitable force for good and a wonderful friend. He was kind,
10580 humorous, generous, gallant, and believed we should protect one
10581 another without exception. We honor him here for his ideals, his
10582 efforts, and his accomplishments. Please honor his memory with works
10583 that would make him proud.
10585 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
10587 The 0.2.7 series adds a more secure identity key type for relays,
10588 improves cryptography performance, resolves several longstanding
10589 hidden-service performance issues, improves controller support for
10590 hidden services, and includes small bugfixes and performance
10591 improvements throughout the program. This release series also includes
10592 more tests than before, and significant simplifications to which parts
10593 of Tor invoke which others. For a full list of changes, see below.
10595 o New system requirements:
10596 - Tor no longer includes workarounds to support Libevent versions
10597 before 1.3e. Libevent 2.0 or later is recommended. Closes
10599 - Tor no longer supports copies of OpenSSL that are missing support
10600 for Elliptic Curve Cryptography. (We began using ECC when
10601 available in 0.2.4.8-alpha, for more safe and efficient key
10602 negotiation.) In particular, support for at least one of P256 or
10603 P224 is now required, with manual configuration needed if only
10604 P224 is available. Resolves ticket 16140.
10605 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
10606 on an operating system that has not upgraded to OpenSSL 1.0 or
10607 later, and you compile Tor from source, you will need to install a
10608 more recent OpenSSL to link Tor against.) These versions of
10609 OpenSSL are still supported by the OpenSSL, but the numerous
10610 cryptographic improvements in later OpenSSL releases makes them a
10611 clear choice. Resolves ticket 16034.
10613 o Major features (controller):
10614 - Add the ADD_ONION and DEL_ONION commands that allow the creation
10615 and management of hidden services via the controller. Closes
10617 - New "GETINFO onions/current" and "GETINFO onions/detached"
10618 commands to get information about hidden services created via the
10619 controller. Part of ticket 6411.
10620 - New HSFETCH command to launch a request for a hidden service
10621 descriptor. Closes ticket 14847.
10622 - New HSPOST command to upload a hidden service descriptor. Closes
10623 ticket 3523. Patch by "DonnchaC".
10625 o Major features (Ed25519 identity keys, Proposal 220):
10626 - Add support for offline encrypted Ed25519 master keys. To use this
10627 feature on your tor relay, run "tor --keygen" to make a new master
10628 key (or to make a new signing key if you already have a master
10629 key). Closes ticket 13642.
10630 - All relays now maintain a stronger identity key, using the Ed25519
10631 elliptic curve signature format. This master key is designed so
10632 that it can be kept offline. Relays also generate an online
10633 signing key, and a set of other Ed25519 keys and certificates.
10634 These are all automatically regenerated and rotated as needed.
10635 Implements part of ticket 12498.
10636 - Directory authorities now vote on Ed25519 identity keys along with
10637 RSA1024 keys. Implements part of ticket 12498.
10638 - Directory authorities track which Ed25519 identity keys have been
10639 used with which RSA1024 identity keys, and do not allow them to
10640 vary freely. Implements part of ticket 12498.
10641 - Microdescriptors now include Ed25519 identity keys. Implements
10642 part of ticket 12498.
10643 - Add a --newpass option to allow changing or removing the
10644 passphrase of an encrypted key with tor --keygen. Implements part
10646 - Add a new OfflineMasterKey option to tell Tor never to try loading
10647 or generating a secret Ed25519 identity key. You can use this in
10648 combination with tor --keygen to manage offline and/or encrypted
10649 Ed25519 keys. Implements ticket 16944.
10650 - On receiving a HUP signal, check to see whether the Ed25519
10651 signing key has changed, and reload it if so. Closes ticket 16790.
10652 - Significant usability improvements for Ed25519 key management. Log
10653 messages are better, and the code can recover from far more
10654 failure conditions. Thanks to "s7r" for reporting and diagnosing
10657 o Major features (ECC performance):
10658 - Improve the runtime speed of Ed25519 signature verification by
10659 using Ed25519-donna's batch verification support. Implements
10661 - Improve the speed of Ed25519 operations and Curve25519 keypair
10662 generation when built targeting 32 bit x86 platforms with SSE2
10663 available. Implements ticket 16535.
10664 - Improve the runtime speed of Ed25519 operations by using the
10665 public-domain Ed25519-donna by Andrew M. ("floodyberry").
10666 Implements ticket 16467.
10667 - Improve the runtime speed of the ntor handshake by using an
10668 optimized curve25519 basepoint scalarmult implementation from the
10669 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
10670 ideas by Adam Langley. Implements ticket 9663.
10672 o Major features (Hidden services):
10673 - Hidden services, if using the EntryNodes option, are required to
10674 use more than one EntryNode, in order to avoid a guard discovery
10675 attack. (This would only affect people who had configured hidden
10676 services and manually specified the EntryNodes option with a
10677 single entry-node. The impact was that it would be easy to
10678 remotely identify the guard node used by such a hidden service.
10679 See ticket for more information.) Fixes ticket 14917.
10680 - Add the torrc option HiddenServiceNumIntroductionPoints, to
10681 specify a fixed number of introduction points. Its maximum value
10682 is 10 and default is 3. Using this option can increase a hidden
10683 service's reliability under load, at the cost of making it more
10684 visible that the hidden service is facing extra load. Closes
10686 - Remove the adaptive algorithm for choosing the number of
10687 introduction points, which used to change the number of
10688 introduction points (poorly) depending on the number of
10689 connections the HS sees. Closes ticket 4862.
10691 o Major features (onion key cross-certification):
10692 - Relay descriptors now include signatures of their own identity
10693 keys, made using the TAP and ntor onion keys. These signatures
10694 allow relays to prove ownership of their own onion keys. Because
10695 of this change, microdescriptors will no longer need to include
10696 RSA identity keys. Implements proposal 228; closes ticket 12499.
10698 o Major bugfixes (client-side privacy, also in 0.2.6.9):
10699 - Properly separate out each SOCKSPort when applying stream
10700 isolation. The error occurred because each port's session group
10701 was being overwritten by a default value when the listener
10702 connection was initialized. Fixes bug 16247; bugfix on
10703 0.2.6.3-alpha. Patch by "jojelino".
10705 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
10706 - Stop refusing to store updated hidden service descriptors on a
10707 client. This reverts commit 9407040c59218 (which indeed fixed bug
10708 14219, but introduced a major hidden service reachability
10709 regression detailed in bug 16381). This is a temporary fix since
10710 we can live with the minor issue in bug 14219 (it just results in
10711 some load on the network) but the regression of 16381 is too much
10712 of a setback. First-round fix for bug 16381; bugfix
10715 o Major bugfixes (hidden services):
10716 - Revert commit that made directory authorities assign the HSDir
10717 flag to relays without a DirPort; this was bad because such relays
10718 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
10720 - When cannibalizing a circuit for an introduction point, always
10721 extend to the chosen exit node (creating a 4 hop circuit).
10722 Previously Tor would use the current circuit exit node, which
10723 changed the original choice of introduction point, and could cause
10724 the hidden service to skip excluded introduction points or
10725 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
10728 o Major bugfixes (memory leaks):
10729 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
10730 17398; bugfix on 0.2.6.1-alpha.
10732 o Major bugfixes (open file limit):
10733 - The open file limit wasn't checked before calling
10734 tor_accept_socket_nonblocking(), which would make Tor exceed the
10735 limit. Now, before opening a new socket, Tor validates the open
10736 file limit just before, and if the max has been reached, return an
10737 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
10739 o Major bugfixes (security, correctness):
10740 - Fix an error that could cause us to read 4 bytes before the
10741 beginning of an openssl string. This bug could be used to cause
10742 Tor to crash on systems with unusual malloc implementations, or
10743 systems with unusual hardening installed. Fixes bug 17404; bugfix
10746 o Major bugfixes (stability, also in 0.2.6.10):
10747 - Stop crashing with an assertion failure when parsing certain kinds
10748 of malformed or truncated microdescriptors. Fixes bug 16400;
10749 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
10750 by "cypherpunks_backup".
10751 - Stop random client-side assertion failures that could occur when
10752 connecting to a busy hidden service, or connecting to a hidden
10753 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
10756 o Minor features (client, SOCKS):
10757 - Add GroupWritable and WorldWritable options to unix-socket based
10758 SocksPort and ControlPort options. These options apply to a single
10759 socket, and override {Control,Socks}SocketsGroupWritable. Closes
10761 - Relax the validation done to hostnames in SOCKS5 requests, and
10762 allow a single trailing '.' to cope with clients that pass FQDNs
10763 using that syntax to explicitly indicate that the domain name is
10764 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
10765 - Relax the validation of hostnames in SOCKS5 requests, allowing the
10766 character '_' to appear, in order to cope with domains observed in
10767 the wild that are serving non-RFC compliant records. Resolves
10770 o Minor features (client-side privacy):
10771 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
10772 lifespan when IsolateSOCKSAuth and streams with SOCKS
10773 authentication are attached to the circuit. This allows
10774 applications like TorBrowser to manage circuit lifetime on their
10775 own. Implements feature 15482.
10776 - When logging malformed hostnames from SOCKS5 requests, respect
10777 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
10779 o Minor features (clock-jump tolerance):
10780 - Recover better when our clock jumps back many hours, like might
10781 happen for Tails or Whonix users who start with a very wrong
10782 hardware clock, use Tor to discover a more accurate time, and then
10783 fix their clock. Resolves part of ticket 8766.
10785 o Minor features (command-line interface):
10786 - Make --hash-password imply --hush to prevent unnecessary noise.
10787 Closes ticket 15542. Patch from "cypherpunks".
10788 - Print a warning whenever we find a relative file path being used
10789 as torrc option. Resolves issue 14018.
10791 o Minor features (compilation):
10792 - Give a warning as early as possible when trying to build with an
10793 unsupported OpenSSL version. Closes ticket 16901.
10794 - Use C99 variadic macros when the compiler is not GCC. This avoids
10795 failing compilations on MSVC, and fixes a log-file-based race
10796 condition in our old workarounds. Original patch from Gisle Vanem.
10798 o Minor features (control protocol):
10799 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
10800 the control protocol. Resolves ticket 15358.
10802 o Minor features (controller):
10803 - Add DirAuthority lines for default directory authorities to the
10804 output of the "GETINFO config/defaults" command if not already
10805 present. Implements ticket 14840.
10806 - Controllers can now use "GETINFO hs/client/desc/id/..." to
10807 retrieve items from the client's hidden service descriptor cache.
10808 Closes ticket 14845.
10809 - Implement a new controller command "GETINFO status/fresh-relay-
10810 descs" to fetch a descriptor/extrainfo pair that was generated on
10811 demand just for the controller's use. Implements ticket 14784.
10813 o Minor features (directory authorities):
10814 - Directory authorities no longer vote against the "Fast", "Stable",
10815 and "HSDir" flags just because they were going to vote against
10816 "Running": if the consensus turns out to be that the router was
10817 running, then the authority's vote should count. Patch from Peter
10818 Retzlaff; closes issue 8712.
10820 o Minor features (directory authorities, security, also in 0.2.6.9):
10821 - The HSDir flag given by authorities now requires the Stable flag.
10822 For the current network, this results in going from 2887 to 2806
10823 HSDirs. Also, it makes it harder for an attacker to launch a sybil
10824 attack by raising the effort for a relay to become Stable to
10825 require at the very least 7 days, while maintaining the 96 hours
10826 uptime requirement for HSDir. Implements ticket 8243.
10828 o Minor features (DoS-resistance):
10829 - Make it harder for attackers to overload hidden services with
10830 introductions, by blocking multiple introduction requests on the
10831 same circuit. Resolves ticket 15515.
10833 o Minor features (geoip):
10834 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
10837 o Minor features (hidden services):
10838 - Add the new options "HiddenServiceMaxStreams" and
10839 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
10840 limit the maximum number of simultaneous streams per circuit, and
10841 optionally tear down the circuit when the limit is exceeded. Part
10843 - Client now uses an introduction point failure cache to know when
10844 to fetch or keep a descriptor in their cache. Previously, failures
10845 were recorded implicitly, but not explicitly remembered. Closes
10847 - Relays need to have the Fast flag to get the HSDir flag. As this
10848 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
10849 drop. This change should make some attacks against the hidden
10850 service directory system harder. Fixes ticket 15963.
10851 - Turn on hidden service statistics collection by setting the torrc
10852 option HiddenServiceStatistics to "1" by default. (This keeps
10853 track only of the fraction of traffic used by hidden services, and
10854 the total number of hidden services in existence.) Closes
10856 - To avoid leaking HS popularity, don't cycle the introduction point
10857 when we've handled a fixed number of INTRODUCE2 cells but instead
10858 cycle it when a random number of introductions is reached, thus
10859 making it more difficult for an attacker to find out the amount of
10860 clients that have used the introduction point for a specific HS.
10861 Closes ticket 15745.
10863 o Minor features (logging):
10864 - Include the Tor version in all LD_BUG log messages, since people
10865 tend to cut and paste those into the bugtracker. Implements
10868 o Minor features (pluggable transports):
10869 - When launching managed pluggable transports on Linux systems,
10870 attempt to have the kernel deliver a SIGTERM on tor exit if the
10871 pluggable transport process is still running. Resolves
10873 - When launching managed pluggable transports, setup a valid open
10874 stdin in the child process that can be used to detect if tor has
10875 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
10876 can be used by implementations to detect this new behavior.
10877 Resolves ticket 15435.
10879 o Minor bugfixes (torrc exit policies):
10880 - In each instance above, usage advice is provided to avoid the
10881 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
10882 16069; bugfix on 0.2.4.7-alpha.
10883 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
10884 produce IPv6 wildcard addresses. Previously they would produce
10885 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
10886 of bug 16069; bugfix on 0.2.4.7-alpha.
10887 - When parsing torrc ExitPolicies, we now issue an info-level
10888 message when expanding an "accept/reject *" line to include both
10889 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
10890 - When parsing torrc ExitPolicies, we now warn for a number of cases
10891 where the user's intent is likely to differ from Tor's actual
10892 behavior. These include: using an IPv4 address with an accept6 or
10893 reject6 line; using "private" on an accept6 or reject6 line; and
10894 including any ExitPolicy lines after accept *:* or reject *:*.
10895 Related to ticket 16069.
10897 o Minor bugfixes (command-line interface):
10898 - When "--quiet" is provided along with "--validate-config", do not
10899 write anything to stdout on success. Fixes bug 14994; bugfix
10901 - When complaining about bad arguments to "--dump-config", use
10902 stderr, not stdout.
10903 - Print usage information for --dump-config when it is used without
10904 an argument. Also, fix the error message to use different wording
10905 and add newline at the end. Fixes bug 15541; bugfix
10908 o Minor bugfixes (compilation):
10909 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
10910 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
10911 - Repair compilation with the most recent (unreleased, alpha)
10912 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
10914 o Minor bugfixes (compilation, also in 0.2.6.9):
10915 - Build with --enable-systemd correctly when libsystemd is
10916 installed, but systemd is not. Fixes bug 16164; bugfix on
10917 0.2.6.3-alpha. Patch from Peter Palfrader.
10919 o Minor bugfixes (configuration, unit tests):
10920 - Only add the default fallback directories when the DirAuthorities,
10921 AlternateDirAuthority, and FallbackDir directory config options
10922 are set to their defaults. The default fallback directory list is
10923 currently empty, this fix will only change tor's behavior when it
10924 has default fallback directories. Includes unit tests for
10925 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
10926 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
10928 o Minor bugfixes (controller):
10929 - Add the descriptor ID in each HS_DESC control event. It was
10930 missing, but specified in control-spec.txt. Fixes bug 15881;
10931 bugfix on 0.2.5.2-alpha.
10933 o Minor bugfixes (correctness):
10934 - For correctness, avoid modifying a constant string in
10935 handle_control_postdescriptor. Fixes bug 15546; bugfix
10937 - Remove side-effects from tor_assert() calls. This was harmless,
10938 because we never disable assertions, but it is bad style and
10939 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
10941 - When calling channel_free_list(), avoid calling smartlist_remove()
10942 while inside a FOREACH loop. This partially reverts commit
10943 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
10944 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
10946 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
10947 - Check for failures from crypto_early_init, and refuse to continue.
10948 A previous typo meant that we could keep going with an
10949 uninitialized crypto library, and would have OpenSSL initialize
10950 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
10951 when implementing ticket 4900. Patch by "teor".
10953 o Minor bugfixes (hidden service):
10954 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
10955 a client authorized hidden service. Fixes bug 15823; bugfix
10957 - Remove an extraneous newline character from the end of hidden
10958 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
10960 o Minor bugfixes (Linux seccomp2 sandbox):
10961 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
10962 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
10963 - Allow bridge authorities to run correctly under the seccomp2
10964 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
10965 - Add the "hidserv-stats" filename to our sandbox filter for the
10966 HiddenServiceStatistics option to work properly. Fixes bug 17354;
10967 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
10969 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
10970 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
10971 these when eventfd2() support is missing. Fixes bug 16363; bugfix
10972 on 0.2.6.3-alpha. Patch from "teor".
10974 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
10975 - Allow systemd connections to work with the Linux seccomp2 sandbox
10976 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
10978 - Fix sandboxing to work when running as a relay, by allowing the
10979 renaming of secret_id_key, and allowing the eventfd2 and futex
10980 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
10983 o Minor bugfixes (logging):
10984 - When building Tor under Clang, do not include an extra set of
10985 parentheses in log messages that include function names. Fixes bug
10986 15269; bugfix on every released version of Tor when compiled with
10987 recent enough Clang.
10989 o Minor bugfixes (network):
10990 - When attempting to use fallback technique for network interface
10991 lookup, disregard loopback and multicast addresses since they are
10992 unsuitable for public communications.
10994 o Minor bugfixes (open file limit):
10995 - Fix set_max_file_descriptors() to set by default the max open file
10996 limit to the current limit when setrlimit() fails. Fixes bug
10997 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
10999 o Minor bugfixes (portability):
11000 - Check correctly for Windows socket errors in the workqueue
11001 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
11002 - Try harder to normalize the exit status of the Tor process to the
11003 standard-provided range. Fixes bug 16975; bugfix on every version
11005 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
11006 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
11008 o Minor bugfixes (relay):
11009 - Ensure that worker threads actually exit when a fatal error or
11010 shutdown is indicated. This fix doesn't currently affect the
11011 behavior of Tor, because Tor workers never indicates fatal error
11012 or shutdown except in the unit tests. Fixes bug 16868; bugfix
11014 - Fix a rarely-encountered memory leak when failing to initialize
11015 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
11016 from "cypherpunks".
11017 - Unblock threads before releasing the work queue mutex to ensure
11018 predictable scheduling behavior. Fixes bug 16644; bugfix
11021 o Minor bugfixes (security, exit policies):
11022 - ExitPolicyRejectPrivate now also rejects the relay's published
11023 IPv6 address (if any), and any publicly routable IPv4 or IPv6
11024 addresses on any local interfaces. ticket 17027. Patch by "teor".
11025 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
11027 o Minor bugfixes (statistics):
11028 - Disregard the ConnDirectionStatistics torrc options when Tor is
11029 not a relay since in that mode of operation no sensible data is
11030 being collected and because Tor might run into measurement hiccups
11031 when running as a client for some time, then becoming a relay.
11032 Fixes bug 15604; bugfix on 0.2.2.35.
11034 o Minor bugfixes (systemd):
11035 - Tor's systemd unit file no longer contains extraneous spaces.
11036 These spaces would sometimes confuse tools like deb-systemd-
11037 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
11039 o Minor bugfixes (test networks):
11040 - When self-testing reachability, use ExtendAllowPrivateAddresses to
11041 determine if local/private addresses imply reachability. The
11042 previous fix used TestingTorNetwork, which implies
11043 ExtendAllowPrivateAddresses, but this excluded rare configurations
11044 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
11045 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
11046 issue discovered by CJ Ess.
11048 o Minor bugfixes (tests, also in 0.2.6.9):
11049 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
11050 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
11052 o Code simplification and refactoring:
11053 - Change the function that's called when we need to retry all
11054 downloads so that it only reschedules the downloads to happen
11055 immediately, rather than launching them all at once itself. This
11056 further simplifies Tor's callgraph.
11057 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
11058 to ensure they remain consistent and visible everywhere.
11059 - Move some format-parsing functions out of crypto.c and
11060 crypto_curve25519.c into crypto_format.c and/or util_format.c.
11061 - Move the client-only parts of init_keys() into a separate
11062 function. Closes ticket 16763.
11063 - Move the hacky fallback code out of get_interface_address6() into
11064 separate function and get it covered with unit-tests. Resolves
11066 - Refactor hidden service client-side cache lookup to intelligently
11067 report its various failure cases, and disentangle failure cases
11068 involving a lack of introduction points. Closes ticket 14391.
11069 - Remove some vestigial workarounds for the MSVC6 compiler. We
11070 haven't supported that in ages.
11071 - Remove the unused "nulterminate" argument from buf_pullup().
11072 - Simplify the microdesc_free() implementation so that it no longer
11073 appears (to code analysis tools) to potentially invoke a huge
11074 suite of other microdesc functions.
11075 - Simply the control graph further by deferring the inner body of
11076 directory_all_unreachable() into a callback. Closes ticket 16762.
11077 - The link authentication code has been refactored for better
11078 testability and reliability. It now uses code generated with the
11079 "trunnel" binary encoding generator, to reduce the risk of bugs
11080 due to programmer error. Done as part of ticket 12498.
11081 - Treat the loss of an owning controller as equivalent to a SIGTERM
11082 signal. This removes a tiny amount of duplicated code, and
11083 simplifies our callgraph. Closes ticket 16788.
11084 - Use our own Base64 encoder instead of OpenSSL's, to allow more
11085 control over the output. Part of ticket 15652.
11086 - When generating an event to send to the controller, we no longer
11087 put the event over the network immediately. Instead, we queue
11088 these events, and use a Libevent callback to deliver them. This
11089 change simplifies Tor's callgraph by reducing the number of
11090 functions from which all other Tor functions are reachable. Closes
11092 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
11093 that try to scan or compile every file on Unix won't decide that
11097 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
11098 - Improve the descriptions of statistics-related torrc options in
11099 the manpage to describe rationale and possible uses cases. Fixes
11101 - Improve the layout and formatting of ./configure --help messages.
11102 Closes ticket 15024. Patch from "cypherpunks".
11103 - Include a specific and (hopefully) accurate documentation of the
11104 torrc file's meta-format in doc/torrc_format.txt. This is mainly
11105 of interest to people writing programs to parse or generate torrc
11106 files. This document is not a commitment to long-term
11107 compatibility; some aspects of the current format are a bit
11108 ridiculous. Closes ticket 2325.
11109 - Include the TUNING document in our source tarball. It is referred
11110 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
11112 - Note that HiddenServicePorts can take a unix domain socket. Closes
11114 - Recommend a 40 GB example AccountingMax in torrc.sample rather
11115 than a 4 GB max. Closes ticket 16742.
11116 - Standardize on the term "server descriptor" in the manual page.
11117 Previously, we had used "router descriptor", "server descriptor",
11118 and "relay descriptor" interchangeably. Part of ticket 14987.
11119 - Advise users on how to configure separate IPv4 and IPv6 exit
11120 policies in the manpage and sample torrcs. Related to ticket 16069.
11121 - Fix an error in the manual page and comments for
11122 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
11123 required "ORPort connectivity". While this is true, it is in no
11124 way unique to the HSDir flag. Of all the flags, only HSDirs need a
11125 DirPort configured in order for the authorities to assign that
11126 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
11128 - Fix the usage message of tor-resolve(1) so that it no longer lists
11129 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
11132 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
11133 and always use the internal Base64 decoder. The internal decoder
11134 has been part of tor since 0.2.0.10-alpha, and no one should
11135 be using the OpenSSL one. Part of ticket 15652.
11136 - Remove the 'tor_strclear()' function; use memwipe() instead.
11137 Closes ticket 14922.
11138 - Remove the code that would try to aggressively flush controller
11139 connections while writing to them. This code was introduced in
11140 0.1.2.7-alpha, in order to keep output buffers from exceeding
11141 their limits. But there is no longer a maximum output buffer size,
11142 and flushing data in this way caused some undesirable recursions
11143 in our call graph. Closes ticket 16480.
11144 - The internal pure-C tor-fw-helper tool is now removed from the Tor
11145 distribution, in favor of the pure-Go clone available from
11146 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
11147 used by the C tor-fw-helper are not, in our opinion, very
11148 confidence- inspiring in their secure-programming techniques.
11149 Closes ticket 13338.
11151 o Removed features:
11152 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
11153 fingerprinting we now recommend pluggable transports; for forward-
11154 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
11155 - Remove the HidServDirectoryV2 option. Now all relays offer to
11156 store hidden service descriptors. Related to 16543.
11157 - Remove the VoteOnHidServDirectoriesV2 option, since all
11158 authorities have long set it to 1. Closes ticket 16543.
11159 - Remove the undocumented "--digests" command-line option. It
11160 complicated our build process, caused subtle build issues on
11161 multiple platforms, and is now redundant since we started
11162 including git version identifiers. Closes ticket 14742.
11163 - Tor no longer contains checks for ancient directory cache versions
11164 that didn't know about microdescriptors.
11165 - Tor no longer contains workarounds for stat files generated by
11166 super-old versions of Tor that didn't choose guards sensibly.
11169 - The test-network.sh script now supports performance testing.
11170 Requires corresponding chutney performance testing changes. Patch
11171 by "teor". Closes ticket 14175.
11172 - Add a new set of callgraph analysis scripts that use clang to
11173 produce a list of which Tor functions are reachable from which
11174 other Tor functions. We're planning to use these to help simplify
11175 our code structure by identifying illogical dependencies.
11176 - Add new 'test-full' and 'test-full-online' targets to run all
11177 tests, including integration tests with stem and chutney.
11178 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
11179 by-side in the same parent directory. Closes ticket 16903. Patch
11181 - Document use of coverity, clang static analyzer, and clang dynamic
11182 undefined behavior and address sanitizers in doc/HACKING. Include
11183 detailed usage instructions in the blacklist. Patch by "teor".
11184 Closes ticket 15817.
11185 - Make "bridges+hs" the default test network. This tests almost all
11186 tor functionality during make test-network, while allowing tests
11187 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
11188 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
11189 (chutney). Patches by "teor".
11190 - Make the test-workqueue test work on Windows by initializing the
11191 network before we begin.
11192 - New make target (make test-network-all) to run multiple applicable
11193 chutney test cases. Patch from Teor; closes 16953.
11194 - Now that OpenSSL has its own scrypt implementation, add an unit
11195 test that checks for interoperability between libscrypt_scrypt()
11196 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
11197 and rely on EVP_PBE_scrypt() whenever possible. Resolves
11199 - The link authentication protocol code now has extensive tests.
11200 - The relay descriptor signature testing code now has
11202 - The test_workqueue program now runs faster, and is enabled by
11203 default as a part of "make check".
11204 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
11205 functions in dns.c. Implements a portion of ticket 16831.
11206 - Use environment variables rather than autoconf substitutions to
11207 send variables from the build system to the test scripts. This
11208 change should be easier to maintain, and cause 'make distcheck' to
11209 work better than before. Fixes bug 17148.
11210 - When building Tor with testing coverage enabled, run Chutney tests
11211 (if any) using the 'tor-cov' coverage binary.
11212 - When running test-network or test-stem, check for the absence of
11213 stem/chutney before doing any build operations.
11214 - Add a test to verify that the compiler does not eliminate our
11215 memwipe() implementation. Closes ticket 15377.
11216 - Add make rule `check-changes` to verify the format of changes
11217 files. Closes ticket 15180.
11218 - Add unit tests for control_event_is_interesting(). Add a compile-
11219 time check that the number of events doesn't exceed the capacity
11220 of control_event_t.event_mask. Closes ticket 15431, checks for
11221 bugs similar to 13085. Patch by "teor".
11222 - Command-line argument tests moved to Stem. Resolves ticket 14806.
11223 - Integrate the ntor, backtrace, and zero-length keys tests into the
11224 automake test suite. Closes ticket 15344.
11225 - Remove assertions during builds to determine Tor's test coverage.
11226 We don't want to trigger these even in assertions, so including
11227 them artificially makes our branch coverage look worse than it is.
11228 This patch provides the new test-stem-full and coverage-html-full
11229 configure options. Implements ticket 15400.
11230 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
11231 explicitly manage consensus flags in testing networks. Patch by
11232 "robgjansen", modified by "teor". Implements part of ticket 14882.
11233 - Check for matching value in server response in ntor_ref.py. Fixes
11234 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
11236 - Set the severity correctly when testing
11237 get_interface_addresses_ifaddrs() and
11238 get_interface_addresses_win32(), so that the tests fail gracefully
11239 instead of triggering an assertion. Fixes bug 15759; bugfix on
11240 0.2.6.3-alpha. Reported by Nicolas Derive.
11242 Changes in version 0.2.6.10 - 2015-07-12
11243 Tor version 0.2.6.10 fixes some significant stability and hidden
11244 service client bugs, bulletproofs the cryptography init process, and
11245 fixes a bug when using the sandbox code with some older versions of
11246 Linux. Everyone running an older version, especially an older version
11247 of 0.2.6, should upgrade.
11249 o Major bugfixes (hidden service clients, stability):
11250 - Stop refusing to store updated hidden service descriptors on a
11251 client. This reverts commit 9407040c59218 (which indeed fixed bug
11252 14219, but introduced a major hidden service reachability
11253 regression detailed in bug 16381). This is a temporary fix since
11254 we can live with the minor issue in bug 14219 (it just results in
11255 some load on the network) but the regression of 16381 is too much
11256 of a setback. First-round fix for bug 16381; bugfix
11259 o Major bugfixes (stability):
11260 - Stop crashing with an assertion failure when parsing certain kinds
11261 of malformed or truncated microdescriptors. Fixes bug 16400;
11262 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
11263 by "cypherpunks_backup".
11264 - Stop random client-side assertion failures that could occur when
11265 connecting to a busy hidden service, or connecting to a hidden
11266 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
11269 o Minor features (geoip):
11270 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
11271 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
11273 o Minor bugfixes (crypto error-handling):
11274 - Check for failures from crypto_early_init, and refuse to continue.
11275 A previous typo meant that we could keep going with an
11276 uninitialized crypto library, and would have OpenSSL initialize
11277 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
11278 when implementing ticket 4900. Patch by "teor".
11280 o Minor bugfixes (Linux seccomp2 sandbox):
11281 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
11282 these when eventfd2() support is missing. Fixes bug 16363; bugfix
11283 on 0.2.6.3-alpha. Patch from "teor".
11286 Changes in version 0.2.6.9 - 2015-06-11
11287 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
11288 requirements for receiving an HSDir flag, and addresses some other small
11289 bugs in the systemd and sandbox code. Clients using circuit isolation
11290 should upgrade; all directory authorities should upgrade.
11292 o Major bugfixes (client-side privacy):
11293 - Properly separate out each SOCKSPort when applying stream
11294 isolation. The error occurred because each port's session group was
11295 being overwritten by a default value when the listener connection
11296 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
11299 o Minor feature (directory authorities, security):
11300 - The HSDir flag given by authorities now requires the Stable flag.
11301 For the current network, this results in going from 2887 to 2806
11302 HSDirs. Also, it makes it harder for an attacker to launch a sybil
11303 attack by raising the effort for a relay to become Stable which
11304 takes at the very least 7 days to do so and by keeping the 96
11305 hours uptime requirement for HSDir. Implements ticket 8243.
11307 o Minor bugfixes (compilation):
11308 - Build with --enable-systemd correctly when libsystemd is
11309 installed, but systemd is not. Fixes bug 16164; bugfix on
11310 0.2.6.3-alpha. Patch from Peter Palfrader.
11312 o Minor bugfixes (Linux seccomp2 sandbox):
11313 - Fix sandboxing to work when running as a relaymby renaming of
11314 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
11315 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
11316 - Allow systemd connections to work with the Linux seccomp2 sandbox
11317 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
11320 o Minor bugfixes (tests):
11321 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
11322 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
11325 Changes in version 0.2.6.8 - 2015-05-21
11326 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
11327 fixes an authority-side bug in assigning the HSDir flag. All directory
11328 authorities should upgrade.
11330 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
11331 - Revert commit that made directory authorities assign the HSDir
11332 flag to relays without a DirPort; this was bad because such relays
11333 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
11336 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
11337 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
11338 a client authorized hidden service. Fixes bug 15823; bugfix
11341 o Minor features (geoip):
11342 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
11343 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
11347 Changes in version 0.2.6.7 - 2015-04-06
11348 Tor 0.2.6.7 fixes two security issues that could be used by an
11349 attacker to crash hidden services, or crash clients visiting hidden
11350 services. Hidden services should upgrade as soon as possible; clients
11351 should upgrade whenever packages become available.
11353 This release also contains two simple improvements to make hidden
11354 services a bit less vulnerable to denial-of-service attacks.
11356 o Major bugfixes (security, hidden service):
11357 - Fix an issue that would allow a malicious client to trigger an
11358 assertion failure and halt a hidden service. Fixes bug 15600;
11359 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11360 - Fix a bug that could cause a client to crash with an assertion
11361 failure when parsing a malformed hidden service descriptor. Fixes
11362 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11364 o Minor features (DoS-resistance, hidden service):
11365 - Introduction points no longer allow multiple INTRODUCE1 cells to
11366 arrive on the same circuit. This should make it more expensive for
11367 attackers to overwhelm hidden services with introductions.
11368 Resolves ticket 15515.
11369 - Decrease the amount of reattempts that a hidden service performs
11370 when its rendezvous circuits fail. This reduces the computational
11371 cost for running a hidden service under heavy load. Resolves
11375 Changes in version 0.2.5.12 - 2015-04-06
11376 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
11377 could be used by an attacker to crash hidden services, or crash clients
11378 visiting hidden services. Hidden services should upgrade as soon as
11379 possible; clients should upgrade whenever packages become available.
11381 This release also backports a simple improvement to make hidden
11382 services a bit less vulnerable to denial-of-service attacks.
11384 o Major bugfixes (security, hidden service):
11385 - Fix an issue that would allow a malicious client to trigger an
11386 assertion failure and halt a hidden service. Fixes bug 15600;
11387 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11388 - Fix a bug that could cause a client to crash with an assertion
11389 failure when parsing a malformed hidden service descriptor. Fixes
11390 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11392 o Minor features (DoS-resistance, hidden service):
11393 - Introduction points no longer allow multiple INTRODUCE1 cells to
11394 arrive on the same circuit. This should make it more expensive for
11395 attackers to overwhelm hidden services with introductions.
11396 Resolves ticket 15515.
11399 Changes in version 0.2.4.27 - 2015-04-06
11400 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
11401 could be used by an attacker to crash hidden services, or crash clients
11402 visiting hidden services. Hidden services should upgrade as soon as
11403 possible; clients should upgrade whenever packages become available.
11405 This release also backports a simple improvement to make hidden
11406 services a bit less vulnerable to denial-of-service attacks.
11408 o Major bugfixes (security, hidden service):
11409 - Fix an issue that would allow a malicious client to trigger an
11410 assertion failure and halt a hidden service. Fixes bug 15600;
11411 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
11412 - Fix a bug that could cause a client to crash with an assertion
11413 failure when parsing a malformed hidden service descriptor. Fixes
11414 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
11416 o Minor features (DoS-resistance, hidden service):
11417 - Introduction points no longer allow multiple INTRODUCE1 cells to
11418 arrive on the same circuit. This should make it more expensive for
11419 attackers to overwhelm hidden services with introductions.
11420 Resolves ticket 15515.
11423 Changes in version 0.2.6.6 - 2015-03-24
11424 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
11426 It adds numerous safety, security, correctness, and performance
11427 improvements. Client programs can be configured to use more kinds of
11428 sockets, AutomapHosts works better, the multithreading backend is
11429 improved, cell transmission is refactored, test coverage is much
11430 higher, more denial-of-service attacks are handled, guard selection is
11431 improved to handle long-term guards better, pluggable transports
11432 should work a bit better, and some annoying hidden service performance
11433 bugs should be addressed.
11435 o New compiler and system requirements:
11436 - Tor 0.2.6.x requires that your compiler support more of the C99
11437 language standard than before. The 'configure' script now detects
11438 whether your compiler supports C99 mid-block declarations and
11439 designated initializers. If it does not, Tor will not compile.
11441 We may revisit this requirement if it turns out that a significant
11442 number of people need to build Tor with compilers that don't
11443 bother implementing a 15-year-old standard. Closes ticket 13233.
11444 - Tor no longer supports systems without threading support. When we
11445 began working on Tor, there were several systems that didn't have
11446 threads, or where the thread support wasn't able to run the
11447 threads of a single process on multiple CPUs. That no longer
11448 holds: every system where Tor needs to run well now has threading
11449 support. Resolves ticket 12439.
11451 o Deprecated versions and removed support:
11452 - Tor relays older than 0.2.4.18-rc are no longer allowed to
11453 advertise themselves on the network. Closes ticket 13555.
11454 - Tor clients no longer support connecting to hidden services
11455 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
11456 option has been removed. (There shouldn't be any hidden services
11457 running these versions on the network.) Closes ticket 7803.
11459 o Directory authority changes:
11460 - The directory authority Faravahar has a new IP address. This
11461 closes ticket 14487.
11462 - Remove turtles as a directory authority.
11463 - Add longclaw as a new (v3) directory authority. This implements
11464 ticket 13296. This keeps the directory authority count at 9.
11466 o Major features (bridges):
11467 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
11468 transports if they are configured via the "TOR_PT_PROXY"
11469 environment variable. Implements proposal 232. Resolves
11472 o Major features (changed defaults):
11473 - Prevent relay operators from unintentionally running exits: When a
11474 relay is configured as an exit node, we now warn the user unless
11475 the "ExitRelay" option is set to 1. We warn even more loudly if
11476 the relay is configured with the default exit policy, since this
11477 can indicate accidental misconfiguration. Setting "ExitRelay 0"
11478 stops Tor from running as an exit relay. Closes ticket 10067.
11480 o Major features (client performance, hidden services):
11481 - Allow clients to use optimistic data when connecting to a hidden
11482 service, which should remove a round-trip from hidden service
11483 initialization. See proposal 181 for details. Implements
11486 o Major features (directory system):
11487 - Upon receiving an unparseable directory object, if its digest
11488 matches what we expected, then don't try to download it again.
11489 Previously, when we got a descriptor we didn't like, we would keep
11490 trying to download it over and over. Closes ticket 11243.
11491 - When downloading server- or microdescriptors from a directory
11492 server, we no longer launch multiple simultaneous requests to the
11493 same server. This reduces load on the directory servers,
11494 especially when directory guards are in use. Closes ticket 9969.
11495 - When downloading server- or microdescriptors over a tunneled
11496 connection, do not limit the length of our requests to what the
11497 Squid proxy is willing to handle. Part of ticket 9969.
11498 - Authorities can now vote on the correct digests and latest
11499 versions for different software packages. This allows packages
11500 that include Tor to use the Tor authority system as a way to get
11501 notified of updates and their correct digests. Implements proposal
11502 227. Closes ticket 10395.
11504 o Major features (guards):
11505 - Introduce the Guardfraction feature to improves load balancing on
11506 guard nodes. Specifically, it aims to reduce the traffic gap that
11507 guard nodes experience when they first get the Guard flag. This is
11508 a required step if we want to increase the guard lifetime to 9
11509 months or greater. Closes ticket 9321.
11511 o Major features (hidden services):
11512 - Make HS port scanning more difficult by immediately closing the
11513 circuit when a user attempts to connect to a nonexistent port.
11514 Closes ticket 13667.
11515 - Add a HiddenServiceStatistics option that allows Tor relays to
11516 gather and publish statistics about the overall size and volume of
11517 hidden service usage. Specifically, when this option is turned on,
11518 an HSDir will publish an approximate number of hidden services
11519 that have published descriptors to it the past 24 hours. Also, if
11520 a relay has acted as a hidden service rendezvous point, it will
11521 publish the approximate amount of rendezvous cells it has relayed
11522 the past 24 hours. The statistics themselves are obfuscated so
11523 that the exact values cannot be derived. For more details see
11524 proposal 238, "Better hidden service stats from Tor relays". This
11525 feature is currently disabled by default. Implements feature 13192.
11527 o Major features (performance):
11528 - Make the CPU worker implementation more efficient by avoiding the
11529 kernel and lengthening pipelines. The original implementation used
11530 sockets to transfer data from the main thread to the workers, and
11531 didn't allow any thread to be assigned more than a single piece of
11532 work at once. The new implementation avoids communications
11533 overhead by making requests in shared memory, avoiding kernel IO
11534 where possible, and keeping more requests in flight at once.
11535 Implements ticket 9682.
11537 o Major features (relay):
11538 - Raise the minimum acceptable configured bandwidth rate for bridges
11539 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
11540 20 KiB/sec.) Closes ticket 13822.
11541 - Complete revision of the code that relays use to decide which cell
11542 to send next. Formerly, we selected the best circuit to write on
11543 each channel, but we didn't select among channels in any
11544 sophisticated way. Now, we choose the best circuits globally from
11545 among those whose channels are ready to deliver traffic.
11547 This patch implements a new inter-cmux comparison API, a global
11548 high/low watermark mechanism and a global scheduler loop for
11549 transmission prioritization across all channels as well as among
11550 circuits on one channel. This schedule is currently tuned to
11551 (tolerantly) avoid making changes in network performance, but it
11552 should form the basis for major circuit performance increases in
11553 the future. Code by Andrea; tuning by Rob Jansen; implements
11556 o Major features (sample torrc):
11557 - Add a new, infrequently-changed "torrc.minimal". This file is
11558 similar to torrc.sample, but it will change as infrequently as
11559 possible, for the benefit of users whose systems prompt them for
11560 intervention whenever a default configuration file is changed.
11561 Making this change allows us to update torrc.sample to be a more
11562 generally useful "sample torrc".
11564 o Major features (security, unix domain sockets):
11565 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
11566 applications can reach Tor without having to create AF_INET or
11567 AF_INET6 sockets, meaning they can completely disable their
11568 ability to make non-Tor network connections. To create a socket of
11569 this type, use "SocksPort unix:/path/to/socket". Implements
11571 - Support mapping hidden service virtual ports to AF_UNIX sockets.
11572 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
11573 Implements ticket 11485.
11575 o Major bugfixes (client, automap):
11576 - Repair automapping with IPv6 addresses. This automapping should
11577 have worked previously, but one piece of debugging code that we
11578 inserted to detect a regression actually caused the regression to
11579 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
11580 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
11583 o Major bugfixes (crash, OSX, security):
11584 - Fix a remote denial-of-service opportunity caused by a bug in
11585 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
11588 o Major bugfixes (directory authorities):
11589 - Do not assign the HSDir flag to relays if they are not Valid, or
11590 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
11592 o Major bugfixes (directory bandwidth performance):
11593 - Don't flush the zlib buffer aggressively when compressing
11594 directory information for clients. This should save about 7% of
11595 the bandwidth currently used for compressed descriptors and
11596 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
11598 o Major bugfixes (exit node stability):
11599 - Fix an assertion failure that could occur under high DNS load.
11600 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
11601 diagnosed and fixed by "cypherpunks".
11603 o Major bugfixes (FreeBSD IPFW transparent proxy):
11604 - Fix address detection with FreeBSD transparent proxies, when
11605 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
11608 o Major bugfixes (hidden services):
11609 - When closing an introduction circuit that was opened in parallel
11610 with others, don't mark the introduction point as unreachable.
11611 Previously, the first successful connection to an introduction
11612 point would make the other introduction points get marked as
11613 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
11615 o Major bugfixes (Linux seccomp2 sandbox):
11616 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
11617 crash during attempts to call wait4. Fixes bug 15088; bugfix on
11618 0.2.5.1-alpha. Patch from "sanic".
11620 o Major bugfixes (mixed relay-client operation):
11621 - When running as a relay and client at the same time (not
11622 recommended), if we decide not to use a new guard because we want
11623 to retry older guards, only close the locally-originating circuits
11624 passing through that guard. Previously we would close all the
11625 circuits through that guard. Fixes bug 9819; bugfix on
11626 0.2.1.1-alpha. Reported by "skruffy".
11628 o Major bugfixes (pluggable transports):
11629 - Initialize the extended OR Port authentication cookie before
11630 launching pluggable transports. This prevents a race condition
11631 that occurred when server-side pluggable transports would cache the
11632 authentication cookie before it has been (re)generated. Fixes bug
11633 15240; bugfix on 0.2.5.1-alpha.
11635 o Major bugfixes (relay, stability, possible security):
11636 - Fix a bug that could lead to a relay crashing with an assertion
11637 failure if a buffer of exactly the wrong layout is passed to
11638 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
11639 0.2.0.10-alpha. Patch from "cypherpunks".
11640 - Do not assert if the 'data' pointer on a buffer is advanced to the
11641 very end of the buffer; log a BUG message instead. Only assert if
11642 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
11644 o Minor features (build):
11645 - New --disable-system-torrc compile-time option to prevent Tor from
11646 looking for the system-wide torrc or torrc-defaults files.
11647 Resolves ticket 13037.
11649 o Minor features (client):
11650 - Clients are now willing to send optimistic data (before they
11651 receive a 'connected' cell) to relays of any version. (Relays
11652 without support for optimistic data are no longer supported on the
11653 Tor network.) Resolves ticket 13153.
11655 o Minor features (client):
11656 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
11657 is enabled, reject requests with IP addresses as hostnames.
11658 Resolves ticket 13315.
11660 o Minor features (controller):
11661 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
11662 write an unscheduled heartbeat message to the log. Implements
11664 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
11665 events so controllers can observe circuit isolation inputs. Closes
11667 - ControlPort now supports the unix:/path/to/socket syntax as an
11668 alternative to the ControlSocket option, for consistency with
11669 SocksPort and HiddenServicePort. Closes ticket 14451.
11670 - New "GETINFO bw-event-cache" to get information about recent
11671 bandwidth events. Closes ticket 14128. Useful for controllers to
11672 get recent bandwidth history after the fix for ticket 13988.
11673 - Messages about problems in the bootstrap process now include
11674 information about the server we were trying to connect to when we
11675 noticed the problem. Closes ticket 15006.
11677 o Minor features (Denial of service resistance):
11678 - Count the total number of bytes used storing hidden service
11679 descriptors against the value of MaxMemInQueues. If we're low on
11680 memory, and more than 20% of our memory is used holding hidden
11681 service descriptors, free them until no more than 10% of our
11682 memory holds hidden service descriptors. Free the least recently
11683 fetched descriptors first. Resolves ticket 13806.
11684 - When we have recently been under memory pressure (over 3/4 of
11685 MaxMemInQueues is allocated), then allocate smaller zlib objects
11686 for small requests. Closes ticket 11791.
11688 o Minor features (directory authorities):
11689 - Don't list relays with a bandwidth estimate of 0 in the consensus.
11690 Implements a feature proposed during discussion of bug 13000.
11691 - In tor-gencert, report an error if the user provides the same
11692 argument more than once.
11693 - If a directory authority can't find a best consensus method in the
11694 votes that it holds, it now falls back to its favorite consensus
11695 method. Previously, it fell back to method 1. Neither of these is
11696 likely to get enough signatures, but "fall back to favorite"
11697 doesn't require us to maintain support an obsolete consensus
11698 method. Implements part of proposal 215.
11700 o Minor features (geoip):
11701 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
11702 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
11705 o Minor features (guard nodes):
11706 - Reduce the time delay before saving guard status to disk from 10
11707 minutes to 30 seconds (or from one hour to 10 minutes if
11708 AvoidDiskWrites is set). Closes ticket 12485.
11710 o Minor features (heartbeat):
11711 - On relays, report how many connections we negotiated using each
11712 version of the Tor link protocols. This information will let us
11713 know if removing support for very old versions of the Tor
11714 protocols is harming the network. Closes ticket 15212.
11716 o Minor features (hidden service):
11717 - Make Sybil attacks against hidden services harder by changing the
11718 minimum time required to get the HSDir flag from 25 hours up to 96
11719 hours. Addresses ticket 14149.
11720 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
11721 services to disable the anti-scanning feature introduced in
11722 0.2.6.2-alpha. With this option not set, a connection to an
11723 unlisted port closes the circuit. With this option set, only a
11724 RELAY_DONE cell is sent. Closes ticket 14084.
11725 - When re-enabling the network, don't try to build introduction
11726 circuits until we have successfully built a circuit. This makes
11727 hidden services come up faster when the network is re-enabled.
11728 Patch from "akwizgran". Closes ticket 13447.
11729 - When we fail to retrieve a hidden service descriptor, send the
11730 controller an "HS_DESC FAILED" controller event. Implements
11732 - New HiddenServiceDirGroupReadable option to cause hidden service
11733 directories and hostname files to be created group-readable. Patch
11734 from "anon", David Stainton, and "meejah". Closes ticket 11291.
11736 o Minor features (interface):
11737 - Implement "-f -" command-line option to read torrc configuration
11738 from standard input, if you don't want to store the torrc file in
11739 the file system. Implements feature 13865.
11741 o Minor features (logging):
11742 - Add a count of unique clients to the bridge heartbeat message.
11743 Resolves ticket 6852.
11744 - Suppress "router info incompatible with extra info" message when
11745 reading extrainfo documents from cache. (This message got loud
11746 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
11748 - Elevate hidden service authorized-client message from DEBUG to
11749 INFO. Closes ticket 14015.
11750 - On Unix-like systems, you can now use named pipes as the target of
11751 the Log option, and other options that try to append to files.
11752 Closes ticket 12061. Patch from "carlo von lynX".
11753 - When opening a log file at startup, send it every log message that
11754 we generated between startup and opening it. Previously, log
11755 messages that were generated before opening the log file were only
11756 logged to stdout. Closes ticket 6938.
11757 - Add a TruncateLogFile option to overwrite logs instead of
11758 appending to them. Closes ticket 5583.
11759 - Quiet some log messages in the heartbeat and at startup. Closes
11762 o Minor features (portability, Solaris):
11763 - Threads are no longer disabled by default on Solaris; we believe
11764 that the versions of Solaris with broken threading support are all
11765 obsolete by now. Resolves ticket 9495.
11767 o Minor features (relay):
11768 - Re-check our address after we detect a changed IP address from
11769 getsockname(). This ensures that the controller command "GETINFO
11770 address" will report the correct value. Resolves ticket 11582.
11772 - A new AccountingRule option lets Relays set whether they'd like
11773 AccountingMax to be applied separately to inbound and outbound
11774 traffic, or applied to the sum of inbound and outbound traffic.
11775 Resolves ticket 961. Patch by "chobe".
11776 - When identity keypair is generated for first time, log a
11777 congratulatory message that links to the new relay lifecycle
11778 document. Implements feature 10427.
11780 o Minor features (security, memory wiping):
11781 - Ensure we securely wipe keys from memory after
11782 crypto_digest_get_digest and init_curve25519_keypair_from_file
11783 have finished using them. Resolves ticket 13477.
11785 o Minor features (security, out-of-memory handling):
11786 - When handling an out-of-memory condition, allocate less memory for
11787 temporary data structures. Fixes issue 10115.
11788 - When handling an out-of-memory condition, consider more types of
11789 buffers, including those on directory connections, and zlib
11790 buffers. Resolves ticket 11792.
11792 o Minor features (stability):
11793 - Add assertions in our hash-table iteration code to check for
11794 corrupted values that could cause infinite loops. Closes
11797 o Minor features (systemd):
11798 - Various improvements and modernizations in systemd hardening
11799 support. Closes ticket 13805. Patch from Craig Andrews.
11800 - Where supported, when running with systemd, report successful
11801 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
11802 - When running with systemd, support systemd watchdog messages. Part
11803 of ticket 11016. Patch by Michael Scherer.
11805 o Minor features (testing networks):
11806 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
11807 the "Exit" flag regardless of their uptime, bandwidth, or exit
11808 policy. TestingTorNetwork must be set for this option to have any
11809 effect. Previously, authorities would take up to 35 minutes to
11810 give nodes the Exit flag in a test network. Partially implements
11812 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
11813 and the default on a testing network to 2 minutes. Drop the
11814 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
11815 keep the default on a testing network at 30 seconds. This reduces
11816 HS bootstrap time to around 25 seconds. Also, change the default
11817 time in test-network.sh to match. Closes ticket 13401. Patch
11819 - Create TestingDirAuthVoteHSDir to correspond to
11820 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
11821 HSDir flag for the listed relays regardless of uptime or ORPort
11822 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
11823 Partial implementation for ticket 14067. Patch by "teor".
11825 o Minor features (tor2web mode):
11826 - Introduce the config option Tor2webRendezvousPoints, which allows
11827 clients in Tor2webMode to select a specific Rendezvous Point to be
11828 used in HS circuits. This might allow better performance for
11829 Tor2Web nodes. Implements ticket 12844.
11831 o Minor features (transparent proxy):
11832 - Update the transparent proxy option checks to allow for both ipfw
11833 and pf on OS X. Closes ticket 14002.
11834 - Use the correct option when using IPv6 with transparent proxy
11835 support on Linux. Resolves 13808. Patch by Francisco Blas
11838 o Minor features (validation):
11839 - Check all date/time values passed to tor_timegm and
11840 parse_rfc1123_time for validity, taking leap years into account.
11841 Improves HTTP header validation. Implemented with bug 13476.
11842 - In correct_tm(), limit the range of values returned by system
11843 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
11844 This means we don't have to deal with negative or too large dates,
11845 even if a clock is wrong. Otherwise we might fail to read a file
11846 written by us which includes such a date. Fixes bug 13476.
11847 - Stop allowing invalid address patterns like "*/24" that contain
11848 both a wildcard address and a bit prefix length. This affects all
11849 our address-range parsing code. Fixes bug 7484; bugfix
11852 o Minor bugfixes (bridge clients):
11853 - When configured to use a bridge without an identity digest (not
11854 recommended), avoid launching an extra channel to it when
11855 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
11857 o Minor bugfixes (bridges):
11858 - When DisableNetwork is set, do not launch pluggable transport
11859 plugins, and if any are running, terminate them. Fixes bug 13213;
11860 bugfix on 0.2.3.6-alpha.
11862 o Minor bugfixes (C correctness):
11863 - Fix several instances of possible integer overflow/underflow/NaN.
11864 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
11866 - In circuit_build_times_calculate_timeout() in circuitstats.c,
11867 avoid dividing by zero in the pareto calculations. This traps
11868 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
11870 - Fix an integer overflow in format_time_interval(). Fixes bug
11871 13393; bugfix on 0.2.0.10-alpha.
11872 - Set the correct day of year value when the system's localtime(_r)
11873 or gmtime(_r) functions fail to set struct tm. Not externally
11874 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
11875 - Avoid unlikely signed integer overflow in tor_timegm on systems
11876 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
11878 o Minor bugfixes (certificate handling):
11879 - If an authority operator accidentally makes a signing certificate
11880 with a future publication time, do not discard its real signing
11881 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
11882 - Remove any old authority certificates that have been superseded
11883 for at least two days. Previously, we would keep superseded
11884 certificates until they expired, if they were published close in
11885 time to the certificate that superseded them. Fixes bug 11454;
11886 bugfix on 0.2.1.8-alpha.
11888 o Minor bugfixes (client):
11889 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
11890 BadExit flag are not considered worthy candidates. Fixes bug
11891 13066; bugfix on 0.1.2.3-alpha.
11892 - Use the consensus schedule for downloading consensuses, and not
11893 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
11894 - Handle unsupported or malformed SOCKS5 requests properly by
11895 responding with the appropriate error message before closing the
11896 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
11898 o Minor bugfixes (client, automapping):
11899 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
11900 no value follows the option. Fixes bug 14142; bugfix on
11901 0.2.4.7-alpha. Patch by "teor".
11902 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
11903 14195; bugfix on 0.1.0.1-rc.
11904 - Prevent changes to other options from removing the wildcard value
11905 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
11907 - Allow MapAddress and AutomapHostsOnResolve to work together when
11908 an address is mapped into another address type (like .onion) that
11909 must be automapped at resolve time. Fixes bug 7555; bugfix
11912 o Minor bugfixes (client, bridges):
11913 - When we are using bridges and we had a network connectivity
11914 problem, only retry connecting to our currently configured
11915 bridges, not all bridges we know about and remember using. Fixes
11916 bug 14216; bugfix on 0.2.2.17-alpha.
11918 o Minor bugfixes (client, DNS):
11919 - Report the correct cached DNS expiration times on SOCKS port or in
11920 DNS replies. Previously, we would report everything as "never
11921 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
11922 - Avoid a small memory leak when we find a cached answer for a
11923 reverse DNS lookup in a client-side DNS cache. (Remember, client-
11924 side DNS caching is off by default, and is not recommended.) Fixes
11925 bug 14259; bugfix on 0.2.0.1-alpha.
11927 o Minor bugfixes (client, IPv6):
11928 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
11929 flag is not set; and not because the NoIPv4Traffic flag was set.
11930 Previously we'd looked at the NoIPv4Traffic flag for both types of
11931 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
11933 o Minor bugfixes (client, microdescriptors):
11934 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
11935 computing which microdescriptors to download. This keeps us from
11936 erroneous download behavior if two microdescriptor digests ever
11937 have the same first 160 bits. Fixes part of bug 13399; bugfix
11939 - Reset a router's status if its microdescriptor digest changes,
11940 even if the first 160 bits remain the same. Fixes part of bug
11941 13399; bugfix on 0.2.3.1-alpha.
11943 o Minor bugfixes (client, torrc):
11944 - Stop modifying the value of our DirReqStatistics torrc option just
11945 because we're not a bridge or relay. This bug was causing Tor
11946 Browser users to write "DirReqStatistics 0" in their torrc files
11947 as if they had chosen to change the config. Fixes bug 4244; bugfix
11949 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
11950 that our options have changed every time we SIGHUP. Fixes bug
11951 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
11953 o Minor bugfixes (compilation):
11954 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
11956 - Silence clang warnings under --enable-expensive-hardening,
11957 including implicit truncation of 64 bit values to 32 bit, const
11958 char assignment to self, tautological compare, and additional
11959 parentheses around equality tests. Fixes bug 13577; bugfix
11961 - Fix a clang warning about checking whether an address in the
11962 middle of a structure is NULL. Fixes bug 14001; bugfix
11964 - The address of an array in the middle of a structure will always
11965 be non-NULL. clang recognises this and complains. Disable the
11966 tautologous and redundant check to silence this warning. Fixes bug
11967 14001; bugfix on 0.2.1.2-alpha.
11968 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
11969 Addresses ticket 14188.
11970 - Build without warnings with the stock OpenSSL srtp.h header, which
11971 has a duplicate declaration of SSL_get_selected_srtp_profile().
11972 Fixes bug 14220; this is OpenSSL's bug, not ours.
11973 - Do not compile any code related to Tor2Web mode when Tor2Web mode
11974 is not enabled at compile time. Previously, this code was included
11975 in a disabled state. See discussion on ticket 12844.
11976 - Allow our configure script to build correctly with autoconf 2.62
11977 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
11978 - Improve the error message from ./configure to make it clear that
11979 when asciidoc has not been found, the user will have to either add
11980 --disable-asciidoc argument or install asciidoc. Resolves
11983 o Minor bugfixes (controller):
11984 - Report "down" in response to the "GETINFO entry-guards" command
11985 when relays are down with an unreachable_since value. Previously,
11986 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
11987 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
11988 14116; bugfix on 0.2.2.9-alpha.
11990 o Minor bugfixes (controller):
11991 - Return an error when the second or later arguments of the
11992 "setevents" controller command are invalid events. Previously we
11993 would return success while silently skipping invalid events. Fixes
11994 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
11996 o Minor bugfixes (directory authority):
11997 - Allow directory authorities to fetch more data from one another if
11998 they find themselves missing lots of votes. Previously, they had
11999 been bumping against the 10 MB queued data limit. Fixes bug 14261;
12000 bugfix on 0.1.2.5-alpha.
12001 - Do not attempt to download extrainfo documents which we will be
12002 unable to validate with a matching server descriptor. Fixes bug
12003 13762; bugfix on 0.2.0.1-alpha.
12004 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
12005 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
12006 - Enlarge the buffer to read bwauth generated files to avoid an
12007 issue when parsing the file in dirserv_read_measured_bandwidths().
12008 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
12009 - When running as a v3 directory authority, advertise that you serve
12010 extra-info documents so that clients who want them can find them
12011 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
12013 o Minor bugfixes (directory system):
12014 - Always believe that v3 directory authorities serve extra-info
12015 documents, whether they advertise "caches-extra-info" or not.
12016 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
12017 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
12018 Previously, directories offering BRIDGE_DIRINFO and some other
12019 flag (i.e. microdescriptors or extrainfo) would be ignored when
12020 looking for bridges. Partially fixes bug 13163; bugfix
12023 o Minor bugfixes (file handling):
12024 - Stop failing when key files are zero-length. Instead, generate new
12025 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
12026 on all versions of Tor. Patch by "teor".
12027 - Stop generating a fresh .old RSA onion key file when the .old file
12028 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
12029 - Avoid overwriting .old key files with empty key files.
12030 - Skip loading zero-length extrainfo store, router store, stats,
12031 state, and key files.
12032 - Avoid crashing when trying to reload a torrc specified as a
12033 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
12036 o Minor bugfixes (hidden services):
12037 - Close the introduction circuit when we have no more usable intro
12038 points, instead of waiting for it to time out. This also ensures
12039 that no follow-up HS descriptor fetch is triggered when the
12040 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
12041 - When fetching a hidden service descriptor for a down service that
12042 was recently up, do not keep refetching until we try the same
12043 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
12044 - Correctly send a controller event when we find that a rendezvous
12045 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
12046 - Pre-check directory permissions for new hidden-services to avoid
12047 at least one case of "Bug: Acting on config options left us in a
12048 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
12049 - When fetching hidden service descriptors, we now check not only
12050 for whether we got the hidden service we had in mind, but also
12051 whether we got the particular descriptors we wanted. This prevents
12052 a class of inefficient but annoying DoS attacks by hidden service
12053 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
12056 o Minor bugfixes (Linux seccomp2 sandbox):
12057 - Make transparent proxy support work along with the seccomp2
12058 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
12059 by Francisco Blas Izquierdo Riera.
12060 - Fix a memory leak in tor-resolve when running with the sandbox
12061 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
12062 - Allow glibc fatal errors to be sent to stderr before Tor exits.
12063 Previously, glibc would try to write them to /dev/tty, and the
12064 sandbox would trap the call and make Tor exit prematurely. Fixes
12065 bug 14759; bugfix on 0.2.5.1-alpha.
12067 o Minor bugfixes (logging):
12068 - Avoid crashing when there are more log domains than entries in
12069 domain_list. Bugfix on 0.2.3.1-alpha.
12070 - Downgrade warnings about RSA signature failures to info log level.
12071 Emit a warning when an extra info document is found incompatible
12072 with a corresponding router descriptor. Fixes bug 9812; bugfix
12074 - Make connection_ap_handshake_attach_circuit() log the circuit ID
12075 correctly. Fixes bug 13701; bugfix on 0.0.6.
12077 o Minor bugfixes (networking):
12078 - Check for orconns and use connection_or_close_for_error() rather
12079 than connection_mark_for_close() directly in the getsockopt()
12080 failure case of connection_handle_write_impl(). Fixes bug 11302;
12081 bugfix on 0.2.4.4-alpha.
12083 o Minor bugfixes (parsing):
12084 - Stop accepting milliseconds (or other junk) at the end of
12085 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
12086 - Support two-number and three-number version numbers correctly, in
12087 case we change the Tor versioning system in the future. Fixes bug
12088 13661; bugfix on 0.0.8pre1.
12090 o Minor bugfixes (portability):
12091 - Fix the ioctl()-based network interface lookup code so that it
12092 will work on systems that have variable-length struct ifreq, for
12094 - Use the correct datatype in the SipHash-2-4 function to prevent
12095 compilers from assuming any sort of alignment. Fixes bug 15436;
12096 bugfix on 0.2.5.3-alpha.
12098 o Minor bugfixes (preventative security, C safety):
12099 - When reading a hexadecimal, base-32, or base-64 encoded value from
12100 a string, always overwrite the whole output buffer. This prevents
12101 some bugs where we would look at (but fortunately, not reveal)
12102 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
12104 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
12105 just the part that's used. This makes it harder for data leak bugs
12106 to occur in the event of other programming failures. Resolves
12109 o Minor bugfixes (relay):
12110 - When generating our family list, remove spaces from around the
12111 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
12112 - If our previous bandwidth estimate was 0 bytes, allow publishing a
12113 new relay descriptor immediately. Fixes bug 13000; bugfix
12116 o Minor bugfixes (shutdown):
12117 - When shutting down, always call event_del() on lingering read or
12118 write events before freeing them. Otherwise, we risk double-frees
12119 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
12122 o Minor bugfixes (small memory leaks):
12123 - Avoid leaking memory when using IPv6 virtual address mappings.
12124 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
12127 o Minor bugfixes (statistics):
12128 - Increase period over which bandwidth observations are aggregated
12129 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
12131 o Minor bugfixes (systemd support):
12132 - Run correctly under systemd with the RunAsDaemon option set. Fixes
12133 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
12134 - Inform the systemd supervisor about more changes in the Tor
12135 process status. Implements part of ticket 14141. Patch from
12138 o Minor bugfixes (testing networks):
12139 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
12140 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
12141 - Stop using the default authorities in networks which provide both
12142 AlternateDirAuthority and AlternateBridgeAuthority. Partially
12143 fixes bug 13163; bugfix on 0.2.0.13-alpha.
12145 o Minor bugfixes (testing networks, fast startup):
12146 - Allow Tor to build circuits using a consensus with no exits. If
12147 the consensus has no exits (typical of a bootstrapping test
12148 network), allow Tor to build circuits once enough descriptors have
12149 been downloaded. This assists in bootstrapping a testing Tor
12150 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
12152 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
12153 header to directory servers. This allows us to obtain consensuses
12154 promptly when the consensus interval is very short. This assists
12155 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
12156 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
12157 - Stop assuming that private addresses are local when checking
12158 reachability in a TestingTorNetwork. Instead, when testing, assume
12159 all OR connections are remote. (This is necessary due to many test
12160 scenarios running all relays on localhost.) This assists in
12161 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
12162 0.1.0.1-rc. Patch by "teor".
12163 - Avoid building exit circuits from a consensus with no exits. Now
12164 thanks to our fix for 13718, we accept a no-exit network as not
12165 wholly lost, but we need to remember not to try to build exit
12166 circuits on it. Closes ticket 13814; patch by "teor".
12167 - Stop requiring exits to have non-zero bandwithcapacity in a
12168 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
12169 ignore exit bandwidthcapacity. This assists in bootstrapping a
12170 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
12171 on 0.2.0.3-alpha. Patch by "teor".
12172 - Add "internal" to some bootstrap statuses when no exits are
12173 available. If the consensus does not contain Exits, Tor will only
12174 build internal circuits. In this case, relevant statuses will
12175 contain the word "internal" as indicated in the Tor control-
12176 spec.txt. When bootstrap completes, Tor will be ready to build
12177 internal circuits. If a future consensus contains Exits, exit
12178 circuits may become available. Fixes part of bug 13718; bugfix on
12179 0.2.4.10-alpha. Patch by "teor".
12180 - Decrease minimum consensus interval to 10 seconds when
12181 TestingTorNetwork is set, or 5 seconds for the first consensus.
12182 Fix assumptions throughout the code that assume larger intervals.
12183 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
12185 - Avoid excluding guards from path building in minimal test
12186 networks, when we're in a test network and excluding guards would
12187 exclude all relays. This typically occurs in incredibly small tor
12188 networks, and those using "TestingAuthVoteGuard *". Fixes part of
12189 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
12191 o Minor bugfixes (testing):
12192 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
12193 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
12194 - Stop spawn test failures due to a race condition between the
12195 SIGCHLD handler updating the process status, and the test reading
12196 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
12197 - Avoid passing an extra backslash when creating a temporary
12198 directory for running the unit tests on Windows. Fixes bug 12392;
12199 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
12201 o Minor bugfixes (TLS):
12202 - Check more thoroughly throughout the TLS code for possible
12203 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
12205 o Minor bugfixes (transparent proxy):
12206 - Use getsockname, not getsockopt, to retrieve the address for a
12207 TPROXY-redirected connection. Fixes bug 13796; bugfix
12210 o Minor bugfixes (windows):
12211 - Remove code to special-case handling of NTE_BAD_KEYSET when
12212 acquiring windows CryptoAPI context. This error can't actually
12213 occur for the parameters we're providing. Fixes bug 10816; bugfix
12216 o Minor bugfixes (zlib):
12217 - Avoid truncating a zlib stream when trying to finalize it with an
12218 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
12220 o Code simplification and refactoring:
12221 - Change the entry_is_live() function to take named bitfield
12222 elements instead of an unnamed list of booleans. Closes
12224 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
12225 Resolves ticket 12205.
12226 - Use calloc and reallocarray functions instead of multiply-
12227 then-malloc. This makes it less likely for us to fall victim to an
12228 integer overflow attack when allocating. Resolves ticket 12855.
12229 - Use the standard macro name SIZE_MAX, instead of our
12231 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
12232 functions which take them as arguments. Replace 0 with NO_DIRINFO
12233 in a function call for clarity. Seeks to prevent future issues
12235 - Avoid 4 null pointer errors under clang static analysis by using
12236 tor_assert() to prove that the pointers aren't null. Fixes
12238 - Rework the API of policies_parse_exit_policy() to use a bitmask to
12239 represent parsing options, instead of a confusing mess of
12240 booleans. Resolves ticket 8197.
12241 - Introduce a helper function to parse ExitPolicy in
12242 or_options_t structure.
12243 - Move fields related to isolating and configuring client ports into
12244 a shared structure. Previously, they were duplicated across
12245 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
12246 to copy them correctly had been the cause of at least one bug in
12247 the past. Closes ticket 8546.
12248 - Refactor the get_interface_addresses_raw() doom-function into
12249 multiple smaller and simpler subfunctions. Cover the resulting
12250 subfunctions with unit-tests. Fixes a significant portion of
12252 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
12253 only for version <= 0.2.2.24 which is now deprecated. Closes
12255 - Remove a test for a long-defunct broken version-one
12257 - Refactor main loop to extract the 'loop' part. This makes it
12258 easier to run Tor under Shadow. Closes ticket 15176.
12259 - Stop using can_complete_circuits as a global variable; access it
12260 with a function instead.
12261 - Avoid using operators directly as macro arguments: this lets us
12262 apply coccinelle transformations to our codebase more directly.
12263 Closes ticket 13172.
12264 - Combine the functions used to parse ClientTransportPlugin and
12265 ServerTransportPlugin into a single function. Closes ticket 6456.
12266 - Add inline functions and convenience macros for inspecting channel
12267 state. Refactor the code to use convenience macros instead of
12268 checking channel state directly. Fixes issue 7356.
12269 - Document all members of was_router_added_t and rename
12270 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
12271 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
12272 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
12273 constant instead of hardcoded value. Fixes issue 13840.
12274 - Refactor our generic strmap and digestmap types into a single
12275 implementation, so that we can add a new digest256map
12279 - Add a doc/TUNING document with tips for handling large numbers of
12280 TCP connections when running busy Tor relay. Update the warning
12281 message to point to this file when running out of sockets
12282 operating system is allowing to use simultaneously. Resolves
12284 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
12285 for writing the OpenBSD-specific tips. Resolves ticket 13702.
12286 - Make the tor-resolve documentation match its help string and its
12287 options. Resolves part of ticket 14325.
12288 - Log a more useful error message from tor-resolve when failing to
12289 look up a hidden service address. Resolves part of ticket 14325.
12290 - Document the bridge-authority-only 'networkstatus-bridges' file.
12291 Closes ticket 13713; patch from "tom".
12292 - Fix typo in PredictedPortsRelevanceTime option description in
12293 manpage. Resolves issue 13707.
12294 - Stop suggesting that users specify relays by nickname: it isn't a
12295 good idea. Also, properly cross-reference how to specify relays in
12296 all parts of manual documenting options that take a list of
12297 relays. Closes ticket 13381.
12298 - Clarify the HiddenServiceDir option description in manpage to make
12299 it clear that relative paths are taken with respect to the current
12300 working directory. Also clarify that this behavior is not
12301 guaranteed to remain indefinitely. Fixes issue 13913.
12303 o Distribution (systemd):
12304 - systemd unit file: only allow tor to write to /var/lib/tor and
12305 /var/log/tor. The rest of the filesystem is accessible for reading
12306 only. Patch by intrigeri; resolves ticket 12751.
12307 - systemd unit file: ensure that the process and all its children
12308 can never gain new privileges. Patch by intrigeri; resolves
12310 - systemd unit file: set up /var/run/tor as writable for the Tor
12311 service. Patch by intrigeri; resolves ticket 13196.
12313 o Downgraded warnings:
12314 - Don't warn when we've attempted to contact a relay using the wrong
12315 ntor onion key. Closes ticket 9635.
12318 - Remove some lingering dead code that once supported mempools.
12319 Mempools were disabled by default in 0.2.5, and removed entirely
12320 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
12323 o Removed features (directory authorities):
12324 - Remove code that prevented authorities from listing Tor relays
12325 affected by CVE-2011-2769 as guards. These relays are already
12326 rejected altogether due to the minimum version requirement of
12327 0.2.3.16-alpha. Closes ticket 13152.
12328 - The "AuthDirRejectUnlisted" option no longer has any effect, as
12329 the fingerprints file (approved-routers) has been deprecated.
12330 - Directory authorities do not support being Naming dirauths anymore.
12331 The "NamingAuthoritativeDir" config option is now obsolete.
12332 - Directory authorities do not support giving out the BadDirectory
12334 - Directory authorities no longer advertise or support consensus
12335 methods 1 through 12 inclusive. These consensus methods were
12336 obsolete and/or insecure: maintaining the ability to support them
12337 served no good purpose. Implements part of proposal 215; closes
12340 o Removed features:
12341 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
12342 longer silently accepted as an alias for "ExitNodes".
12343 - The --enable-mempool and --enable-buf-freelists options, which
12344 were originally created to work around bad malloc implementations,
12345 no longer exist. They were off-by-default in 0.2.5. Closes
12347 - We no longer remind the user about configuration options that have
12348 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
12349 - Remove our old, non-weighted bandwidth-based node selection code.
12350 Previously, we used it as a fallback when we couldn't perform
12351 weighted bandwidth-based node selection. But that would only
12352 happen in the cases where we had no consensus, or when we had a
12353 consensus generated by buggy or ancient directory authorities. In
12354 either case, it's better to use the more modern, better maintained
12355 algorithm, with reasonable defaults for the weights. Closes
12357 - Remove the --disable-curve25519 configure option. Relays and
12358 clients now are required to support curve25519 and the
12360 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
12361 used to be deprecated synonyms for "StrictNodes", are now marked
12362 obsolete. Resolves ticket 12226.
12363 - Clients don't understand the BadDirectory flag in the consensus
12364 anymore, and ignore it.
12366 o Removed platform support:
12367 - We no longer include special code to build on Windows CE; as far
12368 as we know, nobody has used Tor on Windows CE in a very long time.
12369 Closes ticket 11446.
12371 o Testing (test-network.sh):
12372 - Stop using "echo -n", as some shells' built-in echo doesn't
12373 support "-n". Instead, use "/bin/echo -n". Partially fixes
12375 - Stop an apparent test-network hang when used with make -j2. Fixes
12377 - Add a --delay option to test-network.sh, which configures the
12378 delay before the chutney network tests for data transmission.
12379 Partially implements ticket 13161.
12382 - Test that tor does not fail when key files are zero-length. Check
12383 that tor generates new keys, and overwrites the empty key files.
12384 - Test that tor generates new keys when keys are missing
12385 (existing behavior).
12386 - Test that tor does not overwrite key files that already contain
12387 data (existing behavior). Tests bug 13111. Patch by "teor".
12388 - New "make test-stem" target to run stem integration tests.
12389 Requires that the "STEM_SOURCE_DIR" environment variable be set.
12390 Closes ticket 14107.
12391 - Make the test_cmdline_args.py script work correctly on Windows.
12392 Patch from Gisle Vanem.
12393 - Move the slower unit tests into a new "./src/test/test-slow"
12394 binary that can be run independently of the other tests. Closes
12396 - New tests for many parts of channel, relay, and circuitmux
12397 functionality. Code by Andrea; part of 9262.
12398 - New tests for parse_transport_line(). Part of ticket 6456.
12399 - In the unit tests, use chgrp() to change the group of the unit
12400 test temporary directory to the current user, so that the sticky
12401 bit doesn't interfere with tests that check directory groups.
12403 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
12405 - Refactor the function that chooses guard nodes so that it can more
12406 easily be tested; write some tests for it.
12407 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
12408 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
12409 - Create unit tests for format_time_interval(). With bug 13393.
12410 - Add unit tests for tor_timegm signed overflow, tor_timegm and
12411 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
12412 tests (visible) fixes in bug 13476.
12413 - Add a "coverage-html" make target to generate HTML-visualized
12414 coverage results when building with --enable-coverage. (Requires
12415 lcov.) Patch from Kevin Murray.
12416 - Enable the backtrace handler (where supported) when running the
12418 - Revise all unit tests that used the legacy test_* macros to
12419 instead use the recommended tt_* macros. This patch was generated
12420 with coccinelle, to avoid manual errors. Closes ticket 13119.
12422 Changes in version 0.2.5.11 - 2015-03-17
12423 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
12425 It backports several bugfixes from the 0.2.6 branch, including a
12426 couple of medium-level security fixes for relays and exit nodes.
12427 It also updates the list of directory authorities.
12429 o Directory authority changes:
12430 - Remove turtles as a directory authority.
12431 - Add longclaw as a new (v3) directory authority. This implements
12432 ticket 13296. This keeps the directory authority count at 9.
12433 - The directory authority Faravahar has a new IP address. This
12434 closes ticket 14487.
12436 o Major bugfixes (crash, OSX, security):
12437 - Fix a remote denial-of-service opportunity caused by a bug in
12438 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
12441 o Major bugfixes (relay, stability, possible security):
12442 - Fix a bug that could lead to a relay crashing with an assertion
12443 failure if a buffer of exactly the wrong layout was passed to
12444 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
12445 0.2.0.10-alpha. Patch from 'cypherpunks'.
12446 - Do not assert if the 'data' pointer on a buffer is advanced to the
12447 very end of the buffer; log a BUG message instead. Only assert if
12448 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
12450 o Major bugfixes (exit node stability):
12451 - Fix an assertion failure that could occur under high DNS load.
12452 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
12453 diagnosed and fixed by "cypherpunks".
12455 o Major bugfixes (Linux seccomp2 sandbox):
12456 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
12457 crash during attempts to call wait4. Fixes bug 15088; bugfix on
12458 0.2.5.1-alpha. Patch from "sanic".
12460 o Minor features (controller):
12461 - New "GETINFO bw-event-cache" to get information about recent
12462 bandwidth events. Closes ticket 14128. Useful for controllers to
12463 get recent bandwidth history after the fix for ticket 13988.
12465 o Minor features (geoip):
12466 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
12467 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
12470 o Minor bugfixes (client, automapping):
12471 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
12472 no value follows the option. Fixes bug 14142; bugfix on
12473 0.2.4.7-alpha. Patch by "teor".
12474 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
12475 14195; bugfix on 0.1.0.1-rc.
12477 o Minor bugfixes (compilation):
12478 - Build without warnings with the stock OpenSSL srtp.h header, which
12479 has a duplicate declaration of SSL_get_selected_srtp_profile().
12480 Fixes bug 14220; this is OpenSSL's bug, not ours.
12482 o Minor bugfixes (directory authority):
12483 - Allow directory authorities to fetch more data from one another if
12484 they find themselves missing lots of votes. Previously, they had
12485 been bumping against the 10 MB queued data limit. Fixes bug 14261;
12486 bugfix on 0.1.2.5-alpha.
12487 - Enlarge the buffer to read bwauth generated files to avoid an
12488 issue when parsing the file in dirserv_read_measured_bandwidths().
12489 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
12491 o Minor bugfixes (statistics):
12492 - Increase period over which bandwidth observations are aggregated
12493 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
12495 o Minor bugfixes (preventative security, C safety):
12496 - When reading a hexadecimal, base-32, or base-64 encoded value from
12497 a string, always overwrite the whole output buffer. This prevents
12498 some bugs where we would look at (but fortunately, not reveal)
12499 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
12503 Changes in version 0.2.4.26 - 2015-03-17
12504 Tor 0.2.4.26 includes an updated list of directory authorities. It
12505 also backports a couple of stability and security bugfixes from 0.2.5
12508 o Directory authority changes:
12509 - Remove turtles as a directory authority.
12510 - Add longclaw as a new (v3) directory authority. This implements
12511 ticket 13296. This keeps the directory authority count at 9.
12512 - The directory authority Faravahar has a new IP address. This
12513 closes ticket 14487.
12515 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
12516 - Fix an assertion failure that could occur under high DNS load.
12517 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
12518 diagnosed and fixed by "cypherpunks".
12520 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
12521 - Fix a bug that could lead to a relay crashing with an assertion
12522 failure if a buffer of exactly the wrong layout was passed to
12523 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
12524 0.2.0.10-alpha. Patch from 'cypherpunks'.
12525 - Do not assert if the 'data' pointer on a buffer is advanced to the
12526 very end of the buffer; log a BUG message instead. Only assert if
12527 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
12529 o Minor features (geoip):
12530 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
12531 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
12534 Changes in version 0.2.5.10 - 2014-10-24
12535 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
12537 It adds several new security features, including improved
12538 denial-of-service resistance for relays, new compiler hardening
12539 options, and a system-call sandbox for hardened installations on Linux
12540 (requires seccomp2). The controller protocol has several new features,
12541 resolving IPv6 addresses should work better than before, and relays
12542 should be a little more CPU-efficient. We've added support for more
12543 OpenBSD and FreeBSD transparent proxy types. We've improved the build
12544 system and testing infrastructure to allow unit testing of more parts
12545 of the Tor codebase. Finally, we've addressed several nagging pluggable
12546 transport usability issues, and included numerous other small bugfixes
12547 and features mentioned below.
12549 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
12550 have accumulated many known flaws; everyone should upgrade.
12552 o Major features (security):
12553 - The ntor handshake is now on-by-default, no matter what the
12554 directory authorities recommend. Implements ticket 8561.
12555 - Make the "tor-gencert" tool used by directory authority operators
12556 create 2048-bit signing keys by default (rather than 1024-bit, since
12557 1024-bit is uncomfortably small these days). Addresses ticket 10324.
12558 - Warn about attempts to run hidden services and relays in the same
12559 process: that's probably not a good idea. Closes ticket 12908.
12560 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
12561 today support TLS 1.0 or later, so we can safely turn off support
12562 for this old (and insecure) protocol. Fixes bug 13426.
12564 o Major features (relay security, DoS-resistance):
12565 - When deciding whether we have run out of memory and we need to
12566 close circuits, also consider memory allocated in buffers for
12567 streams attached to each circuit.
12569 This change, which extends an anti-DoS feature introduced in
12570 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
12571 better resist more memory-based DoS attacks than before. Since the
12572 MaxMemInCellQueues option now applies to all queues, it is renamed
12573 to MaxMemInQueues. This feature fixes bug 10169.
12574 - Avoid hash-flooding denial-of-service attacks by using the secure
12575 SipHash-2-4 hash function for our hashtables. Without this
12576 feature, an attacker could degrade performance of a targeted
12577 client or server by flooding their data structures with a large
12578 number of entries to be stored at the same hash table position,
12579 thereby slowing down the Tor instance. With this feature, hash
12580 table positions are derived from a randomized cryptographic key,
12581 and an attacker cannot predict which entries will collide. Closes
12583 - If you don't specify MaxMemInQueues yourself, Tor now tries to
12584 pick a good value based on your total system memory. Previously,
12585 the default was always 8 GB. You can still override the default by
12586 setting MaxMemInQueues yourself. Resolves ticket 11396.
12588 o Major features (bridges and pluggable transports):
12589 - Add support for passing arguments to managed pluggable transport
12590 proxies. Implements ticket 3594.
12591 - Bridges now track GeoIP information and the number of their users
12592 even when pluggable transports are in use, and report usage
12593 statistics in their extra-info descriptors. Resolves tickets 4773
12595 - Don't launch pluggable transport proxies if we don't have any
12596 bridges configured that would use them. Now we can list many
12597 pluggable transports, and Tor will dynamically start one when it
12598 hears a bridge address that needs it. Resolves ticket 5018.
12599 - The bridge directory authority now assigns status flags (Stable,
12600 Guard, etc) to bridges based on thresholds calculated over all
12601 Running bridges. Now bridgedb can finally make use of its features
12602 to e.g. include at least one Stable bridge in its answers. Fixes
12605 o Major features (controller):
12606 - Extend ORCONN controller event to include an "ID" parameter,
12607 and add four new controller event types CONN_BW, CIRC_BW,
12608 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
12609 The new events are emitted in private Tor networks only, with the
12610 goal of being able to better track performance and load during
12611 full-network simulations. Implements proposal 218 and ticket 7359.
12613 o Major features (relay performance):
12614 - Speed up server-side lookups of rendezvous and introduction point
12615 circuits by using hashtables instead of linear searches. These
12616 functions previously accounted between 3 and 7% of CPU usage on
12617 some busy relays. Resolves ticket 9841.
12618 - Avoid wasting CPU when extending a circuit over a channel that is
12619 nearly out of circuit IDs. Previously, we would do a linear scan
12620 over possible circuit IDs before finding one or deciding that we
12621 had exhausted our possibilities. Now, we try at most 64 random
12622 circuit IDs before deciding that we probably won't succeed. Fixes
12623 a possible root cause of ticket 11553.
12625 o Major features (seccomp2 sandbox, Linux only):
12626 - Use the seccomp2 syscall filtering facility on Linux to limit
12627 which system calls Tor can invoke. This is an experimental,
12628 Linux-only feature to provide defense-in-depth against unknown
12629 attacks. To try turning it on, set "Sandbox 1" in your torrc
12630 file. Please be ready to report bugs. We hope to add support
12631 for better sandboxing in the future, including more fine-grained
12632 filters, better division of responsibility, and support for more
12633 platforms. This work has been done by Cristian-Matei Toader for
12634 Google Summer of Code. Resolves tickets 11351 and 11465.
12636 o Major features (testing networks):
12637 - Make testing Tor networks bootstrap better: lower directory fetch
12638 retry schedules and maximum interval without directory requests,
12639 and raise maximum download tries. Implements ticket 6752.
12640 - Add make target 'test-network' to run tests on a Chutney network.
12641 Implements ticket 8530.
12643 o Major features (other):
12644 - On some platforms (currently: recent OSX versions, glibc-based
12645 platforms that support the ELF format, and a few other
12646 Unix-like operating systems), Tor can now dump stack traces
12647 when a crash occurs or an assertion fails. By default, traces
12648 are dumped to stderr (if possible) and to any logs that are
12649 reporting errors. Implements ticket 9299.
12651 o Deprecated versions:
12652 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
12653 attention for some while.
12655 o Major bugfixes (security, directory authorities):
12656 - Directory authorities now include a digest of each relay's
12657 identity key as a part of its microdescriptor.
12659 This is a workaround for bug 11743 (reported by "cypherpunks"),
12660 where Tor clients do not support receiving multiple
12661 microdescriptors with the same SHA256 digest in the same
12662 consensus. When clients receive a consensus like this, they only
12663 use one of the relays. Without this fix, a hostile relay could
12664 selectively disable some client use of target relays by
12665 constructing a router descriptor with a different identity and the
12666 same microdescriptor parameters and getting the authorities to
12667 list it in a microdescriptor consensus. This fix prevents an
12668 attacker from causing a microdescriptor collision, because the
12669 router's identity is not forgeable.
12671 o Major bugfixes (openssl bug workaround):
12672 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
12673 1.0.1j, built with the 'no-ssl3' configuration option. Fixes
12674 bug 13471. This is a workaround for an OpenSSL bug.
12676 o Major bugfixes (client):
12677 - Perform circuit cleanup operations even when circuit
12678 construction operations are disabled (because the network is
12679 disabled, or because there isn't enough directory information).
12680 Previously, when we were not building predictive circuits, we
12681 were not closing expired circuits either. Fixes bug 8387; bugfix on
12682 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
12683 became more strict about when we have "enough directory information
12684 to build circuits".
12686 o Major bugfixes (client, pluggable transports):
12687 - When managing pluggable transports, use OS notification facilities
12688 to learn if they have crashed, and don't attempt to kill any
12689 process that has already exited. Fixes bug 8746; bugfix
12692 o Major bugfixes (relay denial of service):
12693 - Instead of writing destroy cells directly to outgoing connection
12694 buffers, queue them and intersperse them with other outgoing cells.
12695 This can prevent a set of resource starvation conditions where too
12696 many pending destroy cells prevent data cells from actually getting
12697 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
12698 bugfix on 0.2.0.1-alpha.
12700 o Major bugfixes (relay):
12701 - Avoid queuing or sending destroy cells for circuit ID zero when we
12702 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
12703 Found and fixed by "cypherpunks".
12704 - Fix ORPort reachability detection on relays running behind a
12705 proxy, by correctly updating the "local" mark on the controlling
12706 channel when changing the address of an or_connection_t after the
12707 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
12708 - Use a direct dirport connection when uploading non-anonymous
12709 descriptors to the directory authorities. Previously, relays would
12710 incorrectly use tunnel connections under a fairly wide variety of
12711 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
12712 - When a circuit accidentally has the same circuit ID for its
12713 forward and reverse direction, correctly detect the direction of
12714 cells using that circuit. Previously, this bug made roughly one
12715 circuit in a million non-functional. Fixes bug 12195; this is a
12716 bugfix on every version of Tor.
12718 o Minor features (security):
12719 - New --enable-expensive-hardening option to enable security
12720 hardening options that consume nontrivial amounts of CPU and
12721 memory. Right now, this includes AddressSanitizer and UbSan, which
12722 are supported in newer versions of GCC and Clang. Closes ticket
12724 - Authorities now assign the Guard flag to the fastest 25% of the
12725 network (it used to be the fastest 50%). Also raise the consensus
12726 weight that guarantees the Guard flag from 250 to 2000. For the
12727 current network, this results in about 1100 guards, down from 2500.
12728 This step paves the way for moving the number of entry guards
12729 down to 1 (proposal 236) while still providing reasonable expected
12730 performance for most users. Implements ticket 12690.
12732 o Minor features (security, memory management):
12733 - Memory allocation tricks (mempools and buffer freelists) are now
12734 disabled by default. You can turn them back on with
12735 --enable-mempools and --enable-buf-freelists respectively. We're
12736 disabling these features because malloc performance is good enough
12737 on most platforms, and a similar feature in OpenSSL exacerbated
12738 exploitation of the Heartbleed attack. Resolves ticket 11476.
12740 o Minor features (bridge client):
12741 - Report a more useful failure message when we can't connect to a
12742 bridge because we don't have the right pluggable transport
12743 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
12745 o Minor features (bridge):
12746 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
12747 cookie file for the ExtORPort g+r by default.
12749 o Minor features (bridges, pluggable transports):
12750 - Bridges now write the SHA1 digest of their identity key
12751 fingerprint (that is, a hash of a hash of their public key) to
12752 notice-level logs, and to a new hashed-fingerprint file. This
12753 information will help bridge operators look up their bridge in
12754 Globe and similar tools. Resolves ticket 10884.
12755 - Improve the message that Tor displays when running as a bridge
12756 using pluggable transports without an Extended ORPort listener.
12757 Also, log the message in the log file too. Resolves ticket 11043.
12758 - Add threshold cutoffs to the networkstatus document created by
12759 the Bridge Authority. Fixes bug 1117.
12760 - On Windows, spawn background processes using the CREATE_NO_WINDOW
12761 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
12762 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
12763 Vidalia set this option for us.) Implements ticket 10297.
12765 o Minor features (build):
12766 - The configure script has a --disable-seccomp option to turn off
12767 support for libseccomp on systems that have it, in case it (or
12768 Tor's use of it) is broken. Resolves ticket 11628.
12769 - Assume that a user using ./configure --host wants to cross-compile,
12770 and give an error if we cannot find a properly named
12771 tool-chain. Add a --disable-tool-name-check option to proceed
12772 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
12773 - If we run ./configure and the compiler recognizes -fstack-protector
12774 but the linker rejects it, warn the user about a potentially missing
12775 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
12776 - Add support for `--library-versions` flag. Implements ticket 6384.
12777 - Return the "unexpected sendme" warnings to a warn severity, but make
12778 them rate limited, to help diagnose ticket 8093.
12779 - Detect a missing asciidoc, and warn the user about it, during
12780 configure rather than at build time. Fixes issue 6506. Patch from
12783 o Minor features (client):
12784 - Add a new option, PredictedPortsRelevanceTime, to control how long
12785 after having received a request to connect to a given port Tor
12786 will try to keep circuits ready in anticipation of future requests
12787 for that port. Patch from "unixninja92"; implements ticket 9176.
12789 o Minor features (config options and command line):
12790 - Add an --allow-missing-torrc commandline option that tells Tor to
12791 run even if the configuration file specified by -f is not available.
12792 Implements ticket 10060.
12793 - Add support for the TPROXY transparent proxying facility on Linux.
12794 See documentation for the new TransProxyType option for more
12795 details. Implementation by "thomo". Closes ticket 10582.
12797 o Minor features (config options):
12798 - Config (torrc) lines now handle fingerprints which are missing
12799 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
12800 - Support a --dump-config option to print some or all of the
12801 configured options. Mainly useful for debugging the command-line
12802 option parsing code. Helps resolve ticket 4647.
12803 - Raise awareness of safer logging: notify user of potentially
12804 unsafe config options, like logging more verbosely than severity
12805 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
12806 - Add a new configuration option TestingV3AuthVotingStartOffset
12807 that bootstraps a network faster by changing the timing for
12808 consensus votes. Addresses ticket 8532.
12809 - Add a new torrc option "ServerTransportOptions" that allows
12810 bridge operators to pass configuration parameters to their
12811 pluggable transports. Resolves ticket 8929.
12812 - The config (torrc) file now accepts bandwidth and space limits in
12813 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
12814 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
12817 o Minor features (controller):
12818 - Make the entire exit policy available from the control port via
12819 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
12821 - Because of the fix for ticket 11396, the real limit for memory
12822 usage may no longer match the configured MaxMemInQueues value. The
12823 real limit is now exposed via GETINFO limits/max-mem-in-queues.
12824 - Add a new "HS_DESC" controller event that reports activities
12825 related to hidden service descriptors. Resolves ticket 8510.
12826 - New "DROPGUARDS" controller command to forget all current entry
12827 guards. Not recommended for ordinary use, since replacing guards
12828 too frequently makes several attacks easier. Resolves ticket 9934;
12830 - Implement the TRANSPORT_LAUNCHED control port event that
12831 notifies controllers about new launched pluggable
12832 transports. Resolves ticket 5609.
12834 o Minor features (diagnostic):
12835 - When logging a warning because of bug 7164, additionally check the
12836 hash table for consistency (as proposed on ticket 11737). This may
12837 help diagnose bug 7164.
12838 - When we log a heartbeat, log how many one-hop circuits we have
12839 that are at least 30 minutes old, and log status information about
12840 a few of them. This is an attempt to track down bug 8387.
12841 - When encountering an unexpected CR while writing text to a file on
12842 Windows, log the name of the file. Should help diagnosing
12844 - Give more specific warnings when a client notices that an onion
12845 handshake has failed. Fixes ticket 9635.
12846 - Add significant new logging code to attempt to diagnose bug 12184,
12847 where relays seem to run out of available circuit IDs.
12848 - Improve the diagnostic log message for bug 8387 even further to
12849 try to improve our odds of figuring out why one-hop directory
12850 circuits sometimes do not get closed.
12851 - Add more log messages to diagnose bug 7164, which causes
12852 intermittent "microdesc_free() called but md was still referenced"
12853 warnings. We now include more information, to figure out why we
12854 might be cleaning a microdescriptor for being too old if it's
12855 still referenced by a live node_t object.
12856 - Log current accounting state (bytes sent and received + remaining
12857 time for the current accounting period) in the relay's heartbeat
12858 message. Implements ticket 5526; patch from Peter Retzlaff.
12860 o Minor features (geoip):
12861 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
12864 o Minor features (interface):
12865 - Generate a warning if any ports are listed in the SocksPolicy,
12866 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
12867 AuthDirBadExit options. (These options only support address
12868 ranges.) Fixes part of ticket 11108.
12870 o Minor features (kernel API usage):
12871 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
12872 sockets in a single system call. Implements ticket 5129.
12874 o Minor features (log messages):
12875 - When ServerTransportPlugin is set on a bridge, Tor can write more
12876 useful statistics about bridge use in its extrainfo descriptors,
12877 but only if the Extended ORPort ("ExtORPort") is set too. Add a
12878 log message to inform the user in this case. Resolves ticket 9651.
12879 - When receiving a new controller connection, log the origin address.
12880 Resolves ticket 9698; patch from "sigpipe".
12881 - When logging OpenSSL engine status at startup, log the status of
12882 more engines. Fixes ticket 10043; patch from Joshua Datko.
12884 o Minor features (log verbosity):
12885 - Demote the message that we give when a flushing connection times
12886 out for too long from NOTICE to INFO. It was usually meaningless.
12887 Resolves ticket 5286.
12888 - Don't log so many notice-level bootstrapping messages at startup
12889 about downloading descriptors. Previously, we'd log a notice
12890 whenever we learned about more routers. Now, we only log a notice
12891 at every 5% of progress. Fixes bug 9963.
12892 - Warn less verbosely when receiving a malformed
12893 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
12895 o Minor features (performance):
12896 - If we're using the pure-C 32-bit curve25519_donna implementation
12897 of curve25519, build it with the -fomit-frame-pointer option to
12898 make it go faster on register-starved hosts. This improves our
12899 handshake performance by about 6% on i386 hosts without nacl.
12900 Closes ticket 8109.
12902 o Minor features (relay):
12903 - If a circuit timed out for at least 3 minutes, check if we have a
12904 new external IP address, and publish a new descriptor with the new
12905 IP address if it changed. Resolves ticket 2454.
12907 o Minor features (testing):
12908 - If Python is installed, "make check" now runs extra tests beyond
12909 the unit test scripts.
12910 - When bootstrapping a test network, sometimes very few relays get
12911 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
12912 specify a set of relays which should be voted Guard regardless of
12913 their uptime or bandwidth. Addresses ticket 9206.
12915 o Minor features (transparent proxy, *BSD):
12916 - Support FreeBSD's ipfw firewall interface for TransPort ports on
12917 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
12918 10267; patch from "yurivict".
12919 - Support OpenBSD's divert-to rules with the pf firewall for
12920 transparent proxy ports. To enable it, set "TransProxyType
12921 pf-divert". This allows Tor to run a TransPort transparent proxy
12922 port on OpenBSD 4.4 or later without root privileges. See the
12923 pf.conf(5) manual page for information on configuring pf to use
12924 divert-to rules. Closes ticket 10896; patch from Dana Koch.
12926 o Minor bugfixes (bridge client):
12927 - Stop accepting bridge lines containing hostnames. Doing so would
12928 cause clients to perform DNS requests on the hostnames, which was
12929 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
12931 o Minor bugfixes (bridges):
12932 - Avoid potential crashes or bad behavior when launching a
12933 server-side managed proxy with ORPort or ExtORPort temporarily
12934 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
12935 - Fix a bug where the first connection works to a bridge that uses a
12936 pluggable transport with client-side parameters, but we don't send
12937 the client-side parameters on subsequent connections. (We don't
12938 use any pluggable transports with client-side parameters yet,
12939 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
12940 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
12942 o Minor bugfixes (build, auxiliary programs):
12943 - Stop preprocessing the "torify" script with autoconf, since
12944 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
12946 - The tor-fw-helper program now follows the standard convention and
12947 exits with status code "0" on success. Fixes bug 9030; bugfix on
12948 0.2.3.1-alpha. Patch by Arlo Breault.
12949 - Corrected ./configure advice for what openssl dev package you should
12950 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
12952 o Minor bugfixes (client):
12953 - Avoid "Tried to open a socket with DisableNetwork set" warnings
12954 when starting a client with bridges configured and DisableNetwork
12955 set. (Tor launcher starts Tor with DisableNetwork set the first
12956 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
12957 - Improve the log message when we can't connect to a hidden service
12958 because all of the hidden service directory nodes hosting its
12959 descriptor are excluded. Improves on our fix for bug 10722, which
12960 was a bugfix on 0.2.0.10-alpha.
12961 - Raise a control port warning when we fail to connect to all of
12962 our bridges. Previously, we didn't inform the controller, and
12963 the bootstrap process would stall. Fixes bug 11069; bugfix on
12965 - Exit immediately when a process-owning controller exits.
12966 Previously, tor relays would wait for a little while after their
12967 controller exited, as if they had gotten an INT signal -- but this
12968 was problematic, since there was no feedback for the user. To do a
12969 clean shutdown, controllers should send an INT signal and give Tor
12970 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
12971 - Stop attempting to connect to bridges before our pluggable
12972 transports are configured (harmless but resulted in some erroneous
12973 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
12974 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
12975 generating incorrect SOCKS5 responses, and confusing client
12976 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
12978 o Minor bugfixes (client, DNSPort):
12979 - When using DNSPort, try to respond to AAAA requests with AAAA
12980 answers. Previously, we hadn't looked at the request type when
12981 deciding which answer type to prefer. Fixes bug 10468; bugfix on
12983 - When receiving a DNS query for an unsupported record type, reply
12984 with no answer rather than with a NOTIMPL error. This behavior
12985 isn't correct either, but it will break fewer client programs, we
12986 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
12989 o Minor bugfixes (client, logging during bootstrap):
12990 - Only report the first fatal bootstrap error on a given OR
12991 connection. This stops us from telling the controller bogus error
12992 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
12993 - Avoid generating spurious warnings when starting with
12994 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
12997 o Minor bugfixes (closing OR connections):
12998 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
12999 check if it's an or_connection_t and correctly call
13000 connection_or_close_for_error() rather than
13001 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
13003 - When closing all connections on setting DisableNetwork to 1, use
13004 connection_or_close_normally() rather than closing OR connections
13005 out from under the channel layer. Fixes bug 11306; bugfix on
13008 o Minor bugfixes (code correctness):
13009 - Previously we used two temporary files when writing descriptors to
13010 disk; now we only use one. Fixes bug 1376.
13011 - Remove an erroneous (but impossible and thus harmless) pointer
13012 comparison that would have allowed compilers to skip a bounds
13013 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
13014 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
13015 - Fix an always-true assertion in pluggable transports code so it
13016 actually checks what it was trying to check. Fixes bug 10046;
13017 bugfix on 0.2.3.9-alpha. Found by "dcb".
13019 o Minor bugfixes (command line):
13020 - Use a single command-line parser for parsing torrc options on the
13021 command line and for finding special command-line options to avoid
13022 inconsistent behavior for torrc option arguments that have the same
13023 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
13025 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
13026 9573; bugfix on 0.0.9pre5.
13028 o Minor bugfixes (compilation):
13029 - Compile correctly with builds and forks of OpenSSL (such as
13030 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
13031 0.2.1.1-alpha. Patch from "dhill".
13032 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
13033 turned off (that is, without support for v2 link handshakes). Fixes
13034 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
13035 - In routerlist_assert_ok(), don't take the address of a
13036 routerinfo's cache_info member unless that routerinfo is non-NULL.
13037 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
13038 - Fix a large number of false positive warnings from the clang
13039 analyzer static analysis tool. This should make real warnings
13040 easier for clang analyzer to find. Patch from "teor". Closes
13042 - Resolve GCC complaints on OpenBSD about discarding constness in
13043 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
13044 on 0.1.1.23. Patch from Dana Koch.
13045 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
13046 treatment of long and time_t as comparable types. Fixes part of
13047 bug 11633. Patch from Dana Koch.
13048 - When deciding whether to build the 64-bit curve25519
13049 implementation, detect platforms where we can compile 128-bit
13050 arithmetic but cannot link it. Fixes bug 11729; bugfix on
13051 0.2.4.8-alpha. Patch from "conradev".
13052 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
13053 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
13054 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
13056 - Build and run correctly on systems like OpenBSD-current that have
13057 patched OpenSSL to remove get_cipher_by_char and/or its
13058 implementations. Fixes issue 13325.
13060 o Minor bugfixes (controller and command-line):
13061 - If changing a config option via "setconf" fails in a recoverable
13062 way, we used to nonetheless write our new control ports to the
13063 file described by the "ControlPortWriteToFile" option. Now we only
13064 write out that file if we successfully switch to the new config
13065 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
13067 o Minor bugfixes (directory server):
13068 - No longer accept malformed http headers when parsing urls from
13069 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
13070 bugfix on 0.0.6pre1.
13071 - When sending a compressed set of descriptors or microdescriptors,
13072 make sure to finalize the zlib stream. Previously, we would write
13073 all the compressed data, but if the last descriptor we wanted to
13074 send was missing or too old, we would not mark the stream as
13075 finished. This caused problems for decompression tools. Fixes bug
13076 11648; bugfix on 0.1.1.23.
13078 o Minor bugfixes (hidden service):
13079 - Only retry attempts to connect to a chosen rendezvous point 8
13080 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
13082 o Minor bugfixes (interface):
13083 - Reject relative control socket paths and emit a warning. Previously,
13084 single-component control socket paths would be rejected, but Tor
13085 would not log why it could not validate the config. Fixes bug 9258;
13086 bugfix on 0.2.3.16-alpha.
13088 o Minor bugfixes (log messages):
13089 - Fix a bug where clients using bridges would report themselves
13090 as 50% bootstrapped even without a live consensus document.
13091 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
13092 - Suppress a warning where, if there's only one directory authority
13093 in the network, we would complain that votes and signatures cannot
13094 be uploaded to other directory authorities. Fixes bug 10842;
13095 bugfix on 0.2.2.26-beta.
13096 - Report bootstrapping progress correctly when we're downloading
13097 microdescriptors. We had updated our "do we have enough microdescs
13098 to begin building circuits?" logic most recently in 0.2.4.10-alpha
13099 (see bug 5956), but we left the bootstrap status event logic at
13100 "how far through getting 1/4 of them are we?" Fixes bug 9958;
13101 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
13103 o Minor bugfixes (logging):
13104 - Downgrade "Unexpected onionskin length after decryption" warning
13105 to a protocol-warn, since there's nothing relay operators can do
13106 about a client that sends them a malformed create cell. Resolves
13107 bug 12996; bugfix on 0.0.6rc1.
13108 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
13109 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
13110 - When logging information about an EXTEND2 or EXTENDED2 cell, log
13111 their names correctly. Fixes part of bug 12700; bugfix
13113 - When logging information about a relay cell whose command we don't
13114 recognize, log its command as an integer. Fixes part of bug 12700;
13115 bugfix on 0.2.1.10-alpha.
13116 - Escape all strings from the directory connection before logging
13117 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
13118 - Squelch a spurious LD_BUG message "No origin circuit for
13119 successful SOCKS stream" in certain hidden service failure cases;
13121 - Downgrade the severity of the 'unexpected sendme cell from client'
13122 from 'warn' to 'protocol warning'. Closes ticket 8093.
13124 o Minor bugfixes (misc code correctness):
13125 - In munge_extrainfo_into_routerinfo(), check the return value of
13126 memchr(). This would have been a serious issue if we ever passed
13127 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
13129 - On the chance that somebody manages to build Tor on a
13130 platform where time_t is unsigned, correct the way that
13131 microdesc_add_to_cache() handles negative time arguments.
13132 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
13133 - Fix various instances of undefined behavior in channeltls.c,
13134 tor_memmem(), and eventdns.c that would cause us to construct
13135 pointers to memory outside an allocated object. (These invalid
13136 pointers were not accessed, but C does not even allow them to
13137 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
13138 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
13139 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
13140 fix some miscellaneous errors in our tests and codebase. Fixes bug
13141 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
13142 - Always check return values for unlink, munmap, UnmapViewOfFile;
13143 check strftime return values more often. In some cases all we can
13144 do is report a warning, but this may help prevent deeper bugs from
13145 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
13147 - Fix numerous warnings from the clang "scan-build" static analyzer.
13148 Some of these are programming style issues; some of them are false
13149 positives that indicated awkward code; some are undefined behavior
13150 cases related to constructing (but not using) invalid pointers;
13151 some are assumptions about API behavior; some are (harmlessly)
13152 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
13153 correct; and one or two are genuine bugs that weren't reachable
13154 from the rest of the program. Fixes bug 8793; bugfixes on many,
13157 o Minor bugfixes (node selection):
13158 - If ExcludeNodes is set, consider non-excluded hidden service
13159 directory servers before excluded ones. Do not consider excluded
13160 hidden service directory servers at all if StrictNodes is
13161 set. (Previously, we would sometimes decide to connect to those
13162 servers, and then realize before we initiated a connection that
13163 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
13164 Reported by "mr-4".
13165 - If we set the ExitNodes option but it doesn't include any nodes
13166 that have the Exit flag, we would choose not to bootstrap. Now we
13167 bootstrap so long as ExitNodes includes nodes which can exit to
13168 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
13170 o Minor bugfixes (performance):
13171 - Avoid a bug where every successful connection made us recompute
13172 the flag telling us whether we have sufficient information to
13173 build circuits. Previously, we would forget our cached value
13174 whenever we successfully opened a channel (or marked a router as
13175 running or not running for any other reason), regardless of
13176 whether we had previously believed the router to be running. This
13177 forced us to run an expensive update operation far too often.
13178 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
13179 - Avoid using tor_memeq() for checking relay cell integrity. This
13180 removes a possible performance bottleneck. Fixes part of bug
13181 12169; bugfix on 0.2.1.31.
13183 o Minor bugfixes (platform-specific):
13184 - When dumping a malformed directory object to disk, save it in
13185 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
13187 - Don't report failures from make_socket_reuseable() on incoming
13188 sockets on OSX: this can happen when incoming connections close
13189 early. Fixes bug 10081.
13191 o Minor bugfixes (pluggable transports):
13192 - Avoid another 60-second delay when starting Tor in a pluggable-
13193 transport-using configuration when we already have cached
13194 descriptors for our bridges. Fixes bug 11965; bugfix
13197 o Minor bugfixes (protocol correctness):
13198 - When receiving a VERSIONS cell with an odd number of bytes, close
13199 the connection immediately since the cell is malformed. Fixes bug
13200 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
13203 o Minor bugfixes (relay, other):
13204 - We now drop CREATE cells for already-existent circuit IDs and for
13205 zero-valued circuit IDs, regardless of other factors that might
13206 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
13208 - When rejecting DATA cells for stream_id zero, still count them
13209 against the circuit's deliver window so that we don't fail to send
13210 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
13212 o Minor bugfixes (relay, threading):
13213 - Check return code on spawn_func() in cpuworker code, so that we
13214 don't think we've spawned a nonworking cpuworker and write junk to
13215 it forever. Fix related to bug 4345; bugfix on all released Tor
13216 versions. Found by "skruffy".
13217 - Use a pthread_attr to make sure that spawn_func() cannot return an
13218 error while at the same time launching a thread. Fix related to
13219 bug 4345; bugfix on all released Tor versions. Reported
13222 o Minor bugfixes (relays and bridges):
13223 - Avoid crashing on a malformed resolv.conf file when running a
13224 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
13225 - Non-exit relays no longer launch mock DNS requests to check for
13226 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
13227 non-exit relays stopped servicing DNS requests. Fixes bug 965;
13228 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
13229 - Bridges now report complete directory request statistics. Related
13230 to bug 5824; bugfix on 0.2.2.1-alpha.
13231 - Bridges now never collect statistics that were designed for
13232 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
13234 o Minor bugfixes (testing):
13235 - Fix all valgrind warnings produced by the unit tests. There were
13236 over a thousand memory leak warnings previously, mostly produced
13237 by forgetting to free things in the unit test code. Fixes bug
13238 11618, bugfixes on many versions of Tor.
13240 o Minor bugfixes (tor-fw-helper):
13241 - Give a correct log message when tor-fw-helper fails to launch.
13242 (Previously, we would say something like "tor-fw-helper sent us a
13243 string we could not parse".) Fixes bug 9781; bugfix
13246 o Minor bugfixes (trivial memory leaks):
13247 - Fix a small memory leak when signing a directory object. Fixes bug
13248 11275; bugfix on 0.2.4.13-alpha.
13249 - Resolve some memory leaks found by coverity in the unit tests, on
13250 exit in tor-gencert, and on a failure to compute digests for our
13251 own keys when generating a v3 networkstatus vote. These leaks
13252 should never have affected anyone in practice.
13254 o Code simplification and refactoring:
13255 - Remove some old fallback code designed to keep Tor clients working
13256 in a network with only two working relays. Elsewhere in the code we
13257 have long since stopped supporting such networks, so there wasn't
13258 much point in keeping it around. Addresses ticket 9926.
13259 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
13260 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
13261 - Extract the common duplicated code for creating a subdirectory
13262 of the data directory and writing to a file in it. Fixes ticket
13263 4282; patch from Peter Retzlaff.
13264 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
13265 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
13266 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
13267 - Add a set of accessor functions for the circuit timeout data
13268 structure. Fixes ticket 6153; patch from "piet".
13269 - Clean up exit paths from connection_listener_new(). Closes ticket
13270 8789. Patch from Arlo Breault.
13271 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
13272 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
13273 - Use a doubly-linked list to implement the global circuit list.
13274 Resolves ticket 9108. Patch from Marek Majkowski.
13275 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
13276 - Remove constants and tests for PKCS1 padding; it's insecure and
13277 shouldn't be used for anything new. Fixes bug 8792; patch
13279 - Remove instances of strcpy() from the unit tests. They weren't
13280 hurting anything, since they were only in the unit tests, but it's
13281 embarrassing to have strcpy() in the code at all, and some analysis
13282 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
13283 0.2.3.8-alpha. Patch from Arlo Breault.
13284 - Remove is_internal_IP() function. Resolves ticket 4645.
13285 - Remove unused function circuit_dump_by_chan from circuitlist.c.
13286 Closes issue 9107; patch from "marek".
13287 - Change our use of the ENUM_BF macro to avoid declarations that
13289 - Get rid of router->address, since in all cases it was just the
13290 string representation of router->addr. Resolves ticket 5528.
13293 - Adjust the URLs in the README to refer to the new locations of
13294 several documents on the website. Fixes bug 12830. Patch from
13296 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
13298 - Update manpage to describe some of the files you can expect to
13299 find in Tor's DataDirectory. Addresses ticket 9839.
13300 - Clean up several option names in the manpage to match their real
13301 names, add the missing documentation for a couple of testing and
13302 directory authority options, remove the documentation for a
13303 V2-directory fetching option that no longer exists. Resolves
13305 - Correct the documentation so that it lists the correct directory
13306 for the stats files. (They are in a subdirectory called "stats",
13308 - In the manpage, move more authority-only options into the
13309 directory authority section so that operators of regular directory
13310 caches don't get confused.
13311 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
13312 11061; bugfix on 0.2.4.7-alpha.
13313 - Resolve warnings from Doxygen.
13314 - Document in the manpage that "KBytes" may also be written as
13315 "kilobytes" or "KB", that "Kbits" may also be written as
13316 "kilobits", and so forth. Closes ticket 9222.
13317 - Document that the ClientOnly config option overrides ORPort.
13318 Our old explanation made ClientOnly sound as though it did
13319 nothing at all. Resolves bug 9059.
13320 - Explain that SocksPolicy, DirPolicy, and similar options don't
13321 take port arguments. Fixes the other part of ticket 11108.
13322 - Fix a comment about the rend_server_descriptor_t.protocols field
13323 to more accurately describe its range. Also, make that field
13324 unsigned, to more accurately reflect its usage. Fixes bug 9099;
13325 bugfix on 0.2.1.5-alpha.
13326 - Fix the manpage's description of HiddenServiceAuthorizeClient:
13327 the maximum client name length is 16, not 19. Fixes bug 11118;
13328 bugfix on 0.2.1.6-alpha.
13331 - The contrib directory has been sorted and tidied. Before, it was
13332 an unsorted dumping ground for useful and not-so-useful things.
13333 Now, it is divided based on functionality, and the items which
13334 seemed to be nonfunctional or useless have been removed. Resolves
13335 ticket 8966; based on patches from "rl1987".
13337 o Removed code and features:
13338 - Clients now reject any directory authority certificates lacking
13339 a dir-key-crosscert element. These have been included since
13340 0.2.1.9-alpha, so there's no real reason for them to be optional
13341 any longer. Completes proposal 157. Resolves ticket 10162.
13342 - Remove all code that existed to support the v2 directory system,
13343 since there are no longer any v2 directory authorities. Resolves
13345 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
13346 options, which were used for designating authorities as "Hidden
13347 service authorities". There has been no use of hidden service
13348 authorities since 0.2.2.1-alpha, when we stopped uploading or
13349 downloading v0 hidden service descriptors. Fixes bug 10881; also
13350 part of a fix for bug 10841.
13351 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
13352 and MTBF calculations, but that nobody was using. Fixes bug 11742.
13353 - The TunnelDirConns and PreferTunnelledDirConns options no longer
13354 exist; tunneled directory connections have been available since
13355 0.1.2.5-alpha, and turning them off is not a good idea. This is a
13356 brute-force fix for 10849, where "TunnelDirConns 0" would break
13358 - Remove all code for the long unused v1 directory protocol.
13359 Resolves ticket 11070.
13360 - Remove all remaining code related to version-0 hidden service
13361 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
13362 the rest of bug 10841.
13363 - Remove migration code from when we renamed the "cached-routers"
13364 file to "cached-descriptors" back in 0.2.0.8-alpha. This
13365 incidentally resolves ticket 6502 by cleaning up the related code
13366 a bit. Patch from Akshay Hebbar.
13368 o Test infrastructure:
13369 - Tor now builds each source file in two modes: a mode that avoids
13370 exposing identifiers needlessly, and another mode that exposes
13371 more identifiers for testing. This lets the compiler do better at
13372 optimizing the production code, while enabling us to take more
13373 radical measures to let the unit tests test things.
13374 - The production builds no longer include functions used only in
13375 the unit tests; all functions exposed from a module only for
13376 unit-testing are now static in production builds.
13377 - Add an --enable-coverage configuration option to make the unit
13378 tests (and a new src/or/tor-cov target) to build with gcov test
13380 - Update to the latest version of tinytest.
13381 - Improve the tinytest implementation of string operation tests so
13382 that comparisons with NULL strings no longer crash the tests; they
13383 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
13384 - New macros in test.h to simplify writing mock-functions for unit
13385 tests. Part of ticket 11507. Patch from Dana Koch.
13386 - We now have rudimentary function mocking support that our unit
13387 tests can use to test functions in isolation. Function mocking
13388 lets the tests temporarily replace a function's dependencies with
13389 stub functions, so that the tests can check the function without
13390 invoking the other functions it calls.
13393 - Complete tests for the status.c module. Resolves ticket 11507.
13394 Patch from Dana Koch.
13395 - Add more unit tests for the <circid,channel>->circuit map, and
13396 the destroy-cell-tracking code to fix bug 7912.
13397 - Unit tests for failing cases of the TAP onion handshake.
13398 - More unit tests for address-manipulation functions.
13400 o Distribution (systemd):
13401 - Include a tor.service file in contrib/dist for use with systemd.
13402 Some distributions will be able to use this file unmodified;
13403 others will need to tweak it, or write their own. Patch from Jamie
13404 Nguyen; resolves ticket 8368.
13405 - Verify configuration file via ExecStartPre in the systemd unit
13406 file. Patch from intrigeri; resolves ticket 12730.
13407 - Explicitly disable RunAsDaemon in the systemd unit file. Our
13408 current systemd unit uses "Type = simple", so systemd does not
13409 expect tor to fork. If the user has "RunAsDaemon 1" in their
13410 torrc, then things won't work as expected. This is e.g. the case
13411 on Debian (and derivatives), since there we pass "--defaults-torrc
13412 /usr/share/tor/tor-service-defaults-torrc" (that contains
13413 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
13417 Changes in version 0.2.4.25 - 2014-10-20
13418 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
13419 (even though POODLE does not affect Tor). It also works around a crash
13420 bug caused by some operating systems' response to the "POODLE" attack
13421 (which does affect Tor).
13423 o Major security fixes (also in 0.2.5.9-rc):
13424 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
13425 today support TLS 1.0 or later, so we can safely turn off support
13426 for this old (and insecure) protocol. Fixes bug 13426.
13428 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
13429 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
13430 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
13431 13471. This is a workaround for an OpenSSL bug.
13434 Changes in version 0.2.4.24 - 2014-09-22
13435 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
13436 connecting to hidden services, and it updates the location of one of
13437 the directory authorities.
13440 - Clients now send the correct address for their chosen rendezvous
13441 point when trying to access a hidden service. They used to send
13442 the wrong address, which would still work some of the time because
13443 they also sent the identity digest of the rendezvous point, and if
13444 the hidden service happened to try connecting to the rendezvous
13445 point from a relay that already had a connection open to it,
13446 the relay would reuse that connection. Now connections to hidden
13447 services should be more robust and faster. Also, this bug meant
13448 that clients were leaking to the hidden service whether they were
13449 on a little-endian (common) or big-endian (rare) system, which for
13450 some users might have reduced their anonymity. Fixes bug 13151;
13451 bugfix on 0.2.1.5-alpha.
13453 o Directory authority changes:
13454 - Change IP address for gabelmoo (v3 directory authority).
13456 o Minor features (geoip):
13457 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
13461 Changes in version 0.2.4.23 - 2014-07-28
13462 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
13463 guard rotation, and also backports several important fixes from the
13464 Tor 0.2.5 alpha release series.
13467 - Clients now look at the "usecreatefast" consensus parameter to
13468 decide whether to use CREATE_FAST or CREATE cells for the first hop
13469 of their circuit. This approach can improve security on connections
13470 where Tor's circuit handshake is stronger than the available TLS
13471 connection security levels, but the tradeoff is more computational
13472 load on guard relays. Implements proposal 221. Resolves ticket 9386.
13473 - Make the number of entry guards configurable via a new
13474 NumEntryGuards consensus parameter, and the number of directory
13475 guards configurable via a new NumDirectoryGuards consensus
13476 parameter. Implements ticket 12688.
13479 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
13480 implementation that caused incorrect results on 32-bit
13481 implementations when certain malformed inputs were used along with
13482 a small class of private ntor keys. This bug does not currently
13483 appear to allow an attacker to learn private keys or impersonate a
13484 Tor server, but it could provide a means to distinguish 32-bit Tor
13485 implementations from 64-bit Tor implementations. Fixes bug 12694;
13486 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
13490 - Warn and drop the circuit if we receive an inbound 'relay early'
13491 cell. Those used to be normal to receive on hidden service circuits
13492 due to bug 1038, but the buggy Tor versions are long gone from
13493 the network so we can afford to resume watching for them. Resolves
13494 the rest of bug 1038; bugfix on 0.2.1.19.
13495 - Correct a confusing error message when trying to extend a circuit
13496 via the control protocol but we don't know a descriptor or
13497 microdescriptor for one of the specified relays. Fixes bug 12718;
13498 bugfix on 0.2.3.1-alpha.
13499 - Avoid an illegal read from stack when initializing the TLS
13500 module using a version of OpenSSL without all of the ciphers
13501 used by the v2 link handshake. Fixes bug 12227; bugfix on
13502 0.2.4.8-alpha. Found by "starlight".
13505 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
13509 Changes in version 0.2.4.22 - 2014-05-16
13510 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
13511 alpha release series. These include blocking all authority signing
13512 keys that may have been affected by the OpenSSL "heartbleed" bug,
13513 choosing a far more secure set of TLS ciphersuites by default, closing
13514 a couple of memory leaks that could be used to run a target relay out
13515 of RAM, and several others.
13517 o Major features (security, backport from 0.2.5.4-alpha):
13518 - Block authority signing keys that were used on authorities
13519 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
13520 don't have any evidence that these keys _were_ compromised; we're
13521 doing this to be prudent.) Resolves ticket 11464.
13523 o Major bugfixes (security, OOM):
13524 - Fix a memory leak that could occur if a microdescriptor parse
13525 fails during the tokenizing step. This bug could enable a memory
13526 exhaustion attack by directory servers. Fixes bug 11649; bugfix
13529 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
13530 - The relay ciphersuite list is now generated automatically based on
13531 uniform criteria, and includes all OpenSSL ciphersuites with
13532 acceptable strength and forward secrecy. Previously, we had left
13533 some perfectly fine ciphersuites unsupported due to omission or
13534 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
13535 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
13536 - Relays now trust themselves to have a better view than clients of
13537 which TLS ciphersuites are better than others. (Thanks to bug
13538 11513, the relay list is now well-considered, whereas the client
13539 list has been chosen mainly for anti-fingerprinting purposes.)
13540 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
13541 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
13542 AES128. Resolves ticket 11528.
13543 - Clients now try to advertise the same list of ciphersuites as
13544 Firefox 28. This change enables selection of (fast) GCM
13545 ciphersuites, disables some strange old ciphers, and stops
13546 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
13547 Resolves ticket 11438.
13549 o Minor bugfixes (configuration, security):
13550 - When running a hidden service, do not allow TunneledDirConns 0:
13551 trying to set that option together with a hidden service would
13552 otherwise prevent the hidden service from running, and also make
13553 it publish its descriptors directly over HTTP. Fixes bug 10849;
13554 bugfix on 0.2.1.1-alpha.
13556 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
13557 - Avoid sending a garbage value to the controller when a circuit is
13558 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
13560 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
13561 - Stop leaking memory when we successfully resolve a PTR record.
13562 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
13564 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
13565 - Avoid 60-second delays in the bootstrapping process when Tor is
13566 launching for a second time while using bridges. Fixes bug 9229;
13567 bugfix on 0.2.0.3-alpha.
13569 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
13570 - Give the correct URL in the warning message when trying to run a
13571 relay on an ancient version of Windows. Fixes bug 9393.
13573 o Minor bugfixes (compilation):
13574 - Fix a compilation error when compiling with --disable-curve25519.
13575 Fixes bug 9700; bugfix on 0.2.4.17-rc.
13578 - Downgrade the warning severity for the the "md was still
13579 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
13580 for trying to diagnose this bug, and the current warning in
13581 earlier versions of tor achieves nothing useful. Addresses warning
13584 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
13585 - When we run out of usable circuit IDs on a channel, log only one
13586 warning for the whole channel, and describe how many circuits
13587 there were on the channel. Fixes part of ticket 11553.
13589 o Minor features (security, backport from 0.2.5.4-alpha):
13590 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
13591 leave the default at 8GBytes), to better support Raspberry Pi
13592 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
13594 o Documentation (backport from 0.2.5.4-alpha):
13595 - Correctly document that we search for a system torrc file before
13596 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
13600 Changes in version 0.2.4.21 - 2014-02-28
13601 Tor 0.2.4.21 further improves security against potential adversaries who
13602 find breaking 1024-bit crypto doable, and backports several stability
13603 and robustness patches from the 0.2.5 branch.
13605 o Major features (client security):
13606 - When we choose a path for a 3-hop circuit, make sure it contains
13607 at least one relay that supports the NTor circuit extension
13608 handshake. Otherwise, there is a chance that we're building
13609 a circuit that's worth attacking by an adversary who finds
13610 breaking 1024-bit crypto doable, and that chance changes the game
13611 theory. Implements ticket 9777.
13614 - Do not treat streams that fail with reason
13615 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
13616 since it could also indicate an ENETUNREACH connection error. Fixes
13617 part of bug 10777; bugfix on 0.2.4.8-alpha.
13619 o Code simplification and refactoring:
13620 - Remove data structures which were introduced to implement the
13621 CellStatistics option: they are now redundant with the new timestamp
13622 field in the regular packed_cell_t data structure, which we did
13623 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
13626 - Always clear OpenSSL bignums before freeing them -- even bignums
13627 that don't contain secrets. Resolves ticket 10793. Patch by
13629 - Build without warnings under clang 3.4. (We have some macros that
13630 define static functions only some of which will get used later in
13631 the module. Starting with clang 3.4, these give a warning unless the
13632 unused attribute is set on them.) Resolves ticket 10904.
13633 - Update geoip and geoip6 files to the February 7 2014 Maxmind
13634 GeoLite2 Country database.
13637 - Set the listen() backlog limit to the largest actually supported
13638 on the system, not to the value in a header file. Fixes bug 9716;
13639 bugfix on every released Tor.
13640 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
13641 exit node as a NOROUTE error, not an INTERNAL error, since they
13642 can apparently happen when trying to connect to the wrong sort
13643 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
13644 - Fix build warnings about missing "a2x" comment when building the
13645 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
13646 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
13647 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
13648 not entirely remove it from the connection lists. Fixes bug 9602;
13649 bugfix on 0.2.4.4-alpha.
13650 - Fix a segmentation fault in our benchmark code when running with
13651 Fedora's OpenSSL package, or any other OpenSSL that provides
13652 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
13653 - Turn "circuit handshake stats since last time" log messages into a
13654 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
13656 o Documentation fixes:
13657 - Document that all but one DirPort entry must have the NoAdvertise
13658 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
13661 Changes in version 0.2.4.20 - 2013-12-22
13662 Tor 0.2.4.20 fixes potentially poor random number generation for users
13663 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
13664 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
13665 and 4) have no state file in their DataDirectory (as would happen on
13666 first start). Users who generated relay or hidden service identity
13667 keys in such a situation should discard them and generate new ones.
13669 This release also fixes a logic error that caused Tor clients to build
13670 many more preemptive circuits than they actually need.
13673 - Do not allow OpenSSL engines to replace the PRNG, even when
13674 HardwareAccel is set. The only default builtin PRNG engine uses
13675 the Intel RDRAND instruction to replace the entire PRNG, and
13676 ignores all attempts to seed it with more entropy. That's
13677 cryptographically stupid: the right response to a new alleged
13678 entropy source is never to discard all previously used entropy
13679 sources. Fixes bug 10402; works around behavior introduced in
13680 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
13682 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
13683 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
13684 - Avoid launching spurious extra circuits when a stream is pending.
13685 This fixes a bug where any circuit that _wasn't_ unusable for new
13686 streams would be treated as if it were, causing extra circuits to
13687 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
13690 - Avoid a crash bug when starting with a corrupted microdescriptor
13691 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
13692 - If we fail to dump a previously cached microdescriptor to disk, avoid
13693 freeing duplicate data later on. Fixes bug 10423; bugfix on
13694 0.2.4.13-alpha. Spotted by "bobnomnom".
13697 Changes in version 0.2.4.19 - 2013-12-11
13698 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
13699 (1986-2013). Aaron worked on diverse projects including helping to guide
13700 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
13701 transparency to the U.S government's PACER documents, and contributing
13702 design and development for Tor and Tor2Web. Aaron was one of the latest
13703 martyrs in our collective fight for civil liberties and human rights,
13704 and his death is all the more painful because he was one of us.
13706 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
13707 a new circuit handshake and link encryption that use ECC to provide
13708 better security and efficiency; makes relays better manage circuit
13709 creation requests; uses "directory guards" to reduce client enumeration
13710 risks; makes bridges collect and report statistics about the pluggable
13711 transports they support; cleans up and improves our geoip database;
13712 gets much closer to IPv6 support for clients, bridges, and relays; makes
13713 directory authorities use measured bandwidths rather than advertised
13714 ones when computing flags and thresholds; disables client-side DNS
13715 caching to reduce tracking risks; and fixes a big bug in bridge
13716 reachability testing. This release introduces two new design
13717 abstractions in the code: a new "channel" abstraction between circuits
13718 and or_connections to allow for implementing alternate relay-to-relay
13719 transports, and a new "circuitmux" abstraction storing the queue of
13720 circuits for a channel. The release also includes many stability,
13721 security, and privacy fixes.
13723 o Major features (new circuit handshake):
13724 - Tor now supports a new circuit extension handshake designed by Ian
13725 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
13726 circuit extension handshake, later called "TAP", was a bit slow
13727 (especially on the relay side), had a fragile security proof, and
13728 used weaker keys than we'd now prefer. The new circuit handshake
13729 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
13730 function, making it significantly more secure than the older
13731 handshake, and significantly faster. Tor can use one of two built-in
13732 pure-C curve25519-donna implementations by Adam Langley, or it
13733 can link against the "nacl" library for a tuned version if present.
13735 The built-in version is very fast for 64-bit systems when building
13736 with GCC. The built-in 32-bit version is still faster than the
13737 old TAP protocol, but using libnacl is better on most such hosts.
13739 Implements proposal 216; closes ticket 7202.
13741 o Major features (better link encryption):
13742 - Relays can now enable the ECDHE TLS ciphersuites when available
13743 and appropriate. These ciphersuites let us negotiate forward-secure
13744 TLS secret keys more safely and more efficiently than with our
13745 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
13746 public relays prefer the (faster) P224 group, and bridges prefer
13747 the (more common) P256 group; you can override this with the
13750 This feature requires clients running 0.2.3.17-beta or later,
13751 and requires both sides to be running OpenSSL 1.0.0 or later
13752 with ECC support. OpenSSL 1.0.1, with the compile-time option
13753 "enable-ec_nistp_64_gcc_128", is highly recommended.
13755 Implements the relay side of proposal 198; closes ticket 7200.
13757 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
13758 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
13759 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
13760 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
13761 them to solve bug 6033.)
13763 o Major features (relay performance):
13764 - Instead of limiting the number of queued onionskins (aka circuit
13765 create requests) to a fixed, hard-to-configure number, we limit
13766 the size of the queue based on how many we expect to be able to
13767 process in a given amount of time. We estimate the time it will
13768 take to process an onionskin based on average processing time
13769 of previous onionskins. Closes ticket 7291. You'll never have to
13770 configure MaxOnionsPending again.
13771 - Relays process the new "NTor" circuit-level handshake requests
13772 with higher priority than the old "TAP" circuit-level handshake
13773 requests. We still process some TAP requests to not totally starve
13774 0.2.3 clients when NTor becomes popular. A new consensus parameter
13775 "NumNTorsPerTAP" lets us tune the balance later if we need to.
13776 Implements ticket 9574.
13778 o Major features (client bootstrapping resilience):
13779 - Add a new "FallbackDir" torrc option to use when we can't use
13780 a directory mirror from the consensus (either because we lack a
13781 consensus, or because they're all down). Currently, all authorities
13782 are fallbacks by default, and there are no other default fallbacks,
13783 but that will change. This option will allow us to give clients a
13784 longer list of servers to try to get a consensus from when first
13785 connecting to the Tor network, and thereby reduce load on the
13786 directory authorities. Implements proposal 206, "Preconfigured
13787 directory sources for bootstrapping". We also removed the old
13788 "FallbackNetworkstatus" option, since we never got it working well
13789 enough to use it. Closes bug 572.
13790 - If we have no circuits open, use a relaxed timeout (the
13791 95th-percentile cutoff) until a circuit succeeds. This heuristic
13792 should allow Tor to succeed at building circuits even when the
13793 network connection drastically changes. Should help with bug 3443.
13795 o Major features (use of guards):
13796 - Support directory guards (proposal 207): when possible, clients now
13797 use their entry guards for non-anonymous directory requests. This
13798 can help prevent client enumeration. Note that this behavior only
13799 works when we have a usable consensus directory, and when options
13800 about what to download are more or less standard. In the future we
13801 should re-bootstrap from our guards, rather than re-bootstrapping
13802 from the preconfigured list of directory sources that ships with
13803 Tor. Resolves ticket 6526.
13804 - Raise the default time that a client keeps an entry guard from
13805 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
13806 2012 paper. (We would make it even longer, but we need better client
13807 load balancing first.) Also, make the guard lifetime controllable
13808 via a new GuardLifetime torrc option and a GuardLifetime consensus
13809 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
13811 o Major features (bridges with pluggable transports):
13812 - Bridges now report the pluggable transports they support to the
13813 bridge authority, so it can pass the supported transports on to
13814 bridgedb and/or eventually do reachability testing. Implements
13816 - Automatically forward the TCP ports of pluggable transport
13817 proxies using tor-fw-helper if PortForwarding is enabled. Implements
13820 o Major features (geoip database):
13821 - Maxmind began labelling Tor relays as being in country "A1",
13822 which breaks by-country node selection inside Tor. Now we use a
13823 script to replace "A1" ("Anonymous Proxy") entries in our geoip
13824 file with real country codes. This script fixes about 90% of "A1"
13825 entries automatically and uses manual country code assignments to
13826 fix the remaining 10%. See src/config/README.geoip for details.
13828 - Add GeoIP database for IPv6 addresses. The new config option
13830 - Update to the October 2 2013 Maxmind GeoLite Country database.
13832 o Major features (IPv6):
13833 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
13834 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
13835 to happen. Implements ticket 5535.
13836 - All kind of relays, not just bridges, can now advertise an IPv6
13837 OR port. Implements ticket 6362.
13838 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
13839 connectivity, then set the IPv6Exit flag to 1. Also make sure your
13840 exit policy reads as you would like: the address * applies to all
13841 address families, whereas *4 is IPv4 address only, and *6 is IPv6
13842 addresses only. On the client side, you'll need to wait for enough
13843 exits to support IPv6, apply the "IPv6Traffic" flag to a SocksPort,
13844 and use Socks5. Closes ticket 5547, implements proposal 117 as
13845 revised in proposal 208.
13846 - Bridge authorities now accept IPv6 bridge addresses and include
13847 them in network status documents. Implements ticket 5534.
13848 - Directory authorities vote on IPv6 OR ports. Implements ticket 6363.
13850 o Major features (directory authorities):
13851 - Directory authorities now prefer using measured bandwidths to
13852 advertised ones when computing flags and thresholds. Resolves
13854 - Directory authorities that vote measured bandwidths about more
13855 than a threshold number of relays now treat relays with
13856 unmeasured bandwidths as having bandwidth 0 when computing their
13857 flags. Resolves ticket 8435.
13858 - Directory authorities now support a new consensus method (17)
13859 where they cap the published bandwidth of relays for which
13860 insufficient bandwidth measurements exist. Fixes part of bug 2286.
13861 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
13862 serve any v2 directory information. Now we can test disabling the
13863 old deprecated v2 directory format, and see whether doing so has
13864 any effect on network load. Begins to fix bug 6783.
13866 o Major features (build and portability):
13867 - Switch to a nonrecursive Makefile structure. Now instead of each
13868 Makefile.am invoking other Makefile.am's, there is a master
13869 Makefile.am that includes the others. This change makes our build
13870 process slightly more maintainable, and improves parallelism for
13871 building with make -j. Original patch by Stewart Smith; various
13872 fixes by Jim Meyering.
13873 - Where available, we now use automake's "silent" make rules by
13874 default, so that warnings are easier to spot. You can get the old
13875 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
13876 - Resume building correctly with MSVC and Makefile.nmake. This patch
13877 resolves numerous bugs and fixes reported by ultramage, including
13878 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
13880 o Security features:
13881 - Switch to a completely time-invariant approach for picking nodes
13882 weighted by bandwidth. Our old approach would run through the
13883 part of the loop after it had made its choice slightly slower
13884 than it ran through the part of the loop before it had made its
13885 choice. Addresses ticket 6538.
13886 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
13887 by tor2web clients allows hidden services to identify tor2web
13888 clients through their repeated selection of the same rendezvous
13889 and introduction point circuit endpoints (their guards). Resolves
13892 o Major bugfixes (relay denial of service):
13893 - When we have too much memory queued in circuits (according to a new
13894 MaxMemInCellQueues option), close the circuits that have the oldest
13895 queued cells, on the theory that those are most responsible for
13896 us running low on memory. This prevents us from running out of
13897 memory as a relay if circuits fill up faster than they can be
13898 drained. Fixes bugs 9063 and 9093; bugfix on the 54th commit of
13899 Tor. This bug is a further fix beyond bug 6252, whose fix was
13900 merged into 0.2.3.21-rc.
13901 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
13902 ID: these could be used to create unexpected streams and circuits
13903 which would count as "present" to some parts of Tor but "absent"
13904 to others, leading to zombie circuits and streams or to a bandwidth
13905 denial-of-service. Fixes bug 7889; bugfix on every released version
13906 of Tor. Reported by "oftc_must_be_destroyed".
13907 - Avoid a bug where our response to TLS renegotiation under certain
13908 network conditions could lead to a busy-loop, with 100% CPU
13909 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
13911 o Major bugfixes (asserts, crashes, leaks):
13912 - Prevent the get_freelists() function from running off the end of
13913 the list of freelists if it somehow gets an unrecognized
13914 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
13916 - Avoid a memory leak where we would leak a consensus body when we
13917 find that a consensus which we couldn't previously verify due to
13918 missing certificates is now verifiable. Fixes bug 8719; bugfix
13920 - If we are unable to save a microdescriptor to the journal, do not
13921 drop it from memory and then reattempt downloading it. Fixes bug
13922 9645; bugfix on 0.2.2.6-alpha.
13923 - Fix an assertion failure that would occur when disabling the
13924 ORPort setting on a running Tor process while accounting was
13925 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
13926 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
13927 when an exit connection with optimistic data succeeds immediately
13928 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
13930 - Fix a memory leak that would occur whenever a configuration
13931 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
13933 o Major bugfixes (relay rate limiting):
13934 - When a TLS write is partially successful but incomplete, remember
13935 that the flushed part has been flushed, and notice that bytes were
13936 actually written. Reported and fixed pseudonymously. Fixes bug 7708;
13937 bugfix on Tor 0.1.0.5-rc.
13938 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
13939 to 1GB/1GB. The previous defaults were intended to be "basically
13940 infinite", but it turns out they're now limiting our 100mbit+
13941 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
13942 last time we raised it).
13943 - No longer stop reading or writing on cpuworker connections when
13944 our rate limiting buckets go empty. Now we should handle circuit
13945 handshake requests more promptly. Resolves bug 9731.
13947 o Major bugfixes (client-side privacy):
13948 - When we mark a circuit as unusable for new circuits, have it
13949 continue to be unusable for new circuits even if MaxCircuitDirtiness
13950 is increased too much at the wrong time, or the system clock jumps
13951 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
13952 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
13953 which have resolved to internal addresses") is set, apply that
13954 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
13955 - When an exit relay rejects a stream with reason "exit policy", but
13956 we only know an exit policy summary (e.g. from the microdesc
13957 consensus) for it, do not mark the relay as useless for all exiting.
13958 Instead, mark just the circuit as unsuitable for that particular
13959 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
13961 o Major bugfixes (stream isolation):
13962 - Allow applications to get proper stream isolation with
13963 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
13964 username/password authentication also offer "no authentication". Tor
13965 had previously preferred "no authentication", so the applications
13966 never actually sent Tor their auth details. Now Tor selects
13967 username/password authentication if it's offered. You can disable
13968 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
13969 bug 8117; bugfix on 0.2.3.3-alpha.
13970 - Follow the socks5 protocol when offering username/password
13971 authentication. The fix for bug 8117 exposed this bug, and it
13972 turns out real-world applications like Pidgin do care. Bugfix on
13973 0.2.3.2-alpha; fixes bug 8879.
13975 o Major bugfixes (client circuit building):
13976 - Alter circuit build timeout measurement to start at the point
13977 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
13978 initialization). This should make our timeout measurements more
13979 uniform. Previously, we were sometimes including ORconn setup time
13980 in our circuit build time measurements. Should resolve bug 3443.
13981 - If the circuit build timeout logic is disabled (via the consensus,
13982 or because we are an authority), then don't build testing circuits.
13983 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
13985 o Major bugfixes (client-side DNS):
13986 - Turn off the client-side DNS cache by default. Updating and using
13987 the DNS cache is now configurable on a per-client-port
13988 level. SOCKSPort, DNSPort, etc lines may now contain
13989 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
13990 cache these types of DNS answers when we receive them from an
13991 exit node in response to an application request on this port, and
13992 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
13993 cached DNS answers of these types, we shouldn't use them. It's
13994 potentially risky to use cached DNS answers at the client, since
13995 doing so can indicate to one exit what answers we've gotten
13996 for DNS lookups in the past. With IPv6, this becomes especially
13997 problematic. Using cached DNS answers for requests on the same
13998 circuit would present less linkability risk, since all traffic
13999 on a circuit is already linkable, but it would also provide
14000 little performance benefit: the exit node caches DNS replies
14001 too. Implements a simplified version of Proposal 205. Implements
14004 o Major bugfixes (hidden service privacy):
14005 - Limit hidden service descriptors to at most ten introduction
14006 points, to slow one kind of guard enumeration. Fixes bug 9002;
14007 bugfix on 0.1.1.11-alpha.
14009 o Major bugfixes (directory fetching):
14010 - If the time to download the next old-style networkstatus is in
14011 the future, do not decline to consider whether to download the
14012 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
14014 - We used to always request authority certificates by identity digest,
14015 meaning we'd get the newest one even when we wanted one with a
14016 different signing key. Then we would complain about being given
14017 a certificate we already had, and never get the one we really
14018 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
14019 resource to request the one we want. Fixes bug 5595; bugfix on
14022 o Major bugfixes (bridge reachability):
14023 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
14024 previously they did not, which prevented them from receiving
14025 successful connections from relays for self-test or bandwidth
14026 testing. Also, when a relay is extending a circuit to a bridge,
14027 it needs to send a NETINFO cell, even when the bridge hasn't sent
14028 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
14030 o Major bugfixes (control interface):
14031 - When receiving a new configuration file via the control port's
14032 LOADCONF command, do not treat the defaults file as absent.
14033 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
14035 o Major bugfixes (directory authorities):
14036 - Stop marking every relay as having been down for one hour every
14037 time we restart a directory authority. These artificial downtimes
14038 were messing with our Stable and Guard flag calculations. Fixes
14039 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
14040 - When computing directory thresholds, ignore any rejected-as-sybil
14041 nodes during the computation so that they can't influence Fast,
14042 Guard, etc. (We should have done this for proposal 109.) Fixes
14044 - When marking a node as a likely sybil, reset its uptime metrics
14045 to zero, so that it cannot time towards getting marked as Guard,
14046 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
14048 - Fix a bug in the voting algorithm that could yield incorrect results
14049 when a non-naming authority declared too many flags. Fixes bug 9200;
14050 bugfix on 0.2.0.3-alpha.
14052 o Internal abstraction features:
14053 - Introduce new channel_t abstraction between circuits and
14054 or_connection_t to allow for implementing alternate OR-to-OR
14055 transports. A channel_t is an abstract object which can either be a
14056 cell-bearing channel, which is responsible for authenticating and
14057 handshaking with the remote OR and transmitting cells to and from
14058 it, or a listening channel, which spawns new cell-bearing channels
14059 at the request of remote ORs. Implements part of ticket 6465.
14060 - Make a channel_tls_t subclass of channel_t, adapting it to the
14061 existing or_connection_t code. The V2/V3 protocol handshaking
14062 code which formerly resided in command.c has been moved below the
14063 channel_t abstraction layer and may be found in channeltls.c now.
14064 Implements the rest of ticket 6465.
14065 - Introduce new circuitmux_t storing the queue of circuits for
14066 a channel; this encapsulates and abstracts the queue logic and
14067 circuit selection policy, and allows the latter to be overridden
14068 easily by switching out a policy object. The existing EWMA behavior
14069 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
14071 o New build requirements:
14072 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
14073 strongly recommended.
14074 - Tor maintainers now require Automake version 1.9 or later to build
14075 Tor from the Git repository. (Automake is not required when building
14076 from a source distribution.)
14078 o Minor features (protocol):
14079 - No longer include the "opt" prefix when generating routerinfos
14080 or v2 directories: it has been needless since Tor 0.1.2. Closes
14082 - Reject EXTEND cells sent to nonexistent streams. According to the
14083 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
14084 we were only checking for stream IDs that were currently in use.
14085 Found while hunting for more instances of bug 6271. Bugfix on
14086 0.0.2pre8, which introduced incremental circuit construction.
14087 - Tor relays and clients now support a better CREATE/EXTEND cell
14088 format, allowing the sender to specify multiple address, identity,
14089 and handshake types. Implements Robert Ransom's proposal 200;
14090 closes ticket 7199.
14091 - Reject as invalid most directory objects containing a NUL.
14092 Belt-and-suspender fix for bug 8037.
14094 o Minor features (security):
14095 - Clear keys and key-derived material left on the stack in
14096 rendservice.c and rendclient.c. Check return value of
14097 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
14098 These fixes should make us more forward-secure against cold-boot
14099 attacks and the like. Fixes bug 2385.
14100 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
14101 Irix's random() only return 15 bits; Solaris's random() returns more
14102 bits but its RAND_MAX says it only returns 15, and so on. Motivated
14103 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
14105 o Minor features (control protocol):
14106 - Add a "GETINFO signal/names" control port command. Implements
14108 - Provide default values for all options via "GETINFO config/defaults".
14109 Implements ticket 4971.
14110 - Allow an optional $ before the node identity digest in the
14111 controller command GETINFO ns/id/<identity>, for consistency with
14112 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
14113 - Add CACHED keyword to ADDRMAP events in the control protocol
14114 to indicate whether a DNS result will be cached or not. Resolves
14116 - Generate bootstrapping status update events correctly when fetching
14117 microdescriptors. Fixes bug 9927.
14119 o Minor features (path selection):
14120 - When deciding whether we have enough descriptors to build circuits,
14121 instead of looking at raw relay counts, look at which fraction
14122 of (bandwidth-weighted) paths we're able to build. This approach
14123 keeps clients from building circuits if their paths are likely to
14124 stand out statistically. The default fraction of paths needed is
14125 taken from the consensus directory; you can override it with the
14126 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
14127 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
14128 and we have GeoIP information, also exclude all nodes with unknown
14129 countries "??" and "A1". This behavior is controlled by the
14130 new GeoIPExcludeUnknown option: you can make such nodes always
14131 excluded with "GeoIPExcludeUnknown 1", and disable the feature
14132 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
14133 gets you the default behavior. Implements feature 7706.
14135 o Minor features (hidden services):
14136 - Improve circuit build timeout handling for hidden services.
14137 In particular: adjust build timeouts more accurately depending
14138 upon the number of hop-RTTs that a particular circuit type
14139 undergoes. Additionally, launch intro circuits in parallel
14140 if they timeout, and take the first one to reply as valid.
14141 - The Tor client now ignores sub-domain components of a .onion
14142 address. This change makes HTTP "virtual" hosting
14143 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
14144 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
14145 hosted on the same hidden service. Implements proposal 204.
14146 - Enable Tor to read configuration, state, and key information from
14147 a FIFO. Previously Tor would only read from files with a positive
14148 stat.st_size. Code from meejah; fixes bug 6044.
14150 o Minor features (clients):
14151 - Teach bridge-using clients to avoid 0.2.2.x bridges when making
14152 microdescriptor-related dir requests, and only fall back to normal
14153 descriptors if none of their bridges can handle microdescriptors
14154 (as opposed to the fix in ticket 4013, which caused them to fall
14155 back to normal descriptors if *any* of their bridges preferred
14156 them). Resolves ticket 4994.
14157 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
14158 TCP ports to forward. In the past it only accepted two ports:
14159 the ORPort and the DirPort.
14161 o Minor features (protecting client timestamps):
14162 - Clients no longer send timestamps in their NETINFO cells. These were
14163 not used for anything, and they provided one small way for clients
14164 to be distinguished from each other as they moved from network to
14165 network or behind NAT. Implements part of proposal 222.
14166 - Clients now round timestamps in INTRODUCE cells down to the nearest
14167 10 minutes. If a new Support022HiddenServices option is set to 0, or
14168 if it's set to "auto" and the feature is disabled in the consensus,
14169 the timestamp is sent as 0 instead. Implements part of proposal 222.
14170 - Stop sending timestamps in AUTHENTICATE cells. This is not such
14171 a big deal from a security point of view, but it achieves no actual
14172 good purpose, and isn't needed. Implements part of proposal 222.
14173 - Reduce down accuracy of timestamps in hidden service descriptors.
14174 Implements part of proposal 222.
14176 o Minor features (bridges):
14177 - Make bridge relays check once a minute for whether their IP
14178 address has changed, rather than only every 15 minutes. Resolves
14179 bugs 1913 and 1992.
14180 - Bridge statistics now count bridge clients connecting over IPv6:
14181 bridge statistics files now list "bridge-ip-versions" and
14182 extra-info documents list "geoip6-db-digest". The control protocol
14183 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
14184 implementation by "shkoo", addressing ticket 5055.
14185 - Add a new torrc option "ServerTransportListenAddr" to let bridge
14186 operators select the address where their pluggable transports will
14187 listen for connections. Resolves ticket 7013.
14188 - Randomize the lifetime of our SSL link certificate, so censors can't
14189 use the static value for filtering Tor flows. Resolves ticket 8443;
14190 related to ticket 4014 which was included in 0.2.2.33.
14192 o Minor features (relays):
14193 - Option OutboundBindAddress can be specified multiple times and
14194 accepts IPv6 addresses. Resolves ticket 6876.
14196 o Minor features (IPv6, client side):
14197 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
14198 prefer to hand out virtual IPv6 addresses, since there are more of
14199 them and we can't run out. To override this behavior and make IPv4
14200 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
14201 or DNSPort you're using for resolving. Implements ticket 7571.
14202 - AutomapHostsOnResolve responses are now randomized, to avoid
14203 annoying situations where Tor is restarted and applications
14204 connect to the wrong addresses.
14205 - Never try more than 1000 times to pick a new virtual address when
14206 AutomapHostsOnResolve is set. That's good enough so long as we
14207 aren't close to handing out our entire virtual address space;
14208 if you're getting there, it's best to switch to IPv6 virtual
14211 o Minor features (IPv6, relay/authority side):
14212 - New config option "AuthDirHasIPv6Connectivity 1" that directory
14213 authorities should set if they have IPv6 connectivity and want to
14214 do reachability tests for IPv6 relays. Implements feature 5974.
14215 - A relay with an IPv6 OR port now sends that address in NETINFO
14216 cells (in addition to its other address). Implements ticket 6364.
14218 o Minor features (directory authorities):
14219 - Directory authorities no long accept descriptors for any version of
14220 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
14221 These versions are insecure, unsupported, or both. Implements
14223 - When directory authorities are computing thresholds for flags,
14224 never let the threshold for the Fast flag fall below 4096
14225 bytes. Also, do not consider nodes with extremely low bandwidths
14226 when deciding thresholds for various directory flags. This change
14227 should raise our threshold for Fast relays, possibly in turn
14228 improving overall network performance; see ticket 1854. Resolves
14230 - Directory authorities now include inside each vote a statement of
14231 the performance thresholds they used when assigning flags.
14232 Implements ticket 8151.
14233 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
14234 in directory authority votes to describe whether they have enough
14235 measured bandwidths to ignore advertised (relay descriptor)
14236 bandwidth claims. Resolves ticket 8711.
14238 o Minor features (path bias detection):
14239 - Path Use Bias: Perform separate accounting for successful circuit
14240 use. Keep separate statistics on stream attempt rates versus stream
14241 success rates for each guard. Provide configurable thresholds to
14242 determine when to emit log messages or disable use of guards that
14243 fail too many stream attempts. Resolves ticket 7802.
14244 - Create three levels of Path Bias log messages, as opposed to just
14245 two. These are configurable via consensus as well as via the torrc
14246 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
14247 The default values are 0.70, 0.50, and 0.30 respectively.
14248 - Separate the log message levels from the decision to drop guards,
14249 which also is available via torrc option PathBiasDropGuards.
14250 PathBiasDropGuards still defaults to 0 (off).
14251 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
14252 in combination with PathBiasExtremeRate.
14253 - Increase the default values for PathBiasScaleThreshold and
14254 PathBiasCircThreshold from (200, 20) to (300, 150).
14255 - Add in circuit usage accounting to path bias. If we try to use a
14256 built circuit but fail for any reason, it counts as path bias.
14257 Certain classes of circuits where the adversary gets to pick your
14258 destination node are exempt from this accounting. Usage accounting
14259 can be specifically disabled via consensus parameter or torrc.
14260 - Convert all internal path bias state to double-precision floating
14261 point, to avoid roundoff error and other issues.
14262 - Only record path bias information for circuits that have completed
14263 *two* hops. Assuming end-to-end tagging is the attack vector, this
14264 makes us more resilient to ambient circuit failure without any
14265 detection capability loss.
14267 o Minor features (build):
14268 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
14269 dhill. Resolves ticket 6982.
14270 - Compile on win64 using mingw64. Fixes bug 7260; patches from
14272 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
14273 separate error codes; or at least, don't break for that reason.
14274 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
14276 o Build improvements (autotools):
14277 - Warn if building on a platform with an unsigned time_t: there
14278 are too many places where Tor currently assumes that time_t can
14279 hold negative values. We'd like to fix them all, but probably
14281 - Do not report status verbosely from autogen.sh unless the -v flag
14282 is specified. Fixes issue 4664. Patch from Onizuka.
14283 - Detect and reject attempts to build Tor with threading support
14284 when OpenSSL has been compiled without threading support.
14286 - Try to detect if we are ever building on a platform where
14287 memset(...,0,...) does not set the value of a double to 0.0. Such
14288 platforms are permitted by the C standard, though in practice
14289 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
14290 currently support them, but it's better to detect them and fail
14291 than to perform erroneously.
14292 - We no longer warn so much when generating manpages from their
14294 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
14295 the signs of types during autoconf. This is better than our old
14296 approach, which didn't work when cross-compiling.
14298 o Minor features (log messages, warnings):
14299 - Detect when we're running with a version of OpenSSL other than the
14300 one we compiled with. This conflict has occasionally given people
14301 hard-to-track-down errors.
14302 - Warn users who run hidden services on a Tor client with
14303 UseEntryGuards disabled that their hidden services will be
14304 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
14305 attack which motivated Tor to support entry guards in the first
14306 place). Resolves ticket 6889.
14307 - Warn when we are binding low ports when hibernation is enabled;
14308 previously we had warned when we were _advertising_ low ports with
14309 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
14310 - Issue a warning when running with the bufferevents backend enabled.
14311 It's still not stable, and people should know that they're likely
14312 to hit unexpected problems. Closes ticket 9147.
14314 o Minor features (log messages, notices):
14315 - Refactor resolve_my_address() so it returns the method by which we
14316 decided our public IP address (explicitly configured, resolved from
14317 explicit hostname, guessed from interfaces, learned by gethostname).
14318 Now we can provide more helpful log messages when a relay guesses
14319 its IP address incorrectly (e.g. due to unexpected lines in
14320 /etc/hosts). Resolves ticket 2267.
14321 - Track how many "TAP" and "NTor" circuit handshake requests we get,
14322 and how many we complete, and log it every hour to help relay
14323 operators follow trends in network load. Addresses ticket 9658.
14325 o Minor features (log messages, diagnostics):
14326 - If we fail to free a microdescriptor because of bug 7164, log
14327 the filename and line number from which we tried to free it.
14328 - We compute the overhead from passing onionskins back and forth to
14329 cpuworkers, and report it when dumping statistics in response to
14330 SIGUSR1. Supports ticket 7291.
14331 - Add another diagnostic to the heartbeat message: track and log
14332 overhead that TLS is adding to the data we write. If this is
14333 high, we are sending too little data to SSL_write at a time.
14334 Diagnostic for bug 7707.
14335 - Log packaged cell fullness as part of the heartbeat message.
14336 Diagnosis to try to determine the extent of bug 7743.
14337 - Add more detail to a log message about relaxed timeouts, to help
14339 - When learning a fingerprint for a bridge, log its corresponding
14340 transport type. Implements ticket 7896.
14341 - Warn more aggressively when flushing microdescriptors to a
14342 microdescriptor cache fails, in an attempt to mitigate bug 8031,
14343 or at least make it more diagnosable.
14344 - Improve the log message when "Bug/attack: unexpected sendme cell
14345 from client" occurs, to help us track bug 8093.
14346 - Improve debugging output to help track down bug 8185 ("Bug:
14347 outgoing relay cell has n_chan==NULL. Dropping.")
14349 o Minor features (log messages, quieter bootstrapping):
14350 - Log fewer lines at level "notice" about our OpenSSL and Libevent
14351 versions and capabilities when everything is going right. Resolves
14352 part of ticket 6736.
14353 - Omit the first heartbeat log message, because it never has anything
14354 useful to say, and it clutters up the bootstrapping messages.
14355 Resolves ticket 6758.
14356 - Don't log about reloading the microdescriptor cache at startup. Our
14357 bootstrap warnings are supposed to tell the user when there's a
14358 problem, and our bootstrap notices say when there isn't. Resolves
14359 ticket 6759; bugfix on 0.2.2.6-alpha.
14360 - Don't log "I learned some more directory information" when we're
14361 reading cached directory information. Reserve it for when new
14362 directory information arrives in response to a fetch. Resolves
14364 - Don't complain about bootstrapping problems while hibernating.
14365 These complaints reflect a general code problem, but not one
14366 with any problematic effects (no connections are actually
14367 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
14369 o Minor features (testing):
14370 - In our testsuite, create temporary directories with a bit more
14371 entropy in their name to make name collisions less likely. Fixes
14373 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
14374 (P-256) Diffie-Hellman handshakes to src/or/bench.
14375 - Add benchmark functions to test onion handshake performance.
14378 - The DirServer option is now DirAuthority, for consistency with
14379 current naming patterns. You can still use the old DirServer form.
14381 o Minor bugfixes (protocol):
14382 - Fix the handling of a TRUNCATE cell when it arrives while the
14383 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
14384 - When a Tor client gets a "truncated" relay cell, the first byte of
14385 its payload specifies why the circuit was truncated. We were
14386 ignoring this 'reason' byte when tearing down the circuit, resulting
14387 in the controller not being told why the circuit closed. Now we
14388 pass the reason from the truncated cell to the controller. Bugfix
14389 on 0.1.2.3-alpha; fixes bug 7039.
14390 - Fix a misframing issue when reading the version numbers in a
14391 VERSIONS cell. Previously we would recognize [00 01 00 02] as
14392 'version 1, version 2, and version 0x100', when it should have
14393 only included versions 1 and 2. Fixes bug 8059; bugfix on
14394 0.2.0.10-alpha. Reported pseudonymously.
14395 - Make the format and order of STREAM events for DNS lookups
14396 consistent among the various ways to launch DNS lookups. Fixes
14397 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
14399 o Minor bugfixes (syscalls and disk interaction):
14400 - Always check the return values of functions fcntl() and
14401 setsockopt(). We don't believe these are ever actually failing in
14402 practice, but better safe than sorry. Also, checking these return
14403 values should please analysis tools like Coverity. Patch from
14404 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
14405 - Avoid double-closing the listener socket in our socketpair()
14406 replacement (used on Windows) in the case where the addresses on
14407 our opened sockets don't match what we expected. Fixes bug 9400;
14408 bugfix on 0.0.2pre7. Found by Coverity.
14409 - Correctly store microdescriptors and extrainfo descriptors that
14410 include an internal NUL byte. Fixes bug 8037; bugfix on
14411 0.2.0.1-alpha. Bug reported by "cypherpunks".
14412 - If for some reason we fail to write a microdescriptor while
14413 rebuilding the cache, do not let the annotations from that
14414 microdescriptor linger in the cache file, and do not let the
14415 microdescriptor stay recorded as present in its old location.
14416 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
14417 - Use direct writes rather than stdio when building microdescriptor
14418 caches, in an attempt to mitigate bug 8031, or at least make it
14421 o Minor fixes (config options):
14422 - Warn and fail if a server is configured not to advertise any
14423 ORPorts at all. (We need *something* to put in our descriptor,
14424 or we just won't work.)
14425 - Behave correctly when the user disables LearnCircuitBuildTimeout
14426 but doesn't tell us what they would like the timeout to be. Fixes
14427 bug 6304; bugfix on 0.2.2.14-alpha.
14428 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
14429 to start with a triple-underscore so the controller won't touch it.
14430 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
14431 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
14432 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
14433 - When autodetecting the number of CPUs, use the number of available
14434 CPUs in preference to the number of configured CPUs. Inform the
14435 user if this reduces the number of available CPUs. Fixes bug 8002;
14436 bugfix on 0.2.3.1-alpha.
14437 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
14438 - Make it an error when you set EntryNodes but disable UseGuardNodes,
14439 since it will (surprisingly to some users) ignore EntryNodes. Fixes
14440 bug 8180; bugfix on 0.2.3.11-alpha.
14441 - Avoid overflows when the user sets MaxCircuitDirtiness to a
14442 ridiculously high value, by imposing a (ridiculously high) 30-day
14443 maximum on MaxCircuitDirtiness.
14445 o Minor bugfixes (control protocol):
14446 - Stop sending a stray "(null)" in some cases for the server status
14447 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
14449 - The ADDRMAP command can no longer generate an ill-formed error
14450 code on a failed MAPADDRESS. It now says "internal" rather than
14451 an English sentence fragment with spaces in the middle. Bugfix on
14452 Tor 0.2.0.19-alpha.
14454 o Minor bugfixes (clients / edges):
14455 - When we receive a RELAY_END cell with the reason DONE, or with no
14456 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
14457 status as "connection refused". Previously we reported these cases
14458 as success but then immediately closed the connection. Fixes bug
14459 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
14460 - If the guard we choose first doesn't answer, we would try the
14461 second guard, but once we connected to the second guard we would
14462 abandon it and retry the first one, slowing down bootstrapping.
14463 The fix is to treat all our initially chosen guards as acceptable
14464 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
14465 - When choosing which stream on a formerly stalled circuit to wake
14466 first, make better use of the platform's weak RNG. Previously,
14467 we had been using the % ("modulo") operator to try to generate a
14468 1/N chance of picking each stream, but this behaves badly with
14469 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
14472 o Minor bugfixes (path bias detection):
14473 - If the state file's path bias counts are invalid (presumably from a
14474 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
14475 additional checks and log messages to the scaling of Path Bias
14476 counts, in case there still are remaining issues with scaling.
14477 Should help resolve bug 8235.
14478 - Prevent rounding error in path bias counts when scaling
14479 them down, and use the correct scale factor default. Also demote
14480 some path bias related log messages down a level and make others
14481 less scary sounding. Fixes bug 6647. Bugfix on 0.2.3.17-beta.
14482 - Remove a source of rounding error during path bias count scaling;
14483 don't count cannibalized circuits as used for path bias until we
14484 actually try to use them; and fix a circuit_package_relay_cell()
14485 warning message about n_chan==NULL. Fixes bug 7802.
14486 - Paste the description for PathBias parameters from the man
14487 page into or.h, so the code documents them too. Fixes bug 7982;
14488 bugfix on 0.2.3.17-beta.
14490 o Minor bugfixes (relays):
14491 - Stop trying to resolve our hostname so often (e.g. every time we
14492 think about doing a directory fetch). Now we reuse the cached
14493 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
14494 and 2410 (bugfix on 0.1.2.2-alpha).
14495 - When examining the list of network interfaces to find our address,
14496 do not consider non-running or disabled network interfaces. Fixes
14497 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
14499 o Minor bugfixes (blocking resistance):
14500 - Only disable TLS session ticket support when running as a TLS
14501 server. Now clients will blend better with regular Firefox
14502 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
14504 o Minor bugfixes (IPv6):
14505 - Use square brackets around IPv6 addresses in numerous places
14506 that needed them, including log messages, HTTPS CONNECT proxy
14507 requests, TransportProxy statefile entries, and pluggable transport
14508 extra-info lines. Fixes bug 7011; patch by David Fifield.
14510 o Minor bugfixes (directory authorities):
14511 - Reject consensus votes with more than 64 known-flags. We aren't even
14512 close to that limit yet, and our code doesn't handle it correctly.
14513 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
14514 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
14515 bugfix on 0.2.0.3-alpha.
14517 o Minor bugfixes (memory leaks):
14518 - Avoid leaking memory if we fail to compute a consensus signature
14519 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
14520 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
14521 on 0.2.1.1-alpha; fixes bug 7816.
14522 - Fix a memory leak during safe-cookie controller authentication.
14523 Bugfix on 0.2.3.13-alpha; fixes bug 7816.
14524 - Free some more still-in-use memory at exit, to make hunting for
14525 memory leaks easier. Resolves bug 7029.
14527 o Minor bugfixes (code correctness):
14528 - Increase the width of the field used to remember a connection's
14529 link protocol version to two bytes. Harmless for now, since the
14530 only currently recognized versions are one byte long. Reported
14531 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
14532 - Fix a crash when debugging unit tests on Windows: deallocate a
14533 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
14534 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
14535 - When detecting the largest possible file descriptor (in order to
14536 close all file descriptors when launching a new program), actually
14537 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
14538 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
14540 - Avoid a crash if we fail to generate an extrainfo descriptor.
14541 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
14542 this is CID 718634.
14543 - Avoid an off-by-one error when checking buffer boundaries when
14544 formatting the exit status of a pluggable transport helper.
14545 This is probably not an exploitable bug, but better safe than
14546 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
14548 - Get rid of a couple of harmless clang warnings, where we compared
14549 enums to ints. These warnings are newly introduced in clang 3.2.
14551 o Minor bugfixes (code cleanliness):
14552 - Avoid use of reserved identifiers in our C code. The C standard
14553 doesn't like us declaring anything that starts with an
14554 underscore, so let's knock it off before we get in trouble. Fix
14555 for bug 1031; bugfix on the first Tor commit.
14556 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
14557 with large values. This situation was untriggered, but nevertheless
14558 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
14559 - Fix an impossible buffer overrun in the AES unit tests. Fixes
14560 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
14561 - Fix handling of rendezvous client authorization types over 8.
14562 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
14563 - Remove a couple of extraneous semicolons that were upsetting the
14564 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
14565 bugfix on 0.2.2.1-alpha.
14566 - When complaining about a client port on a public address, log
14567 which address we're complaining about. Fixes bug 4020; bugfix on
14568 0.2.3.3-alpha. Patch by Tom Fitzhenry.
14570 o Minor bugfixes (log messages, warnings):
14571 - If we encounter a write failure on a SOCKS connection before we
14572 finish our SOCKS handshake, don't warn that we closed the
14573 connection before we could send a SOCKS reply. Fixes bug 8427;
14574 bugfix on 0.1.0.1-rc.
14575 - Fix a directory authority warn caused when we have a large amount
14576 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
14577 - Downgrade "Failed to hand off onionskin" messages to "debug"
14578 severity, since they're typically redundant with the "Your computer
14579 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
14580 - Avoid spurious warnings when configuring multiple client ports of
14581 which only some are nonlocal. Previously, we had claimed that some
14582 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
14585 o Minor bugfixes (log messages, other):
14586 - Fix log messages and comments to avoid saying "GMT" when we mean
14587 "UTC". Fixes bug 6113.
14588 - When rejecting a configuration because we were unable to parse a
14589 quoted string, log an actual error message. Fixes bug 7950; bugfix
14591 - Correctly recognize that [::1] is a loopback address. Fixes
14592 bug 8377; bugfix on 0.2.1.3-alpha.
14593 - Don't log inappropriate heartbeat messages when hibernating: a
14594 hibernating node is _expected_ to drop out of the consensus,
14595 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
14596 bugfix on 0.2.3.1-alpha.
14597 - Eliminate several instances where we use "Nickname=ID" to refer to
14598 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
14599 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
14602 o Minor bugfixes (build):
14603 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
14604 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
14605 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
14607 o Documentation fixes:
14608 - Make the torify manpage no longer refer to tsocks; torify hasn't
14609 supported tsocks since 0.2.3.14-alpha.
14610 - Make the tor manpage no longer reference tsocks.
14611 - Fix the GeoIPExcludeUnknown documentation to refer to
14612 ExcludeExitNodes rather than the currently nonexistent
14613 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
14614 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
14616 - Say "KBytes" rather than "KB" in the man page (for various values
14617 of K), to further reduce confusion about whether Tor counts in
14618 units of memory or fractions of units of memory. Resolves ticket 7054.
14619 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
14620 names match. Fixes bug 7768.
14621 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
14622 message is logged at notice, not at info.
14623 - Clarify the usage and risks of setting the ContactInfo torrc line
14624 for your relay or bridge. Resolves ticket 9854.
14625 - Add anchors to the manpage so we can link to the html version of
14626 the documentation for specific options. Resolves ticket 9866.
14627 - Replace remaining references to DirServer in man page and
14628 log entries. Resolves ticket 10124.
14630 o Removed features:
14631 - Stop exporting estimates of v2 and v3 directory traffic shares
14632 in extrainfo documents. They were unneeded and sometimes inaccurate.
14633 Also stop exporting any v2 directory request statistics. Resolves
14635 - Drop support for detecting and warning about versions of Libevent
14636 before 1.3e. Nothing reasonable ships with them any longer; warning
14637 the user about them shouldn't be needed. Resolves ticket 6826.
14638 - Now that all versions before 0.2.2.x are disallowed, we no longer
14639 need to work around their missing features. Remove a bunch of
14640 compatibility code.
14643 - The tor-tsocks.conf is no longer distributed or installed. We
14644 recommend that tsocks users use torsocks instead. Resolves
14646 - Remove some of the older contents of doc/ as obsolete; move others
14647 to torspec.git. Fixes bug 8965.
14649 o Code simplification:
14650 - Avoid using character buffers when constructing most directory
14651 objects: this approach was unwieldy and error-prone. Instead,
14652 build smartlists of strings, and concatenate them when done.
14653 - Rename "isin" functions to "contains", for grammar. Resolves
14655 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
14656 with the natural logarithm function from the system libm. Resolves
14658 - Start using OpenBSD's implementation of queue.h, so that we don't
14659 need to hand-roll our own pointer and list structures whenever we
14660 need them. (We can't rely on a sys/queue.h, since some operating
14661 systems don't have them, and the ones that do have them don't all
14662 present the same extensions.)
14663 - Start using OpenBSD's implementation of queue.h (originally by
14665 - Enhance our internal sscanf replacement so that we can eliminate
14666 the last remaining uses of the system sscanf. (Though those uses
14667 of sscanf were safe, sscanf itself is generally error prone, so
14668 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
14670 - Replace all calls to snprintf() outside of src/ext with
14671 tor_snprintf(). Also remove the #define to replace snprintf with
14672 _snprintf on Windows; they have different semantics, and all of
14673 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
14676 - Add a wrapper function for the common "log a message with a
14678 - Split the onion.c file into separate modules for the onion queue
14679 and the different handshakes it supports.
14680 - Move the client-side address-map/virtual-address/DNS-cache code
14681 out of connection_edge.c into a new addressmap.c module.
14682 - Move the entry node code from circuitbuild.c to its own file.
14683 - Move the circuit build timeout tracking code from circuitbuild.c
14685 - Source files taken from other packages now reside in src/ext;
14686 previously they were scattered around the rest of Tor.
14687 - Move the generic "config" code into a new file, and have "config.c"
14688 hold only torrc- and state-related code. Resolves ticket 6823.
14689 - Move the core of our "choose a weighted element at random" logic
14690 into its own function, and give it unit tests. Now the logic is
14691 testable, and a little less fragile too.
14692 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
14693 - Move last_reachable and testing_since from routerinfo_t to node_t.
14694 Implements ticket 5529.
14695 - Add replaycache_t structure, functions and unit tests, then refactor
14696 rend_service_introduce() to be more clear to read, improve, debug,
14697 and test. Resolves bug 6177.
14700 - Remove some now-needless code that tried to aggressively flush
14701 OR connections as data was added to them. Since 0.2.0.1-alpha, our
14702 cell queue logic has saved us from the failure mode that this code
14703 was supposed to prevent. Removing this code will limit the number
14704 of baroque control flow paths through Tor's network logic. Reported
14705 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
14706 - Remove unused code for parsing v1 directories and "running routers"
14707 documents. Fixes bug 6887.
14708 - Remove the marshalling/unmarshalling code for sending requests to
14709 cpuworkers over a socket, and instead just send structs. The
14710 recipient will always be the same Tor binary as the sender, so
14711 any encoding is overkill.
14712 - Remove the testing_since field of node_t, which hasn't been used
14713 for anything since 0.2.0.9-alpha.
14714 - Finally remove support for malloc_good_size and malloc_usable_size.
14715 We had hoped that these functions would let us eke a little more
14716 memory out of our malloc implementation. Unfortunately, the only
14717 implementations that provided these functions are also ones that
14718 are already efficient about not overallocation: they never got us
14719 more than 7 or so bytes per allocation. Removing them saves us a
14720 little code complexity and a nontrivial amount of build complexity.
14723 Changes in version 0.2.3.25 - 2012-11-19
14724 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
14725 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
14726 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
14727 programmer, and friend. Unstinting in his dedication to the cause of
14728 freedom, he inspired and helped many of us as we began our work on
14729 anonymity, and inspires us still. Please honor his memory by writing
14730 software to protect people's freedoms, and by helping others to do so.
14732 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
14733 significantly reduced directory overhead (via microdescriptors),
14734 enormous crypto performance improvements for fast relays on new
14735 enough hardware, a new v3 TLS handshake protocol that can better
14736 resist fingerprinting, support for protocol obfuscation plugins (aka
14737 pluggable transports), better scalability for hidden services, IPv6
14738 support for bridges, performance improvements like allowing clients
14739 to skip the first round-trip on the circuit ("optimistic data") and
14740 refilling token buckets more often, a new "stream isolation" design
14741 to isolate different applications on different circuits, and many
14742 stability, security, and privacy fixes.
14744 Major features (v3 directory protocol):
14745 - Clients now use microdescriptors instead of regular descriptors
14746 to build circuits. Microdescriptors are authority-generated
14747 summaries of regular descriptors' contents, designed to change very
14748 rarely (see proposal 158 for details). This feature is designed
14749 to save bandwidth, especially for clients on slow internet
14750 connections. Use "UseMicrodescriptors 0" to disable it.
14751 - Caches now download, cache, and serve microdescriptors, as well
14752 as multiple "flavors" of the consensus, including a flavor that
14753 describes microdescriptors.
14755 o Major features (build hardening):
14756 - Enable gcc and ld hardening by default. Resolves ticket 5210.
14758 o Major features (relay scaling):
14759 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
14760 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
14761 vectorized AES implementations as appropriate. These can be much,
14762 much faster than other AES implementations.
14763 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
14764 implementation. It makes AES_CTR about 7% faster than our old one
14765 (which was about 10% faster than the one OpenSSL used to provide).
14766 Resolves ticket 4526.
14767 - Use OpenSSL's EVP interface for AES encryption, so that all AES
14768 operations can use hardware acceleration (if present). Resolves
14770 - Unconditionally use OpenSSL's AES implementation instead of our
14771 old built-in one. OpenSSL's AES has been better for a while, and
14772 relatively few servers should still be on any version of OpenSSL
14773 that doesn't have good optimized assembly AES.
14775 o Major features (blocking resistance):
14776 - Update TLS cipher list to match Firefox 8 and later. Resolves
14778 - Remove support for clients falsely claiming to support standard
14779 ciphersuites that they can actually provide. As of modern OpenSSL
14780 versions, it's not necessary to fake any standard ciphersuite,
14781 and doing so prevents us from using better ciphersuites in the
14782 future, since servers can't know whether an advertised ciphersuite
14783 is really supported or not. Some hosts -- notably, ones with very
14784 old versions of OpenSSL or where OpenSSL has been built with ECC
14785 disabled -- will stand out because of this change; TBB users should
14786 not be affected. Implements the client side of proposal 198.
14787 - Implement a new handshake protocol (v3) for authenticating Tors to
14788 each other over TLS. It should be more resistant to fingerprinting
14789 than previous protocols, and should require less TLS hacking for
14790 future Tor implementations. Implements proposal 176.
14791 - Allow variable-length padding cells, to disguise the length of
14792 Tor's TLS records. Implements part of proposal 184.
14793 - While we're trying to bootstrap, record how many TLS connections
14794 fail in each state, and report which states saw the most failures
14795 in response to any bootstrap failures. This feature may speed up
14796 diagnosis of censorship events. Implements ticket 3116.
14798 o Major features (pluggable transports):
14799 - Clients and bridges can now be configured to use a separate
14800 "transport" proxy. This approach makes the censorship arms race
14801 easier by allowing bridges to use protocol obfuscation plugins.
14802 Implements proposal 180 (tickets 2841 and 3472).
14804 o Major features (DoS resistance):
14805 - Now that Tor 0.2.0.x is completely deprecated, enable the final
14806 part of "Proposal 110: Avoiding infinite length circuits" by
14807 refusing all circuit-extend requests that do not use a relay_early
14808 cell. This change helps Tor resist a class of denial-of-service
14809 attacks by limiting the maximum circuit length.
14810 - Tear down the circuit if we get an unexpected SENDME cell. Clients
14811 could use this trick to make their circuits receive cells faster
14812 than our flow control would have allowed, or to gum up the network,
14813 or possibly to do targeted memory denial-of-service attacks on
14814 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
14815 from July 2002, before the release of Tor 0.0.0.
14817 o Major features (hidden services):
14818 - Adjust the number of introduction points that a hidden service
14819 will try to maintain based on how long its introduction points
14820 remain in use and how many introductions they handle. Fixes
14822 - Add a "tor2web mode" for clients that want to connect to hidden
14823 services non-anonymously (and possibly more quickly). As a safety
14824 measure to try to keep users from turning this on without knowing
14825 what they are doing, tor2web mode must be explicitly enabled at
14826 compile time, and a copy of Tor compiled to run in tor2web mode
14827 cannot be used as a normal Tor client. Implements feature 2553.
14829 o Major features (IPv6):
14830 - Clients can now connect to private bridges over IPv6. Bridges
14831 still need at least one IPv4 address in order to connect to
14832 other relays. Note that we don't yet handle the case where the
14833 user has two bridge lines for the same bridge (one IPv4, one
14834 IPv6). Implements parts of proposal 186.
14836 o Major features (directory authorities):
14837 - Use a more secure consensus parameter voting algorithm. Now at
14838 least three directory authorities or a majority of them must
14839 vote on a given parameter before it will be included in the
14840 consensus. Implements proposal 178.
14841 - Remove the artificially low cutoff of 20KB to guarantee the Fast
14842 flag. In the past few years the average relay speed has picked
14843 up, and while the "top 7/8 of the network get the Fast flag" and
14844 "all relays with 20KB or more of capacity get the Fast flag" rules
14845 used to have the same result, now the top 7/8 of the network has
14846 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
14848 o Major features (performance):
14849 - Exit nodes now accept and queue data on not-yet-connected streams.
14850 Previously, the client wasn't allowed to send data until the
14851 stream was connected, which slowed down all connections. This
14852 change will enable clients to perform a "fast-start" on streams
14853 and send data without having to wait for a confirmation that the
14854 stream has opened. Patch from Ian Goldberg; implements the server
14855 side of Proposal 174.
14856 - When using an exit relay running 0.2.3.x, clients can now
14857 "optimistically" send data before the exit relay reports that
14858 the stream has opened. This saves a round trip when starting
14859 connections where the client speaks first (such as web browsing).
14860 This behavior is controlled by a consensus parameter (currently
14861 disabled). To turn it on or off manually, use the "OptimisticData"
14862 torrc option. Implements proposal 181; code by Ian Goldberg.
14863 - Add a new TokenBucketRefillInterval option to refill token buckets
14864 more frequently than once per second. This should improve network
14865 performance, alleviate queueing problems, and make traffic less
14866 bursty. Implements proposal 183; closes ticket 3630. Design by
14867 Florian Tschorsch and Björn Scheuermann; implementation by
14869 - Raise the threshold of server descriptors needed (75%) and exit
14870 server descriptors needed (50%) before we will declare ourselves
14871 bootstrapped. This will make clients start building circuits a
14872 little later, but makes the initially constructed circuits less
14873 skewed and less in conflict with further directory fetches. Fixes
14876 o Major features (relays):
14877 - Relays now try regenerating and uploading their descriptor more
14878 frequently if they are not listed in the consensus, or if the
14879 version of their descriptor listed in the consensus is too
14880 old. This fix should prevent situations where a server declines
14881 to re-publish itself because it has done so too recently, even
14882 though the authorities decided not to list its recent-enough
14883 descriptor. Fix for bug 3327.
14885 o Major features (stream isolation):
14886 - You can now configure Tor so that streams from different
14887 applications are isolated on different circuits, to prevent an
14888 attacker who sees your streams as they leave an exit node from
14889 linking your sessions to one another. To do this, choose some way
14890 to distinguish the applications: have them connect to different
14891 SocksPorts, or have one of them use SOCKS4 while the other uses
14892 SOCKS5, or have them pass different authentication strings to the
14893 SOCKS proxy. Then, use the new SocksPort syntax to configure the
14894 degree of isolation you need. This implements Proposal 171.
14895 - There's a new syntax for specifying multiple client ports (such as
14896 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
14897 multiple *Port entries with full addr:port syntax on each.
14898 The old *ListenAddress format is still supported, but you can't
14899 mix it with the new *Port syntax.
14901 o Major features (bufferevents):
14902 - Tor can now optionally build with the "bufferevents" buffered IO
14903 backend provided by Libevent 2. To use this feature, make sure you
14904 have the latest possible version of Libevent, and pass the
14905 --enable-bufferevents flag to configure when building Tor from
14906 source. This feature will make our networking code more flexible,
14907 let us stack layers on each other, and let us use more efficient
14908 zero-copy transports where available.
14909 - Add experimental support for running on Windows with IOCP and no
14910 kernel-space socket buffers. This feature is controlled by a new
14911 "UserspaceIOCPBuffers" config option (off by default), which has
14912 no effect unless Tor has been built with bufferevents enabled,
14913 you're running on Windows, and you've set "DisableIOCP 0". In the
14914 long run, this may help solve or mitigate bug 98.
14916 o Major features (path selection):
14917 - The EntryNodes option can now include country codes like {de} or IP
14918 addresses or network masks. Previously we had disallowed these
14919 options because we didn't have an efficient way to keep the list up
14920 to date. Addresses ticket 1982, but see bug 2798 for an unresolved
14923 o Major features (port forwarding):
14924 - Add support for automatic port mapping on the many home routers
14925 that support NAT-PMP or UPnP. To build the support code, you'll
14926 need to have the libnatpnp library and/or the libminiupnpc library,
14927 and you'll need to enable the feature specifically by passing
14928 "--enable-upnp" and/or "--enable-natpnp" to ./configure. To turn
14929 it on, use the new PortForwarding option.
14931 o Major features (logging):
14932 - Add a new 'Heartbeat' log message type to periodically log a message
14933 describing Tor's status at level Notice. This feature is meant for
14934 operators who log at notice, and want to make sure that their Tor
14935 server is still working. Implementation by George Kadianakis.
14936 - Make logging resolution configurable with a new LogTimeGranularity
14937 option, and change the default from 1 millisecond to 1 second.
14938 Implements enhancement 1668.
14940 o Major features (other):
14941 - New "DisableNetwork" config option to prevent Tor from launching any
14942 connections or accepting any connections except on a control port.
14943 Bundles and controllers can set this option before letting Tor talk
14944 to the rest of the network, for example to prevent any connections
14945 to a non-bridge address. Packages like Orbot can also use this
14946 option to instruct Tor to save power when the network is off.
14947 - Try to use system facilities for enumerating local interface
14948 addresses, before falling back to our old approach (which was
14949 binding a UDP socket, and calling getsockname() on it). That
14950 approach was scaring OS X users whose draconian firewall
14951 software warned about binding to UDP sockets regardless of
14952 whether packets were sent. Now we try to use getifaddrs(),
14953 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
14954 system supports. Resolves ticket 1827.
14955 - Add experimental support for a "defaults" torrc file to be parsed
14956 before the regular torrc. Torrc options override the defaults file's
14957 options in the same way that the command line overrides the torrc.
14958 The SAVECONF controller command saves only those options which
14959 differ between the current configuration and the defaults file. HUP
14960 reloads both files. Implements task 4552.
14962 o New directory authorities:
14963 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
14964 authority. Closes ticket 5749.
14966 o Security/privacy fixes:
14967 - Avoid read-from-freed-memory and double-free bugs that could occur
14968 when a DNS request fails while launching it. Fixes bug 6480;
14969 bugfix on 0.2.0.1-alpha.
14970 - Reject any attempt to extend to an internal address. Without
14971 this fix, a router could be used to probe addresses on an internal
14972 network to see whether they were accepting connections. Fixes bug
14973 6710; bugfix on 0.0.8pre1.
14974 - Close any connection that sends unrecognized junk before the TLS
14975 handshake. Solves an issue noted in bug 4369.
14976 - The advertised platform of a relay now includes only its operating
14977 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not
14978 its service pack level (for Windows) or its CPU architecture
14979 (for Unix). Also drop the "git-XYZ" tag in the version. Packagers
14980 can insert an extra string in the platform line by setting the
14981 preprocessor variable TOR_BUILD_TAG. Resolves bug 2988.
14982 - Disable TLS session tickets. OpenSSL's implementation was giving
14983 our TLS session keys the lifetime of our TLS context objects, when
14984 perfect forward secrecy would want us to discard anything that
14985 could decrypt a link connection as soon as the link connection
14986 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
14987 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
14988 - Tor tries to wipe potentially sensitive data after using it, so
14989 that if some subsequent security failure exposes Tor's memory,
14990 the damage will be limited. But we had a bug where the compiler
14991 was eliminating these wipe operations when it decided that the
14992 memory was no longer visible to a (correctly running) program,
14993 hence defeating our attempt at defense in depth. We fix that
14994 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
14995 is unlikely to optimize away. Future versions of Tor may use
14996 a less ridiculously heavy approach for this. Fixes bug 7352.
14997 Reported in an article by Andrey Karpov.
14999 o Major bugfixes (crashes and asserts):
15000 - Avoid a pair of double-free and use-after-mark bugs that can
15001 occur with certain timings in canceled and re-received DNS
15002 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
15003 - Fix a denial of service attack by which any directory authority
15004 could crash all the others, or by which a single v2 directory
15005 authority could crash everybody downloading v2 directory
15006 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
15007 - Fix an assert that directory authorities could trigger on sighup
15008 during some configuration state transitions. We now don't treat
15009 it as a fatal error when the new descriptor we just generated in
15010 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
15011 - Avoid segfault when starting up having run with an extremely old
15012 version of Tor and parsing its state file. Fixes bug 6801; bugfix
15015 o Major bugfixes (clients):
15016 - If we are unable to find any exit that supports our predicted ports,
15017 stop calling them predicted, so that we don't loop and build
15018 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
15019 which introduced predicted ports.
15020 - Check at each new consensus whether our entry guards were picked
15021 long enough ago that we should rotate them. Previously, we only
15022 did this check at startup, which could lead to us holding a guard
15023 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
15024 - When fetching a bridge descriptor from a bridge authority,
15025 always do so anonymously, whether we have been able to open
15026 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
15027 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
15028 but we'll need to wait for bug 6010 before it's actually usable.
15030 o Major bugfixes (directory voting):
15031 - Check more thoroughly to prevent a rogue authority from
15032 double-voting on any consensus directory parameter. Previously,
15033 authorities would crash in this case if the total number of
15034 votes for any parameter exceeded the number of active voters,
15035 but would let it pass otherwise. Partially fixes bug 5786; bugfix
15037 - When computing weight parameters, behave more robustly in the
15038 presence of a bad bwweightscale value. Previously, the authorities
15039 would crash if they agreed on a sufficiently broken weight_scale
15040 value; now, they use a reasonable default and carry on. Fixes the
15041 rest of bug 5786; bugfix on 0.2.2.17-alpha.
15042 - If authorities are unable to get a v2 consensus document from other
15043 directory authorities, they no longer fall back to fetching
15044 them from regular directory caches. Fixes bug 5635; bugfix on
15045 0.2.2.26-beta, where routers stopped downloading v2 consensus
15046 documents entirely.
15048 o Major bugfixes (relays):
15049 - Fix a bug handling SENDME cells on nonexistent streams that could
15050 result in bizarre window values. Report and patch contributed
15051 pseudonymously. Fixes part of bug 6271. This bug was introduced
15052 before the first Tor release, in svn commit r152.
15053 - Don't update the AccountingSoftLimitHitAt state file entry whenever
15054 tor gets started. This prevents a wrong average bandwidth
15055 estimate, which would cause relays to always start a new accounting
15056 interval at the earliest possible moment. Fixes bug 2003; bugfix
15057 on 0.2.2.7-alpha. Reported by Bryon Eldridge, who also helped
15058 immensely in tracking this bug down.
15059 - Fix a possible crash bug when checking for deactivated circuits
15060 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
15061 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
15062 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
15063 connections. This change should allow busy exit relays to stop
15064 running out of available sockets as quickly. Fixes bug 4950;
15065 bugfix on 0.2.2.26-beta.
15067 o Major bugfixes (blocking resistance):
15068 - Bridges no longer include their address in NETINFO cells on outgoing
15069 OR connections, to allow them to blend in better with clients.
15070 Removes another avenue for enumerating bridges. Reported by
15071 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
15072 cells were introduced.
15073 - Warn the user when HTTPProxy, but no other proxy type, is
15074 configured. This can cause surprising behavior: it doesn't send
15075 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
15076 directory traffic only. Resolves ticket 4663.
15078 o Major bugfixes (hidden services):
15079 - Improve hidden service robustness: when an attempt to connect to
15080 a hidden service ends, be willing to refetch its hidden service
15081 descriptors from each of the HSDir relays responsible for them
15082 immediately. Previously, we would not consider refetching the
15083 service's descriptors from each HSDir for 15 minutes after the last
15084 fetch, which was inconvenient if the hidden service was not running
15085 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
15086 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
15087 They used to check that the timestamp was within 30 minutes
15088 of their system clock, so they could cap the size of their
15089 replay-detection cache, but that approach unnecessarily refused
15090 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
15091 the v3 intro-point protocol (the first one which sent a timestamp
15092 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
15093 - When one of a hidden service's introduction points appears to be
15094 unreachable, stop trying it. Previously, we would keep trying
15095 to build circuits to the introduction point until we lost the
15096 descriptor, usually because the user gave up and restarted Tor.
15097 Fixes part of bug 3825.
15099 o Changes to default torrc file:
15100 - Stop listing "socksport 9050" in torrc.sample. We open a socks
15101 port on 9050 by default anyway, so this should not change anything
15103 - Stop mentioning the deprecated *ListenAddress options in
15104 torrc.sample. Fixes bug 5438.
15105 - Document unit of bandwidth-related options in sample torrc.
15107 - Fix broken URLs in the sample torrc file, and tell readers about
15108 the OutboundBindAddress, ExitPolicyRejectPrivate, and
15109 PublishServerDescriptor options. Addresses bug 4652.
15111 o Minor features (directory authorities):
15112 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
15113 change when the authority is deciding whether to accept a newly
15114 uploaded descriptor. Implements ticket 6423.
15115 - Directory authorities are now a little more lenient at accepting
15116 older router descriptors, or newer router descriptors that don't
15117 make big changes. This should help ameliorate past and future
15118 issues where routers think they have uploaded valid descriptors,
15119 but the authorities don't think so. Fix for ticket 2479.
15120 - Authority operators can now vote for all relays in a given
15121 set of countries to be BadDir/BadExit/Invalid/Rejected.
15122 - Provide two consensus parameters (FastFlagMinThreshold and
15123 FastFlagMaxThreshold) to control the range of allowable bandwidths
15124 for the Fast directory flag. These allow authorities to run
15125 experiments on appropriate requirements for being a "Fast" node.
15126 The AuthDirFastGuarantee config value still applies. Implements
15129 o Minor features (bridges / bridge authorities):
15130 - Make bridge SSL certificates a bit more stealthy by using random
15131 serial numbers, in the same fashion as OpenSSL when generating
15132 self-signed certificates. Implements ticket 4584.
15133 - Tag a bridge's descriptor as "never to be sent unencrypted".
15134 This shouldn't matter, since bridges don't open non-anonymous
15135 connections to the bridge authority and don't allow unencrypted
15136 directory connections from clients, but we might as well make
15137 sure. Closes bug 5139.
15138 - The Bridge Authority now writes statistics on how many bridge
15139 descriptors it gave out in total, and how many unique descriptors
15140 it gave out. It also lists how often the most and least commonly
15141 fetched descriptors were given out, as well as the median and
15142 25th/75th percentile. Implements tickets 4200 and 4294.
15144 o Minor features (IPv6):
15145 - Make the code that clients use to detect an address change be
15146 IPv6-aware, so that it won't fill clients' logs with error
15147 messages when trying to get the IPv4 address of an IPv6
15148 connection. Implements ticket 5537.
15149 - Relays now understand an IPv6 address when they get one from a
15150 directory server. Resolves ticket 4875.
15152 o Minor features (hidden services):
15153 - Expire old or over-used hidden service introduction points.
15154 Required by fix for bug 3460.
15155 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
15156 public key replay-detection cache from 60 minutes to 5 minutes. This
15157 replay-detection cache is now used only to detect multiple
15158 INTRODUCE2 cells specifying the same rendezvous point, so we can
15159 avoid launching multiple simultaneous attempts to connect to it.
15160 - When a hidden service's introduction point times out, consider
15161 trying it again during the next attempt to connect to the
15162 HS. Previously, we would not try it again unless a newly fetched
15163 descriptor contained it. Required by fixes for bugs 1297 and 3825.
15165 o Minor features (relays):
15166 - Relays now include a reason for regenerating their descriptors
15167 in an HTTP header when uploading to the authorities. This will
15168 make it easier to debug descriptor-upload issues in the future.
15169 - Turn on directory request statistics by default and include them in
15170 extra-info descriptors. Don't break if we have no GeoIP database.
15171 - Replace files in stats/ rather than appending to them. Now that we
15172 include statistics in extra-info descriptors, it makes no sense to
15173 keep old statistics forever. Implements ticket 2930.
15174 - Relays that set "ConnDirectionStatistics 1" write statistics on the
15175 bidirectional use of connections to disk every 24 hours.
15176 - Add a GeoIP file digest to the extra-info descriptor. Implements
15179 o Minor features (new config options):
15180 - New config option "DynamicDHGroups" (disabled by default) provides
15181 each bridge with a unique prime DH modulus to be used during
15182 SSL handshakes. This option attempts to help against censors
15183 who might use the Apache DH modulus as a static identifier for
15184 bridges. Addresses ticket 4548.
15185 - New config option "DisableDebuggerAttachment" (on by default)
15186 to prevent basic debugging attachment attempts by other processes.
15187 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
15188 - Ordinarily, Tor does not count traffic from private addresses (like
15189 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
15190 There is now a new option, CountPrivateBandwidth, to disable this
15191 behavior. Patch from Daniel Cagara.
15193 o Minor features (different behavior for old config options):
15194 - Allow MapAddress directives to specify matches against super-domains,
15195 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
15196 Implements issue 933.
15197 - Don't disable the DirPort when we cannot exceed our AccountingMax
15198 limit during this interval because the effective bandwidthrate is
15199 low enough. This is useful in a situation where AccountMax is only
15200 used as an additional safeguard or to provide statistics.
15201 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
15202 implements ticket 3439.
15203 - When configuring a large set of nodes in EntryNodes, and there are
15204 enough of them listed as Guard so that we don't need to consider
15205 the non-guard entries, prefer the ones listed with the Guard flag.
15206 - If you set the NumCPUs option to 0, Tor will now try to detect how
15207 many CPUs you have. This is the new default behavior.
15208 - The NodeFamily option -- which let you declare that you want to
15209 consider nodes to be part of a family whether they list themselves
15210 that way or not -- now allows IP address ranges and country codes.
15212 o Minor features (new command-line config behavior):
15213 - Slightly change behavior of "list" options (that is, config
15214 options that can appear more than once) when they appear both in
15215 torrc and on the command line. Previously, the command-line options
15216 would be appended to the ones from torrc. Now, the command-line
15217 options override the torrc options entirely. This new behavior
15218 allows the user to override list options (like exit policies and
15219 ports to listen on) from the command line, rather than simply
15220 appending to the list.
15221 - You can get the old (appending) command-line behavior for "list"
15222 options by prefixing the option name with a "+".
15223 - You can remove all the values for a "list" option from the command
15224 line without adding any new ones by prefixing the option name
15227 o Minor features (controller, new events):
15228 - Extend the control protocol to report flags that control a circuit's
15229 path selection in CIRC events and in replies to 'GETINFO
15230 circuit-status'. Implements part of ticket 2411.
15231 - Extend the control protocol to report the hidden service address
15232 and current state of a hidden-service-related circuit in CIRC
15233 events and in replies to 'GETINFO circuit-status'. Implements part
15235 - Include the creation time of a circuit in CIRC and CIRC2
15236 control-port events and the list produced by the 'GETINFO
15237 circuit-status' control-port command.
15238 - Add a new CONF_CHANGED event so that controllers can be notified
15239 of any configuration changes made by other controllers, or by the
15240 user. Implements ticket 1692.
15241 - Add a new SIGNAL event to the controller interface so that
15242 controllers can be notified when Tor handles a signal. Resolves
15243 issue 1955. Patch by John Brooks.
15245 o Minor features (controller, new getinfo options):
15246 - Expose our view of whether we have gone dormant to the controller,
15247 via a new "GETINFO dormant" value. Torbutton and other controllers
15248 can use this to avoid doing periodic requests through Tor while
15249 it's dormant (bug 4718). Resolves ticket 5954.
15250 - Add a new GETINFO option to get total bytes read and written. Patch
15251 from pipe, revised by atagar. Resolves ticket 2345.
15252 - Implement new GETINFO controller fields to provide information about
15253 the Tor process's pid, euid, username, and resource limits.
15255 o Minor features (controller, other):
15256 - Allow controllers to request an event notification whenever a
15257 circuit is cannibalized or its purpose is changed. Implements
15258 part of ticket 3457.
15259 - Use absolute path names when reporting the torrc filename in the
15260 control protocol, so a controller can more easily find the torrc
15261 file. Resolves bug 1101.
15262 - When reporting the path to the cookie file to the controller,
15263 give an absolute path. Resolves ticket 4881.
15265 o Minor features (log messages):
15266 - Add more information to a log statement that might help track down
15267 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
15268 non-IP address" messages (or any Bug messages, for that matter!),
15269 please let us know about it.
15270 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
15271 EntryNodes will have no effect. Resolves issue 2571.
15272 - Try to make the introductory warning message that Tor prints on
15273 startup more useful for actually finding help and information.
15274 Resolves ticket 2474.
15275 - When the system call to create a listener socket fails, log the
15276 error message explaining why. This may help diagnose bug 4027.
15278 o Minor features (other):
15279 - When we fail to initialize Libevent, retry with IOCP disabled so we
15280 don't need to turn on multi-threading support in Libevent, which in
15281 turn requires a working socketpair(). This is a workaround for bug
15282 4457, which affects Libevent versions from 2.0.1-alpha through
15284 - When starting as root and then changing our UID via the User
15285 control option, and we have a ControlSocket configured, make sure
15286 that the ControlSocket is owned by the same account that Tor will
15287 run under. Implements ticket 3421; fix by Jérémy Bobbio.
15288 - Accept attempts to include a password authenticator in the
15289 handshake, as supported by SOCKS5. This handles SOCKS clients that
15290 don't know how to omit a password when authenticating. Resolves
15292 - Check for and recover from inconsistency in the microdescriptor
15293 cache. This will make it harder for us to accidentally free a
15294 microdescriptor without removing it from the appropriate data
15295 structures. Fixes issue 3135; issue noted by "wanoskarnet".
15296 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
15298 o Minor bugfixes (code security):
15299 - Prevent a null-pointer dereference when receiving a data cell
15300 for a nonexistent stream when the circuit in question has an
15301 empty deliver window. We don't believe this is triggerable,
15302 since we don't currently allow deliver windows to become empty,
15303 but the logic is tricky enough that it's better to make the code
15304 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
15305 - Fix a (harmless) integer overflow in cell statistics reported by
15306 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
15307 - Fix our implementation of crypto_random_hostname() so it can't
15308 overflow on ridiculously large inputs. (No Tor version has ever
15309 provided this kind of bad inputs, but let's be correct in depth.)
15310 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
15311 - Add a (probably redundant) memory clear between iterations of
15312 the router status voting loop, to prevent future coding errors
15313 where data might leak between iterations of the loop. Resolves
15316 o Minor bugfixes (wrapper functions):
15317 - Abort if tor_vasprintf() fails in connection_printf_to_buf() (a
15318 utility function used in the control-port code). This shouldn't
15319 ever happen unless Tor is completely out of memory, but if it did
15320 happen and Tor somehow recovered from it, Tor could have sent a log
15321 message to a control port in the middle of a reply to a controller
15322 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
15323 - Fix some (not actually triggerable) buffer size checks in usage of
15324 tor_inet_ntop(). Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
15326 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
15327 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
15328 - Enforce correct return behavior of tor_vsscanf() when the '%%'
15329 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
15330 - Make our replacement implementation of strtok_r() compatible with
15331 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
15332 bugfix on 0.2.2.1-alpha.
15333 - Find more places in the code that should have been testing for
15334 invalid sockets using the SOCKET_OK macro. Required for a fix
15335 for bug 4533. Bugfix on 0.2.2.28-beta.
15337 o Minor bugfixes (code correctness):
15338 - Check return value of fputs() when writing authority certificate
15339 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
15340 - When building Tor on Windows with -DUNICODE (not default), ensure
15341 that error messages, filenames, and DNS server names are always
15342 NUL-terminated when we convert them to a single-byte encoding.
15343 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
15344 - Fix a memory leak when trying to launch a DNS request when the
15345 nameservers are unconfigurable. Fixes bug 5916; bugfix on Tor
15347 - Correct file sizes when reading binary files on Cygwin, to avoid
15348 a bug where Tor would fail to read its state file. Fixes bug 6844;
15349 bugfix on 0.1.2.7-alpha.
15350 - Make sure to set *socket_error in all error cases in
15351 connection_connect(), so it can't produce a warning about
15352 errno being zero from errno_to_orconn_end_reason(). Bugfix on
15353 0.2.1.1-alpha; resolves ticket 6028.
15354 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
15355 bug 4532; found by "troll_un".
15357 o Minor bugfixes (clients):
15358 - Allow one-hop directory-fetching circuits the full "circuit build
15359 timeout" period, rather than just half of it, before failing them
15360 and marking the relay down. This fix should help reduce cases where
15361 clients declare relays (or worse, bridges) unreachable because
15362 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
15363 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
15365 - Ensure we don't cannibalize circuits that are longer than three hops
15366 already, so we don't end up making circuits with 5 or more
15367 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
15368 0.1.0.1-rc which introduced cannibalization.
15370 o Minor bugfixes (relays):
15371 - Don't publish a new relay descriptor when we reload our onion key,
15372 unless the onion key has actually changed. Fixes bug 3263 and
15373 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
15374 - When relays refuse a "create" cell because their queue of pending
15375 create cells is too big (typically because their cpu can't keep up
15376 with the arrival rate), send back reason "resource limit" rather
15377 than reason "internal", so network measurement scripts can get a
15378 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
15379 - Exit nodes don't need to fetch certificates for authorities that
15380 they don't recognize; only directory authorities, bridges,
15381 and caches need to do that. Fixes part of bug 2297; bugfix on
15384 o Minor bugfixes (directory authority / mirrors):
15385 - Avoid O(n^2) performance characteristics when parsing a large
15386 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
15387 - Authorities no longer include any router in their microdescriptor
15388 consensuses for which they couldn't generate or agree on a
15389 microdescriptor. Fixes the second piece of bug 6404; fix on
15391 - When checking for requested signatures on the latest consensus
15392 before serving it to a client, make sure to check the right
15393 consensus flavor. Bugfix on 0.2.2.6-alpha.
15394 - Fix an edge case where TestingTorNetwork is set but the authorities
15395 and relays all have an uptime of zero, so the private Tor network
15396 could briefly lack support for hidden services. Fixes bug 3886;
15397 bugfix on 0.2.2.18-alpha.
15398 - Directory caches no longer refuse to clean out descriptors because
15399 of missing v2 networkstatus documents, unless they're configured
15400 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
15401 0.2.2.26-beta. Patch by Daniel Bryg.
15402 - Don't serve or accept v2 hidden service descriptors over a relay's
15403 DirPort. It's never correct to do so, and disabling it might
15404 make it more annoying to exploit any bugs that turn up in the
15405 descriptor-parsing code. Fixes bug 7149.
15407 o Minor bugfixes (hidden services, client-side):
15408 - Assert that hidden-service-related operations are not performed
15409 using single-hop circuits. Previously, Tor would assert that
15410 client-side streams are not attached to single-hop circuits,
15411 but not that other sensitive operations on the client and service
15412 side are not performed using single-hop circuits. Fixes bug 3332;
15414 - Avoid undefined behavior when parsing the list of supported
15415 rendezvous/introduction protocols in a hidden service descriptor.
15416 Previously, Tor would have confused (as-yet-unused) protocol version
15417 numbers greater than 32 with lower ones on many platforms. Fixes
15418 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
15419 - Don't close hidden service client circuits which have almost
15420 finished connecting to their destination when they reach
15421 the normal circuit-build timeout. Previously, we would close
15422 introduction circuits which are waiting for an acknowledgement
15423 from the introduction point, and rendezvous circuits which have
15424 been specified in an INTRODUCE1 cell sent to a hidden service,
15425 after the normal CBT. Now, we mark them as 'timed out', and launch
15426 another rendezvous attempt in parallel. This behavior change can
15427 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
15428 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
15430 o Minor bugfixes (hidden services, service-side):
15431 - Don't close hidden-service-side rendezvous circuits when they
15432 reach the normal circuit-build timeout. This behavior change can
15433 be disabled using the new
15434 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
15435 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
15436 - Don't launch more than 10 service-side introduction-point circuits
15437 for a hidden service in five minutes. Previously, we would consider
15438 launching more introduction-point circuits if at least one second
15439 had passed without any introduction-point circuits failing. Fixes
15440 bug 4607; bugfix on 0.0.7pre1.
15442 o Minor bugfixes (config option behavior):
15443 - If the user tries to set MyFamily on a bridge, refuse to
15444 do so, and warn about the security implications. Fixes bug 4657;
15445 bugfix on 0.2.0.3-alpha.
15446 - The "--quiet" and "--hush" options now apply not only to Tor's
15447 behavior before logs are configured, but also to Tor's behavior in
15448 the absence of configured logs. Fixes bug 3550; bugfix on
15450 - Change the AllowDotExit rules so they should actually work.
15451 We now enforce AllowDotExit only immediately after receiving an
15452 address via SOCKS or DNSPort: other sources are free to provide
15453 .exit addresses after the resolution occurs. Fixes bug 3940;
15454 bugfix on 0.2.2.1-alpha.
15455 - Make "LearnCircuitBuildTimeout 0" work more reliably. Specifically,
15456 don't depend on the consensus parameters or compute adaptive
15457 timeouts when it is disabled. Fixes bug 5049; bugfix on
15459 - After we pick a directory mirror, we would refuse to use it if
15460 it's in our ExcludeExitNodes list, resulting in mysterious failures
15461 to bootstrap for people who just wanted to avoid exiting from
15462 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
15463 - When told to add a bridge with the same digest as a preexisting
15464 bridge but a different addr:port, change the addr:port as
15465 requested. Previously we would not notice the change. Fixes half
15466 of bug 5603; fix on 0.2.2.26-beta.
15468 o Minor bugfixes (controller):
15469 - Allow manual 'authenticate' commands to the controller interface
15470 from netcat (nc) as well as telnet. We were rejecting them because
15471 they didn't come with the expected whitespace at the end of the
15472 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
15473 - Report a real bootstrap problem to the controller on router
15474 identity mismatch. Previously we just said "foo", which probably
15475 made a lot of sense at the time. Fixes bug 4169; bugfix on
15477 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
15478 option is set to 0 (which Vidalia version 0.2.16 now does when
15479 a SAVECONF attempt fails), perform other actions that SIGHUP
15480 usually causes (like reopening the logs). Fixes bug 5095; bugfix
15482 - Correctly handle checking the permissions on the parent
15483 directory of a control socket in the root directory. Bug found
15484 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
15486 - End AUTHCHALLENGE error messages (in the control protocol) with
15487 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36.
15489 o Minor bugfixes (network reading/writing):
15490 - Disable writing on marked-for-close connections when they are
15491 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
15492 bug 5263; bugfix on 0.0.2pre13, where we first added a special
15493 case for flushing marked connections.
15494 - Make sure that there are no unhandled pending TLS errors before
15495 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
15496 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
15497 Bugfix on 0.1.0.5-rc; fixes bug 4528.
15498 - Detect SSL handshake even when the initial attempt to write the
15499 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
15500 - If the client fails to set a reasonable set of ciphersuites
15501 during its v2 handshake renegotiation, allow the renegotiation to
15502 continue nevertheless (i.e. send all the required certificates).
15503 Fixes bug 4591; bugfix on 0.2.0.20-rc.
15505 o Minor bugfixes (other):
15506 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
15507 resource exhaustion, so that clients can adjust their load to
15508 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
15509 started using END_STREAM_REASON_RESOURCELIMIT.
15510 - Don't check for whether the address we're using for outbound
15511 connections has changed until after the outbound connection has
15512 completed. On Windows, getsockname() doesn't succeed until the
15513 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
15514 - Don't hold a Windows file handle open for every file mapping;
15515 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
15517 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
15518 bugfix on 0.2.1.10-alpha.
15519 - If we fail to write a microdescriptor to the disk cache, do not
15520 continue replacing the old microdescriptor file. Fixes bug 2954;
15521 bugfix on 0.2.2.6-alpha.
15523 o Minor bugfixes (log messages, path selection):
15524 - Downgrade "set buildtimeout to low value" messages to "info"
15525 severity; they were never an actual problem, there was never
15526 anything reasonable to do about them, and they tended to spam logs
15527 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
15528 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
15529 more information to it, so that we can track it down in case it
15530 returns again. Mitigates bug 5235.
15531 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
15532 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
15533 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
15534 - Issue a log message if a guard completes less than 40% of your
15535 circuits. Threshold is configurable by torrc option
15536 PathBiasNoticeRate and consensus parameter pb_noticepct. There is
15537 additional, off-by-default code to disable guards which fail too
15538 many circuits. Addresses ticket 5458.
15540 o Minor bugfixes (log messages, client):
15541 - Downgrade "Got a certificate, but we already have it" log messages
15542 from warning to info, except when we're a dirauth. Fixes bug 5238;
15543 bugfix on 0.2.1.7-alpha.
15544 - Fix the log message describing how we work around discovering
15545 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
15546 4837; bugfix on 0.2.2.9-alpha.
15547 - When logging about a disallowed .exit name, do not also call it
15548 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
15549 - Fix a log message suggesting that people contact a non-existent
15550 email address. Fixes bug 3448.
15551 - Rephrase the log message emitted if the TestSocks check is
15552 successful. Patch from Fabian Keil; fixes bug 4094.
15553 - Log (at debug level) whenever a circuit's purpose is changed.
15554 - Log SSL state transitions at log level DEBUG, log domain
15555 HANDSHAKE. This can be useful for debugging censorship events.
15556 Implements ticket 3264.
15557 - We now log which torrc file we're using on startup. Implements
15559 - Rate-limit log messages when asked to connect anonymously to
15560 a private address. When these hit, they tended to hit fast and
15561 often. Also, don't bother trying to connect to addresses that we
15562 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
15563 reply makes us think we have been lied to, even when the address the
15564 client tried to connect to was "localhost." Resolves ticket 2822.
15566 o Minor bugfixes (log messages, non-client):
15567 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
15568 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
15569 - Don't log that we have "decided to publish new relay descriptor"
15570 unless we are actually publishing a descriptor. Fixes bug 3942;
15571 bugfix on 0.2.2.28-beta.
15572 - Log which authority we're missing votes from when we go to fetch
15573 them from the other auths.
15574 - Replace "Sending publish request" log messages with "Launching
15575 upload", so that they no longer confusingly imply that we're
15576 sending something to a directory we might not even be connected
15577 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
15578 - Warn when Tor is configured to use accounting in a way that can
15579 link a hidden service to some other hidden service or public
15580 address. Resolves ticket 6490.
15581 - Fix a minor formatting issue in one of tor-gencert's error messages.
15585 - Update to the latest version of the tinytest unit testing framework.
15586 This includes a couple of bugfixes that can be relevant for
15587 running forked unit tests on Windows, and removes all reserved
15589 - Avoid a false positive in the util/threads unit test by increasing
15590 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
15591 - Make it possible to set the TestingTorNetwork configuration
15592 option using AlternateDirAuthority and AlternateBridgeAuthority
15593 as an alternative to setting DirServer. Addresses ticket 6377.
15594 - Add a unit test for the environment_variable_names_equal() function.
15595 - A wide variety of new unit tests by Esteban Manchado Velázquez.
15596 - Numerous new unit tests for functions in util.c and address.c by
15598 - The long-disabled benchmark tests are now split into their own
15599 ./src/test/bench binary.
15600 - The benchmark tests can now use more accurate timers than
15601 gettimeofday() when such timers are available.
15602 - Use tt_assert(), not tor_assert(), for checking for test failures.
15603 This makes the unit tests more able to go on in the event that
15606 o Build improvements:
15607 - Use the dead_strip option when building Tor on OS X. This reduces
15608 binary size by almost 19% when linking openssl and libevent
15609 statically, which we do for Tor Browser Bundle.
15610 - Provide a better error message about possible OSX Asciidoc failure
15611 reasons. Fixes bug 6436.
15612 - Detect attempts to build Tor on (as yet hypothetical) versions
15613 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
15614 fix for bug 4533. Bugfix on 0.2.2.28-beta.
15615 - On Windows, we now define the _WIN32_WINNT macros only if they
15616 are not already defined. This lets the person building Tor decide,
15617 if they want, to require a later version of Windows.
15618 - Our autogen.sh script now uses autoreconf to launch autoconf,
15619 automake, and so on. This is more robust against some of the failure
15620 modes associated with running the autotools pieces on their own.
15621 - Running "make version" now displays the version of Tor that
15622 we're about to build. Idea from katmagic; resolves issue 4400.
15623 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
15624 on 0.2.2.4-alpha; fixes bug 3427.
15625 - New --enable-static-tor configure option for building Tor as
15626 statically as possible. Idea, general hackery and thoughts from
15627 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
15629 - Limited, experimental support for building with nmake and MSVC.
15631 o Build requirements:
15632 - Building Tor with bufferevent support now requires Libevent
15633 2.0.13-stable or later. Previous versions of Libevent had bugs in
15634 SSL-related bufferevents and related issues that would make Tor
15635 work badly with bufferevents. Requiring 2.0.13-stable also allows
15636 Tor with bufferevents to take advantage of Libevent APIs
15637 introduced after 2.0.8-rc.
15638 - Our build system requires automake 1.6 or later to create the
15639 Makefile.in files. Previously, you could have used 1.4.
15640 This only affects developers and people building Tor from git;
15641 people who build Tor from the source distribution without changing
15642 the Makefile.am files should be fine.
15643 - Detect when we try to build on a platform that doesn't define
15644 AF_UNSPEC to 0. We don't work there, so refuse to compile.
15646 o Build fixes (compile/link):
15647 - Format more doubles with %f, not %lf. Patch from grarpamp to make
15648 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
15650 - When building with --enable-static-tor on OpenBSD, do not
15651 erroneously attempt to link -lrt. Fixes bug 5103.
15652 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
15653 that IPv6 stuff will compile on MSVC, and compilation issues
15654 will be easier to track down. Fixes bug 5861.
15655 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
15656 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
15657 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
15658 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
15660 o Build fixes (other):
15661 - Use the _WIN32 macro throughout our code to detect Windows.
15662 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
15664 - Properly handle the case where the build-tree is not the same
15665 as the source tree when generating src/common/common_sha1.i,
15666 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
15667 bugfix on 0.2.0.1-alpha.
15668 - During configure, search for library containing cos function as
15669 libm lives in libcore on some platforms (BeOS/Haiku). Linking
15670 against libm was hard-coded before. Fixes the first part of bug
15671 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
15673 - Prevent a false positive from the check-spaces script, by disabling
15674 the "whitespace between function name and (" check for functions
15677 o Packaging (RPM) changes:
15678 - Update our default RPM spec files to work with mock and rpmbuild
15679 on RHEL/Fedora. They have an updated set of dependencies and
15680 conflicts, a fix for an ancient typo when creating the "_tor"
15681 user, and better instructions. Thanks to Ondrej Mikle for the
15682 patch series. Fixes bug 6043.
15683 - On OpenSUSE, create the /var/run/tor directory on startup if it
15684 is not already created. Patch from Andreas Stieger. Fixes bug 2573.
15686 o Code refactoring (safety):
15687 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
15688 10 lines. Also, don't nest them. Doing so in the past has
15689 led to hard-to-debug code. The new style is to use the
15690 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
15691 - Use macros to indicate OpenSSL versions, so we don't need to worry
15692 about accidental hexadecimal bit shifts.
15693 - Use tor_sscanf() in place of scanf() in more places through the
15694 code. This makes us a little more locale-independent, and
15695 should help shut up code-analysis tools that can't tell
15696 a safe sscanf string from a dangerous one.
15697 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
15698 - Use the smartlist_add_asprintf() alias more consistently.
15700 o Code refactoring (consolidate):
15701 - A major revision to our internal node-selecting and listing logic.
15702 Tor already had at least two major ways to look at the question of
15703 "which Tor servers do we know about": a list of router descriptors,
15704 and a list of entries in the current consensus. With
15705 microdescriptors, we're adding a third. Having so many systems
15706 without an abstraction layer over them was hurting the codebase.
15707 Now, we have a new "node_t" abstraction that presents a consistent
15708 interface to a client's view of a Tor node, and holds (nearly) all
15709 of the mutable state formerly in routerinfo_t and routerstatus_t.
15710 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
15711 Libevent's notion of cached time when possible.
15712 - Remove duplicate code for invoking getrlimit() from control.c.
15713 - Use OpenSSL's built-in SSL_state_string_long() instead of our
15714 own homebrewed ssl_state_to_string() replacement. Patch from
15715 Emile Snyder. Fixes bug 4653.
15716 - Change the symmetric cipher interface so that creating and
15717 initializing a stream cipher are no longer separate functions.
15719 o Code refactoring (separate):
15720 - Make a new "entry connection" struct as an internal subtype of "edge
15721 connection", to simplify the code and make exit connections smaller.
15722 - Split connection_about_to_close() into separate functions for each
15724 - Rewrite the listener-selection logic so that parsing which ports
15725 we want to listen on is now separate from binding to the ports
15728 o Code refactoring (name changes):
15729 - Rename a handful of old identifiers, mostly related to crypto
15730 structures and crypto functions. By convention, our "create an
15731 object" functions are called "type_new()", our "free an object"
15732 functions are called "type_free()", and our types indicate that
15733 they are types only with a final "_t". But a handful of older
15734 types and functions broke these rules, with function names like
15735 "type_create" or "subsystem_op_type", or with type names like
15737 - Rename Tor functions that turn strings into addresses, so that
15738 "parse" indicates that no hostname resolution occurs, and
15739 "lookup" indicates that hostname resolution may occur. This
15740 should help prevent mistakes in the future. Fixes bug 3512.
15741 - Use the name "CERTS" consistently to refer to the new cell type;
15742 we were calling it CERT in some places and CERTS in others.
15743 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
15744 invalid value, rather than just -1.
15745 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
15746 can pick them up when the tests aren't disabled. Bugfix on
15747 0.2.2.4-alpha which introduced tinytest.
15749 o Code refactoring (other):
15750 - Defensively refactor rend_mid_rendezvous() so that protocol
15751 violations and length checks happen in the beginning. Fixes
15753 - Remove the pure attribute from all functions that used it
15754 previously. In many cases we assigned it incorrectly, because the
15755 functions might assert or call impure functions, and we don't have
15756 evidence that keeping the pure attribute is worthwhile. Implements
15757 changes suggested in ticket 4421.
15758 - Move the replay-detection cache for the RSA-encrypted parts of
15759 INTRODUCE2 cells to the introduction point data structures.
15760 Previously, we would use one replay-detection cache per hidden
15761 service. Required by fix for bug 3460.
15762 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
15763 no longer link against Libevent: they never used it, but
15764 our library structure used to force them to link it.
15766 o Removed features and files:
15767 - Remove all internal support for unpadded RSA. We never used it, and
15768 it would be a bad idea to start.
15769 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
15771 - Remove some redundant #include directives throughout the code.
15772 Patch from Andrea Gelmini.
15773 - Remove some old code to remember statistics about which descriptors
15774 we've served as a directory mirror. The feature wasn't used and
15775 is outdated now that microdescriptors are around.
15776 - Remove some old code to work around even older versions of Tor that
15777 used forked processes to handle DNS requests. Such versions of Tor
15778 are no longer in use as relays.
15779 - The "torify" script no longer supports the "tsocks" socksifier
15780 tool, since tsocks doesn't support DNS and UDP right for Tor.
15781 Everyone should be using torsocks instead. Fixes bugs 3530 and
15782 5180. Based on a patch by "ugh".
15783 - Remove the torrc.bridge file: we don't use it for anything, and
15784 it had become badly desynchronized from torrc.sample. Resolves
15788 - Begin a doc/state-contents.txt file to explain the contents of
15789 the Tor state file. Fixes bug 2987.
15790 - Clarify the documentation for the Alternate*Authority options.
15792 - Document the --defaults-torrc option, and the new semantics for
15793 overriding, extending, and clearing lists of options. Closes
15795 - Add missing man page documentation for consensus and microdesc
15796 files. Resolves ticket 6732.
15797 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
15799 o Documentation fixes:
15800 - Improve the manual's documentation for the NT Service command-line
15801 options. Addresses ticket 3964.
15802 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
15803 - Document the changes to the ORPort and DirPort options, and the
15804 fact that {OR/Dir}ListenAddress is now unnecessary (and
15805 therefore deprecated). Resolves ticket 5597.
15806 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
15807 - Clarify that hidden services are TCP only. Fixes bug 6024.
15810 Changes in version 0.2.2.39 - 2012-09-11
15811 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
15815 - Fix an assertion failure in tor_timegm() that could be triggered
15816 by a badly formatted directory object. Bug found by fuzzing with
15817 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
15818 - Do not crash when comparing an address with port value 0 to an
15819 address policy. This bug could have been used to cause a remote
15820 assertion failure by or against directory authorities, or to
15821 allow some applications to crash clients. Fixes bug 6690; bugfix
15825 Changes in version 0.2.2.38 - 2012-08-12
15826 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
15827 attack that could in theory leak path information.
15830 - Avoid an uninitialized memory read when reading a vote or consensus
15831 document that has an unrecognized flavor name. This read could
15832 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
15833 - Try to leak less information about what relays a client is
15834 choosing to a side-channel attacker. Previously, a Tor client would
15835 stop iterating through the list of available relays as soon as it
15836 had chosen one, thus finishing a little earlier when it picked
15837 a router earlier in the list. If an attacker can recover this
15838 timing information (nontrivial but not proven to be impossible),
15839 they could learn some coarse-grained information about which relays
15840 a client was picking (middle nodes in particular are likelier to
15841 be affected than exits). The timing attack might be mitigated by
15842 other factors (see bug 6537 for some discussion), but it's best
15843 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
15846 Changes in version 0.2.2.37 - 2012-06-06
15847 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
15848 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
15852 - Work around a bug in OpenSSL that broke renegotiation with TLS
15853 1.1 and TLS 1.2. Without this workaround, all attempts to speak
15854 the v2 Tor connection protocol when both sides were using OpenSSL
15855 1.0.1 would fail. Resolves ticket 6033.
15856 - When waiting for a client to renegotiate, don't allow it to add
15857 any bytes to the input buffer. This fixes a potential DoS issue.
15858 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
15859 - Fix an edge case where if we fetch or publish a hidden service
15860 descriptor, we might build a 4-hop circuit and then use that circuit
15861 for exiting afterwards -- even if the new last hop doesn't obey our
15862 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
15865 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
15866 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
15869 - Tell GCC and Clang to check for any errors in format strings passed
15870 to the tor_v*(print|scan)f functions.
15873 Changes in version 0.2.2.36 - 2012-05-24
15874 Tor 0.2.2.36 updates the addresses for two of the eight directory
15875 authorities, fixes some potential anonymity and security issues,
15876 and fixes several crash bugs.
15878 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
15879 known flaws, and nobody should be using them. You should upgrade. If
15880 you're using a Linux or BSD and its packages are obsolete, stop using
15881 those packages and upgrade anyway.
15883 o Directory authority changes:
15884 - Change IP address for maatuska (v3 directory authority).
15885 - Change IP address for ides (v3 directory authority), and rename
15889 - When building or running with any version of OpenSSL earlier
15890 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
15891 versions have a bug (CVE-2011-4576) in which their block cipher
15892 padding includes uninitialized data, potentially leaking sensitive
15893 information to any peer with whom they make a SSLv3 connection. Tor
15894 does not use SSL v3 by default, but a hostile client or server
15895 could force an SSLv3 connection in order to gain information that
15896 they shouldn't have been able to get. The best solution here is to
15897 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
15898 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
15899 to make sure that the bug can't happen.
15900 - Never use a bridge or a controller-supplied node as an exit, even
15901 if its exit policy allows it. Found by wanoskarnet. Fixes bug
15902 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
15903 and 0.2.0.3-alpha (for bridge-purpose descriptors).
15904 - Only build circuits if we have a sufficient threshold of the total
15905 descriptors that are marked in the consensus with the "Exit"
15906 flag. This mitigates an attack proposed by wanoskarnet, in which
15907 all of a client's bridges collude to restrict the exit nodes that
15908 the client knows about. Fixes bug 5343.
15909 - Provide controllers with a safer way to implement the cookie
15910 authentication mechanism. With the old method, if another locally
15911 running program could convince a controller that it was the Tor
15912 process, then that program could trick the controller into telling
15913 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
15914 authentication method uses a challenge-response approach to prevent
15915 this attack. Fixes bug 5185; implements proposal 193.
15918 - Avoid logging uninitialized data when unable to decode a hidden
15919 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
15920 - Avoid a client-side assertion failure when receiving an INTRODUCE2
15921 cell on a general purpose circuit. Fixes bug 5644; bugfix on
15923 - Fix builds when the path to sed, openssl, or sha1sum contains
15924 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
15926 - Correct our replacements for the timeradd() and timersub() functions
15927 on platforms that lack them (for example, Windows). The timersub()
15928 function is used when expiring circuits, while timeradd() is
15929 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
15930 bugfix on 0.2.2.24-alpha.
15931 - Fix the SOCKET_OK test that we use to tell when socket
15932 creation fails so that it works on Win64. Fixes part of bug 4533;
15933 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
15936 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
15937 Fixes bug 5346; bugfix on 0.0.8pre3.
15938 - Make our number-parsing functions always treat too-large values
15939 as an error, even when those values exceed the width of the
15940 underlying type. Previously, if the caller provided these
15941 functions with minima or maxima set to the extreme values of the
15942 underlying integer type, these functions would return those
15943 values on overflow rather than treating overflow as an error.
15944 Fixes part of bug 5786; bugfix on 0.0.9.
15945 - Older Linux kernels erroneously respond to strange nmap behavior
15946 by having accept() return successfully with a zero-length
15947 socket. When this happens, just close the connection. Previously,
15948 we would try harder to learn the remote address: but there was
15949 no such remote address to learn, and our method for trying to
15950 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
15951 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
15952 - Correct parsing of certain date types in parse_http_time().
15953 Without this patch, If-Modified-Since would behave
15954 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
15955 Esteban Manchado Velázques.
15956 - Change the BridgePassword feature (part of the "bridge community"
15957 design, which is not yet implemented) to use a time-independent
15958 comparison. The old behavior might have allowed an adversary
15959 to use timing to guess the BridgePassword value. Fixes bug 5543;
15960 bugfix on 0.2.0.14-alpha.
15961 - Detect and reject certain misformed escape sequences in
15962 configuration values. Previously, these values would cause us
15963 to crash if received in a torrc file or over an authenticated
15964 control port. Bug found by Esteban Manchado Velázquez, and
15965 independently by Robert Connolly from Matta Consulting who further
15966 noted that it allows a post-authentication heap overflow. Patch
15967 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
15968 bugfix on 0.2.0.16-alpha.
15969 - Fix a compile warning when using the --enable-openbsd-malloc
15970 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
15971 - During configure, detect when we're building with clang version
15972 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
15973 CFLAGS. clang doesn't support them yet.
15974 - When sending an HTTP/1.1 proxy request, include a Host header.
15975 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
15976 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
15977 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
15978 - If we hit the error case where routerlist_insert() replaces an
15979 existing (old) server descriptor, make sure to remove that
15980 server descriptor from the old_routers list. Fix related to bug
15981 1776. Bugfix on 0.2.2.18-alpha.
15983 o Minor bugfixes (documentation and log messages):
15984 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
15985 Fixes bug 4856; bugfix on Tor 0.0.6.
15986 - Update "ClientOnly" man page entry to explain that there isn't
15987 really any point to messing with it. Resolves ticket 5005.
15988 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
15989 directory authority option (introduced in Tor 0.2.2.34).
15990 - Downgrade the "We're missing a certificate" message from notice
15991 to info: people kept mistaking it for a real problem, whereas it
15992 is seldom the problem even when we are failing to bootstrap. Fixes
15993 bug 5067; bugfix on 0.2.0.10-alpha.
15994 - Correctly spell "connect" in a log message on failure to create a
15995 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
15996 - Clarify the behavior of MaxCircuitDirtiness with hidden service
15997 circuits. Fixes issue 5259.
16000 - Directory authorities now reject versions of Tor older than
16001 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
16002 inclusive. These versions accounted for only a small fraction of
16003 the Tor network, and have numerous known security issues. Resolves
16005 - Update to the May 1 2012 Maxmind GeoLite Country database.
16008 - When sending or relaying a RELAY_EARLY cell, we used to convert
16009 it to a RELAY cell if the connection was using the v1 link
16010 protocol. This was a workaround for older versions of Tor, which
16011 didn't handle RELAY_EARLY cells properly. Now that all supported
16012 versions can handle RELAY_EARLY cells, and now that we're enforcing
16013 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
16014 remove this workaround. Addresses bug 4786.
16017 Changes in version 0.2.2.35 - 2011-12-16
16018 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
16019 buffers code. Absolutely everybody should upgrade.
16021 The bug relied on an incorrect calculation when making data continuous
16022 in one of our IO buffers, if the first chunk of the buffer was
16023 misaligned by just the wrong amount. The miscalculation would allow an
16024 attacker to overflow a piece of heap-allocated memory. To mount this
16025 attack, the attacker would need to either open a SOCKS connection to
16026 Tor's SocksPort (usually restricted to localhost), or target a Tor
16027 instance configured to make its connections through a SOCKS proxy
16028 (which Tor does not do by default).
16030 Good security practice requires that all heap-overflow bugs should be
16031 presumed to be exploitable until proven otherwise, so we are treating
16032 this as a potential code execution attack. Please upgrade immediately!
16033 This bug does not affect bufferevents-based builds of Tor. Special
16034 thanks to "Vektor" for reporting this issue to us!
16036 Tor 0.2.2.35 also fixes several bugs in previous versions, including
16037 crash bugs for unusual configurations, and a long-term bug that
16038 would prevent Tor from starting on Windows machines with draconian
16041 With this release, we remind everyone that 0.2.0.x has reached its
16042 formal end-of-life. Those Tor versions have many known flaws, and
16043 nobody should be using them. You should upgrade -- ideally to the
16044 0.2.2.x series. If you're using a Linux or BSD and its packages are
16045 obsolete, stop using those packages and upgrade anyway.
16047 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
16048 longer receive support after some time in early 2012.
16051 - Fix a heap overflow bug that could occur when trying to pull
16052 data into the first chunk of a buffer, when that chunk had
16053 already had some data drained from it. Fixes CVE-2011-2778;
16054 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16055 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
16056 that it doesn't attempt to allocate a socketpair. This could cause
16057 some problems on Windows systems with overzealous firewalls. Fix for
16058 bug 4457; workaround for Libevent versions 2.0.1-alpha through
16060 - If we mark an OR connection for close based on a cell we process,
16061 don't process any further cells on it. We already avoid further
16062 reads on marked-for-close connections, but now we also discard the
16063 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
16064 which was the first version where we might mark a connection for
16065 close based on processing a cell on it.
16066 - Correctly sanity-check that we don't underflow on a memory
16067 allocation (and then assert) for hidden service introduction
16068 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16069 bugfix on 0.2.1.5-alpha.
16070 - Fix a memory leak when we check whether a hidden service
16071 descriptor has any usable introduction points left. Fixes bug
16072 4424. Bugfix on 0.2.2.25-alpha.
16073 - Don't crash when we're running as a relay and don't have a GeoIP
16074 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
16075 we've had in the 0.2.3.x branch already.
16076 - When running as a client, do not print a misleading (and plain
16077 wrong) log message that we're collecting "directory request"
16078 statistics: clients don't collect statistics. Also don't create a
16079 useless (because empty) stats file in the stats/ directory. Fixes
16080 bug 4353; bugfix on 0.2.2.34.
16083 - Detect failure to initialize Libevent. This fix provides better
16084 detection for future instances of bug 4457.
16085 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
16086 function. This was eating up hideously large amounts of time on some
16087 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
16088 - Resolve an integer overflow bug in smartlist_ensure_capacity().
16089 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
16091 - Don't warn about unused log_mutex in log.c when building with
16092 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
16093 0.1.0.6-rc which introduced --disable-threads.
16094 - When configuring, starting, or stopping an NT service, stop
16095 immediately after the service configuration attempt has succeeded
16096 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
16097 - When sending a NETINFO cell, include the original address
16098 received for the other side, not its canonical address. Found
16099 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
16100 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
16101 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
16102 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
16103 occurred when a client tried to fetch a descriptor for a bridge
16104 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
16105 - Backport fixes for a pair of compilation warnings on Windows.
16106 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
16107 - If we had ever tried to call tor_addr_to_str on an address of
16108 unknown type, we would have done a strdup on an uninitialized
16109 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
16110 Reported by "troll_un".
16111 - Correctly detect and handle transient lookup failures from
16112 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
16113 Reported by "troll_un".
16114 - Fix null-pointer access that could occur if TLS allocation failed.
16115 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
16116 - Use tor_socket_t type for listener argument to accept(). Fixes bug
16117 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
16120 - Add two new config options for directory authorities:
16121 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
16122 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
16123 that is always sufficient to satisfy the bandwidth requirement for
16124 the Guard flag. Now it will be easier for researchers to simulate
16125 Tor networks with different values. Resolves ticket 4484.
16126 - When Tor ignores a hidden service specified in its configuration,
16127 include the hidden service's directory in the warning message.
16128 Previously, we would only tell the user that some hidden service
16129 was ignored. Bugfix on 0.0.6; fixes bug 4426.
16130 - Update to the December 6 2011 Maxmind GeoLite Country database.
16132 o Packaging changes:
16133 - Make it easier to automate expert package builds on Windows,
16134 by removing an absolute path from makensis.exe command.
16137 Changes in version 0.2.1.32 - 2011-12-16
16138 Tor 0.2.1.32 backports important security and privacy fixes for
16139 oldstable. This release is intended only for package maintainers and
16140 others who cannot use the 0.2.2 stable series. All others should be
16141 using Tor 0.2.2.x or newer.
16143 The Tor 0.2.1.x series will reach formal end-of-life some time in
16144 early 2012; we will stop releasing patches for it then.
16146 o Major bugfixes (also included in 0.2.2.x):
16147 - Correctly sanity-check that we don't underflow on a memory
16148 allocation (and then assert) for hidden service introduction
16149 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
16150 bugfix on 0.2.1.5-alpha.
16151 - Fix a heap overflow bug that could occur when trying to pull
16152 data into the first chunk of a buffer, when that chunk had
16153 already had some data drained from it. Fixes CVE-2011-2778;
16154 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
16157 - Update to the December 6 2011 Maxmind GeoLite Country database.
16160 Changes in version 0.2.2.34 - 2011-10-26
16161 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
16162 can deanonymize Tor users. Everybody should upgrade.
16164 The attack relies on four components: 1) Clients reuse their TLS cert
16165 when talking to different relays, so relays can recognize a user by
16166 the identity key in her cert. 2) An attacker who knows the client's
16167 identity key can probe each guard relay to see if that identity key
16168 is connected to that guard relay right now. 3) A variety of active
16169 attacks in the literature (starting from "Low-Cost Traffic Analysis
16170 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
16171 discover the guard relays that a Tor user visiting the website is using.
16172 4) Clients typically pick three guards at random, so the set of guards
16173 for a given user could well be a unique fingerprint for her. This
16174 release fixes components #1 and #2, which is enough to block the attack;
16175 the other two remain as open research problems. Special thanks to
16176 "frosty_un" for reporting the issue to us!
16178 Clients should upgrade so they are no longer recognizable by the TLS
16179 certs they present. Relays should upgrade so they no longer allow a
16180 remote attacker to probe them to test whether unpatched clients are
16181 currently connected to them.
16183 This release also fixes several vulnerabilities that allow an attacker
16184 to enumerate bridge relays. Some bridge enumeration attacks still
16185 remain; see for example proposal 188.
16187 o Privacy/anonymity fixes (clients):
16188 - Clients and bridges no longer send TLS certificate chains on
16189 outgoing OR connections. Previously, each client or bridge would
16190 use the same cert chain for all outgoing OR connections until
16191 its IP address changes, which allowed any relay that the client
16192 or bridge contacted to determine which entry guards it is using.
16193 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16194 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16195 no longer considers that connection as suitable for satisfying a
16196 circuit EXTEND request. Now relays can protect clients from the
16197 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16198 - Directory authorities no longer assign the Guard flag to relays
16199 that haven't upgraded to the above "refuse EXTEND requests
16200 to client connections" fix. Now directory authorities can
16201 protect clients from the CVE-2011-2768 issue even if neither
16202 the clients nor the relays have upgraded yet. There's a new
16203 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
16204 to let us transition smoothly, else tomorrow there would be no
16207 o Privacy/anonymity fixes (bridge enumeration):
16208 - Bridge relays now do their directory fetches inside Tor TLS
16209 connections, like all the other clients do, rather than connecting
16210 directly to the DirPort like public relays do. Removes another
16211 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
16212 - Bridges relays now build circuits for themselves in a more similar
16213 way to how clients build them. Removes another avenue for
16214 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
16215 when bridges were introduced.
16216 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16217 that they initiated. Relays could distinguish incoming bridge
16218 connections from client connections, creating another avenue for
16219 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16220 Found by "frosty_un".
16223 - Fix a crash bug when changing node restrictions while a DNS lookup
16224 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
16226 - Don't launch a useless circuit after failing to use one of a
16227 hidden service's introduction points. Previously, we would
16228 launch a new introduction circuit, but not set the hidden service
16229 which that circuit was intended to connect to, so it would never
16230 actually be used. A different piece of code would then create a
16231 new introduction circuit correctly. Bug reported by katmagic and
16232 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
16235 - Change an integer overflow check in the OpenBSD_Malloc code so
16236 that GCC is less likely to eliminate it as impossible. Patch
16237 from Mansour Moufid. Fixes bug 4059.
16238 - When a hidden service turns an extra service-side introduction
16239 circuit into a general-purpose circuit, free the rend_data and
16240 intro_key fields first, so we won't leak memory if the circuit
16241 is cannibalized for use as another service-side introduction
16242 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
16243 - Bridges now skip DNS self-tests, to act a little more stealthily.
16244 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
16245 bridges. Patch by "warms0x".
16246 - Fix internal bug-checking logic that was supposed to catch
16247 failures in digest generation so that it will fail more robustly
16248 if we ask for a nonexistent algorithm. Found by Coverity Scan.
16249 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
16250 - Report any failure in init_keys() calls launched because our
16251 IP address has changed. Spotted by Coverity Scan. Bugfix on
16252 0.1.1.4-alpha; fixes CID 484.
16254 o Minor bugfixes (log messages and documentation):
16255 - Remove a confusing dollar sign from the example fingerprint in the
16256 man page, and also make the example fingerprint a valid one. Fixes
16257 bug 4309; bugfix on 0.2.1.3-alpha.
16258 - The next version of Windows will be called Windows 8, and it has
16259 a major version of 6, minor version of 2. Correctly identify that
16260 version instead of calling it "Very recent version". Resolves
16261 ticket 4153; reported by funkstar.
16262 - Downgrade log messages about circuit timeout calibration from
16263 "notice" to "info": they don't require or suggest any human
16264 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
16265 bugfix on 0.2.2.14-alpha.
16268 - Turn on directory request statistics by default and include them in
16269 extra-info descriptors. Don't break if we have no GeoIP database.
16270 Backported from 0.2.3.1-alpha; implements ticket 3951.
16271 - Update to the October 4 2011 Maxmind GeoLite Country database.
16274 Changes in version 0.2.1.31 - 2011-10-26
16275 Tor 0.2.1.31 backports important security and privacy fixes for
16276 oldstable. This release is intended only for package maintainers and
16277 others who cannot use the 0.2.2 stable series. All others should be
16278 using Tor 0.2.2.x or newer.
16280 o Security fixes (also included in 0.2.2.x):
16281 - Replace all potentially sensitive memory comparison operations
16282 with versions whose runtime does not depend on the data being
16283 compared. This will help resist a class of attacks where an
16284 adversary can use variations in timing information to learn
16285 sensitive data. Fix for one case of bug 3122. (Safe memcmp
16286 implementation by Robert Ransom based partially on code by DJB.)
16287 - Fix an assert in parsing router descriptors containing IPv6
16288 addresses. This one took down the directory authorities when
16289 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16291 o Privacy/anonymity fixes (also included in 0.2.2.x):
16292 - Clients and bridges no longer send TLS certificate chains on
16293 outgoing OR connections. Previously, each client or bridge would
16294 use the same cert chain for all outgoing OR connections until
16295 its IP address changes, which allowed any relay that the client
16296 or bridge contacted to determine which entry guards it is using.
16297 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
16298 - If a relay receives a CREATE_FAST cell on a TLS connection, it
16299 no longer considers that connection as suitable for satisfying a
16300 circuit EXTEND request. Now relays can protect clients from the
16301 CVE-2011-2768 issue even if the clients haven't upgraded yet.
16302 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
16303 that they initiated. Relays could distinguish incoming bridge
16304 connections from client connections, creating another avenue for
16305 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
16306 Found by "frosty_un".
16307 - When receiving a hidden service descriptor, check that it is for
16308 the hidden service we wanted. Previously, Tor would store any
16309 hidden service descriptors that a directory gave it, whether it
16310 wanted them or not. This wouldn't have let an attacker impersonate
16311 a hidden service, but it did let directories pre-seed a client
16312 with descriptors that it didn't want. Bugfix on 0.0.6.
16313 - Avoid linkability based on cached hidden service descriptors: forget
16314 all hidden service descriptors cached as a client when processing a
16315 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
16316 - Make the bridge directory authority refuse to answer directory
16317 requests for "all" descriptors. It used to include bridge
16318 descriptors in its answer, which was a major information leak.
16319 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16320 - Don't attach new streams to old rendezvous circuits after SIGNAL
16321 NEWNYM. Previously, we would keep using an existing rendezvous
16322 circuit if it remained open (i.e. if it were kept open by a
16323 long-lived stream, or if a new stream were attached to it before
16324 Tor could notice that it was old and no longer in use). Bugfix on
16325 0.1.1.15-rc; fixes bug 3375.
16327 o Minor bugfixes (also included in 0.2.2.x):
16328 - When we restart our relay, we might get a successful connection
16329 from the outside before we've started our reachability tests,
16330 triggering a warning: "ORPort found reachable, but I have no
16331 routerinfo yet. Failing to inform controller of success." This
16332 bug was harmless unless Tor is running under a controller
16333 like Vidalia, in which case the controller would never get a
16334 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
16336 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
16337 enabled. Fixes bug 1526.
16338 - Remove undocumented option "-F" from tor-resolve: it hasn't done
16339 anything since 0.2.1.16-rc.
16340 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
16341 None of the cases where we did this before were wrong, but by making
16342 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
16343 - Fix a rare crash bug that could occur when a client was configured
16344 with a large number of bridges. Fixes bug 2629; bugfix on
16345 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16346 - Correct the warning displayed when a rendezvous descriptor exceeds
16347 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
16349 - Fix an uncommon assertion failure when running with DNSPort under
16350 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
16351 - When warning about missing zlib development packages during compile,
16352 give the correct package names. Bugfix on 0.2.0.1-alpha.
16353 - Require that introduction point keys and onion keys have public
16354 exponent 65537. Bugfix on 0.2.0.10-alpha.
16355 - Do not crash when our configuration file becomes unreadable, for
16356 example due to a permissions change, between when we start up
16357 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
16359 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
16361 - Always NUL-terminate the sun_path field of a sockaddr_un before
16362 passing it to the kernel. (Not a security issue: kernels are
16363 smart enough to reject bad sockaddr_uns.) Found by Coverity;
16364 CID #428. Bugfix on Tor 0.2.0.3-alpha.
16365 - Don't stack-allocate the list of supplementary GIDs when we're
16366 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
16367 could take up to 256K, which is way too much stack. Found by
16368 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
16370 o Minor bugfixes (only in 0.2.1.x):
16371 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
16372 rely on them. Bugfix on 0.2.1.30.
16373 - Use git revisions instead of svn revisions when generating our
16374 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
16376 o Minor features (also included in 0.2.2.x):
16377 - Adjust the expiration time on our SSL session certificates to
16378 better match SSL certs seen in the wild. Resolves ticket 4014.
16379 - Allow nameservers with IPv6 address. Resolves bug 2574.
16380 - Update to the October 4 2011 Maxmind GeoLite Country database.
16383 Changes in version 0.2.2.33 - 2011-09-13
16384 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
16385 TLS handshake that makes relays and bridges that run this new version
16386 reachable from Iran again.
16389 - Avoid an assertion failure when reloading a configuration with
16390 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
16391 3923; bugfix on 0.2.2.25-alpha.
16393 o Minor features (security):
16394 - Check for replays of the public-key encrypted portion of an
16395 INTRODUCE1 cell, in addition to the current check for replays of
16396 the g^x value. This prevents a possible class of active attacks
16397 by an attacker who controls both an introduction point and a
16398 rendezvous point, and who uses the malleability of AES-CTR to
16399 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
16400 that these attacks are infeasible (requiring the attacker to send
16401 on the order of zettabytes of altered cells in a short interval),
16402 but we'd rather block them off in case there are any classes of
16403 this attack that we missed. Reported by Willem Pinckaers.
16406 - Adjust the expiration time on our SSL session certificates to
16407 better match SSL certs seen in the wild. Resolves ticket 4014.
16408 - Change the default required uptime for a relay to be accepted as
16409 a HSDir (hidden service directory) from 24 hours to 25 hours.
16410 Improves on 0.2.0.10-alpha; resolves ticket 2649.
16411 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
16412 authorities to abstain from voting on assignment of the HSDir
16413 consensus flag. Related to bug 2649.
16414 - Update to the September 6 2011 Maxmind GeoLite Country database.
16416 o Minor bugfixes (documentation and log messages):
16417 - Correct the man page to explain that HashedControlPassword and
16418 CookieAuthentication can both be set, in which case either method
16419 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
16420 when we decided to allow these config options to both be set. Issue
16421 raised by bug 3898.
16422 - Demote the 'replay detected' log message emitted when a hidden
16423 service receives the same Diffie-Hellman public key in two different
16424 INTRODUCE2 cells to info level. A normal Tor client can cause that
16425 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
16426 fixes part of bug 2442.
16427 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
16428 level. There is nothing that a hidden service's operator can do
16429 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
16431 - Clarify a log message specifying the characters permitted in
16432 HiddenServiceAuthorizeClient client names. Previously, the log
16433 message said that "[A-Za-z0-9+-_]" were permitted; that could have
16434 given the impression that every ASCII character between "+" and "_"
16435 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
16438 - Provide a substitute implementation of lround() for MSVC, which
16439 apparently lacks it. Patch from Gisle Vanem.
16440 - Clean up some code issues that prevented Tor from building on older
16441 BSDs. Fixes bug 3894; reported by "grarpamp".
16442 - Search for a platform-specific version of "ar" when cross-compiling.
16443 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
16446 Changes in version 0.2.2.32 - 2011-08-27
16447 The Tor 0.2.2 release series is dedicated to the memory of Andreas
16448 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
16449 a founder of the PETS community, a leader in our field, a mentor,
16450 and a friend. He left us with these words: "I had the possibility
16451 to contribute to this world that is not as it should be. I hope I
16452 could help in some areas to make the world a better place, and that
16453 I could also encourage other people to be engaged in improving the
16454 world. Please, stay engaged. This world needs you, your love, your
16455 initiative -- now I cannot be part of that anymore."
16457 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
16458 ready. More than two years in the making, this release features improved
16459 client performance and hidden service reliability, better compatibility
16460 for Android, correct behavior for bridges that listen on more than
16461 one address, more extensible and flexible directory object handling,
16462 better reporting of network statistics, improved code security, and
16463 many many other features and bugfixes.
16465 o Major features (client performance):
16466 - When choosing which cells to relay first, relays now favor circuits
16467 that have been quiet recently, to provide lower latency for
16468 low-volume circuits. By default, relays enable or disable this
16469 feature based on a setting in the consensus. They can override
16470 this default by using the new "CircuitPriorityHalflife" config
16471 option. Design and code by Ian Goldberg, Can Tang, and Chris
16473 - Directory authorities now compute consensus weightings that instruct
16474 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
16475 and no flag. Clients use these weightings to distribute network load
16476 more evenly across these different relay types. The weightings are
16477 in the consensus so we can change them globally in the future. Extra
16478 thanks to "outofwords" for finding some nasty security bugs in
16479 the first implementation of this feature.
16481 o Major features (client performance, circuit build timeout):
16482 - Tor now tracks how long it takes to build client-side circuits
16483 over time, and adapts its timeout to local network performance.
16484 Since a circuit that takes a long time to build will also provide
16485 bad performance, we get significant latency improvements by
16486 discarding the slowest 20% of circuits. Specifically, Tor creates
16487 circuits more aggressively than usual until it has enough data
16488 points for a good timeout estimate. Implements proposal 151.
16489 - Circuit build timeout constants can be controlled by consensus
16490 parameters. We set good defaults for these parameters based on
16491 experimentation on broadband and simulated high-latency links.
16492 - Circuit build time learning can be disabled via consensus parameter
16493 or by the client via a LearnCircuitBuildTimeout config option. We
16494 also automatically disable circuit build time calculation if either
16495 AuthoritativeDirectory is set, or if we fail to write our state
16496 file. Implements ticket 1296.
16498 o Major features (relays use their capacity better):
16499 - Set SO_REUSEADDR socket option on all sockets, not just
16500 listeners. This should help busy exit nodes avoid running out of
16501 useable ports just because all the ports have been used in the
16502 near past. Resolves issue 2850.
16503 - Relays now save observed peak bandwidth throughput rates to their
16504 state file (along with total usage, which was already saved),
16505 so that they can determine their correct estimated bandwidth on
16506 restart. Resolves bug 1863, where Tor relays would reset their
16507 estimated bandwidth to 0 after restarting.
16508 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
16509 should give us approximately 40-50% more Guard-flagged nodes,
16510 improving the anonymity the Tor network can provide and also
16511 decreasing the dropoff in throughput that relays experience when
16512 they first get the Guard flag.
16513 - Directory authorities now take changes in router IP address and
16514 ORPort into account when determining router stability. Previously,
16515 if a router changed its IP or ORPort, the authorities would not
16516 treat it as having any downtime for the purposes of stability
16517 calculation, whereas clients would experience downtime since the
16518 change would take a while to propagate to them. Resolves issue 1035.
16519 - New AccelName and AccelDir options add support for dynamic OpenSSL
16520 hardware crypto acceleration engines.
16522 o Major features (relays control their load better):
16523 - Exit relays now try harder to block exit attempts from unknown
16524 relays, to make it harder for people to use them as one-hop proxies
16525 a la tortunnel. Controlled by the refuseunknownexits consensus
16526 parameter (currently enabled), or you can override it on your
16527 relay with the RefuseUnknownExits torrc option. Resolves bug 1751;
16528 based on a variant of proposal 163.
16529 - Add separate per-conn write limiting to go with the per-conn read
16530 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
16531 but never per-conn write limits.
16532 - New consensus params "bwconnrate" and "bwconnburst" to let us
16533 rate-limit client connections as they enter the network. It's
16534 controlled in the consensus so we can turn it on and off for
16535 experiments. It's starting out off. Based on proposal 163.
16537 o Major features (controllers):
16538 - Export GeoIP information on bridge usage to controllers even if we
16539 have not yet been running for 24 hours. Now Vidalia bridge operators
16540 can get more accurate and immediate feedback about their
16541 contributions to the network.
16542 - Add an __OwningControllerProcess configuration option and a
16543 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
16544 that when it exits, Tor will shut down. Implements feature 3049.
16546 o Major features (directory authorities):
16547 - Directory authorities now create, vote on, and serve multiple
16548 parallel formats of directory data as part of their voting process.
16549 Partially implements Proposal 162: "Publish the consensus in
16551 - Directory authorities now agree on and publish small summaries
16552 of router information that clients can use in place of regular
16553 server descriptors. This transition will allow Tor 0.2.3 clients
16554 to use far less bandwidth for downloading information about the
16555 network. Begins the implementation of Proposal 158: "Clients
16556 download consensus + microdescriptors".
16557 - The directory voting system is now extensible to use multiple hash
16558 algorithms for signatures and resource selection. Newer formats
16559 are signed with SHA256, with a possibility for moving to a better
16560 hash algorithm in the future.
16561 - Directory authorities can now vote on arbitrary integer values as
16562 part of the consensus process. This is designed to help set
16563 network-wide parameters. Implements proposal 167.
16565 o Major features and bugfixes (node selection):
16566 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
16567 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and Strict*Nodes
16568 options. Previously, we had been ambiguous in describing what
16569 counted as an "exit" node, and what operations exactly "StrictNodes
16570 0" would permit. This created confusion when people saw nodes built
16571 through unexpected circuits, and made it hard to tell real bugs from
16572 surprises. Now the intended behavior is:
16573 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
16574 a node that delivers user traffic outside the Tor network.
16575 . "Entry", in the context of EntryNodes, means a node used as the
16576 first hop of a multihop circuit. It doesn't include direct
16577 connections to directory servers.
16578 . "ExcludeNodes" applies to all nodes.
16579 . "StrictNodes" changes the behavior of ExcludeNodes only. When
16580 StrictNodes is set, Tor should avoid all nodes listed in
16581 ExcludeNodes, even when it will make user requests fail. When
16582 StrictNodes is *not* set, then Tor should follow ExcludeNodes
16583 whenever it can, except when it must use an excluded node to
16584 perform self-tests, connect to a hidden service, provide a
16585 hidden service, fulfill a .exit request, upload directory
16586 information, or fetch directory information.
16587 Collectively, the changes to implement the behavior fix bug 1090.
16588 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
16589 change during a config reload, mark and discard all our origin
16590 circuits. This fix should address edge cases where we change the
16591 config options and but then choose a circuit that we created before
16593 - Make EntryNodes config option much more aggressive even when
16594 StrictNodes is not set. Before it would prepend your requested
16595 entrynodes to your list of guard nodes, but feel free to use others
16596 after that. Now it chooses only from your EntryNodes if any of
16597 those are available, and only falls back to others if a) they're
16598 all down and b) StrictNodes is not set.
16599 - Now we refresh your entry guards from EntryNodes at each consensus
16600 fetch -- rather than just at startup and then they slowly rot as
16601 the network changes.
16602 - Add support for the country code "{??}" in torrc options like
16603 ExcludeNodes, to indicate all routers of unknown country. Closes
16605 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
16606 a node is listed in both, it's treated as excluded.
16607 - ExcludeNodes now applies to directory nodes -- as a preference if
16608 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
16609 Don't exclude all the directory authorities and set StrictNodes to 1
16610 unless you really want your Tor to break.
16611 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
16612 - ExcludeExitNodes now overrides .exit requests.
16613 - We don't use bridges listed in ExcludeNodes.
16614 - When StrictNodes is 1:
16615 . We now apply ExcludeNodes to hidden service introduction points
16616 and to rendezvous points selected by hidden service users. This
16617 can make your hidden service less reliable: use it with caution!
16618 . If we have used ExcludeNodes on ourself, do not try relay
16619 reachability self-tests.
16620 . If we have excluded all the directory authorities, we will not
16621 even try to upload our descriptor if we're a relay.
16622 . Do not honor .exit requests to an excluded node.
16623 - When the set of permitted nodes changes, we now remove any mappings
16624 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
16626 - We never cannibalize a circuit that had excluded nodes on it, even
16627 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
16628 - Improve log messages related to excluded nodes.
16630 o Major features (misc):
16631 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
16632 to help Tor build correctly for Android phones.
16633 - The options SocksPort, ControlPort, and so on now all accept a
16634 value "auto" that opens a socket on an OS-selected port. A
16635 new ControlPortWriteToFile option tells Tor to write its
16636 actual control port or ports to a chosen file. If the option
16637 ControlPortFileGroupReadable is set, the file is created as
16638 group-readable. Now users can run two Tor clients on the same
16639 system without needing to manually mess with parameters. Resolves
16640 part of ticket 3076.
16641 - Tor now supports tunneling all of its outgoing connections over
16642 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
16643 configuration options. Code by Christopher Davis.
16645 o Code security improvements:
16646 - Replace all potentially sensitive memory comparison operations
16647 with versions whose runtime does not depend on the data being
16648 compared. This will help resist a class of attacks where an
16649 adversary can use variations in timing information to learn
16650 sensitive data. Fix for one case of bug 3122. (Safe memcmp
16651 implementation by Robert Ransom based partially on code by DJB.)
16652 - Enable Address Space Layout Randomization (ASLR) and Data Execution
16653 Prevention (DEP) by default on Windows to make it harder for
16654 attackers to exploit vulnerabilities. Patch from John Brooks.
16655 - New "--enable-gcc-hardening" ./configure flag (off by default)
16656 to turn on gcc compile time hardening options. It ensures
16657 that signed ints have defined behavior (-fwrapv), enables
16658 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
16659 with canaries (-fstack-protector-all), turns on ASLR protection if
16660 supported by the kernel (-fPIE, -pie), and adds additional security
16661 related warnings. Verified to work on Mac OS X and Debian Lenny.
16662 - New "--enable-linker-hardening" ./configure flag (off by default)
16663 to turn on ELF specific hardening features (relro, now). This does
16664 not work with Mac OS X or any other non-ELF binary format.
16665 - Always search the Windows system directory for system DLLs, and
16666 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
16667 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
16668 current and future memory pages via mlockall(). On supported
16669 platforms (modern Linux and probably BSD but not Windows or OS X),
16670 this should effectively disable any and all attempts to page out
16671 memory. This option requires that you start your Tor as root --
16672 if you use DisableAllSwap, please consider using the User option
16673 to properly reduce the privileges of your Tor.
16675 o Major bugfixes (crashes):
16676 - Fix crash bug on platforms where gmtime and localtime can return
16677 NULL. Windows 7 users were running into this one. Fixes part of bug
16678 2077. Bugfix on all versions of Tor. Found by boboper.
16679 - Introduce minimum/maximum values that clients will believe
16680 from the consensus. Now we'll have a better chance to avoid crashes
16681 or worse when a consensus param has a weird value.
16682 - Fix a rare crash bug that could occur when a client was configured
16683 with a large number of bridges. Fixes bug 2629; bugfix on
16684 0.2.1.2-alpha. Bugfix by trac user "shitlei".
16685 - Do not crash when our configuration file becomes unreadable, for
16686 example due to a permissions change, between when we start up
16687 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
16689 - If we're in the pathological case where there's no exit bandwidth
16690 but there is non-exit bandwidth, or no guard bandwidth but there
16691 is non-guard bandwidth, don't crash during path selection. Bugfix
16693 - Fix a crash bug when trying to initialize the evdns module in
16694 Libevent 2. Bugfix on 0.2.1.16-rc.
16696 o Major bugfixes (stability):
16697 - Fix an assert in parsing router descriptors containing IPv6
16698 addresses. This one took down the directory authorities when
16699 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
16700 - Fix an uncommon assertion failure when running with DNSPort under
16701 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
16702 - Treat an unset $HOME like an empty $HOME rather than triggering an
16703 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
16704 - More gracefully handle corrupt state files, removing asserts
16705 in favor of saving a backup and resetting state.
16706 - Instead of giving an assertion failure on an internal mismatch
16707 on estimated freelist size, just log a BUG warning and try later.
16708 Mitigates but does not fix bug 1125.
16709 - Fix an assert that got triggered when using the TestingTorNetwork
16710 configuration option and then issuing a GETINFO config-text control
16711 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
16712 - If the cached cert file is unparseable, warn but don't exit.
16714 o Privacy fixes (relays/bridges):
16715 - Don't list Windows capabilities in relay descriptors. We never made
16716 use of them, and maybe it's a bad idea to publish them. Bugfix
16718 - If the Nickname configuration option isn't given, Tor would pick a
16719 nickname based on the local hostname as the nickname for a relay.
16720 Because nicknames are not very important in today's Tor and the
16721 "Unnamed" nickname has been implemented, this is now problematic
16722 behavior: It leaks information about the hostname without being
16723 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
16724 introduced the Unnamed nickname. Reported by tagnaq.
16725 - Maintain separate TLS contexts and certificates for incoming and
16726 outgoing connections in bridge relays. Previously we would use the
16727 same TLS contexts and certs for incoming and outgoing connections.
16728 Bugfix on 0.2.0.3-alpha; addresses bug 988.
16729 - Maintain separate identity keys for incoming and outgoing TLS
16730 contexts in bridge relays. Previously we would use the same
16731 identity keys for incoming and outgoing TLS contexts. Bugfix on
16732 0.2.0.3-alpha; addresses the other half of bug 988.
16733 - Make the bridge directory authority refuse to answer directory
16734 requests for "all descriptors". It used to include bridge
16735 descriptors in its answer, which was a major information leak.
16736 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
16738 o Privacy fixes (clients):
16739 - When receiving a hidden service descriptor, check that it is for
16740 the hidden service we wanted. Previously, Tor would store any
16741 hidden service descriptors that a directory gave it, whether it
16742 wanted them or not. This wouldn't have let an attacker impersonate
16743 a hidden service, but it did let directories pre-seed a client
16744 with descriptors that it didn't want. Bugfix on 0.0.6.
16745 - Start the process of disabling ".exit" address notation, since it
16746 can be used for a variety of esoteric application-level attacks
16747 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
16749 - Reject attempts at the client side to open connections to private
16750 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
16751 a randomly chosen exit node. Attempts to do so are always
16752 ill-defined, generally prevented by exit policies, and usually
16753 in error. This will also help to detect loops in transparent
16754 proxy configurations. You can disable this feature by setting
16755 "ClientRejectInternalAddresses 0" in your torrc.
16756 - Log a notice when we get a new control connection. Now it's easier
16757 for security-conscious users to recognize when a local application
16758 is knocking on their controller door. Suggested by bug 1196.
16760 o Privacy fixes (newnym):
16761 - Avoid linkability based on cached hidden service descriptors: forget
16762 all hidden service descriptors cached as a client when processing a
16763 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
16764 - On SIGHUP, do not clear out all TrackHostExits mappings, client
16765 DNS cache entries, and virtual address mappings: that's what
16766 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
16767 - Don't attach new streams to old rendezvous circuits after SIGNAL
16768 NEWNYM. Previously, we would keep using an existing rendezvous
16769 circuit if it remained open (i.e. if it were kept open by a
16770 long-lived stream, or if a new stream were attached to it before
16771 Tor could notice that it was old and no longer in use). Bugfix on
16772 0.1.1.15-rc; fixes bug 3375.
16774 o Major bugfixes (relay bandwidth accounting):
16775 - Fix a bug that could break accounting on 64-bit systems with large
16776 time_t values, making them hibernate for impossibly long intervals.
16777 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
16778 - Fix a bug in bandwidth accounting that could make us use twice
16779 the intended bandwidth when our interval start changes due to
16780 daylight saving time. Now we tolerate skew in stored vs computed
16781 interval starts: if the start of the period changes by no more than
16782 50% of the period's duration, we remember bytes that we transferred
16783 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
16785 o Major bugfixes (bridges):
16786 - Bridges now use "reject *:*" as their default exit policy. Bugfix
16787 on 0.2.0.3-alpha. Fixes bug 1113.
16788 - If you configure your bridge with a known identity fingerprint,
16789 and the bridge authority is unreachable (as it is in at least
16790 one country now), fall back to directly requesting the descriptor
16791 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
16793 - Fix a bug where bridge users who configure the non-canonical
16794 address of a bridge automatically switch to its canonical
16795 address. If a bridge listens at more than one address, it
16796 should be able to advertise those addresses independently and
16797 any non-blocked addresses should continue to work. Bugfix on Tor
16798 0.2.0.3-alpha. Fixes bug 2510.
16799 - If you configure Tor to use bridge A, and then quit and
16800 configure Tor to use bridge B instead (or if you change Tor
16801 to use bridge B via the controller), it would happily continue
16802 to use bridge A if it's still reachable. While this behavior is
16803 a feature if your goal is connectivity, in some scenarios it's a
16804 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
16805 - When the controller configures a new bridge, don't wait 10 to 60
16806 seconds before trying to fetch its descriptor. Bugfix on
16807 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
16809 o Major bugfixes (directory authorities):
16810 - Many relays have been falling out of the consensus lately because
16811 not enough authorities know about their descriptor for them to get
16812 a majority of votes. When we deprecated the v2 directory protocol,
16813 we got rid of the only way that v3 authorities can hear from each
16814 other about other descriptors. Now authorities examine every v3
16815 vote for new descriptors, and fetch them from that authority. Bugfix
16817 - Authorities could be tricked into giving out the Exit flag to relays
16818 that didn't allow exiting to any ports. This bug could screw
16819 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
16820 1238. Bug discovered by Martin Kowalczyk.
16821 - If all authorities restart at once right before a consensus vote,
16822 nobody will vote about "Running", and clients will get a consensus
16823 with no usable relays. Instead, authorities refuse to build a
16824 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
16826 o Major bugfixes (stream-level fairness):
16827 - When receiving a circuit-level SENDME for a blocked circuit, try
16828 to package cells fairly from all the streams that had previously
16829 been blocked on that circuit. Previously, we had started with the
16830 oldest stream, and allowed each stream to potentially exhaust
16831 the circuit's package window. This gave older streams on any
16832 given circuit priority over newer ones. Fixes bug 1937. Detected
16833 originally by Camilo Viecco. This bug was introduced before the
16834 first Tor release, in svn commit r152: it is the new winner of
16835 the longest-lived bug prize.
16836 - Fix a stream fairness bug that would cause newer streams on a given
16837 circuit to get preference when reading bytes from the origin or
16838 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
16839 introduced before the first Tor release, in svn revision r152.
16840 - When the exit relay got a circuit-level sendme cell, it started
16841 reading on the exit streams, even if had 500 cells queued in the
16842 circuit queue already, so the circuit queue just grew and grew in
16843 some cases. We fix this by not re-enabling reading on receipt of a
16844 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
16845 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
16847 - Newly created streams were allowed to read cells onto circuits,
16848 even if the circuit's cell queue was blocked and waiting to drain.
16849 This created potential unfairness, as older streams would be
16850 blocked, but newer streams would gladly fill the queue completely.
16851 We add code to detect this situation and prevent any stream from
16852 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
16855 o Major bugfixes (hidden services):
16856 - Apply circuit timeouts to opened hidden-service-related circuits
16857 based on the correct start time. Previously, we would apply the
16858 circuit build timeout based on time since the circuit's creation;
16859 it was supposed to be applied based on time since the circuit
16860 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
16861 - Improve hidden service robustness: When we find that we have
16862 extended a hidden service's introduction circuit to a relay not
16863 listed as an introduction point in the HS descriptor we currently
16864 have, retry with an introduction point from the current
16865 descriptor. Previously we would just give up. Fixes bugs 1024 and
16866 1930; bugfix on 0.2.0.10-alpha.
16867 - Directory authorities now use data collected from their own
16868 uptime observations when choosing whether to assign the HSDir flag
16869 to relays, instead of trusting the uptime value the relay reports in
16870 its descriptor. This change helps prevent an attack where a small
16871 set of nodes with frequently-changing identity keys can blackhole
16872 a hidden service. (Only authorities need upgrade; others will be
16873 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
16874 - Stop assigning the HSDir flag to relays that disable their
16875 DirPort (and thus will refuse to answer directory requests). This
16876 fix should dramatically improve the reachability of hidden services:
16877 hidden services and hidden service clients pick six HSDir relays
16878 to store and retrieve the hidden service descriptor, and currently
16879 about half of the HSDir relays will refuse to work. Bugfix on
16880 0.2.0.10-alpha; fixes part of bug 1693.
16882 o Major bugfixes (misc):
16883 - Clients now stop trying to use an exit node associated with a given
16884 destination by TrackHostExits if they fail to reach that exit node.
16885 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
16886 - Fix a regression that caused Tor to rebind its ports if it receives
16887 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
16888 - Remove an extra pair of quotation marks around the error
16889 message in control-port STATUS_GENERAL BUG events. Bugfix on
16890 0.1.2.6-alpha; fixes bug 3732.
16892 o Minor features (relays):
16893 - Ensure that no empty [dirreq-](read|write)-history lines are added
16894 to an extrainfo document. Implements ticket 2497.
16895 - When bandwidth accounting is enabled, be more generous with how
16896 much bandwidth we'll use up before entering "soft hibernation".
16897 Previously, we'd refuse new connections and circuits once we'd
16898 used up 95% of our allotment. Now, we use up 95% of our allotment,
16899 AND make sure that we have no more than 500MB (or 3 hours of
16900 expected traffic, whichever is lower) remaining before we enter
16902 - Relays now log the reason for publishing a new relay descriptor,
16903 so we have a better chance of hunting down instances of bug 1810.
16904 Resolves ticket 3252.
16905 - Log a little more clearly about the times at which we're no longer
16906 accepting new connections (e.g. due to hibernating). Resolves
16908 - When AllowSingleHopExits is set, print a warning to explain to the
16909 relay operator why most clients are avoiding her relay.
16910 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
16911 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
16912 clients are already deprecated because of security bugs.
16914 o Minor features (network statistics):
16915 - Directory mirrors that set "DirReqStatistics 1" write statistics
16916 about directory requests to disk every 24 hours. As compared to the
16917 "--enable-geoip-stats" ./configure flag in 0.2.1.x, there are a few
16918 improvements: 1) stats are written to disk exactly every 24 hours;
16919 2) estimated shares of v2 and v3 requests are determined as mean
16920 values, not at the end of a measurement period; 3) unresolved
16921 requests are listed with country code '??'; 4) directories also
16922 measure download times.
16923 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
16924 number of exit streams and transferred bytes per port to disk every
16926 - Relays that set "CellStatistics 1" write statistics on how long
16927 cells spend in their circuit queues to disk every 24 hours.
16928 - Entry nodes that set "EntryStatistics 1" write statistics on the
16929 rough number and origins of connecting clients to disk every 24
16931 - Relays that write any of the above statistics to disk and set
16932 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
16933 their extra-info documents. Implements proposal 166.
16935 o Minor features (GeoIP and statistics):
16936 - Provide a log message stating which geoip file we're parsing
16937 instead of just stating that we're parsing the geoip file.
16938 Implements ticket 2432.
16939 - Make sure every relay writes a state file at least every 12 hours.
16940 Previously, a relay could go for weeks without writing its state
16941 file, and on a crash could lose its bandwidth history, capacity
16942 estimates, client country statistics, and so on. Addresses bug 3012.
16943 - Relays report the number of bytes spent on answering directory
16944 requests in extra-info descriptors similar to {read,write}-history.
16945 Implements enhancement 1790.
16946 - Report only the top 10 ports in exit-port stats in order not to
16947 exceed the maximum extra-info descriptor length of 50 KB. Implements
16949 - If writing the state file to disk fails, wait up to an hour before
16950 retrying again, rather than trying again each second. Fixes bug
16951 2346; bugfix on Tor 0.1.1.3-alpha.
16952 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
16953 when we switch from being a public relay to a bridge. Otherwise
16954 there will still be clients that see the relay in their consensus,
16955 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes
16957 - Update to the August 2 2011 Maxmind GeoLite Country database.
16959 o Minor features (clients):
16960 - When expiring circuits, use microsecond timers rather than
16961 one-second timers. This can avoid an unpleasant situation where a
16962 circuit is launched near the end of one second and expired right
16963 near the beginning of the next, and prevent fluctuations in circuit
16965 - If we've configured EntryNodes and our network goes away and/or all
16966 our entrynodes get marked down, optimistically retry them all when
16967 a new socks application request appears. Fixes bug 1882.
16968 - Always perform router selections using weighted relay bandwidth,
16969 even if we don't need a high capacity circuit at the time. Non-fast
16970 circuits now only differ from fast ones in that they can use relays
16971 not marked with the Fast flag. This "feature" could turn out to
16972 be a horrible bug; we should investigate more before it goes into
16974 - When we run out of directory information such that we can't build
16975 circuits, but then get enough that we can build circuits, log when
16976 we actually construct a circuit, so the user has a better chance of
16977 knowing what's going on. Fixes bug 1362.
16978 - Log SSL state transitions at debug level during handshake, and
16979 include SSL states in error messages. This may help debug future
16980 SSL handshake issues.
16982 o Minor features (directory authorities):
16983 - When a router changes IP address or port, authorities now launch
16984 a new reachability test for it. Implements ticket 1899.
16985 - Directory authorities now reject relays running any versions of
16986 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
16987 known bugs that keep RELAY_EARLY cells from working on rendezvous
16988 circuits. Followup to fix for bug 2081.
16989 - Directory authorities now reject relays running any version of Tor
16990 older than 0.2.0.26-rc. That version is the earliest that fetches
16991 current directory information correctly. Fixes bug 2156.
16992 - Directory authorities now do an immediate reachability check as soon
16993 as they hear about a new relay. This change should slightly reduce
16994 the time between setting up a relay and getting listed as running
16995 in the consensus. It should also improve the time between setting
16996 up a bridge and seeing use by bridge users.
16997 - Directory authorities no longer launch a TLS connection to every
16998 relay as they startup. Now that we have 2k+ descriptors cached,
16999 the resulting network hiccup is becoming a burden. Besides,
17000 authorities already avoid voting about Running for the first half
17001 hour of their uptime.
17002 - Directory authorities now log the source of a rejected POSTed v3
17003 networkstatus vote, so we can track failures better.
17004 - Backport code from 0.2.3.x that allows directory authorities to
17005 clean their microdescriptor caches. Needed to resolve bug 2230.
17007 o Minor features (hidden services):
17008 - Use computed circuit-build timeouts to decide when to launch
17009 parallel introduction circuits for hidden services. (Previously,
17010 we would retry after 15 seconds.)
17011 - Don't allow v0 hidden service authorities to act as clients.
17012 Required by fix for bug 3000.
17013 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
17014 by fix for bug 3000.
17015 - Make hidden services work better in private Tor networks by not
17016 requiring any uptime to join the hidden service descriptor
17017 DHT. Implements ticket 2088.
17018 - Log (at info level) when purging pieces of hidden-service-client
17019 state because of SIGNAL NEWNYM.
17021 o Minor features (controller interface):
17022 - New "GETINFO net/listeners/(type)" controller command to return
17023 a list of addresses and ports that are bound for listeners for a
17024 given connection type. This is useful when the user has configured
17025 "SocksPort auto" and the controller needs to know which port got
17026 chosen. Resolves another part of ticket 3076.
17027 - Have the controller interface give a more useful message than
17028 "Internal Error" in response to failed GETINFO requests.
17029 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
17030 event, to give information on the current rate of circuit timeouts
17031 over our stored history.
17032 - The 'EXTENDCIRCUIT' control port command can now be used with
17033 a circ id of 0 and no path. This feature will cause Tor to build
17034 a new 'fast' general purpose circuit using its own path selection
17036 - Added a BUILDTIMEOUT_SET controller event to describe changes
17037 to the circuit build timeout.
17038 - New controller command "getinfo config-text". It returns the
17039 contents that Tor would write if you send it a SAVECONF command,
17040 so the controller can write the file to disk itself.
17042 o Minor features (controller protocol):
17043 - Add a new ControlSocketsGroupWritable configuration option: when
17044 it is turned on, ControlSockets are group-writeable by the default
17045 group of the current user. Patch by Jérémy Bobbio; implements
17047 - Tor now refuses to create a ControlSocket in a directory that is
17048 world-readable (or group-readable if ControlSocketsGroupWritable
17049 is 0). This is necessary because some operating systems do not
17050 enforce permissions on an AF_UNIX sockets. Permissions on the
17051 directory holding the socket, however, seems to work everywhere.
17052 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
17053 not. This would lead to a cookie that is still not group readable.
17054 Closes bug 1843. Suggested by katmagic.
17055 - Future-proof the controller protocol a bit by ignoring keyword
17056 arguments we do not recognize.
17058 o Minor features (more useful logging):
17059 - Revise most log messages that refer to nodes by nickname to
17060 instead use the "$key=nickname at address" format. This should be
17061 more useful, especially since nicknames are less and less likely
17062 to be unique. Resolves ticket 3045.
17063 - When an HTTPS proxy reports "403 Forbidden", we now explain
17064 what it means rather than calling it an unexpected status code.
17065 Closes bug 2503. Patch from Michael Yakubovich.
17066 - Rate-limit a warning about failures to download v2 networkstatus
17067 documents. Resolves part of bug 1352.
17068 - Rate-limit the "your application is giving Tor only an IP address"
17069 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
17070 - Rate-limit "Failed to hand off onionskin" warnings.
17071 - When logging a rate-limited warning, we now mention how many messages
17072 got suppressed since the last warning.
17073 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
17074 2 no signature, 4 required" messages about consensus signatures
17075 easier to read, and make sure they get logged at the same severity
17076 as the messages explaining which keys are which. Fixes bug 1290.
17077 - Don't warn when we have a consensus that we can't verify because
17078 of missing certificates, unless those certificates are ones
17079 that we have been trying and failing to download. Fixes bug 1145.
17081 o Minor features (log domains):
17082 - Add documentation for configuring logging at different severities in
17083 different log domains. We've had this feature since 0.2.1.1-alpha,
17084 but for some reason it never made it into the manpage. Fixes
17086 - Make it simpler to specify "All log domains except for A and B".
17087 Previously you needed to say "[*,~A,~B]". Now you can just say
17089 - Add a "LogMessageDomains 1" option to include the domains of log
17090 messages along with the messages. Without this, there's no way
17091 to use log domains without reading the source or doing a lot
17093 - Add a new "Handshake" log domain for activities that happen
17094 during the TLS handshake.
17096 o Minor features (build process):
17097 - Make compilation with clang possible when using
17098 "--enable-gcc-warnings" by removing two warning options that clang
17099 hasn't implemented yet and by fixing a few warnings. Resolves
17101 - Detect platforms that brokenly use a signed size_t, and refuse to
17102 build there. Found and analyzed by doorss and rransom.
17103 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
17105 - Add support for statically linking zlib by specifying
17106 "--enable-static-zlib", to go with our support for statically
17107 linking openssl and libevent. Resolves bug 1358.
17108 - Instead of adding the svn revision to the Tor version string, report
17109 the git commit (when we're building from a git checkout).
17110 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
17112 - New --digests command-line switch to output the digests of the
17113 source files Tor was built with.
17114 - Generate our manpage and HTML documentation using Asciidoc. This
17115 change should make it easier to maintain the documentation, and
17116 produce nicer HTML. The build process fails if asciidoc cannot
17117 be found and building with asciidoc isn't disabled (via the
17118 "--disable-asciidoc" argument to ./configure. Skipping the manpage
17119 speeds up the build considerably.
17121 o Minor features (options / torrc):
17122 - Warn when the same option is provided more than once in a torrc
17123 file, on the command line, or in a single SETCONF statement, and
17124 the option is one that only accepts a single line. Closes bug 1384.
17125 - Warn when the user configures two HiddenServiceDir lines that point
17126 to the same directory. Bugfix on 0.0.6 (the version introducing
17127 HiddenServiceDir); fixes bug 3289.
17128 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
17129 do individual connection-level rate limiting of clients. The torrc
17130 config options with the same names trump the consensus params, if
17131 both are present. Replaces the old "bwconnrate" and "bwconnburst"
17132 consensus params which were broken from 0.2.2.7-alpha through
17133 0.2.2.14-alpha. Closes bug 1947.
17134 - New config option "WarnUnsafeSocks 0" disables the warning that
17135 occurs whenever Tor receives a socks handshake using a version of
17136 the socks protocol that can only provide an IP address (rather
17137 than a hostname). Setups that do DNS locally over Tor are fine,
17138 and we shouldn't spam the logs in that case.
17139 - New config option "CircuitStreamTimeout" to override our internal
17140 timeout schedule for how many seconds until we detach a stream from
17141 a circuit and try a new circuit. If your network is particularly
17142 slow, you might want to set this to a number like 60.
17143 - New options for SafeLogging to allow scrubbing only log messages
17144 generated while acting as a relay. Specify "SafeLogging relay" if
17145 you want to ensure that only messages known to originate from
17146 client use of the Tor process will be logged unsafely.
17147 - Time and memory units in the configuration file can now be set to
17148 fractional units. For example, "2.5 GB" is now a valid value for
17150 - Support line continuations in the torrc config file. If a line
17151 ends with a single backslash character, the newline is ignored, and
17152 the configuration value is treated as continuing on the next line.
17155 o Minor features (unit tests):
17156 - Revise our unit tests to use the "tinytest" framework, so we
17157 can run tests in their own processes, have smarter setup/teardown
17158 code, and so on. The unit test code has moved to its own
17159 subdirectory, and has been split into multiple modules.
17160 - Add a unit test for cross-platform directory-listing code.
17161 - Add some forgotten return value checks during unit tests. Found
17163 - Use GetTempDir to find the proper temporary directory location on
17164 Windows when generating temporary files for the unit tests. Patch
17167 o Minor features (misc):
17168 - The "torify" script now uses torsocks where available.
17169 - Make Libevent log messages get delivered to controllers later,
17170 and not from inside the Libevent log handler. This prevents unsafe
17171 reentrant Libevent calls while still letting the log messages
17173 - Certain Tor clients (such as those behind check.torproject.org) may
17174 want to fetch the consensus in an extra early manner. To enable this
17175 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
17176 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
17177 as only certain clients who must have this information sooner should
17179 - Expand homedirs passed to tor-checkkey. This should silence a
17180 coverity complaint about passing a user-supplied string into
17181 open() without checking it.
17182 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
17183 used on bridges, and it makes bridge scanning somewhat easier.
17184 - Create the /var/run/tor directory on startup on OpenSUSE if it is
17185 not already created. Patch from Andreas Stieger. Fixes bug 2573.
17187 o Minor bugfixes (relays):
17188 - When a relay decides that its DNS is too broken for it to serve
17189 as an exit server, it advertised itself as a non-exit, but
17190 continued to act as an exit. This could create accidental
17191 partitioning opportunities for users. Instead, if a relay is
17192 going to advertise reject *:* as its exit policy, it should
17193 really act with exit policy "reject *:*". Fixes bug 2366.
17194 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
17195 - Publish a router descriptor even if generating an extra-info
17196 descriptor fails. Previously we would not publish a router
17197 descriptor without an extra-info descriptor; this can cause fast
17198 exit relays collecting exit-port statistics to drop from the
17199 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
17200 - When we're trying to guess whether we know our IP address as
17201 a relay, we would log various ways that we failed to guess
17202 our address, but never log that we ended up guessing it
17203 successfully. Now add a log line to help confused and anxious
17204 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
17205 - For bandwidth accounting, calculate our expected bandwidth rate
17206 based on the time during which we were active and not in
17207 soft-hibernation during the last interval. Previously, we were
17208 also considering the time spent in soft-hibernation. If this
17209 was a long time, we would wind up underestimating our bandwidth
17210 by a lot, and skewing our wakeup time towards the start of the
17211 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
17212 - Demote a confusing TLS warning that relay operators might get when
17213 someone tries to talk to their ORPort. It is not the operator's
17214 fault, nor can they do anything about it. Fixes bug 1364; bugfix
17216 - Change "Application request when we're believed to be offline."
17217 notice to "Application request when we haven't used client
17218 functionality lately.", to clarify that it's not an error. Bugfix
17219 on 0.0.9.3; fixes bug 1222.
17221 o Minor bugfixes (bridges):
17222 - When a client starts or stops using bridges, never use a circuit
17223 that was built before the configuration change. This behavior could
17224 put at risk a user who uses bridges to ensure that her traffic
17225 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
17227 - Do not reset the bridge descriptor download status every time we
17228 re-parse our configuration or get a configuration change. Fixes
17229 bug 3019; bugfix on 0.2.0.3-alpha.
17230 - Users couldn't configure a regular relay to be their bridge. It
17231 didn't work because when Tor fetched the bridge descriptor, it found
17232 that it already had it, and didn't realize that the purpose of the
17233 descriptor had changed. Now we replace routers with a purpose other
17234 than bridge with bridge descriptors when fetching them. Bugfix on
17235 0.1.1.9-alpha. Fixes bug 1776.
17236 - In the special case where you configure a public exit relay as your
17237 bridge, Tor would be willing to use that exit relay as the last
17238 hop in your circuit as well. Now we fail that circuit instead.
17239 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
17241 o Minor bugfixes (clients):
17242 - We now ask the other side of a stream (the client or the exit)
17243 for more data on that stream when the amount of queued data on
17244 that stream dips low enough. Previously, we wouldn't ask the
17245 other side for more data until either it sent us more data (which
17246 it wasn't supposed to do if it had exhausted its window!) or we
17247 had completely flushed all our queued data. This flow control fix
17248 should improve throughput. Fixes bug 2756; bugfix on the earliest
17249 released versions of Tor (svn commit r152).
17250 - When a client finds that an origin circuit has run out of 16-bit
17251 stream IDs, we now mark it as unusable for new streams. Previously,
17252 we would try to close the entire circuit. Bugfix on 0.0.6.
17253 - Make it explicit that we don't cannibalize one-hop circuits. This
17254 happens in the wild, but doesn't turn out to be a problem because
17255 we fortunately don't use those circuits. Many thanks to outofwords
17256 for the initial analysis and to swissknife who confirmed that
17257 two-hop circuits are actually created.
17258 - Resolve an edge case in path weighting that could make us misweight
17259 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
17260 - Make the DNSPort option work with libevent 2.x. Don't alter the
17261 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
17263 o Minor bugfixes (directory authorities):
17264 - Make directory authorities more accurate at recording when
17265 relays that have failed several reachability tests became
17266 unreachable, so we can provide more accuracy at assigning Stable,
17267 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
17268 - Directory authorities are now more robust to hops back in time
17269 when calculating router stability. Previously, if a run of uptime
17270 or downtime appeared to be negative, the calculation could give
17271 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
17273 - Directory authorities will now attempt to download consensuses
17274 if their own efforts to make a live consensus have failed. This
17275 change means authorities that restart will fetch a valid
17276 consensus, and it means authorities that didn't agree with the
17277 current consensus will still fetch and serve it if it has enough
17278 signatures. Bugfix on 0.2.0.9-alpha; fixes bug 1300.
17279 - Never vote for a server as "Running" if we have a descriptor for
17280 it claiming to be hibernating, and that descriptor was published
17281 more recently than our last contact with the server. Bugfix on
17282 0.2.0.3-alpha; fixes bug 911.
17283 - Directory authorities no longer change their opinion of, or vote on,
17284 whether a router is Running, unless they have themselves been
17285 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
17288 o Minor bugfixes (hidden services):
17289 - Log malformed requests for rendezvous descriptors as protocol
17290 warnings, not warnings. Also, use a more informative log message
17291 in case someone sees it at log level warning without prior
17292 info-level messages. Fixes bug 2748; bugfix on 0.2.0.10-alpha.
17293 - Accept hidden service descriptors if we think we might be a hidden
17294 service directory, regardless of what our consensus says. This
17295 helps robustness, since clients and hidden services can sometimes
17296 have a more up-to-date view of the network consensus than we do,
17297 and if they think that the directory authorities list us a HSDir,
17298 we might actually be one. Related to bug 2732; bugfix on
17300 - Correct the warning displayed when a rendezvous descriptor exceeds
17301 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
17303 - Clients and hidden services now use HSDir-flagged relays for hidden
17304 service descriptor downloads and uploads even if the relays have no
17305 DirPort set and the client has disabled TunnelDirConns. This will
17306 eventually allow us to give the HSDir flag to relays with no
17307 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
17308 - Only limit the lengths of single HS descriptors, even when multiple
17309 HS descriptors are published to an HSDir relay in a single POST
17310 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
17312 o Minor bugfixes (controllers):
17313 - Allow GETINFO fingerprint to return a fingerprint even when
17314 we have not yet built a router descriptor. Fixes bug 3577;
17315 bugfix on 0.2.0.1-alpha.
17316 - Send a SUCCEEDED stream event to the controller when a reverse
17317 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
17318 discovered by katmagic.
17319 - Remove a trailing asterisk from "exit-policy/default" in the
17320 output of the control port command "GETINFO info/names". Bugfix
17322 - Make the SIGNAL DUMP controller command work on FreeBSD. Fixes bug
17323 2917. Bugfix on 0.1.1.1-alpha.
17324 - When we restart our relay, we might get a successful connection
17325 from the outside before we've started our reachability tests,
17326 triggering a warning: "ORPort found reachable, but I have no
17327 routerinfo yet. Failing to inform controller of success." This
17328 bug was harmless unless Tor is running under a controller
17329 like Vidalia, in which case the controller would never get a
17330 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
17332 - When a controller changes TrackHostExits, remove mappings for
17333 hosts that should no longer have their exits tracked. Bugfix on
17335 - When a controller changes VirtualAddrNetwork, remove any mappings
17336 for hosts that were automapped to the old network. Bugfix on
17338 - When a controller changes one of the AutomapHosts* options, remove
17339 any mappings for hosts that should no longer be automapped. Bugfix
17341 - Fix an off-by-one error in calculating some controller command
17342 argument lengths. Fortunately, this mistake is harmless since
17343 the controller code does redundant NUL termination too. Found by
17344 boboper. Bugfix on 0.1.1.1-alpha.
17345 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
17346 would return "551 Internal error" rather than "552 Unrecognized key
17347 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
17348 - Don't spam the controller with events when we have no file
17349 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
17350 for log messages was already solved from bug 748.)
17351 - Emit a GUARD DROPPED controller event for a case we missed.
17352 - Ensure DNS requests launched by "RESOLVE" commands from the
17353 controller respect the __LeaveStreamsUnattached setconf options. The
17354 same goes for requests launched via DNSPort or transparent
17355 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
17357 o Minor bugfixes (config options):
17358 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
17359 Change the limit to 512 characters by removing base64 newlines.
17360 Fixes bug 2752. Fix by Michael Yakubovich.
17361 - Complain if PublishServerDescriptor is given multiple arguments that
17362 include 0 or 1. This configuration will be rejected in the future.
17363 Bugfix on 0.2.0.1-alpha; closes bug 1107.
17364 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
17365 Bugfix on 0.2.0.13-alpha; closes bug 928.
17367 o Minor bugfixes (log subsystem fixes):
17368 - When unable to format an address as a string, report its value
17369 as "???" rather than reusing the last formatted address. Bugfix
17371 - Be more consistent in our treatment of file system paths. "~" should
17372 get expanded to the user's home directory in the Log config option.
17373 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
17374 feature for the -f and --DataDirectory options.
17376 o Minor bugfixes (memory management):
17377 - Don't stack-allocate the list of supplementary GIDs when we're
17378 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
17379 could take up to 256K, which is way too much stack. Found by
17380 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
17381 - Save a couple bytes in memory allocation every time we escape
17382 certain characters in a string. Patch from Florian Zumbiehl.
17384 o Minor bugfixes (protocol correctness):
17385 - When checking for 1024-bit keys, check for 1024 bits, not 128
17386 bytes. This allows Tor to correctly discard keys of length 1017
17387 through 1023. Bugfix on 0.0.9pre5.
17388 - Require that introduction point keys and onion handshake keys
17389 have a public exponent of 65537. Starts to fix bug 3207; bugfix
17391 - Handle SOCKS messages longer than 128 bytes long correctly, rather
17392 than waiting forever for them to finish. Fixes bug 2330; bugfix
17393 on 0.2.0.16-alpha. Found by doorss.
17394 - Never relay a cell for a circuit we have already destroyed.
17395 Between marking a circuit as closeable and finally closing it,
17396 it may have been possible for a few queued cells to get relayed,
17397 even though they would have been immediately dropped by the next
17398 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
17399 - Never queue a cell for a circuit that's already been marked
17401 - Fix a spec conformance issue: the network-status-version token
17402 must be the first token in a v3 consensus or vote. Discovered by
17403 "parakeep". Bugfix on 0.2.0.3-alpha.
17404 - A networkstatus vote must contain exactly one signature. Spec
17405 conformance issue. Bugfix on 0.2.0.3-alpha.
17406 - When asked about a DNS record type we don't support via a
17407 client DNSPort, reply with NOTIMPL rather than an empty
17408 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
17409 - Make more fields in the controller protocol case-insensitive, since
17410 control-spec.txt said they were.
17412 o Minor bugfixes (log messages):
17413 - Fix a log message that said "bits" while displaying a value in
17414 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
17416 - Downgrade "no current certificates known for authority" message from
17417 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
17418 - Correctly describe errors that occur when generating a TLS object.
17419 Previously we would attribute them to a failure while generating a
17420 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
17422 - Fix an instance where a Tor directory mirror might accidentally
17423 log the IP address of a misbehaving Tor client. Bugfix on
17425 - Stop logging at severity 'warn' when some other Tor client tries
17426 to establish a circuit with us using weak DH keys. It's a protocol
17427 violation, but that doesn't mean ordinary users need to hear about
17428 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
17429 - If your relay can't keep up with the number of incoming create
17430 cells, it would log one warning per failure into your logs. Limit
17431 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
17433 o Minor bugfixes (build fixes):
17434 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
17435 - When warning about missing zlib development packages during compile,
17436 give the correct package names. Bugfix on 0.2.0.1-alpha.
17437 - Fix warnings that newer versions of autoconf produce during
17438 ./autogen.sh. These warnings appear to be harmless in our case,
17439 but they were extremely verbose. Fixes bug 2020.
17440 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
17443 o Minor bugfixes (portability):
17444 - Write several files in text mode, on OSes that distinguish text
17445 mode from binary mode (namely, Windows). These files are:
17446 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
17447 that collect those statistics; 'client_keys' and 'hostname' for
17448 hidden services that use authentication; and (in the tor-gencert
17449 utility) newly generated identity and signing keys. Previously,
17450 we wouldn't specify text mode or binary mode, leading to an
17451 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
17452 the DirRecordUsageByCountry option which would have triggered
17453 the assertion failure was added), although this assertion failure
17454 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
17455 - Selectively disable deprecation warnings on OS X because Lion
17456 started deprecating the shipped copy of openssl. Fixes bug 3643.
17457 - Use a wide type to hold sockets when built for 64-bit Windows.
17459 - Fix an issue that prevented static linking of libevent on
17460 some platforms (notably Linux). Fixes bug 2698; bugfix on 0.2.1.23,
17461 where we introduced the "--with-static-libevent" configure option.
17462 - Fix a bug with our locking implementation on Windows that couldn't
17463 correctly detect when a file was already locked. Fixes bug 2504,
17464 bugfix on 0.2.1.6-alpha.
17465 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
17467 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
17468 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
17471 o Minor bugfixes (code correctness):
17472 - Always NUL-terminate the sun_path field of a sockaddr_un before
17473 passing it to the kernel. (Not a security issue: kernels are
17474 smart enough to reject bad sockaddr_uns.) Found by Coverity;
17475 CID #428. Bugfix on Tor 0.2.0.3-alpha.
17476 - Make connection_printf_to_buf()'s behavior sane. Its callers
17477 expect it to emit a CRLF iff the format string ends with CRLF;
17478 it actually emitted a CRLF iff (a) the format string ended with
17479 CRLF or (b) the resulting string was over 1023 characters long or
17480 (c) the format string did not end with CRLF *and* the resulting
17481 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
17482 fixes part of bug 3407.
17483 - Make send_control_event_impl()'s behavior sane. Its callers
17484 expect it to always emit a CRLF at the end of the string; it
17485 might have emitted extra control characters as well. Bugfix on
17486 0.1.1.9-alpha; fixes another part of bug 3407.
17487 - Make crypto_rand_int() check the value of its input correctly.
17488 Previously, it accepted values up to UINT_MAX, but could return a
17489 negative number if given a value above INT_MAX+1. Found by George
17490 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
17491 - Fix a potential null-pointer dereference while computing a
17492 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
17494 - If we fail to compute the identity digest of a v3 legacy keypair,
17495 warn, and don't use a buffer-full of junk instead. Bugfix on
17496 0.2.1.1-alpha; fixes bug 3106.
17497 - Resolve an untriggerable issue in smartlist_string_num_isin(),
17498 where if the function had ever in the future been used to check
17499 for the presence of a too-large number, it would have given an
17500 incorrect result. (Fortunately, we only used it for 16-bit
17501 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
17502 - Be more careful about reporting the correct error from a failed
17503 connect() system call. Under some circumstances, it was possible to
17504 look at an incorrect value for errno when sending the end reason.
17505 Bugfix on 0.1.0.1-rc.
17506 - Correctly handle an "impossible" overflow cases in connection byte
17507 counting, where we write or read more than 4GB on an edge connection
17508 in a single second. Bugfix on 0.1.2.8-beta.
17509 - Avoid a double mark-for-free warning when failing to attach a
17510 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
17512 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
17513 found by "cypherpunks". This bug was introduced before the first
17514 Tor release, in svn commit r110.
17515 - Fix a bug in bandwidth history state parsing that could have been
17516 triggered if a future version of Tor ever changed the timing
17517 granularity at which bandwidth history is measured. Bugfix on
17518 Tor 0.1.1.11-alpha.
17519 - Add assertions to check for overflow in arguments to
17520 base32_encode() and base32_decode(); fix a signed-unsigned
17521 comparison there too. These bugs are not actually reachable in Tor,
17522 but it's good to prevent future errors too. Found by doorss.
17523 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
17525 - Set target port in get_interface_address6() correctly. Bugfix
17526 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
17527 - Fix an impossible-to-actually-trigger buffer overflow in relay
17528 descriptor generation. Bugfix on 0.1.0.15.
17529 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
17531 o Minor bugfixes (code improvements):
17532 - After we free an internal connection structure, overwrite it
17533 with a different memory value than we use for overwriting a freed
17534 internal circuit structure. Should help with debugging. Suggested
17536 - If OpenSSL fails to make a duplicate of a private or public key, log
17537 an error message and try to exit cleanly. May help with debugging
17538 if bug 1209 ever remanifests.
17539 - Some options used different conventions for uppercasing of acronyms
17540 when comparing manpage and source. Fix those in favor of the
17541 manpage, as it makes sense to capitalize acronyms.
17542 - Take a first step towards making or.h smaller by splitting out
17543 function definitions for all source files in src/or/. Leave
17544 structures and defines in or.h for now.
17545 - Remove a few dead assignments during router parsing. Found by
17547 - Don't use 1-bit wide signed bit fields. Found by coverity.
17548 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
17549 None of the cases where we did this before were wrong, but by making
17550 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
17551 - The memarea code now uses a sentinel value at the end of each area
17552 to make sure nothing writes beyond the end of an area. This might
17553 help debug some conceivable causes of bug 930.
17554 - Always treat failure to allocate an RSA key as an unrecoverable
17556 - Add some more defensive programming for architectures that can't
17557 handle unaligned integer accesses. We don't know of any actual bugs
17558 right now, but that's the best time to fix them. Fixes bug 1943.
17560 o Minor bugfixes (misc):
17561 - Fix a rare bug in rend_fn unit tests: we would fail a test when
17562 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
17563 on 0.2.0.10-alpha; fixes bug 1808.
17564 - Where available, use Libevent 2.0's periodic timers so that our
17565 once-per-second cleanup code gets called even more closely to
17566 once per second than it would otherwise. Fixes bug 943.
17567 - Ignore OutboundBindAddress when connecting to localhost.
17568 Connections to localhost need to come _from_ localhost, or else
17569 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
17571 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
17573 - If any of the v3 certs we download are unparseable, we should
17574 actually notice the failure so we don't retry indefinitely. Bugfix
17575 on 0.2.0.x; reported by "rotator".
17576 - When Tor fails to parse a descriptor of any kind, dump it to disk.
17577 Might help diagnosing bug 1051.
17578 - Make our 'torify' script more portable; if we have only one of
17579 'torsocks' or 'tsocks' installed, don't complain to the user;
17580 and explain our warning about tsocks better.
17581 - Fix some urls in the exit notice file and make it XHTML1.1 strict
17582 compliant. Based on a patch from Christian Kujau.
17584 o Documentation changes:
17585 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
17586 - Resolve all doxygen warnings except those for missing documentation.
17588 - Add doxygen documentation for more functions, fields, and types.
17589 - Convert the HACKING file to asciidoc, and add a few new sections
17590 to it, explaining how we use Git, how we make changelogs, and
17591 what should go in a patch.
17592 - Document the default socks host and port (127.0.0.1:9050) for
17594 - Removed some unnecessary files from the source distribution. The
17595 AUTHORS file has now been merged into the people page on the
17596 website. The roadmaps and design doc can now be found in the
17597 projects directory in svn.
17599 o Deprecated and removed features (config):
17600 - Remove the torrc.complete file. It hasn't been kept up to date
17601 and users will have better luck checking out the manpage.
17602 - Remove the HSAuthorityRecordStats option that version 0 hidden
17603 service authorities could use to track statistics of overall v0
17604 hidden service usage.
17605 - Remove the obsolete "NoPublish" option; it has been flagged
17606 as obsolete and has produced a warning since 0.1.1.18-rc.
17607 - Caches no longer download and serve v2 networkstatus documents
17608 unless FetchV2Networkstatus flag is set: these documents haven't
17609 haven't been used by clients or relays since 0.2.0.x. Resolves
17612 o Deprecated and removed features (controller):
17613 - The controller no longer accepts the old obsolete "addr-mappings/"
17614 or "unregistered-servers-" GETINFO values.
17615 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
17616 always on; using them is necessary for correct forward-compatible
17619 o Deprecated and removed features (misc):
17620 - Hidden services no longer publish version 0 descriptors, and clients
17621 do not request or use version 0 descriptors. However, the old hidden
17622 service authorities still accept and serve version 0 descriptors
17623 when contacted by older hidden services/clients.
17624 - Remove undocumented option "-F" from tor-resolve: it hasn't done
17625 anything since 0.2.1.16-rc.
17626 - Remove everything related to building the expert bundle for OS X.
17627 It has confused many users, doesn't work right on OS X 10.6,
17628 and is hard to get rid of once installed. Resolves bug 1274.
17629 - Remove support for .noconnect style addresses. Nobody was using
17630 them, and they provided another avenue for detecting Tor users
17631 via application-level web tricks.
17632 - When we fixed bug 1038 we had to put in a restriction not to send
17633 RELAY_EARLY cells on rend circuits. This was necessary as long
17634 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
17635 active. Now remove this obsolete check. Resolves bug 2081.
17636 - Remove workaround code to handle directory responses from servers
17637 that had bug 539 (they would send HTTP status 503 responses _and_
17638 send a body too). Since only server versions before
17639 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
17640 keep the workaround in place.
17641 - Remove the old 'fuzzy time' logic. It was supposed to be used for
17642 handling calculations where we have a known amount of clock skew and
17643 an allowed amount of unknown skew. But we only used it in three
17644 places, and we never adjusted the known/unknown skew values. This is
17645 still something we might want to do someday, but if we do, we'll
17646 want to do it differently.
17647 - Remove the "--enable-iphone" option to ./configure. According to
17648 reports from Marco Bonetti, Tor builds fine without any special
17649 tweaking on recent iPhone SDK versions.
17652 Changes in version 0.2.1.30 - 2011-02-23
17653 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
17654 change is a slight tweak to Tor's TLS handshake that makes relays
17655 and bridges that run this new version reachable from Iran again.
17656 We don't expect this tweak will win the arms race long-term, but it
17657 buys us time until we roll out a better solution.
17660 - Stop sending a CLOCK_SKEW controller status event whenever
17661 we fetch directory information from a relay that has a wrong clock.
17662 Instead, only inform the controller when it's a trusted authority
17663 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
17664 the rest of bug 1074.
17665 - Fix a bounds-checking error that could allow an attacker to
17666 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
17667 Found by "piebeer".
17668 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
17669 Tor would ignore their RelayBandwidthBurst setting,
17670 potentially using more bandwidth than expected. Bugfix on
17671 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
17672 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
17673 hidserv" in her torrc. The 'hidserv' argument never controlled
17674 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
17677 - Adjust our TLS Diffie-Hellman parameters to match those used by
17679 - Update to the February 1 2011 Maxmind GeoLite Country database.
17682 - Check for and reject overly long directory certificates and
17683 directory tokens before they have a chance to hit any assertions.
17684 Bugfix on 0.2.1.28. Found by "doorss".
17685 - Bring the logic that gathers routerinfos and assesses the
17686 acceptability of circuits into line. This prevents a Tor OP from
17687 getting locked in a cycle of choosing its local OR as an exit for a
17688 path (due to a .exit request) and then rejecting the circuit because
17689 its OR is not listed yet. It also prevents Tor clients from using an
17690 OR running in the same instance as an exit (due to a .exit request)
17691 if the OR does not meet the same requirements expected of an OR
17692 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
17694 o Packaging changes:
17695 - Stop shipping the Tor specs files and development proposal documents
17696 in the tarball. They are now in a separate git repository at
17697 git://git.torproject.org/torspec.git
17698 - Do not include Git version tags as though they are SVN tags when
17699 generating a tarball from inside a repository that has switched
17700 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
17703 Changes in version 0.2.1.29 - 2011-01-15
17704 Tor 0.2.1.29 continues our recent code security audit work. The main
17705 fix resolves a remote heap overflow vulnerability that can allow remote
17706 code execution. Other fixes address a variety of assert and crash bugs,
17707 most of which we think are hard to exploit remotely.
17709 o Major bugfixes (security):
17710 - Fix a heap overflow bug where an adversary could cause heap
17711 corruption. This bug probably allows remote code execution
17712 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
17714 - Prevent a denial-of-service attack by disallowing any
17715 zlib-compressed data whose compression factor is implausibly
17716 high. Fixes part of bug 2324; reported by "doorss".
17717 - Zero out a few more keys in memory before freeing them. Fixes
17718 bug 2384 and part of bug 2385. These key instances found by
17719 "cypherpunks", based on Andrew Case's report about being able
17720 to find sensitive data in Tor's memory space if you have enough
17721 permissions. Bugfix on 0.0.2pre9.
17723 o Major bugfixes (crashes):
17724 - Prevent calls to Libevent from inside Libevent log handlers.
17725 This had potential to cause a nasty set of crashes, especially
17726 if running Libevent with debug logging enabled, and running
17727 Tor with a controller watching for low-severity log messages.
17728 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
17729 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
17730 underflow errors there too. Fixes the other part of bug 2324.
17731 - Fix a bug where we would assert if we ever had a
17732 cached-descriptors.new file (or another file read directly into
17733 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
17734 on 0.2.1.25. Found by doorss.
17735 - Fix some potential asserts and parsing issues with grossly
17736 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
17739 o Minor bugfixes (other):
17740 - Fix a bug with handling misformed replies to reverse DNS lookup
17741 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
17742 bug reported by doorss.
17743 - Fix compilation on mingw when a pthreads compatibility library
17744 has been installed. (We don't want to use it, so we shouldn't
17745 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
17746 - Fix a bug where we would declare that we had run out of virtual
17747 addresses when the address space was only half-exhausted. Bugfix
17749 - Correctly handle the case where AutomapHostsOnResolve is set but
17750 no virtual addresses are available. Fixes bug 2328; bugfix on
17751 0.1.2.1-alpha. Bug found by doorss.
17752 - Correctly handle wrapping around when we run out of virtual
17753 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
17756 - Update to the January 1 2011 Maxmind GeoLite Country database.
17757 - Introduce output size checks on all of our decryption functions.
17760 - Tor does not build packages correctly with Automake 1.6 and earlier;
17761 added a check to Makefile.am to make sure that we're building with
17762 Automake 1.7 or later.
17763 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
17764 because we built it with a too-old version of automake. Thus that
17765 release broke ./configure --enable-openbsd-malloc, which is popular
17766 among really fast exit relays on Linux.
17769 Changes in version 0.2.1.28 - 2010-12-17
17770 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
17771 exploitable bugs. We also took this opportunity to change the IP address
17772 for one of our directory authorities, and to update the geoip database
17776 - Fix a remotely exploitable bug that could be used to crash instances
17777 of Tor remotely by overflowing on the heap. Remote-code execution
17778 hasn't been confirmed, but can't be ruled out. Everyone should
17779 upgrade. Bugfix on the 0.1.1 series and later.
17781 o Directory authority changes:
17782 - Change IP address and ports for gabelmoo (v3 directory authority).
17785 - Update to the December 1 2010 Maxmind GeoLite Country database.
17788 Changes in version 0.2.1.27 - 2010-11-23
17789 Yet another OpenSSL security patch broke its compatibility with Tor:
17790 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
17791 also took this opportunity to fix several crash bugs, integrate a new
17792 directory authority, and update the bundled GeoIP database.
17795 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
17796 No longer set the tlsext_host_name extension on server SSL objects;
17797 but continue to set it on client SSL objects. Our goal in setting
17798 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
17799 bugfix on 0.2.1.1-alpha.
17800 - Do not log messages to the controller while shrinking buffer
17801 freelists. Doing so would sometimes make the controller connection
17802 try to allocate a buffer chunk, which would mess up the internals
17803 of the freelist and cause an assertion failure. Fixes bug 1125;
17804 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
17805 - Learn our external IP address when we're a relay or bridge, even if
17806 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
17807 where we introduced bridge relays that don't need to publish to
17808 be useful. Fixes bug 2050.
17809 - Do even more to reject (and not just ignore) annotations on
17810 router descriptors received anywhere but from the cache. Previously
17811 we would ignore such annotations at first, but cache them to disk
17812 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
17813 - When you're using bridges and your network goes away and your
17814 bridges get marked as down, recover when you attempt a new socks
17815 connection (if the network is back), rather than waiting up to an
17816 hour to try fetching new descriptors for your bridges. Bugfix on
17817 0.2.0.3-alpha; fixes bug 1981.
17820 - Move to the November 2010 Maxmind GeoLite country db (rather
17821 than the June 2009 ip-to-country GeoIP db) for our statistics that
17822 count how many users relays are seeing from each country. Now we'll
17823 have more accurate data, especially for many African countries.
17825 o New directory authorities:
17826 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
17830 - Fix an assertion failure that could occur in directory caches or
17831 bridge users when using a very short voting interval on a testing
17832 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
17834 - Enforce multiplicity rules when parsing annotations. Bugfix on
17835 0.2.0.8-alpha. Found by piebeer.
17836 - Allow handshaking OR connections to take a full KeepalivePeriod
17837 seconds to handshake. Previously, we would close them after
17838 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
17839 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
17841 - When building with --enable-gcc-warnings on OpenBSD, disable
17842 warnings in system headers. This makes --enable-gcc-warnings
17843 pass on OpenBSD 4.8.
17846 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
17847 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
17848 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
17849 Servers can start sending this code when enough clients recognize
17850 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
17851 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
17852 Patch from mingw-san.
17855 - Remove the old debian/ directory from the main Tor distribution.
17856 The official Tor-for-debian git repository lives at the URL
17857 https://git.torproject.org/debian/tor.git
17858 - Stop shipping the old doc/website/ directory in the tarball. We
17859 changed the website format in late 2010, and what we shipped in
17860 0.2.1.26 really wasn't that useful anyway.
17863 Changes in version 0.2.1.26 - 2010-05-02
17864 Tor 0.2.1.26 addresses the recent connection and memory overload
17865 problems we've been seeing on relays, especially relays with their
17866 DirPort open. If your relay has been crashing, or you turned it off
17867 because it used too many resources, give this release a try.
17869 This release also fixes yet another instance of broken OpenSSL libraries
17870 that was causing some relays to drop out of the consensus.
17873 - Teach relays to defend themselves from connection overload. Relays
17874 now close idle circuits early if it looks like they were intended
17875 for directory fetches. Relays are also more aggressive about closing
17876 TLS connections that have no circuits on them. Such circuits are
17877 unlikely to be re-used, and tens of thousands of them were piling
17878 up at the fast relays, causing the relays to run out of sockets
17879 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
17880 their directory fetches over TLS).
17881 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
17882 that claim to be earlier than 0.9.8m, but which have in reality
17883 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
17884 behavior. Possible fix for some cases of bug 1346.
17885 - Directory mirrors were fetching relay descriptors only from v2
17886 directory authorities, rather than v3 authorities like they should.
17887 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
17888 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
17891 - Finally get rid of the deprecated and now harmful notion of "clique
17892 mode", where directory authorities maintain TLS connections to
17896 - In the util/threads test, no longer free the test_mutex before all
17897 worker threads have finished. Bugfix on 0.2.1.6-alpha.
17898 - The master thread could starve the worker threads quite badly on
17899 certain systems, causing them to run only partially in the allowed
17900 window. This resulted in test failures. Now the master thread sleeps
17901 occasionally for a few microseconds while the two worker-threads
17902 compete for the mutex. Bugfix on 0.2.0.1-alpha.
17905 Changes in version 0.2.1.25 - 2010-03-16
17906 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
17907 prevent relays from guessing their IP address correctly. It also fixes
17908 several minor potential security bugs.
17911 - Fix a regression from our patch for bug 1244 that caused relays
17912 to guess their IP address incorrectly if they didn't set Address
17913 in their torrc and/or their address fails to resolve. Bugfix on
17914 0.2.1.23; fixes bug 1269.
17915 - When freeing a session key, zero it out completely. We only zeroed
17916 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
17917 patched by ekir. Fixes bug 1254.
17920 - Fix a dereference-then-NULL-check sequence when publishing
17921 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
17923 - Fix another dereference-then-NULL-check sequence. Bugfix on
17924 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
17925 - Make sure we treat potentially not NUL-terminated strings correctly.
17926 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
17929 Changes in version 0.2.1.24 - 2010-02-21
17930 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
17934 - Work correctly out-of-the-box with even more vendor-patched versions
17935 of OpenSSL. In particular, make it so Debian and OS X don't need
17936 customized patches to run/build.
17939 Changes in version 0.2.1.23 - 2010-02-13
17940 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
17941 again on the latest OS X, and updates the location of a directory
17944 o Major bugfixes (performance):
17945 - We were selecting our guards uniformly at random, and then weighting
17946 which of our guards we'd use uniformly at random. This imbalance
17947 meant that Tor clients were severely limited on throughput (and
17948 probably latency too) by the first hop in their circuit. Now we
17949 select guards weighted by currently advertised bandwidth. We also
17950 automatically discard guards picked using the old algorithm. Fixes
17951 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
17954 - Make Tor work again on the latest OS X: when deciding whether to
17955 use strange flags to turn TLS renegotiation on, detect the OpenSSL
17956 version at run-time, not compile time. We need to do this because
17957 Apple doesn't update its dev-tools headers when it updates its
17958 libraries in a security patch.
17959 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
17960 that could happen on 32-bit platforms with 64-bit time_t. Also fix
17961 a memory leak when requesting a hidden service descriptor we've
17962 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
17966 - Refactor resolve_my_address() to not use gethostbyname() anymore.
17967 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
17970 - Avoid a mad rush at the beginning of each month when each client
17971 rotates half of its guards. Instead we spread the rotation out
17972 throughout the month, but we still avoid leaving a precise timestamp
17973 in the state file about when we first picked the guard. Improves
17974 over the behavior introduced in 0.1.2.17.
17977 Changes in version 0.2.1.22 - 2010-01-19
17978 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
17979 authorities -- it would tell you its whole history of bridge descriptors
17980 if you make the right directory request. This stable update also
17981 rotates two of the seven v3 directory authority keys and locations.
17983 o Directory authority changes:
17984 - Rotate keys (both v3 identity and relay identity) for moria1
17988 - Stop bridge directory authorities from answering dbg-stability.txt
17989 directory queries, which would let people fetch a list of all
17990 bridge identities they track. Bugfix on 0.2.1.6-alpha.
17993 Changes in version 0.2.1.21 - 2009-12-21
17994 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
17995 library. If you use Tor on Linux / Unix and you're getting SSL
17996 renegotiation errors, upgrading should help. We also recommend an
17997 upgrade if you're an exit relay.
18000 - Work around a security feature in OpenSSL 0.9.8l that prevents our
18001 handshake from working unless we explicitly tell OpenSSL that we
18002 are using SSL renegotiation safely. We are, of course, but OpenSSL
18003 0.9.8l won't work unless we say we are.
18004 - Avoid crashing if the client is trying to upload many bytes and the
18005 circuit gets torn down at the same time, or if the flip side
18006 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
18009 - Do not refuse to learn about authority certs and v2 networkstatus
18010 documents that are older than the latest consensus. This bug might
18011 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
18012 Spotted and fixed by xmux.
18013 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
18014 trigger platform-specific option misparsing case found by Coverity
18016 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
18017 trigger assert. Fixes bug 1173.
18020 Changes in version 0.2.1.20 - 2009-10-15
18021 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
18022 services at once, prepares for more performance improvements, and
18023 fixes a bunch of smaller bugs.
18025 The Windows and OS X bundles also include a more recent Vidalia,
18026 and switch from Privoxy to Polipo.
18028 The OS X installers are now drag and drop. It's best to un-install
18029 Tor/Vidalia and then install this new bundle, rather than upgrade. If
18030 you want to upgrade, you'll need to update the paths for Tor and Polipo
18031 in the Vidalia Settings window.
18034 - Send circuit or stream sendme cells when our window has decreased
18035 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
18036 by Karsten when testing the "reduce circuit window" performance
18037 patch. Bugfix on the 54th commit on Tor -- from July 2002,
18038 before the release of Tor 0.0.0. This is the new winner of the
18040 - Fix a remotely triggerable memory leak when a consensus document
18041 contains more than one signature from the same voter. Bugfix on
18043 - Avoid segfault in rare cases when finishing an introduction circuit
18044 as a client and finding out that we don't have an introduction key
18045 for it. Fixes bug 1073. Reported by Aaron Swartz.
18048 - Tor now reads the "circwindow" parameter out of the consensus,
18049 and uses that value for its circuit package window rather than the
18050 default of 1000 cells. Begins the implementation of proposal 168.
18052 o New directory authorities:
18053 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
18055 - Move moria1 and tonga to alternate IP addresses.
18058 - Fix a signed/unsigned compile warning in 0.2.1.19.
18059 - Fix possible segmentation fault on directory authorities. Bugfix on
18061 - Fix an extremely rare infinite recursion bug that could occur if
18062 we tried to log a message after shutting down the log subsystem.
18063 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
18064 - Fix an obscure bug where hidden services on 64-bit big-endian
18065 systems might mis-read the timestamp in v3 introduce cells, and
18066 refuse to connect back to the client. Discovered by "rotor".
18067 Bugfix on 0.2.1.6-alpha.
18068 - We were triggering a CLOCK_SKEW controller status event whenever
18069 we connect via the v2 connection protocol to any relay that has
18070 a wrong clock. Instead, we should only inform the controller when
18071 it's a trusted authority that claims our clock is wrong. Bugfix
18072 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
18073 - We were telling the controller about CHECKING_REACHABILITY and
18074 REACHABILITY_FAILED status events whenever we launch a testing
18075 circuit or notice that one has failed. Instead, only tell the
18076 controller when we want to inform the user of overall success or
18077 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
18079 - Don't warn when we're using a circuit that ends with a node
18080 excluded in ExcludeExitNodes, but the circuit is not used to access
18081 the outside world. This should help fix bug 1090. Bugfix on
18083 - Work around a small memory leak in some versions of OpenSSL that
18084 stopped the memory used by the hostname TLS extension from being
18088 - Add a "getinfo status/accepted-server-descriptor" controller
18089 command, which is the recommended way for controllers to learn
18090 whether our server descriptor has been successfully received by at
18091 least on directory authority. Un-recommend good-server-descriptor
18092 getinfo and status events until we have a better design for them.
18095 Changes in version 0.2.1.19 - 2009-07-28
18096 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
18100 - Make accessing hidden services on 0.2.1.x work right again.
18101 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
18102 part of patch provided by "optimist".
18105 - When a relay/bridge is writing out its identity key fingerprint to
18106 the "fingerprint" file and to its logs, write it without spaces. Now
18107 it will look like the fingerprints in our bridges documentation,
18108 and confuse fewer users.
18111 - Relays no longer publish a new server descriptor if they change
18112 their MaxAdvertisedBandwidth config option but it doesn't end up
18113 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
18114 fixes bug 1026. Patch from Sebastian.
18115 - Avoid leaking memory every time we get a create cell but we have
18116 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
18117 fixes bug 1034. Reported by BarkerJr.
18120 Changes in version 0.2.1.18 - 2009-07-24
18121 Tor 0.2.1.18 lays the foundations for performance improvements,
18122 adds status events to help users diagnose bootstrap problems, adds
18123 optional authentication/authorization for hidden services, fixes a
18124 variety of potential anonymity problems, and includes a huge pile of
18125 other features and bug fixes.
18127 o Major features (clients):
18128 - Start sending "bootstrap phase" status events to the controller,
18129 so it can keep the user informed of progress fetching directory
18130 information and establishing circuits. Also inform the controller
18131 if we think we're stuck at a particular bootstrap phase. Implements
18133 - Clients replace entry guards that were chosen more than a few months
18134 ago. This change should significantly improve client performance,
18135 especially once more people upgrade, since relays that have been
18136 a guard for a long time are currently overloaded.
18137 - Network status consensus documents and votes now contain bandwidth
18138 information for each relay. Clients use the bandwidth values
18139 in the consensus, rather than the bandwidth values in each
18140 relay descriptor. This approach opens the door to more accurate
18141 bandwidth estimates once the directory authorities start doing
18142 active measurements. Implements part of proposal 141.
18144 o Major features (relays):
18145 - Disable and refactor some debugging checks that forced a linear scan
18146 over the whole server-side DNS cache. These accounted for over 50%
18147 of CPU time on a relatively busy exit node's gprof profile. Also,
18148 disable some debugging checks that appeared in exit node profile
18149 data. Found by Jacob.
18150 - New DirPortFrontPage option that takes an html file and publishes
18151 it as "/" on the DirPort. Now relay operators can provide a
18152 disclaimer without needing to set up a separate webserver. There's
18153 a sample disclaimer in contrib/tor-exit-notice.html.
18155 o Major features (hidden services):
18156 - Make it possible to build hidden services that only certain clients
18157 are allowed to connect to. This is enforced at several points,
18158 so that unauthorized clients are unable to send INTRODUCE cells
18159 to the service, or even (depending on the type of authentication)
18160 to learn introduction points. This feature raises the bar for
18161 certain kinds of active attacks against hidden services. Design
18162 and code by Karsten Loesing. Implements proposal 121.
18163 - Relays now store and serve v2 hidden service descriptors by default,
18164 i.e., the new default value for HidServDirectoryV2 is 1. This is
18165 the last step in proposal 114, which aims to make hidden service
18166 lookups more reliable.
18168 o Major features (path selection):
18169 - ExitNodes and Exclude*Nodes config options now allow you to restrict
18170 by country code ("{US}") or IP address or address pattern
18171 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
18172 refinement to decide what config options should take priority if
18173 you ask to both use a particular node and exclude it.
18175 o Major features (misc):
18176 - When building a consensus, do not include routers that are down.
18177 This cuts down 30% to 40% on consensus size. Implements proposal
18179 - New TestingTorNetwork config option to allow adjustment of
18180 previously constant values that could slow bootstrapping. Implements
18181 proposal 135. Patch from Karsten.
18182 - Convert many internal address representations to optionally hold
18183 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
18184 elements. Make resolver code handle nameservers located at IPv6
18186 - More work on making our TLS handshake blend in: modify the list
18187 of ciphers advertised by OpenSSL in client mode to even more
18188 closely resemble a common web browser. We cheat a little so that
18189 we can advertise ciphers that the locally installed OpenSSL doesn't
18191 - Use the TLS1 hostname extension to more closely resemble browser
18194 o Security fixes (anonymity/entropy):
18195 - Never use a connection with a mismatched address to extend a
18196 circuit, unless that connection is canonical. A canonical
18197 connection is one whose address is authenticated by the router's
18198 identity key, either in a NETINFO cell or in a router descriptor.
18199 - Implement most of proposal 110: The first K cells to be sent
18200 along a circuit are marked as special "early" cells; only K "early"
18201 cells will be allowed. Once this code is universal, we can block
18202 certain kinds of denial-of-service attack by requiring that EXTEND
18203 commands must be sent using an "early" cell.
18204 - Resume using OpenSSL's RAND_poll() for better (and more portable)
18205 cross-platform entropy collection again. We used to use it, then
18206 stopped using it because of a bug that could crash systems that
18207 called RAND_poll when they had a lot of fds open. It looks like the
18208 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
18209 at startup, and to call RAND_poll() when we reseed later only if
18210 we have a non-buggy OpenSSL version.
18211 - When the client is choosing entry guards, now it selects at most
18212 one guard from a given relay family. Otherwise we could end up with
18213 all of our entry points into the network run by the same operator.
18214 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
18215 - Do not use or believe expired v3 authority certificates. Patch
18216 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
18217 - Drop begin cells to a hidden service if they come from the middle
18218 of a circuit. Patch from lark.
18219 - When we erroneously receive two EXTEND cells for the same circuit
18220 ID on the same connection, drop the second. Patch from lark.
18221 - Authorities now vote for the Stable flag for any router whose
18222 weighted MTBF is at least 5 days, regardless of the mean MTBF.
18223 - Clients now never report any stream end reason except 'MISC'.
18224 Implements proposal 148.
18226 o Major bugfixes (crashes):
18227 - Parse dates and IPv4 addresses in a locale- and libc-independent
18228 manner, to avoid platform-dependent behavior on malformed input.
18229 - Fix a crash that occurs on exit nodes when a nameserver request
18230 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
18231 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
18233 - Do not assume that a stack-allocated character array will be
18234 64-bit aligned on platforms that demand that uint64_t access is
18235 aligned. Possible fix for bug 604.
18236 - Resolve a very rare crash bug that could occur when the user forced
18237 a nameserver reconfiguration during the middle of a nameserver
18238 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
18239 - Avoid a "0 divided by 0" calculation when calculating router uptime
18240 at directory authorities. Bugfix on 0.2.0.8-alpha.
18241 - Fix an assertion bug in parsing policy-related options; possible fix
18243 - Rate-limit too-many-sockets messages: when they happen, they happen
18244 a lot and end up filling up the disk. Resolves bug 748.
18245 - Fix a race condition that could cause crashes or memory corruption
18246 when running as a server with a controller listening for log
18248 - Avoid crashing when we have a policy specified in a DirPolicy or
18249 SocksPolicy or ReachableAddresses option with ports set on it,
18250 and we re-load the policy. May fix bug 996.
18251 - Fix an assertion failure on 64-bit platforms when we allocated
18252 memory right up to the end of a memarea, then realigned the memory
18253 one step beyond the end. Fixes a possible cause of bug 930.
18254 - Protect the count of open sockets with a mutex, so we can't
18255 corrupt it when two threads are closing or opening sockets at once.
18256 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
18258 o Major bugfixes (clients):
18259 - Discard router descriptors as we load them if they are more than
18260 five days old. Otherwise if Tor is off for a long time and then
18261 starts with cached descriptors, it will try to use the onion keys
18262 in those obsolete descriptors when building circuits. Fixes bug 887.
18263 - When we choose to abandon a new entry guard because we think our
18264 older ones might be better, close any circuits pending on that
18265 new entry guard connection. This fix should make us recover much
18266 faster when our network is down and then comes back. Bugfix on
18267 0.1.2.8-beta; found by lodger.
18268 - When Tor clients restart after 1-5 days, they discard all their
18269 cached descriptors as too old, but they still use the cached
18270 consensus document. This approach is good for robustness, but
18271 bad for performance: since they don't know any bandwidths, they
18272 end up choosing at random rather than weighting their choice by
18273 speed. Fixed by the above feature of putting bandwidths in the
18276 o Major bugfixes (relays):
18277 - Relays were falling out of the networkstatus consensus for
18278 part of a day if they changed their local config but the
18279 authorities discarded their new descriptor as "not sufficiently
18280 different". Now directory authorities accept a descriptor as changed
18281 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
18282 patch by Sebastian.
18283 - Ensure that two circuits can never exist on the same connection
18284 with the same circuit ID, even if one is marked for close. This
18285 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
18286 - Directory authorities were neglecting to mark relays down in their
18287 internal histories if the relays fall off the routerlist without
18288 ever being found unreachable. So there were relays in the histories
18289 that haven't been seen for eight months, and are listed as being
18290 up for eight months. This wreaked havoc on the "median wfu" and
18291 "median mtbf" calculations, in turn making Guard and Stable flags
18292 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
18295 o Major bugfixes (hidden services):
18296 - When establishing a hidden service, introduction points that
18297 originate from cannibalized circuits were completely ignored
18298 and not included in rendezvous service descriptors. This might
18299 have been another reason for delay in making a hidden service
18300 available. Bugfix from long ago (0.0.9.x?)
18302 o Major bugfixes (memory and resource management):
18303 - Fixed some memory leaks -- some quite frequent, some almost
18304 impossible to trigger -- based on results from Coverity.
18305 - Speed up parsing and cut down on memory fragmentation by using
18306 stack-style allocations for parsing directory objects. Previously,
18307 this accounted for over 40% of allocations from within Tor's code
18308 on a typical directory cache.
18309 - Use a Bloom filter rather than a digest-based set to track which
18310 descriptors we need to keep around when we're cleaning out old
18311 router descriptors. This speeds up the computation significantly,
18312 and may reduce fragmentation.
18314 o New/changed config options:
18315 - Now NodeFamily and MyFamily config options allow spaces in
18316 identity fingerprints, so it's easier to paste them in.
18317 Suggested by Lucky Green.
18318 - Allow ports 465 and 587 in the default exit policy again. We had
18319 rejected them in 0.1.0.15, because back in 2005 they were commonly
18320 misconfigured and ended up as spam targets. We hear they are better
18321 locked down these days.
18322 - Make TrackHostExit mappings expire a while after their last use, not
18323 after their creation. Patch from Robert Hogan.
18324 - Add an ExcludeExitNodes option so users can list a set of nodes
18325 that should be be excluded from the exit node position, but
18326 allowed elsewhere. Implements proposal 151.
18327 - New --hush command-line option similar to --quiet. While --quiet
18328 disables all logging to the console on startup, --hush limits the
18329 output to messages of warning and error severity.
18330 - New configure/torrc options (--enable-geoip-stats,
18331 DirRecordUsageByCountry) to record how many IPs we've served
18332 directory info to in each country code, how many status documents
18333 total we've sent to each country code, and what share of the total
18334 directory requests we should expect to see.
18335 - Make outbound DNS packets respect the OutboundBindAddress setting.
18336 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
18337 - Allow separate log levels to be configured for different logging
18338 domains. For example, this allows one to log all notices, warnings,
18339 or errors, plus all memory management messages of level debug or
18340 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
18341 - Update to the "June 3 2009" ip-to-country file.
18343 o Minor features (relays):
18344 - Raise the minimum rate limiting to be a relay from 20000 bytes
18345 to 20480 bytes (aka 20KB/s), to match our documentation. Also
18346 update directory authorities so they always assign the Fast flag
18347 to relays with 20KB/s of capacity. Now people running relays won't
18348 suddenly find themselves not seeing any use, if the network gets
18350 - If we're a relay and we change our IP address, be more verbose
18351 about the reason that made us change. Should help track down
18352 further bugs for relays on dynamic IP addresses.
18353 - Exit servers can now answer resolve requests for ip6.arpa addresses.
18354 - Implement most of Proposal 152: allow specialized servers to permit
18355 single-hop circuits, and clients to use those servers to build
18356 single-hop circuits when using a specialized controller. Patch
18357 from Josh Albrecht. Resolves feature request 768.
18358 - When relays do their initial bandwidth measurement, don't limit
18359 to just our entry guards for the test circuits. Otherwise we tend
18360 to have multiple test circuits going through a single entry guard,
18361 which makes our bandwidth test less accurate. Fixes part of bug 654;
18362 patch contributed by Josh Albrecht.
18364 o Minor features (directory authorities):
18365 - Try not to open more than one descriptor-downloading connection
18366 to an authority at once. This should reduce load on directory
18367 authorities. Fixes bug 366.
18368 - Add cross-certification to newly generated certificates, so that
18369 a signing key is enough information to look up a certificate. Start
18370 serving certificates by <identity digest, signing key digest>
18371 pairs. Implements proposal 157.
18372 - When a directory authority downloads a descriptor that it then
18373 immediately rejects, do not retry downloading it right away. Should
18374 save some bandwidth on authorities. Fix for bug 888. Patch by
18376 - Directory authorities now serve a /tor/dbg-stability.txt URL to
18377 help debug WFU and MTBF calculations.
18378 - In directory authorities' approved-routers files, allow
18379 fingerprints with or without space.
18381 o Minor features (directory mirrors):
18382 - When a download gets us zero good descriptors, do not notify
18383 Tor that new directory information has arrived.
18384 - Servers support a new URL scheme for consensus downloads that
18385 allows the client to specify which authorities are trusted.
18386 The server then only sends the consensus if the client will trust
18387 it. Otherwise a 404 error is sent back. Clients use this
18388 new scheme when the server supports it (meaning it's running
18389 0.2.1.1-alpha or later). Implements proposal 134.
18391 o Minor features (bridges):
18392 - If the bridge config line doesn't specify a port, assume 443.
18393 This makes bridge lines a bit smaller and easier for users to
18395 - If we're using bridges and our network goes away, be more willing
18396 to forgive our bridges and try again when we get an application
18399 o Minor features (hidden services):
18400 - When the client launches an introduction circuit, retry with a
18401 new circuit after 30 seconds rather than 60 seconds.
18402 - Launch a second client-side introduction circuit in parallel
18403 after a delay of 15 seconds (based on work by Christian Wilms).
18404 - Hidden services start out building five intro circuits rather
18405 than three, and when the first three finish they publish a service
18406 descriptor using those. Now we publish our service descriptor much
18407 faster after restart.
18408 - Drop the requirement to have an open dir port for storing and
18409 serving v2 hidden service descriptors.
18411 o Minor features (build and packaging):
18412 - On Linux, use the prctl call to re-enable core dumps when the User
18414 - Try to make sure that the version of Libevent we're running with
18415 is binary-compatible with the one we built with. May address bug
18417 - Add a new --enable-local-appdata configuration switch to change
18418 the default location of the datadir on win32 from APPDATA to
18419 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
18420 entirely. Patch from coderman.
18421 - Build correctly against versions of OpenSSL 0.9.8 or later that
18422 are built without support for deprecated functions.
18423 - On platforms with a maximum syslog string length, truncate syslog
18424 messages to that length ourselves, rather than relying on the
18425 system to do it for us.
18426 - Automatically detect MacOSX versions earlier than 10.4.0, and
18427 disable kqueue from inside Tor when running with these versions.
18428 We previously did this from the startup script, but that was no
18429 help to people who didn't use the startup script. Resolves bug 863.
18430 - Build correctly when configured to build outside the main source
18431 path. Patch from Michael Gold.
18432 - Disable GCC's strict alias optimization by default, to avoid the
18433 likelihood of its introducing subtle bugs whenever our code violates
18434 the letter of C99's alias rules.
18435 - Change the contrib/tor.logrotate script so it makes the new
18436 logs as "_tor:_tor" rather than the default, which is generally
18437 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
18438 - Change our header file guard macros to be less likely to conflict
18439 with system headers. Adam Langley noticed that we were conflicting
18440 with log.h on Android.
18441 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
18442 and stop using a warning that had become unfixably verbose under
18444 - Use a lockfile to make sure that two Tor processes are not
18445 simultaneously running with the same datadir.
18446 - Allow OpenSSL to use dynamic locks if it wants.
18447 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
18449 o Minor features (controllers):
18450 - When generating circuit events with verbose nicknames for
18451 controllers, try harder to look up nicknames for routers on a
18452 circuit. (Previously, we would look in the router descriptors we had
18453 for nicknames, but not in the consensus.) Partial fix for bug 941.
18454 - New controller event NEWCONSENSUS that lists the networkstatus
18455 lines for every recommended relay. Now controllers like Torflow
18456 can keep up-to-date on which relays they should be using.
18457 - New controller event "clients_seen" to report a geoip-based summary
18458 of which countries we've seen clients from recently. Now controllers
18459 like Vidalia can show bridge operators that they're actually making
18461 - Add a 'getinfo status/clients-seen' controller command, in case
18462 controllers want to hear clients_seen events but connect late.
18463 - New CONSENSUS_ARRIVED event to note when a new consensus has
18464 been fetched and validated.
18465 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
18466 controllers to prevent SIGHUP from reloading the configuration.
18468 - Return circuit purposes in response to GETINFO circuit-status.
18470 - Serve the latest v3 networkstatus consensus via the control
18471 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
18472 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
18473 controller can query our current bootstrap state in case it attaches
18474 partway through and wants to catch up.
18475 - Provide circuit purposes along with circuit events to the controller.
18477 o Minor features (tools):
18478 - Do not have tor-resolve automatically refuse all .onion addresses;
18479 if AutomapHostsOnResolve is set in your torrc, this will work fine.
18480 - Add a -p option to tor-resolve for specifying the SOCKS port: some
18481 people find host:port too confusing.
18482 - Print the SOCKS5 error message string as well as the error code
18483 when a tor-resolve request fails. Patch from Jacob.
18485 o Minor bugfixes (memory and resource management):
18486 - Clients no longer cache certificates for authorities they do not
18487 recognize. Bugfix on 0.2.0.9-alpha.
18488 - Do not use C's stdio library for writing to log files. This will
18489 improve logging performance by a minute amount, and will stop
18490 leaking fds when our disk is full. Fixes bug 861.
18491 - Stop erroneous use of O_APPEND in cases where we did not in fact
18492 want to re-seek to the end of a file before every last write().
18493 - Fix a small alignment and memory-wasting bug on buffer chunks.
18495 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
18496 to avoid unused RAM in buffer chunks and memory pools.
18497 - Reduce the default smartlist size from 32 to 16; it turns out that
18498 most smartlists hold around 8-12 elements tops.
18499 - Make dumpstats() log the fullness and size of openssl-internal
18501 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
18502 patch to their OpenSSL, turn it on to save memory on servers. This
18503 patch will (with any luck) get included in a mainline distribution
18505 - Fix a memory leak when v3 directory authorities load their keys
18506 and cert from disk. Bugfix on 0.2.0.1-alpha.
18507 - Stop using malloc_usable_size() to use more area than we had
18508 actually allocated: it was safe, but made valgrind really unhappy.
18509 - Make the assert_circuit_ok() function work correctly on circuits that
18510 have already been marked for close.
18511 - Fix uninitialized size field for memory area allocation: may improve
18512 memory performance during directory parsing.
18514 o Minor bugfixes (clients):
18515 - Stop reloading the router list from disk for no reason when we
18516 run out of reachable directory mirrors. Once upon a time reloading
18517 it would set the 'is_running' flag back to 1 for them. It hasn't
18518 done that for a long time.
18519 - When we had picked an exit node for a connection, but marked it as
18520 "optional", and it turned out we had no onion key for the exit,
18521 stop wanting that exit and try again. This situation may not
18522 be possible now, but will probably become feasible with proposal
18523 158. Spotted by rovv. Fixes another case of bug 752.
18524 - Fix a bug in address parsing that was preventing bridges or hidden
18525 service targets from being at IPv6 addresses.
18526 - Do not remove routers as too old if we do not have any consensus
18527 document. Bugfix on 0.2.0.7-alpha.
18528 - When an exit relay resolves a stream address to a local IP address,
18529 do not just keep retrying that same exit relay over and
18530 over. Instead, just close the stream. Addresses bug 872. Bugfix
18531 on 0.2.0.32. Patch from rovv.
18532 - Made Tor a little less aggressive about deleting expired
18533 certificates. Partial fix for bug 854.
18534 - Treat duplicate certificate fetches as failures, so that we do
18535 not try to re-fetch an expired certificate over and over and over.
18536 - Do not say we're fetching a certificate when we'll in fact skip it
18537 because of a pending download.
18538 - If we have correct permissions on $datadir, we complain to stdout
18539 and fail to start. But dangerous permissions on
18540 $datadir/cached-status/ would cause us to open a log and complain
18541 there. Now complain to stdout and fail to start in both cases. Fixes
18542 bug 820, reported by seeess.
18544 o Minor bugfixes (bridges):
18545 - When we made bridge authorities stop serving bridge descriptors over
18546 unencrypted links, we also broke DirPort reachability testing for
18547 bridges. So bridges with a non-zero DirPort were printing spurious
18548 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
18549 - Don't allow a bridge to publish its router descriptor to a
18550 non-bridge directory authority. Fixes part of bug 932.
18551 - When we change to or from being a bridge, reset our counts of
18552 client usage by country. Fixes bug 932.
18554 o Minor bugfixes (relays):
18555 - Log correct error messages for DNS-related network errors on
18557 - Actually return -1 in the error case for read_bandwidth_usage().
18558 Harmless bug, since we currently don't care about the return value
18559 anywhere. Bugfix on 0.2.0.9-alpha.
18560 - Provide a more useful log message if bug 977 (related to buffer
18561 freelists) ever reappears, and do not crash right away.
18562 - We were already rejecting relay begin cells with destination port
18563 of 0. Now also reject extend cells with destination port or address
18564 of 0. Suggested by lark.
18565 - When we can't transmit a DNS request due to a network error, retry
18566 it after a while, and eventually transmit a failing response to
18567 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
18568 - Solve a bug that kept hardware crypto acceleration from getting
18569 enabled when accounting was turned on. Fixes bug 907. Bugfix on
18571 - When a canonical connection appears later in our internal list
18572 than a noncanonical one for a given OR ID, always use the
18573 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
18575 - Avoid some nasty corner cases in the logic for marking connections
18576 as too old or obsolete or noncanonical for circuits. Partial
18578 - Fix another interesting corner-case of bug 891 spotted by rovv:
18579 Previously, if two hosts had different amounts of clock drift, and
18580 one of them created a new connection with just the wrong timing,
18581 the other might decide to deprecate the new connection erroneously.
18582 Bugfix on 0.1.1.13-alpha.
18583 - If one win32 nameserver fails to get added, continue adding the
18584 rest, and don't automatically fail.
18585 - Fix a bug where an unreachable relay would establish enough
18586 reachability testing circuits to do a bandwidth test -- if
18587 we already have a connection to the middle hop of the testing
18588 circuit, then it could establish the last hop by using the existing
18589 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
18590 circuits no longer use entry guards in 0.2.1.3-alpha.
18592 o Minor bugfixes (directory authorities):
18593 - Limit uploaded directory documents to be 16M rather than 500K.
18594 The directory authorities were refusing v3 consensus votes from
18595 other authorities, since the votes are now 504K. Fixes bug 959;
18596 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
18597 - Directory authorities should never send a 503 "busy" response to
18598 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
18600 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
18601 headers. Bugfix on 0.2.0.10-alpha.
18603 o Minor bugfixes (hidden services):
18604 - When we can't find an intro key for a v2 hidden service descriptor,
18605 fall back to the v0 hidden service descriptor and log a bug message.
18606 Workaround for bug 1024.
18607 - In very rare situations new hidden service descriptors were
18608 published earlier than 30 seconds after the last change to the
18609 service. (We currently think that a hidden service descriptor
18610 that's been stable for 30 seconds is worth publishing.)
18611 - If a hidden service sends us an END cell, do not consider
18612 retrying the connection; just close it. Patch from rovv.
18613 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
18614 service directories if they have no advertised dir port. Bugfix
18617 o Minor bugfixes (tools):
18618 - In the torify(1) manpage, mention that tsocks will leak your
18621 o Minor bugfixes (controllers):
18622 - If the controller claimed responsibility for a stream, but that
18623 stream never finished making its connection, it would live
18624 forever in circuit_wait state. Now we close it after SocksTimeout
18625 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
18626 - Make DNS resolved controller events into "CLOSED", not
18627 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
18629 - The control port would close the connection before flushing long
18630 replies, such as the network consensus, if a QUIT command was issued
18631 before the reply had completed. Now, the control port flushes all
18632 pending replies before closing the connection. Also fix a spurious
18633 warning when a QUIT command is issued after a malformed or rejected
18634 AUTHENTICATE command, but before the connection was closed. Patch
18635 by Marcus Griep. Fixes bugs 1015 and 1016.
18636 - Fix a bug that made stream bandwidth get misreported to the
18639 o Deprecated and removed features:
18640 - The old "tor --version --version" command, which would print out
18641 the subversion "Id" of most of the source files, is now removed. It
18642 turned out to be less useful than we'd expected, and harder to
18644 - RedirectExits has been removed. It was deprecated since
18646 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
18647 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
18648 - Cell pools are now always enabled; --disable-cell-pools is ignored.
18649 - Directory mirrors no longer fetch the v1 directory or
18650 running-routers files. They are obsolete, and nobody asks for them
18651 anymore. This is the first step to making v1 authorities obsolete.
18652 - Take out the TestVia config option, since it was a workaround for
18653 a bug that was fixed in Tor 0.1.1.21.
18654 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
18655 HiddenServiceExcludeNodes as obsolete: they never worked properly,
18656 and nobody seems to be using them. Fixes bug 754. Bugfix on
18657 0.1.0.1-rc. Patch from Christian Wilms.
18658 - Remove all backward-compatibility code for relays running
18659 versions of Tor so old that they no longer work at all on the
18662 o Code simplifications and refactoring:
18663 - Tool-assisted documentation cleanup. Nearly every function or
18664 static variable in Tor should have its own documentation now.
18665 - Rename the confusing or_is_obsolete field to the more appropriate
18666 is_bad_for_new_circs, and move it to or_connection_t where it
18668 - Move edge-only flags from connection_t to edge_connection_t: not
18669 only is this better coding, but on machines of plausible alignment,
18670 it should save 4-8 bytes per connection_t. "Every little bit helps."
18671 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
18672 for consistency; keep old option working for backward compatibility.
18673 - Simplify the code for finding connections to use for a circuit.
18674 - Revise the connection_new functions so that a more typesafe variant
18675 exists. This will work better with Coverity, and let us find any
18676 actual mistakes we're making here.
18677 - Refactor unit testing logic so that dmalloc can be used sensibly
18678 with unit tests to check for memory leaks.
18679 - Move all hidden-service related fields from connection and circuit
18680 structure to substructures: this way they won't eat so much memory.
18681 - Squeeze 2-5% out of client performance (according to oprofile) by
18682 improving the implementation of some policy-manipulation functions.
18683 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
18684 be more efficient. Formerly it was quadratic in the number of
18685 servers; now it should be linear. Fixes bug 509.
18686 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
18687 and n_conn_id_digest fields into a separate structure that's
18688 only needed when the circuit has not yet attached to an n_conn.
18689 - Optimize out calls to time(NULL) that occur for every IO operation,
18690 or for every cell. On systems like Windows where time() is a
18691 slow syscall, this fix will be slightly helpful.
18694 Changes in version 0.2.0.35 - 2009-06-24
18696 - Avoid crashing in the presence of certain malformed descriptors.
18697 Found by lark, and by automated fuzzing.
18698 - Fix an edge case where a malicious exit relay could convince a
18699 controller that the client's DNS question resolves to an internal IP
18700 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
18703 - Finally fix the bug where dynamic-IP relays disappear when their
18704 IP address changes: directory mirrors were mistakenly telling
18705 them their old address if they asked via begin_dir, so they
18706 never got an accurate answer about their new address, so they
18707 just vanished after a day. For belt-and-suspenders, relays that
18708 don't set Address in their config now avoid using begin_dir for
18709 all direct connections. Should fix bugs 827, 883, and 900.
18710 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
18711 that would occur on some exit nodes when DNS failures and timeouts
18712 occurred in certain patterns. Fix for bug 957.
18715 - When starting with a cache over a few days old, do not leak
18716 memory for the obsolete router descriptors in it. Bugfix on
18717 0.2.0.33; fixes bug 672.
18718 - Hidden service clients didn't use a cached service descriptor that
18719 was older than 15 minutes, but wouldn't fetch a new one either,
18720 because there was already one in the cache. Now, fetch a v2
18721 descriptor unless the same descriptor was added to the cache within
18722 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
18725 Changes in version 0.2.0.34 - 2009-02-08
18726 Tor 0.2.0.34 features several more security-related fixes. You should
18727 upgrade, especially if you run an exit relay (remote crash) or a
18728 directory authority (remote infinite loop), or you're on an older
18729 (pre-XP) or not-recently-patched Windows (remote exploit).
18731 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
18732 have many known flaws, and nobody should be using them. You should
18733 upgrade. If you're using a Linux or BSD and its packages are obsolete,
18734 stop using those packages and upgrade anyway.
18737 - Fix an infinite-loop bug on handling corrupt votes under certain
18738 circumstances. Bugfix on 0.2.0.8-alpha.
18739 - Fix a temporary DoS vulnerability that could be performed by
18740 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
18741 - Avoid a potential crash on exit nodes when processing malformed
18742 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
18743 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
18744 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
18747 - Fix compilation on systems where time_t is a 64-bit integer.
18748 Patch from Matthias Drochner.
18749 - Don't consider expiring already-closed client connections. Fixes
18750 bug 893. Bugfix on 0.0.2pre20.
18753 Changes in version 0.2.0.33 - 2009-01-21
18754 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
18755 useful to users. It also finally fixes a bug where a relay or client
18756 that's been off for many days would take a long time to bootstrap.
18758 This update also fixes an important security-related bug reported by
18759 Ilja van Sprundel. You should upgrade. (We'll send out more details
18760 about the bug once people have had some time to upgrade.)
18763 - Fix a heap-corruption bug that may be remotely triggerable on
18764 some platforms. Reported by Ilja van Sprundel.
18767 - When a stream at an exit relay is in state "resolving" or
18768 "connecting" and it receives an "end" relay cell, the exit relay
18769 would silently ignore the end cell and not close the stream. If
18770 the client never closes the circuit, then the exit relay never
18771 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
18772 reported by "wood".
18773 - When sending CREATED cells back for a given circuit, use a 64-bit
18774 connection ID to find the right connection, rather than an addr:port
18775 combination. Now that we can have multiple OR connections between
18776 the same ORs, it is no longer possible to use addr:port to uniquely
18777 identify a connection.
18778 - Bridge relays that had DirPort set to 0 would stop fetching
18779 descriptors shortly after startup, and then briefly resume
18780 after a new bandwidth test and/or after publishing a new bridge
18781 descriptor. Bridge users that try to bootstrap from them would
18782 get a recent networkstatus but would get descriptors from up to
18783 18 hours earlier, meaning most of the descriptors were obsolete
18784 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
18785 - Prevent bridge relays from serving their 'extrainfo' document
18786 to anybody who asks, now that extrainfo docs include potentially
18787 sensitive aggregated client geoip summaries. Bugfix on
18789 - If the cached networkstatus consensus is more than five days old,
18790 discard it rather than trying to use it. In theory it could be
18791 useful because it lists alternate directory mirrors, but in practice
18792 it just means we spend many minutes trying directory mirrors that
18793 are long gone from the network. Also discard router descriptors as
18794 we load them if they are more than five days old, since the onion
18795 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
18798 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
18799 could make gcc generate non-functional binary search code. Bugfix
18801 - Build correctly on platforms without socklen_t.
18802 - Compile without warnings on solaris.
18803 - Avoid potential crash on internal error during signature collection.
18804 Fixes bug 864. Patch from rovv.
18805 - Correct handling of possible malformed authority signing key
18806 certificates with internal signature types. Fixes bug 880.
18807 Bugfix on 0.2.0.3-alpha.
18808 - Fix a hard-to-trigger resource leak when logging credential status.
18810 - When we can't initialize DNS because the network is down, do not
18811 automatically stop Tor from starting. Instead, we retry failed
18812 dns_init() every 10 minutes, and change the exit policy to reject
18813 *:* until one succeeds. Fixes bug 691.
18814 - Use 64 bits instead of 32 bits for connection identifiers used with
18815 the controller protocol, to greatly reduce risk of identifier reuse.
18816 - When we're choosing an exit node for a circuit, and we have
18817 no pending streams, choose a good general exit rather than one that
18818 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
18819 - Fix another case of assuming, when a specific exit is requested,
18820 that we know more than the user about what hosts it allows.
18821 Fixes one case of bug 752. Patch from rovv.
18822 - Clip the MaxCircuitDirtiness config option to a minimum of 10
18823 seconds. Warn the user if lower values are given in the
18824 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
18825 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
18826 user if lower values are given in the configuration. Bugfix on
18827 0.1.1.17-rc. Patch by Sebastian.
18828 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
18829 the cache because we already had a v0 descriptor with the same ID.
18830 Bugfix on 0.2.0.18-alpha.
18831 - Fix a race condition when freeing keys shared between main thread
18832 and CPU workers that could result in a memory leak. Bugfix on
18833 0.1.0.1-rc. Fixes bug 889.
18834 - Send a valid END cell back when a client tries to connect to a
18835 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
18836 840. Patch from rovv.
18837 - Check which hops rendezvous stream cells are associated with to
18838 prevent possible guess-the-streamid injection attacks from
18839 intermediate hops. Fixes another case of bug 446. Based on patch
18841 - If a broken client asks a non-exit router to connect somewhere,
18842 do not even do the DNS lookup before rejecting the connection.
18843 Fixes another case of bug 619. Patch from rovv.
18844 - When a relay gets a create cell it can't decrypt (e.g. because it's
18845 using the wrong onion key), we were dropping it and letting the
18846 client time out. Now actually answer with a destroy cell. Fixes
18847 bug 904. Bugfix on 0.0.2pre8.
18849 o Minor bugfixes (hidden services):
18850 - Do not throw away existing introduction points on SIGHUP. Bugfix on
18851 0.0.6pre1. Patch by Karsten. Fixes bug 874.
18854 - Report the case where all signatures in a detached set are rejected
18855 differently than the case where there is an error handling the
18857 - When we realize that another process has modified our cached
18858 descriptors, print out a more useful error message rather than
18859 triggering an assertion. Fixes bug 885. Patch from Karsten.
18860 - Implement the 0x20 hack to better resist DNS poisoning: set the
18861 case on outgoing DNS requests randomly, and reject responses that do
18862 not match the case correctly. This logic can be disabled with the
18863 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
18864 of servers that do not reliably preserve case in replies. See
18865 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
18867 - Check DNS replies for more matching fields to better resist DNS
18869 - Never use OpenSSL compression: it wastes RAM and CPU trying to
18870 compress cells, which are basically all encrypted, compressed, or
18874 Changes in version 0.2.0.32 - 2008-11-20
18875 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
18876 packages (and maybe other packages) noticed by Theo de Raadt, fixes
18877 a smaller security flaw that might allow an attacker to access local
18878 services, further improves hidden service performance, and fixes a
18879 variety of other issues.
18882 - The "User" and "Group" config options did not clear the
18883 supplementary group entries for the Tor process. The "User" option
18884 is now more robust, and we now set the groups to the specified
18885 user's primary group. The "Group" option is now ignored. For more
18886 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
18887 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
18888 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
18889 - The "ClientDNSRejectInternalAddresses" config option wasn't being
18890 consistently obeyed: if an exit relay refuses a stream because its
18891 exit policy doesn't allow it, we would remember what IP address
18892 the relay said the destination address resolves to, even if it's
18893 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
18896 - Fix a DOS opportunity during the voting signature collection process
18897 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
18899 o Major bugfixes (hidden services):
18900 - When fetching v0 and v2 rendezvous service descriptors in parallel,
18901 we were failing the whole hidden service request when the v0
18902 descriptor fetch fails, even if the v2 fetch is still pending and
18903 might succeed. Similarly, if the last v2 fetch fails, we were
18904 failing the whole hidden service request even if a v0 fetch is
18905 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
18906 - When extending a circuit to a hidden service directory to upload a
18907 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
18908 requests failed, because the router descriptor has not been
18909 downloaded yet. In these cases, do not attempt to upload the
18910 rendezvous descriptor, but wait until the router descriptor is
18911 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
18912 descriptor from a hidden service directory for which the router
18913 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
18917 - Fix several infrequent memory leaks spotted by Coverity.
18918 - When testing for libevent functions, set the LDFLAGS variable
18919 correctly. Found by Riastradh.
18920 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
18921 bootstrapping with tunneled directory connections. Bugfix on
18922 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
18923 - When asked to connect to A.B.exit:80, if we don't know the IP for A
18924 and we know that server B rejects most-but-not all connections to
18925 port 80, we would previously reject the connection. Now, we assume
18926 the user knows what they were asking for. Fixes bug 752. Bugfix
18927 on 0.0.9rc5. Diagnosed by BarkerJr.
18928 - If we overrun our per-second write limits a little, count this as
18929 having used up our write allocation for the second, and choke
18930 outgoing directory writes. Previously, we had only counted this when
18931 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
18932 Bugfix on 0.2.0.x (??).
18933 - Remove the old v2 directory authority 'lefkada' from the default
18934 list. It has been gone for many months.
18935 - Stop doing unaligned memory access that generated bus errors on
18936 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
18937 - Make USR2 log-level switch take effect immediately. Bugfix on
18940 o Minor bugfixes (controller):
18941 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
18942 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
18945 Changes in version 0.2.0.31 - 2008-09-03
18946 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
18947 a big bug we're seeing where in rare cases traffic from one Tor stream
18948 gets mixed into another stream, and fixes a variety of smaller issues.
18951 - Make sure that two circuits can never exist on the same connection
18952 with the same circuit ID, even if one is marked for close. This
18953 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
18954 - Relays now reject risky extend cells: if the extend cell includes
18955 a digest of all zeroes, or asks to extend back to the relay that
18956 sent the extend cell, tear down the circuit. Ideas suggested
18958 - If not enough of our entry guards are available so we add a new
18959 one, we might use the new one even if it overlapped with the
18960 current circuit's exit relay (or its family). Anonymity bugfix
18961 pointed out by rovv.
18964 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
18965 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
18966 - Correctly detect the presence of the linux/netfilter_ipv4.h header
18967 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
18968 - Pick size of default geoip filename string correctly on windows.
18969 Fixes bug 806. Bugfix on 0.2.0.30.
18970 - Make the autoconf script accept the obsolete --with-ssl-dir
18971 option as an alias for the actually-working --with-openssl-dir
18972 option. Fix the help documentation to recommend --with-openssl-dir.
18973 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
18974 - When using the TransPort option on OpenBSD, and using the User
18975 option to change UID and drop privileges, make sure to open
18976 /dev/pf before dropping privileges. Fixes bug 782. Patch from
18977 Christopher Davis. Bugfix on 0.1.2.1-alpha.
18978 - Try to attach connections immediately upon receiving a RENDEZVOUS2
18979 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
18980 on the client side when connecting to a hidden service. Bugfix
18981 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
18982 - When closing an application-side connection because its circuit is
18983 getting torn down, generate the stream event correctly. Bugfix on
18984 0.1.2.x. Anonymous patch.
18987 Changes in version 0.2.0.30 - 2008-07-15
18988 This new stable release switches to a more efficient directory
18989 distribution design, adds features to make connections to the Tor
18990 network harder to block, allows Tor to act as a DNS proxy, adds separate
18991 rate limiting for relayed traffic to make it easier for clients to
18992 become relays, fixes a variety of potential anonymity problems, and
18993 includes the usual huge pile of other features and bug fixes.
18995 o New v3 directory design:
18996 - Tor now uses a new way to learn about and distribute information
18997 about the network: the directory authorities vote on a common
18998 network status document rather than each publishing their own
18999 opinion. Now clients and caches download only one networkstatus
19000 document to bootstrap, rather than downloading one for each
19001 authority. Clients only download router descriptors listed in
19002 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
19004 - Set up moria1, tor26, and dizum as v3 directory authorities
19005 in addition to being v2 authorities. Also add three new ones:
19006 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
19007 dannenberg (run by CCC).
19008 - Switch to multi-level keys for directory authorities: now their
19009 long-term identity key can be kept offline, and they periodically
19010 generate a new signing key. Clients fetch the "key certificates"
19011 to keep up to date on the right keys. Add a standalone tool
19012 "tor-gencert" to generate key certificates. Implements proposal 103.
19013 - Add a new V3AuthUseLegacyKey config option to make it easier for
19014 v3 authorities to change their identity keys if another bug like
19015 Debian's OpenSSL RNG flaw appears.
19016 - Authorities and caches fetch the v2 networkstatus documents
19017 less often, now that v3 is recommended.
19019 o Make Tor connections stand out less on the wire:
19020 - Use an improved TLS handshake designed by Steven Murdoch in proposal
19021 124, as revised in proposal 130. The new handshake is meant to
19022 be harder for censors to fingerprint, and it adds the ability
19023 to detect certain kinds of man-in-the-middle traffic analysis
19024 attacks. The new handshake format includes version negotiation for
19025 OR connections as described in proposal 105, which will allow us
19026 to improve Tor's link protocol more safely in the future.
19027 - Enable encrypted directory connections by default for non-relays,
19028 so censor tools that block Tor directory connections based on their
19029 plaintext patterns will no longer work. This means Tor works in
19030 certain censored countries by default again.
19031 - Stop including recognizeable strings in the commonname part of
19032 Tor's x509 certificates.
19034 o Implement bridge relays:
19035 - Bridge relays (or "bridges" for short) are Tor relays that aren't
19036 listed in the main Tor directory. Since there is no complete public
19037 list of them, even an ISP that is filtering connections to all the
19038 known Tor relays probably won't be able to block all the bridges.
19039 See doc/design-paper/blocking.pdf and proposal 125 for details.
19040 - New config option BridgeRelay that specifies you want to be a
19041 bridge relay rather than a normal relay. When BridgeRelay is set
19042 to 1, then a) you cache dir info even if your DirPort ins't on,
19043 and b) the default for PublishServerDescriptor is now "bridge"
19044 rather than "v2,v3".
19045 - New config option "UseBridges 1" for clients that want to use bridge
19046 relays instead of ordinary entry guards. Clients then specify
19047 bridge relays by adding "Bridge" lines to their config file. Users
19048 can learn about a bridge relay either manually through word of
19049 mouth, or by one of our rate-limited mechanisms for giving out
19050 bridge addresses without letting an attacker easily enumerate them
19051 all. See https://www.torproject.org/bridges for details.
19052 - Bridge relays behave like clients with respect to time intervals
19053 for downloading new v3 consensus documents -- otherwise they
19054 stand out. Bridge users now wait until the end of the interval,
19055 so their bridge relay will be sure to have a new consensus document.
19057 o Implement bridge directory authorities:
19058 - Bridge authorities are like normal directory authorities, except
19059 they don't serve a list of known bridges. Therefore users that know
19060 a bridge's fingerprint can fetch a relay descriptor for that bridge,
19061 including fetching updates e.g. if the bridge changes IP address,
19062 yet an attacker can't just fetch a list of all the bridges.
19063 - Set up Tonga as the default bridge directory authority.
19064 - Bridge authorities refuse to serve bridge descriptors or other
19065 bridge information over unencrypted connections (that is, when
19066 responding to direct DirPort requests rather than begin_dir cells.)
19067 - Bridge directory authorities do reachability testing on the
19068 bridges they know. They provide router status summaries to the
19069 controller via "getinfo ns/purpose/bridge", and also dump summaries
19070 to a file periodically, so we can keep internal stats about which
19071 bridges are functioning.
19072 - If bridge users set the UpdateBridgesFromAuthority config option,
19073 but the digest they ask for is a 404 on the bridge authority,
19074 they fall back to contacting the bridge directly.
19075 - Bridges always use begin_dir to publish their server descriptor to
19076 the bridge authority using an anonymous encrypted tunnel.
19077 - Early work on a "bridge community" design: if bridge authorities set
19078 the BridgePassword config option, they will serve a snapshot of
19079 known bridge routerstatuses from their DirPort to anybody who
19080 knows that password. Unset by default.
19081 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
19082 report sanitized aggregated summaries in their extra-info documents
19083 privately to the bridge authority, listing which countries are
19084 able to reach them. We hope this mechanism will let us learn when
19085 certain countries start trying to block bridges.
19086 - Bridge authorities write bridge descriptors to disk, so they can
19087 reload them after a reboot. They can also export the descriptors
19088 to other programs, so we can distribute them to blocked users via
19089 the BridgeDB interface, e.g. via https://bridges.torproject.org/
19090 and bridges@torproject.org.
19092 o Tor can be a DNS proxy:
19093 - The new client-side DNS proxy feature replaces the need for
19094 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
19095 for DNS requests on port 9999, use the Tor network to resolve them
19096 anonymously, and send the reply back like a regular DNS server.
19097 The code still only implements a subset of DNS.
19098 - Add a new AutomapHostsOnResolve option: when it is enabled, any
19099 resolve request for hosts matching a given pattern causes Tor to
19100 generate an internal virtual address mapping for that host. This
19101 allows DNSPort to work sensibly with hidden service users. By
19102 default, .exit and .onion addresses are remapped; the list of
19103 patterns can be reconfigured with AutomapHostsSuffixes.
19104 - Add an "-F" option to tor-resolve to force a resolve for a .onion
19105 address. Thanks to the AutomapHostsOnResolve option, this is no
19106 longer a completely silly thing to do.
19108 o Major features (relay usability):
19109 - New config options RelayBandwidthRate and RelayBandwidthBurst:
19110 a separate set of token buckets for relayed traffic. Right now
19111 relayed traffic is defined as answers to directory requests, and
19112 OR connections that don't have any local circuits on them. See
19113 proposal 111 for details.
19114 - Create listener connections before we setuid to the configured
19115 User and Group. Now non-Windows users can choose port values
19116 under 1024, start Tor as root, and have Tor bind those ports
19117 before it changes to another UID. (Windows users could already
19119 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
19120 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
19121 on "vserver" accounts. Patch from coderman.
19123 o Major features (directory authorities):
19124 - Directory authorities track weighted fractional uptime and weighted
19125 mean-time-between failures for relays. WFU is suitable for deciding
19126 whether a node is "usually up", while MTBF is suitable for deciding
19127 whether a node is "likely to stay up." We need both, because
19128 "usually up" is a good requirement for guards, while "likely to
19129 stay up" is a good requirement for long-lived connections.
19130 - Directory authorities use a new formula for selecting which relays
19131 to advertise as Guards: they must be in the top 7/8 in terms of
19132 how long we have known about them, and above the median of those
19133 nodes in terms of weighted fractional uptime.
19134 - Directory authorities use a new formula for selecting which relays
19135 to advertise as Stable: when we have 4 or more days of data, use
19136 median measured MTBF rather than median declared uptime. Implements
19138 - Directory authorities accept and serve "extra info" documents for
19139 routers. Routers now publish their bandwidth-history lines in the
19140 extra-info docs rather than the main descriptor. This step saves
19141 60% (!) on compressed router descriptor downloads. Servers upload
19142 extra-info docs to any authority that accepts them; directory
19143 authorities now allow multiple router descriptors and/or extra
19144 info documents to be uploaded in a single go. Authorities, and
19145 caches that have been configured to download extra-info documents,
19146 download them as needed. Implements proposal 104.
19147 - Authorities now list relays who have the same nickname as
19148 a different named relay, but list them with a new flag:
19149 "Unnamed". Now we can make use of relays that happen to pick the
19150 same nickname as a server that registered two years ago and then
19151 disappeared. Implements proposal 122.
19152 - Store routers in a file called cached-descriptors instead of in
19153 cached-routers. Initialize cached-descriptors from cached-routers
19154 if the old format is around. The new format allows us to store
19155 annotations along with descriptors, to record the time we received
19156 each descriptor, its source, and its purpose: currently one of
19157 general, controller, or bridge.
19159 o Major features (other):
19160 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
19161 Tor can warn and/or refuse connections to ports commonly used with
19162 vulnerable-plaintext protocols. Currently we warn on ports 23,
19163 109, 110, and 143, but we don't reject any. Based on proposal 129
19164 by Kevin Bauer and Damon McCoy.
19165 - Integrate Karsten Loesing's Google Summer of Code project to publish
19166 hidden service descriptors on a set of redundant relays that are a
19167 function of the hidden service address. Now we don't have to rely
19168 on three central hidden service authorities for publishing and
19169 fetching every hidden service descriptor. Implements proposal 114.
19170 - Allow tunnelled directory connections to ask for an encrypted
19171 "begin_dir" connection or an anonymized "uses a full Tor circuit"
19172 connection independently. Now we can make anonymized begin_dir
19173 connections for (e.g.) more secure hidden service posting and
19176 o Major bugfixes (crashes and assert failures):
19177 - Stop imposing an arbitrary maximum on the number of file descriptors
19178 used for busy servers. Bug reported by Olaf Selke; patch from
19180 - Avoid possible failures when generating a directory with routers
19181 with over-long versions strings, or too many flags set.
19182 - Fix a rare assert error when we're closing one of our threads:
19183 use a mutex to protect the list of logs, so we never write to the
19184 list as it's being freed. Fixes the very rare bug 575, which is
19185 kind of the revenge of bug 222.
19186 - Avoid segfault in the case where a badly behaved v2 versioning
19187 directory sends a signed networkstatus with missing client-versions.
19188 - When we hit an EOF on a log (probably because we're shutting down),
19189 don't try to remove the log from the list: just mark it as
19190 unusable. (Bulletproofs against bug 222.)
19192 o Major bugfixes (code security fixes):
19193 - Detect size overflow in zlib code. Reported by Justin Ferguson and
19195 - Rewrite directory tokenization code to never run off the end of
19196 a string. Fixes bug 455. Patch from croup.
19197 - Be more paranoid about overwriting sensitive memory on free(),
19198 as a defensive programming tactic to ensure forward secrecy.
19200 o Major bugfixes (anonymity fixes):
19201 - Reject requests for reverse-dns lookup of names that are in
19202 a private address space. Patch from lodger.
19203 - Never report that we've used more bandwidth than we're willing to
19204 relay: it leaks how much non-relay traffic we're using. Resolves
19206 - As a client, do not believe any server that tells us that an
19207 address maps to an internal address space.
19208 - Warn about unsafe ControlPort configurations.
19209 - Directory authorities now call routers Fast if their bandwidth is
19210 at least 100KB/s, and consider their bandwidth adequate to be a
19211 Guard if it is at least 250KB/s, no matter the medians. This fix
19212 complements proposal 107.
19213 - Directory authorities now never mark more than 2 servers per IP as
19214 Valid and Running (or 5 on addresses shared by authorities).
19215 Implements proposal 109, by Kevin Bauer and Damon McCoy.
19216 - If we're a relay, avoid picking ourselves as an introduction point,
19217 a rendezvous point, or as the final hop for internal circuits. Bug
19218 reported by taranis and lodger.
19219 - Exit relays that are used as a client can now reach themselves
19220 using the .exit notation, rather than just launching an infinite
19221 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
19222 - Fix a bug where, when we were choosing the 'end stream reason' to
19223 put in our relay end cell that we send to the exit relay, Tor
19224 clients on Windows were sometimes sending the wrong 'reason'. The
19225 anonymity problem is that exit relays may be able to guess whether
19226 the client is running Windows, thus helping partition the anonymity
19227 set. Down the road we should stop sending reasons to exit relays,
19228 or otherwise prevent future versions of this bug.
19229 - Only update guard status (usable / not usable) once we have
19230 enough directory information. This was causing us to discard all our
19231 guards on startup if we hadn't been running for a few weeks. Fixes
19233 - When our directory information has been expired for a while, stop
19234 being willing to build circuits using it. Fixes bug 401.
19236 o Major bugfixes (peace of mind for relay operators)
19237 - Non-exit relays no longer answer "resolve" relay cells, so they
19238 can't be induced to do arbitrary DNS requests. (Tor clients already
19239 avoid using non-exit relays for resolve cells, but now servers
19240 enforce this too.) Fixes bug 619. Patch from lodger.
19241 - When we setconf ClientOnly to 1, close any current OR and Dir
19242 listeners. Reported by mwenge.
19244 o Major bugfixes (other):
19245 - If we only ever used Tor for hidden service lookups or posts, we
19246 would stop building circuits and start refusing connections after
19247 24 hours, since we falsely believed that Tor was dormant. Reported
19249 - Add a new __HashedControlSessionPassword option for controllers
19250 to use for one-off session password hashes that shouldn't get
19251 saved to disk by SAVECONF --- Vidalia users were accumulating a
19252 pile of HashedControlPassword lines in their torrc files, one for
19253 each time they had restarted Tor and then clicked Save. Make Tor
19254 automatically convert "HashedControlPassword" to this new option but
19255 only when it's given on the command line. Partial fix for bug 586.
19256 - Patch from "Andrew S. Lists" to catch when we contact a directory
19257 mirror at IP address X and he says we look like we're coming from
19258 IP address X. Otherwise this would screw up our address detection.
19259 - Reject uploaded descriptors and extrainfo documents if they're
19260 huge. Otherwise we'll cache them all over the network and it'll
19261 clog everything up. Suggested by Aljosha Judmayer.
19262 - When a hidden service was trying to establish an introduction point,
19263 and Tor *did* manage to reuse one of the preemptively built
19264 circuits, it didn't correctly remember which one it used,
19265 so it asked for another one soon after, until there were no
19266 more preemptive circuits, at which point it launched one from
19267 scratch. Bugfix on 0.0.9.x.
19269 o Rate limiting and load balancing improvements:
19270 - When we add data to a write buffer in response to the data on that
19271 write buffer getting low because of a flush, do not consider the
19272 newly added data as a candidate for immediate flushing, but rather
19273 make it wait until the next round of writing. Otherwise, we flush
19274 and refill recursively, and a single greedy TLS connection can
19275 eat all of our bandwidth.
19276 - When counting the number of bytes written on a TLS connection,
19277 look at the BIO actually used for writing to the network, not
19278 at the BIO used (sometimes) to buffer data for the network.
19279 Looking at different BIOs could result in write counts on the
19280 order of ULONG_MAX. Fixes bug 614.
19281 - If we change our MaxAdvertisedBandwidth and then reload torrc,
19282 Tor won't realize it should publish a new relay descriptor. Fixes
19283 bug 688, reported by mfr.
19284 - Avoid using too little bandwidth when our clock skips a few seconds.
19285 - Choose which bridge to use proportional to its advertised bandwidth,
19286 rather than uniformly at random. This should speed up Tor for
19287 bridge users. Also do this for people who set StrictEntryNodes.
19289 o Bootstrapping faster and building circuits more intelligently:
19290 - Fix bug 660 that was preventing us from knowing that we should
19291 preemptively build circuits to handle expected directory requests.
19292 - When we're checking if we have enough dir info for each relay
19293 to begin establishing circuits, make sure that we actually have
19294 the descriptor listed in the consensus, not just any descriptor.
19295 - Correctly notify one-hop connections when a circuit build has
19296 failed. Possible fix for bug 669. Found by lodger.
19297 - Clients now hold circuitless TLS connections open for 1.5 times
19298 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
19299 rebuild a new circuit over them within that timeframe. Previously,
19300 they held them open only for KeepalivePeriod (5 minutes).
19302 o Performance improvements (memory):
19303 - Add OpenBSD malloc code from "phk" as an optional malloc
19304 replacement on Linux: some glibc libraries do very poorly with
19305 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
19306 ./configure to get the replacement malloc code.
19307 - Switch our old ring buffer implementation for one more like that
19308 used by free Unix kernels. The wasted space in a buffer with 1mb
19309 of data will now be more like 8k than 1mb. The new implementation
19310 also avoids realloc();realloc(); patterns that can contribute to
19311 memory fragmentation.
19312 - Change the way that Tor buffers data that it is waiting to write.
19313 Instead of queueing data cells in an enormous ring buffer for each
19314 client->OR or OR->OR connection, we now queue cells on a separate
19315 queue for each circuit. This lets us use less slack memory, and
19316 will eventually let us be smarter about prioritizing different kinds
19318 - Reference-count and share copies of address policy entries; only 5%
19319 of them were actually distinct.
19320 - Tune parameters for cell pool allocation to minimize amount of
19322 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
19323 for every single inactive connection_t. Free items from the
19324 4k/16k-buffer free lists when they haven't been used for a while.
19325 - Make memory debugging information describe more about history
19326 of cell allocation, so we can help reduce our memory use.
19327 - Be even more aggressive about releasing RAM from small
19328 empty buffers. Thanks to our free-list code, this shouldn't be too
19329 performance-intensive.
19330 - Log malloc statistics from mallinfo() on platforms where it exists.
19331 - Use memory pools to allocate cells with better speed and memory
19332 efficiency, especially on platforms where malloc() is inefficient.
19333 - Add a --with-tcmalloc option to the configure script to link
19334 against tcmalloc (if present). Does not yet search for non-system
19337 o Performance improvements (socket management):
19338 - Count the number of open sockets separately from the number of
19339 active connection_t objects. This will let us avoid underusing
19340 our allocated connection limit.
19341 - We no longer use socket pairs to link an edge connection to an
19342 anonymous directory connection or a DirPort test connection.
19343 Instead, we track the link internally and transfer the data
19344 in-process. This saves two sockets per "linked" connection (at the
19345 client and at the server), and avoids the nasty Windows socketpair()
19347 - We were leaking a file descriptor if Tor started with a zero-length
19348 cached-descriptors file. Patch by "freddy77".
19350 o Performance improvements (CPU use):
19351 - Never walk through the list of logs if we know that no log target
19352 is interested in a given message.
19353 - Call routerlist_remove_old_routers() much less often. This should
19354 speed startup, especially on directory caches.
19355 - Base64 decoding was actually showing up on our profile when parsing
19356 the initial descriptor file; switch to an in-process all-at-once
19357 implementation that's about 3.5x times faster than calling out to
19359 - Use a slightly simpler string hashing algorithm (copying Python's
19360 instead of Java's) and optimize our digest hashing algorithm to take
19361 advantage of 64-bit platforms and to remove some possibly-costly
19363 - When implementing AES counter mode, update only the portions of the
19364 counter buffer that need to change, and don't keep separate
19365 network-order and host-order counters on big-endian hosts (where
19366 they are the same).
19367 - Add an in-place version of aes_crypt() so that we can avoid doing a
19368 needless memcpy() call on each cell payload.
19369 - Use Critical Sections rather than Mutexes for synchronizing threads
19370 on win32; Mutexes are heavier-weight, and designed for synchronizing
19373 o Performance improvements (bandwidth use):
19374 - Don't try to launch new descriptor downloads quite so often when we
19375 already have enough directory information to build circuits.
19376 - Version 1 directories are no longer generated in full. Instead,
19377 authorities generate and serve "stub" v1 directories that list
19378 no servers. This will stop Tor versions 0.1.0.x and earlier from
19379 working, but (for security reasons) nobody should be running those
19381 - Avoid going directly to the directory authorities even if you're a
19382 relay, if you haven't found yourself reachable yet or if you've
19383 decided not to advertise your dirport yet. Addresses bug 556.
19384 - If we've gone 12 hours since our last bandwidth check, and we
19385 estimate we have less than 50KB bandwidth capacity but we could
19386 handle more, do another bandwidth test.
19387 - Support "If-Modified-Since" when answering HTTP requests for
19388 directories, running-routers documents, and v2 and v3 networkstatus
19389 documents. (There's no need to support it for router descriptors,
19390 since those are downloaded by descriptor digest.)
19391 - Stop fetching directory info so aggressively if your DirPort is
19392 on but your ORPort is off; stop fetching v2 dir info entirely.
19393 You can override these choices with the new FetchDirInfoEarly
19396 o Changed config option behavior (features):
19397 - Configuration files now accept C-style strings as values. This
19398 helps encode characters not allowed in the current configuration
19399 file format, such as newline or #. Addresses bug 557.
19400 - Add hidden services and DNSPorts to the list of things that make
19401 Tor accept that it has running ports. Change starting Tor with no
19402 ports from a fatal error to a warning; we might change it back if
19403 this turns out to confuse anybody. Fixes bug 579.
19404 - Make PublishServerDescriptor default to 1, so the default doesn't
19405 have to change as we invent new directory protocol versions.
19406 - Allow people to say PreferTunnelledDirConns rather than
19407 PreferTunneledDirConns, for those alternate-spellers out there.
19408 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
19409 accommodate the growing number of servers that use the default
19410 and are reaching it.
19411 - Make it possible to enable HashedControlPassword and
19412 CookieAuthentication at the same time.
19413 - When a TrackHostExits-chosen exit fails too many times in a row,
19414 stop using it. Fixes bug 437.
19416 o Changed config option behavior (bugfixes):
19417 - Do not read the configuration file when we've only been told to
19418 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
19419 based on patch from Sebastian Hahn.
19420 - Actually validate the options passed to AuthDirReject,
19421 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
19422 - Make "ClientOnly 1" config option disable directory ports too.
19423 - Don't stop fetching descriptors when FetchUselessDescriptors is
19424 set, even if we stop asking for circuits. Bug reported by tup
19426 - Servers used to decline to publish their DirPort if their
19427 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
19428 they look only at BandwidthRate and RelayBandwidthRate.
19429 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
19430 minus 1 byte: the actual maximum declared bandwidth.
19431 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
19432 - Make the NodeFamilies config option work. (Reported by
19433 lodger -- it has never actually worked, even though we added it
19435 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
19436 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
19438 o New config options:
19439 - New configuration options AuthDirMaxServersPerAddr and
19440 AuthDirMaxServersperAuthAddr to override default maximum number
19441 of servers allowed on a single IP address. This is important for
19442 running a test network on a single host.
19443 - Three new config options (AlternateDirAuthority,
19444 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
19445 user selectively replace the default directory authorities by type,
19446 rather than the all-or-nothing replacement that DirServer offers.
19447 - New config options AuthDirBadDir and AuthDirListBadDirs for
19448 authorities to mark certain relays as "bad directories" in the
19449 networkstatus documents. Also supports the "!baddir" directive in
19450 the approved-routers file.
19451 - New config option V2AuthoritativeDirectory that all v2 directory
19452 authorities must set. This lets v3 authorities choose not to serve
19453 v2 directory information.
19455 o Minor features (other):
19456 - When we're not serving v2 directory information, there is no reason
19457 to actually keep any around. Remove the obsolete files and directory
19458 on startup if they are very old and we aren't going to serve them.
19459 - When we negotiate a v2 link-layer connection (not yet implemented),
19460 accept RELAY_EARLY cells and turn them into RELAY cells if we've
19461 negotiated a v1 connection for their next step. Initial steps for
19463 - When we have no consensus, check FallbackNetworkstatusFile (defaults
19464 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
19465 we can start out knowing some directory caches. We don't ship with
19466 a fallback consensus by default though, because it was making
19467 bootstrapping take too long while we tried many down relays.
19468 - Authorities send back an X-Descriptor-Not-New header in response to
19469 an accepted-but-discarded descriptor upload. Partially implements
19471 - If we find a cached-routers file that's been sitting around for more
19472 than 28 days unmodified, then most likely it's a leftover from
19473 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
19475 - When we (as a cache) download a descriptor because it was listed
19476 in a consensus, remember when the consensus was supposed to expire,
19477 and don't expire the descriptor until then.
19478 - Optionally (if built with -DEXPORTMALLINFO) export the output
19479 of mallinfo via http, as tor/mallinfo.txt. Only accessible
19481 - Tag every guard node in our state file with the version that
19482 we believe added it, or with our own version if we add it. This way,
19483 if a user temporarily runs an old version of Tor and then switches
19484 back to a new one, she doesn't automatically lose her guards.
19485 - When somebody requests a list of statuses or servers, and we have
19486 none of those, return a 404 rather than an empty 200.
19487 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
19489 - Add an HSAuthorityRecordStats option that hidden service authorities
19490 can use to track statistics of overall hidden service usage without
19491 logging information that would be as useful to an attacker.
19492 - Allow multiple HiddenServicePort directives with the same virtual
19493 port; when they occur, the user is sent round-robin to one
19494 of the target ports chosen at random. Partially fixes bug 393 by
19495 adding limited ad-hoc round-robining.
19496 - Revamp file-writing logic so we don't need to have the entire
19497 contents of a file in memory at once before we write to disk. Tor,
19500 o Minor bugfixes (other):
19501 - Alter the code that tries to recover from unhandled write
19502 errors, to not try to flush onto a socket that's given us
19504 - Directory mirrors no longer include a guess at the client's IP
19505 address if the connection appears to be coming from the same /24
19506 network; it was producing too many wrong guesses.
19507 - If we're trying to flush the last bytes on a connection (for
19508 example, when answering a directory request), reset the
19509 time-to-give-up timeout every time we manage to write something
19511 - Reject router descriptors with out-of-range bandwidthcapacity or
19512 bandwidthburst values.
19513 - If we can't expand our list of entry guards (e.g. because we're
19514 using bridges or we have StrictEntryNodes set), don't mark relays
19515 down when they fail a directory request. Otherwise we're too quick
19516 to mark all our entry points down.
19517 - Authorities no longer send back "400 you're unreachable please fix
19518 it" errors to Tor servers that aren't online all the time. We're
19519 supposed to tolerate these servers now.
19520 - Let directory authorities startup even when they can't generate
19521 a descriptor immediately, e.g. because they don't know their
19523 - Correctly enforce that elements of directory objects do not appear
19524 more often than they are allowed to appear.
19525 - Stop allowing hibernating servers to be "stable" or "fast".
19526 - On Windows, we were preventing other processes from reading
19527 cached-routers while Tor was running. (Reported by janbar)
19528 - Check return values from pthread_mutex functions.
19529 - When opening /dev/null in finish_daemonize(), do not pass the
19530 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
19531 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
19533 o Controller features:
19534 - The GETCONF command now escapes and quotes configuration values
19535 that don't otherwise fit into the torrc file.
19536 - The SETCONF command now handles quoted values correctly.
19537 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
19538 ask about source, timestamp of arrival, purpose, etc. We need
19539 something like this to help Vidalia not do GeoIP lookups on bridge
19541 - Allow multiple HashedControlPassword config lines, to support
19542 multiple controller passwords.
19543 - Accept LF instead of CRLF on controller, since some software has a
19544 hard time generating real Internet newlines.
19545 - Add GETINFO values for the server status events
19546 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
19548 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
19549 GETINFO for Torstat to use until it can switch to using extrainfos.
19550 - New config option CookieAuthFile to choose a new location for the
19551 cookie authentication file, and config option
19552 CookieAuthFileGroupReadable to make it group-readable.
19553 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
19554 match requests to applications. Patch from Robert Hogan.
19555 - Add a RESOLVE command to launch hostname lookups. Original patch
19557 - Add GETINFO status/enough-dir-info to let controllers tell whether
19558 Tor has downloaded sufficient directory information. Patch from Tup.
19559 - You can now use the ControlSocket option to tell Tor to listen for
19560 controller connections on Unix domain sockets on systems that
19561 support them. Patch from Peter Palfrader.
19562 - New "GETINFO address-mappings/*" command to get address mappings
19563 with expiry information. "addr-mappings/*" is now deprecated.
19565 - Add a new config option __DisablePredictedCircuits designed for
19566 use by the controller, when we don't want Tor to build any circuits
19568 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
19569 so we can exit from the middle of the circuit.
19570 - Implement "getinfo status/circuit-established".
19571 - Implement "getinfo status/version/..." so a controller can tell
19572 whether the current version is recommended, and whether any versions
19573 are good, and how many authorities agree. Patch from "shibz".
19574 - Controllers should now specify cache=no or cache=yes when using
19575 the +POSTDESCRIPTOR command.
19576 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
19577 Robert Hogan. Fixes the first part of bug 681.
19578 - When reporting clock skew, and we know that the clock is _at least
19579 as skewed_ as some value, but we don't know the actual value,
19580 report the value as a "minimum skew."
19582 o Controller bugfixes:
19583 - Generate "STATUS_SERVER" events rather than misspelled
19584 "STATUS_SEVER" events. Caught by mwenge.
19585 - Reject controller commands over 1MB in length, so rogue
19586 processes can't run us out of memory.
19587 - Change the behavior of "getinfo status/good-server-descriptor"
19588 so it doesn't return failure when any authority disappears.
19589 - Send NAMESERVER_STATUS messages for a single failed nameserver
19591 - When the DANGEROUS_VERSION controller status event told us we're
19592 running an obsolete version, it used the string "OLD" to describe
19593 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
19594 "OBSOLETE" in both cases.
19595 - Respond to INT and TERM SIGNAL commands before we execute the
19596 signal, in case the signal shuts us down. We had a patch in
19597 0.1.2.1-alpha that tried to do this by queueing the response on
19598 the connection's buffer before shutting down, but that really
19599 isn't the same thing at all. Bug located by Matt Edman.
19600 - Provide DNS expiry times in GMT, not in local time. For backward
19601 compatibility, ADDRMAP events only provide GMT expiry in an extended
19602 field. "GETINFO address-mappings" always does the right thing.
19603 - Use CRLF line endings properly in NS events.
19604 - Make 'getinfo fingerprint' return a 551 error if we're not a
19605 server, so we match what the control spec claims we do. Reported
19607 - Fix a typo in an error message when extendcircuit fails that
19608 caused us to not follow the \r\n-based delimiter protocol. Reported
19610 - When tunneling an encrypted directory connection, and its first
19611 circuit fails, do not leave it unattached and ask the controller
19612 to deal. Fixes the second part of bug 681.
19613 - Treat some 403 responses from directory servers as INFO rather than
19614 WARN-severity events.
19616 o Portability / building / compiling:
19617 - When building with --enable-gcc-warnings, check for whether Apple's
19618 warning "-Wshorten-64-to-32" is available.
19619 - Support compilation to target iPhone; patch from cjacker huang.
19620 To build for iPhone, pass the --enable-iphone option to configure.
19621 - Port Tor to build and run correctly on Windows CE systems, using
19622 the wcecompat library. Contributed by Valerio Lupi.
19623 - Detect non-ASCII platforms (if any still exist) and refuse to
19624 build there: some of our code assumes that 'A' is 65 and so on.
19625 - Clear up some MIPSPro compiler warnings.
19626 - Make autoconf search for libevent, openssl, and zlib consistently.
19627 - Update deprecated macros in configure.in.
19628 - When warning about missing headers, tell the user to let us
19629 know if the compile succeeds anyway, so we can downgrade the
19631 - Include the current subversion revision as part of the version
19632 string: either fetch it directly if we're in an SVN checkout, do
19633 some magic to guess it if we're in an SVK checkout, or use
19634 the last-detected version if we're building from a .tar.gz.
19635 Use this version consistently in log messages.
19636 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
19637 - Read resolv.conf files correctly on platforms where read() returns
19638 partial results on small file reads.
19639 - Build without verbose warnings even on gcc 4.2 and 4.3.
19640 - On Windows, correctly detect errors when listing the contents of
19641 a directory. Fix from lodger.
19642 - Run 'make test' as part of 'make dist', so we stop releasing so
19643 many development snapshots that fail their unit tests.
19644 - Add support to detect Libevent versions in the 1.4.x series
19646 - Add command-line arguments to unit-test executable so that we can
19647 invoke any chosen test from the command line rather than having
19648 to run the whole test suite at once; and so that we can turn on
19649 logging for the unit tests.
19650 - Do not automatically run configure from autogen.sh. This
19651 non-standard behavior tended to annoy people who have built other
19653 - Fix a macro/CPP interaction that was confusing some compilers:
19654 some GCCs don't like #if/#endif pairs inside macro arguments.
19656 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
19657 Fixes bug 704; fix from Steven Murdoch.
19658 - Correctly detect transparent proxy support on Linux hosts that
19659 require in.h to be included before netfilter_ipv4.h. Patch
19662 o Logging improvements:
19663 - When we haven't had any application requests lately, don't bother
19664 logging that we have expired a bunch of descriptors.
19665 - When attempting to open a logfile fails, tell us why.
19666 - Only log guard node status when guard node status has changed.
19667 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
19668 make "INFO" 75% less verbose.
19669 - When SafeLogging is disabled, log addresses along with all TLS
19671 - Report TLS "zero return" case as a "clean close" and "IO error"
19672 as a "close". Stop calling closes "unexpected closes": existing
19673 Tors don't use SSL_close(), so having a connection close without
19674 the TLS shutdown handshake is hardly unexpected.
19675 - When we receive a consensus from the future, warn about skew.
19676 - Make "not enough dir info yet" warnings describe *why* Tor feels
19677 it doesn't have enough directory info yet.
19678 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
19679 consumers. (We already do this on HUP.)
19680 - Give more descriptive well-formedness errors for out-of-range
19681 hidden service descriptor/protocol versions.
19682 - Stop recommending that every server operator send mail to tor-ops.
19683 Resolves bug 597. Bugfix on 0.1.2.x.
19684 - Improve skew reporting: try to give the user a better log message
19685 about how skewed they are, and how much this matters.
19686 - New --quiet command-line option to suppress the default console log.
19687 Good in combination with --hash-password.
19688 - Don't complain that "your server has not managed to confirm that its
19689 ports are reachable" if we haven't been able to build any circuits
19691 - Detect the reason for failing to mmap a descriptor file we just
19692 wrote, and give a more useful log message. Fixes bug 533.
19693 - Always prepend "Bug: " to any log message about a bug.
19694 - When dumping memory usage, list bytes used in buffer memory
19696 - When running with dmalloc, dump more stats on hup and on exit.
19697 - Put a platform string (e.g. "Linux i686") in the startup log
19698 message, so when people paste just their logs, we know if it's
19699 OpenBSD or Windows or what.
19700 - When logging memory usage, break down memory used in buffers by
19702 - When we are reporting the DirServer line we just parsed, we were
19703 logging the second stanza of the key fingerprint, not the first.
19704 - Even though Windows is equally happy with / and \ as path separators,
19705 try to use \ consistently on Windows and / consistently on Unix: it
19706 makes the log messages nicer.
19707 - On OSX, stop warning the user that kqueue support in libevent is
19708 "experimental", since it seems to have worked fine for ages.
19710 o Contributed scripts and tools:
19711 - Update linux-tor-prio.sh script to allow QoS based on the uid of
19712 the Tor process. Patch from Marco Bonetti with tweaks from Mike
19714 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
19715 Unix users an easy way to script their Tor process (e.g. by
19716 adjusting bandwidth based on the time of the day).
19717 - In the exitlist script, only consider the most recently published
19718 server descriptor for each server. Also, when the user requests
19719 a list of servers that _reject_ connections to a given address,
19720 explicitly exclude the IPs that also have servers that accept
19721 connections to that address. Resolves bug 405.
19722 - Include a new contrib/tor-exit-notice.html file that exit relay
19723 operators can put on their website to help reduce abuse queries.
19725 o Newly deprecated features:
19726 - The status/version/num-versioning and status/version/num-concurring
19727 GETINFO controller options are no longer useful in the v3 directory
19728 protocol: treat them as deprecated, and warn when they're used.
19729 - The RedirectExits config option is now deprecated.
19731 o Removed features:
19732 - Drop the old code to choke directory connections when the
19733 corresponding OR connections got full: thanks to the cell queue
19734 feature, OR conns don't get full any more.
19735 - Remove the old "dns worker" server DNS code: it hasn't been default
19736 since 0.1.2.2-alpha, and all the servers are using the new
19738 - Remove the code to generate the oldest (v1) directory format.
19739 - Remove support for the old bw_accounting file: we've been storing
19740 bandwidth accounting information in the state file since
19741 0.1.2.5-alpha. This may result in bandwidth accounting errors
19742 if you try to upgrade from 0.1.1.x or earlier, or if you try to
19743 downgrade to 0.1.1.x or earlier.
19744 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
19745 it, it had no AES, and it hasn't seen any security patches since
19747 - Stop overloading the circuit_t.onionskin field for both "onionskin
19748 from a CREATE cell that we are waiting for a cpuworker to be
19749 assigned" and "onionskin from an EXTEND cell that we are going to
19750 send to an OR as soon as we are connected". Might help with bug 600.
19751 - Remove the tor_strpartition() function: its logic was confused,
19752 and it was only used for one thing that could be implemented far
19754 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
19755 and TorControl.py, as they use the old v0 controller protocol,
19756 and are obsoleted by TorFlow anyway.
19757 - Drop support for v1 rendezvous descriptors, since we never used
19758 them anyway, and the code has probably rotted by now. Based on
19759 patch from Karsten Loesing.
19760 - Stop allowing address masks that do not correspond to bit prefixes.
19761 We have warned about these for a really long time; now it's time
19762 to reject them. (Patch from croup.)
19763 - Remove an optimization in the AES counter-mode code that assumed
19764 that the counter never exceeded 2^68. When the counter can be set
19765 arbitrarily as an IV (as it is by Karsten's new hidden services
19766 code), this assumption no longer holds.
19767 - Disable the SETROUTERPURPOSE controller command: it is now
19771 Changes in version 0.1.2.19 - 2008-01-17
19772 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
19773 exit policy a little bit more conservative so it's safer to run an
19774 exit relay on a home system, and fixes a variety of smaller issues.
19777 - Exit policies now reject connections that are addressed to a
19778 relay's public (external) IP address too, unless
19779 ExitPolicyRejectPrivate is turned off. We do this because too
19780 many relays are running nearby to services that trust them based
19781 on network address.
19784 - When the clock jumps forward a lot, do not allow the bandwidth
19785 buckets to become negative. Fixes bug 544.
19786 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
19787 on every successful resolve. Reported by Mike Perry.
19788 - Purge old entries from the "rephist" database and the hidden
19789 service descriptor database even when DirPort is zero.
19790 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
19791 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
19792 crashing or mis-answering these requests.
19793 - When we decide to send a 503 response to a request for servers, do
19794 not then also send the server descriptors: this defeats the whole
19795 purpose. Fixes bug 539.
19798 - Changing the ExitPolicyRejectPrivate setting should cause us to
19799 rebuild our server descriptor.
19800 - Fix handling of hex nicknames when answering controller requests for
19801 networkstatus by name, or when deciding whether to warn about
19802 unknown routers in a config option. (Patch from mwenge.)
19803 - Fix a couple of hard-to-trigger autoconf problems that could result
19804 in really weird results on platforms whose sys/types.h files define
19805 nonstandard integer types.
19806 - Don't try to create the datadir when running --verify-config or
19807 --hash-password. Resolves bug 540.
19808 - If we were having problems getting a particular descriptor from the
19809 directory caches, and then we learned about a new descriptor for
19810 that router, we weren't resetting our failure count. Reported
19812 - Although we fixed bug 539 (where servers would send HTTP status 503
19813 responses _and_ send a body too), there are still servers out there
19814 that haven't upgraded. Therefore, make clients parse such bodies
19815 when they receive them.
19816 - Run correctly on systems where rlim_t is larger than unsigned long.
19817 This includes some 64-bit systems.
19818 - Run correctly on platforms (like some versions of OS X 10.5) where
19819 the real limit for number of open files is OPEN_FILES, not rlim_max
19820 from getrlimit(RLIMIT_NOFILES).
19821 - Avoid a spurious free on base64 failure.
19822 - Avoid segfaults on certain complex invocations of
19823 router_get_by_hexdigest().
19824 - Fix rare bug on REDIRECTSTREAM control command when called with no
19825 port set: it could erroneously report an error when none had
19829 Changes in version 0.1.2.18 - 2007-10-28
19830 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
19831 hidden service introduction that were causing huge delays, and a big
19832 bug that was causing some servers to disappear from the network status
19833 lists for a few hours each day.
19835 o Major bugfixes (crashes):
19836 - If a connection is shut down abruptly because of something that
19837 happened inside connection_flushed_some(), do not call
19838 connection_finished_flushing(). Should fix bug 451:
19839 "connection_stop_writing: Assertion conn->write_event failed"
19840 Bugfix on 0.1.2.7-alpha.
19841 - Fix possible segfaults in functions called from
19842 rend_process_relay_cell().
19844 o Major bugfixes (hidden services):
19845 - Hidden services were choosing introduction points uniquely by
19846 hexdigest, but when constructing the hidden service descriptor
19847 they merely wrote the (potentially ambiguous) nickname.
19848 - Clients now use the v2 intro format for hidden service
19849 connections: they specify their chosen rendezvous point by identity
19850 digest rather than by (potentially ambiguous) nickname. These
19851 changes could speed up hidden service connections dramatically.
19853 o Major bugfixes (other):
19854 - Stop publishing a new server descriptor just because we get a
19855 HUP signal. This led (in a roundabout way) to some servers getting
19856 dropped from the networkstatus lists for a few hours each day.
19857 - When looking for a circuit to cannibalize, consider family as well
19858 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
19859 circuit cannibalization).
19860 - When a router wasn't listed in a new networkstatus, we were leaving
19861 the flags for that router alone -- meaning it remained Named,
19862 Running, etc -- even though absence from the networkstatus means
19863 that it shouldn't be considered to exist at all anymore. Now we
19864 clear all the flags for routers that fall out of the networkstatus
19865 consensus. Fixes bug 529.
19868 - Don't try to access (or alter) the state file when running
19869 --list-fingerprint or --verify-config or --hash-password. Resolves
19871 - When generating information telling us how to extend to a given
19872 router, do not try to include the nickname if it is
19873 absent. Resolves bug 467.
19874 - Fix a user-triggerable segfault in expand_filename(). (There isn't
19875 a way to trigger this remotely.)
19876 - When sending a status event to the controller telling it that an
19877 OR address is reachable, set the port correctly. (Previously we
19878 were reporting the dir port.)
19879 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
19880 command. Bugfix on 0.1.2.17.
19881 - When loading bandwidth history, do not believe any information in
19882 the future. Fixes bug 434.
19883 - When loading entry guard information, do not believe any information
19885 - When we have our clock set far in the future and generate an
19886 onion key, then re-set our clock to be correct, we should not stop
19887 the onion key from getting rotated.
19888 - On some platforms, accept() can return a broken address. Detect
19889 this more quietly, and deal accordingly. Fixes bug 483.
19890 - It's not actually an error to find a non-pending entry in the DNS
19891 cache when canceling a pending resolve. Don't log unless stuff
19892 is fishy. Resolves bug 463.
19893 - Don't reset trusted dir server list when we set a configuration
19894 option. Patch from Robert Hogan.
19897 Changes in version 0.1.2.17 - 2007-08-30
19898 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
19899 X bundles. Vidalia 0.0.14 makes authentication required for the
19900 ControlPort in the default configuration, which addresses important
19901 security risks. Everybody who uses Vidalia (or another controller)
19904 In addition, this Tor update fixes major load balancing problems with
19905 path selection, which should speed things up a lot once many people
19908 o Major bugfixes (security):
19909 - We removed support for the old (v0) control protocol. It has been
19910 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
19911 become more of a headache than it's worth.
19913 o Major bugfixes (load balancing):
19914 - When choosing nodes for non-guard positions, weight guards
19915 proportionally less, since they already have enough load. Patch
19917 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
19918 will allow fast Tor servers to get more attention.
19919 - When we're upgrading from an old Tor version, forget our current
19920 guards and pick new ones according to the new weightings. These
19921 three load balancing patches could raise effective network capacity
19922 by a factor of four. Thanks to Mike Perry for measurements.
19924 o Major bugfixes (stream expiration):
19925 - Expire not-yet-successful application streams in all cases if
19926 they've been around longer than SocksTimeout. Right now there are
19927 some cases where the stream will live forever, demanding a new
19928 circuit every 15 seconds. Fixes bug 454; reported by lodger.
19930 o Minor features (controller):
19931 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
19932 is valid before any authentication has been received. It tells
19933 a controller what kind of authentication is expected, and what
19934 protocol is spoken. Implements proposal 119.
19936 o Minor bugfixes (performance):
19937 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
19938 greatly speeding up loading cached-routers from disk on startup.
19939 - Disable sentinel-based debugging for buffer code: we squashed all
19940 the bugs that this was supposed to detect a long time ago, and now
19941 its only effect is to change our buffer sizes from nice powers of
19942 two (which platform mallocs tend to like) to values slightly over
19943 powers of two (which make some platform mallocs sad).
19945 o Minor bugfixes (misc):
19946 - If exit bandwidth ever exceeds one third of total bandwidth, then
19947 use the correct formula to weight exit nodes when choosing paths.
19948 Based on patch from Mike Perry.
19949 - Choose perfectly fairly among routers when choosing by bandwidth and
19950 weighting by fraction of bandwidth provided by exits. Previously, we
19951 would choose with only approximate fairness, and correct ourselves
19952 if we ran off the end of the list.
19953 - If we require CookieAuthentication but we fail to write the
19954 cookie file, we would warn but not exit, and end up in a state
19955 where no controller could authenticate. Now we exit.
19956 - If we require CookieAuthentication, stop generating a new cookie
19957 every time we change any piece of our config.
19958 - Refuse to start with certain directory authority keys, and
19959 encourage people using them to stop.
19960 - Terminate multi-line control events properly. Original patch
19962 - Fix a minor memory leak when we fail to find enough suitable
19963 servers to choose a circuit.
19964 - Stop leaking part of the descriptor when we run into a particularly
19965 unparseable piece of it.
19968 Changes in version 0.1.2.16 - 2007-08-01
19969 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
19970 remote attacker in certain situations to rewrite the user's torrc
19971 configuration file. This can completely compromise anonymity of users
19972 in most configurations, including those running the Vidalia bundles,
19973 TorK, etc. Or worse.
19975 o Major security fixes:
19976 - Close immediately after missing authentication on control port;
19977 do not allow multiple authentication attempts.
19980 Changes in version 0.1.2.15 - 2007-07-17
19981 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
19982 problems, fixes compilation on BSD, and fixes a variety of other
19983 bugs. Everybody should upgrade.
19985 o Major bugfixes (compilation):
19986 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
19988 o Major bugfixes (crashes):
19989 - Try even harder not to dereference the first character after
19990 an mmap(). Reported by lodger.
19991 - Fix a crash bug in directory authorities when we re-number the
19992 routerlist while inserting a new router.
19993 - When the cached-routers file is an even multiple of the page size,
19994 don't run off the end and crash. (Fixes bug 455; based on idea
19996 - Fix eventdns.c behavior on Solaris: It is critical to include
19997 orconfig.h _before_ sys/types.h, so that we can get the expected
19998 definition of _FILE_OFFSET_BITS.
20000 o Major bugfixes (security):
20001 - Fix a possible buffer overrun when using BSD natd support. Bug
20003 - When sending destroy cells from a circuit's origin, don't include
20004 the reason for tearing down the circuit. The spec says we didn't,
20005 and now we actually don't. Reported by lodger.
20006 - Keep streamids from different exits on a circuit separate. This
20007 bug may have allowed other routers on a given circuit to inject
20008 cells into streams. Reported by lodger; fixes bug 446.
20009 - If there's a never-before-connected-to guard node in our list,
20010 never choose any guards past it. This way we don't expand our
20011 guard list unless we need to.
20013 o Minor bugfixes (guard nodes):
20014 - Weight guard selection by bandwidth, so that low-bandwidth nodes
20015 don't get overused as guards.
20017 o Minor bugfixes (directory):
20018 - Correctly count the number of authorities that recommend each
20019 version. Previously, we were under-counting by 1.
20020 - Fix a potential crash bug when we load many server descriptors at
20021 once and some of them make others of them obsolete. Fixes bug 458.
20023 o Minor bugfixes (hidden services):
20024 - Stop tearing down the whole circuit when the user asks for a
20025 connection to a port that the hidden service didn't configure.
20028 o Minor bugfixes (misc):
20029 - On Windows, we were preventing other processes from reading
20030 cached-routers while Tor was running. Reported by janbar.
20031 - Fix a possible (but very unlikely) bug in picking routers by
20032 bandwidth. Add a log message to confirm that it is in fact
20033 unlikely. Patch from lodger.
20034 - Backport a couple of memory leak fixes.
20035 - Backport miscellaneous cosmetic bugfixes.
20038 Changes in version 0.1.2.14 - 2007-05-25
20039 Tor 0.1.2.14 changes the addresses of two directory authorities (this
20040 change especially affects those who serve or use hidden services),
20041 and fixes several other crash- and security-related bugs.
20043 o Directory authority changes:
20044 - Two directory authorities (moria1 and moria2) just moved to new
20045 IP addresses. This change will particularly affect those who serve
20046 or use hidden services.
20048 o Major bugfixes (crashes):
20049 - If a directory server runs out of space in the connection table
20050 as it's processing a begin_dir request, it will free the exit stream
20051 but leave it attached to the circuit, leading to unpredictable
20052 behavior. (Reported by seeess, fixes bug 425.)
20053 - Fix a bug in dirserv_remove_invalid() that would cause authorities
20054 to corrupt memory under some really unlikely scenarios.
20055 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
20056 - Avoid segfaults when reading from mmaped descriptor file. (Reported
20059 o Major bugfixes (security):
20060 - When choosing an entry guard for a circuit, avoid using guards
20061 that are in the same family as the chosen exit -- not just guards
20062 that are exactly the chosen exit. (Reported by lodger.)
20064 o Major bugfixes (resource management):
20065 - If a directory authority is down, skip it when deciding where to get
20066 networkstatus objects or descriptors. Otherwise we keep asking
20067 every 10 seconds forever. Fixes bug 384.
20068 - Count it as a failure if we fetch a valid network-status but we
20069 don't want to keep it. Otherwise we'll keep fetching it and keep
20070 not wanting to keep it. Fixes part of bug 422.
20071 - If all of our dirservers have given us bad or no networkstatuses
20072 lately, then stop hammering them once per minute even when we
20073 think they're failed. Fixes another part of bug 422.
20076 - Actually set the purpose correctly for descriptors inserted with
20077 purpose=controller.
20078 - When we have k non-v2 authorities in our DirServer config,
20079 we ignored the last k authorities in the list when updating our
20081 - Correctly back-off from requesting router descriptors that we are
20082 having a hard time downloading.
20083 - Read resolv.conf files correctly on platforms where read() returns
20084 partial results on small file reads.
20085 - Don't rebuild the entire router store every time we get 32K of
20086 routers: rebuild it when the journal gets very large, or when
20087 the gaps in the store get very large.
20090 - When routers publish SVN revisions in their router descriptors,
20091 authorities now include those versions correctly in networkstatus
20093 - Warn when using a version of libevent before 1.3b to run a server on
20094 OSX or BSD: these versions interact badly with userspace threads.
20097 Changes in version 0.1.2.13 - 2007-04-24
20098 This release features some major anonymity fixes, such as safer path
20099 selection; better client performance; faster bootstrapping, better
20100 address detection, and better DNS support for servers; write limiting as
20101 well as read limiting to make servers easier to run; and a huge pile of
20102 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
20104 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
20105 of the Freenode IRC network, remembering his patience and vision for
20106 free speech on the Internet.
20108 o Major features, client performance:
20109 - Weight directory requests by advertised bandwidth. Now we can
20110 let servers enable write limiting but still allow most clients to
20111 succeed at their directory requests. (We still ignore weights when
20112 choosing a directory authority; I hope this is a feature.)
20113 - Stop overloading exit nodes -- avoid choosing them for entry or
20114 middle hops when the total bandwidth available from non-exit nodes
20115 is much higher than the total bandwidth available from exit nodes.
20116 - Rather than waiting a fixed amount of time between retrying
20117 application connections, we wait only 10 seconds for the first,
20118 10 seconds for the second, and 15 seconds for each retry after
20119 that. Hopefully this will improve the expected user experience.
20120 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
20121 to open a stream fails; now we do in more cases. This should
20122 make clients able to find a good exit faster in some cases, since
20123 unhandleable requests will now get an error rather than timing out.
20125 o Major features, client functionality:
20126 - Implement BEGIN_DIR cells, so we can connect to a directory
20127 server via TLS to do encrypted directory requests rather than
20128 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
20129 config options if you like. For now, this feature only works if
20130 you already have a descriptor for the destination dirserver.
20131 - Add support for transparent application connections: this basically
20132 bundles the functionality of trans-proxy-tor into the Tor
20133 mainline. Now hosts with compliant pf/netfilter implementations
20134 can redirect TCP connections straight to Tor without diverting
20135 through SOCKS. (Based on patch from tup.)
20136 - Add support for using natd; this allows FreeBSDs earlier than
20137 5.1.2 to have ipfw send connections through Tor without using
20138 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
20140 o Major features, servers:
20141 - Setting up a dyndns name for your server is now optional: servers
20142 with no hostname or IP address will learn their IP address by
20143 asking the directory authorities. This code only kicks in when you
20144 would normally have exited with a "no address" error. Nothing's
20145 authenticated, so use with care.
20146 - Directory servers now spool server descriptors, v1 directories,
20147 and v2 networkstatus objects to buffers as needed rather than en
20148 masse. They also mmap the cached-routers files. These steps save
20150 - Stop requiring clients to have well-formed certificates, and stop
20151 checking nicknames in certificates. (Clients have certificates so
20152 that they can look like Tor servers, but in the future we might want
20153 to allow them to look like regular TLS clients instead. Nicknames
20154 in certificates serve no purpose other than making our protocol
20155 easier to recognize on the wire.) Implements proposal 106.
20157 o Improvements on DNS support:
20158 - Add "eventdns" asynchronous dns library originally based on code
20159 from Adam Langley. Now we can discard the old rickety dnsworker
20160 concept, and support a wider variety of DNS functions. Allows
20161 multithreaded builds on NetBSD and OpenBSD again.
20162 - Add server-side support for "reverse" DNS lookups (using PTR
20163 records so clients can determine the canonical hostname for a given
20164 IPv4 address). Only supported by servers using eventdns; servers
20165 now announce in their descriptors if they don't support eventdns.
20166 - Workaround for name servers (like Earthlink's) that hijack failing
20167 DNS requests and replace the no-such-server answer with a "helpful"
20168 redirect to an advertising-driven search portal. Also work around
20169 DNS hijackers who "helpfully" decline to hijack known-invalid
20170 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
20171 lets you turn it off.
20172 - Servers now check for the case when common DNS requests are going to
20173 wildcarded addresses (i.e. all getting the same answer), and change
20174 their exit policy to reject *:* if it's happening.
20175 - When asked to resolve a hostname, don't use non-exit servers unless
20176 requested to do so. This allows servers with broken DNS to be
20177 useful to the network.
20178 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
20179 useless IPv6 DNS resolves.
20180 - Specify and implement client-side SOCKS5 interface for reverse DNS
20181 lookups (see doc/socks-extensions.txt). Also cache them.
20182 - When we change nameservers or IP addresses, reset and re-launch
20183 our tests for DNS hijacking.
20185 o Improvements on reachability testing:
20186 - Servers send out a burst of long-range padding cells once they've
20187 established that they're reachable. Spread them over 4 circuits,
20188 so hopefully a few will be fast. This exercises bandwidth and
20189 bootstraps them into the directory more quickly.
20190 - When we find our DirPort to be reachable, publish a new descriptor
20191 so we'll tell the world (reported by pnx).
20192 - Directory authorities now only decide that routers are reachable
20193 if their identity keys are as expected.
20194 - Do DirPort reachability tests less often, since a single test
20195 chews through many circuits before giving up.
20196 - Avoid some false positives during reachability testing: don't try
20197 to test via a server that's on the same /24 network as us.
20198 - Start publishing one minute or so after we find our ORPort
20199 to be reachable. This will help reduce the number of descriptors
20200 we have for ourselves floating around, since it's quite likely
20201 other things (e.g. DirPort) will change during that minute too.
20202 - Routers no longer try to rebuild long-term connections to directory
20203 authorities, and directory authorities no longer try to rebuild
20204 long-term connections to all servers. We still don't hang up
20205 connections in these two cases though -- we need to look at it
20206 more carefully to avoid flapping, and we likely need to wait til
20207 0.1.1.x is obsolete.
20209 o Improvements on rate limiting:
20210 - Enable write limiting as well as read limiting. Now we sacrifice
20211 capacity if we're pushing out lots of directory traffic, rather
20212 than overrunning the user's intended bandwidth limits.
20213 - Include TLS overhead when counting bandwidth usage; previously, we
20214 would count only the bytes sent over TLS, but not the bytes used
20216 - Servers decline directory requests much more aggressively when
20217 they're low on bandwidth. Otherwise they end up queueing more and
20218 more directory responses, which can't be good for latency.
20219 - But never refuse directory requests from local addresses.
20220 - Be willing to read or write on local connections (e.g. controller
20221 connections) even when the global rate limiting buckets are empty.
20222 - Flush local controller connection buffers periodically as we're
20223 writing to them, so we avoid queueing 4+ megabytes of data before
20225 - Revise and clean up the torrc.sample that we ship with; add
20226 a section for BandwidthRate and BandwidthBurst.
20228 o Major features, NT services:
20229 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
20230 command-line flag so that admins can override the default by saying
20231 "tor --service install --user "SomeUser"". This will not affect
20232 existing installed services. Also, warn the user that the service
20233 will look for its configuration file in the service user's
20234 %appdata% directory. (We can't do the "hardwire the user's appdata
20235 directory" trick any more, since we may not have read access to that
20237 - Support running the Tor service with a torrc not in the same
20238 directory as tor.exe and default to using the torrc located in
20239 the %appdata%\Tor\ of the user who installed the service. Patch
20241 - Add an --ignore-missing-torrc command-line option so that we can
20242 get the "use sensible defaults if the configuration file doesn't
20243 exist" behavior even when specifying a torrc location on the
20245 - When stopping an NT service, wait up to 10 sec for it to actually
20246 stop. (Patch from Matt Edman; resolves bug 295.)
20248 o Directory authority improvements:
20249 - Stop letting hibernating or obsolete servers affect uptime and
20251 - Stop listing hibernating servers in the v1 directory.
20252 - Authorities no longer recommend exits as guards if this would shift
20253 too much load to the exit nodes.
20254 - Authorities now specify server versions in networkstatus. This adds
20255 about 2% to the size of compressed networkstatus docs, and allows
20256 clients to tell which servers support BEGIN_DIR and which don't.
20257 The implementation is forward-compatible with a proposed future
20258 protocol version scheme not tied to Tor versions.
20259 - DirServer configuration lines now have an orport= option so
20260 clients can open encrypted tunnels to the authorities without
20261 having downloaded their descriptors yet. Enabled for moria1,
20262 moria2, tor26, and lefkada now in the default configuration.
20263 - Add a BadDirectory flag to network status docs so that authorities
20264 can (eventually) tell clients about caches they believe to be
20265 broken. Not used yet.
20266 - Allow authorities to list nodes as bad exits in their
20267 approved-routers file by fingerprint or by address. If most
20268 authorities set a BadExit flag for a server, clients don't think
20269 of it as a general-purpose exit. Clients only consider authorities
20270 that advertise themselves as listing bad exits.
20271 - Patch from Steve Hildrey: Generate network status correctly on
20272 non-versioning dirservers.
20273 - Have directory authorities allow larger amounts of drift in uptime
20274 without replacing the server descriptor: previously, a server that
20275 restarted every 30 minutes could have 48 "interesting" descriptors
20277 - Reserve the nickname "Unnamed" for routers that can't pick
20278 a hostname: any router can call itself Unnamed; directory
20279 authorities will never allocate Unnamed to any particular router;
20280 clients won't believe that any router is the canonical Unnamed.
20282 o Directory mirrors and clients:
20283 - Discard any v1 directory info that's over 1 month old (for
20284 directories) or over 1 week old (for running-routers lists).
20285 - Clients track responses with status 503 from dirservers. After a
20286 dirserver has given us a 503, we try not to use it until an hour has
20287 gone by, or until we have no dirservers that haven't given us a 503.
20288 - When we get a 503 from a directory, and we're not a server, we no
20289 longer count the failure against the total number of failures
20290 allowed for the object we're trying to download.
20291 - Prepare for servers to publish descriptors less often: never
20292 discard a descriptor simply for being too old until either it is
20293 recommended by no authorities, or until we get a better one for
20294 the same router. Make caches consider retaining old recommended
20295 routers for even longer.
20296 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
20297 headers for content, so that we can work better in the presence of
20298 caching HTTP proxies.
20299 - Stop fetching descriptors if you're not a dir mirror and you
20300 haven't tried to establish any circuits lately. (This currently
20301 causes some dangerous behavior, because when you start up again
20302 you'll use your ancient server descriptors.)
20304 o Major fixes, crashes:
20305 - Stop crashing when the controller asks us to resetconf more than
20306 one config option at once. (Vidalia 0.0.11 does this.)
20307 - Fix a longstanding obscure crash bug that could occur when we run
20308 out of DNS worker processes, if we're not using eventdns. (Resolves
20310 - Fix an assert that could trigger if a controller quickly set then
20311 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
20312 - Avoid crash when telling controller about stream-status and a
20313 stream is detached.
20314 - Avoid sending junk to controllers or segfaulting when a controller
20315 uses EVENT_NEW_DESC with verbose nicknames.
20316 - Stop triggering asserts if the controller tries to extend hidden
20317 service circuits (reported by mwenge).
20318 - If we start a server with ClientOnly 1, then set ClientOnly to 0
20319 and hup, stop triggering an assert based on an empty onion_key.
20320 - Mask out all signals in sub-threads; only the libevent signal
20321 handler should be processing them. This should prevent some crashes
20322 on some machines using pthreads. (Patch from coderman.)
20323 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
20325 o Major fixes, anonymity/security:
20326 - Automatically avoid picking more than one node from the same
20327 /16 network when constructing a circuit. Add an
20328 "EnforceDistinctSubnets" option to let people disable it if they
20329 want to operate private test networks on a single subnet.
20330 - When generating bandwidth history, round down to the nearest
20331 1k. When storing accounting data, round up to the nearest 1k.
20332 - When we're running as a server, remember when we last rotated onion
20333 keys, so that we will rotate keys once they're a week old even if
20334 we never stay up for a week ourselves.
20335 - If a client asked for a server by name, and there's a named server
20336 in our network-status but we don't have its descriptor yet, we
20337 could return an unnamed server instead.
20338 - Reject (most) attempts to use Tor circuits with length one. (If
20339 many people start using Tor as a one-hop proxy, exit nodes become
20340 a more attractive target for compromise.)
20341 - Just because your DirPort is open doesn't mean people should be
20342 able to remotely teach you about hidden service descriptors. Now
20343 only accept rendezvous posts if you've got HSAuthoritativeDir set.
20344 - Fix a potential race condition in the rpm installer. Found by
20346 - Do not log IPs with TLS failures for incoming TLS
20347 connections. (Fixes bug 382.)
20349 o Major fixes, other:
20350 - If our system clock jumps back in time, don't publish a negative
20351 uptime in the descriptor.
20352 - When we start during an accounting interval before it's time to wake
20353 up, remember to wake up at the correct time. (May fix bug 342.)
20354 - Previously, we would cache up to 16 old networkstatus documents
20355 indefinitely, if they came from nontrusted authorities. Now we
20356 discard them if they are more than 10 days old.
20357 - When we have a state file we cannot parse, tell the user and
20358 move it aside. Now we avoid situations where the user starts
20359 Tor in 1904, Tor writes a state file with that timestamp in it,
20360 the user fixes her clock, and Tor refuses to start.
20361 - Publish a new descriptor after we hup/reload. This is important
20362 if our config has changed such that we'll want to start advertising
20363 our DirPort now, etc.
20364 - If we are using an exit enclave and we can't connect, e.g. because
20365 its webserver is misconfigured to not listen on localhost, then
20366 back off and try connecting from somewhere else before we fail.
20368 o New config options or behaviors:
20369 - When EntryNodes are configured, rebuild the guard list to contain,
20370 in order: the EntryNodes that were guards before; the rest of the
20371 EntryNodes; the nodes that were guards before.
20372 - Do not warn when individual nodes in the configuration's EntryNodes,
20373 ExitNodes, etc are down: warn only when all possible nodes
20374 are down. (Fixes bug 348.)
20375 - Put a lower-bound on MaxAdvertisedBandwidth.
20376 - Start using the state file to store bandwidth accounting data:
20377 the bw_accounting file is now obsolete. We'll keep generating it
20378 for a while for people who are still using 0.1.2.4-alpha.
20379 - Try to batch changes to the state file so that we do as few
20380 disk writes as possible while still storing important things in
20382 - The state file and the bw_accounting file get saved less often when
20383 the AvoidDiskWrites config option is set.
20384 - Make PIDFile work on Windows.
20385 - Add internal descriptions for a bunch of configuration options:
20386 accessible via controller interface and in comments in saved
20388 - Reject *:563 (NNTPS) in the default exit policy. We already reject
20389 NNTP by default, so this seems like a sensible addition.
20390 - Clients now reject hostnames with invalid characters. This should
20391 avoid some inadvertent info leaks. Add an option
20392 AllowNonRFC953Hostnames to disable this behavior, in case somebody
20393 is running a private network with hosts called @, !, and #.
20394 - Check for addresses with invalid characters at the exit as well,
20395 and warn less verbosely when they fail. You can override this by
20396 setting ServerDNSAllowNonRFC953Addresses to 1.
20397 - Remove some options that have been deprecated since at least
20398 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
20399 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
20400 to set log options. Mark PathlenCoinWeight as obsolete.
20401 - Stop accepting certain malformed ports in configured exit policies.
20402 - When the user uses bad syntax in the Log config line, stop
20403 suggesting other bad syntax as a replacement.
20404 - Add new config option "ResolvConf" to let the server operator
20405 choose an alternate resolve.conf file when using eventdns.
20406 - If one of our entry guards is on the ExcludeNodes list, or the
20407 directory authorities don't think it's a good guard, treat it as
20408 if it were unlisted: stop using it as a guard, and throw it off
20409 the guards list if it stays that way for a long time.
20410 - Allow directory authorities to be marked separately as authorities
20411 for the v1 directory protocol, the v2 directory protocol, and
20412 as hidden service directories, to make it easier to retire old
20413 authorities. V1 authorities should set "HSAuthoritativeDir 1"
20414 to continue being hidden service authorities too.
20415 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
20416 - Make TrackExitHosts case-insensitive, and fix the behavior of
20417 ".suffix" TrackExitHosts items to avoid matching in the middle of
20419 - New DirPort behavior: if you have your dirport set, you download
20420 descriptors aggressively like a directory mirror, whether or not
20421 your ORPort is set.
20424 - Create a new file ReleaseNotes which was the old ChangeLog. The
20425 new ChangeLog file now includes the notes for all development
20427 - Add a new address-spec.txt document to describe our special-case
20428 addresses: .exit, .onion, and .noconnnect.
20429 - Fork the v1 directory protocol into its own spec document,
20430 and mark dir-spec.txt as the currently correct (v2) spec.
20432 o Packaging, porting, and contrib
20433 - "tor --verify-config" now exits with -1(255) or 0 depending on
20434 whether the config options are bad or good.
20435 - The Debian package now uses --verify-config when (re)starting,
20436 to distinguish configuration errors from other errors.
20437 - Adapt a patch from goodell to let the contrib/exitlist script
20438 take arguments rather than require direct editing.
20439 - Prevent the contrib/exitlist script from printing the same
20440 result more than once.
20441 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
20442 - In the hidden service example in torrc.sample, stop recommending
20443 esoteric and discouraged hidden service options.
20444 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
20445 values before failing, and always enables eventdns.
20446 - Try to detect Windows correctly when cross-compiling.
20447 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
20448 Try to fix this in configure.in by checking for most functions
20449 before we check for libevent.
20450 - Update RPMs to require libevent 1.2.
20451 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
20452 or later. Log when we are doing this, so we can diagnose it when
20453 it fails. (Also, recommend libevent 1.1b for kqueue and
20454 win32 methods; deprecate libevent 1.0b harder; make libevent
20455 recommendation system saner.)
20456 - Build with recent (1.3+) libevents on platforms that do not
20457 define the nonstandard types "u_int8_t" and friends.
20458 - Remove architecture from OS X builds. The official builds are
20459 now universal binaries.
20460 - Run correctly on OS X platforms with case-sensitive filesystems.
20461 - Correctly set maximum connection limit on Cygwin. (This time
20463 - Start compiling on MinGW on Windows (patches from Mike Chiussi
20465 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
20466 - Finally fix the openssl warnings from newer gccs that believe that
20467 ignoring a return value is okay, but casting a return value and
20468 then ignoring it is a sign of madness.
20469 - On architectures where sizeof(int)>4, still clamp declarable
20470 bandwidth to INT32_MAX.
20472 o Minor features, controller:
20473 - Warn the user when an application uses the obsolete binary v0
20474 control protocol. We're planning to remove support for it during
20475 the next development series, so it's good to give people some
20477 - Add STREAM_BW events to report per-entry-stream bandwidth
20478 use. (Patch from Robert Hogan.)
20479 - Rate-limit SIGNEWNYM signals in response to controllers that
20480 impolitely generate them for every single stream. (Patch from
20481 mwenge; closes bug 394.)
20482 - Add a REMAP status to stream events to note that a stream's
20483 address has changed because of a cached address or a MapAddress
20485 - Make REMAP stream events have a SOURCE (cache or exit), and
20486 make them generated in every case where we get a successful
20487 connected or resolved cell.
20488 - Track reasons for OR connection failure; make these reasons
20489 available via the controller interface. (Patch from Mike Perry.)
20490 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
20491 can learn when clients are sending malformed hostnames to Tor.
20492 - Specify and implement some of the controller status events.
20493 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
20494 - Reimplement GETINFO so that info/names stays in sync with the
20496 - Implement "GETINFO fingerprint".
20497 - Implement "SETEVENTS GUARD" so controllers can get updates on
20498 entry guard status as it changes.
20499 - Make all connections to addresses of the form ".noconnect"
20500 immediately get closed. This lets application/controller combos
20501 successfully test whether they're talking to the same Tor by
20502 watching for STREAM events.
20503 - Add a REASON field to CIRC events; for backward compatibility, this
20504 field is sent only to controllers that have enabled the extended
20505 event format. Also, add additional reason codes to explain why
20506 a given circuit has been destroyed or truncated. (Patches from
20508 - Add a REMOTE_REASON field to extended CIRC events to tell the
20509 controller why a remote OR told us to close a circuit.
20510 - Stream events also now have REASON and REMOTE_REASON fields,
20511 working much like those for circuit events.
20512 - There's now a GETINFO ns/... field so that controllers can ask Tor
20513 about the current status of a router.
20514 - A new event type "NS" to inform a controller when our opinion of
20515 a router's status has changed.
20516 - Add a GETINFO events/names and GETINFO features/names so controllers
20517 can tell which events and features are supported.
20518 - A new CLEARDNSCACHE signal to allow controllers to clear the
20519 client-side DNS cache without expiring circuits.
20520 - Fix CIRC controller events so that controllers can learn the
20521 identity digests of non-Named servers used in circuit paths.
20522 - Let controllers ask for more useful identifiers for servers. Instead
20523 of learning identity digests for un-Named servers and nicknames
20524 for Named servers, the new identifiers include digest, nickname,
20525 and indication of Named status. Off by default; see control-spec.txt
20526 for more information.
20527 - Add a "getinfo address" controller command so it can display Tor's
20528 best guess to the user.
20529 - New controller event to alert the controller when our server
20530 descriptor has changed.
20531 - Give more meaningful errors on controller authentication failure.
20532 - Export the default exit policy via the control port, so controllers
20533 don't need to guess what it is / will be later.
20535 o Minor bugfixes, controller:
20536 - When creating a circuit via the controller, send a 'launched'
20537 event when we're done, so we follow the spec better.
20538 - Correct the control spec to match how the code actually responds
20539 to 'getinfo addr-mappings/*'. Reported by daejees.
20540 - The control spec described a GUARDS event, but the code
20541 implemented a GUARD event. Standardize on GUARD, but let people
20542 ask for GUARDS too. Reported by daejees.
20543 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
20544 clear the corresponding on_circuit variable, and remember later
20545 that we don't need to send a redundant CLOSED event. (Resolves part
20547 - Report events where a resolve succeeded or where we got a socks
20548 protocol error correctly, rather than calling both of them
20550 - Change reported stream target addresses to IP consistently when
20551 we finally get the IP from an exit node.
20552 - Send log messages to the controller even if they happen to be very
20554 - Flush ERR-level controller status events just like we currently
20555 flush ERR-level log events, so that a Tor shutdown doesn't prevent
20556 the controller from learning about current events.
20557 - Report the circuit number correctly in STREAM CLOSED events. Bug
20558 reported by Mike Perry.
20559 - Do not report bizarre values for results of accounting GETINFOs
20560 when the last second's write or read exceeds the allotted bandwidth.
20561 - Report "unrecognized key" rather than an empty string when the
20562 controller tries to fetch a networkstatus that doesn't exist.
20563 - When the controller does a "GETINFO network-status", tell it
20564 about even those routers whose descriptors are very old, and use
20565 long nicknames where appropriate.
20566 - Fix handling of verbose nicknames with ORCONN controller events:
20567 make them show up exactly when requested, rather than exactly when
20569 - Controller signals now work on non-Unix platforms that don't define
20570 SIGUSR1 and SIGUSR2 the way we expect.
20571 - Respond to SIGNAL command before we execute the signal, in case
20572 the signal shuts us down. Suggested by Karsten Loesing.
20573 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
20575 o Minor features, code performance:
20576 - Major performance improvement on inserting descriptors: change
20577 algorithm from O(n^2) to O(n).
20578 - Do not rotate onion key immediately after setting it for the first
20580 - Call router_have_min_dir_info half as often. (This is showing up in
20581 some profiles, but not others.)
20582 - When using GCC, make log_debug never get called at all, and its
20583 arguments never get evaluated, when no debug logs are configured.
20584 (This is showing up in some profiles, but not others.)
20585 - Statistics dumped by -USR2 now include a breakdown of public key
20586 operations, for profiling.
20587 - Make the common memory allocation path faster on machines where
20588 malloc(0) returns a pointer.
20589 - Split circuit_t into origin_circuit_t and or_circuit_t, and
20590 split connection_t into edge, or, dir, control, and base structs.
20591 These will save quite a bit of memory on busy servers, and they'll
20592 also help us track down bugs in the code and bugs in the spec.
20593 - Use OpenSSL's AES implementation on platforms where it's faster.
20594 This could save us as much as 10% CPU usage.
20596 o Minor features, descriptors and descriptor handling:
20597 - Avoid duplicate entries on MyFamily line in server descriptor.
20598 - When Tor receives a router descriptor that it asked for, but
20599 no longer wants (because it has received fresh networkstatuses
20600 in the meantime), do not warn the user. Cache the descriptor if
20601 we're a cache; drop it if we aren't.
20602 - Servers no longer ever list themselves in their "family" line,
20603 even if configured to do so. This makes it easier to configure
20604 family lists conveniently.
20606 o Minor fixes, confusing/misleading log messages:
20607 - Display correct results when reporting which versions are
20608 recommended, and how recommended they are. (Resolves bug 383.)
20609 - Inform the server operator when we decide not to advertise a
20610 DirPort due to AccountingMax enabled or a low BandwidthRate.
20611 - Only include function names in log messages for info/debug messages.
20612 For notice/warn/err, the content of the message should be clear on
20613 its own, and printing the function name only confuses users.
20614 - Remove even more protocol-related warnings from Tor server logs,
20615 such as bad TLS handshakes and malformed begin cells.
20616 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
20617 when the IP address is mapped through MapAddress to a hostname.
20618 - Fix misleading log messages: an entry guard that is "unlisted",
20619 as well as not known to be "down" (because we've never heard
20620 of it), is not therefore "up".
20622 o Minor fixes, old/obsolete behavior:
20623 - Start assuming we can use a create_fast cell if we don't know
20624 what version a router is running.
20625 - We no longer look for identity and onion keys in "identity.key" and
20626 "onion.key" -- these were replaced by secret_id_key and
20627 secret_onion_key in 0.0.8pre1.
20628 - We no longer require unrecognized directory entries to be
20630 - Drop compatibility with obsolete Tors that permit create cells
20631 to have the wrong circ_id_type.
20632 - Remove code to special-case "-cvs" ending, since it has not
20633 actually mattered since 0.0.9.
20634 - Don't re-write the fingerprint file every restart, unless it has
20637 o Minor fixes, misc client-side behavior:
20638 - Always remove expired routers and networkstatus docs before checking
20639 whether we have enough information to build circuits. (Fixes
20641 - When computing clock skew from directory HTTP headers, consider what
20642 time it was when we finished asking for the directory, not what
20644 - Make our socks5 handling more robust to broken socks clients:
20645 throw out everything waiting on the buffer in between socks
20646 handshake phases, since they can't possibly (so the theory
20647 goes) have predicted what we plan to respond to them.
20648 - Expire socks connections if they spend too long waiting for the
20649 handshake to finish. Previously we would let them sit around for
20650 days, if the connecting application didn't close them either.
20651 - And if the socks handshake hasn't started, don't send a
20652 "DNS resolve socks failed" handshake reply; just close it.
20653 - If the user asks to use invalid exit nodes, be willing to use
20655 - Track unreachable entry guards correctly: don't conflate
20656 'unreachable by us right now' with 'listed as down by the directory
20657 authorities'. With the old code, if a guard was unreachable by us
20658 but listed as running, it would clog our guard list forever.
20659 - Behave correctly in case we ever have a network with more than
20660 2GB/s total advertised capacity.
20661 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
20662 - Fix a memory leak when we ask for "all" networkstatuses and we
20663 get one we don't recognize.
20666 Changes in version 0.1.1.26 - 2006-12-14
20667 o Security bugfixes:
20668 - Stop sending the HttpProxyAuthenticator string to directory
20669 servers when directory connections are tunnelled through Tor.
20670 - Clients no longer store bandwidth history in the state file.
20671 - Do not log introduction points for hidden services if SafeLogging
20675 - Fix an assert failure when a directory authority sets
20676 AuthDirRejectUnlisted and then receives a descriptor from an
20677 unlisted router (reported by seeess).
20680 Changes in version 0.1.1.25 - 2006-11-04
20682 - When a client asks us to resolve (rather than connect to)
20683 an address, and we have a cached answer, give them the cached
20684 answer. Previously, we would give them no answer at all.
20685 - We were building exactly the wrong circuits when we predict
20686 hidden service requirements, meaning Tor would have to build all
20687 its circuits on demand.
20688 - If none of our live entry guards have a high uptime, but we
20689 require a guard with a high uptime, try adding a new guard before
20690 we give up on the requirement. This patch should make long-lived
20691 connections more stable on average.
20692 - When testing reachability of our DirPort, don't launch new
20693 tests when there's already one in progress -- unreachable
20694 servers were stacking up dozens of testing streams.
20696 o Security bugfixes:
20697 - When the user sends a NEWNYM signal, clear the client-side DNS
20698 cache too. Otherwise we continue to act on previous information.
20701 - Avoid a memory corruption bug when creating a hash table for
20703 - Avoid possibility of controller-triggered crash when misusing
20704 certain commands from a v0 controller on platforms that do not
20705 handle printf("%s",NULL) gracefully.
20706 - Avoid infinite loop on unexpected controller input.
20707 - Don't log spurious warnings when we see a circuit close reason we
20708 don't recognize; it's probably just from a newer version of Tor.
20709 - Add Vidalia to the OS X uninstaller script, so when we uninstall
20710 Tor/Privoxy we also uninstall Vidalia.
20713 Changes in version 0.1.1.24 - 2006-09-29
20715 - Allow really slow clients to not hang up five minutes into their
20716 directory downloads (suggested by Adam J. Richter).
20717 - Fix major performance regression from 0.1.0.x: instead of checking
20718 whether we have enough directory information every time we want to
20719 do something, only check when the directory information has changed.
20720 This should improve client CPU usage by 25-50%.
20721 - Don't crash if, after a server has been running for a while,
20722 it can't resolve its hostname.
20723 - When a client asks us to resolve (not connect to) an address,
20724 and we have a cached answer, give them the cached answer.
20725 Previously, we would give them no answer at all.
20728 - Allow Tor to start when RunAsDaemon is set but no logs are set.
20729 - Don't crash when the controller receives a third argument to an
20730 "extendcircuit" request.
20731 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
20732 response; fix error code when "getinfo dir/status/" fails.
20733 - Fix configure.in to not produce broken configure files with
20734 more recent versions of autoconf. Thanks to Clint for his auto*
20736 - Fix security bug on NetBSD that could allow someone to force
20737 uninitialized RAM to be sent to a server's DNS resolver. This
20738 only affects NetBSD and other platforms that do not bounds-check
20740 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
20741 methods: these are known to be buggy.
20742 - If we're a directory mirror and we ask for "all" network status
20743 documents, we would discard status documents from authorities
20744 we don't recognize.
20747 Changes in version 0.1.1.23 - 2006-07-30
20749 - Fast Tor servers, especially exit nodes, were triggering asserts
20750 due to a bug in handling the list of pending DNS resolves. Some
20751 bugs still remain here; we're hunting them.
20752 - Entry guards could crash clients by sending unexpected input.
20753 - More fixes on reachability testing: if you find yourself reachable,
20754 then don't ever make any client requests (so you stop predicting
20755 circuits), then hup or have your clock jump, then later your IP
20756 changes, you won't think circuits are working, so you won't try to
20757 test reachability, so you won't publish.
20760 - Avoid a crash if the controller does a resetconf firewallports
20761 and then a setconf fascistfirewall=1.
20762 - Avoid an integer underflow when the dir authority decides whether
20763 a router is stable: we might wrongly label it stable, and compute
20764 a slightly wrong median stability, when a descriptor is published
20766 - Fix a place where we might trigger an assert if we can't build our
20767 own server descriptor yet.
20770 Changes in version 0.1.1.22 - 2006-07-05
20772 - Fix a big bug that was causing servers to not find themselves
20773 reachable if they changed IP addresses. Since only 0.1.1.22+
20774 servers can do reachability testing correctly, now we automatically
20775 make sure to test via one of these.
20776 - Fix to allow clients and mirrors to learn directory info from
20777 descriptor downloads that get cut off partway through.
20778 - Directory authorities had a bug in deciding if a newly published
20779 descriptor was novel enough to make everybody want a copy -- a few
20780 servers seem to be publishing new descriptors many times a minute.
20782 - Fix a rare bug that was causing some servers to complain about
20783 "closing wedged cpuworkers" and skip some circuit create requests.
20784 - Make the Exit flag in directory status documents actually work.
20787 Changes in version 0.1.1.21 - 2006-06-10
20788 o Crash and assert fixes from 0.1.1.20:
20789 - Fix a rare crash on Tor servers that have enabled hibernation.
20790 - Fix a seg fault on startup for Tor networks that use only one
20791 directory authority.
20792 - Fix an assert from a race condition that occurs on Tor servers
20793 while exiting, where various threads are trying to log that they're
20794 exiting, and delete the logs, at the same time.
20795 - Make our unit tests pass again on certain obscure platforms.
20798 - Add support for building SUSE RPM packages.
20799 - Speed up initial bootstrapping for clients: if we are making our
20800 first ever connection to any entry guard, then don't mark it down
20802 - When only one Tor server in the network is labelled as a guard,
20803 and we've already picked him, we would cycle endlessly picking him
20804 again, being unhappy about it, etc. Now we specifically exclude
20805 current guards when picking a new guard.
20806 - Servers send create cells more reliably after the TLS connection
20807 is established: we were sometimes forgetting to send half of them
20808 when we had more than one pending.
20809 - If we get a create cell that asks us to extend somewhere, but the
20810 Tor server there doesn't match the expected digest, we now send
20811 a destroy cell back, rather than silently doing nothing.
20812 - Make options->RedirectExit work again.
20813 - Make cookie authentication for the controller work again.
20814 - Stop being picky about unusual characters in the arguments to
20815 mapaddress. It's none of our business.
20816 - Add a new config option "TestVia" that lets you specify preferred
20817 middle hops to use for test circuits. Perhaps this will let me
20818 debug the reachability problems better.
20820 o Log / documentation fixes:
20821 - If we're a server and some peer has a broken TLS certificate, don't
20822 log about it unless ProtocolWarnings is set, i.e., we want to hear
20823 about protocol violations by others.
20824 - Fix spelling of VirtualAddrNetwork in man page.
20825 - Add a better explanation at the top of the autogenerated torrc file
20826 about what happened to our old torrc.
20829 Changes in version 0.1.1.20 - 2006-05-23
20830 o Crash and assert fixes from 0.1.0.17:
20831 - Fix assert bug in close_logs() on exit: when we close and delete
20832 logs, remove them all from the global "logfiles" list.
20833 - Fix an assert error when we're out of space in the connection_list
20834 and we try to post a hidden service descriptor (reported by Peter
20836 - Fix a rare assert error when we've tried all intro points for
20837 a hidden service and we try fetching the service descriptor again:
20838 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
20839 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
20840 out and refuse the setconf if it would fail.
20841 - If you specify a relative torrc path and you set RunAsDaemon in
20842 your torrc, then it chdir()'s to the new directory. If you then
20843 HUP, it tries to load the new torrc location, fails, and exits.
20844 The fix: no longer allow a relative path to torrc when using -f.
20845 - Check for integer overflows in more places, when adding elements
20846 to smartlists. This could possibly prevent a buffer overflow
20847 on malicious huge inputs.
20849 o Security fixes, major:
20850 - When we're printing strings from the network, don't try to print
20851 non-printable characters. Now we're safer against shell escape
20852 sequence exploits, and also against attacks to fool users into
20853 misreading their logs.
20854 - Implement entry guards: automatically choose a handful of entry
20855 nodes and stick with them for all circuits. Only pick new guards
20856 when the ones you have are unsuitable, and if the old guards
20857 become suitable again, switch back. This will increase security
20858 dramatically against certain end-point attacks. The EntryNodes
20859 config option now provides some hints about which entry guards you
20860 want to use most; and StrictEntryNodes means to only use those.
20861 Fixes CVE-2006-0414.
20862 - Implement exit enclaves: if we know an IP address for the
20863 destination, and there's a running Tor server at that address
20864 which allows exit to the destination, then extend the circuit to
20865 that exit first. This provides end-to-end encryption and end-to-end
20866 authentication. Also, if the user wants a .exit address or enclave,
20867 use 4 hops rather than 3, and cannibalize a general circ for it
20869 - Obey our firewall options more faithfully:
20870 . If we can't get to a dirserver directly, try going via Tor.
20871 . Don't ever try to connect (as a client) to a place our
20872 firewall options forbid.
20873 . If we specify a proxy and also firewall options, obey the
20874 firewall options even when we're using the proxy: some proxies
20875 can only proxy to certain destinations.
20876 - Make clients regenerate their keys when their IP address changes.
20877 - For the OS X package's modified privoxy config file, comment
20878 out the "logfile" line so we don't log everything passed
20880 - Our TLS handshakes were generating a single public/private
20881 keypair for the TLS context, rather than making a new one for
20882 each new connection. Oops. (But we were still rotating them
20883 periodically, so it's not so bad.)
20884 - When we were cannibalizing a circuit with a particular exit
20885 node in mind, we weren't checking to see if that exit node was
20886 already present earlier in the circuit. Now we are.
20887 - Require server descriptors to list IPv4 addresses -- hostnames
20888 are no longer allowed. This also fixes potential vulnerabilities
20889 to servers providing hostnames as their address and then
20890 preferentially resolving them so they can partition users.
20891 - Our logic to decide if the OR we connected to was the right guy
20892 was brittle and maybe open to a mitm for invalid routers.
20894 o Security fixes, minor:
20895 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
20896 Ian Goldberg can prove things about our handshake protocol more
20898 - Make directory authorities generate a separate "guard" flag to
20899 mean "would make a good entry guard". Clients now honor the
20900 is_guard flag rather than looking at is_fast or is_stable.
20901 - Try to list MyFamily elements by key, not by nickname, and warn
20902 if we've not heard of a server.
20903 - Start using RAND_bytes rather than RAND_pseudo_bytes from
20904 OpenSSL. Also, reseed our entropy every hour, not just at
20905 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
20906 - Refuse server descriptors where the fingerprint line doesn't match
20907 the included identity key. Tor doesn't care, but other apps (and
20908 humans) might actually be trusting the fingerprint line.
20909 - We used to kill the circuit when we receive a relay command we
20910 don't recognize. Now we just drop that cell.
20911 - Fix a bug found by Lasse Overlier: when we were making internal
20912 circuits (intended to be cannibalized later for rendezvous and
20913 introduction circuits), we were picking them so that they had
20914 useful exit nodes. There was no need for this, and it actually
20915 aids some statistical attacks.
20916 - Start treating internal circuits and exit circuits separately.
20917 It's important to keep them separate because internal circuits
20918 have their last hops picked like middle hops, rather than like
20919 exit hops. So exiting on them will break the user's expectations.
20920 - Fix a possible way to DoS dirservers.
20921 - When the client asked for a rendezvous port that the hidden
20922 service didn't want to provide, we were sending an IP address
20923 back along with the end cell. Fortunately, it was zero. But stop
20926 o Packaging improvements:
20927 - Implement --with-libevent-dir option to ./configure. Improve
20928 search techniques to find libevent, and use those for openssl too.
20929 - Fix a couple of bugs in OpenSSL detection. Deal better when
20930 there are multiple SSLs installed with different versions.
20931 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
20932 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
20934 - Make unit tests (and other invocations that aren't the real Tor)
20935 run without launching listeners, creating subdirectories, and so on.
20936 - The OS X installer was adding a symlink for tor_resolve but
20937 the binary was called tor-resolve (reported by Thomas Hardly).
20938 - Now we can target arch and OS in rpm builds (contributed by
20939 Phobos). Also make the resulting dist-rpm filename match the
20941 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
20942 if you log to syslog and want something other than LOG_DAEMON.
20943 - Fix the torify (tsocks) config file to not use Tor for localhost
20945 - Start shipping socks-extensions.txt, tor-doc-unix.html,
20946 tor-doc-server.html, and stylesheet.css in the tarball.
20947 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
20948 They are useless now.
20949 - Add Peter Palfrader's contributed check-tor script. It lets you
20950 easily check whether a given server (referenced by nickname)
20951 is reachable by you.
20952 - Add BSD-style contributed startup script "rc.subr" from Peter
20955 o Directory improvements -- new directory protocol:
20956 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
20957 - Authorities and caches publish individual descriptors (by
20958 digest, by fingerprint, by "all", and by "tell me yours").
20959 - Clients don't download or use the old directory anymore. Now they
20960 download network-statuses from the directory authorities, and
20961 fetch individual server descriptors as needed from mirrors.
20962 - Clients don't download descriptors of non-running servers.
20963 - Download descriptors by digest, not by fingerprint. Caches try to
20964 download all listed digests from authorities; clients try to
20965 download "best" digests from caches. This avoids partitioning
20966 and isolating attacks better.
20967 - Only upload a new server descriptor when options change, 18
20968 hours have passed, uptime is reset, or bandwidth changes a lot.
20969 - Directory authorities silently throw away new descriptors that
20970 haven't changed much if the timestamps are similar. We do this to
20971 tolerate older Tor servers that upload a new descriptor every 15
20972 minutes. (It seemed like a good idea at the time.)
20973 - Clients choose directory servers from the network status lists,
20974 not from their internal list of router descriptors. Now they can
20975 go to caches directly rather than needing to go to authorities
20976 to bootstrap the first set of descriptors.
20977 - When picking a random directory, prefer non-authorities if any
20979 - Add a new flag to network-status indicating whether the server
20980 can answer v2 directory requests too.
20981 - Directory mirrors now cache up to 16 unrecognized network-status
20982 docs, so new directory authorities will be cached too.
20983 - Stop parsing, storing, or using running-routers output (but
20984 mirrors still cache and serve it).
20985 - Clients consider a threshold of "versioning" directory authorities
20986 before deciding whether to warn the user that he's obsolete.
20987 - Authorities publish separate sorted lists of recommended versions
20988 for clients and for servers.
20989 - Change DirServers config line to note which dirs are v1 authorities.
20990 - Put nicknames on the DirServer line, so we can refer to them
20991 without requiring all our users to memorize their IP addresses.
20992 - Remove option when getting directory cache to see whether they
20993 support running-routers; they all do now. Replace it with one
20994 to see whether caches support v2 stuff.
20995 - Stop listing down or invalid nodes in the v1 directory. This
20996 reduces its bulk by about 1/3, and reduces load on mirrors.
20997 - Mirrors no longer cache the v1 directory as often.
20998 - If we as a directory mirror don't know of any v1 directory
20999 authorities, then don't try to cache any v1 directories.
21001 o Other directory improvements:
21002 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
21003 fifth authoritative directory servers.
21004 - Directory authorities no longer require an open connection from
21005 a server to consider him "reachable". We need this change because
21006 when we add new directory authorities, old servers won't know not
21007 to hang up on them.
21008 - Dir authorities now do their own external reachability testing
21009 of each server, and only list as running the ones they found to
21010 be reachable. We also send back warnings to the server's logs if
21011 it uploads a descriptor that we already believe is unreachable.
21012 - Spread the directory authorities' reachability testing over the
21013 entire testing interval, so we don't try to do 500 TLS's at once
21015 - Make the "stable" router flag in network-status be the median of
21016 the uptimes of running valid servers, and make clients pay
21017 attention to the network-status flags. Thus the cutoff adapts
21018 to the stability of the network as a whole, making IRC, IM, etc
21019 connections more reliable.
21020 - Make the v2 dir's "Fast" flag based on relative capacity, just
21021 like "Stable" is based on median uptime. Name everything in the
21022 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
21023 - Retry directory requests if we fail to get an answer we like
21024 from a given dirserver (we were retrying before, but only if
21025 we fail to connect).
21026 - Return a robots.txt on our dirport to discourage google indexing.
21028 o Controller protocol improvements:
21029 - Revised controller protocol (version 1) that uses ascii rather
21030 than binary: tor/doc/control-spec.txt. Add supporting libraries
21031 in python and java and c# so you can use the controller from your
21032 applications without caring how our protocol works.
21033 - Allow the DEBUG controller event to work again. Mark certain log
21034 entries as "don't tell this to controllers", so we avoid cycles.
21035 - New controller function "getinfo accounting", to ask how
21036 many bytes we've used in this time period.
21037 - Add a "resetconf" command so you can set config options like
21038 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
21039 a config option in the torrc with no value, then it clears it
21040 entirely (rather than setting it to its default).
21041 - Add a "getinfo config-file" to tell us where torrc is. Also
21042 expose guard nodes, config options/names.
21043 - Add a "quit" command (when when using the controller manually).
21044 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
21045 stop using any currently-dirty circuits for new streams, so we
21046 don't link new actions to old actions. This also occurs on HUP
21047 or "signal reload".
21048 - If we would close a stream early (e.g. it asks for a .exit that
21049 we know would refuse it) but the LeaveStreamsUnattached config
21050 option is set by the controller, then don't close it.
21051 - Add a new controller event type "authdir_newdescs" that allows
21052 controllers to get all server descriptors that were uploaded to
21053 a router in its role as directory authority.
21054 - New controller option "getinfo desc/all-recent" to fetch the
21055 latest server descriptor for every router that Tor knows about.
21056 - Fix the controller's "attachstream 0" command to treat conn like
21057 it just connected, doing address remapping, handling .exit and
21058 .onion idioms, and so on. Now we're more uniform in making sure
21059 that the controller hears about new and closing connections.
21060 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
21061 the controller. Also, rotate dns and cpu workers if the controller
21062 changes options that will affect them; and initialize the dns
21063 worker cache tree whether or not we start out as a server.
21064 - Add a new circuit purpose 'controller' to let the controller ask
21065 for a circuit that Tor won't try to use. Extend the "extendcircuit"
21066 controller command to let you specify the purpose if you're starting
21067 a new circuit. Add a new "setcircuitpurpose" controller command to
21068 let you change a circuit's purpose after it's been created.
21069 - Let the controller ask for "getinfo dir/server/foo" so it can ask
21070 directly rather than connecting to the dir port. "getinfo
21071 dir/status/foo" also works, but currently only if your DirPort
21073 - Let the controller tell us about certain router descriptors
21074 that it doesn't want Tor to use in circuits. Implement
21075 "setrouterpurpose" and modify "+postdescriptor" to do this.
21076 - If the controller's *setconf commands fail, collect an error
21077 message in a string and hand it back to the controller -- don't
21078 just tell them to go read their logs.
21080 o Scalability, resource management, and performance:
21081 - Fix a major load balance bug: we were round-robin reading in 16 KB
21082 chunks, and servers with bandwidthrate of 20 KB, while downloading
21083 a 600 KB directory, would starve their other connections. Now we
21084 try to be a bit more fair.
21085 - Be more conservative about whether to advertise our DirPort.
21086 The main change is to not advertise if we're running at capacity
21087 and either a) we could hibernate ever or b) our capacity is low
21088 and we're using a default DirPort.
21089 - We weren't cannibalizing circuits correctly for
21090 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
21091 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
21092 build those from scratch. This should make hidden services faster.
21093 - Predict required circuits better, with an eye toward making hidden
21094 services faster on the service end.
21095 - Compress exit policies even more: look for duplicate lines and
21097 - Generate 18.0.0.0/8 address policy format in descs when we can;
21098 warn when the mask is not reducible to a bit-prefix.
21099 - There used to be two ways to specify your listening ports in a
21100 server descriptor: on the "router" line and with a separate "ports"
21101 line. Remove support for the "ports" line.
21102 - Reduce memory requirements in our structs by changing the order
21103 of fields. Replace balanced trees with hash tables. Inline
21104 bottleneck smartlist functions. Add a "Map from digest to void*"
21105 abstraction so we can do less hex encoding/decoding, and use it
21106 in router_get_by_digest(). Many other CPU and memory improvements.
21107 - Allow tor_gzip_uncompress to extract as much as possible from
21108 truncated compressed data. Try to extract as many
21109 descriptors as possible from truncated http responses (when
21110 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
21111 - Make circ->onionskin a pointer, not a static array. moria2 was using
21112 125000 circuit_t's after it had been up for a few weeks, which
21113 translates to 20+ megs of wasted space.
21114 - The private half of our EDH handshake keys are now chosen out
21115 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
21116 - Stop doing the complex voodoo overkill checking for insecure
21117 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
21118 - Do round-robin writes for TLS of at most 16 kB per write. This
21119 might be more fair on loaded Tor servers.
21120 - Do not use unaligned memory access on alpha, mips, or mipsel.
21121 It *works*, but is very slow, so we treat them as if it doesn't.
21123 o Other bugfixes and improvements:
21124 - Start storing useful information to $DATADIR/state, so we can
21125 remember things across invocations of Tor. Retain unrecognized
21126 lines so we can be forward-compatible, and write a TorVersion line
21127 so we can be backward-compatible.
21128 - If ORPort is set, Address is not explicitly set, and our hostname
21129 resolves to a private IP address, try to use an interface address
21130 if it has a public address. Now Windows machines that think of
21131 themselves as localhost can guess their address.
21132 - Regenerate our local descriptor if it's dirty and we try to use
21133 it locally (e.g. if it changes during reachability detection).
21134 This was causing some Tor servers to keep publishing the same
21135 initial descriptor forever.
21136 - Tor servers with dynamic IP addresses were needing to wait 18
21137 hours before they could start doing reachability testing using
21138 the new IP address and ports. This is because they were using
21139 the internal descriptor to learn what to test, yet they were only
21140 rebuilding the descriptor once they decided they were reachable.
21141 - It turns out we couldn't bootstrap a network since we added
21142 reachability detection in 0.1.0.1-rc. Good thing the Tor network
21143 has never gone down. Add an AssumeReachable config option to let
21144 servers and authorities bootstrap. When we're trying to build a
21145 high-uptime or high-bandwidth circuit but there aren't enough
21146 suitable servers, try being less picky rather than simply failing.
21147 - Newly bootstrapped Tor networks couldn't establish hidden service
21148 circuits until they had nodes with high uptime. Be more tolerant.
21149 - Really busy servers were keeping enough circuits open on stable
21150 connections that they were wrapping around the circuit_id
21151 space. (It's only two bytes.) This exposed a bug where we would
21152 feel free to reuse a circuit_id even if it still exists but has
21153 been marked for close. Try to fix this bug. Some bug remains.
21154 - When we fail to bind or listen on an incoming or outgoing
21155 socket, we now close it before refusing, rather than just
21156 leaking it. (Thanks to Peter Palfrader for finding.)
21157 - Fix a file descriptor leak in start_daemon().
21158 - On Windows, you can't always reopen a port right after you've
21159 closed it. So change retry_listeners() to only close and re-open
21160 ports that have changed.
21161 - Workaround a problem with some http proxies that refuse GET
21162 requests that specify "Content-Length: 0". Reported by Adrian.
21163 - Recover better from TCP connections to Tor servers that are
21164 broken but don't tell you (it happens!); and rotate TLS
21165 connections once a week.
21166 - Fix a scary-looking but apparently harmless bug where circuits
21167 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
21168 servers, and never switch to state CIRCUIT_STATE_OPEN.
21169 - Check for even more Windows version flags when writing the platform
21170 string in server descriptors, and note any we don't recognize.
21171 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
21172 get a better idea of why their circuits failed. Not used yet.
21173 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
21174 We don't use them yet, but maybe one day our DNS resolver will be
21175 able to discover them.
21176 - Let people type "tor --install" as well as "tor -install" when they
21177 want to make it an NT service.
21178 - Looks like we were never delivering deflated (i.e. compressed)
21179 running-routers lists, even when asked. Oops.
21180 - We were leaking some memory every time the client changed IPs.
21181 - Clean up more of the OpenSSL memory when exiting, so we can detect
21182 memory leaks better.
21183 - Never call free() on tor_malloc()d memory. This will help us
21184 use dmalloc to detect memory leaks.
21185 - Some Tor servers process billions of cells per day. These
21186 statistics are now uint64_t's.
21187 - Check [X-]Forwarded-For headers in HTTP requests when generating
21188 log messages. This lets people run dirservers (and caches) behind
21189 Apache but still know which IP addresses are causing warnings.
21190 - Fix minor integer overflow in calculating when we expect to use up
21191 our bandwidth allocation before hibernating.
21192 - Lower the minimum required number of file descriptors to 1000,
21193 so we can have some overhead for Valgrind on Linux, where the
21194 default ulimit -n is 1024.
21195 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
21196 and its existence is confusing some users.
21198 o Config option fixes:
21199 - Add a new config option ExitPolicyRejectPrivate which defaults
21200 to on. Now all exit policies will begin with rejecting private
21201 addresses, unless the server operator explicitly turns it off.
21202 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
21203 - Add new ReachableORAddresses and ReachableDirAddresses options
21204 that understand address policies. FascistFirewall is now a synonym
21205 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
21206 - Start calling it FooListenAddress rather than FooBindAddress,
21207 since few of our users know what it means to bind an address
21209 - If the user gave Tor an odd number of command-line arguments,
21210 we were silently ignoring the last one. Now we complain and fail.
21211 This wins the oldest-bug prize -- this bug has been present since
21212 November 2002, as released in Tor 0.0.0.
21213 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
21214 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
21215 it would silently ignore the 6668.
21216 - If we get a linelist or linelist_s config option from the torrc,
21217 e.g. ExitPolicy, and it has no value, warn and skip rather than
21218 silently resetting it to its default.
21219 - Setconf was appending items to linelists, not clearing them.
21220 - Add MyFamily to torrc.sample in the server section, so operators
21221 will be more likely to learn that it exists.
21222 - Make ContactInfo mandatory for authoritative directory servers.
21223 - MaxConn has been obsolete for a while now. Document the ConnLimit
21224 config option, which is a *minimum* number of file descriptors
21225 that must be available else Tor refuses to start.
21226 - Get rid of IgnoreVersion undocumented config option, and make us
21227 only warn, never exit, when we're running an obsolete version.
21228 - Make MonthlyAccountingStart config option truly obsolete now.
21229 - Correct the man page entry on TrackHostExitsExpire.
21230 - Let directory authorities start even if they don't specify an
21231 Address config option.
21232 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
21233 reflect the updated flags in our v2 dir protocol.
21235 o Config option features:
21236 - Add a new config option FastFirstHopPK (on by default) so clients
21237 do a trivial crypto handshake for their first hop, since TLS has
21238 already taken care of confidentiality and authentication.
21239 - Let the user set ControlListenAddress in the torrc. This can be
21240 dangerous, but there are some cases (like a secured LAN) where it
21242 - New config options to help controllers: FetchServerDescriptors
21243 and FetchHidServDescriptors for whether to fetch server
21244 info and hidserv info or let the controller do it, and
21245 PublishServerDescriptor and PublishHidServDescriptors.
21246 - Also let the controller set the __AllDirActionsPrivate config
21247 option if you want all directory fetches/publishes to happen via
21248 Tor (it assumes your controller bootstraps your circuits).
21249 - Add "HardwareAccel" config option: support for crypto hardware
21250 accelerators via OpenSSL. Off by default, until we find somebody
21251 smart who can test it for us. (It appears to produce seg faults
21252 in at least some cases.)
21253 - New config option "AuthDirRejectUnlisted" for directory authorities
21254 as a panic button: if we get flooded with unusable servers we can
21255 revert to only listing servers in the approved-routers file.
21256 - Directory authorities can now reject/invalidate by key and IP,
21257 with the config options "AuthDirInvalid" and "AuthDirReject", or
21258 by marking a fingerprint as "!reject" or "!invalid" (as its
21259 nickname) in the approved-routers file. This is useful since
21260 currently we automatically list servers as running and usable
21261 even if we know they're jerks.
21262 - Add a new config option TestSocks so people can see whether their
21263 applications are using socks4, socks4a, socks5-with-ip, or
21264 socks5-with-fqdn. This way they don't have to keep mucking
21265 with tcpdump and wondering if something got cached somewhere.
21266 - Add "private:*" as an alias in configuration for policies. Now
21267 you can simplify your exit policy rather than needing to list
21268 every single internal or nonroutable network space.
21269 - Accept "private:*" in routerdesc exit policies; not generated yet
21270 because older Tors do not understand it.
21271 - Add configuration option "V1AuthoritativeDirectory 1" which
21272 moria1, moria2, and tor26 have set.
21273 - Implement an option, VirtualAddrMask, to set which addresses
21274 get handed out in response to mapaddress requests. This works
21275 around a bug in tsocks where 127.0.0.0/8 is never socksified.
21276 - Add a new config option FetchUselessDescriptors, off by default,
21277 for when you plan to run "exitlist" on your client and you want
21278 to know about even the non-running descriptors.
21279 - SocksTimeout: How long do we let a socks connection wait
21280 unattached before we fail it?
21281 - CircuitBuildTimeout: Cull non-open circuits that were born
21282 at least this many seconds ago.
21283 - CircuitIdleTimeout: Cull open clean circuits that were born
21284 at least this many seconds ago.
21285 - New config option SafeSocks to reject all application connections
21286 using unsafe socks protocols. Defaults to off.
21288 o Improved and clearer log messages:
21289 - Reduce clutter in server logs. We're going to try to make
21290 them actually usable now. New config option ProtocolWarnings that
21291 lets you hear about how _other Tors_ are breaking the protocol. Off
21293 - Divide log messages into logging domains. Once we put some sort
21294 of interface on this, it will let people looking at more verbose
21295 log levels specify the topics they want to hear more about.
21296 - Log server fingerprint on startup, so new server operators don't
21297 have to go hunting around their filesystem for it.
21298 - Provide dire warnings to any users who set DirServer manually;
21299 move it out of torrc.sample and into torrc.complete.
21300 - Make the log message less scary when all the dirservers are
21301 temporarily unreachable.
21302 - When tor_socketpair() fails in Windows, give a reasonable
21303 Windows-style errno back.
21304 - Improve tor_gettimeofday() granularity on windows.
21305 - We were printing the number of idle dns workers incorrectly when
21307 - Handle duplicate lines in approved-routers files without warning.
21308 - We were whining about using socks4 or socks5-with-local-lookup
21309 even when it's an IP address in the "virtual" range we designed
21310 exactly for this case.
21311 - Check for named servers when looking them up by nickname;
21312 warn when we're calling a non-named server by its nickname;
21313 don't warn twice about the same name.
21314 - Downgrade the dirserver log messages when whining about
21316 - Correct "your server is reachable" log entries to indicate that
21317 it was self-testing that told us so.
21318 - If we're trying to be a Tor server and running Windows 95/98/ME
21319 as a server, explain that we'll likely crash.
21320 - Provide a more useful warn message when our onion queue gets full:
21321 the CPU is too slow or the exit policy is too liberal.
21322 - Don't warn when we receive a 503 from a dirserver/cache -- this
21323 will pave the way for them being able to refuse if they're busy.
21324 - When we fail to bind a listener, try to provide a more useful
21325 log message: e.g., "Is Tor already running?"
21326 - Only start testing reachability once we've established a
21327 circuit. This will make startup on dir authorities less noisy.
21328 - Don't try to upload hidden service descriptors until we have
21329 established a circuit.
21330 - Tor didn't warn when it failed to open a log file.
21331 - Warn when listening on a public address for socks. We suspect a
21332 lot of people are setting themselves up as open socks proxies,
21333 and they have no idea that jerks on the Internet are using them,
21334 since they simply proxy the traffic into the Tor network.
21335 - Give a useful message when people run Tor as the wrong user,
21336 rather than telling them to start chowning random directories.
21337 - Fix a harmless bug that was causing Tor servers to log
21338 "Got an end because of misc error, but we're not an AP. Closing."
21339 - Fix wrong log message when you add a "HiddenServiceNodes" config
21340 line without any HiddenServiceDir line (reported by Chris Thomas).
21341 - Directory authorities now stop whining so loudly about bad
21342 descriptors that they fetch from other dirservers. So when there's
21343 a log complaint, it's for sure from a freshly uploaded descriptor.
21344 - When logging via syslog, include the pid whenever we provide
21345 a log entry. Suggested by Todd Fries.
21346 - When we're shutting down and we do something like try to post a
21347 server descriptor or rendezvous descriptor, don't complain that
21348 we seem to be unreachable. Of course we are, we're shutting down.
21349 - Change log line for unreachability to explicitly suggest /etc/hosts
21350 as the culprit. Also make it clearer what IP address and ports we're
21351 testing for reachability.
21352 - Put quotes around user-supplied strings when logging so users are
21353 more likely to realize if they add bad characters (like quotes)
21355 - NT service patch from Matt Edman to improve error messages on Win32.
21358 Changes in version 0.1.0.17 - 2006-02-17
21359 o Crash bugfixes on 0.1.0.x:
21360 - When servers with a non-zero DirPort came out of hibernation,
21361 sometimes they would trigger an assert.
21363 o Other important bugfixes:
21364 - On platforms that don't have getrlimit (like Windows), we were
21365 artificially constraining ourselves to a max of 1024
21366 connections. Now just assume that we can handle as many as 15000
21367 connections. Hopefully this won't cause other problems.
21369 o Backported features:
21370 - When we're a server, a client asks for an old-style directory,
21371 and our write bucket is empty, don't give it to him. This way
21372 small servers can continue to serve the directory *sometimes*,
21373 without getting overloaded.
21374 - Whenever you get a 503 in response to a directory fetch, try
21375 once more. This will become important once servers start sending
21376 503's whenever they feel busy.
21377 - Fetch a new directory every 120 minutes, not every 40 minutes.
21378 Now that we have hundreds of thousands of users running the old
21379 directory algorithm, it's starting to hurt a lot.
21380 - Bump up the period for forcing a hidden service descriptor upload
21381 from 20 minutes to 1 hour.
21384 Changes in version 0.1.0.16 - 2006-01-02
21385 o Crash bugfixes on 0.1.0.x:
21386 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
21387 corrupting the heap, losing FDs, or crashing when we need to resize
21388 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
21389 - It turns out sparc64 platforms crash on unaligned memory access
21390 too -- so detect and avoid this.
21391 - Handle truncated compressed data correctly (by detecting it and
21393 - Fix possible-but-unlikely free(NULL) in control.c.
21394 - When we were closing connections, there was a rare case that
21395 stomped on memory, triggering seg faults and asserts.
21396 - Avoid potential infinite recursion when building a descriptor. (We
21397 don't know that it ever happened, but better to fix it anyway.)
21398 - We were neglecting to unlink marked circuits from soon-to-close OR
21399 connections, which caused some rare scribbling on freed memory.
21400 - Fix a memory stomping race bug when closing the joining point of two
21401 rendezvous circuits.
21402 - Fix an assert in time parsing found by Steven Murdoch.
21404 o Other bugfixes on 0.1.0.x:
21405 - When we're doing reachability testing, provide more useful log
21406 messages so the operator knows what to expect.
21407 - Do not check whether DirPort is reachable when we are suppressing
21408 advertising it because of hibernation.
21409 - When building with -static or on Solaris, we sometimes needed -ldl.
21410 - One of the dirservers (tor26) changed its IP address.
21411 - When we're deciding whether a stream has enough circuits around
21412 that can handle it, count the freshly dirty ones and not the ones
21413 that are so dirty they won't be able to handle it.
21414 - When we're expiring old circuits, we had a logic error that caused
21415 us to close new rendezvous circuits rather than old ones.
21416 - Give a more helpful log message when you try to change ORPort via
21417 the controller: you should upgrade Tor if you want that to work.
21418 - We were failing to parse Tor versions that start with "Tor ".
21419 - Tolerate faulty streams better: when a stream fails for reason
21420 exitpolicy, stop assuming that the router is lying about his exit
21421 policy. When a stream fails for reason misc, allow it to retry just
21422 as if it was resolvefailed. When a stream has failed three times,
21423 reset its failure count so we can try again and get all three tries.
21426 Changes in version 0.1.0.15 - 2005-09-23
21427 o Bugfixes on 0.1.0.x:
21428 - Reject ports 465 and 587 (spam targets) in default exit policy.
21429 - Don't crash when we don't have any spare file descriptors and we
21430 try to spawn a dns or cpu worker.
21431 - Get rid of IgnoreVersion undocumented config option, and make us
21432 only warn, never exit, when we're running an obsolete version.
21433 - Don't try to print a null string when your server finds itself to
21434 be unreachable and the Address config option is empty.
21435 - Make the numbers in read-history and write-history into uint64s,
21436 so they don't overflow and publish negatives in the descriptor.
21437 - Fix a minor memory leak in smartlist_string_remove().
21438 - We were only allowing ourselves to upload a server descriptor at
21439 most every 20 minutes, even if it changed earlier than that.
21440 - Clean up log entries that pointed to old URLs.
21443 Changes in version 0.1.0.14 - 2005-08-08
21444 o Bugfixes on 0.1.0.x:
21445 - Fix the other half of the bug with crypto handshakes
21447 - Fix an assert trigger if you send a 'signal term' via the
21448 controller when it's listening for 'event info' messages.
21451 Changes in version 0.1.0.13 - 2005-08-04
21452 o Bugfixes on 0.1.0.x:
21453 - Fix a critical bug in the security of our crypto handshakes.
21454 - Fix a size_t underflow in smartlist_join_strings2() that made
21455 it do bad things when you hand it an empty smartlist.
21456 - Fix Windows installer to ship Tor license (thanks to Aphex for
21457 pointing out this oversight) and put a link to the doc directory
21459 - Explicitly set no-unaligned-access for sparc: it turns out the
21460 new gcc's let you compile broken code, but that doesn't make it
21464 Changes in version 0.1.0.12 - 2005-07-18
21465 o New directory servers:
21466 - tor26 has changed IP address.
21468 o Bugfixes on 0.1.0.x:
21469 - Fix a possible double-free in tor_gzip_uncompress().
21470 - When --disable-threads is set, do not search for or link against
21471 pthreads libraries.
21472 - Don't trigger an assert if an authoritative directory server
21473 claims its dirport is 0.
21474 - Fix bug with removing Tor as an NT service: some people were
21475 getting "The service did not return an error." Thanks to Matt
21479 Changes in version 0.1.0.11 - 2005-06-30
21480 o Bugfixes on 0.1.0.x:
21481 - Fix major security bug: servers were disregarding their
21482 exit policies if clients behaved unexpectedly.
21483 - Make OS X init script check for missing argument, so we don't
21484 confuse users who invoke it incorrectly.
21485 - Fix a seg fault in "tor --hash-password foo".
21486 - The MAPADDRESS control command was broken.
21489 Changes in version 0.1.0.10 - 2005-06-14
21491 - Make NT services work and start on startup on Win32 (based on
21492 patch by Matt Edman). See the FAQ entry for details.
21493 - Make 'platform' string in descriptor more accurate for Win32
21494 servers, so it's not just "unknown platform".
21495 - REUSEADDR on normal platforms means you can rebind to the port
21496 right after somebody else has let it go. But REUSEADDR on Win32
21497 means you can bind to the port _even when somebody else already
21498 has it bound_! So, don't do that on Win32.
21499 - Clean up the log messages when starting on Win32 with no config
21501 - Allow seeding the RNG on Win32 even when you're not running as
21502 Administrator. If seeding the RNG on Win32 fails, quit.
21504 o Assert / crash bugs:
21505 - Refuse relay cells that claim to have a length larger than the
21506 maximum allowed. This prevents a potential attack that could read
21507 arbitrary memory (e.g. keys) from an exit server's process
21509 - If unofficial Tor clients connect and send weird TLS certs, our
21510 Tor server triggers an assert. Stop asserting, and start handling
21511 TLS errors better in other situations too.
21512 - Fix a race condition that can trigger an assert when we have a
21513 pending create cell and an OR connection attempt fails.
21516 - Use pthreads for worker processes rather than forking. This was
21517 forced because when we forked, we ended up wasting a lot of
21518 duplicate ram over time.
21519 - Also switch to foo_r versions of some library calls to allow
21520 reentry and threadsafeness.
21521 - Implement --disable-threads configure option. Disable threads on
21522 netbsd and openbsd by default, because they have no reentrant
21523 resolver functions (!), and on solaris since it has other
21525 - Fix possible bug on threading platforms (e.g. win32) which was
21526 leaking a file descriptor whenever a cpuworker or dnsworker died.
21527 - Fix a minor memory leak when somebody establishes an introduction
21528 point at your Tor server.
21529 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
21531 - Add ./configure --with-dmalloc option, to track memory leaks.
21532 - And try to free all memory on closing, so we can detect what
21535 o Protocol correctness:
21536 - When we've connected to an OR and handshaked but didn't like
21537 the result, we were closing the conn without sending destroy
21538 cells back for pending circuits. Now send those destroys.
21539 - Start sending 'truncated' cells back rather than destroy cells
21540 if the circuit closes in front of you. This means we won't have
21541 to abandon partially built circuits.
21542 - Handle changed router status correctly when dirserver reloads
21543 fingerprint file. We used to be dropping all unverified descriptors
21544 right then. The bug was hidden because we would immediately
21545 fetch a directory from another dirserver, which would include the
21546 descriptors we just dropped.
21547 - Revise tor-spec to add more/better stream end reasons.
21548 - Revise all calls to connection_edge_end to avoid sending 'misc',
21549 and to take errno into account where possible.
21550 - Client now retries when streams end early for 'hibernating' or
21551 'resource limit' reasons, rather than failing them.
21552 - Try to be more zealous about calling connection_edge_end when
21553 things go bad with edge conns in connection.c.
21555 o Robustness improvements:
21556 - Better handling for heterogeneous / unreliable nodes:
21557 - Annotate circuits with whether they aim to contain high uptime
21558 nodes and/or high capacity nodes. When building circuits, choose
21560 - This means that every single node in an intro rend circuit,
21561 not just the last one, will have a minimum uptime.
21562 - New config option LongLivedPorts to indicate application streams
21563 that will want high uptime circuits.
21564 - Servers reset uptime when a dir fetch entirely fails. This
21565 hopefully reflects stability of the server's network connectivity.
21566 - If somebody starts his tor server in Jan 2004 and then fixes his
21567 clock, don't make his published uptime be a year.
21568 - Reset published uptime when we wake up from hibernation.
21569 - Introduce a notion of 'internal' circs, which are chosen without
21570 regard to the exit policy of the last hop. Intro and rendezvous
21571 circs must be internal circs, to avoid leaking information. Resolve
21572 and connect streams can use internal circs if they want.
21573 - New circuit pooling algorithm: keep track of what destination ports
21574 we've used recently (start out assuming we'll want to use 80), and
21575 make sure to have enough circs around to satisfy these ports. Also
21576 make sure to have 2 internal circs around if we've required internal
21577 circs lately (and with high uptime if we've seen that lately too).
21578 - Turn addr_policy_compare from a tristate to a quadstate; this should
21579 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
21580 for google.com" problem.
21581 - When a client asks us for a dir mirror and we don't have one,
21582 launch an attempt to get a fresh one.
21583 - First cut at support for "create-fast" cells. Clients can use
21584 these when extending to their first hop, since the TLS already
21585 provides forward secrecy and authentication. Not enabled on
21588 o Reachability testing.
21589 - Your Tor server will automatically try to see if its ORPort and
21590 DirPort are reachable from the outside, and it won't upload its
21591 descriptor until it decides at least ORPort is reachable (when
21592 DirPort is not yet found reachable, publish it as zero).
21593 - When building testing circs for ORPort testing, use only
21594 high-bandwidth nodes, so fewer circuits fail.
21595 - Notice when our IP changes, and reset stats/uptime/reachability.
21596 - Authdirservers don't do ORPort reachability detection, since
21597 they're in clique mode, so it will be rare to find a server not
21598 already connected to them.
21599 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
21603 - Now we allow two unverified servers with the same nickname
21604 but different keys. But if a nickname is verified, only that
21605 nickname+key are allowed.
21606 - If you're an authdirserver connecting to an address:port,
21607 and it's not the OR you were expecting, forget about that
21608 descriptor. If he *was* the one you were expecting, then forget
21609 about all other descriptors for that address:port.
21610 - Allow servers to publish descriptors from 12 hours in the future.
21611 Corollary: only whine about clock skew from the dirserver if
21612 he's a trusted dirserver (since now even verified servers could
21613 have quite wrong clocks).
21614 - Require servers that use the default dirservers to have public IP
21615 addresses. We have too many servers that are configured with private
21616 IPs and their admins never notice the log entries complaining that
21617 their descriptors are being rejected.
21619 o Efficiency improvements:
21620 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
21621 and /dev/poll), and hopefully work better on Windows too.
21622 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
21623 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
21624 - Find libevent even if it's hiding in /usr/local/ and your
21625 CFLAGS and LDFLAGS don't tell you to look there.
21626 - Be able to link with libevent as a shared library (the default
21627 after 1.0d), even if it's hiding in /usr/local/lib and even
21628 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
21629 assuming you're running gcc. Otherwise fail and give a useful
21631 - Switch to a new buffer management algorithm, which tries to avoid
21632 reallocing and copying quite as much. In first tests it looks like
21633 it uses *more* memory on average, but less cpu.
21634 - Switch our internal buffers implementation to use a ring buffer,
21635 to hopefully improve performance for fast servers a lot.
21636 - Reenable the part of the code that tries to flush as soon as an
21637 OR outbuf has a full TLS record available. Perhaps this will make
21638 OR outbufs not grow as huge except in rare cases, thus saving lots
21639 of CPU time plus memory.
21640 - Improve performance for dirservers: stop re-parsing the whole
21641 directory every time you regenerate it.
21642 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
21643 it much faster to look up a circuit for each relay cell.
21644 - Remove most calls to assert_all_pending_dns_resolves_ok(),
21645 since they're eating our cpu on exit nodes.
21646 - Stop wasting time doing a case insensitive comparison for every
21647 dns name every time we do any lookup. Canonicalize the names to
21648 lowercase when you first see them.
21651 - Handle unavailable hidden services better. Handle slow or busy
21652 hidden services better.
21653 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
21654 circ as necessary, if there are any completed ones lying around
21655 when we try to launch one.
21656 - Make hidden services try to establish a rendezvous for 30 seconds
21657 after fetching the descriptor, rather than for n (where n=3)
21658 attempts to build a circuit.
21659 - Adjust maximum skew and age for rendezvous descriptors: let skew
21660 be 48 hours rather than 90 minutes.
21661 - Reject malformed .onion addresses rather then passing them on as
21662 normal web requests.
21665 - More Tor controller support. See
21666 http://tor.eff.org/doc/control-spec.txt for all the new features,
21667 including signals to emulate unix signals from any platform;
21668 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
21669 closestream; closecircuit; etc.
21670 - Encode hashed controller passwords in hex instead of base64,
21671 to make it easier to write controllers.
21672 - Revise control spec and implementation to allow all log messages to
21673 be sent to controller with their severities intact (suggested by
21674 Matt Edman). Disable debug-level logs while delivering a debug-level
21675 log to the controller, to prevent loop. Update TorControl to handle
21676 new log event types.
21678 o New config options/defaults:
21679 - Begin scrubbing sensitive strings from logs by default. Turn off
21680 the config option SafeLogging if you need to do debugging.
21681 - New exit policy: accept most low-numbered ports, rather than
21682 rejecting most low-numbered ports.
21683 - Put a note in the torrc about abuse potential with the default
21685 - Add support for CONNECTing through https proxies, with "HttpsProxy"
21687 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
21688 based on patch from Adam Langley (basic auth only).
21689 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
21690 the fast servers that have been joining lately. (Clients are now
21691 willing to load balance over up to 2 MB of advertised bandwidth
21693 - New config option MaxAdvertisedBandwidth which lets you advertise
21694 a low bandwidthrate (to not attract as many circuits) while still
21695 allowing a higher bandwidthrate in reality.
21696 - Require BandwidthRate to be at least 20kB/s for servers.
21697 - Add a NoPublish config option, so you can be a server (e.g. for
21698 testing running Tor servers in other Tor networks) without
21699 publishing your descriptor to the primary dirservers.
21700 - Add a new AddressMap config directive to rewrite incoming socks
21701 addresses. This lets you, for example, declare an implicit
21702 required exit node for certain sites.
21703 - Add a new TrackHostExits config directive to trigger addressmaps
21704 for certain incoming socks addresses -- for sites that break when
21705 your exit keeps changing (based on patch from Mike Perry).
21706 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
21707 which describes how often we retry making new circuits if current
21708 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
21709 how long we're willing to make use of an already-dirty circuit.
21710 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
21711 a config option "ShutdownWaitLength" (when using kill -INT on
21713 - Fix an edge case in parsing config options: if they say "--"
21714 on the commandline, it's not a config option (thanks weasel).
21715 - New config option DirAllowPrivateAddresses for authdirservers.
21716 Now by default they refuse router descriptors that have non-IP or
21717 private-IP addresses.
21718 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
21719 smart" default value: low for servers and high for clients.
21720 - Some people were putting "Address " in their torrc, and they had
21721 a buggy resolver that resolved " " to 0.0.0.0. Oops.
21722 - If DataDir is ~/.tor, and that expands to /.tor, then default to
21723 LOCALSTATEDIR/tor instead.
21724 - Implement --verify-config command-line option to check if your torrc
21725 is valid without actually launching Tor.
21727 o Logging improvements:
21728 - When dirservers refuse a server descriptor, we now log its
21729 contactinfo, platform, and the poster's IP address.
21730 - Only warn once per nickname from add_nickname_list_to_smartlist()
21731 per failure, so an entrynode or exitnode choice that's down won't
21733 - When we're connecting to an OR and he's got a different nickname/key
21734 than we were expecting, only complain loudly if we're an OP or a
21735 dirserver. Complaining loudly to the OR admins just confuses them.
21736 - Whine at you if you're a server and you don't set your contactinfo.
21737 - Warn when exit policy implicitly allows local addresses.
21738 - Give a better warning when some other server advertises an
21739 ORPort that is actually an apache running ssl.
21740 - If we get an incredibly skewed timestamp from a dirserver mirror
21741 that isn't a verified OR, don't warn -- it's probably him that's
21743 - When a dirserver causes you to give a warn, mention which dirserver
21745 - Initialize libevent later in the startup process, so the logs are
21746 already established by the time we start logging libevent warns.
21747 - Use correct errno on win32 if libevent fails.
21748 - Check and warn about known-bad/slow libevent versions.
21749 - Stop warning about sigpipes in the logs. We're going to
21750 pretend that getting these occasionally is normal and fine.
21752 o New contrib scripts:
21753 - New experimental script tor/contrib/exitlist: a simple python
21754 script to parse directories and find Tor nodes that exit to listed
21756 - New experimental script tor/contrib/ExerciseServer.py (needs more
21757 work) that uses the controller interface to build circuits and
21758 fetch pages over them. This will help us bootstrap servers that
21759 have lots of capacity but haven't noticed it yet.
21760 - New experimental script tor/contrib/PathDemo.py (needs more work)
21761 that uses the controller interface to let you choose whole paths
21763 "<hostname>.<path,separated by dots>.<length of path>.path"
21764 - New contributed script "privoxy-tor-toggle" to toggle whether
21765 Privoxy uses Tor. Seems to be configured for Debian by default.
21766 - Have torctl.in/tor.sh.in check for location of su binary (needed
21770 - chdir() to your datadirectory at the *end* of the daemonize process,
21771 not the beginning. This was a problem because the first time you
21772 run tor, if your datadir isn't there, and you have runasdaemon set
21773 to 1, it will try to chdir to it before it tries to create it. Oops.
21774 - Fix several double-mark-for-close bugs, e.g. where we were finding
21775 a conn for a cell even if that conn is already marked for close.
21776 - Stop most cases of hanging up on a socks connection without sending
21778 - Fix a bug in the RPM package: set home directory for _tor to
21779 something more reasonable when first installing.
21780 - Stop putting nodename in the Platform string in server descriptors.
21781 It doesn't actually help, and it is confusing/upsetting some people.
21782 - When using preferred entry or exit nodes, ignore whether the
21783 circuit wants uptime or capacity. They asked for the nodes, they
21785 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
21786 artificially capped at 500kB.
21787 - Cache local dns resolves correctly even when they're .exit
21789 - If we're hibernating and we get a SIGINT, exit immediately.
21790 - tor-resolve requests were ignoring .exit if there was a working circuit
21791 they could use instead.
21792 - Pay more attention to the ClientOnly config option.
21793 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
21794 installer screens; and don't put stuff into StartupItems unless
21795 the user asks you to.
21798 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
21799 rather than just rejecting it.
21800 - If our clock jumps forward by 100 seconds or more, assume something
21801 has gone wrong with our network and abandon all not-yet-used circs.
21802 - When an application is using socks5, give him the whole variety of
21803 potential socks5 responses (connect refused, host unreachable, etc),
21804 rather than just "success" or "failure".
21805 - A more sane version numbering system. See
21806 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
21807 - Change version parsing logic: a version is "obsolete" if it is not
21808 recommended and (1) there is a newer recommended version in the
21809 same series, or (2) there are no recommended versions in the same
21810 series, but there are some recommended versions in a newer series.
21811 A version is "new" if it is newer than any recommended version in
21813 - Report HTTP reasons to client when getting a response from directory
21814 servers -- so you can actually know what went wrong.
21815 - Reject odd-looking addresses at the client (e.g. addresses that
21816 contain a colon), rather than having the server drop them because
21818 - Stop publishing socksport in the directory, since it's not
21819 actually meant to be public. For compatibility, publish a 0 there
21821 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
21822 cookies to disk and doesn't log each web request to disk. (Thanks
21823 to Brett Carrington for pointing this out.)
21824 - Add OSX uninstall instructions. An actual uninstall script will
21826 - Add "opt hibernating 1" to server descriptor to make it clearer
21827 whether the server is hibernating.
21830 Changes in version 0.0.9.10 - 2005-06-16
21831 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
21832 - Refuse relay cells that claim to have a length larger than the
21833 maximum allowed. This prevents a potential attack that could read
21834 arbitrary memory (e.g. keys) from an exit server's process
21838 Changes in version 0.0.9.9 - 2005-04-23
21839 o Bugfixes on 0.0.9.x:
21840 - If unofficial Tor clients connect and send weird TLS certs, our
21841 Tor server triggers an assert. This release contains a minimal
21842 backport from the broader fix that we put into 0.1.0.4-rc.
21845 Changes in version 0.0.9.8 - 2005-04-07
21846 o Bugfixes on 0.0.9.x:
21847 - We have a bug that I haven't found yet. Sometimes, very rarely,
21848 cpuworkers get stuck in the 'busy' state, even though the cpuworker
21849 thinks of itself as idle. This meant that no new circuits ever got
21850 established. Here's a workaround to kill any cpuworker that's been
21851 busy for more than 100 seconds.
21854 Changes in version 0.0.9.7 - 2005-04-01
21855 o Bugfixes on 0.0.9.x:
21856 - Fix another race crash bug (thanks to Glenn Fink for reporting).
21857 - Compare identity to identity, not to nickname, when extending to
21858 a router not already in the directory. This was preventing us from
21859 extending to unknown routers. Oops.
21860 - Make sure to create OS X Tor user in <500 range, so we aren't
21861 creating actual system users.
21862 - Note where connection-that-hasn't-sent-end was marked, and fix
21863 a few really loud instances of this harmless bug (it's fixed more
21867 Changes in version 0.0.9.6 - 2005-03-24
21868 o Bugfixes on 0.0.9.x (crashes and asserts):
21869 - Add new end stream reasons to maintenance branch. Fix bug where
21870 reason (8) could trigger an assert. Prevent bug from recurring.
21871 - Apparently win32 stat wants paths to not end with a slash.
21872 - Fix assert triggers in assert_cpath_layer_ok(), where we were
21873 blowing away the circuit that conn->cpath_layer points to, then
21874 checking to see if the circ is well-formed. Backport check to make
21875 sure we dont use the cpath on a closed connection.
21876 - Prevent circuit_resume_edge_reading_helper() from trying to package
21877 inbufs for marked-for-close streams.
21878 - Don't crash on hup if your options->address has become unresolvable.
21879 - Some systems (like OS X) sometimes accept() a connection and tell
21880 you the remote host is 0.0.0.0:0. If this happens, due to some
21881 other mis-features, we get confused; so refuse the conn for now.
21883 o Bugfixes on 0.0.9.x (other):
21884 - Fix harmless but scary "Unrecognized content encoding" warn message.
21885 - Add new stream error reason: TORPROTOCOL reason means "you are not
21886 speaking a version of Tor I understand; say bye-bye to your stream."
21887 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
21888 into the future, now that we are more tolerant of skew. This
21889 resolves a bug where a Tor server would refuse to cache a directory
21890 because all the directories it gets are too far in the future;
21891 yet the Tor server never logs any complaints about clock skew.
21892 - Mac packaging magic: make man pages useable, and do not overwrite
21893 existing torrc files.
21894 - Make OS X log happily to /var/log/tor/tor.log
21897 Changes in version 0.0.9.5 - 2005-02-22
21898 o Bugfixes on 0.0.9.x:
21899 - Fix an assert race at exit nodes when resolve requests fail.
21900 - Stop picking unverified dir mirrors--it only leads to misery.
21901 - Patch from Matt Edman to make NT services work better. Service
21902 support is still not compiled into the executable by default.
21903 - Patch from Dmitri Bely so the Tor service runs better under
21904 the win32 SYSTEM account.
21905 - Make tor-resolve actually work (?) on Win32.
21906 - Fix a sign bug when getrlimit claims to have 4+ billion
21907 file descriptors available.
21908 - Stop refusing to start when bandwidthburst == bandwidthrate.
21909 - When create cells have been on the onion queue more than five
21910 seconds, just send back a destroy and take them off the list.
21913 Changes in version 0.0.9.4 - 2005-02-03
21914 o Bugfixes on 0.0.9:
21915 - Fix an assert bug that took down most of our servers: when
21916 a server claims to have 1 GB of bandwidthburst, don't
21918 - Don't crash as badly if we have spawned the max allowed number
21919 of dnsworkers, or we're out of file descriptors.
21920 - Block more file-sharing ports in the default exit policy.
21921 - MaxConn is now automatically set to the hard limit of max
21922 file descriptors we're allowed (ulimit -n), minus a few for
21924 - Give a clearer message when servers need to raise their
21925 ulimit -n when they start running out of file descriptors.
21926 - SGI Compatibility patches from Jan Schaumann.
21927 - Tolerate a corrupt cached directory better.
21928 - When a dirserver hasn't approved your server, list which one.
21929 - Go into soft hibernation after 95% of the bandwidth is used,
21930 not 99%. This is especially important for daily hibernators who
21931 have a small accounting max. Hopefully it will result in fewer
21932 cut connections when the hard hibernation starts.
21933 - Load-balance better when using servers that claim more than
21934 800kB/s of capacity.
21935 - Make NT services work (experimental, only used if compiled in).
21938 Changes in version 0.0.9.3 - 2005-01-21
21939 o Bugfixes on 0.0.9:
21940 - Backport the cpu use fixes from main branch, so busy servers won't
21941 need as much processor time.
21942 - Work better when we go offline and then come back, or when we
21943 run Tor at boot before the network is up. We do this by
21944 optimistically trying to fetch a new directory whenever an
21945 application request comes in and we think we're offline -- the
21946 human is hopefully a good measure of when the network is back.
21947 - Backport some minimal hidserv bugfixes: keep rend circuits open as
21948 long as you keep using them; actually publish hidserv descriptors
21949 shortly after they change, rather than waiting 20-40 minutes.
21950 - Enable Mac startup script by default.
21951 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
21952 - When you update AllowUnverifiedNodes or FirewallPorts via the
21953 controller's setconf feature, we were always appending, never
21955 - When you update HiddenServiceDir via setconf, it was screwing up
21956 the order of reading the lines, making it fail.
21957 - Do not rewrite a cached directory back to the cache; otherwise we
21958 will think it is recent and not fetch a newer one on startup.
21959 - Workaround for webservers that lie about Content-Encoding: Tor
21960 now tries to autodetect compressed directories and compression
21961 itself. This lets us Proxypass dir fetches through apache.
21964 Changes in version 0.0.9.2 - 2005-01-04
21965 o Bugfixes on 0.0.9 (crashes and asserts):
21966 - Fix an assert on startup when the disk is full and you're logging
21968 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
21969 style address, then we'd crash.
21970 - Fix an assert trigger when the running-routers string we get from
21971 a dirserver is broken.
21972 - Make worker threads start and run on win32. Now win32 servers
21974 - Bandaid (not actually fix, but now it doesn't crash) an assert
21975 where the dns worker dies mysteriously and the main Tor process
21976 doesn't remember anything about the address it was resolving.
21978 o Bugfixes on 0.0.9 (Win32):
21979 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
21980 name out of the warning/assert messages.
21981 - Fix a superficial "unhandled error on read" bug on win32.
21982 - The win32 installer no longer requires a click-through for our
21983 license, since our Free Software license grants rights but does not
21985 - Win32: When connecting to a dirserver fails, try another one
21986 immediately. (This was already working for non-win32 Tors.)
21987 - Stop trying to parse $HOME on win32 when hunting for default
21989 - Make tor-resolve.c work on win32 by calling network_init().
21991 o Bugfixes on 0.0.9 (other):
21992 - Make 0.0.9.x build on Solaris again.
21993 - Due to a fencepost error, we were blowing away the \n when reporting
21994 confvalue items in the controller. So asking for multiple config
21995 values at once couldn't work.
21996 - When listing circuits that are pending on an opening OR connection,
21997 if we're an OR we were listing circuits that *end* at us as
21998 being pending on every listener, dns/cpu worker, etc. Stop that.
21999 - Dirservers were failing to create 'running-routers' or 'directory'
22000 strings if we had more than some threshold of routers. Fix them so
22001 they can handle any number of routers.
22002 - Fix a superficial "Duplicate mark for close" bug.
22003 - Stop checking for clock skew for OR connections, even for servers.
22004 - Fix a fencepost error that was chopping off the last letter of any
22005 nickname that is the maximum allowed nickname length.
22006 - Update URLs in log messages so they point to the new website.
22007 - Fix a potential problem in mangling server private keys while
22008 writing to disk (not triggered yet, as far as we know).
22009 - Include the licenses for other free software we include in Tor,
22010 now that we're shipping binary distributions more regularly.
22013 Changes in version 0.0.9.1 - 2004-12-15
22014 o Bugfixes on 0.0.9:
22015 - Make hibernation actually work.
22016 - Make HashedControlPassword config option work.
22017 - When we're reporting event circuit status to a controller,
22018 don't use the stream status code.
22021 Changes in version 0.0.9 - 2004-12-12
22022 o Bugfixes on 0.0.8.1 (Crashes and asserts):
22023 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
22024 write() call will fail and we handle it there.
22025 - When we run out of disk space, or other log writing error, don't
22026 crash. Just stop logging to that log and continue.
22027 - Fix isspace() and friends so they still make Solaris happy
22028 but also so they don't trigger asserts on win32.
22029 - Fix assert failure on malformed socks4a requests.
22030 - Fix an assert bug where a hidden service provider would fail if
22031 the first hop of his rendezvous circuit was down.
22032 - Better handling of size_t vs int, so we're more robust on 64
22035 o Bugfixes on 0.0.8.1 (Win32):
22036 - Make windows sockets actually non-blocking (oops), and handle
22037 win32 socket errors better.
22038 - Fix parse_iso_time on platforms without strptime (eg win32).
22039 - win32: when being multithreaded, leave parent fdarray open.
22040 - Better handling of winsock includes on non-MSV win32 compilers.
22041 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
22043 - Make unit tests work on win32.
22045 o Bugfixes on 0.0.8.1 (Path selection and streams):
22046 - Calculate timeout for waiting for a connected cell from the time
22047 we sent the begin cell, not from the time the stream started. If
22048 it took a long time to establish the circuit, we would time out
22049 right after sending the begin cell.
22050 - Fix router_compare_addr_to_addr_policy: it was not treating a port
22051 of * as always matching, so we were picking reject *:* nodes as
22052 exit nodes too. Oops.
22053 - When read() failed on a stream, we would close it without sending
22054 back an end. So 'connection refused' would simply be ignored and
22055 the user would get no response.
22056 - Stop a sigpipe: when an 'end' cell races with eof from the app,
22057 we shouldn't hold-open-until-flush if the eof arrived first.
22058 - Let resolve conns retry/expire also, rather than sticking around
22060 - Fix more dns related bugs: send back resolve_failed and end cells
22061 more reliably when the resolve fails, rather than closing the
22062 circuit and then trying to send the cell. Also attach dummy resolve
22063 connections to a circuit *before* calling dns_resolve(), to fix
22064 a bug where cached answers would never be sent in RESOLVED cells.
22066 o Bugfixes on 0.0.8.1 (Circuits):
22067 - Finally fix a bug that's been plaguing us for a year:
22068 With high load, circuit package window was reaching 0. Whenever
22069 we got a circuit-level sendme, we were reading a lot on each
22070 socket, but only writing out a bit. So we would eventually reach
22071 eof. This would be noticed and acted on even when there were still
22072 bytes sitting in the inbuf.
22073 - Use identity comparison, not nickname comparison, to choose which
22074 half of circuit-ID-space each side gets to use. This is needed
22075 because sometimes we think of a router as a nickname, and sometimes
22076 as a hex ID, and we can't predict what the other side will do.
22078 o Bugfixes on 0.0.8.1 (Other):
22079 - Fix a whole slew of memory leaks.
22080 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
22081 - If we are using select, make sure we stay within FD_SETSIZE.
22082 - When poll() is interrupted, we shouldn't believe the revents values.
22083 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
22084 and smartlist_len, which are two major profiling offenders.
22085 - If do_hup fails, actually notice.
22086 - Flush the log file descriptor after we print "Tor opening log file",
22087 so we don't see those messages days later.
22088 - Hidden service operators now correctly handle version 1 style
22089 INTRODUCE1 cells (nobody generates them still, so not a critical
22091 - Handle more errnos from accept() without closing the listener.
22092 Some OpenBSD machines were closing their listeners because
22093 they ran out of file descriptors.
22094 - Some people had wrapped their tor client/server in a script
22095 that would restart it whenever it died. This did not play well
22096 with our "shut down if your version is obsolete" code. Now people
22097 don't fetch a new directory if their local cached version is
22099 - Make our autogen.sh work on ksh as well as bash.
22100 - Better torrc example lines for dirbindaddress and orbindaddress.
22101 - Improved bounds checking on parsed ints (e.g. config options and
22102 the ones we find in directories.)
22103 - Stop using separate defaults for no-config-file and
22104 empty-config-file. Now you have to explicitly turn off SocksPort,
22105 if you don't want it open.
22106 - We were starting to daemonize before we opened our logs, so if
22107 there were any problems opening logs, we would complain to stderr,
22108 which wouldn't work, and then mysteriously exit.
22109 - If a verified OR connects to us before he's uploaded his descriptor,
22110 or we verify him and hup but he still has the original TLS
22111 connection, then conn->nickname is still set like he's unverified.
22113 o Code security improvements, inspired by Ilja:
22114 - tor_snprintf wrapper over snprintf with consistent (though not C99)
22116 - Replace sprintf with tor_snprintf. (I think they were all safe, but
22118 - Replace strcpy/strncpy with strlcpy in more places.
22119 - Avoid strcat; use tor_snprintf or strlcat instead.
22121 o Features (circuits and streams):
22122 - New circuit building strategy: keep a list of ports that we've
22123 used in the past 6 hours, and always try to have 2 circuits open
22124 or on the way that will handle each such port. Seed us with port
22125 80 so web users won't complain that Tor is "slow to start up".
22126 - Make kill -USR1 dump more useful stats about circuits.
22127 - When warning about retrying or giving up, print the address, so
22128 the user knows which one it's talking about.
22129 - If you haven't used a clean circuit in an hour, throw it away,
22130 just to be on the safe side. (This means after 6 hours a totally
22131 unused Tor client will have no circuits open.)
22132 - Support "foo.nickname.exit" addresses, to let Alice request the
22133 address "foo" as viewed by exit node "nickname". Based on a patch
22134 from Geoff Goodell.
22135 - If your requested entry or exit node has advertised bandwidth 0,
22137 - Be more greedy about filling up relay cells -- we try reading again
22138 once we've processed the stuff we read, in case enough has arrived
22139 to fill the last cell completely.
22140 - Refuse application socks connections to port 0.
22141 - Use only 0.0.9pre1 and later servers for resolve cells.
22143 o Features (bandwidth):
22144 - Hibernation: New config option "AccountingMax" lets you
22145 set how many bytes per month (in each direction) you want to
22146 allow your server to consume. Rather than spreading those
22147 bytes out evenly over the month, we instead hibernate for some
22148 of the month and pop up at a deterministic time, work until
22149 the bytes are consumed, then hibernate again. Config option
22150 "MonthlyAccountingStart" lets you specify which day of the month
22151 your billing cycle starts on.
22152 - Implement weekly/monthly/daily accounting: now you specify your
22153 hibernation properties by
22154 AccountingMax N bytes|KB|MB|GB|TB
22155 AccountingStart day|week|month [day] HH:MM
22156 Defaults to "month 1 0:00".
22157 - Let bandwidth and interval config options be specified as 5 bytes,
22158 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
22160 o Features (directories):
22161 - New "router-status" line in directory, to better bind each verified
22162 nickname to its identity key.
22163 - Clients can ask dirservers for /dir.z to get a compressed version
22164 of the directory. Only works for servers running 0.0.9, of course.
22165 - Make clients cache directories and use them to seed their router
22166 lists at startup. This means clients have a datadir again.
22167 - Respond to content-encoding headers by trying to uncompress as
22169 - Clients and servers now fetch running-routers; cache
22170 running-routers; compress running-routers; serve compressed
22172 - Make moria2 advertise a dirport of 80, so people behind firewalls
22173 will be able to get a directory.
22174 - Http proxy support
22175 - Dirservers translate requests for http://%s:%d/x to /x
22176 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
22177 be routed through this host.
22178 - Clients ask for /tor/x rather than /x for new enough dirservers.
22179 This way we can one day coexist peacefully with apache.
22180 - Clients specify a "Host: %s%d" http header, to be compatible
22181 with more proxies, and so running squid on an exit node can work.
22182 - Protect dirservers from overzealous descriptor uploading -- wait
22183 10 seconds after directory gets dirty, before regenerating.
22185 o Features (packages and install):
22186 - Add NSI installer contributed by J Doe.
22187 - Apply NT service patch from Osamu Fujino. Still needs more work.
22188 - Commit VC6 and VC7 workspace/project files.
22189 - Commit a tor.spec for making RPM files, with help from jbash.
22190 - Add contrib/torctl.in contributed by Glenn Fink.
22191 - Make expand_filename handle ~ and ~username.
22192 - Use autoconf to enable largefile support where necessary. Use
22193 ftello where available, since ftell can fail at 2GB.
22194 - Ship src/win32/ in the tarball, so people can use it to build.
22195 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
22198 o Features (ui controller):
22199 - Control interface: a separate program can now talk to your
22200 client/server over a socket, and get/set config options, receive
22201 notifications of circuits and streams starting/finishing/dying,
22202 bandwidth used, etc. The next step is to get some GUIs working.
22203 Let us know if you want to help out. See doc/control-spec.txt .
22204 - Ship a contrib/tor-control.py as an example script to interact
22205 with the control port.
22206 - "tor --hash-password zzyxz" will output a salted password for
22207 use in authenticating to the control interface.
22208 - Implement the control-spec's SAVECONF command, to write your
22209 configuration to torrc.
22210 - Get cookie authentication for the controller closer to working.
22211 - When set_conf changes our server descriptor, upload a new copy.
22212 But don't upload it too often if there are frequent changes.
22214 o Features (config and command-line):
22215 - Deprecate unofficial config option abbreviations, and abbreviations
22216 not on the command line.
22217 - Configuration infrastructure support for warning on obsolete
22219 - Give a slightly more useful output for "tor -h".
22220 - Break DirFetchPostPeriod into:
22221 - DirFetchPeriod for fetching full directory,
22222 - StatusFetchPeriod for fetching running-routers,
22223 - DirPostPeriod for posting server descriptor,
22224 - RendPostPeriod for posting hidden service descriptors.
22225 - New log format in config:
22226 "Log minsev[-maxsev] stdout|stderr|syslog" or
22227 "Log minsev[-maxsev] file /var/foo"
22228 - DirPolicy config option, to let people reject incoming addresses
22229 from their dirserver.
22230 - "tor --list-fingerprint" will list your identity key fingerprint
22232 - Make tor --version --version dump the cvs Id of every file.
22233 - New 'MyFamily nick1,...' config option for a server to
22234 specify other servers that shouldn't be used in the same circuit
22235 with it. Only believed if nick1 also specifies us.
22236 - New 'NodeFamily nick1,nick2,...' config option for a client to
22237 specify nodes that it doesn't want to use in the same circuit.
22238 - New 'Redirectexit pattern address:port' config option for a
22239 server to redirect exit connections, e.g. to a local squid.
22240 - Add "pass" target for RedirectExit, to make it easier to break
22241 out of a sequence of RedirectExit rules.
22242 - Make the dirservers file obsolete.
22243 - Include a dir-signing-key token in directories to tell the
22244 parsing entity which key is being used to sign.
22245 - Remove the built-in bulky default dirservers string.
22246 - New config option "Dirserver %s:%d [fingerprint]", which can be
22247 repeated as many times as needed. If no dirservers specified,
22248 default to moria1,moria2,tor26.
22249 - Make 'Routerfile' config option obsolete.
22250 - Discourage people from setting their dirfetchpostperiod more often
22251 than once per minute.
22253 o Features (other):
22254 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
22255 get back to normal.)
22256 - Accept *:706 (silc) in default exit policy.
22257 - Implement new versioning format for post 0.1.
22258 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
22259 log more informatively.
22260 - Check clock skew for verified servers, but allow unverified
22261 servers and clients to have any clock skew.
22262 - Make sure the hidden service descriptors are at a random offset
22263 from each other, to hinder linkability.
22264 - Clients now generate a TLS cert too, in preparation for having
22265 them act more like real nodes.
22266 - Add a pure-C tor-resolve implementation.
22267 - Use getrlimit and friends to ensure we can reach MaxConn (currently
22268 1024) file descriptors.
22269 - Raise the max dns workers from 50 to 100.
22272 Changes in version 0.0.8.1 - 2004-10-13
22274 - Fix a seg fault that can be triggered remotely for Tor
22275 clients/servers with an open dirport.
22276 - Fix a rare assert trigger, where routerinfos for entries in
22277 our cpath would expire while we're building the path.
22278 - Fix a bug in OutboundBindAddress so it (hopefully) works.
22279 - Fix a rare seg fault for people running hidden services on
22280 intermittent connections.
22281 - Fix a bug in parsing opt keywords with objects.
22282 - Fix a stale pointer assert bug when a stream detaches and
22284 - Fix a string format vulnerability (probably not exploitable)
22285 in reporting stats locally.
22286 - Fix an assert trigger: sometimes launching circuits can fail
22287 immediately, e.g. because too many circuits have failed recently.
22288 - Fix a compile warning on 64 bit platforms.
22291 Changes in version 0.0.8 - 2004-08-25
22293 - Made our unit tests compile again on OpenBSD 3.5, and tor
22294 itself compile again on OpenBSD on a sparc64.
22295 - We were neglecting milliseconds when logging on win32, so
22296 everything appeared to happen at the beginning of each second.
22297 - Check directory signature _before_ you decide whether you're
22298 you're running an obsolete version and should exit.
22299 - Check directory signature _before_ you parse the running-routers
22300 list to decide who's running.
22301 - Check return value of fclose while writing to disk, so we don't
22302 end up with broken files when servers run out of disk space.
22303 - Port it to SunOS 5.9 / Athena
22304 - Fix two bugs in saving onion keys to disk when rotating, so
22305 hopefully we'll get fewer people using old onion keys.
22306 - Remove our mostly unused -- and broken -- hex_encode()
22307 function. Use base16_encode() instead. (Thanks to Timo Lindfors
22308 for pointing out this bug.)
22309 - Only pick and establish intro points after we've gotten a
22311 - Fix assert triggers: if the other side returns an address 0.0.0.0,
22312 don't put it into the client dns cache.
22313 - If a begin failed due to exit policy, but we believe the IP
22314 address should have been allowed, switch that router to exitpolicy
22315 reject *:* until we get our next directory.
22317 o Protocol changes:
22318 - 'Extend' relay cell payloads now include the digest of the
22319 intended next hop's identity key. Now we can verify that we're
22320 extending to the right router, and also extend to routers we
22321 hadn't heard of before.
22324 - Tor nodes can now act as relays (with an advertised ORPort)
22325 without being manually verified by the dirserver operators.
22326 - Uploaded descriptors of unverified routers are now accepted
22327 by the dirservers, and included in the directory.
22328 - Verified routers are listed by nickname in the running-routers
22329 list; unverified routers are listed as "$<fingerprint>".
22330 - We now use hash-of-identity-key in most places rather than
22331 nickname or addr:port, for improved security/flexibility.
22332 - AllowUnverifiedNodes config option to let circuits choose no-name
22333 routers in entry,middle,exit,introduction,rendezvous positions.
22334 Allow middle and rendezvous positions by default.
22335 - When picking unverified routers, skip those with low uptime and/or
22336 low bandwidth, depending on what properties you care about.
22337 - ClientOnly option for nodes that never want to become servers.
22338 - Directory caching.
22339 - "AuthoritativeDir 1" option for the official dirservers.
22340 - Now other nodes (clients and servers) will cache the latest
22341 directory they've pulled down.
22342 - They can enable their DirPort to serve it to others.
22343 - Clients will pull down a directory from any node with an open
22344 DirPort, and check the signature/timestamp correctly.
22345 - Authoritative dirservers now fetch directories from other
22346 authdirservers, to stay better synced.
22347 - Running-routers list tells who's down also, along with noting
22348 if they're verified (listed by nickname) or unverified (listed
22350 - Allow dirservers to serve running-router list separately.
22351 This isn't used yet.
22352 - You can now fetch $DIRURL/running-routers to get just the
22353 running-routers line, not the whole descriptor list. (But
22354 clients don't use this yet.)
22355 - Clients choose nodes proportional to advertised bandwidth.
22356 - Clients avoid using nodes with low uptime as introduction points.
22357 - Handle servers with dynamic IP addresses: don't just replace
22358 options->Address with the resolved one at startup, and
22359 detect our address right before we make a routerinfo each time.
22360 - 'FascistFirewall' option to pick dirservers and ORs on specific
22361 ports; plus 'FirewallPorts' config option to tell FascistFirewall
22362 which ports are open. (Defaults to 80,443)
22363 - Try other dirservers immediately if the one you try is down. This
22364 should tolerate down dirservers better now.
22365 - ORs connect-on-demand to other ORs
22366 - If you get an extend cell to an OR you're not connected to,
22367 connect, handshake, and forward the create cell.
22368 - The authoritative dirservers stay connected to everybody,
22369 and everybody stays connected to 0.0.7 servers, but otherwise
22370 clients/servers expire unused connections after 5 minutes.
22371 - When servers get a sigint, they delay 30 seconds (refusing new
22372 connections) then exit. A second sigint causes immediate exit.
22373 - File and name management:
22374 - Look for .torrc if no CONFDIR "torrc" is found.
22375 - If no datadir is defined, then choose, make, and secure ~/.tor
22377 - If torrc not found, exitpolicy reject *:*.
22378 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
22379 - If no nickname is defined, derive default from hostname.
22380 - Rename secret key files, e.g. identity.key -> secret_id_key,
22381 to discourage people from mailing their identity key to tor-ops.
22382 - Refuse to build a circuit before the directory has arrived --
22383 it won't work anyway, since you won't know the right onion keys
22385 - Parse tor version numbers so we can do an is-newer-than check
22386 rather than an is-in-the-list check.
22387 - New socks command 'resolve', to let us shim gethostbyname()
22389 - A 'tor_resolve' script to access the socks resolve functionality.
22390 - A new socks-extensions.txt doc file to describe our
22391 interpretation and extensions to the socks protocols.
22392 - Add a ContactInfo option, which gets published in descriptor.
22393 - Write tor version at the top of each log file
22394 - New docs in the tarball:
22396 - Document that you should proxy your SSL traffic too.
22397 - Log a warning if the user uses an unsafe socks variant, so people
22398 are more likely to learn about privoxy or socat.
22399 - Log a warning if you're running an unverified server, to let you
22400 know you might want to get it verified.
22401 - Change the default exit policy to reject the default edonkey,
22402 kazaa, gnutella ports.
22403 - Add replace_file() to util.[ch] to handle win32's rename().
22404 - Publish OR uptime in descriptor (and thus in directory) too.
22405 - Remember used bandwidth (both in and out), and publish 15-minute
22406 snapshots for the past day into our descriptor.
22407 - Be more aggressive about trying to make circuits when the network
22408 has changed (e.g. when you unsuspend your laptop).
22409 - Check for time skew on http headers; report date in response to
22411 - If the entrynode config line has only one node, don't pick it as
22413 - Add strict{entry|exit}nodes config options. If set to 1, then
22414 we refuse to build circuits that don't include the specified entry
22416 - OutboundBindAddress config option, to bind to a specific
22417 IP address for outgoing connect()s.
22418 - End truncated log entries (e.g. directories) with "[truncated]".
22421 Changes in version 0.0.7.3 - 2004-08-12
22422 o Stop dnsworkers from triggering an assert failure when you
22423 ask them to resolve the host "".
22426 Changes in version 0.0.7.2 - 2004-07-07
22427 o A better fix for the 0.0.0.0 problem, that will hopefully
22428 eliminate the remaining related assertion failures.
22431 Changes in version 0.0.7.1 - 2004-07-04
22432 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
22433 since internally we use 0.0.0.0 to signify "not yet resolved".
22436 Changes in version 0.0.7 - 2004-06-07
22437 o Fixes for crashes and other obnoxious bugs:
22438 - Fix an epipe bug: sometimes when directory connections failed
22439 to connect, we would give them a chance to flush before closing
22441 - When we detached from a circuit because of resolvefailed, we
22442 would immediately try the same circuit twice more, and then
22443 give up on the resolve thinking we'd tried three different
22445 - Limit the number of intro circuits we'll attempt to build for a
22446 hidden service per 15-minute period.
22447 - Check recommended-software string *early*, before actually parsing
22448 the directory. Thus we can detect an obsolete version and exit,
22449 even if the new directory format doesn't parse.
22450 o Fixes for security bugs:
22451 - Remember which nodes are dirservers when you startup, and if a
22452 random OR enables his dirport, don't automatically assume he's
22453 a trusted dirserver.
22455 - Directory connections were asking the wrong poll socket to
22456 start writing, and not asking themselves to start writing.
22457 - When we detached from a circuit because we sent a begin but
22458 didn't get a connected, we would use it again the first time;
22459 but after that we would correctly switch to a different one.
22460 - Stop warning when the first onion decrypt attempt fails; they
22461 will sometimes legitimately fail now that we rotate keys.
22462 - Override unaligned-access-ok check when $host_cpu is ia64 or
22463 arm. Apparently they allow it but the kernel whines.
22464 - Dirservers try to reconnect periodically too, in case connections
22466 - Fix some memory leaks in directory servers.
22467 - Allow backslash in Win32 filenames.
22468 - Made Tor build complain-free on FreeBSD, hopefully without
22469 breaking other BSD builds. We'll see.
22470 - Check directory signatures based on name of signer, not on whom
22471 we got the directory from. This will let us cache directories more
22473 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
22476 - Doxygen markup on all functions and global variables.
22477 - Make directory functions update routerlist, not replace it. So
22478 now directory disagreements are not so critical a problem.
22479 - Remove the upper limit on number of descriptors in a dirserver's
22480 directory (not that we were anywhere close).
22481 - Allow multiple logfiles at different severity ranges.
22482 - Allow *BindAddress to specify ":port" rather than setting *Port
22483 separately. Allow multiple instances of each BindAddress config
22484 option, so you can bind to multiple interfaces if you want.
22485 - Allow multiple exit policy lines, which are processed in order.
22486 Now we don't need that huge line with all the commas in it.
22487 - Enable accept/reject policies on SOCKS connections, so you can bind
22488 to 0.0.0.0 but still control who can use your OP.
22489 - Updated the man page to reflect these features.
22492 Changes in version 0.0.6.2 - 2004-05-16
22493 o Our integrity-checking digest was checking only the most recent cell,
22494 not the previous cells like we'd thought.
22495 Thanks to Stefan Mark for finding the flaw!
22498 Changes in version 0.0.6.1 - 2004-05-06
22499 o Fix two bugs in our AES counter-mode implementation (this affected
22500 onion-level stream encryption, but not TLS-level). It turns
22501 out we were doing something much more akin to a 16-character
22502 polyalphabetic cipher. Oops.
22503 Thanks to Stefan Mark for finding the flaw!
22504 o Retire moria3 as a directory server, and add tor26 as a directory
22508 Changes in version 0.0.6 - 2004-05-02
22510 - Hidden services and rendezvous points are implemented. Go to
22511 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
22512 hidden services. (This only works via a socks4a proxy such as
22513 Privoxy, and currently it's quite slow.)
22514 - We now rotate link (tls context) keys and onion keys.
22515 - CREATE cells now include oaep padding, so you can tell
22516 if you decrypted them correctly.
22517 - Retry stream correctly when we fail to connect because of
22518 exit-policy-reject (should try another) or can't-resolve-address.
22519 - When we hup a dirserver and we've *removed* a server from the
22520 approved-routers list, now we remove that server from the
22521 in-memory directories too.
22522 - Add bandwidthburst to server descriptor.
22523 - Directories now say which dirserver signed them.
22524 - Use a tor_assert macro that logs failed assertions too.
22525 - Since we don't support truncateds much, don't bother sending them;
22526 just close the circ.
22527 - Fetch randomness from /dev/urandom better (not via fopen/fread)
22528 - Better debugging for tls errors
22529 - Set Content-Type on the directory and hidserv descriptor.
22530 - Remove IVs from cipher code, since AES-ctr has none.
22532 - Fix an assert trigger for exit nodes that's been plaguing us since
22533 the days of 0.0.2prexx (thanks weasel!)
22534 - Fix a bug where we were closing tls connections intermittently.
22535 It turns out openssl keeps its errors around -- so if an error
22536 happens, and you don't ask about it, and then another openssl
22537 operation happens and succeeds, and you ask if there was an error,
22538 it tells you about the first error.
22539 - Fix a bug that's been lurking since 27 may 03 (!)
22540 When passing back a destroy cell, we would use the wrong circ id.
22541 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
22542 - Some versions of openssl have an SSL_pending function that erroneously
22543 returns bytes when there is a non-application record pending.
22544 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
22545 o We were using an array of length zero in a few places.
22546 o Win32's gethostbyname can't resolve an IP to an IP.
22547 o Win32's close can't close a socket.
22548 o Handle windows socket errors correctly.
22550 - check for <sys/limits.h> so we build on FreeBSD again, and
22551 <machine/limits.h> for NetBSD.
22554 Changes in version 0.0.5 - 2004-03-30
22555 o Install torrc as torrc.sample -- we no longer clobber your
22557 o Fix mangled-state bug in directory fetching (was causing sigpipes).
22558 o Only build circuits after we've fetched the directory: clients were
22559 using only the directory servers before they'd fetched a directory.
22560 This also means longer startup time; so it goes.
22561 o Fix an assert trigger where an OP would fail to handshake, and we'd
22562 expect it to have a nickname.
22563 o Work around a tsocks bug: do a socks reject when AP connection dies
22564 early, else tsocks goes into an infinite loop.
22565 o Hold socks connection open until reply is flushed (if possible)
22566 o Make exit nodes resolve IPs to IPs immediately, rather than asking
22567 the dns farm to do it.
22568 o Fix c99 aliasing warnings in rephist.c
22569 o Don't include server descriptors that are older than 24 hours in the
22571 o Give socks 'reject' replies their whole 15s to attempt to flush,
22572 rather than seeing the 60s timeout and assuming the flush had failed.
22573 o Clean automake droppings from the cvs repository
22574 o Add in a 'notice' log level for things the operator should hear
22575 but that aren't warnings
22578 Changes in version 0.0.4 - 2004-03-26
22579 o When connecting to a dirserver or OR and the network is down,
22583 Changes in version 0.0.3 - 2004-03-26
22584 o Warn and fail if server chose a nickname with illegal characters
22585 o Port to Solaris and Sparc:
22586 - include missing header fcntl.h
22587 - have autoconf find -lsocket -lnsl automatically
22588 - deal with hardware word alignment
22589 - make uname() work (solaris has a different return convention)
22590 - switch from using signal() to sigaction()
22591 o Preliminary work on reputation system:
22592 - Keep statistics on success/fail of connect attempts; they're published
22593 by kill -USR1 currently.
22594 - Add a RunTesting option to try to learn link state by creating test
22595 circuits, even when SocksPort is off.
22596 - Remove unused open circuits when there are too many.
22599 Changes in version 0.0.2 - 2004-03-19
22600 - Include strlcpy and strlcat for safer string ops
22601 - define INADDR_NONE so we compile (but still not run) on solaris
22604 Changes in version 0.0.2pre27 - 2004-03-14
22606 - Allow internal tor networks (we were rejecting internal IPs,
22607 now we allow them if they're set explicitly).
22608 - And fix a few endian issues.
22611 Changes in version 0.0.2pre26 - 2004-03-14
22613 - If a stream times out after 15s without a connected cell, don't
22614 try that circuit again: try a new one.
22615 - Retry streams at most 4 times. Then give up.
22616 - When a dirserver gets a descriptor from an unknown router, it
22617 logs its fingerprint (so the dirserver operator can choose to
22618 accept it even without mail from the server operator).
22619 - Inform unapproved servers when we reject their descriptors.
22620 - Make tor build on Windows again. It works as a client, who knows
22622 - Clearer instructions in the torrc for how to set up a server.
22623 - Be more efficient about reading fd's when our global token bucket
22624 (used for rate limiting) becomes empty.
22626 - Stop asserting that computers always go forward in time. It's
22628 - When we sent a cell (e.g. destroy) and then marked an OR connection
22629 expired, we might close it before finishing a flush if the other
22630 side isn't reading right then.
22631 - Don't allow dirservers to start if they haven't defined
22632 RecommendedVersions
22633 - We were caching transient dns failures. Oops.
22634 - Prevent servers from publishing an internal IP as their address.
22635 - Address a strcat vulnerability in circuit.c
22638 Changes in version 0.0.2pre25 - 2004-03-04
22640 - Put the OR's IP in its router descriptor, not its fqdn. That way
22641 we'll stop being stalled by gethostbyname for nodes with flaky dns,
22644 - If the user typed in an address that didn't resolve, the server
22648 Changes in version 0.0.2pre24 - 2004-03-03
22650 - Fix an assertion failure in dns.c, where we were trying to dequeue
22651 a pending dns resolve even if it wasn't pending
22652 - Fix a spurious socks5 warning about still trying to write after the
22653 connection is finished.
22654 - Hold certain marked_for_close connections open until they're finished
22655 flushing, rather than losing bytes by closing them too early.
22656 - Correctly report the reason for ending a stream
22657 - Remove some duplicate calls to connection_mark_for_close
22658 - Put switch_id and start_daemon earlier in the boot sequence, so it
22659 will actually try to chdir() to options.DataDirectory
22660 - Make 'make test' exit(1) if a test fails; fix some unit tests
22661 - Make tor fail when you use a config option it doesn't know about,
22662 rather than warn and continue.
22663 - Make --version work
22664 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
22667 Changes in version 0.0.2pre23 - 2004-02-29
22669 - Print a statement when the first circ is finished, so the user
22670 knows it's working.
22671 - If a relay cell is unrecognized at the end of the circuit,
22672 send back a destroy. (So attacks to mutate cells are more
22674 - New config option 'excludenodes' to avoid certain nodes for circuits.
22675 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
22676 so you can collect coredumps there.
22678 - Fix a bug in tls flushing where sometimes data got wedged and
22679 didn't flush until more data got sent. Hopefully this bug was
22680 a big factor in the random delays we were seeing.
22681 - Make 'connected' cells include the resolved IP, so the client
22682 dns cache actually gets populated.
22683 - Disallow changing from ORPort=0 to ORPort>0 on hup.
22684 - When we time-out on a stream and detach from the circuit, send an
22685 end cell down it first.
22686 - Only warn about an unknown router (in exitnodes, entrynodes,
22687 excludenodes) after we've fetched a directory.
22690 Changes in version 0.0.2pre22 - 2004-02-26
22692 - Servers publish less revealing uname information in descriptors.
22693 - More memory tracking and assertions, to crash more usefully when
22695 - If the default torrc isn't there, just use some default defaults.
22696 Plus provide an internal dirservers file if they don't have one.
22697 - When the user tries to use Tor as an http proxy, give them an http
22698 501 failure explaining that we're a socks proxy.
22699 - Dump a new router.desc on hup, to help confused people who change
22700 their exit policies and then wonder why router.desc doesn't reflect
22702 - Clean up the generic tor.sh init script that we ship with.
22704 - If the exit stream is pending on the resolve, and a destroy arrives,
22705 then the stream wasn't getting removed from the pending list. I
22706 think this was the one causing recent server crashes.
22707 - Use a more robust poll on OSX 10.3, since their poll is flaky.
22708 - When it couldn't resolve any dirservers, it was useless from then on.
22709 Now it reloads the RouterFile (or default dirservers) if it has no
22711 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
22712 many users don't even *have* a /usr/local/sbin/.
22715 Changes in version 0.0.2pre21 - 2004-02-18
22717 - There's a ChangeLog file that actually reflects the changelog.
22718 - There's a 'torify' wrapper script, with an accompanying
22719 tor-tsocks.conf, that simplifies the process of using tsocks for
22720 tor. It even has a man page.
22721 - The tor binary gets installed to sbin rather than bin now.
22722 - Retry streams where the connected cell hasn't arrived in 15 seconds
22723 - Clean up exit policy handling -- get the default out of the torrc,
22724 so we can update it without forcing each server operator to fix
22726 - Allow imaps and pop3s in default exit policy
22728 - Prevent picking middleman nodes as the last node in the circuit
22731 Changes in version 0.0.2pre20 - 2004-01-30
22733 - We now have a deb package, and it's in debian unstable. Go to
22734 it, apt-getters. :)
22735 - I've split the TotalBandwidth option into BandwidthRate (how many
22736 bytes per second you want to allow, long-term) and
22737 BandwidthBurst (how many bytes you will allow at once before the cap
22738 kicks in). This better token bucket approach lets you, say, set
22739 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
22740 performance while not exceeding your monthly bandwidth quota.
22741 - Push out a tls record's worth of data once you've got it, rather
22742 than waiting until you've read everything waiting to be read. This
22743 may improve performance by pipelining better. We'll see.
22744 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
22745 from failed circuits (if they haven't been connected yet) and attach
22747 - Expire old streams that haven't managed to connect. Some day we'll
22748 have them reattach to new circuits instead.
22751 - Fix several memory leaks that were causing servers to become bloated
22753 - Fix a few very rare assert triggers. A few more remain.
22754 - Setuid to User _before_ complaining about running as root.
22757 Changes in version 0.0.2pre19 - 2004-01-07
22759 - Fix deadlock condition in dns farm. We were telling a child to die by
22760 closing the parent's file descriptor to him. But newer children were
22761 inheriting the open file descriptor from the parent, and since they
22762 weren't closing it, the socket never closed, so the child never read
22763 eof, so he never knew to exit. Similarly, dns workers were holding
22764 open other sockets, leading to all sorts of chaos.
22765 - New cleaner daemon() code for forking and backgrounding.
22766 - If you log to a file, it now prints an entry at the top of the
22767 logfile so you know it's working.
22768 - The onionskin challenge length was 30 bytes longer than necessary.
22769 - Started to patch up the spec so it's not quite so out of date.
22772 Changes in version 0.0.2pre18 - 2004-01-02
22774 - Fix endian issues with the 'integrity' field in the relay header.
22775 - Fix a potential bug where connections in state
22776 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
22779 Changes in version 0.0.2pre17 - 2003-12-30
22781 - Made --debuglogfile (or any second log file, actually) work.
22782 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
22783 adversary could force us into an infinite loop.
22786 - Each onionskin handshake now includes a hash of the computed key,
22787 to prove the server's identity and help perfect forward secrecy.
22788 - Changed cell size from 256 to 512 bytes (working toward compatibility
22790 - Changed cell length to 2 bytes, and moved it to the relay header.
22791 - Implemented end-to-end integrity checking for the payloads of
22793 - Separated streamid from 'recognized' (otherwise circuits will get
22794 messed up when we try to have streams exit from the middle). We
22795 use the integrity-checking to confirm that a cell is addressed to
22797 - Randomize the initial circid and streamid values, so an adversary who
22798 breaks into a node can't learn how many circuits or streams have
22802 Changes in version 0.0.2pre16 - 2003-12-14
22804 - Fixed a bug that made HUP trigger an assert
22805 - Fixed a bug where a circuit that immediately failed wasn't being
22806 counted as a failed circuit in counting retries.
22809 - Now we close the circuit when we get a truncated cell: otherwise we're
22810 open to an anonymity attack where a bad node in the path truncates
22811 the circuit and then we open streams at him.
22812 - Add port ranges to exit policies
22813 - Add a conservative default exit policy
22814 - Warn if you're running tor as root
22815 - on HUP, retry OR connections and close/rebind listeners
22816 - options.EntryNodes: try these nodes first when picking the first node
22817 - options.ExitNodes: if your best choices happen to include any of
22818 your preferred exit nodes, you choose among just those preferred
22820 - options.ExcludedNodes: nodes that are never picked in path building
22823 Changes in version 0.0.2pre15 - 2003-12-03
22824 o Robustness and bugfixes:
22825 - Sometimes clients would cache incorrect DNS resolves, which would
22826 really screw things up.
22827 - An OP that goes offline would slowly leak all its sockets and stop
22829 - A wide variety of bugfixes in exit node selection, exit policy
22830 handling, and processing pending streams when a new circuit is
22832 - Pick nodes for a path only from those the directory says are up
22833 - Choose randomly from all running dirservers, not always the first one
22834 - Increase allowed http header size for directory fetch.
22835 - Stop writing to stderr (if we're daemonized it will be closed).
22836 - Enable -g always, so cores will be more useful to me.
22837 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
22840 - Wrote a man page. It lists commonly used options.
22843 - Change default loglevel to warn.
22844 - Make PidFile default to null rather than littering in your CWD.
22845 - OnionRouter config option is now obsolete. Instead it just checks
22847 - Moved to a single unified torrc file for both clients and servers.
22850 Changes in version 0.0.2pre14 - 2003-11-29
22851 o Robustness and bugfixes:
22852 - Force the admin to make the DataDirectory himself
22853 - to get ownership/permissions right
22854 - so clients no longer make a DataDirectory and then never use it
22855 - fix bug where a client who was offline for 45 minutes would never
22856 pull down a directory again
22857 - fix (or at least hide really well) the dns assert bug that was
22858 causing server crashes
22859 - warnings and improved robustness wrt clockskew for certs
22860 - use the native daemon(3) to daemonize, when available
22861 - exit if bind() fails
22862 - exit if neither socksport nor orport is defined
22863 - include our own tor_timegm (Win32 doesn't have its own)
22864 - bugfix for win32 with lots of connections
22865 - fix minor bias in PRNG
22866 - make dirserver more robust to corrupt cached directory
22869 - Wrote the design document (woo)
22871 o Circuit building and exit policies:
22872 - Circuits no longer try to use nodes that the directory has told them
22874 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
22875 bitcounts (18.0.0.0/8).
22876 - Make AP connections standby for a circuit if no suitable circuit
22877 exists, rather than failing
22878 - Circuits choose exit node based on addr/port, exit policies, and
22879 which AP connections are standing by
22880 - Bump min pathlen from 2 to 3
22881 - Relay end cells have a payload to describe why the stream ended.
22882 - If the stream failed because of exit policy, try again with a new
22884 - Clients have a dns cache to remember resolved addresses.
22885 - Notice more quickly when we have no working circuits
22888 - APPort is now called SocksPort
22889 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
22891 - RecommendedVersions is now a config variable rather than
22892 hardcoded (for dirservers)
22893 - Reloads config on HUP
22894 - Usage info on -h or --help
22895 - If you set User and Group config vars, it'll setu/gid to them.
22897 Changes in version 0.0.2pre13 - 2003-10-19
22898 o General stability:
22899 - SSL_write no longer fails when it returns WANTWRITE and the number
22900 of bytes in the buf has changed by the next SSL_write call.
22901 - Fix segfault fetching directory when network is down
22902 - Fix a variety of minor memory leaks
22903 - Dirservers reload the fingerprints file on HUP, so I don't have
22904 to take down the network when I approve a new router
22905 - Default server config file has explicit Address line to specify fqdn
22908 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
22909 - Make listener connections not ever alloc bufs
22911 o Autoconf improvements:
22912 - don't clobber an external CFLAGS in ./configure
22913 - Make install now works
22914 - create var/lib/tor on make install
22915 - autocreate a tor.sh initscript to help distribs
22916 - autocreate the torrc and sample-server-torrc with correct paths
22918 o Log files and Daemonizing now work:
22919 - If --DebugLogFile is specified, log to it at -l debug
22920 - If --LogFile is specified, use it instead of commandline
22921 - If --RunAsDaemon is set, tor forks and backgrounds on startup