1 Changes in version 0.4.1.3-alpha - 2019-06-25
2 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
3 alpha, most of them from earlier release series.
5 o Major bugfixes (Onion service reachability):
6 - Properly clean up the introduction point map when circuits change
7 purpose from onion service circuits to pathbias, measurement, or
8 other circuit types. This should fix some service-side instances
9 of introduction point failure. Fixes bug 29034; bugfix
12 o Minor features (geoip):
13 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
14 Country database. Closes ticket 30852.
16 o Minor features (logging):
17 - Give a more useful assertion failure message if we think we have
18 minherit() but we fail to make a region non-inheritable. Give a
19 compile-time warning if our support for minherit() is incomplete.
22 o Minor bugfixes (circuit isolation):
23 - Fix a logic error that prevented the SessionGroup sub-option from
24 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
26 o Minor bugfixes (continuous integration):
27 - Allow the test-stem job to fail in Travis, because it sometimes
28 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
29 - Skip test_rebind on macOS in Travis, because it is unreliable on
30 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
31 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
32 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
34 o Minor bugfixes (directory authorities):
35 - Stop crashing after parsing an unknown descriptor purpose
36 annotation. We think this bug can only be triggered by modifying a
37 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
39 o Minor bugfixes (pluggable transports):
40 - When running as a bridge with pluggable transports, always publish
41 pluggable transport information in our extrainfo descriptor, even
42 if ExtraInfoStatistics is 0. This information is needed by
43 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
46 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
50 Changes in version 0.4.1.2-alpha - 2019-06-06
51 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
52 previous alpha, and some much older. It also contains minor testing
53 improvements, and an improvement to the security of our authenticated
54 SENDME implementation.
56 o Major bugfixes (bridges):
57 - Consider our directory information to have changed when our list
58 of bridges changes. Previously, Tor would not re-compute the
59 status of its directory information when bridges changed, and
60 therefore would not realize that it was no longer able to build
61 circuits. Fixes part of bug 29875.
62 - Do not count previously configured working bridges towards our
63 total of working bridges. Previously, when Tor's list of bridges
64 changed, it would think that the old bridges were still usable,
65 and delay fetching router descriptors for the new ones. Fixes part
66 of bug 29875; bugfix on 0.3.0.1-alpha.
68 o Major bugfixes (flow control, SENDME):
69 - Decrement the stream-level package window after packaging a cell.
70 Previously, it was done inside a log_debug() call, meaning that if
71 debug logs were not enabled, the decrement would never happen, and
72 thus the window would be out of sync with the other end point.
73 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
75 o Major bugfixes (onion service reachability):
76 - Properly clean up the introduction point map and associated state
77 when circuits change purpose from onion service circuits to
78 pathbias, measurement, or other circuit types. This may fix some
79 instances of introduction point failure. Fixes bug 29034; bugfix
82 o Minor features (authenticated SENDME):
83 - Ensure that there is enough randomness on every circuit to prevent
84 an attacker from successfully predicting the hashes they will need
85 to include in authenticated SENDME cells. At a random interval, if
86 we have not sent randomness already, we now leave some extra space
87 at the end of a cell that we can fill with random bytes. Closes
90 o Minor features (continuous integration):
91 - When running coverage builds on Travis, we now set
92 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
95 o Minor features (maintenance):
96 - Add a new "make autostyle" target that developers can use to apply
97 all automatic Tor style and consistency conversions to the
98 codebase. Closes ticket 30539.
100 o Minor features (testing):
101 - The circuitpadding tests now use a reproducible RNG implementation,
102 so that if a test fails, we can learn why. Part of ticket 28878.
103 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
104 to set the RNG seed for tests that use a reproducible RNG. Part of
106 - When running tests in coverage mode, take additional care to make
107 our coverage deterministic, so that we can accurately track
108 changes in code coverage. Closes ticket 30519.
110 o Minor bugfixes (configuration, proxies):
111 - Fix a bug that prevented us from supporting SOCKS5 proxies that
112 want authentication along with configured (but unused!)
113 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
115 o Minor bugfixes (controller):
116 - POSTDESCRIPTOR requests should work again. Previously, they were
117 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
119 - Repair the HSFETCH command so that it works again. Previously, it
120 expected a body when it shouldn't have. Fixes bug 30646; bugfix
123 o Minor bugfixes (developer tooling):
124 - Fix pre-push hook to allow fixup and squash commits when pushing
125 to non-upstream git remote. Fixes bug 30286; bugfix
128 o Minor bugfixes (directory authority):
129 - Move the "bandwidth-file-headers" line in directory authority
130 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
133 o Minor bugfixes (NetBSD):
134 - Fix usage of minherit() on NetBSD and other platforms that define
135 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
136 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
138 o Minor bugfixes (out-of-memory handler):
139 - When purging the DNS cache because of an out-of-memory condition,
140 try purging just the older entries at first. Previously, we would
141 always purge the whole thing. Fixes bug 29617; bugfix
144 o Minor bugfixes (portability):
145 - Avoid crashing in our tor_vasprintf() implementation on systems
146 that define neither vasprintf() nor _vscprintf(). (This bug has
147 been here long enough that we question whether people are running
148 Tor on such systems, but we're applying the fix out of caution.)
149 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
152 o Minor bugfixes (shutdown, libevent, memory safety):
153 - Avoid use-after-free bugs when shutting down, by making sure that
154 we shut down libevent only after shutting down all of its users.
155 We believe these are harmless in practice, since they only occur
156 on the shutdown path, and do not involve any attacker-controlled
157 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
159 o Minor bugfixes (static analysis):
160 - Fix several spurious Coverity warnings about the unit tests, to
161 lower our chances of missing real warnings in the future. Fixes
162 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
165 - Specify torrc paths (with empty files) when launching tor in
166 integration tests; refrain from reading user and system torrcs.
167 Resolves issue 29702.
170 Changes in version 0.4.1.1-alpha - 2019-05-22
171 This is the first alpha in the 0.4.1.x series. It introduces
172 lightweight circuit padding to make some onion-service circuits harder
173 to distinguish, includes a new "authenticated SENDME" feature to make
174 certain denial-of-service attacks more difficult, and improves
175 performance in several areas.
177 o Major features (circuit padding):
178 - Onion service clients now add padding cells at the start of their
179 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
180 look more like general purpose Exit traffic. The overhead for this
181 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
182 extra upstream cell and 10 downstream cells for INTRODUCE
183 circuits. This feature is only enabled when also supported by the
184 circuit's middle node. (Clients may specify fixed middle nodes
185 with the MiddleNodes option, and may force-disable this feature
186 with the CircuitPadding torrc.) Closes ticket 28634.
188 o Major features (code organization):
189 - Tor now includes a generic publish-subscribe message-passing
190 subsystem that we can use to organize intermodule dependencies. We
191 hope to use this to reduce dependencies between modules that don't
192 need to be related, and to generally simplify our codebase. Closes
195 o Major features (controller protocol):
196 - Controller commands are now parsed using a generalized parsing
197 subsystem. Previously, each controller command was responsible for
198 parsing its own input, which led to strange inconsistencies.
201 o Major features (flow control):
202 - Implement authenticated SENDMEs as detailed in proposal 289. A
203 SENDME cell now includes the digest of the traffic that it
204 acknowledges, so that once an end point receives the SENDME, it
205 can confirm the other side's knowledge of the previous cells that
206 were sent, and prevent certain types of denial-of-service attacks.
207 This behavior is controlled by two new consensus parameters: see
208 the proposal for more details. Fixes ticket 26288.
210 o Major features (performance):
211 - Our node selection algorithm now excludes nodes in linear time.
212 Previously, the algorithm was quadratic, which could slow down
213 heavily used onion services. Closes ticket 30307.
215 o Major features (performance, RNG):
216 - Tor now constructs a fast secure pseudorandom number generator for
217 each thread, to use when performance is critical. This PRNG is
218 based on AES-CTR, using a buffering construction similar to
219 libottery and the (newer) OpenBSD arc4random() code. It
220 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
221 small outputs. Although we believe it to be cryptographically
222 strong, we are only using it when necessary for performance.
223 Implements tickets 29023 and 29536.
225 o Major bugfixes (onion service v3):
226 - Fix an unreachable bug in which an introduction point could try to
227 send an INTRODUCE_ACK with a status code that Trunnel would refuse
228 to encode, leading the relay to assert(). We've consolidated the
229 ABI values into Trunnel now. Fixes bug 30454; bugfix
231 - Clients can now handle unknown status codes from INTRODUCE_ACK
232 cells. (The NACK behavior will stay the same.) This will allow us
233 to extend status codes in the future without breaking the normal
234 client behavior. Fixes another part of bug 30454; bugfix
237 o Minor features (circuit padding):
238 - We now use a fast PRNG when scheduling circuit padding. Part of
240 - Allow the padding machine designer to pick the edges of their
241 histogram instead of trying to compute them automatically using an
242 exponential formula. Resolves some undefined behavior in the case
243 of small histograms and allows greater flexibility on machine
244 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
245 - Allow circuit padding machines to hold a circuit open until they
246 are done padding it. Closes ticket 28780.
248 o Minor features (compile-time modules):
249 - Add a "--list-modules" command to print a list of which compile-
250 time modules are enabled. Closes ticket 30452.
252 o Minor features (continuous integration):
253 - Remove sudo configuration lines from .travis.yml as they are no
254 longer needed with current Travis build environment. Resolves
256 - In Travis, show stem's tor log after failure. Closes ticket 30234.
258 o Minor features (controller):
259 - Add onion service version 3 support to the HSFETCH command.
260 Previously, only version 2 onion services were supported. Closes
261 ticket 25417. Patch by Neel Chauhan.
263 o Minor features (debugging):
264 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
265 logging of additional information during assert failure. Now we
266 can use format strings to include information for trouble
267 shooting. Resolves ticket 29662.
269 o Minor features (defense in depth):
270 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
271 case a bug causes them to be used later. Closes ticket 30176.
272 Patch from Tobias Stoeckmann.
273 - Tor now uses a cryptographically strong PRNG even for decisions
274 that we do not believe are security-sensitive. Previously, for
275 performance reasons, we had used a trivially predictable linear
276 congruential generator algorithm for certain load-balancing and
277 statistical sampling decisions. Now we use our fast RNG in those
278 cases. Closes ticket 29542.
280 o Minor features (developer tools):
281 - Tor's "practracker" test script now checks for files and functions
282 that seem too long and complicated. Existing overlong functions
283 and files are accepted for now, but should eventually be
284 refactored. Closes ticket 29221.
285 - Add some scripts used for git maintenance to scripts/git. Closes
287 - Call practracker from pre-push and pre-commit git hooks to let
288 developers know if they made any code style violations. Closes
290 - Add a script to check that each header has a well-formed and
291 unique guard macro. Closes ticket 29756.
293 o Minor features (geoip):
294 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
295 Country database. Closes ticket 30522.
297 o Minor features (HTTP tunnel):
298 - Return an informative web page when the HTTPTunnelPort is used as
299 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
301 o Minor features (IPv6, v3 onion services):
302 - Make v3 onion services put IPv6 addresses in service descriptors.
303 Before this change, service descriptors only contained IPv4
304 addresses. Implements 26992.
306 o Minor features (modularity):
307 - The "--disable-module-dirauth" compile-time option now disables
308 even more dirauth-only code. Closes ticket 30345.
310 o Minor features (performance):
311 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
312 1.1.1 and later), since they tend to be faster than tiny-keccak.
315 o Minor features (testing):
316 - Tor's unit test code now contains helper functions to replace the
317 PRNG with a deterministic or reproducible version for testing.
318 Previously, various tests implemented this in various ways.
319 Implements ticket 29732.
320 - We now have a script, cov-test-determinism.sh, to identify places
321 where our unit test coverage has become nondeterministic. Closes
323 - Check that representative subsets of values of `int` and `unsigned
324 int` can be represented by `void *`. Resolves issue 29537.
326 o Minor bugfixes (bridge authority):
327 - Bridge authorities now set bridges as running or non-running when
328 about to dump their status to a file. Previously, they set bridges
329 as running in response to a GETINFO command, but those shouldn't
330 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
331 Patch by Neel Chauhan.
333 o Minor bugfixes (channel padding statistics):
334 - Channel padding write totals and padding-enabled totals are now
335 counted properly in relay extrainfo descriptors. Fixes bug 29231;
336 bugfix on 0.3.1.1-alpha.
338 o Minor bugfixes (circuit padding):
339 - Add a "CircuitPadding" torrc option to disable circuit padding.
340 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
341 - Allow circuit padding machines to specify that they do not
342 contribute much overhead, and provide consensus flags and torrc
343 options to force clients to only use these low overhead machines.
344 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
345 - Provide a consensus parameter to fully disable circuit padding, to
346 be used in emergency network overload situations. Fixes bug 30173;
347 bugfix on 0.4.0.1-alpha.
348 - The circuit padding subsystem will no longer schedule padding if
349 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
350 - Inspect a circuit-level cell queue before sending padding, to
351 avoid sending padding while too much data is already queued. Fixes
352 bug 29204; bugfix on 0.4.0.1-alpha.
353 - Avoid calling monotime_absolute_usec() in circuit padding machines
354 that do not use token removal or circuit RTT estimation. Fixes bug
355 29085; bugfix on 0.4.0.1-alpha.
357 o Minor bugfixes (compilation, unusual configurations):
358 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
359 due to missing declarations of abort(), and prevent other such
360 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
362 o Minor bugfixes (controller protocol):
363 - Teach the controller parser to distinguish an object preceded by
364 an argument list from one without. Previously, it couldn't
365 distinguish an argument list from the first line of a multiline
366 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
368 o Minor bugfixes (directory authority, ipv6):
369 - Directory authorities with IPv6 support now always mark themselves
370 as reachable via IPv6. Fixes bug 24338; bugfix on 0.4.0.2-alpha.
371 Patch by Neel Chauhan.
373 o Minor bugfixes (documentation):
374 - Improve the documentation for using MapAddress with ".exit". Fixes
375 bug 30109; bugfix on 0.1.0.1-rc.
376 - Improve the monotonic time module and function documentation to
377 explain what "monotonic" actually means, and document some results
378 that have surprised people. Fixes bug 29640; bugfix
380 - Use proper formatting when providing an example on quoting options
381 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
383 o Minor bugfixes (logging):
384 - Do not log a warning when running with an OpenSSL version other
385 than the one Tor was compiled with, if the two versions should be
386 compatible. Previously, we would warn whenever the version was
387 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
388 - Warn operators when the MyFamily option is set but ContactInfo is
389 missing, as the latter should be set too. Fixes bug 25110; bugfix
392 o Minor bugfixes (memory leak):
393 - Avoid a minor memory leak that could occur on relays when failing
394 to create a "keys" directory. Fixes bug 30148; bugfix
397 o Minor bugfixes (onion services):
398 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
399 implemenation) when failing to load an onion service client
400 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
401 - When refusing to launch a controller's HSFETCH request because of
402 rate-limiting, respond to the controller with a new response,
403 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
404 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
406 - When relaunching a circuit to a rendezvous service, mark the
407 circuit as needing high-uptime routers as appropriate. Fixes bug
408 17357; bugfix on 0.4.0.2-alpha. Patch by Neel Chauhan.
409 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
410 (IPv6 support for v3 onion services is still incomplete: see
411 ticket 23493 for details.) Fixes bug 23588; bugfix on
412 0.3.2.1-alpha. Patch by Neel Chauhan.
414 o Minor bugfixes (onion services, performance):
415 - When building circuits to onion services, call tor_addr_parse()
416 less often. Previously, we called tor_addr_parse() in
417 circuit_is_acceptable() even if its output wasn't used. This
418 change should improve performance when building circuits. Fixes
419 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
421 o Minor bugfixes (performance):
422 - When checking whether a node is a bridge, use a fast check to make
423 sure that its identity is set. Previously, we used a constant-time
424 check, which is not necessary in this case. Fixes bug 30308;
425 bugfix on 0.3.5.1-alpha.
427 o Minor bugfixes (pluggable transports):
428 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
429 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
431 o Minor bugfixes (probability distributions):
432 - Refactor and improve parts of the probability distribution code
433 that made Coverity complain. Fixes bug 29805; bugfix
436 o Minor bugfixes (python):
437 - Stop assuming that /usr/bin/python3 exists. For scripts that work
438 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
439 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
441 o Minor bugfixes (relay):
442 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
443 is auto, act as if ExitRelay is 1. Previously, we would ignore
444 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
445 0.3.5.1-alpha. Patch by Neel Chauhan.
447 o Minor bugfixes (stats):
448 - When ExtraInfoStatistics is 0, stop including bandwidth usage
449 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
450 bridge statistics by country in extra-info documents. Fixes bug
451 29018; bugfix on 0.2.4.1-alpha.
453 o Minor bugfixes (testing):
454 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
455 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
456 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
457 - Fix some incorrect code in the v3 onion service unit tests. Fixes
458 bug 29243; bugfix on 0.3.2.1-alpha.
459 - In the "routerkeys/*" tests, check the return values of mkdir()
460 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
461 Found by Coverity as CID 1444254.
462 - Split test_utils_general() into several smaller test functions.
463 This makes it easier to perform resource deallocation on assert
464 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
465 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
467 o Minor bugfixes (tor-resolve):
468 - Fix a memory leak in tor-resolve that could happen if Tor gave it
469 a malformed SOCKS response. (Memory leaks in tor-resolve don't
470 actually matter, but it's good to fix them anyway.) Fixes bug
471 30151; bugfix on 0.4.0.1-alpha.
473 o Code simplification and refactoring:
474 - Abstract out the low-level formatting of replies on the control
475 port. Implements ticket 30007.
476 - Add several assertions in an attempt to fix some Coverity
477 warnings. Closes ticket 30149.
478 - Introduce a connection_dir_buf_add() helper function that checks
479 for compress_state of dir_connection_t and automatically writes a
480 string to directory connection with or without compression.
481 Resolves issue 28816.
482 - Make the base32_decode() API return the number of bytes written,
483 for consistency with base64_decode(). Closes ticket 28913.
484 - Move most relay-only periodic events out of mainloop.c into the
485 relay subsystem. Closes ticket 30414.
486 - Refactor and encapsulate parts of the codebase that manipulate
487 crypt_path_t objects. Resolves issue 30236.
488 - Refactor several places in our code that Coverity incorrectly
489 believed might have memory leaks. Closes ticket 30147.
490 - Remove redundant return values in crypto_format, and the
491 associated return value checks elsewhere in the code. Make the
492 implementations in crypto_format consistent, and remove redundant
493 code. Resolves ticket 29660.
494 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
495 it is not a constant-time function. Closes ticket 30309.
496 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
497 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
498 bugfix on 0.3.2.1-alpha.
499 - Simplify v3 onion service link specifier handling code. Fixes bug
500 23576; bugfix on 0.3.2.1-alpha.
501 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
502 code. Resolves ticket 29108.
503 - Split control.c into several submodules, in preparation for
504 distributing its current responsibilities throughout the codebase.
506 - Start to move responsibility for knowing about periodic events to
507 the appropriate subsystems, so that the mainloop doesn't need to
508 know all the periodic events in the rest of the codebase.
509 Implements tickets 30293 and 30294.
512 - Document how to find git commits and tags for bug fixes in
513 CodingStandards.md. Update some file documentation. Closes
517 - Remove the linux-tor-prio.sh script from contrib/operator-tools
518 directory. Resolves issue 29434.
519 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
520 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
523 o Code simplification and refactoring (shell scripts):
524 - Clean up many of our shell scripts to fix shellcheck warnings.
525 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
526 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
527 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
528 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
529 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
530 nagios-check-tor-authority-cert (ticket 29071),
531 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
532 (ticket 29060), test_key_expiration.sh (ticket 30002),
533 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
537 - In "make test-network-all", test IPv6-only v3 single onion
538 services, using the chutney network single-onion-v23-ipv6-md.
542 Changes in version 0.4.0.5 - 2019-05-02
543 This is the first stable release in the 0.4.0.x series. It contains
544 improvements for power management and bootstrap reporting, as well as
545 preliminary backend support for circuit padding to prevent some kinds
546 of traffic analysis. It also continues our work in refactoring Tor for
547 long-term maintainability.
549 Per our support policy, we will support the 0.4.0.x series for nine
550 months, or until three months after the release of a stable 0.4.1.x:
551 whichever is longer. If you need longer-term support, please stick
552 with 0.3.5.x, which will we plan to support until Feb 2022.
554 Below are the changes since 0.4.0.4-rc. For a complete list of changes
555 since 0.3.5.7, see the ReleaseNotes file.
557 o Minor features (continuous integration):
558 - In Travis, tell timelimit to use stem's backtrace signals, and
559 launch python directly from timelimit, so python receives the
560 signals from timelimit, rather than make. Closes ticket 30117.
562 o Minor features (diagnostic):
563 - Add more diagnostic log messages in an attempt to solve the issue
564 of NUL bytes appearing in a microdescriptor cache. Related to
567 o Minor features (testing):
568 - Use the approx_time() function when setting the "Expires" header
569 in directory replies, to make them more testable. Needed for
572 o Minor bugfixes (rust):
573 - Abort on panic in all build profiles, instead of potentially
574 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
576 o Minor bugfixes (shellcheck):
577 - Look for scripts in their correct locations during "make
578 shellcheck". Previously we had looked in the wrong place during
579 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
581 o Minor bugfixes (testing):
582 - Check the time in the "Expires" header using approx_time(). Fixes
583 bug 30001; bugfix on 0.4.0.4-rc.
585 o Minor bugfixes (UI):
586 - Lower log level of unlink() errors during bootstrap. Fixes bug
587 29930; bugfix on 0.4.0.1-alpha.
590 Changes in version 0.4.0.4-rc - 2019-04-11
591 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
592 several bugs from earlier versions, including some that had affected
593 stability, and one that prevented relays from working with NSS.
595 o Major bugfixes (NSS, relay):
596 - When running with NSS, disable TLS 1.2 ciphersuites that use
597 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
598 these ciphersuites don't work -- which caused relays to fail to
599 handshake with one another when these ciphersuites were enabled.
600 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
602 o Minor features (bandwidth authority):
603 - Make bandwidth authorities ignore relays that are reported in the
604 bandwidth file with the flag "vote=0". This change allows us to
605 report unmeasured relays for diagnostic reasons without including
606 their bandwidth in the bandwidth authorities' vote. Closes
608 - When a directory authority is using a bandwidth file to obtain the
609 bandwidth values that will be included in the next vote, serve
610 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
613 o Minor features (circuit padding):
614 - Stop warning about undefined behavior in the probability
615 distribution tests. Float division by zero may technically be
616 undefined behavior in C, but it's well defined in IEEE 754.
617 Partial backport of 29298. Closes ticket 29527; bugfix
620 o Minor features (continuous integration):
621 - On Travis Rust builds, cleanup Rust registry and refrain from
622 caching the "target/" directory to speed up builds. Resolves
625 o Minor features (dormant mode):
626 - Add a DormantCanceledByStartup option to tell Tor that it should
627 treat a startup event as cancelling any previous dormant state.
628 Integrators should use this option with caution: it should only be
629 used if Tor is being started because of something that the user
630 did, and not if Tor is being automatically started in the
631 background. Closes ticket 29357.
633 o Minor features (geoip):
634 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
635 Country database. Closes ticket 29992.
637 o Minor features (NSS, diagnostic):
638 - Try to log an error from NSS (if there is any) and a more useful
639 description of our situation if we are using NSS and a call to
640 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
642 o Minor bugfixes (security):
643 - Fix a potential double free bug when reading huge bandwidth files.
644 The issue is not exploitable in the current Tor network because
645 the vulnerable code is only reached when directory authorities
646 read bandwidth files, but bandwidth files come from a trusted
647 source (usually the authorities themselves). Furthermore, the
648 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
649 which are not used by any of the current authorities. Fixes bug
650 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
652 - Verify in more places that we are not about to create a buffer
653 with more than INT_MAX bytes, to avoid possible OOB access in the
654 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
655 fixed by Tobias Stoeckmann.
657 o Minor bugfix (continuous integration):
658 - Reset coverage state on disk after Travis CI has finished. This
659 should prevent future coverage merge errors from causing the test
660 suite for the "process" subsystem to fail. The process subsystem
661 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
663 - Terminate test-stem if it takes more than 9.5 minutes to run.
664 (Travis terminates the job after 10 minutes of no output.)
665 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
667 o Minor bugfixes (bootstrap reporting):
668 - During bootstrap reporting, correctly distinguish pluggable
669 transports from plain proxies. Fixes bug 28925; bugfix
672 o Minor bugfixes (C correctness):
673 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
674 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
677 o Minor bugfixes (circuitpadding testing):
678 - Minor tweaks to avoid rare test failures related to timers and
679 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
681 o Minor bugfixes (directory authorities):
682 - Actually include the bandwidth-file-digest line in directory
683 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
685 o Minor bugfixes (logging):
686 - On Windows, when errors cause us to reload a consensus from disk,
687 tell the user that we are retrying at log level "notice".
688 Previously we only logged this information at "info", which was
689 confusing because the errors themselves were logged at "warning".
690 Improves previous fix for 28614. Fixes bug 30004; bugfix
693 o Minor bugfixes (pluggable transports):
694 - Restore old behavior when it comes to discovering the path of a
695 given Pluggable Transport executable file. A change in
696 0.4.0.1-alpha had broken this behavior on paths containing a
697 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
699 o Minor bugfixes (testing):
700 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
701 recent test-network.sh to use new chutney features in CI. Fixes
702 bug 29703; bugfix on 0.2.9.1-alpha.
703 - Fix a test failure on Windows caused by an unexpected "BUG"
704 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
707 o Minor bugfixes (TLS protocol):
708 - When classifying a client's selection of TLS ciphers, if the
709 client ciphers are not yet available, do not cache the result.
710 Previously, we had cached the unavailability of the cipher list
711 and never looked again, which in turn led us to assume that the
712 client only supported the ancient V1 link protocol. This, in turn,
713 was causing Stem integration tests to stall in some cases. Fixes
714 bug 30021; bugfix on 0.2.4.8-alpha.
716 o Code simplification and refactoring:
717 - Introduce a connection_dir_buf_add() helper function that detects
718 whether compression is in use, and adds a string accordingly.
719 Resolves issue 28816.
720 - Refactor handle_get_next_bandwidth() to use
721 connection_dir_buf_add(). Implements ticket 29897.
724 - Clarify that Tor performs stream isolation among *Port listeners
725 by default. Resolves issue 29121.
728 Changes in version 0.4.0.3-alpha - 2019-03-22
729 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
730 bugs from earlier versions.
732 o Minor features (address selection):
733 - Treat the subnet 100.64.0.0/10 as public for some purposes;
734 private for others. This subnet is the RFC 6598 (Carrier Grade
735 NAT) IP range, and is deployed by many ISPs as an alternative to
736 RFC 1918 that does not break existing internal networks. Tor now
737 blocks SOCKS and control ports on these addresses and warns users
738 if client ports or ExtORPorts are listening on a RFC 6598 address.
739 Closes ticket 28525. Patch by Neel Chauhan.
741 o Minor features (geoip):
742 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
743 Country database. Closes ticket 29666.
745 o Minor bugfixes (circuitpadding):
746 - Inspect the circuit-level cell queue before sending padding, to
747 avoid sending padding when too much data is queued. Fixes bug
748 29204; bugfix on 0.4.0.1-alpha.
750 o Minor bugfixes (logging):
751 - Correct a misleading error message when IPv4Only or IPv6Only is
752 used but the resolved address can not be interpreted as an address
753 of the specified IP version. Fixes bug 13221; bugfix on
754 0.2.3.9-alpha. Patch from Kris Katterjohn.
755 - Log the correct port number for listening sockets when "auto" is
756 used to let Tor pick the port number. Previously, port 0 was
757 logged instead of the actual port number. Fixes bug 29144; bugfix
758 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
759 - Stop logging a BUG() warning when Tor is waiting for exit
760 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
762 o Minor bugfixes (memory management):
763 - Refactor the shared random state's memory management so that it
764 actually takes ownership of the shared random value pointers.
765 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
767 o Minor bugfixes (memory management, testing):
768 - Stop leaking parts of the shared random state in the shared-random
769 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
771 o Minor bugfixes (pluggable transports):
772 - Fix an assertion failure crash bug when a pluggable transport is
773 terminated during the bootstrap phase. Fixes bug 29562; bugfix
776 o Minor bugfixes (Rust, protover):
777 - Add a missing "Padding" value to the Rust implementation of
778 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
780 o Minor bugfixes (single onion services):
781 - Allow connections to single onion services to remain idle without
782 being disconnected. Previously, relays acting as rendezvous points
783 for single onion services were mistakenly closing idle rendezvous
784 circuits after 60 seconds, thinking that they were unused
785 directory-fetching circuits that had served their purpose. Fixes
786 bug 29665; bugfix on 0.2.1.26.
788 o Minor bugfixes (stats):
789 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
790 relay and bridge extra-info documents. Fixes bug 29017; bugfix
793 o Minor bugfixes (testing):
794 - Downgrade some LOG_ERR messages in the address/* tests to
795 warnings. The LOG_ERR messages were occurring when we had no
796 configured network. We were failing the unit tests, because we
797 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
798 29530; bugfix on 0.3.5.8.
799 - Fix our gcov wrapper script to look for object files at the
800 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
801 - Decrease the false positive rate of stochastic probability
802 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
804 o Minor bugfixes (Windows, CI):
805 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
806 Windows Server 2012 R2 job. The remaining 2 jobs still provide
807 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
808 fast_finish, so failed jobs terminate the build immediately. Fixes
809 bug 29601; bugfix on 0.3.5.4-alpha.
812 Changes in version 0.3.5.8 - 2019-02-21
813 Tor 0.3.5.8 backports several fixes from later releases, including fixes
814 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
817 It also includes a fix for a medium-severity security bug affecting Tor
818 0.3.2.1-alpha and later. All Tor instances running an affected release
819 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
821 o Major bugfixes (cell scheduler, KIST, security):
822 - Make KIST consider the outbuf length when computing what it can
823 put in the outbuf. Previously, KIST acted as though the outbuf
824 were empty, which could lead to the outbuf becoming too full. It
825 is possible that an attacker could exploit this bug to cause a Tor
826 client or relay to run out of memory and crash. Fixes bug 29168;
827 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
828 TROVE-2019-001 and CVE-2019-8955.
830 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
831 - Gracefully handle empty username/password fields in SOCKS5
832 username/password auth message and allow SOCKS5 handshake to
833 continue. Previously, we had rejected these handshakes, breaking
834 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
836 o Minor features (compilation, backport from 0.4.0.2-alpha):
837 - Compile correctly when OpenSSL is built with engine support
838 disabled, or with deprecated APIs disabled. Closes ticket 29026.
839 Patches from "Mangix".
841 o Minor features (geoip):
842 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
843 Country database. Closes ticket 29478.
845 o Minor features (testing, backport from 0.4.0.2-alpha):
846 - Treat all unexpected ERR and BUG messages as test failures. Closes
849 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
850 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
851 connection waiting for a descriptor that we actually have in the
852 cache. It turns out that this can actually happen, though it is
853 rare. Now, tor will recover and retry the descriptor. Fixes bug
854 28669; bugfix on 0.3.2.4-alpha.
856 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
857 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
858 IPv6 socket was bound using an address family of AF_INET instead
859 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
862 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
863 - Update Cargo.lock file to match the version made by the latest
864 version of Rust, so that "make distcheck" will pass again. Fixes
865 bug 29244; bugfix on 0.3.3.4-alpha.
867 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
868 - Select guards even if the consensus has expired, as long as the
869 consensus is still reasonably live. Fixes bug 24661; bugfix
872 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
873 - Compile correctly on OpenBSD; previously, we were missing some
874 headers required in order to detect it properly. Fixes bug 28938;
875 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
877 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
878 - Describe the contents of the v3 onion service client authorization
879 files correctly: They hold public keys, not private keys. Fixes
880 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
882 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
883 - Rework rep_hist_log_link_protocol_counts() to iterate through all
884 link protocol versions when logging incoming/outgoing connection
885 counts. Tor no longer skips version 5, and we won't have to
886 remember to update this function when new link protocol version is
887 developed. Fixes bug 28920; bugfix on 0.2.6.10.
889 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
890 - Log more information at "warning" level when unable to read a
891 private key; log more information at "info" level when unable to
892 read a public key. We had warnings here before, but they were lost
893 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
895 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
896 - The amount of total available physical memory is now determined
897 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
898 when it is defined and a 64-bit variant is not available. Fixes
899 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
901 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
902 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
903 than one private key for a hidden service. Fixes bug 29040; bugfix
905 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
906 "debug" level. Tor used to log it as a warning, which caused very
907 long log lines to appear for some users. Fixes bug 29135; bugfix
909 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
910 as a warning. Instead, log it as a protocol warning, because there
911 is nothing that relay operators can do to fix it. Fixes bug 29029;
912 bugfix on 0.2.5.7-rc.
914 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
915 - Mark outdated dirservers when Tor only has a reasonably live
916 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
918 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
919 - Detect and suppress "bug" warnings from the util/time test on
920 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
921 - Do not log an error-level message if we fail to find an IPv6
922 network interface from the unit tests. Fixes bug 29160; bugfix
925 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
926 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
927 Some users took this phrasing to mean that the mentioned guard was
928 under their control or responsibility, which it is not. Fixes bug
929 28895; bugfix on Tor 0.3.0.1-alpha.
932 Changes in version 0.3.4.11 - 2019-02-21
933 Tor 0.3.4.11 is the third stable release in its series. It includes
934 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
935 later. All Tor instances running an affected release should upgrade to
936 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
938 o Major bugfixes (cell scheduler, KIST, security):
939 - Make KIST consider the outbuf length when computing what it can
940 put in the outbuf. Previously, KIST acted as though the outbuf
941 were empty, which could lead to the outbuf becoming too full. It
942 is possible that an attacker could exploit this bug to cause a Tor
943 client or relay to run out of memory and crash. Fixes bug 29168;
944 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
945 TROVE-2019-001 and CVE-2019-8955.
947 o Minor features (geoip):
948 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
949 Country database. Closes ticket 29478.
951 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
952 - Update Cargo.lock file to match the version made by the latest
953 version of Rust, so that "make distcheck" will pass again. Fixes
954 bug 29244; bugfix on 0.3.3.4-alpha.
956 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
957 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
958 as a warning. Instead, log it as a protocol warning, because there
959 is nothing that relay operators can do to fix it. Fixes bug 29029;
960 bugfix on 0.2.5.7-rc.
963 Changes in version 0.3.3.12 - 2019-02-21
964 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
965 0.3.2.1-alpha and later. All Tor instances running an affected release
966 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
968 This release marks the end of support for the Tor 0.3.3.x series. We
969 recommend that users switch to either the Tor 0.3.4 series (supported
970 until at least 10 June 2019), or the Tor 0.3.5 series, which will
971 receive long-term support until at least 1 Feb 2022.
973 o Major bugfixes (cell scheduler, KIST, security):
974 - Make KIST consider the outbuf length when computing what it can
975 put in the outbuf. Previously, KIST acted as though the outbuf
976 were empty, which could lead to the outbuf becoming too full. It
977 is possible that an attacker could exploit this bug to cause a Tor
978 client or relay to run out of memory and crash. Fixes bug 29168;
979 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
980 TROVE-2019-001 and CVE-2019-8955.
982 o Minor features (geoip):
983 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
984 Country database. Closes ticket 29478.
986 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
987 - Update Cargo.lock file to match the version made by the latest
988 version of Rust, so that "make distcheck" will pass again. Fixes
989 bug 29244; bugfix on 0.3.3.4-alpha.
991 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
992 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
993 as a warning. Instead, log it as a protocol warning, because there
994 is nothing that relay operators can do to fix it. Fixes bug 29029;
995 bugfix on 0.2.5.7-rc.
998 Changes in version 0.4.0.2-alpha - 2019-02-21
999 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
1000 bugs from earlier versions, including several that had broken
1001 backward compatibility.
1003 It also includes a fix for a medium-severity security bug affecting Tor
1004 0.3.2.1-alpha and later. All Tor instances running an affected release
1005 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1007 o Major bugfixes (cell scheduler, KIST, security):
1008 - Make KIST consider the outbuf length when computing what it can
1009 put in the outbuf. Previously, KIST acted as though the outbuf
1010 were empty, which could lead to the outbuf becoming too full. It
1011 is possible that an attacker could exploit this bug to cause a Tor
1012 client or relay to run out of memory and crash. Fixes bug 29168;
1013 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1014 TROVE-2019-001 and CVE-2019-8955.
1016 o Major bugfixes (networking):
1017 - Gracefully handle empty username/password fields in SOCKS5
1018 username/password auth messsage and allow SOCKS5 handshake to
1019 continue. Previously, we had rejected these handshakes, breaking
1020 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
1022 o Major bugfixes (windows, startup):
1023 - When reading a consensus file from disk, detect whether it was
1024 written in text mode, and re-read it in text mode if so. Always
1025 write consensus files in binary mode so that we can map them into
1026 memory later. Previously, we had written in text mode, which
1027 confused us when we tried to map the file on windows. Fixes bug
1028 28614; bugfix on 0.4.0.1-alpha.
1030 o Minor features (compilation):
1031 - Compile correctly when OpenSSL is built with engine support
1032 disabled, or with deprecated APIs disabled. Closes ticket 29026.
1033 Patches from "Mangix".
1035 o Minor features (developer tooling):
1036 - Check that bugfix versions in changes files look like Tor versions
1037 from the versions spec. Warn when bugfixes claim to be on a future
1038 release. Closes ticket 27761.
1039 - Provide a git pre-commit hook that disallows committing if we have
1040 any failures in our code and changelog formatting checks. It is
1041 now available in scripts/maint/pre-commit.git-hook. Implements
1044 o Minor features (directory authority):
1045 - When a directory authority is using a bandwidth file to obtain
1046 bandwidth values, include the digest of that file in the vote.
1047 Closes ticket 26698.
1049 o Minor features (geoip):
1050 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1051 Country database. Closes ticket 29478.
1053 o Minor features (testing):
1054 - Treat all unexpected ERR and BUG messages as test failures. Closes
1057 o Minor bugfixes (build, compatibility, rust):
1058 - Update Cargo.lock file to match the version made by the latest
1059 version of Rust, so that "make distcheck" will pass again. Fixes
1060 bug 29244; bugfix on 0.3.3.4-alpha.
1062 o Minor bugfixes (compilation):
1063 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
1064 29169; bugfix on 0.4.0.1-alpha.
1065 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
1066 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
1068 o Minor bugfixes (documentation):
1069 - Describe the contents of the v3 onion service client authorization
1070 files correctly: They hold public keys, not private keys. Fixes
1071 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
1073 o Minor bugfixes (linux seccomp sandbox):
1074 - Fix startup crash when experimental sandbox support is enabled.
1075 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
1077 o Minor bugfixes (logging):
1078 - Avoid logging that we are relaxing a circuit timeout when that
1079 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
1080 - Log more information at "warning" level when unable to read a
1081 private key; log more information at "info" level when unable to
1082 read a public key. We had warnings here before, but they were lost
1083 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
1085 o Minor bugfixes (misc):
1086 - The amount of total available physical memory is now determined
1087 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
1088 when it is defined and a 64-bit variant is not available. Fixes
1089 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
1091 o Minor bugfixes (onion services):
1092 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
1093 than one private key for a hidden service. Fixes bug 29040; bugfix
1095 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
1096 "debug" level. Tor used to log it as a warning, which caused very
1097 long log lines to appear for some users. Fixes bug 29135; bugfix
1099 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1100 as a warning. Instead, log it as a protocol warning, because there
1101 is nothing that relay operators can do to fix it. Fixes bug 29029;
1102 bugfix on 0.2.5.7-rc.
1104 o Minor bugfixes (scheduler):
1105 - When re-adding channels to the pending list, check the correct
1106 channel's sched_heap_idx. This issue has had no effect in mainline
1107 Tor, but could have led to bugs down the road in improved versions
1108 of our circuit scheduling code. Fixes bug 29508; bugfix
1111 o Minor bugfixes (tests):
1112 - Fix intermittent failures on an adaptive padding test. Fixes one
1113 case of bug 29122; bugfix on 0.4.0.1-alpha.
1114 - Disable an unstable circuit-padding test that was failing
1115 intermittently because of an ill-defined small histogram. Such
1116 histograms will be allowed again after 29298 is implemented. Fixes
1117 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
1118 - Detect and suppress "bug" warnings from the util/time test on
1119 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
1120 - Do not log an error-level message if we fail to find an IPv6
1121 network interface from the unit tests. Fixes bug 29160; bugfix
1125 - In the manpage entry describing MapAddress torrc setting, use
1126 example IP addresses from ranges specified for use in documentation
1127 by RFC 5737. Resolves issue 28623.
1130 - Remove the old check-tor script. Resolves issue 29072.
1133 Changes in version 0.4.0.1-alpha - 2019-01-18
1134 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
1135 introduces improved features for power and bandwidth conservation,
1136 more accurate reporting of bootstrap progress for user interfaces, and
1137 an experimental backend for an exciting new adaptive padding feature.
1138 There is also the usual assortment of bugfixes and minor features, all
1141 o Major features (battery management, client, dormant mode):
1142 - When Tor is running as a client, and it is unused for a long time,
1143 it can now enter a "dormant" state. When Tor is dormant, it avoids
1144 network and CPU activity until it is reawoken either by a user
1145 request or by a controller command. For more information, see the
1146 configuration options starting with "Dormant". Implements tickets
1148 - The client's memory of whether it is "dormant", and how long it
1149 has spent idle, persists across invocations. Implements
1151 - There is a DormantOnFirstStartup option that integrators can use
1152 if they expect that in many cases, Tor will be installed but
1155 o Major features (bootstrap reporting):
1156 - When reporting bootstrap progress, report the first connection
1157 uniformly, regardless of whether it's a connection for building
1158 application circuits. This allows finer-grained reporting of early
1159 progress than previously possible, with the improvements of ticket
1160 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
1161 - When reporting bootstrap progress, treat connecting to a proxy or
1162 pluggable transport as separate from having successfully used that
1163 proxy or pluggable transport to connect to a relay. Closes tickets
1166 o Major features (circuit padding):
1167 - Implement preliminary support for the circuit padding portion of
1168 Proposal 254. The implementation supports Adaptive Padding (aka
1169 WTF-PAD) state machines for use between experimental clients and
1170 relays. Support is also provided for APE-style state machines that
1171 use probability distributions instead of histograms to specify
1172 inter-packet delay. At the moment, Tor does not provide any
1173 padding state machines that are used in normal operation: for now,
1174 this feature exists solely for experimentation. Closes
1177 o Major features (refactoring):
1178 - Tor now uses an explicit list of its own subsystems when
1179 initializing and shutting down. Previously, these systems were
1180 managed implicitly in various places throughout the codebase.
1181 (There may still be some subsystems using the old system.) Closes
1184 o Minor features (bootstrap reporting):
1185 - When reporting bootstrap progress, stop distinguishing between
1186 situations where only internal paths are available and situations
1187 where external paths are available. Previously, Tor would often
1188 erroneously report that it had only internal paths. Closes
1191 o Minor features (continuous integration):
1192 - Log Python version during each Travis CI job. Resolves
1195 o Minor features (controller):
1196 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
1197 Implements ticket 28843.
1199 o Minor features (developer tooling):
1200 - Provide a git hook script to prevent "fixup!" and "squash!"
1201 commits from ending up in the master branch, as scripts/main/pre-
1202 push.git-hook. Closes ticket 27993.
1204 o Minor features (directory authority):
1205 - Directory authorities support a new consensus algorithm, under
1206 which the family lines in microdescriptors are encoded in a
1207 canonical form. This change makes family lines more compressible
1208 in transit, and on the client. Closes ticket 28266; implements
1211 o Minor features (directory authority, relay):
1212 - Authorities now vote on a "StaleDesc" flag to indicate that a
1213 relay's descriptor is so old that the relay should upload again
1214 soon. Relays treat this flag as a signal to upload a new
1215 descriptor. This flag will eventually let us remove the
1216 'published' date from routerstatus entries, and make our consensus
1217 diffs much smaller. Closes ticket 26770; implements proposal 293.
1219 o Minor features (fallback directory mirrors):
1220 - Update the fallback whitelist based on operator opt-ins and opt-
1221 outs. Closes ticket 24805, patch by Phoul.
1223 o Minor features (FreeBSD):
1224 - On FreeBSD-based systems, warn relay operators if the
1225 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
1226 Closes ticket 28518.
1228 o Minor features (HTTP standards compliance):
1229 - Stop sending the header "Content-type: application/octet-stream"
1230 along with transparently compressed documents: this confused
1231 browsers. Closes ticket 28100.
1233 o Minor features (IPv6):
1234 - We add an option ClientAutoIPv6ORPort, to make clients randomly
1235 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
1236 every time a node is loaded from a new consensus or bridge config.
1237 We expect that this option will enable clients to bootstrap more
1238 quickly without having to determine whether they support IPv4,
1239 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
1240 - When using addrs_in_same_network_family(), avoid choosing circuit
1241 paths that pass through the same IPv6 subnet more than once.
1242 Previously, we only checked IPv4 subnets. Closes ticket 24393.
1243 Patch by Neel Chauhan.
1245 o Minor features (log messages):
1246 - Improve log message in v3 onion services that could print out
1247 negative revision counters. Closes ticket 27707. Patch
1250 o Minor features (memory usage):
1251 - Save memory by storing microdescriptor family lists with a more
1252 compact representation. Closes ticket 27359.
1253 - Tor clients now use mmap() to read consensus files from disk, so
1254 that they no longer need keep the full text of a consensus in
1255 memory when parsing it or applying a diff. Closes ticket 27244.
1257 o Minor features (parsing):
1258 - Directory authorities now validate that router descriptors and
1259 ExtraInfo documents are in a valid subset of UTF-8, and reject
1260 them if they are not. Closes ticket 27367.
1262 o Minor features (performance):
1263 - Cache the results of summarize_protocol_flags(), so that we don't
1264 have to parse the same protocol-versions string over and over.
1265 This should save us a huge number of malloc calls on startup, and
1266 may reduce memory fragmentation with some allocators. Closes
1268 - Remove a needless memset() call from get_token_arguments, thereby
1269 speeding up the tokenization of directory objects by about 20%.
1270 Closes ticket 28852.
1271 - Replace parse_short_policy() with a faster implementation, to
1272 improve microdescriptor parsing time. Closes ticket 28853.
1273 - Speed up directory parsing a little by avoiding use of the non-
1274 inlined strcmp_len() function. Closes ticket 28856.
1275 - Speed up microdescriptor parsing by about 30%, to help improve
1276 startup time. Closes ticket 28839.
1278 o Minor features (pluggable transports):
1279 - Add support for emitting STATUS updates to Tor's control port from
1280 a pluggable transport process. Closes ticket 28846.
1281 - Add support for logging to Tor's logging subsystem from a
1282 pluggable transport process. Closes ticket 28180.
1284 o Minor features (process management):
1285 - Add a new process API for handling child processes. This new API
1286 allows Tor to have bi-directional communication with child
1287 processes on both Unix and Windows. Closes ticket 28179.
1288 - Use the subsystem manager to initialize and shut down the process
1289 module. Closes ticket 28847.
1291 o Minor features (relay):
1292 - When listing relay families, list them in canonical form including
1293 the relay's own identity, and try to give a more useful set of
1294 warnings. Part of ticket 28266 and proposal 298.
1296 o Minor features (required protocols):
1297 - Before exiting because of a missing required protocol, Tor will
1298 now check the publication time of the consensus, and not exit
1299 unless the consensus is newer than the Tor program's own release
1300 date. Previously, Tor would not check the consensus publication
1301 time, and so might exit because of a missing protocol that might
1302 no longer be required in a current consensus. Implements proposal
1303 297; closes ticket 27735.
1305 o Minor features (testing):
1306 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
1307 networks. Closes ticket 28840. Patch by Rob Jansen.
1309 o Minor bugfixes (client, clock skew):
1310 - Bootstrap successfully even when Tor's clock is behind the clocks
1311 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
1312 - Select guards even if the consensus has expired, as long as the
1313 consensus is still reasonably live. Fixes bug 24661; bugfix
1316 o Minor bugfixes (compilation):
1317 - Compile correctly on OpenBSD; previously, we were missing some
1318 headers required in order to detect it properly. Fixes bug 28938;
1319 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1321 o Minor bugfixes (directory clients):
1322 - Mark outdated dirservers when Tor only has a reasonably live
1323 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
1325 o Minor bugfixes (directory mirrors):
1326 - Even when a directory mirror's clock is behind the clocks on the
1327 authorities, we now allow the mirror to serve "future"
1328 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
1330 o Minor bugfixes (DNS):
1331 - Gracefully handle an empty or absent resolve.conf file by falling
1332 back to using "localhost" as a DNS server (and hoping it works).
1333 Previously, we would just stop running as an exit. Fixes bug
1334 21900; bugfix on 0.2.1.10-alpha.
1336 o Minor bugfixes (guards):
1337 - In count_acceptable_nodes(), the minimum number is now one bridge
1338 or guard node, and two non-guard nodes for a circuit. Previously,
1339 we had added up the sum of all nodes with a descriptor, but that
1340 could cause us to build failing circuits when we had either too
1341 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
1342 0.3.6.1-alpha. Patch by Neel Chauhan.
1344 o Minor bugfixes (IPv6):
1345 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
1346 IPv6 socket was bound using an address family of AF_INET instead
1347 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
1350 o Minor bugfixes (logging):
1351 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1352 link protocol versions when logging incoming/outgoing connection
1353 counts. Tor no longer skips version 5, and we won't have to
1354 remember to update this function when new link protocol version is
1355 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1357 o Minor bugfixes (networking):
1358 - Introduce additional checks into tor_addr_parse() to reject
1359 certain incorrect inputs that previously were not detected. Fixes
1360 bug 23082; bugfix on 0.2.0.10-alpha.
1362 o Minor bugfixes (onion service v3, client):
1363 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
1364 connection waiting for a descriptor that we actually have in the
1365 cache. It turns out that this can actually happen, though it is
1366 rare. Now, tor will recover and retry the descriptor. Fixes bug
1367 28669; bugfix on 0.3.2.4-alpha.
1369 o Minor bugfixes (periodic events):
1370 - Refrain from calling routerlist_remove_old_routers() from
1371 check_descriptor_callback(). Instead, create a new hourly periodic
1372 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
1374 o Minor bugfixes (pluggable transports):
1375 - Make sure that data is continously read from standard output and
1376 standard error pipes of a pluggable transport child-process, to
1377 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
1378 bugfix on 0.2.3.6-alpha.
1380 o Minor bugfixes (unit tests):
1381 - Instead of relying on hs_free_all() to clean up all onion service
1382 objects in test_build_descriptors(), we now deallocate them one by
1383 one. This lets Coverity know that we are not leaking memory there
1384 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
1386 o Minor bugfixes (usability):
1387 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1388 Some users took this phrasing to mean that the mentioned guard was
1389 under their control or responsibility, which it is not. Fixes bug
1390 28895; bugfix on Tor 0.3.0.1-alpha.
1392 o Code simplification and refactoring:
1393 - Reimplement NETINFO cell parsing and generation to rely on
1394 trunnel-generated wire format handling code. Closes ticket 27325.
1395 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
1397 - Rework SOCKS wire format handling to rely on trunnel-generated
1398 parsing/generation code. Resolves ticket 27620.
1399 - Split out bootstrap progress reporting from control.c into a
1400 separate file. Part of ticket 27402.
1401 - The .may_include files that we use to describe our directory-by-
1402 directory dependency structure now describe a noncircular
1403 dependency graph over the directories that they cover. Our
1404 checkIncludes.py tool now enforces this noncircularity. Closes
1408 - Mention that you cannot add a new onion service if Tor is already
1409 running with Sandbox enabled. Closes ticket 28560.
1410 - Improve ControlPort documentation. Mention that it accepts
1411 address:port pairs, and can be used multiple times. Closes
1413 - Document the exact output of "tor --version". Closes ticket 28889.
1416 - Stop responding to the 'GETINFO status/version/num-concurring' and
1417 'GETINFO status/version/num-versioning' control port commands, as
1418 those were deprecated back in 0.2.0.30. Also stop listing them in
1419 output of 'GETINFO info/names'. Resolves ticket 28757.
1420 - The scripts used to generate and maintain the list of fallback
1421 directories have been extracted into a new "fallback-scripts"
1422 repository. Closes ticket 27914.
1425 - Run shellcheck for scripts in the in scripts/ directory. Closes
1427 - Add unit tests for tokenize_string() and get_next_token()
1428 functions. Resolves ticket 27625.
1430 o Code simplification and refactoring (onion service v3):
1431 - Consolidate the authorized client descriptor cookie computation
1432 code from client and service into one function. Closes
1435 o Code simplification and refactoring (shell scripts):
1436 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
1438 - Fix issues that shellcheck found in chutney-git-bisect.sh.
1439 Resolves ticket 28006.
1440 - Fix issues that shellcheck found in updateRustDependencies.sh.
1441 Resolves ticket 28012.
1442 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
1443 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
1444 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
1445 - Fix shellcheck warnings in scripts/test/coverage. Resolves
1449 Changes in version 0.3.3.11 - 2019-01-07
1450 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
1451 numerous fixes, including an important fix for anyone using OpenSSL
1452 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
1453 to this version, or to a later series.
1455 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
1456 We anticipate that this will be the last release of Tor 0.3.3, unless
1457 some major bug is before then. Some time between now and then, users
1458 should switch to either the Tor 0.3.4 series (supported until at least
1459 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
1460 support until at least 1 Feb 2022.
1462 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1463 - Fix our usage of named groups when running as a TLS 1.3 client in
1464 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1465 running as a relay, which caused clients to fail to negotiate TLS
1466 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1469 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1470 - Fix a use-after-free error that could be caused by passing Tor an
1471 impossible set of options that would fail during options_act().
1472 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1474 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1475 - Only run one online rust build in Travis, to reduce network
1476 errors. Skip offline rust builds on Travis for Linux gcc, because
1477 they're redundant. Implements ticket 27252.
1478 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1479 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1480 Linux with default settings, because all the non-default builds
1481 use gcc on Linux. Implements ticket 27252.
1483 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1484 - Use the Travis Homebrew addon to install packages on macOS during
1485 Travis CI. The package list is the same, but the Homebrew addon
1486 does not do a `brew update` by default. Implements ticket 27738.
1488 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1489 - Replace the 150 fallbacks originally introduced in Tor
1490 0.3.3.1-alpha in January 2018 (of which ~115 were still
1491 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1492 removed) generated in December 2018. Closes ticket 24803.
1494 o Minor features (geoip):
1495 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1496 Country database. Closes ticket 29012.
1498 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1499 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1500 key export function from handling long labels. When this bug is
1501 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1502 version of OpenSSL without this bug when it becomes available.
1503 Closes ticket 28973.
1505 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1506 - Update relay descriptor on bandwidth changes only when the uptime
1507 is smaller than 24h, in order to reduce the efficiency of guard
1508 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1510 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
1511 - Avoid undefined behavior in an end-of-string check when parsing
1512 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1515 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1516 - Rewrite our assertion macros so that they no longer suppress the
1517 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1519 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1520 - Initialize a variable unconditionally in aes_new_cipher(), since
1521 some compilers cannot tell that we always initialize it before
1522 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1524 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
1525 - Log additional info when we get a relay that shares an ed25519 ID
1526 with a different relay, instead making a BUG() warning. Fixes bug
1527 27800; bugfix on 0.3.2.1-alpha.
1529 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1530 - When a user requests a group-readable DataDirectory, give it to
1531 them. Previously, when the DataDirectory and the CacheDirectory
1532 were the same, the default setting (0) for
1533 CacheDirectoryGroupReadable would override the setting for
1534 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1537 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1538 - When the onion service directory can't be created or has the wrong
1539 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1542 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1543 - Close all SOCKS request (for the same .onion) if the newly fetched
1544 descriptor is unusable. Before that, we would close only the first
1545 one leaving the other hanging and let to time out by themselves.
1546 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1548 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1549 - Don't warn so loudly when Tor is unable to decode an onion
1550 descriptor. This can now happen as a normal use case if a client
1551 gets a descriptor with client authorization but the client is not
1552 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1554 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1555 - When deleting an ephemeral onion service (DEL_ONION), do not close
1556 any rendezvous circuits in order to let the existing client
1557 connections finish by themselves or closed by the application. The
1558 HS v2 is doing that already so now we have the same behavior for
1559 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1561 o Minor bugfixes (HTTP tunnel):
1562 - Fix a bug warning when closing an HTTP tunnel connection due to
1563 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
1566 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1567 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1568 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1570 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1571 - Ensure circuitmux queues are empty before scheduling or sending
1572 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1574 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1575 - Reject protocol names containing bytes other than alphanumeric
1576 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1579 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1580 - Compute protover votes correctly in the rust version of the
1581 protover code. Previously, the protover rewrite in 24031 allowed
1582 repeated votes from the same voter for the same protocol version
1583 to be counted multiple times in protover_compute_vote(). Fixes bug
1584 27649; bugfix on 0.3.3.5-rc.
1585 - Reject protover names that contain invalid characters. Fixes bug
1586 27687; bugfix on 0.3.3.1-alpha.
1588 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1589 - protover_all_supported() would attempt to allocate up to 16GB on
1590 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1591 bugfix on 0.3.3.5-rc.
1593 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
1594 - Fix a potential null dereference in protover_all_supported(). Add
1595 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1596 - Return a string that can be safely freed by C code, not one
1597 created by the rust allocator, in protover_all_supported(). Fixes
1598 bug 27740; bugfix on 0.3.3.1-alpha.
1599 - Fix an API mismatch in the rust implementation of
1600 protover_compute_vote(). This bug could have caused crashes on any
1601 directory authorities running Tor with Rust (which we do not yet
1602 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1604 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1605 - If a unit test running in a subprocess exits abnormally or with a
1606 nonzero status code, treat the test as having failed, even if the
1607 test reported success. Without this fix, memory leaks don't cause
1608 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1609 bugfix on 0.2.2.4-alpha.
1611 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
1612 - Treat backtrace test failures as expected on BSD-derived systems
1613 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1614 (FreeBSD failures have been treated as expected since 18204 in
1615 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1617 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1618 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1619 bugfix on 0.3.0.1-alpha.
1622 Changes in version 0.3.4.10 - 2019-01-07
1623 Tor 0.3.4.9 is the second stable release in its series; it backports
1624 numerous fixes, including an important fix for relays, and for anyone
1625 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
1628 As a reminder, the Tor 0.3.4 series will be supported until 10 June
1629 2019. Some time between now and then, users should switch to the Tor
1630 0.3.5 series, which will receive long-term support until at least 1
1633 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1634 - Fix our usage of named groups when running as a TLS 1.3 client in
1635 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1636 running as a relay, which caused clients to fail to negotiate TLS
1637 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1640 o Major bugfixes (relay, directory, backport from 0.3.5.7):
1641 - Always reactivate linked connections in the main loop so long as
1642 any linked connection has been active. Previously, connections
1643 serving directory information wouldn't get reactivated after the
1644 first chunk of data was sent (usually 32KB), which would prevent
1645 clients from bootstrapping. Fixes bug 28912; bugfix on
1646 0.3.4.1-alpha. Patch by "cypherpunks3".
1648 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
1649 - Always show the configure and test logs, and upload them as build
1650 artifacts, when building for Windows using Appveyor CI.
1653 o Minor features (controller, backport from 0.3.5.1-alpha):
1654 - For purposes of CIRC_BW-based dropped cell detection, track half-
1655 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1656 bias check cells to arrive without counting it as dropped until
1657 either the END arrives, or the windows are empty. Closes
1660 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1661 - Replace the 150 fallbacks originally introduced in Tor
1662 0.3.3.1-alpha in January 2018 (of which ~115 were still
1663 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1664 removed) generated in December 2018. Closes ticket 24803.
1666 o Minor features (geoip):
1667 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1668 Country database. Closes ticket 28395.
1670 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1671 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1672 key export function from handling long labels. When this bug is
1673 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1674 version of OpenSSL without this bug when it becomes available.
1675 Closes ticket 28973.
1677 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1678 - Initialize a variable unconditionally in aes_new_cipher(), since
1679 some compilers cannot tell that we always initialize it before
1680 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1682 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
1683 - Avoid a logging a BUG() stacktrace when closing connection held
1684 open because the write side is rate limited but not the read side.
1685 Now, the connection read side is simply shut down until Tor is
1686 able to flush the connection and close it. Fixes bug 27750; bugfix
1689 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
1690 - Manually configure the zstd compiler options, when building using
1691 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1692 not come with a pkg-config file. Fixes bug 28454; bugfix
1694 - Stop using an external OpenSSL install, and stop installing MSYS2
1695 packages, when building using mingw on Appveyor Windows CI. Fixes
1696 bug 28399; bugfix on 0.3.4.1-alpha.
1698 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
1699 - Explicitly specify the path to the OpenSSL library and do not
1700 download OpenSSL from Pacman, but instead use the library that is
1701 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1703 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1704 - When a user requests a group-readable DataDirectory, give it to
1705 them. Previously, when the DataDirectory and the CacheDirectory
1706 were the same, the default setting (0) for
1707 CacheDirectoryGroupReadable would override the setting for
1708 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1711 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1712 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1713 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1715 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1716 - Don't warn so loudly when Tor is unable to decode an onion
1717 descriptor. This can now happen as a normal use case if a client
1718 gets a descriptor with client authorization but the client is not
1719 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1721 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1722 - When deleting an ephemeral onion service (DEL_ONION), do not close
1723 any rendezvous circuits in order to let the existing client
1724 connections finish by themselves or closed by the application. The
1725 HS v2 is doing that already so now we have the same behavior for
1726 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1728 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1729 - Update relay descriptor on bandwidth changes only when the uptime
1730 is smaller than 24h, in order to reduce the efficiency of guard
1731 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1733 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1734 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1735 bugfix on 0.3.0.1-alpha.
1738 Changes in version 0.3.5.7 - 2019-01-07
1739 Tor 0.3.5.7 is the first stable release in its series; it includes
1740 compilation and portability fixes, and a fix for a severe problem
1741 affecting directory caches.
1743 The Tor 0.3.5 series includes several new features and performance
1744 improvements, including client authorization for v3 onion services,
1745 cleanups to bootstrap reporting, support for improved bandwidth-
1746 measurement tools, experimental support for NSS in place of OpenSSL,
1747 and much more. It also begins a full reorganization of Tor's code
1748 layout, for improved modularity and maintainability in the future.
1749 Finally, there is the usual set of performance improvements and
1750 bugfixes that we try to do in every release series.
1752 There are a couple of changes in the 0.3.5 that may affect
1753 compatibility. First, the default version for newly created onion
1754 services is now v3. Use the HiddenServiceVersion option if you want to
1755 override this. Second, some log messages related to bootstrapping have
1756 changed; if you use stem, you may need to update to the latest version
1757 so it will recognize them.
1759 We have designated 0.3.5 as a "long-term support" (LTS) series: we
1760 will continue to patch major bugs in typical configurations of 0.3.5
1761 until at least 1 Feb 2022. (We do not plan to provide long-term
1762 support for embedding, Rust support, NSS support, running a directory
1763 authority, or unsupported platforms. For these, you will need to stick
1764 with the latest stable release.)
1766 Below are the changes since 0.3.5.6-rc. For a complete list of changes
1767 since 0.3.4.9, see the ReleaseNotes file.
1769 o Major bugfixes (relay, directory):
1770 - Always reactivate linked connections in the main loop so long as
1771 any linked connection has been active. Previously, connections
1772 serving directory information wouldn't get reactivated after the
1773 first chunk of data was sent (usually 32KB), which would prevent
1774 clients from bootstrapping. Fixes bug 28912; bugfix on
1775 0.3.4.1-alpha. Patch by "cypherpunks3".
1777 o Minor features (compilation):
1778 - When possible, place our warning flags in a separate file, to
1779 avoid flooding verbose build logs. Closes ticket 28924.
1781 o Minor features (geoip):
1782 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1783 Country database. Closes ticket 29012.
1785 o Minor features (OpenSSL bug workaround):
1786 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1787 key export function from handling long labels. When this bug is
1788 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1789 version of OpenSSL without this bug when it becomes available.
1790 Closes ticket 28973.
1792 o Minor features (performance):
1793 - Remove about 96% of the work from the function that we run at
1794 startup to test our curve25519_basepoint implementation. Since
1795 this function has yet to find an actual failure, we now only run
1796 it for 8 iterations instead of 200. Based on our profile
1797 information, this change should save around 8% of our startup time
1798 on typical desktops, and may have a similar effect on other
1799 platforms. Closes ticket 28838.
1800 - Stop re-validating our hardcoded Diffie-Hellman parameters on
1801 every startup. Doing this wasted time and cycles, especially on
1802 low-powered devices. Closes ticket 28851.
1804 o Minor bugfixes (compilation):
1805 - Fix compilation for Android by adding a missing header to
1806 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
1808 o Minor bugfixes (correctness):
1809 - Fix an unreached code path where we checked the value of
1810 "hostname" inside send_resolved_hostname_cell(). Previously, we
1811 used it before checking it; now we check it first. Fixes bug
1812 28879; bugfix on 0.1.2.7-alpha.
1814 o Minor bugfixes (testing):
1815 - Make sure that test_rebind.py actually obeys its timeout, even
1816 when it receives a large number of log messages. Fixes bug 28883;
1817 bugfix on 0.3.5.4-alpha.
1818 - Stop running stem's unit tests as part of "make test-stem", but
1819 continue to run stem's unit and online tests during "make test-
1820 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
1822 o Minor bugfixes (windows services):
1823 - Make Tor start correctly as an NT service again: previously it was
1824 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
1826 o Code simplification and refactoring:
1827 - When parsing a port configuration, make it more obvious to static
1828 analyzer tools that we always initialize the address. Closes
1832 Changes in version 0.3.5.6-rc - 2018-12-18
1833 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
1834 It is the first release candidate in the 0.3.5.x series; if no further
1835 huge bugs are found, our next release may be the stable 0.3.5.x.
1837 o Minor features (continuous integration, Windows):
1838 - Always show the configure and test logs, and upload them as build
1839 artifacts, when building for Windows using Appveyor CI.
1842 o Minor features (fallback directory list):
1843 - Replace the 150 fallbacks originally introduced in Tor
1844 0.3.3.1-alpha in January 2018 (of which ~115 were still
1845 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1846 removed) generated in December 2018. Closes ticket 24803.
1848 o Minor features (geoip):
1849 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
1850 Country database. Closes ticket 28744.
1852 o Minor bugfixes (compilation):
1853 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
1854 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
1856 o Minor bugfixes (continuous integration, Windows):
1857 - Explicitly specify the path to the OpenSSL library and do not
1858 download OpenSSL from Pacman, but instead use the library that is
1859 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1861 o Minor bugfixes (onion service v3):
1862 - When deleting an ephemeral onion service (DEL_ONION), do not close
1863 any rendezvous circuits in order to let the existing client
1864 connections finish by themselves or closed by the application. The
1865 HS v2 is doing that already so now we have the same behavior for
1866 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1868 o Minor bugfixes (restart-in-process, boostrap):
1869 - Add missing resets of bootstrap tracking state when shutting down
1870 (regression caused by ticket 27169). Fixes bug 28524; bugfix
1873 o Minor bugfixes (testing):
1874 - Use a separate DataDirectory for the test_rebind script.
1875 Previously, this script would run using the default DataDirectory,
1876 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
1877 Patch from Taylor R Campbell.
1878 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1879 bugfix on 0.3.0.1-alpha.
1881 o Minor bugfixes (Windows):
1882 - Correctly identify Windows 8.1, Windows 10, and Windows Server
1883 2008 and later from their NT versions. Fixes bug 28096; bugfix on
1884 0.2.2.34; reported by Keifer Bly.
1885 - On recent Windows versions, the GetVersionEx() function may report
1886 an earlier Windows version than the running OS. To avoid user
1887 confusion, add "[or later]" to Tor's version string on affected
1888 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
1890 - Remove Windows versions that were never supported by the
1891 GetVersionEx() function. Stop duplicating the latest Windows
1892 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
1893 reported by Keifer Bly.
1896 - Increase logging and tag all log entries with timestamps in
1897 test_rebind.py. Provides diagnostics for issue 28229.
1899 o Code simplification and refactoring (shared random, dirauth):
1900 - Change many tor_assert() to use BUG() instead. The idea is to not
1901 crash a dirauth but rather scream loudly with a stacktrace and let
1902 it continue run. The shared random subsystem is very resilient and
1903 if anything wrong happens with it, at worst a non coherent value
1904 will be put in the vote and discarded by the other authorities.
1905 Closes ticket 19566.
1907 o Documentation (onion services):
1908 - Document in the man page that changing ClientOnionAuthDir value or
1909 adding a new file in the directory will not work at runtime upon
1910 sending a HUP if Sandbox 1. Closes ticket 28128.
1911 - Note in the man page that the only real way to fully revoke an
1912 onion service v3 client authorization is by restarting the tor
1913 process. Closes ticket 28275.
1916 Changes in version 0.3.5.5-alpha - 2018-11-16
1917 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
1918 including several that we hope to backport to older release series in
1921 o Major bugfixes (OpenSSL, portability):
1922 - Fix our usage of named groups when running as a TLS 1.3 client in
1923 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1924 running as a relay, which caused clients to fail to negotiate TLS
1925 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1928 o Minor features (geoip):
1929 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1930 Country database. Closes ticket 28395.
1932 o Minor bugfixes (compilation):
1933 - Initialize a variable unconditionally in aes_new_cipher(), since
1934 some compilers cannot tell that we always initialize it before
1935 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1937 o Minor bugfixes (connection, relay):
1938 - Avoid a logging a BUG() stacktrace when closing connection held
1939 open because the write side is rate limited but not the read side.
1940 Now, the connection read side is simply shut down until Tor is
1941 able to flush the connection and close it. Fixes bug 27750; bugfix
1944 o Minor bugfixes (continuous integration, Windows):
1945 - Manually configure the zstd compiler options, when building using
1946 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1947 not come with a pkg-config file. Fixes bug 28454; bugfix
1949 - Stop using an external OpenSSL install, and stop installing MSYS2
1950 packages, when building using mingw on Appveyor Windows CI. Fixes
1951 bug 28399; bugfix on 0.3.4.1-alpha.
1953 o Minor bugfixes (documentation):
1954 - Make Doxygen work again after the code movement in the 0.3.5
1955 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
1957 o Minor bugfixes (Linux seccomp2 sandbox):
1958 - Permit the "shutdown()" system call, which is apparently used by
1959 OpenSSL under some circumstances. Fixes bug 28183; bugfix
1962 o Minor bugfixes (logging):
1963 - Stop talking about the Named flag in log messages. Clients have
1964 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
1967 o Minor bugfixes (memory leaks):
1968 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1969 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1971 o Minor bugfixes (onion services):
1972 - On an intro point for a version 3 onion service, stop closing
1973 introduction circuits on an NACK. This lets the client decide
1974 whether to reuse the circuit or discard it. Previously, we closed
1975 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
1976 0.3.2.1-alpha. Patch by Neel Chaunan.
1977 - When replacing a descriptor in the client cache, make sure to
1978 close all client introduction circuits for the old descriptor, so
1979 we don't end up with unusable leftover circuits. Fixes bug 27471;
1980 bugfix on 0.3.2.1-alpha.
1983 Changes in version 0.3.5.4-alpha - 2018-11-08
1984 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
1985 improves our continuous integration support. It continues our attempts
1986 to stabilize this alpha branch and build it into a foundation for an
1987 acceptable long-term-support release.
1989 o Major bugfixes (compilation, rust):
1990 - Rust tests can now build and run successfully with the
1991 --enable-fragile-hardening option enabled. Doing this currently
1992 requires the rust beta channel; it will be possible with stable
1993 rust once Rust version 1.31 is released. Patch from Alex Crichton.
1994 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
1996 o Major bugfixes (embedding, main loop):
1997 - When DisableNetwork becomes set, actually disable periodic events
1998 that are already enabled. (Previously, we would refrain from
1999 enabling new ones, but we would leave the old ones turned on.)
2000 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
2002 o Minor features (continuous integration):
2003 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
2005 - Add new CI job to Travis configuration to run stem-based
2006 integration tests. Closes ticket 27913.
2008 o Minor features (Windows, continuous integration):
2009 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
2010 Appveyor's CI. Closes ticket 28318.
2012 o Minor bugfixes (C correctness, also in 0.3.4.9):
2013 - Avoid undefined behavior in an end-of-string check when parsing
2014 the BEGIN line in a directory object. Fixes bug 28202; bugfix
2017 o Minor bugfixes (compilation):
2018 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
2019 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
2021 o Minor bugfixes (compilation, OpenSolaris):
2022 - Fix compilation on OpenSolaris and its descendants by adding a
2023 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
2026 o Minor bugfixes (configuration):
2027 - Refuse to start with relative file paths and RunAsDaemon set
2028 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
2031 o Minor bugfixes (directory authority, also in 0.3.4.9):
2032 - Log additional info when we get a relay that shares an ed25519 ID
2033 with a different relay, instead of a BUG() warning with a
2034 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
2036 o Minor bugfixes (onion service v3):
2037 - Build the service descriptor's signing key certificate before
2038 uploading, so we always have a fresh one: leaving no chances for
2039 it to expire service side. Fixes bug 27838; bugfix
2042 o Minor bugfixes (onion service v3, client authorization):
2043 - Fix an assert() when adding a client authorization for the first
2044 time and then sending a HUP signal to the service. Before that,
2045 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
2047 o Minor bugfixes (onion services):
2048 - Unless we have explicitly set HiddenServiceVersion, detect the
2049 onion service version and then look for invalid options.
2050 Previously, we did the reverse, but that broke existing configs
2051 which were pointed to a v2 service and had options like
2052 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
2053 0.3.5.1-alpha. Patch by Neel Chauhan.
2055 o Minor bugfixes (portability):
2056 - Make the OPE code (which is used for v3 onion services) run
2057 correctly on big-endian platforms. Fixes bug 28115; bugfix
2060 o Minor bugfixes (protover, rust):
2061 - Reject extra commas in version strings. Fixes bug 27197; bugfix
2064 o Minor bugfixes (relay shutdown, systemd):
2065 - Notify systemd of ShutdownWaitLength so it can be set to longer
2066 than systemd's TimeoutStopSec. In Tor's systemd service file, set
2067 TimeoutSec to 60 seconds to allow Tor some time to shut down.
2068 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
2070 o Minor bugfixes (rust, also in 0.3.4.9):
2071 - Fix a potential null dereference in protover_all_supported(). Add
2072 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2073 - Return a string that can be safely freed by C code, not one
2074 created by the rust allocator, in protover_all_supported(). Fixes
2075 bug 27740; bugfix on 0.3.3.1-alpha.
2077 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
2078 - Fix an API mismatch in the rust implementation of
2079 protover_compute_vote(). This bug could have caused crashes on any
2080 directory authorities running Tor with Rust (which we do not yet
2081 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2083 o Minor bugfixes (testing):
2084 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
2085 27968; bugfix on 0.3.5.1-alpha.
2087 o Minor bugfixes (testing, also in 0.3.4.9):
2088 - Treat backtrace test failures as expected on BSD-derived systems
2089 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2090 (FreeBSD failures have been treated as expected since 18204 in
2091 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2093 o Documentation (onion service manpage):
2094 - Improve HSv3 client authorization by making some options more
2095 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
2098 Changes in version 0.3.4.9 - 2018-11-02
2099 Tor 0.3.4.9 is the second stable release in its series; it backports
2100 numerous fixes, including a fix for a bandwidth management bug that
2101 was causing memory exhaustion on relays. Anyone running an earlier
2102 version of Tor 0.3.4.9 should upgrade.
2104 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
2105 - Fix compilation on ARM (and other less-used CPUs) when compiling
2106 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2108 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
2109 - Make sure Tor bootstraps and works properly if only the
2110 ControlPort is set. Prior to this fix, Tor would only bootstrap
2111 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2112 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2114 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
2115 - When our write bandwidth limit is exhausted, stop writing on the
2116 connection. Previously, we had a typo in the code that would make
2117 us stop reading instead, leading to relay connections being stuck
2118 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2121 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
2122 - Fix a use-after-free error that could be caused by passing Tor an
2123 impossible set of options that would fail during options_act().
2124 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2126 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
2127 - Don't do a distcheck with --disable-module-dirauth in Travis.
2128 Implements ticket 27252.
2129 - Only run one online rust build in Travis, to reduce network
2130 errors. Skip offline rust builds on Travis for Linux gcc, because
2131 they're redundant. Implements ticket 27252.
2132 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2133 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2134 Linux with default settings, because all the non-default builds
2135 use gcc on Linux. Implements ticket 27252.
2137 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
2138 - Use the Travis Homebrew addon to install packages on macOS during
2139 Travis CI. The package list is the same, but the Homebrew addon
2140 does not do a `brew update` by default. Implements ticket 27738.
2142 o Minor features (geoip):
2143 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2144 Country database. Closes ticket 27991.
2146 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
2147 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2148 difference algorithm for 32-bit Apple platforms. Previously, it
2149 would overflow when calculating the difference between two times
2150 more than 47 days apart. Fixes part of bug 27139; bugfix
2152 - Improve the precision of our 32-bit millisecond difference
2153 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2154 bugfix on 0.3.4.1-alpha.
2155 - Relax the tolerance on the mainloop/update_time_jumps test when
2156 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2159 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
2160 - Avoid undefined behavior in an end-of-string check when parsing
2161 the BEGIN line in a directory object. Fixes bug 28202; bugfix
2164 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
2165 - Only install the necessary mingw packages during our appveyor
2166 builds. This change makes the build a little faster, and prevents
2167 a conflict with a preinstalled mingw openssl that appveyor now
2168 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
2170 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
2171 - Rewrite our assertion macros so that they no longer suppress the
2172 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2174 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
2175 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2176 27464; bugfix on 0.3.4.1-alpha.
2178 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
2179 - Log additional info when we get a relay that shares an ed25519 ID
2180 with a different relay, instead making a BUG() warning. Fixes bug
2181 27800; bugfix on 0.3.2.1-alpha.
2183 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
2184 - Avoid a double-close when shutting down a stalled directory
2185 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2187 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
2188 - Fix a bug warning when closing an HTTP tunnel connection due to an
2189 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2192 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
2193 - Ensure circuitmux queues are empty before scheduling or sending
2194 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2196 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
2197 - When the onion service directory can't be created or has the wrong
2198 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2201 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
2202 - Close all SOCKS request (for the same .onion) if the newly fetched
2203 descriptor is unusable. Before that, we would close only the first
2204 one leaving the other hanging and let to time out by themselves.
2205 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2207 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
2208 - When selecting a v3 rendezvous point, don't only look at the
2209 protover, but also check whether the curve25519 onion key is
2210 present. This way we avoid picking a relay that supports the v3
2211 rendezvous but for which we don't have the microdescriptor. Fixes
2212 bug 27797; bugfix on 0.3.2.1-alpha.
2214 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
2215 - Reject protocol names containing bytes other than alphanumeric
2216 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2219 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
2220 - Compute protover votes correctly in the rust version of the
2221 protover code. Previously, the protover rewrite in 24031 allowed
2222 repeated votes from the same voter for the same protocol version
2223 to be counted multiple times in protover_compute_vote(). Fixes bug
2224 27649; bugfix on 0.3.3.5-rc.
2225 - Reject protover names that contain invalid characters. Fixes bug
2226 27687; bugfix on 0.3.3.1-alpha.
2228 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
2229 - protover_all_supported() would attempt to allocate up to 16GB on
2230 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2231 bugfix on 0.3.3.5-rc.
2233 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
2234 - Fix an API mismatch in the rust implementation of
2235 protover_compute_vote(). This bug could have caused crashes on any
2236 directory authorities running Tor with Rust (which we do not yet
2237 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2239 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
2240 - Fix a potential null dereference in protover_all_supported(). Add
2241 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2242 - Return a string that can be safely freed by C code, not one
2243 created by the rust allocator, in protover_all_supported(). Fixes
2244 bug 27740; bugfix on 0.3.3.1-alpha.
2246 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
2247 - If a unit test running in a subprocess exits abnormally or with a
2248 nonzero status code, treat the test as having failed, even if the
2249 test reported success. Without this fix, memory leaks don't cause
2250 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2251 bugfix on 0.2.2.4-alpha.
2253 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
2254 - Make the hs_service tests use the same time source when creating
2255 the introduction point and when testing it. Now tests work better
2256 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2259 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
2260 - Treat backtrace test failures as expected on BSD-derived systems
2261 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2262 (FreeBSD failures have been treated as expected since 18204 in
2263 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2266 Changes in version 0.3.5.3-alpha - 2018-10-17
2267 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
2268 versions. One important fix for relays addresses a problem with rate-
2269 limiting code from back in 0.3.4.x: If the fix works out, we'll be
2270 backporting it soon. This release is still an alpha, but we hope it's
2271 getting closer and closer to stability.
2273 o Major features (onion services):
2274 - Version 3 onion services can now use the per-service
2275 HiddenServiceExportCircuitID option to differentiate client
2276 circuits. It communicates with the service by using the HAProxy
2277 protocol to assign virtual IP addresses to inbound client
2278 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
2280 o Major bugfixes (compilation):
2281 - Fix compilation on ARM (and other less-used CPUs) when compiling
2282 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2284 o Major bugfixes (initialization, crash):
2285 - Fix an assertion crash that would stop Tor from starting up if it
2286 tried to activate a periodic event too early. Fixes bug 27861;
2287 bugfix on 0.3.5.1-alpha.
2289 o Major bugfixes (mainloop, bootstrap):
2290 - Make sure Tor bootstraps and works properly if only the
2291 ControlPort is set. Prior to this fix, Tor would only bootstrap
2292 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2293 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2295 o Major bugfixes (relay):
2296 - When our write bandwidth limit is exhausted, stop writing on the
2297 connection. Previously, we had a typo in the code that would make
2298 us stop reading instead, leading to relay connections being stuck
2299 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2302 o Minor features (continuous integration):
2303 - Use the Travis Homebrew addon to install packages on macOS during
2304 Travis CI. The package list is the same, but the Homebrew addon
2305 does not do a `brew update` by default. Implements ticket 27738.
2306 - Report what program produced the mysterious core file that we
2307 occasionally see on Travis CI during make distcheck. Closes
2310 o Minor features (geoip):
2311 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2312 Country database. Closes ticket 27991.
2314 o Minor bugfixes (code safety):
2315 - Rewrite our assertion macros so that they no longer suppress the
2316 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2319 o Minor bugfixes (compilation):
2320 - Compile the ed25519-donna code with a correct declaration of
2321 crypto_strongest_rand(). Previously, we built it with one type,
2322 but linked it against another in the unit tests, which caused
2323 compilation failures with LTO enabled. This could have caused
2324 other undefined behavior in the tests. Fixes bug 27728; bugfix
2327 o Minor bugfixes (compilation, netbsd):
2328 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
2331 o Minor bugfixes (continuous integration, appveyor):
2332 - Install only the necessary mingw packages during our appveyor
2333 builds. This change makes the build a little faster, and prevents
2334 a conflict with a preinstalled mingw openssl that appveyor now
2335 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
2337 o Minor bugfixes (directory permissions):
2338 - When a user requests a group-readable DataDirectory, give it to
2339 them. Previously, when the DataDirectory and the CacheDirectory
2340 were the same, the default setting (0) for
2341 CacheDirectoryGroupReadable would override the setting for
2342 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
2345 o Minor bugfixes (memory leaks):
2346 - Fix a small memory leak when calling Tor with --dump-config. Fixes
2347 bug 27893; bugfix on 0.3.2.1-alpha.
2349 o Minor bugfixes (networking):
2350 - In retry_listeners_ports(), make sure that we're removing a member
2351 of old_conns smartlist at most once. Fixes bug 27808; bugfix
2353 - Refrain from attempting socket rebinding when old and new
2354 listeners are in different address families. Fixes bug 27928;
2355 bugfix on 0.3.5.1-alpha.
2357 o Minor bugfixes (onion service v3):
2358 - Stop dumping a stack trace when trying to connect to an intro
2359 point without having a descriptor for it. Fixes bug 27774; bugfix
2361 - Don't warn so loudly when Tor is unable to decode an onion
2362 descriptor. This can now happen as a normal use case if a client
2363 gets a descriptor with client authorization but the client is not
2364 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
2365 - When selecting a v3 rendezvous point, don't only look at the
2366 protover, but also check whether the curve25519 onion key is
2367 present. This way we avoid picking a relay that supports the v3
2368 rendezvous but for which we don't have the microdescriptor. Fixes
2369 bug 27797; bugfix on 0.3.2.1-alpha.
2371 o Minor bugfixes (protover):
2372 - Reject protocol names containing bytes other than alphanumeric
2373 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2376 o Minor bugfixes (testing):
2377 - Make the hs_service tests use the same time source when creating
2378 the introduction point and when testing it. Now tests work better
2379 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2381 - In test_rebind.py, check if the Python version is in the supported
2382 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
2384 o Code simplification and refactoring:
2385 - Divide more large Tor source files -- especially ones that span
2386 multiple areas of functionality -- into smaller parts, including
2387 onion.c and main.c. Closes ticket 26747.
2388 - Divide the "routerparse.c" module into separate modules for each
2389 group of parsed objects. Closes ticket 27924.
2390 - Move protover_rust.c to the same place protover.c was moved to.
2391 Closes ticket 27814.
2392 - Split directory.c into separate pieces for client, server, and
2393 common functionality. Closes ticket 26744.
2394 - Split the non-statistics-related parts from the rephist.c and
2395 geoip.c modules. Closes ticket 27892.
2396 - Split the router.c file into relay-only and shared components, to
2397 help with future modularization. Closes ticket 27864.
2400 - In the tor-resolve(1) manpage, fix the reference to socks-
2401 extensions.txt by adding a web URL. Resolves ticket 27853.
2402 - Mention that we require Python to be 2.7 or newer for some
2403 integration tests that we ship with Tor. Resolves ticket 27677.
2406 Changes in version 0.3.5.2-alpha - 2018-09-21
2407 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
2408 that made Tor think it had run out of sockets. Anybody running a relay
2409 or an onion service on 0.3.5.1-alpha should upgrade.
2411 o Major bugfixes (relay bandwidth statistics):
2412 - When we close relayed circuits, report the data in the circuit
2413 queues as being written in our relay bandwidth stats. This
2414 mitigates guard discovery and other attacks that close circuits
2415 for the explicit purpose of noticing this discrepancy in
2416 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
2418 o Major bugfixes (socket accounting):
2419 - In our socket accounting code, count a socket as closed even when
2420 it is closed indirectly by the TLS layer. Previously, we would
2421 count these sockets as still in use, and incorrectly believe that
2422 we had run out of sockets. Fixes bug 27795; bugfix
2425 o Minor bugfixes (32-bit OSX and iOS, timing):
2426 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2427 difference algorithm for 32-bit Apple platforms. Previously, it
2428 would overflow when calculating the difference between two times
2429 more than 47 days apart. Fixes part of bug 27139; bugfix
2431 - Improve the precision of our 32-bit millisecond difference
2432 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2433 bugfix on 0.3.4.1-alpha.
2434 - Relax the tolerance on the mainloop/update_time_jumps test when
2435 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2438 o Minor bugfixes (onion service v3):
2439 - Close all SOCKS request (for the same .onion) if the newly fetched
2440 descriptor is unusable. Before that, we would close only the first
2441 one leaving the other hanging and let to time out by themselves.
2442 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2444 o Minor bugfixes (memory leak):
2445 - Fix an unlikely memory leak when trying to read a private key from
2446 a ridiculously large file. Fixes bug 27764; bugfix on
2447 0.3.5.1-alpha. This is CID 1439488.
2449 o Minor bugfixes (NSS):
2450 - Correctly detect failure to open a dummy TCP socket when stealing
2451 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
2454 o Minor bugfixes (rust):
2455 - protover_all_supported() would attempt to allocate up to 16GB on
2456 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2457 bugfix on 0.3.3.5-rc.
2459 o Minor bugfixes (testing):
2460 - Revise the "conditionvar_timeout" test so that it succeeds even on
2461 heavily loaded systems where the test threads are not scheduled
2462 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
2464 o Code simplification and refactoring:
2465 - Divide the routerlist.c and dirserv.c modules into smaller parts.
2466 Closes ticket 27799.
2469 Changes in version 0.3.5.1-alpha - 2018-09-18
2470 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
2471 client authorization for modern (v3) onion services, improves
2472 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
2473 support for NSS in place of OpenSSL, and much more.
2475 o Major features (onion services, UI change):
2476 - For a newly created onion service, the default version is now 3.
2477 Tor still supports existing version 2 services, but the operator
2478 now needs to set "HiddenServiceVersion 2" in order to create a new
2479 version 2 service. For existing services, Tor now learns the
2480 version by reading the key file. Closes ticket 27215.
2482 o Major features (relay, UI change):
2483 - Relays no longer run as exits by default. If the "ExitRelay"
2484 option is auto (or unset), and no exit policy is specified with
2485 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
2486 Previously in this case, we allowed exit traffic and logged a
2487 warning message. Closes ticket 21530. Patch by Neel Chauhan.
2488 - Tor now validates that the ContactInfo config option is valid UTF-
2489 8 when parsing torrc. Closes ticket 27428.
2491 o Major features (bootstrap):
2492 - Don't report directory progress until after a connection to a
2493 relay or bridge has succeeded. Previously, we'd report 80%
2494 progress based on cached directory information when we couldn't
2495 even connect to the network. Closes ticket 27169.
2497 o Major features (new code layout):
2498 - Nearly all of Tor's source code has been moved around into more
2499 logical places. The "common" directory is now divided into a set
2500 of libraries in "lib", and files in the "or" directory have been
2501 split into "core" (logic absolutely needed for onion routing),
2502 "feature" (independent modules in Tor), and "app" (to configure
2503 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
2504 more information. Closes ticket 26481.
2506 This refactoring is not complete: although the libraries have been
2507 refactored to be acyclic, the main body of Tor is still too
2508 interconnected. We will attempt to improve this in the future.
2510 o Major features (onion services v3):
2511 - Implement onion service client authorization at the descriptor
2512 level: only authorized clients can decrypt a service's descriptor
2513 to find out how to contact it. A new torrc option was added to
2514 control this client side: ClientOnionAuthDir <path>. On the
2515 service side, if the "authorized_clients/" directory exists in the
2516 onion service directory path, client configurations are read from
2517 the files within. See the manpage for more details. Closes ticket
2518 27547. Patch done by Suphanat Chunhapanya (haxxpop).
2519 - Improve revision counter generation in next-gen onion services.
2520 Onion services can now scale by hosting multiple instances on
2521 different hosts without synchronization between them, which was
2522 previously impossible because descriptors would get rejected by
2523 HSDirs. Addresses ticket 25552.
2525 o Major features (portability, cryptography, experimental, TLS):
2526 - Tor now has the option to compile with the NSS library instead of
2527 OpenSSL. This feature is experimental, and we expect that bugs may
2528 remain. It is mainly intended for environments where Tor's
2529 performance is not CPU-bound, and where NSS is already known to be
2530 installed. To try it out, configure Tor with the --enable-nss
2531 flag. Closes tickets 26631, 26815, and 26816.
2533 If you are experimenting with this option and using an old cached
2534 consensus, Tor may fail to start. To solve this, delete your
2535 "cached-consensus" and "cached-microdesc-consensus" files,
2536 (if present), and restart Tor.
2538 o Major bugfixes (directory authority):
2539 - Actually check that the address we get from DirAuthority
2540 configuration line is valid IPv4. Explicitly disallow DirAuthority
2541 address to be a DNS hostname. Fixes bug 26488; bugfix
2544 o Major bugfixes (restart-in-process):
2545 - Fix a use-after-free error that could be caused by passing Tor an
2546 impossible set of options that would fail during options_act().
2547 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2549 o Minor features (admin tools):
2550 - Add a new --key-expiration option to print the expiration date of
2551 the signing cert in an ed25519_signing_cert file. Resolves
2554 o Minor features (build):
2555 - If you pass the "--enable-pic" option to configure, Tor will try
2556 to tell the compiler to build position-independent code suitable
2557 to link into a dynamic library. (The default remains -fPIE, for
2558 code suitable for a relocatable executable.) Closes ticket 23846.
2560 o Minor features (code correctness, testing):
2561 - Tor's build process now includes a "check-includes" make target to
2562 verify that no module of Tor relies on any headers from a higher-
2563 level module. We hope to use this feature over time to help
2564 refactor our codebase. Closes ticket 26447.
2566 o Minor features (code layout):
2567 - We have a new "lowest-level" error-handling API for use by code
2568 invoked from within the logging module. With this interface, the
2569 logging code is no longer at risk of calling into itself if a
2570 failure occurs while it is trying to log something. Closes
2573 o Minor features (compilation):
2574 - Tor's configure script now supports a --with-malloc= option to
2575 select your malloc implementation. Supported options are
2576 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
2577 default). Addresses part of ticket 20424. Based on a patch from
2580 o Minor features (config):
2581 - The "auto" keyword in torrc is now case-insensitive. Closes
2584 o Minor features (continuous integration):
2585 - Don't do a distcheck with --disable-module-dirauth in Travis.
2586 Implements ticket 27252.
2587 - Install libcap-dev and libseccomp2-dev so these optional
2588 dependencies get tested on Travis CI. Closes ticket 26560.
2589 - Only run one online rust build in Travis, to reduce network
2590 errors. Skip offline rust builds on Travis for Linux gcc, because
2591 they're redundant. Implements ticket 27252.
2592 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2593 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2594 Linux with default settings, because all the non-default builds
2595 use gcc on Linux. Implements ticket 27252.
2597 o Minor features (controller):
2598 - Emit CIRC_BW events as soon as we detect that we processed an
2599 invalid or otherwise dropped cell on a circuit. This allows
2600 vanguards and other controllers to react more quickly to dropped
2601 cells. Closes ticket 27678.
2602 - For purposes of CIRC_BW-based dropped cell detection, track half-
2603 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
2604 bias check cells to arrive without counting it as dropped until
2605 either the END arrives, or the windows are empty. Closes
2607 - Implement a 'GETINFO md/all' controller command to enable getting
2608 all known microdescriptors. Closes ticket 8323.
2609 - The GETINFO command now support an "uptime" argument, to return
2610 Tor's uptime in seconds. Closes ticket 25132.
2612 o Minor features (denial-of-service avoidance):
2613 - Make our OOM handler aware of the DNS cache so that it doesn't
2614 fill up the memory. This check is important for our DoS mitigation
2615 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
2617 o Minor features (development):
2618 - Tor's makefile now supports running the "clippy" Rust style tool
2619 on our Rust code. Closes ticket 22156.
2621 o Minor features (directory authority):
2622 - There is no longer an artificial upper limit on the length of
2623 bandwidth lines. Closes ticket 26223.
2624 - When a bandwidth file is used to obtain the bandwidth measurements,
2625 include this bandwidth file headers in the votes. Closes
2627 - Improved support for networks with only a single authority or a
2628 single fallback directory. Patch from Gabriel Somlo. Closes
2631 o Minor features (embedding API):
2632 - The Tor controller API now supports a function to launch Tor with
2633 a preconstructed owning controller FD, so that embedding
2634 applications don't need to manage controller ports and
2635 authentication. Closes ticket 24204.
2636 - The Tor controller API now has a function that returns the name
2637 and version of the backend implementing the API. Closes
2640 o Minor features (geoip):
2641 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
2642 Country database. Closes ticket 27631.
2644 o Minor features (memory management):
2645 - Get Libevent to use the same memory allocator as Tor, by calling
2646 event_set_mem_functions() during initialization. Resolves
2649 o Minor features (memory usage):
2650 - When not using them, store legacy TAP public onion keys in DER-
2651 encoded format, rather than as expanded public keys. This should
2652 save several megabytes on typical clients. Closes ticket 27246.
2654 o Minor features (OpenSSL):
2655 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
2656 than our own. Resolves ticket 19979.
2658 o Minor features (Rust, code quality):
2659 - Improve rust code quality in the rust protover implementation by
2660 making it more idiomatic. Includes changing an internal API to
2661 take &str instead of &String. Closes ticket 26492.
2663 o Minor features (testing):
2664 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
2665 chutney. Implements ticket 27211.
2667 o Minor features (tor-resolve):
2668 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
2669 Side-effect of the refactoring for ticket 26526.
2671 o Minor features (UI):
2672 - Log each included configuration file or directory as we read it,
2673 to provide more visibility about where Tor is reading from. Patch
2674 from Unto Sten; closes ticket 27186.
2675 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
2676 Closes ticket 26703.
2678 o Minor bugfixes (bootstrap):
2679 - Try harder to get descriptors in non-exit test networks, by using
2680 the mid weight for the third hop when there are no exits. Fixes
2681 bug 27237; bugfix on 0.2.6.2-alpha.
2683 o Minor bugfixes (C correctness):
2684 - Avoid casting smartlist index to int implicitly, as it may trigger
2685 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
2686 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
2687 - Use time_t for all values in
2688 predicted_ports_prediction_time_remaining(). Rework the code that
2689 computes difference between durations/timestamps. Fixes bug 27165;
2690 bugfix on 0.3.1.1-alpha.
2692 o Minor bugfixes (client, memory usage):
2693 - When not running as a directory cache, there is no need to store
2694 the text of the current consensus networkstatus in RAM.
2695 Previously, however, clients would store it anyway, at a cost of
2696 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
2699 o Minor bugfixes (client, reachableaddresses):
2700 - Instead of adding a "reject *:*" line to ReachableAddresses when
2701 loading the configuration, add one to the policy after parsing it
2702 in parse_reachable_addresses(). This prevents extra "reject *.*"
2703 lines from accumulating on reloads. Fixes bug 20874; bugfix on
2704 0.1.1.5-alpha. Patch by Neel Chauhan.
2706 o Minor bugfixes (code quality):
2707 - Rename sandbox_getaddrinfo() and other functions to no longer
2708 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
2709 bugfix on 0.2.7.1-alpha.
2711 o Minor bugfixes (configuration, Onion Services):
2712 - In rend_service_parse_port_config(), disallow any input to remain
2713 after address-port pair was parsed. This will catch address and
2714 port being whitespace-separated by mistake of the user. Fixes bug
2715 27044; bugfix on 0.2.9.10.
2717 o Minor bugfixes (continuous integration):
2718 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2719 27464; bugfix on 0.3.4.1-alpha.
2721 o Minor bugfixes (controller):
2722 - Consider all routerinfo errors other than "not a server" to be
2723 transient for the purpose of "GETINFO exit-policy/*" controller
2724 request. Print stacktrace in the unlikely case of failing to
2725 recompute routerinfo digest. Fixes bug 27034; bugfix
2728 o Minor bugfixes (directory connection shutdown):
2729 - Avoid a double-close when shutting down a stalled directory
2730 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2732 o Minor bugfixes (HTTP tunnel):
2733 - Fix a bug warning when closing an HTTP tunnel connection due to an
2734 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2737 o Minor bugfixes (ipv6):
2738 - In addrs_in_same_network_family(), we choose the subnet size based
2739 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
2740 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
2741 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
2743 o Minor bugfixes (logging):
2744 - As a precaution, do an early return from log_addr_has_changed() if
2745 Tor is running as client. Also, log a stack trace for debugging as
2746 this function should only be called when Tor runs as server. Fixes
2747 bug 26892; bugfix on 0.1.1.9-alpha.
2748 - Refrain from mentioning bug 21018 in the logs, as it is already
2749 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
2751 o Minor bugfixes (logging, documentation):
2752 - When SafeLogging is enabled, scrub IP address in
2753 channel_tls_process_netinfo_cell(). Also, add a note to manpage
2754 that scrubbing is not guaranteed on loglevels below Notice. Fixes
2755 bug 26882; bugfix on 0.2.4.10-alpha.
2757 o Minor bugfixes (netflow padding):
2758 - Ensure circuitmux queues are empty before scheduling or sending
2759 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2761 o Minor bugfixes (onion service v2):
2762 - Log at level "info", not "warning", in the case that we do not
2763 have a consensus when a .onion request comes in. This can happen
2764 normally while bootstrapping. Fixes bug 27040; bugfix
2767 o Minor bugfixes (onion service v3):
2768 - When the onion service directory can't be created or has the wrong
2769 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2772 o Minor bugfixes (OS compatibility):
2773 - Properly handle configuration changes that move a listener to/from
2774 wildcard IP address. If the first attempt to bind a socket fails,
2775 close the old listener and try binding the socket again. Fixes bug
2776 17873; bugfix on 0.0.8pre-1.
2778 o Minor bugfixes (performance)::
2779 - Rework node_is_a_configured_bridge() to no longer call
2780 node_get_all_orports(), which was performing too many memory
2781 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
2783 o Minor bugfixes (relay statistics):
2784 - Update relay descriptor on bandwidth changes only when the uptime
2785 is smaller than 24h, in order to reduce the efficiency of guard
2786 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
2788 o Minor bugfixes (relays):
2789 - Consider the fact that we'll be making direct connections to our
2790 entry and guard nodes when computing the fraction of nodes that
2791 have their descriptors. Also, if we are using bridges and there is
2792 at least one bridge with a full descriptor, treat the fraction of
2793 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
2794 Patch by Neel Chauhan.
2795 - Update the message logged on relays when DirCache is disabled.
2796 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
2797 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
2799 o Minor bugfixes (rust, protover):
2800 - Compute protover votes correctly in the rust version of the
2801 protover code. Previously, the protover rewrite in 24031 allowed
2802 repeated votes from the same voter for the same protocol version
2803 to be counted multiple times in protover_compute_vote(). Fixes bug
2804 27649; bugfix on 0.3.3.5-rc.
2805 - Reject protover names that contain invalid characters. Fixes bug
2806 27687; bugfix on 0.3.3.1-alpha.
2808 o Minor bugfixes (testing):
2809 - Fix two unit tests to work when HOME environment variable is not
2810 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
2811 - If a unit test running in a subprocess exits abnormally or with a
2812 nonzero status code, treat the test as having failed, even if the
2813 test reported success. Without this fix, memory leaks don't cause
2814 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2815 bugfix on 0.2.2.4-alpha.
2816 - When logging a version mismatch in our openssl_version tests,
2817 report the actual offending version strings. Fixes bug 26152;
2818 bugfix on 0.2.9.1-alpha.
2819 - Fix forking tests on Windows when there is a space somewhere in
2820 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
2822 o Code simplification and refactoring:
2823 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
2824 longer needed. Closes ticket 26502.
2825 - Include paths to header files within Tor are now qualified by
2826 directory within the top-level src directory.
2827 - Many structures have been removed from the centralized "or.h"
2828 header, and moved into their own headers. This will allow us to
2829 reduce the number of places in the code that rely on each
2830 structure's contents and layout. Closes ticket 26383.
2831 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
2832 - Remove GetAdaptersAddresses_fn_t. The code that used it was
2833 removed as part of the 26481 refactor. Closes ticket 27467.
2834 - Rework Tor SOCKS server code to use Trunnel and benefit from
2835 autogenerated functions for parsing and generating SOCKS wire
2836 format. New implementation is cleaner, more maintainable and
2837 should be less prone to heartbleed-style vulnerabilities.
2838 Implements a significant fraction of ticket 3569.
2839 - Split sampled_guards_update_from_consensus() and
2840 select_entry_guard_for_circuit() into subfunctions. In
2841 entry_guards_update_primary() unite three smartlist enumerations
2842 into one and move smartlist comparison code out of the function.
2843 Closes ticket 21349.
2844 - Tor now assumes that you have standards-conformant stdint.h and
2845 inttypes.h headers when compiling. Closes ticket 26626.
2846 - Unify our bloom filter logic. Previously we had two copies of this
2847 code: one for routerlist filtering, and one for address set
2848 calculations. Closes ticket 26510.
2849 - Use the simpler strcmpstart() helper in
2850 rend_parse_v2_service_descriptor instead of strncmp(). Closes
2852 - Utility functions that can perform a DNS lookup are now wholly
2853 separated from those that can't, in separate headers and C
2854 modules. Closes ticket 26526.
2857 - Copy paragraph and URL to Tor's code of conduct document from
2858 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
2859 - Remove old instructions from INSTALL document. Closes ticket 26588.
2860 - Warn users that they should not include MyFamily line(s) in their
2861 torrc when running Tor bridge. Closes ticket 26908.
2864 - Tor no longer supports building with the dmalloc library. For
2865 debugging memory issues, we suggest using gperftools or msan
2866 instead. Closes ticket 26426.
2867 - Tor no longer attempts to run on Windows environments without the
2868 GetAdaptersAddresses() function. This function has existed since
2869 Windows XP, which is itself already older than we support.
2870 - Remove Tor2web functionality for version 2 onion services. The
2871 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
2872 (This feature was never shipped in vanilla Tor and it was only
2873 possible to use this feature by building the support at compile
2874 time. Tor2webMode is not implemented for version 3 onion services.)
2875 Closes ticket 26367.
2878 Changes in version 0.2.9.17 - 2018-09-10
2879 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
2881 o Minor features (compatibility, backport from 0.3.4.8):
2882 - Tell OpenSSL to maintain backward compatibility with previous
2883 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2884 ciphers are disabled by default. Closes ticket 27344.
2886 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2887 - Enable macOS builds in our Travis CI configuration. Closes
2889 - Install libcap-dev and libseccomp2-dev so these optional
2890 dependencies get tested on Travis CI. Closes ticket 26560.
2891 - Run asciidoc during Travis CI. Implements ticket 27087.
2892 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2894 o Minor features (geoip):
2895 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2896 Country database. Closes ticket 27089.
2898 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2899 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2900 tell the compiler not to include the system malloc implementation.
2901 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2903 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2904 - Silence a spurious compiler warning on the GetAdaptersAddresses
2905 function pointer cast. This issue is already fixed by 26481 in
2906 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2907 bugfix on 0.2.3.11-alpha.
2908 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2909 supported, and always fails. Some compilers warn about the
2910 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2913 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2914 - Don't link or search for pthreads when building for Windows, even
2915 if we are using build environment (like mingw) that provides a
2916 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2918 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2919 - Skip a pair of unreliable key generation tests on Windows, until
2920 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2921 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2923 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2924 - Pass the module flags to distcheck configure, and log the flags
2925 before running configure. (Backported to 0.2.9 and later as a
2926 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2928 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2929 - When a Travis build fails, and showing a log fails, keep trying to
2930 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2931 - When we use echo in Travis, don't pass a --flag as the first
2932 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2934 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2935 - When voting for recommended versions, make sure that all of the
2936 versions are well-formed and parsable. Fixes bug 26485; bugfix
2939 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2940 - Fix a bug in out sandboxing rules for the openat() syscall.
2941 Previously, no openat() call would be permitted, which would break
2942 filesystem operations on recent glibc versions. Fixes bug 25440;
2943 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2945 o Minor bugfixes (onion services, backport from 0.3.4.8):
2946 - Silence a spurious compiler warning in
2947 rend_client_send_introduction(). Fixes bug 27463; bugfix
2950 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2951 - Log a protocol warning when single onion services or Tor2web clients
2952 fail to authenticate direct connections to relays.
2953 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2955 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2956 - Disable core dumps in test_bt.sh, to avoid failures in "make
2957 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2959 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2960 - Before running make test-network-all, delete old logs and test
2961 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2964 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2965 - Our "tortls/cert_matches_key" unit test no longer relies on
2966 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2967 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2968 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2970 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2971 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2972 27185; bugfix on 0.2.2.2-alpha.
2975 Changes in version 0.3.2.12 - 2018-09-10
2976 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
2978 o Minor features (compatibility, backport from 0.3.4.8):
2979 - Tell OpenSSL to maintain backward compatibility with previous
2980 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2981 ciphers are disabled by default. Closes ticket 27344.
2983 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2984 - Enable macOS builds in our Travis CI configuration. Closes
2986 - Install libcap-dev and libseccomp2-dev so these optional
2987 dependencies get tested on Travis CI. Closes ticket 26560.
2988 - Run asciidoc during Travis CI. Implements ticket 27087.
2989 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2991 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2992 - Use cargo cache in our Travis CI configuration. Closes
2995 o Minor features (controller, backport from 0.3.4.6-rc):
2996 - The control port now exposes the list of HTTPTunnelPorts and
2997 ExtOrPorts via GETINFO net/listeners/httptunnel and
2998 net/listeners/extor respectively. Closes ticket 26647.
3000 o Minor features (directory authorities, backport from 0.3.4.7-rc):
3001 - Authorities no longer vote to make the subprotocol version
3002 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3003 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3005 o Minor features (geoip):
3006 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3007 Country database. Closes ticket 27089.
3009 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3010 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3011 tell the compiler not to include the system malloc implementation.
3012 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3013 - Don't try to use a pragma to temporarily disable the
3014 -Wunused-const-variable warning if the compiler doesn't support
3015 it. Fixes bug 26785; bugfix on 0.3.2.11.
3017 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3018 - Silence a spurious compiler warning on the GetAdaptersAddresses
3019 function pointer cast. This issue is already fixed by 26481 in
3020 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3021 bugfix on 0.2.3.11-alpha.
3022 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3023 supported, and always fails. Some compilers warn about the
3024 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3027 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3028 - Don't link or search for pthreads when building for Windows, even
3029 if we are using build environment (like mingw) that provides a
3030 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3032 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3033 - Skip a pair of unreliable key generation tests on Windows, until
3034 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3035 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3037 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3038 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3039 - Pass the module flags to distcheck configure, and log the flags
3040 before running configure. (Backported to 0.2.9 and later as a
3041 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3043 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3044 - When a Travis build fails, and showing a log fails, keep trying to
3045 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3046 - When we use echo in Travis, don't pass a --flag as the first
3047 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3049 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3050 - When voting for recommended versions, make sure that all of the
3051 versions are well-formed and parsable. Fixes bug 26485; bugfix
3054 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3055 - Fix a bug in out sandboxing rules for the openat() syscall.
3056 Previously, no openat() call would be permitted, which would break
3057 filesystem operations on recent glibc versions. Fixes bug 25440;
3058 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3060 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3061 - Improve the log message when connection initiators fail to
3062 authenticate direct connections to relays. Fixes bug 26927; bugfix
3065 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3066 - Fix bug that causes services to not ever rotate their descriptors
3067 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3070 o Minor bugfixes (onion services, backport from 0.3.4.8):
3071 - Silence a spurious compiler warning in
3072 rend_client_send_introduction(). Fixes bug 27463; bugfix
3075 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3076 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3078 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3079 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3080 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3081 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3083 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3084 - Log a protocol warning when single onion services or Tor2web clients
3085 fail to authenticate direct connections to relays.
3086 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3088 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3089 - Disable core dumps in test_bt.sh, to avoid failures in "make
3090 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3092 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3093 - When running make test-network-all, use the mixed+hs-v2 network.
3094 (A previous fix to chutney removed v3 onion services from the
3095 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3096 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3097 - Before running make test-network-all, delete old logs and test
3098 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3101 o Minor bugfixes (testing, openssl compatibility):
3102 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
3103 internals. Previously, it relied on unsupported OpenSSL behavior in
3104 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
3105 bugfix on 0.2.5.1-alpha.
3107 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3108 - Our "tortls/cert_matches_key" unit test no longer relies on
3109 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3110 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3111 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3113 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3114 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3115 27185; bugfix on 0.2.2.2-alpha.
3118 Changes in version 0.3.3.10 - 2018-09-10
3119 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
3121 o Minor features (bug workaround, backport from 0.3.4.7-rc):
3122 - Compile correctly on systems that provide the C11 stdatomic.h
3123 header, but where C11 atomic functions don't actually compile.
3124 Closes ticket 26779; workaround for Debian issue 903709.
3126 o Minor features (compatibility, backport from 0.3.4.8):
3127 - Tell OpenSSL to maintain backward compatibility with previous
3128 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3129 ciphers are disabled by default. Closes ticket 27344.
3131 o Minor features (continuous integration, backport from 0.3.4.7-rc):
3132 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3133 - Enable macOS builds in our Travis CI configuration. Closes
3135 - Install libcap-dev and libseccomp2-dev so these optional
3136 dependencies get tested on Travis CI. Closes ticket 26560.
3137 - Run asciidoc during Travis CI. Implements ticket 27087.
3138 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3140 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
3141 - Use cargo cache in our Travis CI configuration. Closes
3144 o Minor features (controller, backport from 0.3.4.6-rc):
3145 - The control port now exposes the list of HTTPTunnelPorts and
3146 ExtOrPorts via GETINFO net/listeners/httptunnel and
3147 net/listeners/extor respectively. Closes ticket 26647.
3149 o Minor features (directory authorities, backport from 0.3.4.7-rc):
3150 - Authorities no longer vote to make the subprotocol version
3151 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3152 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3154 o Minor features (geoip):
3155 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3156 Country database. Closes ticket 27089.
3158 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3159 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3160 tell the compiler not to include the system malloc implementation.
3161 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3162 - Don't try to use a pragma to temporarily disable the
3163 -Wunused-const-variable warning if the compiler doesn't support
3164 it. Fixes bug 26785; bugfix on 0.3.2.11.
3166 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3167 - Silence a spurious compiler warning on the GetAdaptersAddresses
3168 function pointer cast. This issue is already fixed by 26481 in
3169 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3170 bugfix on 0.2.3.11-alpha.
3171 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3172 supported, and always fails. Some compilers warn about the
3173 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3176 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3177 - Don't link or search for pthreads when building for Windows, even
3178 if we are using build environment (like mingw) that provides a
3179 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3181 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3182 - Skip a pair of unreliable key generation tests on Windows, until
3183 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3184 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3186 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3187 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3188 - Pass the module flags to distcheck configure, and log the flags
3189 before running configure. (Backported to 0.2.9 and later as a
3190 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3192 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3193 - When a Travis build fails, and showing a log fails, keep trying to
3194 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3195 - When we use echo in Travis, don't pass a --flag as the first
3196 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3198 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3199 - When voting for recommended versions, make sure that all of the
3200 versions are well-formed and parsable. Fixes bug 26485; bugfix
3203 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
3204 - Always call tor_free_all() when leaving tor_run_main(). When we
3205 did not, restarting tor in-process would cause an assertion
3206 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3208 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3209 - Fix a bug in our sandboxing rules for the openat() syscall.
3210 Previously, no openat() call would be permitted, which would break
3211 filesystem operations on recent glibc versions. Fixes bug 25440;
3212 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3214 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3215 - Improve the log message when connection initiators fail to
3216 authenticate direct connections to relays. Fixes bug 26927; bugfix
3219 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3220 - Fix bug that causes services to not ever rotate their descriptors
3221 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3224 o Minor bugfixes (onion services, backport from 0.3.4.8):
3225 - Silence a spurious compiler warning in
3226 rend_client_send_introduction(). Fixes bug 27463; bugfix
3229 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
3230 - Work around two different bugs in the OS X 10.10 and later SDKs
3231 that would prevent us from successfully targeting earlier versions
3232 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3234 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
3235 - Fix compilation of the unit tests on GNU/Hurd, which does not
3236 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3239 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3240 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3242 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3243 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3244 - Protover parsing was accepting the presence of whitespace in
3245 version strings, which the C implementation would choke on, e.g.
3246 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3247 - Protover parsing was ignoring a 2nd hyphen and everything after
3248 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3250 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3251 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3252 - cd to ${abs_top_builddir}/src/rust before running cargo in
3253 src/test/test_rust.sh. This makes the working directory consistent
3254 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3256 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3257 - Log a protocol warning when single onion services or Tor2web clients
3258 fail to authenticate direct connections to relays.
3259 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3261 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3262 - Disable core dumps in test_bt.sh, to avoid failures in "make
3263 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3265 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3266 - When running make test-network-all, use the mixed+hs-v2 network.
3267 (A previous fix to chutney removed v3 onion services from the
3268 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3269 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3270 - Before running make test-network-all, delete old logs and test
3271 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3274 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3275 - Our "tortls/cert_matches_key" unit test no longer relies on
3276 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3277 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3278 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3280 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
3281 - Stop sending ed25519 link specifiers in v3 onion service introduce
3282 cells and descriptors, when the rendezvous or introduction point
3283 doesn't support ed25519 link authentication. Fixes bug 26627;
3284 bugfix on 0.3.2.4-alpha.
3286 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3287 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3288 27185; bugfix on 0.2.2.2-alpha.
3291 Changes in version 0.3.4.8 - 2018-09-10
3292 Tor 0.3.4.8 is the first stable release in its series; it includes
3293 compilation and portability fixes.
3295 The Tor 0.3.4 series includes improvements for running Tor in
3296 low-power and embedded environments, which should help performance in
3297 general. We've begun work on better modularity, and included preliminary
3298 changes on the directory authority side to accommodate a new bandwidth
3299 measurement system. We've also integrated more continuous-integration
3300 systems into our development process, and made corresponding changes to
3301 Tor's testing infrastructure. Finally, we've continued to refine
3302 our anti-denial-of-service code.
3304 Below are the changes since 0.3.4.7-rc. For a complete list of changes
3305 since 0.3.3.9, see the ReleaseNotes file.
3307 o Minor features (compatibility):
3308 - Tell OpenSSL to maintain backward compatibility with previous
3309 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3310 ciphers are disabled by default. Closes ticket 27344.
3312 o Minor features (continuous integration):
3313 - Log the compiler path and version during Appveyor builds.
3314 Implements ticket 27449.
3315 - Show config.log and test-suite.log after failed Appveyor builds.
3316 Also upload the zipped full logs as a build artifact. Implements
3319 o Minor bugfixes (compilation):
3320 - Silence a spurious compiler warning on the GetAdaptersAddresses
3321 function pointer cast. This issue is already fixed by 26481 in
3322 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3323 bugfix on 0.2.3.11-alpha.
3324 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3325 supported, and always fails. Some compilers warn about the
3326 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3329 o Minor bugfixes (continuous integration):
3330 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
3331 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
3332 Executables compiled for 64-bit Windows with this version of gcc
3333 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
3334 27460; bugfix on 0.3.4.1-alpha.
3335 - When a Travis build fails, and showing a log fails, keep trying to
3336 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3337 - When we use echo in Travis, don't pass a --flag as the first
3338 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3340 o Minor bugfixes (onion services):
3341 - Silence a spurious compiler warning in
3342 rend_client_send_introduction(). Fixes bug 27463; bugfix
3345 o Minor bugfixes (testing, chutney):
3346 - When running make test-network-all, use the mixed+hs-v2 network.
3347 (A previous fix to chutney removed v3 onion services from the
3348 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3349 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3350 - Before running make test-network-all, delete old logs and test
3351 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3354 Changes in version 0.3.4.7-rc - 2018-08-24
3355 Tor 0.3.4.7-rc fixes several small compilation, portability, and
3356 correctness issues in previous versions of Tor. This version is a
3357 release candidate: if no serious bugs are found, we expect that the
3358 stable 0.3.4 release will be (almost) the same as this release.
3360 o Minor features (bug workaround):
3361 - Compile correctly on systems that provide the C11 stdatomic.h
3362 header, but where C11 atomic functions don't actually compile.
3363 Closes ticket 26779; workaround for Debian issue 903709.
3365 o Minor features (continuous integration):
3366 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3367 - Enable macOS builds in our Travis CI configuration. Closes
3369 - Install libcap-dev and libseccomp2-dev so these optional
3370 dependencies get tested on Travis CI. Closes ticket 26560.
3371 - Only post Appveyor IRC notifications when the build fails.
3372 Implements ticket 27275.
3373 - Run asciidoc during Travis CI. Implements ticket 27087.
3374 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3376 o Minor features (continuous integration, rust):
3377 - Use cargo cache in our Travis CI configuration. Closes
3380 o Minor features (directory authorities):
3381 - Authorities no longer vote to make the subprotocol version
3382 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3383 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3385 o Minor features (geoip):
3386 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3387 Country database. Closes ticket 27089.
3389 o Minor bugfixes (compilation, windows):
3390 - Don't link or search for pthreads when building for Windows, even
3391 if we are using build environment (like mingw) that provides a
3392 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3394 o Minor bugfixes (continuous integration):
3395 - Improve Appveyor CI IRC logging. Generate correct branches and
3396 URLs for pull requests and tags. Use unambiguous short commits.
3397 Fixes bug 26979; bugfix on master.
3398 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3399 - Pass the module flags to distcheck configure, and log the flags
3400 before running configure. (Backported to 0.2.9 and later as a
3401 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3403 o Minor bugfixes (in-process restart):
3404 - Always call tor_free_all() when leaving tor_run_main(). When we
3405 did not, restarting tor in-process would cause an assertion
3406 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3408 o Minor bugfixes (linux seccomp2 sandbox):
3409 - Fix a bug in out sandboxing rules for the openat() syscall.
3410 Previously, no openat() call would be permitted, which would break
3411 filesystem operations on recent glibc versions. Fixes bug 25440;
3412 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3414 o Minor bugfixes (onion services):
3415 - Fix bug that causes services to not ever rotate their descriptors
3416 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3419 o Minor bugfixes (portability):
3420 - Fix compilation of the unit tests on GNU/Hurd, which does not
3421 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3424 o Minor bugfixes (rust):
3425 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3427 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3428 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3429 - Protover parsing was accepting the presence of whitespace in
3430 version strings, which the C implementation would choke on, e.g.
3431 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3432 - Protover parsing was ignoring a 2nd hyphen and everything after
3433 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3435 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3436 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3437 - cd to ${abs_top_builddir}/src/rust before running cargo in
3438 src/test/test_rust.sh. This makes the working directory consistent
3439 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3441 o Minor bugfixes (testing, bootstrap):
3442 - When calculating bootstrap progress, check exit policies and the
3443 exit flag. Previously, Tor would only check the exit flag, which
3444 caused race conditions in small and fast networks like chutney.
3445 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
3447 o Minor bugfixes (testing, openssl compatibility):
3448 - Our "tortls/cert_matches_key" unit test no longer relies on
3449 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3450 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3451 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3453 o Minor bugfixes (Windows, compilation):
3454 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3455 27185; bugfix on 0.2.2.2-alpha.
3458 Changes in version 0.3.4.6-rc - 2018-08-06
3459 Tor 0.3.4.6-rc fixes several small compilation, portability, and
3460 correctness issues in previous versions of Tor. This version is a
3461 release candidate: if no serious bugs are found, we expect that the
3462 stable 0.3.4 release will be (almost) the same as this release.
3464 o Major bugfixes (event scheduler):
3465 - When we enable a periodic event, schedule it in the event loop
3466 rather than running it immediately. Previously, we would re-run
3467 periodic events immediately in the middle of (for example)
3468 changing our options, with unpredictable effects. Fixes bug 27003;
3469 bugfix on 0.3.4.1-alpha.
3471 o Minor features (compilation):
3472 - When building Tor, prefer to use Python 3 over Python 2, and more
3473 recent (contemplated) versions over older ones. Closes
3475 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3476 tell the compiler not to include the system malloc implementation.
3477 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3478 - Don't try to use a pragma to temporarily disable the
3479 -Wunused-const-variable warning if the compiler doesn't support
3480 it. Fixes bug 26785; bugfix on 0.3.2.11.
3482 o Minor bugfixes (continuous integration):
3483 - Skip a pair of unreliable key generation tests on Windows, until
3484 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3485 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3487 o Minor features (controller):
3488 - The control port now exposes the list of HTTPTunnelPorts and
3489 ExtOrPorts via GETINFO net/listeners/httptunnel and
3490 net/listeners/extor respectively. Closes ticket 26647.
3492 o Minor bugfixes (directory authority):
3493 - When voting for recommended versions, make sure that all of the
3494 versions are well-formed and parsable. Fixes bug 26485; bugfix
3497 o Minor features (geoip):
3498 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3499 Country database. Closes ticket 26674.
3501 o Minor features (Rust, portability):
3502 - Rust cross-compilation is now supported. Closes ticket 25895.
3504 o Minor bugfixes (compilation):
3505 - Update build system so that tor builds again with --disable-unittests
3506 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
3507 - Fix a compilation warning on some versions of GCC when building
3508 code that calls routerinfo_get_my_routerinfo() twice, assuming
3509 that the second call will succeed if the first one did. Fixes bug
3510 26269; bugfix on 0.2.8.2-alpha.
3512 o Minor bugfixes (controller):
3513 - Report the port correctly when a port is configured to bind to
3514 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3515 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
3516 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
3517 on 0.3.3.1-alpha. Patch by "akwizgran".
3519 o Minor bugfixes (correctness, flow control):
3520 - Upon receiving a stream-level SENDME cell, verify that our window
3521 has not grown too large. Fixes bug 26214; bugfix on svn
3524 o Minor bugfixes (memory, correctness):
3525 - Fix a number of small memory leaks identified by coverity. Fixes
3526 bug 26467; bugfix on numerous Tor versions.
3528 o Minor bugfixes (logging):
3529 - Improve the log message when connection initiators fail to
3530 authenticate direct connections to relays. Fixes bug 26927; bugfix
3533 o Minor bugfixes (portability):
3534 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
3535 26994; bugfix on 0.3.4.1-alpha.
3536 - Work around two different bugs in the OS X 10.10 and later SDKs
3537 that would prevent us from successfully targeting earlier versions
3538 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3540 o Minor bugfixes (single onion services, Tor2web):
3541 - Log a protocol warning when single onion services or Tor2web
3542 clients fail to authenticate direct connections to relays. Fixes
3543 bug 26924; bugfix on 0.2.9.1-alpha.
3545 o Minor bugfixes (testing):
3546 - Disable core dumps in test_bt.sh, to avoid failures in "make
3547 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3549 o Minor bugfixes (testing, compatibility):
3550 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
3551 only to pass strings (rather than "bytes" objects) to the Python
3552 subprocess module. Python 3 on Windows seems to require this.
3553 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
3554 0.3.1.1-alpha (for hs_ntor_ref.py).
3556 o Minor bugfixes (v3 onion services):
3557 - Stop sending ed25519 link specifiers in v3 onion service introduce
3558 cells and descriptors, when the rendezvous or introduction point
3559 doesn't support ed25519 link authentication. Fixes bug 26627;
3560 bugfix on 0.3.2.4-alpha.
3563 Changes in version 0.3.4.5-rc - 2018-07-13
3564 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
3565 bridge relays should upgrade.
3567 o Directory authority changes:
3568 - The "Bifroest" bridge authority has been retired; the new bridge
3569 authority is "Serge", and it is operated by George from the
3570 TorBSD project. Closes ticket 26771.
3573 Changes in version 0.3.3.9 - 2018-07-13
3574 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
3575 bridge relays should upgrade.
3577 o Directory authority changes:
3578 - The "Bifroest" bridge authority has been retired; the new bridge
3579 authority is "Serge", and it is operated by George from the
3580 TorBSD project. Closes ticket 26771.
3583 Changes in version 0.3.2.11 - 2018-07-13
3584 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
3585 bridge relays should upgrade. We also take this opportunity to backport
3588 o Directory authority changes:
3589 - The "Bifroest" bridge authority has been retired; the new bridge
3590 authority is "Serge", and it is operated by George from the
3591 TorBSD project. Closes ticket 26771.
3593 o Directory authority changes (backport from 0.3.3.7):
3594 - Add an IPv6 address for the "dannenberg" directory authority.
3595 Closes ticket 26343.
3597 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3598 - When directory authorities read a zero-byte bandwidth file, they
3599 would previously log a warning with the contents of an
3600 uninitialised buffer. They now log a warning about the empty file
3601 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3603 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3604 - Correctly detect when onion services get disabled after HUP. Fixes
3605 bug 25761; bugfix on 0.3.2.1.
3607 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3608 - Explicitly permit the poll() system call when the Linux
3609 seccomp2-based sandbox is enabled: apparently, some versions of
3610 libc use poll() when calling getpwnam(). Closes ticket 25313.
3612 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
3613 - Update the Travis CI configuration to use the stable Rust channel,
3614 now that we have decided to require that. Closes ticket 25714.
3616 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3617 - Our .travis.yml configuration now includes support for testing the
3618 results of "make distcheck". (It's not uncommon for "make check"
3619 to pass but "make distcheck" to fail.) Closes ticket 25814.
3620 - Our Travis CI configuration now integrates with the Coveralls
3621 coverage analysis tool. Closes ticket 25818.
3623 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3624 - Add several checks to detect whether Tor relays are uploading
3625 their descriptors without specifying why they regenerated them.
3626 Diagnostic for ticket 25686.
3628 o Minor features (compilation, backport from 0.3.4.4-rc):
3629 - When building Tor, prefer to use Python 3 over Python 2, and more
3630 recent (contemplated) versions over older ones. Closes
3633 o Minor features (geoip):
3634 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3635 Country database. Closes ticket 26674.
3637 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3638 - Upon receiving a malformed connected cell, stop processing the
3639 cell immediately. Previously we would mark the connection for
3640 close, but continue processing the cell as if the connection were
3641 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3643 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3644 - Allow the nanosleep() system call, which glibc uses to implement
3645 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3647 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3648 - When running the hs_ntor_ref.py test, make sure only to pass
3649 strings (rather than "bytes" objects) to the Python subprocess
3650 module. Python 3 on Windows seems to require this. Fixes bug
3651 26535; bugfix on 0.3.1.1-alpha.
3652 - When running the ntor_ref.py test, make sure only to pass strings
3653 (rather than "bytes" objects) to the Python subprocess module.
3654 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3657 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3658 - Work around a change in OpenSSL 1.1.1 where return values that
3659 would previously indicate "no password" now indicate an empty
3660 password. Without this workaround, Tor instances running with
3661 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3662 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3664 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
3665 - Document that the PerConnBW{Rate,Burst} options will fall back to
3666 their corresponding consensus parameters only if those parameters
3667 are set. Previously we had claimed that these values would always
3668 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3670 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3671 - Fix a compilation warning on some versions of GCC when building
3672 code that calls routerinfo_get_my_routerinfo() twice, assuming
3673 that the second call will succeed if the first one did. Fixes bug
3674 26269; bugfix on 0.2.8.2-alpha.
3676 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3677 - Don't consider Tor running as a client if the ControlPort is open,
3678 but no actual client ports are open. Fixes bug 26062; bugfix
3681 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3682 - Prevent a possible out-of-bounds smartlist read in
3683 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3685 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3686 - Fix a very unlikely (impossible, we believe) null pointer
3687 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3688 Coverity; this is CID 1430932.
3690 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3691 - Fix a memory leak when a v3 onion service is configured and gets a
3692 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3693 - When parsing the descriptor signature, look for the token plus an
3694 extra white-space at the end. This is more correct but also will
3695 allow us to support new fields that might start with "signature".
3696 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3698 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3699 - Relays now correctly block attempts to re-extend to the previous
3700 relay by Ed25519 identity. Previously they would warn in this
3701 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3704 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3705 - Avoid a crash when running with DirPort set but ORPort turned off.
3706 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3708 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3709 - Silence unused-const-variable warnings in zstd.h with some GCC
3710 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3712 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
3713 - Avoid intermittent test failures due to a test that had relied on
3714 onion service introduction point creation finishing within 5
3715 seconds of real clock time. Fixes bug 25450; bugfix
3718 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
3719 - Fix a C99 compliance issue in our configuration script that caused
3720 compilation issues when compiling Tor with certain versions of
3721 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3723 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3724 - Fix a number of small memory leaks identified by coverity. Fixes
3725 bug 26467; bugfix on numerous Tor versions.
3727 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3728 - Move the list of default directory authorities to its own file.
3729 Closes ticket 24854. Patch by "beastr0".
3732 Changes in version 0.2.9.16 - 2018-07-13
3733 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
3734 bridge relays should upgrade. We also take this opportunity to backport
3737 o Directory authority changes:
3738 - The "Bifroest" bridge authority has been retired; the new bridge
3739 authority is "Serge", and it is operated by George from the
3740 TorBSD project. Closes ticket 26771.
3742 o Directory authority changes (backport from 0.3.3.7):
3743 - Add an IPv6 address for the "dannenberg" directory authority.
3744 Closes ticket 26343.
3746 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3747 - When directory authorities read a zero-byte bandwidth file, they
3748 would previously log a warning with the contents of an
3749 uninitialised buffer. They now log a warning about the empty file
3750 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3752 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3753 - Explicitly permit the poll() system call when the Linux
3754 seccomp2-based sandbox is enabled: apparently, some versions of
3755 libc use poll() when calling getpwnam(). Closes ticket 25313.
3757 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3758 - Our .travis.yml configuration now includes support for testing the
3759 results of "make distcheck". (It's not uncommon for "make check"
3760 to pass but "make distcheck" to fail.) Closes ticket 25814.
3761 - Our Travis CI configuration now integrates with the Coveralls
3762 coverage analysis tool. Closes ticket 25818.
3764 o Minor features (compilation, backport from 0.3.4.4-rc):
3765 - When building Tor, prefer to use Python 3 over Python 2, and more
3766 recent (contemplated) versions over older ones. Closes
3769 o Minor features (geoip):
3770 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3771 Country database. Closes ticket 26674.
3773 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3774 - Upon receiving a malformed connected cell, stop processing the
3775 cell immediately. Previously we would mark the connection for
3776 close, but continue processing the cell as if the connection were
3777 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3779 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3780 - Allow the nanosleep() system call, which glibc uses to implement
3781 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3783 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3784 - When running the ntor_ref.py test, make sure only to pass strings
3785 (rather than "bytes" objects) to the Python subprocess module.
3786 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3789 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3790 - Work around a change in OpenSSL 1.1.1 where return values that
3791 would previously indicate "no password" now indicate an empty
3792 password. Without this workaround, Tor instances running with
3793 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3794 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3796 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3797 - Fix a compilation warning on some versions of GCC when building
3798 code that calls routerinfo_get_my_routerinfo() twice, assuming
3799 that the second call will succeed if the first one did. Fixes bug
3800 26269; bugfix on 0.2.8.2-alpha.
3802 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3803 - Don't consider Tor running as a client if the ControlPort is open,
3804 but no actual client ports are open. Fixes bug 26062; bugfix
3807 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3808 - Prevent a possible out-of-bounds smartlist read in
3809 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3811 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3812 - Fix a very unlikely (impossible, we believe) null pointer
3813 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3814 Coverity; this is CID 1430932.
3816 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3817 - Fix a number of small memory leaks identified by coverity. Fixes
3818 bug 26467; bugfix on numerous Tor versions.
3820 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3821 - Move the list of default directory authorities to its own file.
3822 Closes ticket 24854. Patch by "beastr0".
3825 Changes in version 0.3.4.4-rc - 2018-07-09
3826 Tor 0.3.4.4-rc fixes several small compilation, portability, and
3827 correctness issues in previous versions of Tor. This version is a
3828 release candidate: if no serious bugs are found, we expect that the
3829 stable 0.3.4 release will be (almost) the same as this release.
3831 o Minor features (compilation):
3832 - When building Tor, prefer to use Python 3 over Python 2, and more
3833 recent (contemplated) versions over older ones. Closes
3836 o Minor features (geoip):
3837 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3838 Country database. Closes ticket 26674.
3840 o Minor features (Rust, portability):
3841 - Rust cross-compilation is now supported. Closes ticket 25895.
3843 o Minor bugfixes (compilation):
3844 - Fix a compilation warning on some versions of GCC when building
3845 code that calls routerinfo_get_my_routerinfo() twice, assuming
3846 that the second call will succeed if the first one did. Fixes bug
3847 26269; bugfix on 0.2.8.2-alpha.
3849 o Minor bugfixes (control port):
3850 - Report the port correctly when a port is configured to bind to
3851 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3852 - Handle the HSADDRESS= argument to the HSPOST command properly.
3853 (Previously, this argument was misparsed and thus ignored.) Fixes
3854 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3856 o Minor bugfixes (correctness, flow control):
3857 - Upon receiving a stream-level SENDME cell, verify that our window
3858 has not grown too large. Fixes bug 26214; bugfix on svn
3861 o Minor bugfixes (memory, correctness):
3862 - Fix a number of small memory leaks identified by coverity. Fixes
3863 bug 26467; bugfix on numerous Tor versions.
3865 o Minor bugfixes (testing, compatibility):
3866 - When running the hs_ntor_ref.py test, make sure only to pass
3867 strings (rather than "bytes" objects) to the Python subprocess
3868 module. Python 3 on Windows seems to require this. Fixes bug
3869 26535; bugfix on 0.3.1.1-alpha.
3870 - When running the ntor_ref.py test, make sure only to pass strings
3871 (rather than "bytes" objects) to the Python subprocess module.
3872 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3876 Changes in version 0.3.3.8 - 2018-07-09
3877 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
3878 fixes for a memory leak affecting directory authorities.
3880 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
3881 - Stop leaking memory on directory authorities when planning to
3882 vote. This bug was crashing authorities by exhausting their
3883 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3885 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
3886 - Make sure that failing tests in Rust will actually cause the build
3887 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3890 o Minor features (compilation, backport from 0.3.4.4-rc):
3891 - When building Tor, prefer to use Python 3 over Python 2, and more
3892 recent (contemplated) versions over older ones. Closes
3895 o Minor features (geoip):
3896 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3897 Country database. Closes ticket 26674.
3899 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3900 - Add several checks to detect whether Tor relays are uploading
3901 their descriptors without specifying why they regenerated them.
3902 Diagnostic for ticket 25686.
3904 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
3905 - Don't count path selection failures as circuit build failures.
3906 This change should eliminate cases where Tor blames its guard or
3907 the network for situations like insufficient microdescriptors
3908 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
3911 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3912 - Fix a compilation warning on some versions of GCC when building
3913 code that calls routerinfo_get_my_routerinfo() twice, assuming
3914 that the second call will succeed if the first one did. Fixes bug
3915 26269; bugfix on 0.2.8.2-alpha.
3917 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
3918 - Handle the HSADDRESS= argument to the HSPOST command properly.
3919 (Previously, this argument was misparsed and thus ignored.) Fixes
3920 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3922 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3923 - Fix a number of small memory leaks identified by coverity. Fixes
3924 bug 26467; bugfix on numerous Tor versions.
3926 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3927 - Relays now correctly block attempts to re-extend to the previous
3928 relay by Ed25519 identity. Previously they would warn in this
3929 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3932 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
3933 - When shutting down, Tor now clears all the flags in the control.c
3934 module. This should prevent a bug where authentication cookies are
3935 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
3937 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3938 - When running the hs_ntor_ref.py test, make sure only to pass
3939 strings (rather than "bytes" objects) to the Python subprocess
3940 module. Python 3 on Windows seems to require this. Fixes bug
3941 26535; bugfix on 0.3.1.1-alpha.
3942 - When running the ntor_ref.py test, make sure only to pass strings
3943 (rather than "bytes" objects) to the Python subprocess module.
3944 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3948 Changes in version 0.3.4.3-alpha - 2018-06-26
3949 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
3950 one that was causing stability issues on directory authorities.
3952 o Major bugfixes (directory authority):
3953 - Stop leaking memory on directory authorities when planning to
3954 vote. This bug was crashing authorities by exhausting their
3955 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3957 o Major bugfixes (rust, testing):
3958 - Make sure that failing tests in Rust will actually cause the build
3959 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3962 o Minor feature (directory authorities):
3963 - Stop warning about incomplete bw lines before the first complete
3964 bw line has been found, so that additional header lines can be
3965 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
3967 o Minor features (relay, diagnostic):
3968 - Add several checks to detect whether Tor relays are uploading
3969 their descriptors without specifying why they regenerated them.
3970 Diagnostic for ticket 25686.
3972 o Minor features (unit tests):
3973 - Test complete bandwidth measurements files, and test that
3974 incomplete bandwidth lines only give warnings when the end of the
3975 header has not been detected. Fixes bug 25947; bugfix
3978 o Minor bugfixes (compilation):
3979 - Refrain from compiling unit testing related object files when
3980 --disable-unittests is set to configure script. Fixes bug 24891;
3981 bugfix on 0.2.5.1-alpha.
3982 - When linking the libtor_testing.a library, only include the
3983 dirauth object files once. Previously, they were getting added
3984 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
3985 - The --enable-fatal-warnings flag now affects Rust code as well.
3986 Closes ticket 26245.
3988 o Minor bugfixes (onion services):
3989 - Recompute some consensus information after detecting a clock jump,
3990 or after transitioning from a non-live consensus to a live
3991 consensus. We do this to avoid having an outdated state, and
3992 miscalculating the index for next-generation onion services. Fixes
3993 bug 24977; bugfix on 0.3.2.1-alpha.
3995 o Minor bugfixes (relay):
3996 - Relays now correctly block attempts to re-extend to the previous
3997 relay by Ed25519 identity. Previously they would warn in this
3998 case, but not actually reject the attempt. Fixes bug 26158; bugfix
4001 o Minor bugfixes (testing):
4002 - Fix compilation of the doctests in the Rust crypto crate. Fixes
4003 bug 26415; bugfix on 0.3.4.1-alpha.
4004 - Instead of trying to read the geoip configuration files from
4005 within the unit tests, instead create our own ersatz files with
4006 just enough geoip data in the format we expect. Trying to read
4007 from the source directory created problems on Windows with mingw,
4008 where the build system's paths are not the same as the platform's
4009 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
4010 - Refrain from trying to get an item from an empty smartlist in
4011 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
4012 to catch improper smartlist usage. Furthermore, enable
4013 DEBUG_SMARTLIST globally when build is configured with fragile
4014 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
4017 Changes in version 0.3.3.7 - 2018-06-12
4018 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
4019 fixes for bugs affecting compatibility and stability.
4021 o Directory authority changes:
4022 - Add an IPv6 address for the "dannenberg" directory authority.
4023 Closes ticket 26343.
4025 o Minor features (geoip):
4026 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
4027 Country database. Closes ticket 26351.
4029 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
4030 - Work around a change in OpenSSL 1.1.1 where return values that
4031 would previously indicate "no password" now indicate an empty
4032 password. Without this workaround, Tor instances running with
4033 OpenSSL 1.1.1 would accept descriptors that other Tor instances
4034 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
4036 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
4037 - Silence unused-const-variable warnings in zstd.h with some GCC
4038 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
4040 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
4041 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
4042 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
4043 miscounting the total number of circuits for these field values.)
4044 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
4046 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
4047 - Prevent a possible out-of-bounds smartlist read in
4048 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4050 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
4051 - Only select relays when they have the descriptors we prefer to use
4052 for them. This change fixes a bug where we could select a relay
4053 because it had _some_ descriptor, but reject it later with a
4054 nonfatal assertion error because it didn't have the exact one we
4055 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4058 Changes in version 0.3.4.2-alpha - 2018-06-12
4059 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
4060 release, and forward-ports an authority-only security fix from 0.3.3.6.
4062 o Directory authority changes:
4063 - Add an IPv6 address for the "dannenberg" directory authority.
4064 Closes ticket 26343.
4066 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
4067 - Fix a bug that could have allowed an attacker to force a directory
4068 authority to use up all its RAM by passing it a maliciously
4069 crafted protocol versions string. Fixes bug 25517; bugfix on
4070 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4072 o Minor features (continuous integration):
4073 - Add the necessary configuration files for continuous integration
4074 testing on Windows, via the Appveyor platform. Closes ticket
4075 25549. Patches from Marcin Cieślak and Isis Lovecruft.
4077 o Minor features (geoip):
4078 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
4079 Country database. Closes ticket 26351.
4081 o Minor bugfixes (compatibility, openssl):
4082 - Work around a change in OpenSSL 1.1.1 where return values that
4083 would previously indicate "no password" now indicate an empty
4084 password. Without this workaround, Tor instances running with
4085 OpenSSL 1.1.1 would accept descriptors that other Tor instances
4086 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
4088 o Minor bugfixes (compilation):
4089 - Silence unused-const-variable warnings in zstd.h with some GCC
4090 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
4091 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
4092 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
4093 - Avoid a compiler warning when casting the return value of
4094 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
4095 26283; bugfix on 0.2.4.10-alpha.
4097 o Minor bugfixes (control port):
4098 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
4099 CIRC_BW events. Previously, such cells were counted entirely in
4100 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
4103 o Minor bugfixes (controller):
4104 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
4105 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
4106 miscounting the total number of circuits for these field values.)
4107 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
4109 o Minor bugfixes (hardening):
4110 - Prevent a possible out-of-bounds smartlist read in
4111 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4113 o Minor bugfixes (onion services):
4114 - Fix a bug that blocked the creation of ephemeral v3 onion
4115 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
4117 o Minor bugfixes (test coverage tools):
4118 - Update our "cov-diff" script to handle output from the latest
4119 version of gcov, and to remove extraneous timestamp information
4120 from its output. Fixes bugs 26101 and 26102; bugfix
4124 Changes in version 0.3.3.6 - 2018-05-22
4125 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
4126 backports several important fixes from the 0.3.4.1-alpha.
4128 The Tor 0.3.3 series includes controller support and other
4129 improvements for v3 onion services, official support for embedding Tor
4130 within other applications, and our first non-trivial module written in
4131 the Rust programming language. (Rust is still not enabled by default
4132 when building Tor.) And as usual, there are numerous other smaller
4133 bugfixes, features, and improvements.
4135 Below are the changes since 0.3.3.5-rc. For a list of all changes
4136 since 0.3.2.10, see the ReleaseNotes file.
4138 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
4139 - When directory authorities read a zero-byte bandwidth file, they
4140 would previously log a warning with the contents of an
4141 uninitialised buffer. They now log a warning about the empty file
4142 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4144 o Major bugfixes (security, directory authority, denial-of-service):
4145 - Fix a bug that could have allowed an attacker to force a directory
4146 authority to use up all its RAM by passing it a maliciously
4147 crafted protocol versions string. Fixes bug 25517; bugfix on
4148 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4150 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
4151 - Avoid a rare assertion failure in the circuit build timeout code
4152 if we fail to allow any circuits to actually complete. Fixes bug
4153 25733; bugfix on 0.2.2.2-alpha.
4155 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
4156 - Avoid a crash when testing router reachability on a router that
4157 could have an ed25519 ID, but which does not. Fixes bug 25415;
4158 bugfix on 0.3.3.2-alpha.
4160 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
4161 - Correctly detect when onion services get disabled after HUP. Fixes
4162 bug 25761; bugfix on 0.3.2.1.
4164 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
4165 - Impose a limit on circuit cell queue size. The limit can be
4166 controlled by a consensus parameter. Fixes bug 25226; bugfix
4169 o Minor features (compatibility, backport from 0.3.4.1-alpha):
4170 - Avoid some compilation warnings with recent versions of LibreSSL.
4171 Closes ticket 26006.
4173 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
4174 - Our .travis.yml configuration now includes support for testing the
4175 results of "make distcheck". (It's not uncommon for "make check"
4176 to pass but "make distcheck" to fail.) Closes ticket 25814.
4177 - Our Travis CI configuration now integrates with the Coveralls
4178 coverage analysis tool. Closes ticket 25818.
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 bugfixes (client, backport from 0.3.4.1-alpha):
4185 - Don't consider Tor running as a client if the ControlPort is open,
4186 but no actual client ports are open. Fixes bug 26062; bugfix
4189 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
4190 - Upon receiving a malformed connected cell, stop processing the
4191 cell immediately. Previously we would mark the connection for
4192 close, but continue processing the cell as if the connection were
4193 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
4195 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
4196 - Stop saying in the manual that clients cache ipv4 dns answers from
4197 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4198 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4199 we forgot to say so in the man page. Fixes bug 26052; bugfix
4202 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
4203 - Allow the nanosleep() system call, which glibc uses to implement
4204 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4206 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
4207 - Fix a memory leak when a v3 onion service is configured and gets a
4208 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4209 - When parsing the descriptor signature, look for the token plus an
4210 extra white-space at the end. This is more correct but also will
4211 allow us to support new fields that might start with "signature".
4212 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4214 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
4215 - Avoid a crash when running with DirPort set but ORPort turned off.
4216 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4218 o Documentation (backport from 0.3.4.1-alpha):
4219 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4220 ticket 25857. Patch from "CTassisF".
4223 Changes in version 0.3.4.1-alpha - 2018-05-17
4224 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
4225 includes refactoring to begin reducing Tor's binary size and idle CPU
4226 usage on mobile, along with prep work for new bandwidth scanners,
4227 improvements to the experimental "vanguards" feature, and numerous
4228 other small features and bugfixes.
4230 o New system requirements:
4231 - Tor no longer tries to support old operating systems without
4232 mmap() or some local equivalent. Apparently, compilation on such
4233 systems has been broken for some time, without anybody noticing or
4234 complaining. Closes ticket 25398.
4236 o Major feature (directory authority, modularization):
4237 - The directory authority subsystem has been modularized. The code
4238 is now located in src/or/dirauth/, and is compiled in by default.
4239 To disable the module, the configure option
4240 --disable-module-dirauth has been added. This module may be
4241 disabled by default in some future release. Closes ticket 25610.
4243 o Major features (main loop, CPU usage):
4244 - When Tor is disabled (via DisableNetwork or via hibernation), it
4245 no longer needs to run any per-second events. This change should
4246 make it easier for mobile applications to disable Tor while the
4247 device is sleeping, or Tor is not running. Closes ticket 26063.
4248 - Tor no longer enables all of its periodic events by default.
4249 Previously, Tor would enable all possible main loop events,
4250 regardless of whether it needed them. Furthermore, many of these
4251 events are now disabled with Tor is hibernating or DisableNetwork
4252 is set. This is a big step towards reducing client CPU usage by
4253 reducing the amount of wake-ups the daemon does. Closes ticket
4255 - The bandwidth-limitation logic has been refactored so that
4256 bandwidth calculations are performed on-demand, rather than every
4257 TokenBucketRefillInterval milliseconds. This change should improve
4258 the granularity of our bandwidth calculations, and limit the
4259 number of times that the Tor process needs to wake up when it is
4260 idle. Closes ticket 25373.
4261 - Move responsibility for many operations from a once-per-second
4262 callback to a callback that is only scheduled as needed. Moving
4263 this functionality has allowed us to disable the callback when
4264 Tor's network is disabled. Once enough items are removed from our
4265 once-per-second callback, we can eliminate it entirely to conserve
4266 CPU when idle. The functionality removed includes: closing
4267 connections, circuits, and channels (ticket 25932); consensus
4268 voting (25937); flushing log callbacks (25951); honoring delayed
4269 SIGNEWNYM requests (25949); rescanning the consensus cache
4270 (25931); saving the state file to disk (25948); warning relay
4271 operators about unreachable ports (25952); and keeping track of
4272 Tor's uptime (26009).
4274 o Major bugfixes (directory authorities, security):
4275 - When directory authorities read a zero-byte bandwidth file, they
4276 would previously log a warning with the contents of an
4277 uninitialised buffer. They now log a warning about the empty file
4278 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4280 o Major bugfixes (crash):
4281 - Avoid a rare assertion failure in the circuit build timeout code
4282 if we fail to allow any circuits to actually complete. Fixes bug
4283 25733; bugfix on 0.2.2.2-alpha.
4285 o Major bugfixes (directory authority):
4286 - Avoid a crash when testing router reachability on a router that
4287 could have an ed25519 ID, but which does not. Fixes bug 25415;
4288 bugfix on 0.3.3.2-alpha.
4290 o Major bugfixes (onion service):
4291 - Correctly detect when onion services get disabled after HUP. Fixes
4292 bug 25761; bugfix on 0.3.2.1.
4294 o Major bugfixes (protover, voting):
4295 - Revise Rust implementation of protover to use a more memory-
4296 efficient voting algorithm and corresponding data structures, thus
4297 avoiding a potential (but small impact) DoS attack where specially
4298 crafted protocol strings would expand to several potential
4299 megabytes in memory. In the process, several portions of code were
4300 revised to be methods on new, custom types, rather than functions
4301 taking interchangeable types, thus increasing type safety of the
4302 module. Custom error types and handling were added as well, in
4303 order to facilitate better error dismissal/handling in outside
4304 crates and avoid mistakenly passing an internal error string to C
4305 over the FFI boundary. Many tests were added, and some previous
4306 differences between the C and Rust implementations have been
4307 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4309 o Major bugfixes (relay, denial of service):
4310 - Impose a limit on circuit cell queue size. The limit can be
4311 controlled by a consensus parameter. Fixes bug 25226; bugfix
4314 o Minor features (accounting):
4315 - When Tor becomes dormant, it now uses a scheduled event to wake up
4316 at the right time. Previously, we would use the per-second timer
4317 to check whether to wake up, but we no longer have any per-second
4318 timers enabled when the network is disabled. Closes ticket 26064.
4320 o Minor features (code quality):
4321 - Add optional spell-checking for the Tor codebase, using the
4322 "misspell" program. To use this feature, run "make check-typos".
4323 Closes ticket 25024.
4325 o Minor features (compatibility):
4326 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
4327 the no-deprecated option, and builds correctly with them. Closes
4328 tickets 19429, 19981, and 25353.
4329 - Avoid some compilation warnings with recent versions of LibreSSL.
4330 Closes ticket 26006.
4332 o Minor features (compression, zstd):
4333 - When running with zstd, Tor now considers using advanced functions
4334 that the zstd maintainers have labeled as potentially unstable. To
4335 prevent breakage, Tor will only use this functionality when the
4336 runtime version of the zstd library matches the version with which
4337 Tor was compiled. Closes ticket 25162.
4339 o Minor features (configuration):
4340 - The "DownloadSchedule" options have been renamed to end with
4341 "DownloadInitialDelay". The old names are still allowed, but will
4342 produce a warning. Comma-separated lists are still permitted for
4343 these options, but all values after the first are ignored (as they
4344 have been since 0.2.9). Closes ticket 23354.
4346 o Minor features (continuous integration):
4347 - Our .travis.yml configuration now includes support for testing the
4348 results of "make distcheck". (It's not uncommon for "make check"
4349 to pass but "make distcheck" to fail.) Closes ticket 25814.
4350 - Our Travis CI configuration now integrates with the Coveralls
4351 coverage analysis tool. Closes ticket 25818.
4353 o Minor features (control port):
4354 - Introduce GETINFO "current-time/{local,utc}" to return the local
4355 and UTC times respectively in ISO format. This helps a controller
4356 like Tor Browser detect a time-related error. Closes ticket 25511.
4357 Patch by Neel Chauhan.
4358 - Introduce new fields to the CIRC_BW event. There are two new
4359 fields in each of the read and written directions. The DELIVERED
4360 fields report the total valid data on the circuit, as measured by
4361 the payload sizes of verified and error-checked relay command
4362 cells. The OVERHEAD fields report the total unused bytes in each
4363 of these cells. Closes ticket 25903.
4365 o Minor features (directory authority):
4366 - Directory authorities now open their key-pinning files as O_SYNC,
4367 to limit their chances of accidentally writing partial lines.
4368 Closes ticket 23909.
4370 o Minor features (directory authority, forward compatibility):
4371 - Make the lines of the measured bandwidth file able to contain
4372 their entries in any order. Previously, the node_id entry needed
4373 to come first. Closes ticket 26004.
4375 o Minor features (entry guards):
4376 - Introduce a new torrc option NumPrimaryGuards for controlling the
4377 number of primary guards. Closes ticket 25843.
4379 o Minor features (geoip):
4380 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4381 database. Closes ticket 26104.
4383 o Minor features (performance):
4384 - Avoid a needless call to malloc() when processing an incoming
4385 relay cell. Closes ticket 24914.
4386 - Make our timing-wheel code run a tiny bit faster on 32-bit
4387 platforms, by preferring 32-bit math to 64-bit. Closes
4389 - Avoid a needless malloc()/free() pair every time we handle an ntor
4390 handshake. Closes ticket 25150.
4392 o Minor features (testing):
4393 - Add a unit test for voting_schedule_get_start_of_next_interval().
4394 Closes ticket 26014, and helps make unit test coverage
4396 - A new unittests module specifically for testing the functions in
4397 the (new-ish) bridges.c module has been created with new
4398 unittests, raising the code coverage percentages. Closes 25425.
4399 - We now have improved testing for addressmap_get_virtual_address()
4400 function. This should improve our test coverage, and make our test
4401 coverage more deterministic. Closes ticket 25993.
4403 o Minor features (timekeeping, circuit scheduling):
4404 - When keeping track of how busy each circuit have been recently on
4405 a given connection, use coarse-grained monotonic timers rather
4406 than gettimeofday(). This change should marginally increase
4407 accuracy and performance. Implements part of ticket 25927.
4409 o Minor bugfixes (bandwidth management):
4410 - Consider ourselves "low on write bandwidth" if we have exhausted
4411 our write bandwidth some time in the last second. This was the
4412 documented behavior before, but the actual behavior was to change
4413 this value every TokenBucketRefillInterval. Fixes bug 25828;
4414 bugfix on 0.2.3.5-alpha.
4416 o Minor bugfixes (C correctness):
4417 - Add a missing lock acquisition in the shutdown code of the control
4418 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
4419 Coverity; this is CID 1433643.
4421 o Minor bugfixes (circuit path selection):
4422 - Don't count path selection failures as circuit build failures.
4423 This change should eliminate cases where Tor blames its guard or
4424 the network for situations like insufficient microdescriptors
4425 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
4428 o Minor bugfixes (client):
4429 - Don't consider Tor running as a client if the ControlPort is open,
4430 but no actual client ports are open. Fixes bug 26062; bugfix
4433 o Minor bugfixes (code style):
4434 - Fixed multiple includes of transports.h in src/or/connection.c
4435 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
4436 - Remove the unused variable n_possible from the function
4437 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
4439 o Minor bugfixes (control interface):
4440 - Respond with more human-readable error messages to GETINFO exit-
4441 policy/* requests. Also, let controller know if an error is
4442 transient (response code 551) or not (response code 552). Fixes
4443 bug 25852; bugfix on 0.2.8.1-alpha.
4445 o Minor bugfixes (controller):
4446 - Make CIRC_BW event reflect the total of all data sent on a
4447 circuit, including padding and dropped cells. Also fix a mis-
4448 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
4449 bugfix on 0.2.5.2-alpha.
4451 o Minor bugfixes (correctness, client):
4452 - Upon receiving a malformed connected cell, stop processing the cell
4453 immediately. Previously we would mark the connection for close, but
4454 continue processing the cell as if the connection were open. Fixes bug
4455 26072; bugfix on 0.2.4.7-alpha.
4457 o Minor bugfixes (directory client):
4458 - When unverified-consensus is verified, rename it to cached-
4459 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
4460 - Fixed launching a certificate fetch always during the scheduled
4461 periodic consensus fetch by fetching only in those cases when
4462 consensus are waiting for certs. Fixes bug 24740; bugfix
4465 o Minor bugfixes (documentation):
4466 - Stop saying in the manual that clients cache ipv4 dns answers from
4467 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4468 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4469 we forgot to say so in the man page. Fixes bug 26052; bugfix
4472 o Minor bugfixes (error reporting):
4473 - Improve tolerance for directory authorities with skewed clocks.
4474 Previously, an authority with a clock more than 60 seconds ahead
4475 could cause a client with a correct clock to warn that the
4476 client's clock was behind. Now the clocks of a majority of
4477 directory authorities have to be ahead of the client before this
4478 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
4480 o Minor bugfixes (Linux seccomp2 sandbox):
4481 - Allow the nanosleep() system call, which glibc uses to implement
4482 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4484 o Minor bugfixes (onion service):
4485 - Fix a memory leak when a v3 onion service is configured and gets a
4486 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4487 - When parsing the descriptor signature, look for the token plus an
4488 extra white-space at the end. This is more correct but also will
4489 allow us to support new fields that might start with "signature".
4490 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4492 o Minor bugfixes (path selection):
4493 - Only select relays when they have the descriptors we prefer to use
4494 for them. This change fixes a bug where we could select a relay
4495 because it had _some_ descriptor, but reject it later with a
4496 nonfatal assertion error because it didn't have the exact one we
4497 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4499 o Minor bugfixes (portability):
4500 - Do not align mmap length, as it is not required by POSIX, and the
4501 getpagesize function is deprecated. Fixes bug 25399; bugfix
4504 o Minor bugfixes (portability, FreeBSD):
4505 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
4506 does not stringify on FreeBSD, so we switch to tor_asprintf().
4507 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
4509 o Minor bugfixes (relay statistics):
4510 - When a relay is collecting internal statistics about how many
4511 create cell requests it has seen of each type, accurately count
4512 the requests from relays that temporarily fall out of the
4513 consensus. (To be extra conservative, we were already ignoring
4514 requests from clients in our counts, and we continue ignoring them
4515 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
4517 o Minor bugfixes (relay, crash):
4518 - Avoid a crash when running with DirPort set but ORPort turned off.
4519 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4521 o Minor bugfixes (restart-in-process):
4522 - When shutting down, Tor now clears all the flags in the control.c
4523 module. This should prevent a bug where authentication cookies are
4524 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
4526 o Minor bugfixes (testing):
4527 - When testing workqueue event-cancellation, make sure that we
4528 actually cancel an event, and that cancel each event with equal
4529 probability. (It was previously possible, though extremely
4530 unlikely, for our event-canceling test not to cancel any events.)
4531 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
4532 - Repeat part of the test in test_client_pick_intro() a number of
4533 times, to give it consistent coverage. Fixes bug 25996; bugfix
4535 - Remove randomness from the hs_common/responsible_hsdirs test, so
4536 that it always takes the same path through the function it tests.
4537 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
4538 - Change the behavior of the "channel/outbound" test so that it
4539 never causes a 10-second rollover for the EWMA circuitmux code.
4540 Previously, this behavior would happen randomly, and result in
4541 fluctuating test coverage. Fixes bug 25994; bugfix
4543 - Use X509_new() to allocate certificates that will be freed later
4544 with X509_free(). Previously, some parts of the unit tests had
4545 used tor_malloc_zero(), which is incorrect, and which caused test
4546 failures on Windows when they were built with extra hardening.
4547 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
4549 - While running the circuit_timeout test, fix the PRNG to a
4550 deterministic AES stream, so that the test coverage from this test
4551 will itself be deterministic. Fixes bug 25995; bugfix
4554 o Minor bugfixes (vanguards):
4555 - Allow the last hop in a vanguard circuit to be the same as our
4556 first, to prevent the adversary from influencing guard node choice
4557 by choice of last hop. Also prevent the creation of A - B - A
4558 paths, or A - A paths, which are forbidden by relays. Fixes bug
4559 25870; bugfix on 0.3.3.1-alpha.
4561 o Code simplification and refactoring:
4562 - Remove duplicate code in parse_{c,s}method_line and bootstrap
4563 their functionalities into a single function. Fixes bug 6236;
4564 bugfix on 0.2.3.6-alpha.
4565 - We remove the PortForwsrding and PortForwardingHelper options,
4566 related functions, and the port_forwarding tests. These options
4567 were used by the now-deprecated Vidalia to help ordinary users
4568 become Tor relays or bridges. Closes ticket 25409. Patch by
4570 - In order to make the OR and dir checking function in router.c less
4571 confusing we renamed some functions and
4572 consider_testing_reachability() has been split into
4573 router_should_check_reachability() and
4574 router_do_reachability_checks(). Also we improved the documentation
4575 in some functions. Closes ticket 18918.
4576 - Initial work to isolate Libevent usage to a handful of modules in
4577 our codebase, to simplify our call structure, and so that we can
4578 more easily change event loops in the future if needed. Closes
4580 - Introduce a function to call getsockname() and return tor_addr_t,
4581 to save a little complexity throughout the codebase. Closes
4583 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
4584 as hsdir_index is always present. Also, we move hsdir_index_t into
4585 or.h. Closes ticket 23094. Patch by Neel Chauhan.
4586 - Merge functions used for describing nodes and suppress the
4587 functions that do not allocate memory for the output buffer
4588 string. NODE_DESC_BUF_LEN constant and format_node_description()
4589 function cannot be used externally from router.c module anymore.
4590 Closes ticket 25432. Patch by valentecaio.
4591 - Our main loop has been simplified so that all important operations
4592 happen inside events. Previously, some operations had to happen
4593 outside the event loop, to prevent infinite sequences of event
4594 activations. Closes ticket 25374.
4595 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
4596 it in register_intro_circ() and service_intro_point_new(). This
4597 prevents the digest from being re-calculated each time. Closes
4598 ticket 23107. Patch by Neel Chauhan.
4599 - Refactor token-bucket implementations to use a common backend.
4600 Closes ticket 25766.
4601 - Remove extern declaration of stats_n_seconds_working variable from
4602 main, protecting its accesses with get_uptime() and reset_uptime()
4603 functions. Closes ticket 25081, patch by “valentecaio”.
4604 - Remove our previous logic for "cached gettimeofday()" -- our
4605 coarse monotonic timers are fast enough for this purpose, and far
4606 less error-prone. Implements part of ticket 25927.
4607 - Remove the return value for fascist_firewall_choose_address_base(),
4608 and sister functions such as fascist_firewall_choose_address_node()
4609 and fascist_firewall_choose_address_rs(). Also, while we're here,
4610 initialize the ap argument as leaving it uninitialized can pose a
4611 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
4612 - Rename two fields of connection_t struct. timestamp_lastwritten is
4613 renamed to timestamp_last_write_allowed and timestamp_lastread is
4614 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
4616 - Since Tor requires C99, remove our old workaround code for libc
4617 implementations where free(NULL) doesn't work. Closes ticket 24484.
4618 - Use our standard rate-limiting code to deal with excessive
4619 libevent failures, rather than the hand-rolled logic we had
4620 before. Closes ticket 26016.
4621 - We remove the return value of node_get_prim_orport() and
4622 node_get_prim_dirport(), and introduce node_get_prim_orport() in
4623 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
4624 check for a null address. Closes ticket 23873. Patch by
4626 - We switch to should_record_bridge_info() in
4627 geoip_note_client_seen() and options_need_geoip_info() instead of
4628 accessing the configuration values directly. Fixes bug 25290;
4629 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
4631 o Deprecated features:
4632 - As we are not recommending 0.2.5 anymore, we require relays that
4633 once had an ed25519 key associated with their RSA key to always
4634 have that key, instead of allowing them to drop back to a version
4635 that didn't support ed25519. This means they need to use a new RSA
4636 key if they want to downgrade to an older version of tor without
4637 ed25519. Closes ticket 20522.
4640 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4641 ticket 25857. Patch from "CTassisF".
4644 - Directory authorities will no longer support voting according to
4645 any consensus method before consensus method 25. This keeps
4646 authorities compatible with all authorities running 0.2.9.8 and
4647 later, and does not break any clients or relays. Implements ticket
4648 24378 and proposal 290.
4649 - The PortForwarding and PortForwardingHelper features have been
4650 removed. The reasoning is, given that implementations of NAT
4651 traversal protocols within common consumer grade routers are
4652 frequently buggy, and that the target audience for a NAT punching
4653 feature is a perhaps less-technically-inclined relay operator,
4654 when the helper fails to setup traversal the problems are usually
4655 deep, ugly, and very router specific, making them horrendously
4656 impossible for technical support to reliable assist with, and thus
4657 resulting in frustration all around. Unfortunately, relay
4658 operators who would like to run relays behind NATs will need to
4659 become more familiar with the port forwarding configurations on
4660 their local router. Closes 25409.
4661 - The TestingEnableTbEmptyEvent option has been removed. It was used
4662 in testing simulations to measure how often connection buckets
4663 were emptied, in order to improve our scheduling, but it has not
4664 been actively used in years. Closes ticket 25760.
4665 - The old "round-robin" circuit multiplexer (circuitmux)
4666 implementation has been removed, along with a fairly large set of
4667 code that existed to support it. It has not been the default
4668 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
4669 but it still required an unreasonable amount of memory and CPU.
4670 Closes ticket 25268.
4673 Changes in version 0.3.3.5-rc - 2018-04-15
4674 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
4675 including some that could affect reliability or correctness.
4677 This is the first release candidate in the 0.3.3 series. If we find no
4678 new bugs or regression here, then the first stable 0.3.3 release will
4679 be nearly identical to this one.
4681 o Major bugfixes (security, protover, voting):
4682 - Revise Rust implementation of protover to use a more memory-
4683 efficient voting algorithm and corresponding data structures, thus
4684 avoiding a potential memory-based DoS attack where specially
4685 crafted protocol strings would expand to fill available memory.
4686 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4688 o Major bugfixes (performance, load balancing):
4689 - Directory authorities no longer vote in favor of the Guard flag
4690 for relays without directory support. Starting in Tor
4691 0.3.0.1-alpha, clients have been avoiding using such relays in the
4692 Guard position, leading to increasingly broken load balancing for
4693 the 5%-or-so of Guards that don't advertise directory support.
4694 Fixes bug 22310; bugfix on 0.3.0.6.
4696 o Minor feature (continuous integration):
4697 - Update the Travis CI configuration to use the stable Rust channel,
4698 now that we have decided to require that. Closes ticket 25714.
4700 o Minor features (config options):
4701 - Change the way the default value for MaxMemInQueues is calculated.
4702 We now use 40% of the hardware RAM if the system has 8 GB RAM or
4703 more. Otherwise we use the former value of 75%. Closes
4706 o Minor features (geoip):
4707 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
4708 Country database. Closes ticket 25718.
4710 o Minor bugfixes (client):
4711 - When using a listed relay as a bridge, and also using
4712 microdescriptors, and considering that relay as a non-bridge in a
4713 circuit, treat its microdescriptor as a valid source of
4714 information about that relay. This change should prevent a non-
4715 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
4717 o Minor bugfixes (controller):
4718 - Restore the correct operation of the RESOLVE command, which had
4719 been broken since we added the ability to enable/disable DNS on
4720 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
4722 o Minor bugfixes (distribution, compilation, rust):
4723 - Build correctly when the rust dependencies submodule is loaded,
4724 but the TOR_RUST_DEPENDENCIES environment variable is not set.
4725 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
4726 - Actually include all of our Rust source in our source
4727 distributions. (Previously, a few of the files were accidentally
4728 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
4730 o Minor bugfixes (documentation):
4731 - Document that the PerConnBW{Rate,Burst} options will fall back to
4732 their corresponding consensus parameters only if those parameters
4733 are set. Previously we had claimed that these values would always
4734 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
4735 - Revert a misformatting issue in the ExitPolicy documentation.
4736 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
4738 o Minor bugfixes (exit relay DNS retries):
4739 - Re-attempt timed-out DNS queries 3 times before failure, since our
4740 timeout is 5 seconds for them, but clients wait 10-15. Also allow
4741 slightly more timeouts per resolver when an exit has multiple
4742 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
4744 o Minor bugfixes (onion services):
4745 - Re-instate counting the client HSDir fetch circuits against the
4746 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
4748 - Remove underscores from the _HSLayer{2,3}Nodes options. This
4749 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
4750 Fixes bug 25581; bugfix on 0.3.3.1-alpha
4752 o Code simplification and refactoring:
4753 - Move the list of default directory authorities to its own file.
4754 Closes ticket 24854. Patch by "beastr0".
4756 o Documentation (manpage, denial of service):
4757 - Provide more detail about the denial-of-service options, by
4758 listing each mitigation and explaining how they relate. Closes
4762 Changes in version 0.3.3.4-alpha - 2018-03-29
4763 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
4764 the alpha testing of earlier releases in its series. We are
4765 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
4767 o New system requirements:
4768 - When built with Rust, Tor now depends on version 0.2.39 of the
4769 libc crate. Closes tickets 25310 and 25664.
4771 o Major bugfixes (relay, connection):
4772 - If we have failed to connect to a relay and received a connection
4773 refused, timeout, or similar error (at the TCP level), do not try
4774 that same address/port again for 60 seconds after the failure has
4775 occurred. Fixes bug 24767; bugfix on 0.0.6.
4777 o Minor features (geoip):
4778 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
4779 Country database. Closes ticket 25469.
4781 o Minor features (log messages):
4782 - Improve log message in the out-of-memory handler to include
4783 information about memory usage from the different compression
4784 backends. Closes ticket 25372.
4786 o Minor features (sandbox):
4787 - Explicitly permit the poll() system call when the Linux
4788 seccomp2-based sandbox is enabled: apparently, some versions of
4789 libc use poll() when calling getpwnam(). Closes ticket 25313.
4791 o Minor bugfixes (C correctness):
4792 - Fix a very unlikely (impossible, we believe) null pointer
4793 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
4794 Coverity; this is CID 1430932.
4796 o Minor bugfixes (channel, client):
4797 - Better identify client connection when reporting to the geoip
4798 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
4800 o Minor bugfixes (compilation):
4801 - Fix a C99 compliance issue in our configuration script that caused
4802 compilation issues when compiling Tor with certain versions of
4803 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
4805 o Minor bugfixes (controller, reliability):
4806 - Avoid a (nonfatal) assertion failure when extending a one-hop
4807 circuit from the controller to become a multihop circuit. Fixes
4808 bug 24903; bugfix on 0.2.5.2-alpha.
4810 o Major bugfixes (networking):
4811 - Tor will no longer reject IPv6 address strings from Tor Browser
4812 when they are passed as hostnames in SOCKS5 requests. Fixes bug
4813 25036, bugfix on Tor 0.3.1.2.
4815 o Minor bugfixes (networking):
4816 - string_is_valid_hostname() will not consider IP strings to be
4817 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
4819 o Minor bugfixes (onion service v3):
4820 - Avoid an assertion failure when the next onion service
4821 descriptor rotation type is out of sync with the consensus's
4822 valid-after time. Instead, log a warning message with extra
4823 information, so we can better hunt down the cause of this
4824 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
4826 o Minor bugfixes (testing):
4827 - Avoid intermittent test failures due to a test that had relied on
4828 onion service introduction point creation finishing within 5
4829 seconds of real clock time. Fixes bug 25450; bugfix
4831 - Rust crates are now automatically detected and tested. Previously,
4832 some crates were not tested by `make test-rust` due to a static
4833 string in the `src/test/test_rust.sh` script specifying which
4834 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
4836 o Minor bugfixes (testing, benchmarks):
4837 - Fix a crash when running benchmark tests on win32 systems. The
4838 crash was due to a mutex that wasn't initialized before logging
4839 and options were initialized. Fixes bug 25479; bugfix
4842 o Minor bugfixes (warnings, ipv6):
4843 - Avoid a bug warning that could occur when trying to connect to a
4844 relay over IPv6. This warning would occur on a Tor instance that
4845 downloads router descriptors, but prefers to use microdescriptors.
4846 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
4848 o Code simplification and refactoring:
4849 - Remove the old (deterministic) directory retry logic entirely:
4850 We've used exponential backoff exclusively for some time. Closes
4854 - Improved the documentation of AccountingStart parameter. Closes
4856 - Update the documentation for "Log" to include the current list of
4857 logging domains. Closes ticket 25378.
4860 Changes in version 0.3.1.10 - 2018-03-03
4861 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
4864 It includes an important security fix for a remote crash attack
4865 against directory authorities, tracked as TROVE-2018-001.
4867 This release also backports our new system for improved resistance to
4868 denial-of-service attacks against relays.
4870 This release also fixes several minor bugs and annoyances from
4873 All directory authorities should upgrade to one of the versions
4874 released today. Relays running 0.3.1.x may wish to update to one of
4875 the versions released today, for the DoS mitigations.
4877 Please note: according to our release calendar, Tor 0.3.1 will no
4878 longer be supported after 1 July 2018. If you will be running Tor
4879 after that date, you should make sure to plan to upgrade to the latest
4880 stable version, or downgrade to 0.2.9 (which will receive long-term
4883 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4884 - Fix a protocol-list handling bug that could be used to remotely crash
4885 directory authorities with a null-pointer exception. Fixes bug 25074;
4886 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4889 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4890 - Give relays some defenses against the recent network overload. We
4891 start with three defenses (default parameters in parentheses).
4892 First: if a single client address makes too many concurrent
4893 connections (>100), hang up on further connections. Second: if a
4894 single client address makes circuits too quickly (more than 3 per
4895 second, with an allowed burst of 90) while also having too many
4896 connections open (3), refuse new create cells for the next while
4897 (1-2 hours). Third: if a client asks to establish a rendezvous
4898 point to you directly, ignore the request. These defenses can be
4899 manually controlled by new torrc options, but relays will also
4900 take guidance from consensus parameters, so there's no need to
4901 configure anything manually. Implements ticket 24902.
4903 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4904 - Update the sandbox rules so that they should now work correctly
4905 with Glibc 2.26. Closes ticket 24315.
4907 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4908 - Fix an "off by 2" error in counting rendezvous failures on the
4909 onion service side. While we thought we would stop the rendezvous
4910 attempt after one failed circuit, we were actually making three
4911 circuit attempts before giving up. Now switch to a default of 2,
4912 and allow the consensus parameter "hs_service_max_rdv_failures" to
4913 override. Fixes bug 24895; bugfix on 0.0.6.
4915 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4916 - Add Link protocol version 5 to the supported protocols list. Fixes
4917 bug 25070; bugfix on 0.3.1.1-alpha.
4919 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4920 - Fix a set of false positives where relays would consider
4921 connections to other relays as being client-only connections (and
4922 thus e.g. deserving different link padding schemes) if those
4923 relays fell out of the consensus briefly. Now we look only at the
4924 initial handshake and whether the connection authenticated as a
4925 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4927 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
4928 - Make our OOM handler aware of the geoip client history cache so it
4929 doesn't fill up the memory. This check is important for IPv6 and
4930 our DoS mitigation subsystem. Closes ticket 25122.
4932 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
4933 - Change relay bandwidth reporting stats interval from 4 hours to 24
4934 hours in order to reduce the efficiency of guard discovery
4935 attacks. Fixes ticket 23856.
4937 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4938 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4939 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4940 since they neither disabled TLS 1.3 nor enabled any of the
4941 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4942 Closes ticket 24978.
4944 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
4945 - The fallback directory list has been re-generated based on the
4946 current status of the network. Tor uses fallback directories to
4947 bootstrap when it doesn't yet have up-to-date directory
4948 information. Closes ticket 24801.
4949 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4950 prefer to bootstrap from fallback directory mirrors. This is a
4951 follow-up to 24679, which removed weights from the default
4952 fallbacks. Implements ticket 24681.
4954 o Minor features (geoip):
4955 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4958 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4959 - Use the actual observed address of an incoming relay connection,
4960 not the canonical address of the relay from its descriptor, when
4961 making decisions about how to handle the incoming connection.
4962 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4964 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4965 - Directory authorities, when refusing a descriptor from a rejected
4966 relay, now explicitly tell the relay (in its logs) to set a valid
4967 ContactInfo address and contact the bad-relays@ mailing list.
4968 Fixes bug 25170; bugfix on 0.2.9.1.
4970 o Minor bugfixes (address selection, backport from 0.3.2.9):
4971 - When the fascist_firewall_choose_address_ functions don't find a
4972 reachable address, set the returned address to the null address
4973 and port. This is a precautionary measure, because some callers do
4974 not check the return value. Fixes bug 24736; bugfix
4977 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
4978 - Fetch descriptors aggressively whenever we lack enough to build
4979 circuits, regardless of how many descriptors we are missing.
4980 Previously, we would delay launching the fetch when we had fewer
4981 than 15 missing descriptors, even if some of those descriptors
4982 were blocking circuits from building. Fixes bug 23985; bugfix on
4983 0.1.1.11-alpha. The effects of this bug became worse in
4984 0.3.0.3-alpha, when we began treating missing descriptors from our
4985 primary guards as a reason to delay circuits.
4986 - Don't try fetching microdescriptors from relays that have failed
4987 to deliver them in the past. Fixes bug 23817; bugfix
4990 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
4991 - Fix a signed/unsigned comparison warning introduced by our fix to
4992 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4994 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4995 - Avoid a crash when attempting to use the seccomp2 sandbox together
4996 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4999 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5000 - Fix a possible crash on malformed consensus. If a consensus had
5001 contained an unparseable protocol line, it could have made clients
5002 and relays crash with a null-pointer exception. To exploit this
5003 issue, however, an attacker would need to be able to subvert the
5004 directory authority system. Fixes bug 25251; bugfix on
5005 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5007 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
5008 - Recover better from empty or corrupt files in the consensus cache
5009 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
5010 - When a consensus diff calculation is only partially successful,
5011 only record the successful parts as having succeeded. Partial
5012 success can happen if (for example) one compression method fails
5013 but the others succeed. Previously we misrecorded all the
5014 calculations as having succeeded, which would later cause a
5015 nonfatal assertion failure. Fixes bug 24086; bugfix
5018 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
5019 - Tor now updates its guard state when it reads a consensus
5020 regardless of whether it's missing descriptors. That makes tor use
5021 its primary guards to fetch descriptors in some edge cases where
5022 it would previously have used fallback directories. Fixes bug
5023 23862; bugfix on 0.3.0.1-alpha.
5025 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5026 - Don't treat inability to store a cached consensus object as a bug:
5027 it can happen normally when we are out of disk space. Fixes bug
5028 24859; bugfix on 0.3.1.1-alpha.
5030 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
5031 - When queuing DESTROY cells on a channel, only queue the circuit-id
5032 and reason fields: not the entire 514-byte cell. This fix should
5033 help mitigate any bugs or attacks that fill up these queues, and
5034 free more RAM for other uses. Fixes bug 24666; bugfix
5037 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
5038 - When closing a connection via close_connection_immediately(), we
5039 mark it as "not blocked on bandwidth", to prevent later calls from
5040 trying to unblock it, and give it permission to read. This fixes a
5041 backtrace warning that can happen on relays under various
5042 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5044 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
5045 - When selecting relays by bandwidth, avoid a rounding error that
5046 could sometimes cause load to be imbalanced incorrectly.
5047 Previously, we would always round upwards; now, we round towards
5048 the nearest integer. This had the biggest effect when a relay's
5049 weight adjustments should have given it weight 0, but it got
5050 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5051 - When calculating the fraction of nodes that have descriptors, and
5052 all nodes in the network have zero bandwidths, count the number of
5053 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5054 - Actually log the total bandwidth in compute_weighted_bandwidths().
5055 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5057 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5058 - Improve the performance of our consensus-diff application code
5059 when Tor is built with the --enable-fragile-hardening option set.
5060 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5062 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5063 - Don't exit the Tor process if setrlimit() fails to change the file
5064 limit (which can happen sometimes on some versions of OSX). Fixes
5065 bug 21074; bugfix on 0.0.9pre5.
5067 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
5068 - Fix a bug in the bit-counting parts of our timing-wheel code on
5069 MSVC. (Note that MSVC is still not a supported build platform, due
5070 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
5073 o Minor bugfixes (relay, partial backport):
5074 - Make the internal channel_is_client() function look at what sort
5075 of connection handshake the other side used, rather than whether
5076 the other side ever sent a create_fast cell to us. Backports part
5077 of the fixes from bugs 22805 and 24898.
5079 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5080 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5082 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5083 bugfix on 0.2.9.4-alpha.
5085 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5086 - Update the "rust dependencies" submodule to be a project-level
5087 repository, rather than a user repository. Closes ticket 25323.
5090 Changes in version 0.2.9.15 - 2018-03-03
5091 Tor 0.2.9.15 backports important security and stability bugfixes from
5094 It includes an important security fix for a remote crash attack
5095 against directory authorities, tracked as TROVE-2018-001.
5097 This release also backports our new system for improved resistance to
5098 denial-of-service attacks against relays.
5100 This release also fixes several minor bugs and annoyances from
5103 All directory authorities should upgrade to one of the versions
5104 released today. Relays running 0.2.9.x may wish to update to one of
5105 the versions released today, for the DoS mitigations.
5107 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5108 - Fix a protocol-list handling bug that could be used to remotely crash
5109 directory authorities with a null-pointer exception. Fixes bug 25074;
5110 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5113 o Major features (denial-of-service mitigation):
5114 - Give relays some defenses against the recent network overload. We
5115 start with three defenses (default parameters in parentheses).
5116 First: if a single client address makes too many concurrent
5117 connections (>100), hang up on further connections. Second: if a
5118 single client address makes circuits too quickly (more than 3 per
5119 second, with an allowed burst of 90) while also having too many
5120 connections open (3), refuse new create cells for the next while
5121 (1-2 hours). Third: if a client asks to establish a rendezvous
5122 point to you directly, ignore the request. These defenses can be
5123 manually controlled by new torrc options, but relays will also
5124 take guidance from consensus parameters, so there's no need to
5125 configure anything manually. Implements ticket 24902.
5127 o Major bugfixes (bootstrapping):
5128 - Fetch descriptors aggressively whenever we lack enough to build
5129 circuits, regardless of how many descriptors we are missing.
5130 Previously, we would delay launching the fetch when we had fewer
5131 than 15 missing descriptors, even if some of those descriptors
5132 were blocking circuits from building. Fixes bug 23985; bugfix on
5133 0.1.1.11-alpha. The effects of this bug became worse in
5134 0.3.0.3-alpha, when we began treating missing descriptors from our
5135 primary guards as a reason to delay circuits.
5137 o Major bugfixes (onion services, retry behavior):
5138 - Fix an "off by 2" error in counting rendezvous failures on the
5139 onion service side. While we thought we would stop the rendezvous
5140 attempt after one failed circuit, we were actually making three
5141 circuit attempts before giving up. Now switch to a default of 2,
5142 and allow the consensus parameter "hs_service_max_rdv_failures" to
5143 override. Fixes bug 24895; bugfix on 0.0.6.
5145 o Minor feature (relay statistics):
5146 - Change relay bandwidth reporting stats interval from 4 hours to 24
5147 hours in order to reduce the efficiency of guard discovery
5148 attacks. Fixes ticket 23856.
5150 o Minor features (compatibility, OpenSSL):
5151 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5152 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5153 since they neither disabled TLS 1.3 nor enabled any of the
5154 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5155 Closes ticket 24978.
5157 o Minor features (denial-of-service avoidance):
5158 - Make our OOM handler aware of the geoip client history cache so it
5159 doesn't fill up the memory. This check is important for IPv6 and
5160 our DoS mitigation subsystem. Closes ticket 25122.
5162 o Minor features (fallback directory mirrors):
5163 - The fallback directory list has been re-generated based on the
5164 current status of the network. Tor uses fallback directories to
5165 bootstrap when it doesn't yet have up-to-date directory
5166 information. Closes ticket 24801.
5167 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5168 prefer to bootstrap from fallback directory mirrors. This is a
5169 follow-up to 24679, which removed weights from the default
5170 fallbacks. Implements ticket 24681.
5172 o Minor features (geoip):
5173 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5176 o Minor features (linux seccomp2 sandbox):
5177 - Update the sandbox rules so that they should now work correctly
5178 with Glibc 2.26. Closes ticket 24315.
5180 o Minor bugfix (channel connection):
5181 - Use the actual observed address of an incoming relay connection,
5182 not the canonical address of the relay from its descriptor, when
5183 making decisions about how to handle the incoming connection.
5184 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5186 o Minor bugfix (directory authority):
5187 - Directory authorities, when refusing a descriptor from a rejected
5188 relay, now explicitly tell the relay (in its logs) to set a valid
5189 ContactInfo address and contact the bad-relays@ mailing list.
5190 Fixes bug 25170; bugfix on 0.2.9.1.
5192 o Minor bugfixes (address selection):
5193 - When the fascist_firewall_choose_address_ functions don't find a
5194 reachable address, set the returned address to the null address
5195 and port. This is a precautionary measure, because some callers do
5196 not check the return value. Fixes bug 24736; bugfix
5199 o Minor bugfixes (compilation):
5200 - Fix a signed/unsigned comparison warning introduced by our fix to
5201 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5203 o Minor bugfixes (control port, linux seccomp2 sandbox):
5204 - Avoid a crash when attempting to use the seccomp2 sandbox together
5205 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5208 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5209 - Fix a possible crash on malformed consensus. If a consensus had
5210 contained an unparseable protocol line, it could have made clients
5211 and relays crash with a null-pointer exception. To exploit this
5212 issue, however, an attacker would need to be able to subvert the
5213 directory authority system. Fixes bug 25251; bugfix on
5214 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5216 o Minor bugfixes (memory usage):
5217 - When queuing DESTROY cells on a channel, only queue the circuit-id
5218 and reason fields: not the entire 514-byte cell. This fix should
5219 help mitigate any bugs or attacks that fill up these queues, and
5220 free more RAM for other uses. Fixes bug 24666; bugfix
5223 o Minor bugfixes (network layer):
5224 - When closing a connection via close_connection_immediately(), we
5225 mark it as "not blocked on bandwidth", to prevent later calls from
5226 trying to unblock it, and give it permission to read. This fixes a
5227 backtrace warning that can happen on relays under various
5228 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5230 o Minor bugfixes (OSX):
5231 - Don't exit the Tor process if setrlimit() fails to change the file
5232 limit (which can happen sometimes on some versions of OSX). Fixes
5233 bug 21074; bugfix on 0.0.9pre5.
5235 o Minor bugfixes (path selection):
5236 - When selecting relays by bandwidth, avoid a rounding error that
5237 could sometimes cause load to be imbalanced incorrectly.
5238 Previously, we would always round upwards; now, we round towards
5239 the nearest integer. This had the biggest effect when a relay's
5240 weight adjustments should have given it weight 0, but it got
5241 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5242 - When calculating the fraction of nodes that have descriptors, and
5243 all nodes in the network have zero bandwidths, count the number of
5244 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5245 - Actually log the total bandwidth in compute_weighted_bandwidths().
5246 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5248 o Minor bugfixes (portability, msvc):
5249 - Fix a bug in the bit-counting parts of our timing-wheel code on
5250 MSVC. (Note that MSVC is still not a supported build platform, due
5251 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5254 o Minor bugfixes (relay):
5255 - Make the internal channel_is_client() function look at what sort
5256 of connection handshake the other side used, rather than whether
5257 the other side ever sent a create_fast cell to us. Backports part
5258 of the fixes from bugs 22805 and 24898.
5260 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5261 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5263 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5264 bugfix on 0.2.9.4-alpha.
5267 Changes in version 0.3.2.10 - 2018-03-03
5268 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
5269 backports a number of bugfixes, including important fixes for security
5272 It includes an important security fix for a remote crash attack
5273 against directory authorities, tracked as TROVE-2018-001.
5275 Additionally, it backports a fix for a bug whose severity we have
5276 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
5277 triggered in order to crash relays with a use-after-free pattern. As
5278 such, we are now tracking that bug as TROVE-2018-002 and
5279 CVE-2018-0491, and backporting it to earlier releases. This bug
5280 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
5283 This release also backports our new system for improved resistance to
5284 denial-of-service attacks against relays.
5286 This release also fixes several minor bugs and annoyances from
5289 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
5290 today, for the fix to TROVE-2018-002. Directory authorities should
5291 also upgrade. (Relays on earlier versions might want to update too for
5292 the DoS mitigations.)
5294 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5295 - Fix a protocol-list handling bug that could be used to remotely crash
5296 directory authorities with a null-pointer exception. Fixes bug 25074;
5297 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5300 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
5301 - Avoid adding the same channel twice in the KIST scheduler pending
5302 list, which could lead to remote denial-of-service use-after-free
5303 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
5305 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
5306 - Give relays some defenses against the recent network overload. We
5307 start with three defenses (default parameters in parentheses).
5308 First: if a single client address makes too many concurrent
5309 connections (>100), hang up on further connections. Second: if a
5310 single client address makes circuits too quickly (more than 3 per
5311 second, with an allowed burst of 90) while also having too many
5312 connections open (3), refuse new create cells for the next while
5313 (1-2 hours). Third: if a client asks to establish a rendezvous
5314 point to you directly, ignore the request. These defenses can be
5315 manually controlled by new torrc options, but relays will also
5316 take guidance from consensus parameters, so there's no need to
5317 configure anything manually. Implements ticket 24902.
5319 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
5320 - Fix an "off by 2" error in counting rendezvous failures on the
5321 onion service side. While we thought we would stop the rendezvous
5322 attempt after one failed circuit, we were actually making three
5323 circuit attempts before giving up. Now switch to a default of 2,
5324 and allow the consensus parameter "hs_service_max_rdv_failures" to
5325 override. Fixes bug 24895; bugfix on 0.0.6.
5326 - New-style (v3) onion services now obey the "max rendezvous circuit
5327 attempts" logic. Previously they would make as many rendezvous
5328 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5329 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5331 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
5332 - Add Link protocol version 5 to the supported protocols list. Fixes
5333 bug 25070; bugfix on 0.3.1.1-alpha.
5335 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
5336 - Fix a set of false positives where relays would consider
5337 connections to other relays as being client-only connections (and
5338 thus e.g. deserving different link padding schemes) if those
5339 relays fell out of the consensus briefly. Now we look only at the
5340 initial handshake and whether the connection authenticated as a
5341 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5343 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
5344 - The scheduler subsystem was failing to promptly notice changes in
5345 consensus parameters, making it harder to switch schedulers
5346 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5348 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
5349 - Make our OOM handler aware of the geoip client history cache so it
5350 doesn't fill up the memory. This check is important for IPv6 and
5351 our DoS mitigation subsystem. Closes ticket 25122.
5353 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
5354 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5355 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5356 since they neither disabled TLS 1.3 nor enabled any of the
5357 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5358 Closes ticket 24978.
5360 o Minor features (geoip):
5361 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5364 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
5365 - When logging a failure to create an onion service's descriptor,
5366 also log what the problem with the descriptor was. Diagnostic
5369 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
5370 - Use the actual observed address of an incoming relay connection,
5371 not the canonical address of the relay from its descriptor, when
5372 making decisions about how to handle the incoming connection.
5373 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5375 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5376 - Fix a possible crash on malformed consensus. If a consensus had
5377 contained an unparseable protocol line, it could have made clients
5378 and relays crash with a null-pointer exception. To exploit this
5379 issue, however, an attacker would need to be able to subvert the
5380 directory authority system. Fixes bug 25251; bugfix on
5381 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5383 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
5384 - Directory authorities, when refusing a descriptor from a rejected
5385 relay, now explicitly tell the relay (in its logs) to set a valid
5386 ContactInfo address and contact the bad-relays@ mailing list.
5387 Fixes bug 25170; bugfix on 0.2.9.1.
5389 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
5390 - When building with Rust on OSX, link against libresolv, to work
5391 around the issue at https://github.com/rust-lang/rust/issues/46797.
5392 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5394 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
5395 - Remove a BUG() statement when a client fetches an onion descriptor
5396 that has a lower revision counter than the one in its cache. This
5397 can happen in normal circumstances due to HSDir desync. Fixes bug
5398 24976; bugfix on 0.3.2.1-alpha.
5400 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5401 - Don't treat inability to store a cached consensus object as a bug:
5402 it can happen normally when we are out of disk space. Fixes bug
5403 24859; bugfix on 0.3.1.1-alpha.
5405 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5406 - Improve the performance of our consensus-diff application code
5407 when Tor is built with the --enable-fragile-hardening option set.
5408 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5410 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5411 - Don't exit the Tor process if setrlimit() fails to change the file
5412 limit (which can happen sometimes on some versions of OSX). Fixes
5413 bug 21074; bugfix on 0.0.9pre5.
5415 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5416 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5418 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5419 bugfix on 0.2.9.4-alpha.
5421 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
5422 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5423 25005; bugfix on 0.3.2.7-rc.
5425 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
5426 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5427 version, when deciding whether a consensus entry can support the
5428 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5429 bugfix on 0.3.2.1-alpha.
5431 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5432 - Update the "rust dependencies" submodule to be a project-level
5433 repository, rather than a user repository. Closes ticket 25323.
5435 o Documentation (backport from 0.3.3.1-alpha)
5436 - Document that operators who run more than one relay or bridge are
5437 expected to set MyFamily and ContactInfo correctly. Closes
5441 Changes in version 0.3.3.3-alpha - 2018-03-03
5442 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
5443 It includes an important security fix for a remote crash attack
5444 against directory authorities tracked as TROVE-2018-001.
5446 Additionally, with this release, we are upgrading the severity of a
5447 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
5448 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
5449 a use-after-free pattern. As such, we are now tracking that bug as
5450 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
5451 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
5453 This release also fixes several minor bugs and annoyances from
5456 Relays running 0.3.2.x should upgrade to one of the versions released
5457 today, for the fix to TROVE-2018-002. Directory authorities should
5458 also upgrade. (Relays on earlier versions might want to update too for
5459 the DoS mitigations.)
5461 o Major bugfixes (denial-of-service, directory authority):
5462 - Fix a protocol-list handling bug that could be used to remotely crash
5463 directory authorities with a null-pointer exception. Fixes bug 25074;
5464 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5467 o Minor features (compatibility, OpenSSL):
5468 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5469 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5470 since they neither disabled TLS 1.3 nor enabled any of the
5471 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5472 Closes ticket 24978.
5474 o Minor features (logging):
5475 - Clarify the log messages produced when getrandom() or a related
5476 entropy-generation mechanism gives an error. Closes ticket 25120.
5478 o Minor features (testing):
5479 - Add a "make test-rust" target to run the rust tests only. Closes
5482 o Minor bugfixes (denial-of-service):
5483 - Fix a possible crash on malformed consensus. If a consensus had
5484 contained an unparseable protocol line, it could have made clients
5485 and relays crash with a null-pointer exception. To exploit this
5486 issue, however, an attacker would need to be able to subvert the
5487 directory authority system. Fixes bug 25251; bugfix on
5488 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5490 o Minor bugfixes (DoS mitigation):
5491 - Add extra safety checks when refilling the circuit creation bucket
5492 to ensure we never set a value above the allowed maximum burst.
5493 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
5494 - When a new consensus arrives, don't update our DoS-mitigation
5495 parameters if we aren't a public relay. Fixes bug 25223; bugfix
5498 o Minor bugfixes (man page, SocksPort):
5499 - Remove dead code from the old "SocksSocket" option, and rename
5500 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
5501 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
5503 o Minor bugfixes (performance):
5504 - Reduce the number of circuits that will be opened at once during
5505 the circuit build timeout phase. This is done by increasing the
5506 idle timeout to 3 minutes, and lowering the maximum number of
5507 concurrent learning circuits to 10. Fixes bug 24769; bugfix
5510 o Minor bugfixes (spec conformance):
5511 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5513 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5514 bugfix on 0.2.9.4-alpha.
5516 o Minor bugfixes (spec conformance, rust):
5517 - Resolve a denial-of-service issue caused by an infinite loop in
5518 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
5519 Also tracked as TROVE-2018-003.
5521 o Code simplification and refactoring:
5522 - Update the "rust dependencies" submodule to be a project-level
5523 repository, rather than a user repository. Closes ticket 25323.
5526 Changes in version 0.3.3.2-alpha - 2018-02-10
5527 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
5528 introduces a mechanism to handle the high loads that many relay
5529 operators have been reporting recently. It also fixes several bugs in
5530 older releases. If this new code proves reliable, we plan to backport
5531 it to older supported release series.
5533 o Major features (denial-of-service mitigation):
5534 - Give relays some defenses against the recent network overload. We
5535 start with three defenses (default parameters in parentheses).
5536 First: if a single client address makes too many concurrent
5537 connections (>100), hang up on further connections. Second: if a
5538 single client address makes circuits too quickly (more than 3 per
5539 second, with an allowed burst of 90) while also having too many
5540 connections open (3), refuse new create cells for the next while
5541 (1-2 hours). Third: if a client asks to establish a rendezvous
5542 point to you directly, ignore the request. These defenses can be
5543 manually controlled by new torrc options, but relays will also
5544 take guidance from consensus parameters, so there's no need to
5545 configure anything manually. Implements ticket 24902.
5547 o Major bugfixes (netflow padding):
5548 - Stop adding unneeded channel padding right after we finish
5549 flushing to a connection that has been trying to flush for many
5550 seconds. Instead, treat all partial or complete flushes as
5551 activity on the channel, which will defer the time until we need
5552 to add padding. This fix should resolve confusing and scary log
5553 messages like "Channel padding timeout scheduled 221453ms in the
5554 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
5556 o Major bugfixes (protocol versions):
5557 - Add Link protocol version 5 to the supported protocols list. Fixes
5558 bug 25070; bugfix on 0.3.1.1-alpha.
5560 o Major bugfixes (scheduler, consensus):
5561 - The scheduler subsystem was failing to promptly notice changes in
5562 consensus parameters, making it harder to switch schedulers
5563 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5565 o Minor features (denial-of-service avoidance):
5566 - Make our OOM handler aware of the geoip client history cache so it
5567 doesn't fill up the memory. This check is important for IPv6 and
5568 our DoS mitigation subsystem. Closes ticket 25122.
5570 o Minor features (directory authority):
5571 - When directory authorities are unable to add signatures to a
5572 pending consensus, log the reason why. Closes ticket 24849.
5574 o Minor features (geoip):
5575 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5578 o Minor features (logging, diagnostic):
5579 - When logging a failure to create an onion service's descriptor,
5580 also log what the problem with the descriptor was. Diagnostic for
5583 o Minor bugfix (channel connection):
5584 - Use the actual observed address of an incoming relay connection,
5585 not the canonical address of the relay from its descriptor, when
5586 making decisions about how to handle the incoming connection.
5587 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5589 o Minor bugfix (directory authority):
5590 - Directory authorities, when refusing a descriptor from a rejected
5591 relay, now explicitly tell the relay (in its logs) to set a valid
5592 ContactInfo address and contact the bad-relays@ mailing list.
5593 Fixes bug 25170; bugfix on 0.2.9.1.
5595 o Minor bugfixes (all versions of Tor):
5596 - Use the "misspell" tool to detect and fix typos throughout the
5597 source code. Fixes bug 23650; bugfix on various versions of Tor.
5598 Patch from Deepesh Pathak.
5600 o Minor bugfixes (circuit, cannibalization):
5601 - Don't cannibalize preemptively-built circuits if we no longer
5602 recognize their first hop. This situation can happen if our Guard
5603 relay went off the consensus after the circuit was created. Fixes
5604 bug 24469; bugfix on 0.0.6.
5606 o Minor bugfixes (correctness):
5607 - Remove a nonworking, unnecessary check to see whether a circuit
5608 hop's identity digest was set when the circuit failed. Fixes bug
5609 24927; bugfix on 0.2.4.4-alpha.
5611 o Minor bugfixes (logging):
5612 - Don't treat inability to store a cached consensus object as a bug:
5613 it can happen normally when we are out of disk space. Fixes bug
5614 24859; bugfix on 0.3.1.1-alpha.
5615 - Fix a (mostly harmless) race condition when invoking
5616 LOG_PROTOCOL_WARN message from a subthread while the torrc options
5617 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
5619 o Minor bugfixes (onion services):
5620 - Remove a BUG() statement when a client fetches an onion descriptor
5621 that has a lower revision counter than the one in its cache. This
5622 can happen in normal circumstances due to HSDir desync. Fixes bug
5623 24976; bugfix on 0.3.2.1-alpha.
5624 - If we are configured to offer a single onion service, don't log
5625 long-term established one hop rendezvous points in the heartbeat.
5626 Fixes bug 25116; bugfix on 0.2.9.6-rc.
5628 o Minor bugfixes (performance):
5629 - Avoid calling protocol_list_supports_protocol() from inside tight
5630 loops when running with cached routerinfo_t objects. Instead,
5631 summarize the relevant protocols as flags in the routerinfo_t, as
5632 we do for routerstatus_t objects. This change simplifies our code
5633 a little, and saves a large amount of short-term memory allocation
5634 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
5636 o Minor bugfixes (Rust FFI):
5637 - Fix a minor memory leak which would happen whenever the C code
5638 would call the Rust implementation of
5639 protover_get_supported_protocols(). This was due to the C version
5640 returning a static string, whereas the Rust version newly allocated
5641 a CString to pass across the FFI boundary. Consequently, the C
5642 code was not expecting to need to free() what it was given. Fixes
5643 bug 25127; bugfix on 0.3.2.1-alpha.
5645 o Minor bugfixes (scheduler, KIST):
5646 - Avoid adding the same channel twice in the KIST scheduler pending
5647 list, which would waste CPU cycles. Fixes bug 24700; bugfix
5650 o Minor bugfixes (unit test, monotonic time):
5651 - Increase a constant (1msec to 10msec) in the monotonic time test
5652 that makes sure the nsec/usec/msec times read are synchronized.
5653 This change was needed to accommodate slow systems like armel or
5654 when the clock_gettime() is not a VDSO on the running kernel.
5655 Fixes bug 25113; bugfix on 0.2.9.1.
5657 o Minor bugfixes (v3 onion services):
5658 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5659 version, when deciding whether a consensus entry can support the
5660 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5661 bugfix on 0.3.2.1-alpha.
5663 o Code simplification and refactoring:
5664 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
5666 - Remove a series of counters used to track circuit extend attempts
5667 and connection status but that in reality we aren't using for
5668 anything other than stats logged by a SIGUSR1 signal. Closes
5671 o Documentation (man page):
5672 - The HiddenServiceVersion torrc option accepts only one number:
5673 either version 2 or 3. Closes ticket 25026; bugfix
5677 Changes in version 0.3.3.1-alpha - 2018-01-25
5678 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
5679 several new features to Tor, including several improvements to
5680 bootstrapping, and support for an experimental "vanguards" feature to
5681 resist guard discovery attacks. This series also includes better
5682 support for applications that need to embed Tor or manage v3
5685 o Major features (embedding):
5686 - There is now a documented stable API for programs that need to
5687 embed Tor. See tor_api.h for full documentation and known bugs.
5688 Closes ticket 23684.
5689 - Tor now has support for restarting in the same process.
5690 Controllers that run Tor using the "tor_api.h" interface can now
5691 restart Tor after Tor has exited. This support is incomplete,
5692 however: we fixed crash bugs that prevented it from working at
5693 all, but many bugs probably remain, including a possibility of
5694 security issues. Implements ticket 24581.
5696 o Major features (IPv6, directory documents):
5697 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
5698 consensus. This information makes it easier for IPv6 clients to
5699 bootstrap and choose reachable entry guards. Implements ticket 23826.
5700 - Add consensus method 28, which removes IPv6 ORPorts from
5701 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
5702 are redundant in microdescs. This change will be used by Tor clients
5703 on 0.2.8.x and later. (That is to say, with all Tor clients that
5704 have IPv6 bootstrap and guard support.) Implements ticket 23828.
5705 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
5706 set by different numbers of authorities. Fixes 23870
5709 o Major features (onion service v3, control port):
5710 - The control port now supports commands and events for v3 onion
5711 services. It is now possible to create ephemeral v3 services using
5712 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
5713 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
5714 DEL_ONION) have been extended to support v3 onion services. Closes
5715 ticket 20699; implements proposal 284.
5717 o Major features (onion services):
5718 - Provide torrc options to pin the second and third hops of onion
5719 service circuits to a list of nodes. The option HSLayer2Guards
5720 pins the second hop, and the option HSLayer3Guards pins the third
5721 hop. These options are for use in conjunction with experiments
5722 with "vanguards" for preventing guard enumeration attacks. Closes
5725 o Major features (rust, portability, experimental):
5726 - Tor now ships with an optional implementation of one of its
5727 smaller modules (protover.c) in the Rust programming language. To
5728 try it out, install a Rust build environment, and configure Tor
5729 with "--enable-rust --enable-cargo-online-mode". This should not
5730 cause any user-visible changes, but should help us gain more
5731 experience with Rust, and plan future Rust integration work.
5732 Implementation by Chelsea Komlo. Closes ticket 22840.
5734 o Minor features (storage, configuration):
5735 - Users can store cached directory documents somewhere other than
5736 the DataDirectory by using the CacheDirectory option. Similarly,
5737 the storage location for relay's keys can be overridden with the
5738 KeyDirectory option. Closes ticket 22703.
5740 o Major features (v3 onion services, ipv6):
5741 - When v3 onion service clients send introduce cells, they now
5742 include the IPv6 address of the rendezvous point, if it has one.
5743 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
5744 in future Tor versions, IPv6-only v3 single onion services will be
5745 able to use IPv6 addresses to connect directly to the rendezvous
5746 point. Closes ticket 23577. Patch by Neel Chauhan.
5748 o Major bugfixes (onion services, retry behavior):
5749 - Fix an "off by 2" error in counting rendezvous failures on the
5750 onion service side. While we thought we would stop the rendezvous
5751 attempt after one failed circuit, we were actually making three
5752 circuit attempts before giving up. Now switch to a default of 2,
5753 and allow the consensus parameter "hs_service_max_rdv_failures" to
5754 override. Fixes bug 24895; bugfix on 0.0.6.
5755 - New-style (v3) onion services now obey the "max rendezvous circuit
5756 attempts" logic. Previously they would make as many rendezvous
5757 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5758 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5760 o Major bugfixes (relays):
5761 - Fix a set of false positives where relays would consider
5762 connections to other relays as being client-only connections (and
5763 thus e.g. deserving different link padding schemes) if those
5764 relays fell out of the consensus briefly. Now we look only at the
5765 initial handshake and whether the connection authenticated as a
5766 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5768 o Minor feature (IPv6):
5769 - Make IPv6-only clients wait for microdescs for relays, even if we
5770 were previously using descriptors (or were using them as a bridge)
5771 and have a cached descriptor for them. Implements ticket 23827.
5772 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
5773 them, rather than waiting to download microdescriptors.
5774 Implements ticket 23827.
5776 o Minor features (cleanup):
5777 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
5778 when it stops. Closes ticket 23271.
5780 o Minor features (defensive programming):
5781 - Most of the functions in Tor that free objects have been replaced
5782 with macros that free the objects and set the corresponding
5783 pointers to NULL. This change should help prevent a large class of
5784 dangling pointer bugs. Closes ticket 24337.
5785 - Where possible, the tor_free() macro now only evaluates its input
5786 once. Part of ticket 24337.
5787 - Check that microdesc ed25519 ids are non-zero in
5788 node_get_ed25519_id() before returning them. Implements ticket
5789 24001, patch by "aruna1234".
5791 o Minor features (embedding):
5792 - Tor can now start with a preauthenticated control connection
5793 created by the process that launched it. This feature is meant for
5794 use by programs that want to launch and manage a Tor process
5795 without allowing other programs to manage it as well. For more
5796 information, see the __OwningControllerFD option documented in
5797 control-spec.txt. Closes ticket 23900.
5798 - On most errors that would cause Tor to exit, it now tries to
5799 return from the tor_main() function, rather than calling the
5800 system exit() function. Most users won't notice a difference here,
5801 but it should be significant for programs that run Tor inside
5802 a separate thread: they should now be able to survive Tor's exit
5803 conditions rather than having Tor shut down the entire process.
5804 Closes ticket 23848.
5805 - Applications that want to embed Tor can now tell Tor not to
5806 register any of its own POSIX signal handlers, using the
5807 __DisableSignalHandlers option. Closes ticket 24588.
5809 o Minor features (fallback directory list):
5810 - Avoid selecting fallbacks that change their IP addresses too
5811 often. Select more fallbacks by ignoring the Guard flag, and
5812 allowing lower cutoffs for the Running and V2Dir flags. Also allow
5813 a lower bandwidth, and a higher number of fallbacks per operator
5814 (5% of the list). Implements ticket 24785.
5815 - Update the fallback whitelist and blacklist based on opt-ins and
5816 relay changes. Closes tickets 22321, 24678, 22527, 24135,
5819 o Minor features (fallback directory mirror configuration):
5820 - Add a nickname to each fallback in a C comment. This makes it
5821 easier for operators to find their relays, and allows stem to use
5822 nicknames to identify fallbacks. Implements ticket 24600.
5823 - Add a type and version header to the fallback directory mirror
5824 file. Also add a delimiter to the end of each fallback entry. This
5825 helps external parsers like stem and Relay Search. Implements
5827 - Add an extrainfo cache flag for each fallback in a C comment. This
5828 allows stem to use fallbacks to fetch extra-info documents, rather
5829 than using authorities. Implements ticket 22759.
5830 - Add the generateFallbackDirLine.py script for automatically
5831 generating fallback directory mirror lines from relay fingerprints.
5832 No more typos! Add the lookupFallbackDirContact.py script for
5833 automatically looking up operator contact info from relay
5834 fingerprints. Implements ticket 24706, patch by teor and atagar.
5835 - Reject any fallback directory mirror that serves an expired
5836 consensus. Implements ticket 20942, patch by "minik".
5837 - Remove commas and equals signs from external string inputs to the
5838 fallback list. This avoids format confusion attacks. Implements
5840 - Remove the "weight=10" line from fallback directory mirror
5841 entries. Ticket 24681 will maintain the current fallback weights
5842 by changing Tor's default fallback weight to 10. Implements
5844 - Stop logging excessive information about fallback netblocks.
5845 Implements ticket 24791.
5847 o Minor features (forward-compatibility):
5848 - If a relay supports some link authentication protocol that we do
5849 not recognize, then include that relay's ed25519 key when telling
5850 other relays to extend to it. Previously, we treated future
5851 versions as if they were too old to support ed25519 link
5852 authentication. Closes ticket 20895.
5854 o Minor features (heartbeat):
5855 - Add onion service information to our heartbeat logs, displaying
5856 stats about the activity of configured onion services. Closes
5859 o Minor features (instrumentation, development):
5860 - Add the MainloopStats option to allow developers to get
5861 instrumentation information from the main event loop via the
5862 heartbeat messages. We hope to use this to improve Tor's behavior
5863 when it's trying to sleep. Closes ticket 24605.
5865 o Minor features (log messages):
5866 - Improve a warning message that happens when we fail to re-parse an
5867 old router because of an expired certificate. Closes ticket 20020.
5868 - Make the log more quantitative when we hit MaxMemInQueues
5869 threshold exposing some values. Closes ticket 24501.
5871 o Minor features (logging, android):
5872 - Added support for the Android logging subsystem. Closes
5875 o Minor features (performance):
5876 - Support predictive circuit building for onion service circuits
5877 with multiple layers of guards. Closes ticket 23101.
5878 - Use stdatomic.h where available, rather than mutexes, to implement
5879 atomic_counter_t. Closes ticket 23953.
5881 o Minor features (performance, 32-bit):
5882 - Improve performance on 32-bit systems by avoiding 64-bit division
5883 when calculating the timestamp in milliseconds for channel padding
5884 computations. Implements ticket 24613.
5885 - Improve performance on 32-bit systems by avoiding 64-bit division
5886 when timestamping cells and buffer chunks for OOM calculations.
5887 Implements ticket 24374.
5889 o Minor features (performance, OSX, iOS):
5890 - Use the mach_approximate_time() function (when available) to
5891 implement coarse monotonic time. Having a coarse time function
5892 should avoid a large number of system calls, and improve
5893 performance slightly, especially under load. Closes ticket 24427.
5895 o Minor features (performance, windows):
5896 - Improve performance on Windows Vista and Windows 7 by adjusting
5897 TCP send window size according to the recommendation from
5898 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
5901 o Major features (relay):
5902 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
5903 operator to use a more reasonable ("reduced") exit policy, rather
5904 than the default one. If you want to run an exit node without
5905 thinking too hard about which ports to allow, this one is for you.
5906 Closes ticket 13605. Patch from Neel Chauhan.
5908 o Minor features (testing, debugging, embedding):
5909 - For development purposes, Tor now has a mode in which it runs for
5910 a few seconds, then stops, and starts again without exiting the
5911 process. This mode is meant to help us debug various issues with
5912 ticket 23847. To use this feature, compile with
5913 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
5914 environment variable. This is expected to crash a lot, and is
5915 really meant for developers only. It will likely be removed in a
5916 future release. Implements ticket 24583.
5918 o Minor bugfix (network IPv6 test):
5919 - Tor's test scripts now check if "ping -6 ::1" works when the user
5920 runs "make test-network-all". Fixes bug 24677; bugfix on
5921 0.2.9.3-alpha. Patch by "ffmancera".
5923 o Minor bugfixes (build, rust):
5924 - Fix output of autoconf checks to display success messages for Rust
5925 dependencies and a suitable rustc compiler version. Fixes bug
5926 24612; bugfix on 0.3.1.3-alpha.
5927 - When building with Rust on OSX, link against libresolv, to work
5928 around the issue at https://github.com/rust-lang/rust/issues/46797.
5929 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5930 - Don't pass the --quiet option to cargo: it seems to suppress some
5931 errors, which is not what we want to do when building. Fixes bug
5932 24518; bugfix on 0.3.1.7.
5933 - Build correctly when building from outside Tor's source tree with
5934 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
5937 o Minor bugfixes (directory authorities, IPv6):
5938 - When creating a routerstatus (vote) from a routerinfo (descriptor),
5939 set the IPv6 address to the unspecified IPv6 address, and
5940 explicitly initialize the port to zero. Fixes bug 24488; bugfix
5943 o Minor bugfixes (fallback directory mirrors):
5944 - Make updateFallbackDirs.py search harder for python. (Some OSs
5945 don't put it in /usr/bin.) Fixes bug 24708; bugfix
5948 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
5949 - When hibernating, close connections normally and allow them to
5950 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
5952 - Do not attempt to launch self-reachability tests when entering
5953 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5954 - Resolve several bugs related to descriptor fetching on bridge
5955 clients with bandwidth accounting enabled. (This combination is
5956 not recommended!) Fixes a case of bug 12062; bugfix
5958 - When hibernating, do not attempt to launch DNS checks. Fixes a
5959 case of bug 12062; bugfix on 0.1.2.2-alpha.
5960 - When hibernating, do not try to upload or download descriptors.
5961 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5963 o Minor bugfixes (IPv6, bridges):
5964 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
5965 bugfix on 0.2.8.2-alpha.
5966 - Tor now sets IPv6 address in the routerstatus as well as in the
5967 router descriptors when updating addresses for a bridge. Closes
5968 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
5970 o Minor bugfixes (linux seccomp2 sandbox):
5971 - When running with the sandbox enabled, reload configuration files
5972 correctly even when %include was used. Previously we would crash.
5973 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
5975 o Minor bugfixes (memory leaks):
5976 - Avoid possible at-exit memory leaks related to use of Libevent's
5977 event_base_once() function. (This function tends to leak memory if
5978 the event_base is closed before the event fires.) Fixes bug 24584;
5979 bugfix on 0.2.8.1-alpha.
5980 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
5983 o Minor bugfixes (OSX):
5984 - Don't exit the Tor process if setrlimit() fails to change the file
5985 limit (which can happen sometimes on some versions of OSX). Fixes
5986 bug 21074; bugfix on 0.0.9pre5.
5988 o Minor bugfixes (performance, fragile-hardening):
5989 - Improve the performance of our consensus-diff application code
5990 when Tor is built with the --enable-fragile-hardening option set.
5991 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5993 o Minor bugfixes (performance, timeouts):
5994 - Consider circuits for timeout as soon as they complete a hop. This
5995 is more accurate than applying the timeout in
5996 circuit_expire_building() because that function is only called
5997 once per second, which is now too slow for typical timeouts on the
5998 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
5999 - Use onion service circuits (and other circuits longer than 3 hops)
6000 to calculate a circuit build timeout. Previously, Tor only
6001 calculated its build timeout based on circuits that planned to be
6002 exactly 3 hops long. With this change, we include measurements
6003 from all circuits at the point where they complete their third
6004 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
6006 o Minor bugfixes (testing):
6007 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
6008 bugfix on 0.2.3.1-alpha.
6009 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
6010 25005; bugfix on 0.3.2.7-rc.
6012 o Code simplification and refactoring:
6013 - Remove /usr/athena from search path in configure.ac. Closes
6015 - Remove duplicate code in node_has_curve25519_onion_key() and
6016 node_get_curve25519_onion_key(), and add a check for a zero
6017 microdesc curve25519 onion key. Closes ticket 23966, patch by
6018 "aruna1234" and teor.
6019 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
6020 memory allocations with large numbers of OR connections (e.g.
6021 relays). Closes ticket 24119.
6022 - Separate the function that deletes ephemeral files when Tor
6024 - Small changes to Tor's buf_t API to make it suitable for use as a
6025 general-purpose safe string constructor. Closes ticket 22342.
6026 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
6027 avoid source code identifier confusion. Closes ticket 24467.
6028 - The tor_git_revision[] constant no longer needs to be redeclared
6029 by everything that links against the rest of Tor. Done as part of
6030 ticket 23845, to simplify our external API.
6031 - We make extend_info_from_node() use node_get_curve25519_onion_key()
6032 introduced in ticket 23577 to access the curve25519 public keys
6033 rather than accessing it directly. Closes ticket 23760. Patch by
6035 - Add a function to log channels' scheduler state changes to aid
6036 debugging efforts. Closes ticket 24531.
6039 - Add documentation on how to build tor with Rust dependencies
6040 without having to be online. Closes ticket 22907; bugfix
6042 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
6043 traffic. Closes ticket 24318.
6044 - Document that OutboundBindAddress doesn't apply to DNS requests.
6045 Closes ticket 22145. Patch from Aruna Maurya.
6046 - Document that operators who run more than one relay or bridge are
6047 expected to set MyFamily and ContactInfo correctly. Closes
6050 o Code simplification and refactoring (channels):
6051 - Remove the incoming and outgoing channel queues. These were never
6052 used, but still took up a step in our fast path.
6053 - The majority of the channel unit tests have been rewritten and the
6054 code coverage has now been raised to 83.6% for channel.c. Closes
6056 - Remove other dead code from the channel subsystem: All together,
6057 this cleanup has removed more than 1500 lines of code overall and
6058 adding very little except for unit test.
6060 o Code simplification and refactoring (circuit rendezvous):
6061 - Split the client-side rendezvous circuit lookup into two
6062 functions: one that returns only established circuits and another
6063 that returns all kinds of circuits. Closes ticket 23459.
6065 o Code simplification and refactoring (controller):
6066 - Make most of the variables in networkstatus_getinfo_by_purpose()
6067 const. Implements ticket 24489.
6070 Changes in version 0.3.2.9 - 2018-01-09
6071 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
6073 The 0.3.2 series includes our long-anticipated new onion service
6074 design, with numerous security features. (For more information, see
6075 our blog post at https://blog.torproject.org/fall-harvest.) We also
6076 have a new circuit scheduler algorithm for improved performance on
6077 relays everywhere (see https://blog.torproject.org/kist-and-tell),
6078 along with many smaller features and bugfixes.
6080 Per our stable release policy, we plan to support each stable release
6081 series for at least the next nine months, or for three months after
6082 the first stable release of the next series: whichever is longer. If
6083 you need a release with long-term support, we recommend that you stay
6084 with the 0.2.9 series.
6086 Below is a list of the changes since 0.3.2.8-rc. For a list of all
6087 changes since 0.3.1, see the ReleaseNotes file.
6089 o Minor features (fallback directory mirrors):
6090 - The fallback directory list has been re-generated based on the
6091 current status of the network. Tor uses fallback directories to
6092 bootstrap when it doesn't yet have up-to-date directory
6093 information. Closes ticket 24801.
6094 - Make the default DirAuthorityFallbackRate 0.1, so that clients
6095 prefer to bootstrap from fallback directory mirrors. This is a
6096 follow-up to 24679, which removed weights from the default
6097 fallbacks. Implements ticket 24681.
6099 o Minor features (geoip):
6100 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
6103 o Minor bugfixes (address selection):
6104 - When the fascist_firewall_choose_address_ functions don't find a
6105 reachable address, set the returned address to the null address
6106 and port. This is a precautionary measure, because some callers do
6107 not check the return value. Fixes bug 24736; bugfix
6110 o Minor bugfixes (compilation):
6111 - Resolve a few shadowed-variable warnings in the onion service
6112 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
6114 o Minor bugfixes (portability, msvc):
6115 - Fix a bug in the bit-counting parts of our timing-wheel code on
6116 MSVC. (Note that MSVC is still not a supported build platform, due
6117 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
6121 Changes in version 0.3.2.8-rc - 2017-12-21
6122 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
6123 schedulers that had led servers under heavy load to overload their
6124 outgoing connections. All relay operators running earlier 0.3.2.x
6125 versions should upgrade. This version also includes a mitigation for
6126 over-full DESTROY queues leading to out-of-memory conditions: if it
6127 works, we will soon backport it to earlier release series.
6129 This is the second release candidate in the 0.3.2 series. If we find
6130 no new bugs or regression here, then the first stable 0.3.2 release
6131 will be nearly identical to this.
6133 o Major bugfixes (KIST, scheduler):
6134 - The KIST scheduler did not correctly account for data already
6135 enqueued in each connection's send socket buffer, particularly in
6136 cases when the TCP/IP congestion window was reduced between
6137 scheduler calls. This situation lead to excessive per-connection
6138 buffering in the kernel, and a potential memory DoS. Fixes bug
6139 24665; bugfix on 0.3.2.1-alpha.
6141 o Minor features (geoip):
6142 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
6145 o Minor bugfixes (hidden service v3):
6146 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
6147 the probability of reaching a service for a client missing
6148 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
6150 o Minor bugfixes (memory usage):
6151 - When queuing DESTROY cells on a channel, only queue the circuit-id
6152 and reason fields: not the entire 514-byte cell. This fix should
6153 help mitigate any bugs or attacks that fill up these queues, and
6154 free more RAM for other uses. Fixes bug 24666; bugfix
6157 o Minor bugfixes (scheduler, KIST):
6158 - Use a sane write limit for KISTLite when writing onto a connection
6159 buffer instead of using INT_MAX and shoving as much as it can.
6160 Because the OOM handler cleans up circuit queues, we are better
6161 off at keeping them in that queue instead of the connection's
6162 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
6165 Changes in version 0.3.2.7-rc - 2017-12-14
6166 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
6167 including some that could affect reliability or correctness.
6169 This is the first release candidate in the 0.3.2 series. If we find no
6170 new bugs or regression here, then the first stable 0.3.2. release will
6171 be nearly identical to this.
6173 o Major bugfixes (circuit prediction):
6174 - Fix circuit prediction logic so that a client doesn't treat a port
6175 as being "handled" by a circuit if that circuit already has
6176 isolation settings on it. This change should make Tor clients more
6177 responsive by improving their chances of having a pre-created
6178 circuit ready for use when a request arrives. Fixes bug 18859;
6179 bugfix on 0.2.3.3-alpha.
6181 o Minor features (logging):
6182 - Provide better warnings when the getrandom() syscall fails. Closes
6185 o Minor features (portability):
6186 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
6187 (It doesn't yet work with the sandbox enabled.) Closes
6190 o Minor bugfixes (bridge clients, bootstrap):
6191 - Retry directory downloads when we get our first bridge descriptor
6192 during bootstrap or while reconnecting to the network. Keep
6193 retrying every time we get a bridge descriptor, until we have a
6194 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
6195 - Stop delaying bridge descriptor fetches when we have cached bridge
6196 descriptors. Instead, only delay bridge descriptor fetches when we
6197 have at least one reachable bridge. Fixes part of bug 24367;
6198 bugfix on 0.2.0.3-alpha.
6199 - Stop delaying directory fetches when we have cached bridge
6200 descriptors. Instead, only delay bridge descriptor fetches when
6201 all our bridges are definitely unreachable. Fixes part of bug
6202 24367; bugfix on 0.2.0.3-alpha.
6204 o Minor bugfixes (compilation):
6205 - Fix a signed/unsigned comparison warning introduced by our fix to
6206 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
6208 o Minor bugfixes (correctness):
6209 - Fix several places in our codebase where a C compiler would be
6210 likely to eliminate a check, based on assuming that undefined
6211 behavior had not happened elsewhere in the code. These cases are
6212 usually a sign of redundant checking or dubious arithmetic. Found
6213 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
6214 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
6217 o Minor bugfixes (onion service v3):
6218 - Fix a race where an onion service would launch a new intro circuit
6219 after closing an old one, but fail to register it before freeing
6220 the previously closed circuit. This bug was making the service
6221 unable to find the established intro circuit and thus not upload
6222 its descriptor, thus making a service unavailable for up to 24
6223 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
6225 o Minor bugfixes (scheduler, KIST):
6226 - Properly set the scheduler state of an unopened channel in the
6227 KIST scheduler main loop. This prevents a harmless but annoying
6228 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
6229 - Avoid a possible integer overflow when computing the available
6230 space on the TCP buffer of a channel. This had no security
6231 implications; but could make KIST allow too many cells on a
6232 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
6233 - Downgrade to "info" a harmless warning about the monotonic time
6234 moving backwards: This can happen on platform not supporting
6235 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
6238 Changes in version 0.3.2.6-alpha - 2017-12-01
6239 This version of Tor is the latest in the 0.3.2 alpha series. It
6240 includes fixes for several important security issues. All Tor users
6241 should upgrade to this release, or to one of the other releases coming
6244 o Major bugfixes (security):
6245 - Fix a denial of service bug where an attacker could use a
6246 malformed directory object to cause a Tor instance to pause while
6247 OpenSSL would try to read a passphrase from the terminal. (Tor
6248 instances run without a terminal, which is the case for most Tor
6249 packages, are not impacted.) Fixes bug 24246; bugfix on every
6250 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6251 Found by OSS-Fuzz as testcase 6360145429790720.
6252 - Fix a denial of service issue where an attacker could crash a
6253 directory authority using a malformed router descriptor. Fixes bug
6254 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6256 - When checking for replays in the INTRODUCE1 cell data for a
6257 (legacy) onion service, correctly detect replays in the RSA-
6258 encrypted part of the cell. We were previously checking for
6259 replays on the entire cell, but those can be circumvented due to
6260 the malleability of Tor's legacy hybrid encryption. This fix helps
6261 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6262 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6265 o Major bugfixes (security, onion service v2):
6266 - Fix a use-after-free error that could crash v2 Tor onion services
6267 when they failed to open circuits while expiring introduction
6268 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6269 also tracked as TROVE-2017-013 and CVE-2017-8823.
6271 o Major bugfixes (security, relay):
6272 - When running as a relay, make sure that we never build a path
6273 through ourselves, even in the case where we have somehow lost the
6274 version of our descriptor appearing in the consensus. Fixes part
6275 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6276 as TROVE-2017-012 and CVE-2017-8822.
6277 - When running as a relay, make sure that we never choose ourselves
6278 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6279 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6281 o Minor feature (relay statistics):
6282 - Change relay bandwidth reporting stats interval from 4 hours to 24
6283 hours in order to reduce the efficiency of guard discovery
6284 attacks. Fixes ticket 23856.
6286 o Minor features (directory authority):
6287 - Add an IPv6 address for the "bastet" directory authority. Closes
6290 o Minor bugfixes (client):
6291 - By default, do not enable storage of client-side DNS values. These
6292 values were unused by default previously, but they should not have
6293 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
6296 Changes in version 0.3.1.9 - 2017-12-01:
6297 Tor 0.3.1.9 backports important security and stability fixes from the
6298 0.3.2 development series. All Tor users should upgrade to this
6299 release, or to another of the releases coming out today.
6301 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6302 - Fix a denial of service bug where an attacker could use a
6303 malformed directory object to cause a Tor instance to pause while
6304 OpenSSL would try to read a passphrase from the terminal. (Tor
6305 instances run without a terminal, which is the case for most Tor
6306 packages, are not impacted.) Fixes bug 24246; bugfix on every
6307 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6308 Found by OSS-Fuzz as testcase 6360145429790720.
6309 - Fix a denial of service issue where an attacker could crash a
6310 directory authority using a malformed router descriptor. Fixes bug
6311 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6313 - When checking for replays in the INTRODUCE1 cell data for a
6314 (legacy) onion service, correctly detect replays in the RSA-
6315 encrypted part of the cell. We were previously checking for
6316 replays on the entire cell, but those can be circumvented due to
6317 the malleability of Tor's legacy hybrid encryption. This fix helps
6318 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6319 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6322 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6323 - Fix a use-after-free error that could crash v2 Tor onion services
6324 when they failed to open circuits while expiring introduction
6325 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6326 also tracked as TROVE-2017-013 and CVE-2017-8823.
6328 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6329 - When running as a relay, make sure that we never build a path
6330 through ourselves, even in the case where we have somehow lost the
6331 version of our descriptor appearing in the consensus. Fixes part
6332 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6333 as TROVE-2017-012 and CVE-2017-8822.
6334 - When running as a relay, make sure that we never choose ourselves
6335 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6336 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6338 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6339 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6340 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6341 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6342 identifying and finding a workaround to this bug and to Moritz,
6343 Arthur Edelstein, and Roger for helping to track it down and
6346 o Minor features (bridge):
6347 - Bridges now include notice in their descriptors that they are
6348 bridges, and notice of their distribution status, based on their
6349 publication settings. Implements ticket 18329. For more fine-
6350 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6353 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6354 - Add an IPv6 address for the "bastet" directory authority. Closes
6357 o Minor features (geoip):
6358 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6361 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6362 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6363 relays, to prevent spurious address resolutions and descriptor
6364 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6365 bugfix on in 0.2.8.1-alpha.
6367 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6368 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6369 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6371 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6372 - When a circuit is marked for close, do not attempt to package any
6373 cells for channels on that circuit. Previously, we would detect
6374 this condition lower in the call stack, when we noticed that the
6375 circuit had no attached channel, and log an annoying message.
6376 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6378 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
6379 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6380 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6383 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6384 - Avoid a crash when transitioning from client mode to bridge mode.
6385 Previously, we would launch the worker threads whenever our
6386 "public server" mode changed, but not when our "server" mode
6387 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6390 Changes in version 0.3.0.13 - 2017-12-01
6391 Tor 0.3.0.13 backports important security and stability bugfixes from
6392 later Tor releases. All Tor users should upgrade to this release, or
6393 to another of the releases coming out today.
6395 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6396 2018. If you need a release with long-term support, please stick with
6397 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6399 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6400 - Fix a denial of service bug where an attacker could use a
6401 malformed directory object to cause a Tor instance to pause while
6402 OpenSSL would try to read a passphrase from the terminal. (Tor
6403 instances run without a terminal, which is the case for most Tor
6404 packages, are not impacted.) Fixes bug 24246; bugfix on every
6405 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6406 Found by OSS-Fuzz as testcase 6360145429790720.
6407 - Fix a denial of service issue where an attacker could crash a
6408 directory authority using a malformed router descriptor. Fixes bug
6409 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6411 - When checking for replays in the INTRODUCE1 cell data for a
6412 (legacy) onion service, correctly detect replays in the RSA-
6413 encrypted part of the cell. We were previously checking for
6414 replays on the entire cell, but those can be circumvented due to
6415 the malleability of Tor's legacy hybrid encryption. This fix helps
6416 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6417 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6420 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6421 - Fix a use-after-free error that could crash v2 Tor onion services
6422 when they failed to open circuits while expiring introduction
6423 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6424 also tracked as TROVE-2017-013 and CVE-2017-8823.
6426 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6427 - When running as a relay, make sure that we never build a path
6428 through ourselves, even in the case where we have somehow lost the
6429 version of our descriptor appearing in the consensus. Fixes part
6430 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6431 as TROVE-2017-012 and CVE-2017-8822.
6432 - When running as a relay, make sure that we never choose ourselves
6433 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6434 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6436 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6437 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6438 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6439 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6440 identifying and finding a workaround to this bug and to Moritz,
6441 Arthur Edelstein, and Roger for helping to track it down and
6444 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6445 - Enable a couple of pieces of Windows hardening: one
6446 (HeapEnableTerminationOnCorruption) that has been on-by-default
6447 since Windows 8, and unavailable before Windows 7; and one
6448 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6449 affect us, but shouldn't do any harm. Closes ticket 21953.
6451 o Minor features (bridge, backport from 0.3.1.9):
6452 - Bridges now include notice in their descriptors that they are
6453 bridges, and notice of their distribution status, based on their
6454 publication settings. Implements ticket 18329. For more fine-
6455 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6458 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6459 - Add an IPv6 address for the "bastet" directory authority. Closes
6462 o Minor features (geoip):
6463 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6466 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6467 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6468 relays, to prevent spurious address resolutions and descriptor
6469 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6470 bugfix on in 0.2.8.1-alpha.
6472 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6473 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6474 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6476 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6477 - When a circuit is marked for close, do not attempt to package any
6478 cells for channels on that circuit. Previously, we would detect
6479 this condition lower in the call stack, when we noticed that the
6480 circuit had no attached channel, and log an annoying message.
6481 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6483 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6484 - Avoid a crash when transitioning from client mode to bridge mode.
6485 Previously, we would launch the worker threads whenever our
6486 "public server" mode changed, but not when our "server" mode
6487 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6489 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6490 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6491 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6494 Changes in version 0.2.9.14 - 2017-12-01
6495 Tor 0.3.0.13 backports important security and stability bugfixes from
6496 later Tor releases. All Tor users should upgrade to this release, or
6497 to another of the releases coming out today.
6499 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6500 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6501 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6502 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6503 identifying and finding a workaround to this bug and to Moritz,
6504 Arthur Edelstein, and Roger for helping to track it down and
6507 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6508 - Fix a denial of service bug where an attacker could use a
6509 malformed directory object to cause a Tor instance to pause while
6510 OpenSSL would try to read a passphrase from the terminal. (Tor
6511 instances run without a terminal, which is the case for most Tor
6512 packages, are not impacted.) Fixes bug 24246; bugfix on every
6513 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6514 Found by OSS-Fuzz as testcase 6360145429790720.
6515 - Fix a denial of service issue where an attacker could crash a
6516 directory authority using a malformed router descriptor. Fixes bug
6517 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6519 - When checking for replays in the INTRODUCE1 cell data for a
6520 (legacy) onion service, correctly detect replays in the RSA-
6521 encrypted part of the cell. We were previously checking for
6522 replays on the entire cell, but those can be circumvented due to
6523 the malleability of Tor's legacy hybrid encryption. This fix helps
6524 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6525 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6528 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6529 - Fix a use-after-free error that could crash v2 Tor onion services
6530 when they failed to open circuits while expiring introduction
6531 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6532 also tracked as TROVE-2017-013 and CVE-2017-8823.
6534 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6535 - When running as a relay, make sure that we never build a path
6536 through ourselves, even in the case where we have somehow lost the
6537 version of our descriptor appearing in the consensus. Fixes part
6538 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6539 as TROVE-2017-012 and CVE-2017-8822.
6541 o Minor features (bridge, backport from 0.3.1.9):
6542 - Bridges now include notice in their descriptors that they are
6543 bridges, and notice of their distribution status, based on their
6544 publication settings. Implements ticket 18329. For more fine-
6545 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6548 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6549 - Add an IPv6 address for the "bastet" directory authority. Closes
6552 o Minor features (geoip):
6553 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6556 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6557 - Enable a couple of pieces of Windows hardening: one
6558 (HeapEnableTerminationOnCorruption) that has been on-by-default
6559 since Windows 8, and unavailable before Windows 7; and one
6560 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6561 affect us, but shouldn't do any harm. Closes ticket 21953.
6563 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6564 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6565 relays, to prevent spurious address resolutions and descriptor
6566 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6567 bugfix on in 0.2.8.1-alpha.
6569 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6570 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6571 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6573 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6574 - When a circuit is marked for close, do not attempt to package any
6575 cells for channels on that circuit. Previously, we would detect
6576 this condition lower in the call stack, when we noticed that the
6577 circuit had no attached channel, and log an annoying message.
6578 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6580 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6581 - Avoid a crash when transitioning from client mode to bridge mode.
6582 Previously, we would launch the worker threads whenever our
6583 "public server" mode changed, but not when our "server" mode
6584 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6586 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6587 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6588 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6591 Changes in version 0.2.8.17 - 2017-12-01
6592 Tor 0.2.8.17 backports important security and stability bugfixes from
6593 later Tor releases. All Tor users should upgrade to this release, or
6594 to another of the releases coming out today.
6596 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6597 2018. If you need a release with long-term support, please upgrade with
6598 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6600 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6601 - Fix a denial of service bug where an attacker could use a
6602 malformed directory object to cause a Tor instance to pause while
6603 OpenSSL would try to read a passphrase from the terminal. (Tor
6604 instances run without a terminal, which is the case for most Tor
6605 packages, are not impacted.) Fixes bug 24246; bugfix on every
6606 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6607 Found by OSS-Fuzz as testcase 6360145429790720.
6608 - When checking for replays in the INTRODUCE1 cell data for a
6609 (legacy) onion service, correctly detect replays in the RSA-
6610 encrypted part of the cell. We were previously checking for
6611 replays on the entire cell, but those can be circumvented due to
6612 the malleability of Tor's legacy hybrid encryption. This fix helps
6613 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6614 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6617 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6618 - Fix a use-after-free error that could crash v2 Tor onion services
6619 when they failed to open circuits while expiring introduction
6620 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6621 also tracked as TROVE-2017-013 and CVE-2017-8823.
6623 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6624 - When running as a relay, make sure that we never build a path through
6625 ourselves, even in the case where we have somehow lost the version of
6626 our descriptor appearing in the consensus. Fixes part of bug 21534;
6627 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
6630 o Minor features (bridge, backport from 0.3.1.9):
6631 - Bridges now include notice in their descriptors that they are
6632 bridges, and notice of their distribution status, based on their
6633 publication settings. Implements ticket 18329. For more fine-
6634 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6637 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6638 - Add an IPv6 address for the "bastet" directory authority. Closes
6641 o Minor features (geoip):
6642 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6645 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6646 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6647 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6650 Changes in version 0.2.5.16 - 2017-12-01
6651 Tor 0.2.5.13 backports important security and stability bugfixes from
6652 later Tor releases. All Tor users should upgrade to this release, or
6653 to another of the releases coming out today.
6655 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6656 2018. If you need a release with long-term support, please upgrade to
6657 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6659 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6660 - Fix a denial of service bug where an attacker could use a
6661 malformed directory object to cause a Tor instance to pause while
6662 OpenSSL would try to read a passphrase from the terminal. (Tor
6663 instances run without a terminal, which is the case for most Tor
6664 packages, are not impacted.) Fixes bug 24246; bugfix on every
6665 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6666 Found by OSS-Fuzz as testcase 6360145429790720.
6667 - When checking for replays in the INTRODUCE1 cell data for a
6668 (legacy) onion service, correctly detect replays in the RSA-
6669 encrypted part of the cell. We were previously checking for
6670 replays on the entire cell, but those can be circumvented due to
6671 the malleability of Tor's legacy hybrid encryption. This fix helps
6672 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6673 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6676 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6677 - When running as a relay, make sure that we never build a path
6678 through ourselves, even in the case where we have somehow lost the
6679 version of our descriptor appearing in the consensus. Fixes part
6680 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6681 as TROVE-2017-012 and CVE-2017-8822.
6683 o Minor features (bridge, backport from 0.3.1.9):
6684 - Bridges now include notice in their descriptors that they are
6685 bridges, and notice of their distribution status, based on their
6686 publication settings. Implements ticket 18329. For more fine-
6687 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6690 o Minor features (geoip):
6691 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6695 Changes in version 0.3.2.5-alpha - 2017-11-22
6696 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
6697 fixes several stability and reliability bugs, including a fix for
6698 intermittent bootstrapping failures that some people have been seeing
6699 since the 0.3.0.x series.
6701 Please test this alpha out -- many of these fixes will soon be
6702 backported to stable Tor versions if no additional bugs are found
6705 o Major bugfixes (bootstrapping):
6706 - Fetch descriptors aggressively whenever we lack enough to build
6707 circuits, regardless of how many descriptors we are missing.
6708 Previously, we would delay launching the fetch when we had fewer
6709 than 15 missing descriptors, even if some of those descriptors
6710 were blocking circuits from building. Fixes bug 23985; bugfix on
6711 0.1.1.11-alpha. The effects of this bug became worse in
6712 0.3.0.3-alpha, when we began treating missing descriptors from our
6713 primary guards as a reason to delay circuits.
6714 - Don't try fetching microdescriptors from relays that have failed
6715 to deliver them in the past. Fixes bug 23817; bugfix
6718 o Minor features (directory authority):
6719 - Make the "Exit" flag assignment only depend on whether the exit
6720 policy allows connections to ports 80 and 443. Previously relays
6721 would get the Exit flag if they allowed connections to one of
6722 these ports and also port 6667. Resolves ticket 23637.
6724 o Minor features (geoip):
6725 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6728 o Minor features (linux seccomp2 sandbox):
6729 - Update the sandbox rules so that they should now work correctly
6730 with Glibc 2.26. Closes ticket 24315.
6732 o Minor features (logging):
6733 - Downgrade a pair of log messages that could occur when an exit's
6734 resolver gave us an unusual (but not forbidden) response. Closes
6736 - Improve the message we log when re-enabling circuit build timeouts
6737 after having received a consensus. Closes ticket 20963.
6739 o Minor bugfixes (compilation):
6740 - Fix a memory leak warning in one of the libevent-related
6741 configuration tests that could occur when manually specifying
6742 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
6743 Found and patched by Alex Xu.
6744 - When detecting OpenSSL on Windows from our configure script, make
6745 sure to try linking with the ws2_32 library. Fixes bug 23783;
6746 bugfix on 0.3.2.2-alpha.
6748 o Minor bugfixes (control port, linux seccomp2 sandbox):
6749 - Avoid a crash when attempting to use the seccomp2 sandbox together
6750 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
6753 o Minor bugfixes (control port, onion services):
6754 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
6755 HS_DESC event when a service is not able to upload a descriptor.
6756 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
6758 o Minor bugfixes (directory cache):
6759 - Recover better from empty or corrupt files in the consensus cache
6760 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
6761 - When a consensus diff calculation is only partially successful,
6762 only record the successful parts as having succeeded. Partial
6763 success can happen if (for example) one compression method fails
6764 but the others succeed. Previously we misrecorded all the
6765 calculations as having succeeded, which would later cause a
6766 nonfatal assertion failure. Fixes bug 24086; bugfix
6769 o Minor bugfixes (logging):
6770 - Only log once if we notice that KIST support is gone. Fixes bug
6771 24158; bugfix on 0.3.2.1-alpha.
6772 - Suppress a log notice when relay descriptors arrive. We already
6773 have a bootstrap progress for this so no need to log notice
6774 everytime tor receives relay descriptors. Microdescriptors behave
6775 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
6777 o Minor bugfixes (network layer):
6778 - When closing a connection via close_connection_immediately(), we
6779 mark it as "not blocked on bandwidth", to prevent later calls from
6780 trying to unblock it, and give it permission to read. This fixes a
6781 backtrace warning that can happen on relays under various
6782 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
6784 o Minor bugfixes (onion services):
6785 - The introduction circuit was being timed out too quickly while
6786 waiting for the rendezvous circuit to complete. Keep the intro
6787 circuit around longer instead of timing out and reopening new ones
6788 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
6789 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6790 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6792 - Silence a warning about failed v3 onion descriptor uploads that
6793 can happen naturally under certain edge cases. Fixes part of bug
6794 23662; bugfix on 0.3.2.1-alpha.
6796 o Minor bugfixes (tests):
6797 - Fix a memory leak in one of the bridge-distribution test cases.
6798 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
6799 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
6800 to correctly handle cases where a caller gives it an RSA key of
6801 under 160 bits. (This is not actually a bug in Tor itself, but
6802 rather in our fuzzing code.) Fixes bug 24247; bugfix on
6803 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
6806 - Add notes in man page regarding OS support for the various
6807 scheduler types. Attempt to use less jargon in the scheduler
6808 section. Closes ticket 24254.
6811 Changes in version 0.3.2.4-alpha - 2017-11-08
6812 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
6813 It fixes several stability and reliability bugs, especially including
6814 a major reliability issue that has been plaguing fast exit relays in
6817 o Major bugfixes (exit relays, DNS):
6818 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6819 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6820 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6821 identifying and finding a workaround to this bug and to Moritz,
6822 Arthur Edelstein, and Roger for helping to track it down and
6825 o Major bugfixes (scheduler, channel):
6826 - Stop processing scheduled channels if they closed while flushing
6827 cells. This can happen if the write on the connection fails
6828 leading to the channel being closed while in the scheduler loop.
6829 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
6831 o Minor features (logging, scheduler):
6832 - Introduce a SCHED_BUG() function to log extra information about
6833 the scheduler state if we ever catch a bug in the scheduler.
6834 Closes ticket 23753.
6836 o Minor features (removed deprecations):
6837 - The ClientDNSRejectInternalAddresses flag can once again be set in
6838 non-testing Tor networks, so long as they do not use the default
6839 directory authorities. This change also removes the deprecation of
6840 this flag from 0.2.9.2-alpha. Closes ticket 21031.
6842 o Minor features (testing):
6843 - Our fuzzing tests now test the encrypted portions of v3 onion
6844 service descriptors. Implements more of 21509.
6846 o Minor bugfixes (directory client):
6847 - On failure to download directory information, delay retry attempts
6848 by a random amount based on the "decorrelated jitter" algorithm.
6849 Our previous delay algorithm tended to produce extra-long delays
6850 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
6852 o Minor bugfixes (IPv6, v3 single onion services):
6853 - Remove buggy code for IPv6-only v3 single onion services, and
6854 reject attempts to configure them. This release supports IPv4,
6855 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
6856 stack v3 single onion services. Fixes bug 23820; bugfix
6859 o Minor bugfixes (logging, relay):
6860 - Give only a protocol warning when the ed25519 key is not
6861 consistent between the descriptor and microdescriptor of a relay.
6862 This can happen, for instance, if the relay has been flagged
6863 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
6865 o Minor bugfixes (manpage, onion service):
6866 - Document that the HiddenServiceNumIntroductionPoints option is
6867 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
6868 bugfix on 0.3.2.1-alpha.
6870 o Minor bugfixes (memory leaks):
6871 - Fix a minor memory leak at exit in the KIST scheduler. This bug
6872 should have no user-visible impact. Fixes bug 23774; bugfix
6874 - Fix a memory leak when decrypting a badly formatted v3 onion
6875 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
6876 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
6878 o Minor bugfixes (onion services):
6879 - Cache some needed onion service client information instead of
6880 constantly computing it over and over again. Fixes bug 23623;
6881 bugfix on 0.3.2.1-alpha.
6882 - Properly retry HSv3 descriptor fetches when missing required
6883 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
6885 o Minor bugfixes (path selection):
6886 - When selecting relays by bandwidth, avoid a rounding error that
6887 could sometimes cause load to be imbalanced incorrectly.
6888 Previously, we would always round upwards; now, we round towards
6889 the nearest integer. This had the biggest effect when a relay's
6890 weight adjustments should have given it weight 0, but it got
6891 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
6892 - When calculating the fraction of nodes that have descriptors, and
6893 all nodes in the network have zero bandwidths, count the number of
6894 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
6895 - Actually log the total bandwidth in compute_weighted_bandwidths().
6896 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
6898 o Minor bugfixes (relay, crash):
6899 - Avoid a crash when transitioning from client mode to bridge mode.
6900 Previously, we would launch the worker threads whenever our
6901 "public server" mode changed, but not when our "server" mode
6902 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6904 o Minor bugfixes (testing):
6905 - Fix a spurious fuzzing-only use of an uninitialized value. Found
6906 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
6907 - Test that IPv6-only clients can use microdescriptors when running
6908 "make test-network-all". Requires chutney master 61c28b9 or later.
6909 Closes ticket 24109.
6912 Changes in version 0.3.2.3-alpha - 2017-10-27
6913 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
6914 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
6915 directory authority, Bastet.
6917 o Directory authority changes:
6918 - Add "Bastet" as a ninth directory authority to the default list.
6919 Closes ticket 23910.
6920 - The directory authority "Longclaw" has changed its IP address.
6921 Closes ticket 23592.
6923 o Minor features (bridge):
6924 - Bridge relays can now set the BridgeDistribution config option to
6925 add a "bridge-distribution-request" line to their bridge
6926 descriptor, which tells BridgeDB how they'd like their bridge
6927 address to be given out. (Note that as of Oct 2017, BridgeDB does
6928 not yet implement this feature.) As a side benefit, this feature
6929 provides a way to distinguish bridge descriptors from non-bridge
6930 descriptors. Implements tickets 18329.
6932 o Minor features (client, entry guards):
6933 - Improve log messages when missing descriptors for primary guards.
6934 Resolves ticket 23670.
6936 o Minor features (geoip):
6937 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6940 o Minor bugfixes (bridge):
6941 - Overwrite the bridge address earlier in the process of retrieving
6942 its descriptor, to make sure we reach it on the configured
6943 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
6945 o Minor bugfixes (documentation):
6946 - Document better how to read gcov, and what our gcov postprocessing
6947 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
6949 o Minor bugfixes (entry guards):
6950 - Tor now updates its guard state when it reads a consensus
6951 regardless of whether it's missing descriptors. That makes tor use
6952 its primary guards to fetch descriptors in some edge cases where
6953 it would previously have used fallback directories. Fixes bug
6954 23862; bugfix on 0.3.0.1-alpha.
6956 o Minor bugfixes (hidden service client):
6957 - When handling multiple SOCKS request for the same .onion address,
6958 only fetch the service descriptor once.
6959 - When a descriptor fetch fails with a non-recoverable error, close
6960 all pending SOCKS requests for that .onion. Fixes bug 23653;
6961 bugfix on 0.3.2.1-alpha.
6963 o Minor bugfixes (hidden service):
6964 - Always regenerate missing hidden service public key files. Prior
6965 to this, if the public key was deleted from disk, it wouldn't get
6966 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
6968 - Make sure that we have a usable ed25519 key when the intro point
6969 relay supports ed25519 link authentication. Fixes bug 24002;
6970 bugfix on 0.3.2.1-alpha.
6972 o Minor bugfixes (hidden service, v2):
6973 - When reloading configured hidden services, copy all information
6974 from the old service object. Previously, some data was omitted,
6975 causing delays in descriptor upload, and other bugs. Fixes bug
6976 23790; bugfix on 0.2.1.9-alpha.
6978 o Minor bugfixes (memory safety, defensive programming):
6979 - Clear the target address when node_get_prim_orport() returns
6980 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6982 o Minor bugfixes (relay):
6983 - Avoid a BUG warning when receiving a dubious CREATE cell while an
6984 option transition is in progress. Fixes bug 23952; bugfix
6987 o Minor bugfixes (testing):
6988 - Adjust the GitLab CI configuration to more closely match that of
6989 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
6990 - Prevent scripts/test/coverage from attempting to move gcov output
6991 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
6992 - When running unit tests as root, skip a test that would fail
6993 because it expects a permissions error. This affects some
6994 continuous integration setups. Fixes bug 23758; bugfix
6996 - Stop unconditionally mirroring the tor repository in GitLab CI.
6997 This prevented developers from enabling GitLab CI on master. Fixes
6998 bug 23755; bugfix on 0.3.2.2-alpha.
6999 - Fix the hidden service v3 descriptor decoding fuzzing to use the
7000 latest decoding API correctly. Fixes bug 21509; bugfix
7003 o Minor bugfixes (warnings):
7004 - When we get an HTTP request on a SOCKS port, tell the user about
7005 the new HTTPTunnelPort option. Previously, we would give a "Tor is
7006 not an HTTP Proxy" message, which stopped being true when
7007 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
7011 Changes in version 0.2.5.15 - 2017-10-25
7012 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
7013 series. It also adds a new directory authority, Bastet.
7015 Note: the Tor 0.2.5 series will no longer be supported after 1 May
7016 2018. If you need a release with long-term support, please upgrade to
7017 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7019 o Directory authority changes:
7020 - Add "Bastet" as a ninth directory authority to the default list.
7021 Closes ticket 23910.
7022 - The directory authority "Longclaw" has changed its IP address.
7023 Closes ticket 23592.
7025 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7026 - Avoid an assertion failure bug affecting our implementation of
7027 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7028 handling of "0xx" differs from what we had expected. Fixes bug
7029 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7031 o Minor features (geoip):
7032 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7035 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7036 - Fix a memset() off the end of an array when packing cells. This
7037 bug should be harmless in practice, since the corrupted bytes are
7038 still in the same structure, and are always padding bytes,
7039 ignored, or immediately overwritten, depending on compiler
7040 behavior. Nevertheless, because the memset()'s purpose is to make
7041 sure that any other cell-handling bugs can't expose bytes to the
7042 network, we need to fix it. Fixes bug 22737; bugfix on
7043 0.2.4.11-alpha. Fixes CID 1401591.
7045 o Build features (backport from 0.3.1.5-alpha):
7046 - Tor's repository now includes a Travis Continuous Integration (CI)
7047 configuration file (.travis.yml). This is meant to help new
7048 developers and contributors who fork Tor to a Github repository be
7049 better able to test their changes, and understand what we expect
7050 to pass. To use this new build feature, you must fork Tor to your
7051 Github account, then go into the "Integrations" menu in the
7052 repository settings for your fork and enable Travis, then push
7053 your changes. Closes ticket 22636.
7056 Changes in version 0.2.8.16 - 2017-10-25
7057 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
7058 series, including a bugfix for a crash issue that had affected relays
7059 under memory pressure. It also adds a new directory authority, Bastet.
7061 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
7062 2018. If you need a release with long-term support, please stick with
7063 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7065 o Directory authority changes:
7066 - Add "Bastet" as a ninth directory authority to the default list.
7067 Closes ticket 23910.
7068 - The directory authority "Longclaw" has changed its IP address.
7069 Closes ticket 23592.
7071 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7072 - Fix a timing-based assertion failure that could occur when the
7073 circuit out-of-memory handler freed a connection's output buffer.
7074 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7076 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7077 - Remove longclaw's IPv6 address, as it will soon change. Authority
7078 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7079 3/8 directory authorities with IPv6 addresses, but there are also
7080 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7082 o Minor features (geoip):
7083 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7087 Changes in version 0.2.9.13 - 2017-10-25
7088 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
7089 series, including a bugfix for a crash issue that had affected relays
7090 under memory pressure. It also adds a new directory authority, Bastet.
7092 o Directory authority changes:
7093 - Add "Bastet" as a ninth directory authority to the default list.
7094 Closes ticket 23910.
7095 - The directory authority "Longclaw" has changed its IP address.
7096 Closes ticket 23592.
7098 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7099 - Fix a timing-based assertion failure that could occur when the
7100 circuit out-of-memory handler freed a connection's output buffer.
7101 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7103 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7104 - Remove longclaw's IPv6 address, as it will soon change. Authority
7105 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7106 3/8 directory authorities with IPv6 addresses, but there are also
7107 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7109 o Minor features (geoip):
7110 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7113 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
7114 - When a directory authority rejects a descriptor or extrainfo with
7115 a given digest, mark that digest as undownloadable, so that we do
7116 not attempt to download it again over and over. We previously
7117 tried to avoid downloading such descriptors by other means, but we
7118 didn't notice if we accidentally downloaded one anyway. This
7119 behavior became problematic in 0.2.7.2-alpha, when authorities
7120 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7123 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7124 - Clear the address when node_get_prim_orport() returns early.
7125 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7127 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7128 - When running as a Windows service, set the ID of the main thread
7129 correctly. Failure to do so made us fail to send log messages to
7130 the controller in 0.2.1.16-rc, slowed down controller event
7131 delivery in 0.2.7.3-rc and later, and crash with an assertion
7132 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7133 Patch and diagnosis from "Vort".
7136 Changes in version 0.3.0.12 - 2017-10-25
7137 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
7138 series, including a bugfix for a crash issue that had affected relays
7139 under memory pressure. It also adds a new directory authority, Bastet.
7141 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
7142 2018. If you need a release with long-term support, please stick with
7143 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7145 o Directory authority changes:
7146 - Add "Bastet" as a ninth directory authority to the default list.
7147 Closes ticket 23910.
7148 - The directory authority "Longclaw" has changed its IP address.
7149 Closes ticket 23592.
7151 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7152 - Fix a timing-based assertion failure that could occur when the
7153 circuit out-of-memory handler freed a connection's output buffer.
7154 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7156 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7157 - Remove longclaw's IPv6 address, as it will soon change. Authority
7158 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7159 3/8 directory authorities with IPv6 addresses, but there are also
7160 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7162 o Minor features (geoip):
7163 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7166 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
7167 - When a directory authority rejects a descriptor or extrainfo with
7168 a given digest, mark that digest as undownloadable, so that we do
7169 not attempt to download it again over and over. We previously
7170 tried to avoid downloading such descriptors by other means, but we
7171 didn't notice if we accidentally downloaded one anyway. This
7172 behavior became problematic in 0.2.7.2-alpha, when authorities
7173 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7176 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7177 - Avoid a possible double close of a circuit by the intro point on
7178 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7179 bugfix on 0.3.0.1-alpha.
7181 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7182 - Clear the address when node_get_prim_orport() returns early.
7183 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7185 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7186 - When running as a Windows service, set the ID of the main thread
7187 correctly. Failure to do so made us fail to send log messages to
7188 the controller in 0.2.1.16-rc, slowed down controller event
7189 delivery in 0.2.7.3-rc and later, and crash with an assertion
7190 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7191 Patch and diagnosis from "Vort".
7194 Changes in version 0.3.1.8 - 2017-10-25
7195 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
7196 It includes several bugfixes, including a bugfix for a crash issue
7197 that had affected relays under memory pressure. It also adds
7198 a new directory authority, Bastet.
7200 o Directory authority changes:
7201 - Add "Bastet" as a ninth directory authority to the default list.
7202 Closes ticket 23910.
7203 - The directory authority "Longclaw" has changed its IP address.
7204 Closes ticket 23592.
7206 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7207 - Fix a timing-based assertion failure that could occur when the
7208 circuit out-of-memory handler freed a connection's output buffer.
7209 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7211 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7212 - Remove longclaw's IPv6 address, as it will soon change. Authority
7213 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7214 3/8 directory authorities with IPv6 addresses, but there are also
7215 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7217 o Minor features (geoip):
7218 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7221 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
7222 - Fix a compilation warning when building with zstd support on
7223 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7224 and fixed by Andreas Stieger.
7226 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
7227 - Handle a pathological case when decompressing Zstandard data when
7228 the output buffer size is zero. Fixes bug 23551; bugfix
7231 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
7232 - Remove the length limit on HTTP status lines that authorities can
7233 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
7235 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7236 - Avoid a possible double close of a circuit by the intro point on
7237 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7238 bugfix on 0.3.0.1-alpha.
7240 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7241 - Clear the address when node_get_prim_orport() returns early.
7242 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7244 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
7245 - Fix additional channelpadding unit test failures by using mocked
7246 time instead of actual time for all tests. Fixes bug 23608; bugfix
7250 Changes in version 0.3.2.2-alpha - 2017-09-29
7251 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
7252 release fixes several minor bugs in the new scheduler and next-
7253 generation onion services; both features were newly added in the 0.3.2
7254 series. Other fixes in this alpha include several fixes for non-fatal
7255 tracebacks which would appear in logs.
7257 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
7258 alpha does not contain any substantial new features. Minor features
7259 include better testing and logging.
7261 The following comprises the complete list of changes included
7264 o Major bugfixes (relay, crash, assertion failure):
7265 - Fix a timing-based assertion failure that could occur when the
7266 circuit out-of-memory handler freed a connection's output buffer.
7267 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7269 o Major bugfixes (scheduler):
7270 - If a channel is put into the scheduler's pending list, then it
7271 starts closing, and then if the scheduler runs before it finishes
7272 closing, the scheduler will get stuck trying to flush its cells
7273 while the lower layers refuse to cooperate. Fix that race
7274 condition by giving the scheduler an escape method. Fixes bug
7275 23676; bugfix on 0.3.2.1-alpha.
7277 o Minor features (build, compilation):
7278 - The "check-changes" feature is now part of the "make check" tests;
7279 we'll use it to try to prevent misformed changes files from
7280 accumulating. Closes ticket 23564.
7281 - Tor builds should now fail if there are any mismatches between the
7282 C type representing a configuration variable and the C type the
7283 data-driven parser uses to store a value there. Previously, we
7284 needed to check these by hand, which sometimes led to mistakes.
7285 Closes ticket 23643.
7287 o Minor features (directory authorities):
7288 - Remove longclaw's IPv6 address, as it will soon change. Authority
7289 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7290 3/8 directory authorities with IPv6 addresses, but there are also
7291 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7293 o Minor features (hidden service, circuit, logging):
7294 - Improve logging of many callsite in the circuit subsystem to print
7295 the circuit identifier(s).
7296 - Log when we cleanup an intro point from a service so we know when
7297 and for what reason it happened. Closes ticket 23604.
7299 o Minor features (logging):
7300 - Log more circuit information whenever we are about to try to
7301 package a relay cell on a circuit with a nonexistent n_chan.
7302 Attempt to diagnose ticket 8185.
7303 - Improve info-level log identification of particular circuits, to
7304 help with debugging. Closes ticket 23645.
7306 o Minor features (relay):
7307 - When choosing which circuits can be expired as unused, consider
7308 circuits from clients even if those clients used regular CREATE
7309 cells to make them; and do not consider circuits from relays even
7310 if they were made with CREATE_FAST. Part of ticket 22805.
7312 o Minor features (robustness):
7313 - Change several fatal assertions when flushing buffers into non-
7314 fatal assertions, to prevent any recurrence of 23690.
7316 o Minor features (spec conformance, bridge, diagnostic):
7317 - When handling the USERADDR command on an ExtOrPort, warn when the
7318 transports provides a USERADDR with no port. In a future version,
7319 USERADDR commands of this format may be rejected. Detects problems
7320 related to ticket 23080.
7322 o Minor features (testing):
7323 - Add a unit test to make sure that our own generated platform
7324 string will be accepted by directory authorities. Closes
7327 o Minor bugfixes (bootstrapping):
7328 - When warning about state file clock skew, report the correct
7329 direction for the detected skew. Fixes bug 23606; bugfix
7331 - Avoid an assertion failure when logging a state file clock skew
7332 very early in bootstrapping. Fixes bug 23607; bugfix
7335 o Minor bugfixes (build, compilation):
7336 - Fix a compilation warning when building with zstd support on
7337 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7338 and fixed by Andreas Stieger.
7339 - When searching for OpenSSL, don't accept any OpenSSL library that
7340 lacks TLSv1_1_method(): Tor doesn't build with those versions.
7341 Additionally, look in /usr/local/opt/openssl, if it's present.
7342 These changes together repair the default build on OSX systems
7343 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
7345 o Minor bugfixes (compression):
7346 - Handle a pathological case when decompressing Zstandard data when
7347 the output buffer size is zero. Fixes bug 23551; bugfix
7350 o Minor bugfixes (documentation):
7351 - Fix manpage to not refer to the obsolete (and misspelled)
7352 UseEntryGuardsAsDirectoryGuards parameter in the description of
7353 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
7355 o Minor bugfixes (hidden service v3):
7356 - Don't log an assertion failure when we can't find the right
7357 information to extend to an introduction point. In rare cases,
7358 this could happen, causing a warning, even though tor would
7359 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
7360 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
7361 much bigger so the rendezvous point can't distinguish which hidden
7362 service protocol is being used. Fixes bug 23420; bugfix
7365 o Minor bugfixes (hidden service, relay):
7366 - Avoid a possible double close of a circuit by the intro point on
7367 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7368 bugfix on 0.3.0.1-alpha.
7370 o Minor bugfixes (logging, relay shutdown, annoyance):
7371 - When a circuit is marked for close, do not attempt to package any
7372 cells for channels on that circuit. Previously, we would detect
7373 this condition lower in the call stack, when we noticed that the
7374 circuit had no attached channel, and log an annoying message.
7375 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
7377 o Minor bugfixes (scheduler):
7378 - When switching schedulers due to a consensus change, we didn't
7379 give the new scheduler a chance to react to the consensus. Fix
7380 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
7381 - Make the KISTSchedRunInterval option a non negative value. With
7382 this, the way to disable KIST through the consensus is to set it
7383 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
7384 - Only notice log the selected scheduler when we switch scheduler
7385 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
7386 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
7387 by a different tv_usec data type. Fixes bug 23575; bugfix
7389 - Make a hard exit if tor is unable to pick a scheduler which can
7390 happen if the user specifies a scheduler type that is not
7391 supported and not other types in Schedulers. Fixes bug 23581;
7392 bugfix on 0.3.2.1-alpha.
7393 - Properly initialize the scheduler last run time counter so it is
7394 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
7396 o Minor bugfixes (testing):
7397 - Capture and detect several "Result does not fit" warnings in unit
7398 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
7400 - Fix additional channelpadding unit test failures by using mocked
7401 time instead of actual time for all tests. Fixes bug 23608; bugfix
7403 - The removal of some old scheduler options caused some tests to
7404 fail on BSD systems. Assume current behavior is correct and make
7405 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
7407 o Code simplification and refactoring:
7408 - Remove various ways of testing circuits and connections for
7409 "clientness"; instead, favor channel_is_client(). Part of
7412 o Deprecated features:
7413 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
7414 now deprecated; they do not apply to relays, and they have had no
7415 effect on clients since 0.2.8.x. Closes ticket 19704.
7418 - HiddenServiceVersion man page entry wasn't mentioning the now
7419 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
7420 - Clarify that the Address option is entirely about setting an
7421 advertised IPv4 address. Closes ticket 18891.
7422 - Clarify the manpage's use of the term "address" to clarify what
7423 kind of address is intended. Closes ticket 21405.
7424 - Document that onion service subdomains are allowed, and ignored.
7425 Closes ticket 18736.
7428 Changes in version 0.3.2.1-alpha - 2017-09-18
7429 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
7430 includes support for our next-generation ("v3") onion service
7431 protocol, and adds a new circuit scheduler for more responsive
7432 forwarding decisions from relays. There are also numerous other small
7433 features and bugfixes here.
7435 Below are the changes since Tor 0.3.1.7.
7437 o Major feature (scheduler, channel):
7438 - Tor now uses new schedulers to decide which circuits should
7439 deliver cells first, in order to improve congestion at relays. The
7440 first type is called "KIST" ("Kernel Informed Socket Transport"),
7441 and is only available on Linux-like systems: it uses feedback from
7442 the kernel to prevent the kernel's TCP buffers from growing too
7443 full. The second new scheduler type is called "KISTLite": it
7444 behaves the same as KIST, but runs on systems without kernel
7445 support for inspecting TCP implementation details. The old
7446 scheduler is still available, under the name "Vanilla". To change
7447 the default scheduler preference order, use the new "Schedulers"
7448 option. (The default preference order is "KIST,KISTLite,Vanilla".)
7450 Matt Traudt implemented KIST, based on research by Rob Jansen,
7451 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
7452 more information, see the design paper at
7453 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
7454 followup implementation paper at https://arxiv.org/abs/1709.01044.
7455 Closes ticket 12541.
7457 o Major features (next-generation onion services):
7458 - Tor now supports the next-generation onion services protocol for
7459 clients and services! As part of this release, the core of
7460 proposal 224 has been implemented and is available for
7461 experimentation and testing by our users. This newer version of
7462 onion services ("v3") features many improvements over the legacy
7465 a) Better crypto (replaced SHA1/DH/RSA1024
7466 with SHA3/ed25519/curve25519)
7468 b) Improved directory protocol, leaking much less information to
7471 c) Improved directory protocol, with smaller surface for
7474 d) Better onion address security against impersonation.
7476 e) More extensible introduction/rendezvous protocol.
7478 f) A cleaner and more modular codebase.
7480 You can identify a next-generation onion address by its length:
7481 they are 56 characters long, as in
7482 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
7484 In the future, we will release more options and features for v3
7485 onion services, but we first need a testing period, so that the
7486 current codebase matures and becomes more robust. Planned features
7487 include: offline keys, advanced client authorization, improved
7488 guard algorithms, and statistics. For full details, see
7491 Legacy ("v2") onion services will still work for the foreseeable
7492 future, and will remain the default until this new codebase gets
7493 tested and hardened. Service operators who want to experiment with
7494 the new system can use the 'HiddenServiceVersion 3' torrc
7495 directive along with the regular onion service configuration
7496 options. We will publish a blog post about this new feature
7499 o Major bugfixes (usability, control port):
7500 - Report trusted clock skew indications as bootstrap errors, so
7501 controllers can more easily alert users when their clocks are
7502 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
7504 o Minor features (bug detection):
7505 - Log a warning message with a stack trace for any attempt to call
7506 get_options() during option validation. This pattern has caused
7507 subtle bugs in the past. Closes ticket 22281.
7509 o Minor features (client):
7510 - You can now use Tor as a tunneled HTTP proxy: use the new
7511 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
7512 requests. Closes ticket 22407.
7513 - Add an extra check to make sure that we always use the newer guard
7514 selection code for picking our guards. Closes ticket 22779.
7515 - When downloading (micro)descriptors, don't split the list into
7516 multiple requests unless we want at least 32 descriptors.
7517 Previously, we split at 4, not 32, which led to significant
7518 overhead in HTTP request size and degradation in compression
7519 performance. Closes ticket 23220.
7521 o Minor features (command line):
7522 - Add a new commandline option, --key-expiration, which prints when
7523 the current signing key is going to expire. Implements ticket
7524 17639; patch by Isis Lovecruft.
7526 o Minor features (control port):
7527 - If an application tries to use the control port as an HTTP proxy,
7528 respond with a meaningful "This is the Tor control port" message,
7529 and log the event. Closes ticket 1667. Patch from Ravi
7531 - Provide better error message for GETINFO desc/(id|name) when not
7532 fetching router descriptors. Closes ticket 5847. Patch by
7534 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
7535 whether Tor will try to download router descriptors and
7536 microdescriptors respectively. Closes ticket 22684.
7537 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
7538 so controllers can tell whether the geoip databases are loaded.
7539 Closes ticket 23237.
7540 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
7541 events. Closes ticket 19254. Patch by "DonnchaC".
7543 o Minor features (development support):
7544 - Developers can now generate a call-graph for Tor using the
7545 "calltool" python program, which post-processes object dumps. It
7546 should work okay on many Linux and OSX platforms, and might work
7547 elsewhere too. To run it, install calltool from
7548 https://gitweb.torproject.org/user/nickm/calltool.git and run
7549 "make callgraph". Closes ticket 19307.
7551 o Minor features (ed25519):
7552 - Add validation function to checks for torsion components in
7553 ed25519 public keys, used by prop224 client-side code. Closes
7554 ticket 22006. Math help by Ian Goldberg.
7556 o Minor features (exit relay, DNS):
7557 - Improve the clarity and safety of the log message from evdns when
7558 receiving an apparently spoofed DNS reply. Closes ticket 3056.
7560 o Minor features (integration, hardening):
7561 - Add a new NoExec option to prevent Tor from running other
7562 programs. When this option is set to 1, Tor will never try to run
7563 another program, regardless of the settings of
7564 PortForwardingHelper, ClientTransportPlugin, or
7565 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
7566 without restarting Tor. Closes ticket 22976.
7568 o Minor features (logging):
7569 - Improve the warning message for specifying a relay by nickname.
7570 The previous message implied that nickname registration was still
7571 part of the Tor network design, which it isn't. Closes
7573 - If the sandbox filter fails to load, suggest to the user that
7574 their kernel might not support seccomp2. Closes ticket 23090.
7576 o Minor features (portability):
7577 - Check at configure time whether uint8_t is the same type as
7578 unsigned char. Lots of existing code already makes this
7579 assumption, and there could be strict aliasing issues if the
7580 assumption is violated. Closes ticket 22410.
7582 o Minor features (relay, configuration):
7583 - Reject attempts to use relative file paths when RunAsDaemon is
7584 set. Previously, Tor would accept these, but the directory-
7585 changing step of RunAsDaemon would give strange and/or confusing
7586 results. Closes ticket 22731.
7588 o Minor features (startup, safety):
7589 - When configured to write a PID file, Tor now exits if it is unable
7590 to do so. Previously, it would warn and continue. Closes
7593 o Minor features (static analysis):
7594 - The BUG() macro has been changed slightly so that Coverity no
7595 longer complains about dead code if the bug is impossible. Closes
7598 o Minor features (testing):
7599 - The default chutney network tests now include tests for the v3
7600 hidden service design. Make sure you have the latest version of
7601 chutney if you want to run these. Closes ticket 22437.
7602 - Add a unit test to verify that we can parse a hardcoded v2 hidden
7603 service descriptor. Closes ticket 15554.
7605 o Minor bugfixes (certificate handling):
7606 - Fix a time handling bug in Tor certificates set to expire after
7607 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
7608 Coverity as CID 1415728.
7610 o Minor bugfixes (client, usability):
7611 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
7612 SOCKS4a requests that contain IP address strings, even when
7613 SafeSocks in enabled, as this prevents user from connecting to
7614 known IP addresses without relying on DNS for resolving. SafeSocks
7615 still rejects SOCKS connections that connect to IP addresses when
7616 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
7617 bugfix on Tor 0.2.6.2-alpha.
7619 o Minor bugfixes (code correctness):
7620 - Call htons() in extend_cell_format() for encoding a 16-bit value.
7621 Previously we used ntohs(), which happens to behave the same on
7622 all the platforms we support, but which isn't really correct.
7623 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
7624 - For defense-in-depth, make the controller's write_escaped_data()
7625 function robust to extremely long inputs. Fixes bug 19281; bugfix
7626 on 0.1.1.1-alpha. Reported by Guido Vranken.
7628 o Minor bugfixes (compilation):
7629 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
7630 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
7632 o Minor bugfixes (consensus expiry):
7633 - Check for adequate directory information correctly. Previously, Tor
7634 would reconsider whether it had sufficient directory information
7635 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
7637 o Minor bugfixes (directory protocol):
7638 - Directory servers now include a "Date:" http header for response
7639 codes other than 200. Clients starting with a skewed clock and a
7640 recent consensus were getting "304 Not modified" responses from
7641 directory authorities, so without the Date header, the client
7642 would never hear about a wrong clock. Fixes bug 23499; bugfix
7644 - Make clients wait for 6 seconds before trying to download a
7645 consensus from an authority. Fixes bug 17750; bugfix
7648 o Minor bugfixes (DoS-resistance):
7649 - If future code asks if there are any running bridges, without
7650 checking if bridges are enabled, log a BUG warning rather than
7651 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
7653 o Minor bugfixes (format strictness):
7654 - Restrict several data formats to decimal. Previously, the
7655 BuildTimeHistogram entries in the state file, the "bw=" entries in
7656 the bandwidth authority file, and the process IDs passed to the
7657 __OwningControllerProcess option could all be specified in hex or
7658 octal as well as in decimal. This was not an intentional feature.
7659 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
7662 o Minor bugfixes (heartbeat):
7663 - If we fail to write a heartbeat message, schedule a retry for the
7664 minimum heartbeat interval number of seconds in the future. Fixes
7665 bug 19476; bugfix on 0.2.3.1-alpha.
7667 o Minor bugfixes (linux seccomp2 sandbox, logging):
7668 - Fix some messages on unexpected errors from the seccomp2 library.
7669 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
7671 o Minor bugfixes (logging):
7672 - Remove duplicate log messages regarding opening non-local
7673 SocksPorts upon parsing config and opening listeners at startup.
7674 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
7675 - Use a more comprehensible log message when telling the user
7676 they've excluded every running exit node. Fixes bug 7890; bugfix
7678 - When logging the number of descriptors we intend to download per
7679 directory request, do not log a number higher than then the number
7680 of descriptors we're fetching in total. Fixes bug 19648; bugfix
7682 - When warning about a directory owned by the wrong user, log the
7683 actual name of the user owning the directory. Previously, we'd log
7684 the name of the process owner twice. Fixes bug 23487; bugfix
7686 - The tor specification says hop counts are 1-based, so fix two log
7687 messages that mistakenly logged 0-based hop counts. Fixes bug
7688 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
7689 Credit to Xiaofan Li for reporting this issue.
7691 o Minor bugfixes (portability):
7692 - Stop using the PATH_MAX variable, which is not defined on GNU
7693 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
7695 o Minor bugfixes (relay):
7696 - When uploading our descriptor for the first time after startup,
7697 report the reason for uploading as "Tor just started" rather than
7698 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
7699 - Avoid unnecessary calls to directory_fetches_from_authorities() on
7700 relays, to prevent spurious address resolutions and descriptor
7701 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
7702 bugfix on in 0.2.8.1-alpha.
7704 o Minor bugfixes (tests):
7705 - Fix a broken unit test for the OutboundAddress option: the parsing
7706 function was never returning an error on failure. Fixes bug 23366;
7707 bugfix on 0.3.0.3-alpha.
7708 - Fix a signed-integer overflow in the unit tests for
7709 dir/download_status_random_backoff, which was untriggered until we
7710 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
7712 o Minor bugfixes (usability, control port):
7713 - Stop making an unnecessary routerlist check in NETINFO clock skew
7714 detection; this was preventing clients from reporting NETINFO clock
7715 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
7717 o Code simplification and refactoring:
7718 - Extract the code for handling newly-open channels into a separate
7719 function from the general code to handle channel state
7720 transitions. This change simplifies our callgraph, reducing the
7721 size of the largest strongly connected component by roughly a
7722 factor of two. Closes ticket 22608.
7723 - Remove dead code for largely unused statistics on the number of
7724 times we've attempted various public key operations. Fixes bug
7725 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
7726 - Remove several now-obsolete functions for asking about old
7727 variants directory authority status. Closes ticket 22311; patch
7729 - Remove some of the code that once supported "Named" and "Unnamed"
7730 routers. Authorities no longer vote for these flags. Closes
7732 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
7733 and old hidden services, to indicate that they aren't suitable for
7734 new protocols or formats. Closes ticket 23026.
7735 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
7736 22521. Patch from Neel Chauhan.
7737 - Split the enormous circuit_send_next_onion_skin() function into
7738 multiple subfunctions. Closes ticket 22804.
7739 - Split the portions of the buffer.c module that handle particular
7740 protocols into separate modules. Part of ticket 23149.
7741 - Use our test macros more consistently, to produce more useful
7742 error messages when our unit tests fail. Add coccinelle patches to
7743 allow us to re-check for test macro uses. Closes ticket 22497.
7745 o Deprecated features:
7746 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
7747 only applies to direct unencrypted HTTP connections to your
7748 directory server, which your Tor probably isn't using. Closes
7752 - Clarify in the manual that "Sandbox 1" is only supported on Linux
7753 kernels. Closes ticket 22677.
7754 - Document all values of PublishServerDescriptor in the manpage.
7755 Closes ticket 15645.
7756 - Improve the documentation for the directory port part of the
7757 DirAuthority line. Closes ticket 20152.
7758 - Restore documentation for the authorities' "approved-routers"
7759 file. Closes ticket 21148.
7762 - The AllowDotExit option has been removed as unsafe. It has been
7763 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
7764 - The ClientDNSRejectInternalAddresses flag can no longer be set on
7765 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
7766 Closes ticket 21031.
7767 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
7768 nobody was using it any longer. Closes ticket 22377.
7771 Changes in version 0.2.8.15 - 2017-09-18
7772 Tor 0.2.8.15 backports a collection of bugfixes from later
7775 Most significantly, it includes a fix for TROVE-2017-008, a
7776 security bug that affects hidden services running with the
7777 SafeLogging option disabled. For more information, see
7778 https://trac.torproject.org/projects/tor/ticket/23490
7780 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
7781 2018. We suggest that you upgrade to the latest stable release if
7782 possible. If you can't, we recommend that you upgrade at least to
7783 0.2.9, which will be supported until 2020.
7785 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7786 - Avoid an assertion failure bug affecting our implementation of
7787 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7788 handling of "0xx" differs from what we had expected. Fixes bug
7789 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7792 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7795 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7796 - Backport a fix for an "unused variable" warning that appeared
7797 in some versions of mingw. Fixes bug 22838; bugfix on
7800 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7801 - Fix a memset() off the end of an array when packing cells. This
7802 bug should be harmless in practice, since the corrupted bytes are
7803 still in the same structure, and are always padding bytes,
7804 ignored, or immediately overwritten, depending on compiler
7805 behavior. Nevertheless, because the memset()'s purpose is to make
7806 sure that any other cell-handling bugs can't expose bytes to the
7807 network, we need to fix it. Fixes bug 22737; bugfix on
7808 0.2.4.11-alpha. Fixes CID 1401591.
7810 o Build features (backport from 0.3.1.5-alpha):
7811 - Tor's repository now includes a Travis Continuous Integration (CI)
7812 configuration file (.travis.yml). This is meant to help new
7813 developers and contributors who fork Tor to a Github repository be
7814 better able to test their changes, and understand what we expect
7815 to pass. To use this new build feature, you must fork Tor to your
7816 Github account, then go into the "Integrations" menu in the
7817 repository settings for your fork and enable Travis, then push
7818 your changes. Closes ticket 22636.
7821 Changes in version 0.2.9.12 - 2017-09-18
7822 Tor 0.2.9.12 backports a collection of bugfixes from later
7825 Most significantly, it includes a fix for TROVE-2017-008, a
7826 security bug that affects hidden services running with the
7827 SafeLogging option disabled. For more information, see
7828 https://trac.torproject.org/projects/tor/ticket/23490
7830 o Major features (security, backport from 0.3.0.2-alpha):
7831 - Change the algorithm used to decide DNS TTLs on client and server
7832 side, to better resist DNS-based correlation attacks like the
7833 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
7834 Feamster. Now relays only return one of two possible DNS TTL
7835 values, and clients are willing to believe DNS TTL values up to 3
7836 hours long. Closes ticket 19769.
7838 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
7839 - Fix a rare crash when sending a begin cell on a circuit whose
7840 linked directory connection had already been closed. Fixes bug
7841 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
7843 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
7844 - Fix a bug that prevented exit nodes from caching DNS records for
7845 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7847 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7848 - Fix a typo that had prevented TPROXY-based transparent proxying
7849 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7850 Patch from "d4fq0fQAgoJ".
7852 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7853 - Avoid an assertion failure bug affecting our implementation of
7854 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7855 handling of "0xx" differs from what we had expected. Fixes bug
7856 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7858 o Minor features (code style, backport from 0.3.1.3-alpha):
7859 - Add "Falls through" comments to our codebase, in order to silence
7860 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7861 Stieger. Closes ticket 22446.
7863 o Minor features (geoip):
7864 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7867 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
7868 - Roll over monthly accounting at the configured hour and minute,
7869 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7870 Found by Andrey Karpov with PVS-Studio.
7872 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
7873 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7874 bugfix on 0.2.8.1-alpha.
7875 - Fix warnings when building with libscrypt and openssl scrypt support
7876 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7877 - When building with certain versions the mingw C header files, avoid
7878 float-conversion warnings when calling the C functions isfinite(),
7879 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
7881 o Minor bugfixes (compilation, backport from 0.3.1.7):
7882 - Avoid compiler warnings in the unit tests for running tor_sscanf()
7883 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7885 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7886 - Backport a fix for an "unused variable" warning that appeared
7887 in some versions of mingw. Fixes bug 22838; bugfix on
7890 o Minor bugfixes (controller, backport from 0.3.1.7):
7891 - Do not crash when receiving a HSPOST command with an empty body.
7892 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7893 - Do not crash when receiving a POSTDESCRIPTOR command with an
7894 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7896 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
7897 - Avoid Coverity build warnings related to our BUG() macro. By
7898 default, Coverity treats BUG() as the Linux kernel does: an
7899 instant abort(). We need to override that so our BUG() macro
7900 doesn't prevent Coverity from analyzing functions that use it.
7901 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7903 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7904 - Fix a memset() off the end of an array when packing cells. This
7905 bug should be harmless in practice, since the corrupted bytes are
7906 still in the same structure, and are always padding bytes,
7907 ignored, or immediately overwritten, depending on compiler
7908 behavior. Nevertheless, because the memset()'s purpose is to make
7909 sure that any other cell-handling bugs can't expose bytes to the
7910 network, we need to fix it. Fixes bug 22737; bugfix on
7911 0.2.4.11-alpha. Fixes CID 1401591.
7913 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7914 - When setting the maximum number of connections allowed by the OS,
7915 always allow some extra file descriptors for other files. Fixes
7916 bug 22797; bugfix on 0.2.0.10-alpha.
7918 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
7919 - Avoid a sandbox failure when trying to re-bind to a socket and
7920 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7922 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
7923 - Permit the fchmod system call, to avoid crashing on startup when
7924 starting with the seccomp2 sandbox and an unexpected set of
7925 permissions on the data directory or its contents. Fixes bug
7926 22516; bugfix on 0.2.5.4-alpha.
7928 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
7929 - Avoid a double-marked-circuit warning that could happen when we
7930 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
7933 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
7934 - Reject version numbers with non-numeric prefixes (such as +, -, or
7935 whitespace). Disallowing whitespace prevents differential version
7936 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7937 and part of 21508; bugfix on 0.0.8pre1.
7939 o Build features (backport from 0.3.1.5-alpha):
7940 - Tor's repository now includes a Travis Continuous Integration (CI)
7941 configuration file (.travis.yml). This is meant to help new
7942 developers and contributors who fork Tor to a Github repository be
7943 better able to test their changes, and understand what we expect
7944 to pass. To use this new build feature, you must fork Tor to your
7945 Github account, then go into the "Integrations" menu in the
7946 repository settings for your fork and enable Travis, then push
7947 your changes. Closes ticket 22636.
7950 Changes in version 0.3.0.11 - 2017-09-18
7951 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
7954 Most significantly, it includes a fix for TROVE-2017-008, a
7955 security bug that affects hidden services running with the
7956 SafeLogging option disabled. For more information, see
7957 https://trac.torproject.org/projects/tor/ticket/23490
7959 o Minor features (code style, backport from 0.3.1.7):
7960 - Add "Falls through" comments to our codebase, in order to silence
7961 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7962 Stieger. Closes ticket 22446.
7965 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7968 o Minor bugfixes (compilation, backport from 0.3.1.7):
7969 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7970 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7972 o Minor bugfixes (controller, backport from 0.3.1.7):
7973 - Do not crash when receiving a HSPOST command with an empty body.
7974 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7975 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7976 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7978 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7979 - When setting the maximum number of connections allowed by the OS,
7980 always allow some extra file descriptors for other files. Fixes
7981 bug 22797; bugfix on 0.2.0.10-alpha.
7983 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
7984 - Remove a forgotten debugging message when an introduction point
7985 successfully establishes a hidden service prop224 circuit with
7987 - Change three other log_warn() for an introduction point to
7988 protocol warnings, because they can be failure from the network
7989 and are not relevant to the operator. Fixes bug 23078; bugfix on
7990 0.3.0.1-alpha and 0.3.0.2-alpha.
7993 Changes in version 0.3.1.7 - 2017-09-18
7994 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
7996 With the 0.3.1 series, Tor now serves and downloads directory
7997 information in more compact formats, to save on bandwidth overhead. It
7998 also contains a new padding system to resist netflow-based traffic
7999 analysis, and experimental support for building parts of Tor in Rust
8000 (though no parts of Tor are in Rust yet). There are also numerous
8001 small features, bugfixes on earlier release series, and groundwork for
8002 the hidden services revamp of 0.3.2.
8004 This release also includes a fix for TROVE-2017-008, a security bug
8005 that affects hidden services running with the SafeLogging option
8006 disabled. For more information, see
8007 https://trac.torproject.org/projects/tor/ticket/23490
8009 Per our stable release policy, we plan to support each stable release
8010 series for at least the next nine months, or for three months after
8011 the first stable release of the next series: whichever is longer. If
8012 you need a release with long-term support, we recommend that you stay
8013 with the 0.2.9 series.
8015 Below is a list of the changes since 0.3.1.6-rc. For a list of all
8016 changes since 0.3.0, see the ReleaseNotes file.
8018 o Major bugfixes (security, hidden services, loggging):
8019 - Fix a bug where we could log uninitialized stack when a certain
8020 hidden service error occurred while SafeLogging was disabled.
8021 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
8022 TROVE-2017-008 and CVE-2017-0380.
8024 o Minor features (defensive programming):
8025 - Create a pair of consensus parameters, nf_pad_tor2web and
8026 nf_pad_single_onion, to disable netflow padding in the consensus
8027 for non-anonymous connections in case the overhead is high. Closes
8030 o Minor features (diagnostic):
8031 - Add a stack trace to the bug warnings that can be logged when
8032 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
8033 attempt for bug 23105.
8035 o Minor features (geoip):
8036 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
8039 o Minor bugfixes (compilation):
8040 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
8041 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
8043 o Minor bugfixes (controller):
8044 - Do not crash when receiving a HSPOST command with an empty body.
8045 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
8046 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
8047 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
8049 o Minor bugfixes (relay):
8050 - Inform the geoip and rephist modules about all requests, even on
8051 relays that are only fetching microdescriptors. Fixes a bug
8052 related to 21585; bugfix on 0.3.0.1-alpha.
8054 o Minor bugfixes (unit tests):
8055 - Fix a channelpadding unit test failure on slow systems by using
8056 mocked time instead of actual time. Fixes bug 23077; bugfix
8060 Changes in version 0.3.1.6-rc - 2017-09-05
8061 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
8062 release series, including a bug that produced weird behavior on
8063 Windows directory caches.
8065 This is the first release candidate in the Tor 0.3.1 series. If we
8066 find no new bugs or regressions here, the first stable 0.3.1 release
8067 will be nearly identical to it.
8069 o Major bugfixes (windows, directory cache):
8070 - On Windows, do not try to delete cached consensus documents and
8071 diffs before they are unmapped from memory--Windows won't allow
8072 that. Instead, allow the consensus cache directory to grow larger,
8073 to hold files that might need to stay around longer. Fixes bug
8074 22752; bugfix on 0.3.1.1-alpha.
8076 o Minor features (directory authority):
8077 - Improve the message that authorities report to relays that present
8078 RSA/Ed25519 keypairs that conflict with previously pinned keys.
8079 Closes ticket 22348.
8081 o Minor features (geoip):
8082 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
8085 o Minor features (testing):
8086 - Add more tests for compression backend initialization. Closes
8089 o Minor bugfixes (directory cache):
8090 - Fix a memory leak when recovering space in the consensus cache.
8091 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
8093 o Minor bugfixes (hidden service):
8094 - Increase the number of circuits that a service is allowed to
8095 open over a specific period of time. The value was lower than it
8096 should be (8 vs 12) in the normal case of 3 introduction points.
8097 Fixes bug 22159; bugfix on 0.3.0.5-rc.
8098 - Fix a BUG warning during HSv3 descriptor decoding that could be
8099 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
8100 on 0.3.0.1-alpha. Bug found by "haxxpop".
8101 - Rate-limit the log messages if we exceed the maximum number of
8102 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
8104 o Minor bugfixes (logging, relay):
8105 - Remove a forgotten debugging message when an introduction point
8106 successfully establishes a hidden service prop224 circuit with
8108 - Change three other log_warn() for an introduction point to
8109 protocol warnings, because they can be failure from the network
8110 and are not relevant to the operator. Fixes bug 23078; bugfix on
8111 0.3.0.1-alpha and 0.3.0.2-alpha.
8113 o Minor bugfixes (relay):
8114 - When a relay is not running as a directory cache, it will no
8115 longer generate compressed consensuses and consensus diff
8116 information. Previously, this was a waste of disk and CPU. Fixes
8117 bug 23275; bugfix on 0.3.1.1-alpha.
8119 o Minor bugfixes (robustness, error handling):
8120 - Improve our handling of the cases where OpenSSL encounters a
8121 memory error while encoding keys and certificates. We haven't
8122 observed these errors in the wild, but if they do happen, we now
8123 detect and respond better. Fixes bug 19418; bugfix on all versions
8124 of Tor. Reported by Guido Vranken.
8126 o Minor bugfixes (stability):
8127 - Avoid crashing on a double-free when unable to load or process an
8128 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
8129 with the clang static analyzer.
8131 o Minor bugfixes (testing):
8132 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
8133 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
8134 - Port the hs_ntor handshake test to work correctly with recent
8135 versions of the pysha3 module. Fixes bug 23071; bugfix
8138 o Minor bugfixes (Windows service):
8139 - When running as a Windows service, set the ID of the main thread
8140 correctly. Failure to do so made us fail to send log messages to
8141 the controller in 0.2.1.16-rc, slowed down controller event
8142 delivery in 0.2.7.3-rc and later, and crash with an assertion
8143 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
8144 Patch and diagnosis from "Vort".
8147 Changes in version 0.3.0.10 - 2017-08-02
8148 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
8149 from the current Tor alpha series. OpenBSD users and TPROXY users
8150 should upgrade; others are probably okay sticking with 0.3.0.9.
8152 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
8153 - Tor's repository now includes a Travis Continuous Integration (CI)
8154 configuration file (.travis.yml). This is meant to help new
8155 developers and contributors who fork Tor to a Github repository be
8156 better able to test their changes, and understand what we expect
8157 to pass. To use this new build feature, you must fork Tor to your
8158 Github account, then go into the "Integrations" menu in the
8159 repository settings for your fork and enable Travis, then push
8160 your changes. Closes ticket 22636.
8162 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
8163 - Fix a typo that had prevented TPROXY-based transparent proxying
8164 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8165 Patch from "d4fq0fQAgoJ".
8167 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
8168 - Avoid an assertion failure bug affecting our implementation of
8169 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8170 handling of "0xbar" differs from what we had expected. Fixes bug
8171 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8173 o Minor features (backport from 0.3.1.5-alpha):
8174 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8177 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
8178 - Roll over monthly accounting at the configured hour and minute,
8179 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8180 Found by Andrey Karpov with PVS-Studio.
8182 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
8183 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
8184 bugfix on 0.2.8.1-alpha.
8185 - Fix warnings when building with libscrypt and openssl scrypt
8186 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8187 - When building with certain versions of the mingw C header files,
8188 avoid float-conversion warnings when calling the C functions
8189 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8192 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
8193 - Backport a fix for an "unused variable" warning that appeared
8194 in some versions of mingw. Fixes bug 22838; bugfix on
8197 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
8198 - Avoid Coverity build warnings related to our BUG() macro. By
8199 default, Coverity treats BUG() as the Linux kernel does: an
8200 instant abort(). We need to override that so our BUG() macro
8201 doesn't prevent Coverity from analyzing functions that use it.
8202 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8204 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
8205 - When rejecting a router descriptor for running an obsolete version
8206 of Tor without ntor support, warn about the obsolete tor version,
8207 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8209 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
8210 - Avoid a sandbox failure when trying to re-bind to a socket and
8211 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8213 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
8214 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8215 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8218 Changes in version 0.3.1.5-alpha - 2017-08-01
8219 Tor 0.3.1.5-alpha improves the performance of consensus diff
8220 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
8221 several other bugs. If no serious bugs are found in this version, the
8222 next version will be a release candidate.
8224 This release also marks the end of support for the Tor 0.2.4.x,
8225 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
8226 further bug or security fixes. Anyone still running or distributing
8227 one of those versions should upgrade.
8229 o Major features (build system, continuous integration):
8230 - Tor's repository now includes a Travis Continuous Integration (CI)
8231 configuration file (.travis.yml). This is meant to help new
8232 developers and contributors who fork Tor to a Github repository be
8233 better able to test their changes, and understand what we expect
8234 to pass. To use this new build feature, you must fork Tor to your
8235 Github account, then go into the "Integrations" menu in the
8236 repository settings for your fork and enable Travis, then push
8237 your changes. Closes ticket 22636.
8239 o Major bugfixes (openbsd, denial-of-service):
8240 - Avoid an assertion failure bug affecting our implementation of
8241 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8242 handling of "0xbar" differs from what we had expected. Fixes bug
8243 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8245 o Major bugfixes (relay, performance):
8246 - Perform circuit handshake operations at a higher priority than we
8247 use for consensus diff creation and compression. This should
8248 prevent circuits from starving when a relay or bridge receives a
8249 new consensus, especially on lower-powered machines. Fixes bug
8250 22883; bugfix on 0.3.1.1-alpha.
8252 o Minor features (bridge authority):
8253 - Add "fingerprint" lines to the networkstatus-bridges file produced
8254 by bridge authorities. Closes ticket 22207.
8256 o Minor features (directory cache, consensus diff):
8257 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
8258 operators with low-resource environments to adjust the number of
8259 consensuses they'll store and generate diffs from. Most cache
8260 operators should leave it unchanged. Helps to work around
8263 o Minor features (geoip):
8264 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8267 o Minor features (relay, performance):
8268 - Always start relays with at least two worker threads, to prevent
8269 priority inversion on slow tasks. Part of the fix for bug 22883.
8270 - Allow background work to be queued with different priorities, so
8271 that a big pile of slow low-priority jobs will not starve out
8272 higher priority jobs. This lays the groundwork for a fix for
8275 o Minor bugfixes (build system, rust):
8276 - Fix a problem where Rust toolchains were not being found when
8277 building without --enable-cargo-online-mode, due to setting the
8278 $HOME environment variable instead of $CARGO_HOME. Fixes bug
8279 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
8281 o Minor bugfixes (compatibility, zstd):
8282 - Write zstd epilogues correctly when the epilogue requires
8283 reallocation of the output buffer, even with zstd 1.3.0.
8284 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
8285 22927; bugfix on 0.3.1.1-alpha.
8287 o Minor bugfixes (compilation warnings):
8288 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
8289 22915; bugfix on 0.2.8.1-alpha.
8290 - Fix warnings when building with libscrypt and openssl scrypt
8291 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8292 - Compile correctly when both openssl 1.1.0 and libscrypt are
8293 detected. Previously this would cause an error. Fixes bug 22892;
8294 bugfix on 0.3.1.1-alpha.
8295 - When building with certain versions of the mingw C header files,
8296 avoid float-conversion warnings when calling the C functions
8297 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8300 o Minor bugfixes (coverity build support):
8301 - Avoid Coverity build warnings related to our BUG() macro. By
8302 default, Coverity treats BUG() as the Linux kernel does: an
8303 instant abort(). We need to override that so our BUG() macro
8304 doesn't prevent Coverity from analyzing functions that use it.
8305 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8307 o Minor bugfixes (directory authority):
8308 - When a directory authority rejects a descriptor or extrainfo with
8309 a given digest, mark that digest as undownloadable, so that we do
8310 not attempt to download it again over and over. We previously
8311 tried to avoid downloading such descriptors by other means, but we
8312 didn't notice if we accidentally downloaded one anyway. This
8313 behavior became problematic in 0.2.7.2-alpha, when authorities
8314 began pinning Ed25519 keys. Fixes bug 22349; bugfix
8317 o Minor bugfixes (error reporting, windows):
8318 - When formatting Windows error messages, use the English format to
8319 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
8322 o Minor bugfixes (file limits, osx):
8323 - When setting the maximum number of connections allowed by the OS,
8324 always allow some extra file descriptors for other files. Fixes
8325 bug 22797; bugfix on 0.2.0.10-alpha.
8327 o Minor bugfixes (linux seccomp2 sandbox):
8328 - Avoid a sandbox failure when trying to re-bind to a socket and
8329 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8331 o Minor bugfixes (memory leaks):
8332 - Fix a small memory leak when validating a configuration that uses
8333 two or more AF_UNIX sockets for the same port type. Fixes bug
8334 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
8336 o Minor bugfixes (unit tests):
8337 - test_consdiff_base64cmp would fail on OS X because while OS X
8338 follows the standard of (less than zero/zero/greater than zero),
8339 it doesn't follow the convention of (-1/0/+1). Make the test
8340 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
8341 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8342 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8345 Changes in version 0.3.1.4-alpha - 2017-06-29
8346 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
8347 to use a guard that was in the same network family as a chosen exit
8348 relay. This is a security regression; all clients running earlier
8349 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
8352 This release also fixes several other bugs introduced in 0.3.0.x
8353 and 0.3.1.x, including others that can affect bandwidth usage
8357 - To build with zstd and lzma support, Tor now requires the
8358 pkg-config tool at build time. (This requirement was new in
8359 0.3.1.1-alpha, but was not noted at the time. Noting it here to
8360 close ticket 22623.)
8362 o Major bugfixes (path selection, security):
8363 - When choosing which guard to use for a circuit, avoid the exit's
8364 family along with the exit itself. Previously, the new guard
8365 selection logic avoided the exit, but did not consider its family.
8366 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8367 006 and CVE-2017-0377.
8369 o Major bugfixes (compression, zstd):
8370 - Correctly detect a full buffer when decompressing a large zstd-
8371 compressed input. Previously, we would sometimes treat a full
8372 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
8374 o Major bugfixes (directory protocol):
8375 - Ensure that we send "304 Not modified" as HTTP status code when a
8376 client is attempting to fetch a consensus or consensus diff, and
8377 the best one we can send them is one they already have. Fixes bug
8378 22702; bugfix on 0.3.1.1-alpha.
8380 o Major bugfixes (entry guards):
8381 - When starting with an old consensus, do not add new entry guards
8382 unless the consensus is "reasonably live" (under 1 day old). Fixes
8383 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8385 o Minor features (bug mitigation, diagnostics, logging):
8386 - Avoid an assertion failure, and log a better error message, when
8387 unable to remove a file from the consensus cache on Windows.
8388 Attempts to mitigate and diagnose bug 22752.
8390 o Minor features (geoip):
8391 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8394 o Minor bugfixes (compression):
8395 - When compressing or decompressing a buffer, check for a failure to
8396 create a compression object. Fixes bug 22626; bugfix
8398 - When decompressing a buffer, check for extra data after the end of
8399 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
8400 - When decompressing an object received over an anonymous directory
8401 connection, if we have already decompressed it using an acceptable
8402 compression method, do not reject it for looking like an
8403 unacceptable compression method. Fixes part of bug 22670; bugfix
8405 - When serving directory votes compressed with zlib, do not claim to
8406 have compressed them with zstd. Fixes bug 22669; bugfix
8408 - When spooling compressed data to an output buffer, don't try to
8409 spool more data when there is no more data to spool and we are not
8410 trying to flush the input. Previously, we would sometimes launch
8411 compression requests with nothing to do, which interferes with our
8412 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
8414 o Minor bugfixes (defensive programming):
8415 - Detect and break out of infinite loops in our compression code. We
8416 don't think that any such loops exist now, but it's best to be
8417 safe. Closes ticket 22672.
8418 - Fix a memset() off the end of an array when packing cells. This
8419 bug should be harmless in practice, since the corrupted bytes are
8420 still in the same structure, and are always padding bytes,
8421 ignored, or immediately overwritten, depending on compiler
8422 behavior. Nevertheless, because the memset()'s purpose is to make
8423 sure that any other cell-handling bugs can't expose bytes to the
8424 network, we need to fix it. Fixes bug 22737; bugfix on
8425 0.2.4.11-alpha. Fixes CID 1401591.
8427 o Minor bugfixes (linux seccomp2 sandbox):
8428 - Permit the fchmod system call, to avoid crashing on startup when
8429 starting with the seccomp2 sandbox and an unexpected set of
8430 permissions on the data directory or its contents. Fixes bug
8431 22516; bugfix on 0.2.5.4-alpha.
8432 - Fix a crash in the LZMA module, when the sandbox was enabled, and
8433 liblzma would allocate more than 16 MB of memory. We solve this by
8434 bumping the mprotect() limit in the sandbox module from 16 MB to
8435 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
8437 o Minor bugfixes (logging):
8438 - When decompressing, do not warn if we fail to decompress using a
8439 compression method that we merely guessed. Fixes part of bug
8440 22670; bugfix on 0.1.1.14-alpha.
8441 - When decompressing, treat mismatch between content-encoding and
8442 actual compression type as a protocol warning. Fixes part of bug
8443 22670; bugfix on 0.1.1.9-alpha.
8444 - Downgrade "assigned_to_cpuworker failed" message to info-level
8445 severity. In every case that can reach it, either a better warning
8446 has already been logged, or no warning is warranted. Fixes bug
8447 22356; bugfix on 0.2.6.3-alpha.
8448 - Demote a warn that was caused by libevent delays to info if
8449 netflow padding is less than 4.5 seconds late, or to notice
8450 if it is more (4.5 seconds is the amount of time that a netflow
8451 record might be emitted after, if we chose the maximum timeout).
8452 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8454 o Minor bugfixes (process behavior):
8455 - When exiting because of an error, always exit with a nonzero exit
8456 status. Previously, we would fail to report an error in our exit
8457 status in cases related to __OwningControllerProcess failure,
8458 lockfile contention, and Ed25519 key initialization. Fixes bug
8459 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
8460 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
8464 - Add a manpage description for the key-pinning-journal file. Closes
8466 - Correctly note that bandwidth accounting values are stored in the
8467 state file, and the bw_accounting file is now obsolete. Closes
8469 - Document more of the files in the Tor data directory, including
8470 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
8471 approved-routers, sr-random, and diff-cache. Found while fixing
8475 Changes in version 0.3.0.9 - 2017-06-29
8476 Tor 0.3.0.9 fixes a path selection bug that would allow a client
8477 to use a guard that was in the same network family as a chosen exit
8478 relay. This is a security regression; all clients running earlier
8479 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
8482 This release also backports several other bugfixes from the 0.3.1.x
8485 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
8486 - When choosing which guard to use for a circuit, avoid the exit's
8487 family along with the exit itself. Previously, the new guard
8488 selection logic avoided the exit, but did not consider its family.
8489 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8490 006 and CVE-2017-0377.
8492 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
8493 - Don't block bootstrapping when a primary bridge is offline and we
8494 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8495 21969; bugfix on 0.3.0.3-alpha.
8497 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
8498 - When starting with an old consensus, do not add new entry guards
8499 unless the consensus is "reasonably live" (under 1 day old). Fixes
8500 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8502 o Minor features (geoip):
8503 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8506 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
8507 - Reject version numbers with non-numeric prefixes (such as +, -, or
8508 whitespace). Disallowing whitespace prevents differential version
8509 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8510 and part of 21508; bugfix on 0.0.8pre1.
8512 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
8513 - Permit the fchmod system call, to avoid crashing on startup when
8514 starting with the seccomp2 sandbox and an unexpected set of
8515 permissions on the data directory or its contents. Fixes bug
8516 22516; bugfix on 0.2.5.4-alpha.
8518 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
8519 - Fix a memset() off the end of an array when packing cells. This
8520 bug should be harmless in practice, since the corrupted bytes are
8521 still in the same structure, and are always padding bytes,
8522 ignored, or immediately overwritten, depending on compiler
8523 behavior. Nevertheless, because the memset()'s purpose is to make
8524 sure that any other cell-handling bugs can't expose bytes to the
8525 network, we need to fix it. Fixes bug 22737; bugfix on
8526 0.2.4.11-alpha. Fixes CID 1401591.
8529 Changes in version 0.3.1.3-alpha - 2017-06-08
8530 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
8531 remotely crash a hidden service with an assertion failure. Anyone
8532 running a hidden service should upgrade to this version, or to some
8533 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8535 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
8536 that sometimes made relays unreliable, as well as several other
8537 bugfixes described below.
8539 o Major bugfixes (hidden service, relay, security):
8540 - Fix a remotely triggerable assertion failure when a hidden service
8541 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8542 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8543 - Fix a remotely triggerable assertion failure caused by receiving a
8544 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8545 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8548 o Major bugfixes (relay, link handshake):
8549 - When performing the v3 link handshake on a TLS connection, report
8550 that we have the x509 certificate that we actually used on that
8551 connection, even if we have changed certificates since that
8552 connection was first opened. Previously, we would claim to have
8553 used our most recent x509 link certificate, which would sometimes
8554 make the link handshake fail. Fixes one case of bug 22460; bugfix
8557 o Major bugfixes (relays, key management):
8558 - Regenerate link and authentication certificates whenever the key
8559 that signs them changes; also, regenerate link certificates
8560 whenever the signed key changes. Previously, these processes were
8561 only weakly coupled, and we relays could (for minutes to hours)
8562 wind up with an inconsistent set of keys and certificates, which
8563 other relays would not accept. Fixes two cases of bug 22460;
8564 bugfix on 0.3.0.1-alpha.
8565 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8566 send the certificate that matches the x509 certificate that we
8567 used on the TLS connection. Previously, there was a race condition
8568 if the TLS context rotated after we began the TLS handshake but
8569 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8572 o Major bugfixes (torrc, crash):
8573 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
8574 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
8576 o Minor features (code style):
8577 - Add "Falls through" comments to our codebase, in order to silence
8578 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
8579 Stieger. Closes ticket 22446.
8581 o Minor features (diagnostic):
8582 - Add logging messages to try to diagnose a rare bug that seems to
8583 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
8584 think this is happening because of incorrect system clocks, but
8585 we'd like to know for certain. Diagnostic for bug 22466.
8587 o Minor bugfixes (correctness):
8588 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8589 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8591 o Minor bugfixes (directory protocol):
8592 - Check for libzstd >= 1.1, because older versions lack the
8593 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
8595 o Minor bugfixes (link handshake):
8596 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8597 months, and regenerate it when it is within one month of expiring.
8598 Previously, we had generated this certificate at startup with a
8599 ten-year lifetime, but that could lead to weird behavior when Tor
8600 was started with a grossly inaccurate clock. Mitigates bug 22466;
8601 mitigation on 0.3.0.1-alpha.
8603 o Minor bugfixes (storage directories):
8604 - Always check for underflows in the cached storage directory usage.
8605 If the usage does underflow, re-calculate it. Also, avoid a
8606 separate underflow when the usage is not known. Fixes bug 22424;
8607 bugfix on 0.3.1.1-alpha.
8609 o Minor bugfixes (unit tests):
8610 - The unit tests now pass on systems where localhost is misconfigured
8611 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
8615 - Clarify the manpage for the (deprecated) torify script. Closes
8618 Changes in version 0.3.0.8 - 2017-06-08
8619 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
8620 remotely crash a hidden service with an assertion failure. Anyone
8621 running a hidden service should upgrade to this version, or to some
8622 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8624 Tor 0.3.0.8 also includes fixes for several key management bugs
8625 that sometimes made relays unreliable, as well as several other
8626 bugfixes described below.
8628 o Major bugfixes (hidden service, relay, security, backport
8629 from 0.3.1.3-alpha):
8630 - Fix a remotely triggerable assertion failure when a hidden service
8631 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8632 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8633 - Fix a remotely triggerable assertion failure caused by receiving a
8634 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8635 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8638 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8639 - When performing the v3 link handshake on a TLS connection, report
8640 that we have the x509 certificate that we actually used on that
8641 connection, even if we have changed certificates since that
8642 connection was first opened. Previously, we would claim to have
8643 used our most recent x509 link certificate, which would sometimes
8644 make the link handshake fail. Fixes one case of bug 22460; bugfix
8647 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
8648 - Regenerate link and authentication certificates whenever the key
8649 that signs them changes; also, regenerate link certificates
8650 whenever the signed key changes. Previously, these processes were
8651 only weakly coupled, and we relays could (for minutes to hours)
8652 wind up with an inconsistent set of keys and certificates, which
8653 other relays would not accept. Fixes two cases of bug 22460;
8654 bugfix on 0.3.0.1-alpha.
8655 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8656 send the certificate that matches the x509 certificate that we
8657 used on the TLS connection. Previously, there was a race condition
8658 if the TLS context rotated after we began the TLS handshake but
8659 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8662 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
8663 - Stop rejecting v3 hidden service descriptors because their size
8664 did not match an old padding rule. Fixes bug 22447; bugfix on
8667 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8668 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8669 December 2016 (of which ~126 were still functional) with a list of
8670 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8671 2017. Resolves ticket 21564.
8673 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
8674 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8675 bug 22252; bugfix on 0.2.9.3-alpha.
8677 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8678 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8679 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8681 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
8682 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8683 months, and regenerate it when it is within one month of expiring.
8684 Previously, we had generated this certificate at startup with a
8685 ten-year lifetime, but that could lead to weird behavior when Tor
8686 was started with a grossly inaccurate clock. Mitigates bug 22466;
8687 mitigation on 0.3.0.1-alpha.
8689 o Minor bugfixes (memory leak, directory authority, backport from
8691 - When directory authorities reject a router descriptor due to
8692 keypinning, free the router descriptor rather than leaking the
8693 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8696 Changes in version 0.2.9.11 - 2017-06-08
8697 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
8698 remotely crash a hidden service with an assertion failure. Anyone
8699 running a hidden service should upgrade to this version, or to some
8700 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8701 are not affected by TROVE-2017-004.)
8703 Tor 0.2.9.11 also backports fixes for several key management bugs
8704 that sometimes made relays unreliable, as well as several other
8705 bugfixes described below.
8707 o Major bugfixes (hidden service, relay, security, backport
8708 from 0.3.1.3-alpha):
8709 - Fix a remotely triggerable assertion failure caused by receiving a
8710 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8711 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8714 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8715 - When performing the v3 link handshake on a TLS connection, report
8716 that we have the x509 certificate that we actually used on that
8717 connection, even if we have changed certificates since that
8718 connection was first opened. Previously, we would claim to have
8719 used our most recent x509 link certificate, which would sometimes
8720 make the link handshake fail. Fixes one case of bug 22460; bugfix
8723 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8724 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8725 December 2016 (of which ~126 were still functional) with a list of
8726 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8727 2017. Resolves ticket 21564.
8729 o Minor features (future-proofing, backport from 0.3.0.7):
8730 - Tor no longer refuses to download microdescriptors or descriptors if
8731 they are listed as "published in the future". This change will
8732 eventually allow us to stop listing meaningful "published" dates
8733 in microdescriptor consensuses, and thereby allow us to reduce the
8734 resources required to download consensus diffs by over 50%.
8735 Implements part of ticket 21642; implements part of proposal 275.
8737 o Minor features (directory authorities, backport from 0.3.0.4-rc)
8738 - Directory authorities now reject relays running versions
8739 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8740 suffer from bug 20499 and don't keep their consensus cache
8741 up-to-date. Resolves ticket 20509.
8743 o Minor features (geoip):
8744 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8747 o Minor bugfixes (control port, backport from 0.3.0.6):
8748 - The GETINFO extra-info/digest/<digest> command was broken because
8749 of a wrong base16 decode return value check, introduced when
8750 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8752 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8753 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8754 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8756 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
8757 - The getpid() system call is now permitted under the Linux seccomp2
8758 sandbox, to avoid crashing with versions of OpenSSL (and other
8759 libraries) that attempt to learn the process's PID by using the
8760 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8763 o Minor bugfixes (memory leak, directory authority, backport
8764 from 0.3.1.2-alpha):
8765 - When directory authorities reject a router descriptor due to
8766 keypinning, free the router descriptor rather than leaking the
8767 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8769 Changes in version 0.2.8.14 - 2017-06-08
8770 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8771 remotely crash a hidden service with an assertion failure. Anyone
8772 running a hidden service should upgrade to this version, or to some
8773 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8774 are not affected by TROVE-2017-004.)
8776 o Major bugfixes (hidden service, relay, security):
8777 - Fix a remotely triggerable assertion failure caused by receiving a
8778 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8779 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8782 o Minor features (geoip):
8783 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8786 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8787 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8788 December 2016 (of which ~126 were still functional) with a list of
8789 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8790 2017. Resolves ticket 21564.
8792 o Minor bugfixes (correctness):
8793 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8794 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8796 Changes in version 0.2.7.8 - 2017-06-08
8797 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8798 remotely crash a hidden service with an assertion failure. Anyone
8799 running a hidden service should upgrade to this version, or to some
8800 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8801 are not affected by TROVE-2017-004.)
8803 o Major bugfixes (hidden service, relay, security):
8804 - Fix a remotely triggerable assertion failure caused by receiving a
8805 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8806 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8809 o Minor features (geoip):
8810 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8813 o Minor bugfixes (correctness):
8814 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8815 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8818 Changes in version 0.2.6.12 - 2017-06-08
8819 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
8820 remotely crash a hidden service with an assertion failure. Anyone
8821 running a hidden service should upgrade to this version, or to some
8822 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8823 are not affected by TROVE-2017-004.)
8825 o Major bugfixes (hidden service, relay, security):
8826 - Fix a remotely triggerable assertion failure caused by receiving a
8827 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8828 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8831 o Minor features (geoip):
8832 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8835 o Minor bugfixes (correctness):
8836 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8837 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8839 Changes in version 0.2.5.14 - 2017-06-08
8840 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
8841 remotely crash a hidden service with an assertion failure. Anyone
8842 running a hidden service should upgrade to this version, or to some
8843 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8844 are not affected by TROVE-2017-004.)
8846 o Major bugfixes (hidden service, relay, security):
8847 - Fix a remotely triggerable assertion failure caused by receiving a
8848 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8849 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8852 o Minor features (geoip):
8853 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8856 o Minor bugfixes (correctness):
8857 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8858 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8860 Changes in version 0.2.4.29 - 2017-06-08
8861 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
8862 remotely crash a hidden service with an assertion failure. Anyone
8863 running a hidden service should upgrade to this version, or to some
8864 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8865 are not affected by TROVE-2017-004.)
8867 o Major bugfixes (hidden service, relay, security):
8868 - Fix a remotely triggerable assertion failure caused by receiving a
8869 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8870 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8873 o Minor features (geoip):
8874 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8877 o Minor bugfixes (correctness):
8878 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8879 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8882 Changes in version 0.3.1.2-alpha - 2017-05-26
8883 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
8884 fixes a few bugs found while testing 0.3.1.1-alpha, including a
8885 memory corruption bug that affected relay stability.
8887 o Major bugfixes (crash, relay):
8888 - Fix a memory-corruption bug in relays that set MyFamily.
8889 Previously, they would double-free MyFamily elements when making
8890 the next descriptor or when changing their configuration. Fixes
8891 bug 22368; bugfix on 0.3.1.1-alpha.
8893 o Minor bugfixes (logging):
8894 - Log a better message when a directory authority replies to an
8895 upload with an unexpected status code. Fixes bug 11121; bugfix
8898 o Minor bugfixes (memory leak, directory authority):
8899 - When directory authorities reject a router descriptor due to
8900 keypinning, free the router descriptor rather than leaking the
8901 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8904 Changes in version 0.3.1.1-alpha - 2017-05-22
8905 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
8906 reduces the bandwidth usage for Tor's directory protocol, adds some
8907 basic padding to resist netflow-based traffic analysis and to serve as
8908 the basis of other padding in the future, and adds rust support to the
8911 It also contains numerous other small features and improvements to
8912 security, correctness, and performance.
8914 Below are the changes since 0.3.0.7.
8916 o Major features (directory protocol):
8917 - Tor relays and authorities can now serve clients an abbreviated
8918 version of the consensus document, containing only the changes
8919 since an older consensus document that the client holds. Clients
8920 now request these documents when available. When both client and
8921 server use this new protocol, they will use far less bandwidth (up
8922 to 94% less) to keep the client's consensus up-to-date. Implements
8923 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
8924 - Tor can now compress directory traffic with lzma or with zstd
8925 compression algorithms, which can deliver better bandwidth
8926 performance. Because lzma is computationally expensive, it's only
8927 used for documents that can be compressed once and served many
8928 times. Support for these algorithms requires that tor is built
8929 with the libzstd and/or liblzma libraries available. Implements
8930 proposal 278; closes ticket 21662.
8931 - Relays now perform the more expensive compression operations, and
8932 consensus diff generation, in worker threads. This separation
8933 avoids delaying the main thread when a new consensus arrives.
8935 o Major features (experimental):
8936 - Tor can now build modules written in Rust. To turn this on, pass
8937 the "--enable-rust" flag to the configure script. It's not time to
8938 get excited yet: currently, there is no actual Rust functionality
8939 beyond some simple glue code, and a notice at startup to tell you
8940 that Rust is running. Still, we hope that programmers and
8941 packagers will try building Tor with Rust support, so that we can
8942 find issues and solve portability problems. Closes ticket 22106.
8944 o Major features (traffic analysis resistance):
8945 - Connections between clients and relays now send a padding cell in
8946 each direction every 1.5 to 9.5 seconds (tunable via consensus
8947 parameters). This padding will not resist specialized
8948 eavesdroppers, but it should be enough to make many ISPs' routine
8949 network flow logging less useful in traffic analysis against
8952 Padding is negotiated using Tor's link protocol, so both relays
8953 and clients must upgrade for this to take effect. Clients may
8954 still send padding despite the relay's version by setting
8955 ConnectionPadding 1 in torrc, and may disable padding by setting
8956 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
8957 users with the torrc option ReducedConnectionPadding. Implements
8958 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
8959 - Relays will publish 24 hour totals of padding and non-padding cell
8960 counts to their extra-info descriptors, unless PaddingStatistics 0
8961 is set in torrc. These 24 hour totals are also rounded to
8964 o Major bugfixes (connection usage):
8965 - We use NETINFO cells to try to determine if both relays involved
8966 in a connection will agree on the canonical status of that
8967 connection. We prefer the connections where this is the case for
8968 extend cells, and try to close connections where relays disagree
8969 on their canonical status early. Also, we now prefer the oldest
8970 valid connection for extend cells. These two changes should reduce
8971 the number of long-term connections that are kept open between
8972 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
8973 - Relays now log hourly statistics (look for
8974 "channel_check_for_duplicates" lines) on the total number of
8975 connections to other relays. If the number of connections per
8976 relay is unexpectedly large, this log message is at notice level.
8977 Otherwise it is at info.
8979 o Major bugfixes (entry guards):
8980 - Don't block bootstrapping when a primary bridge is offline and we
8981 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8982 21969; bugfix on 0.3.0.3-alpha.
8984 o Major bugfixes (linux TPROXY support):
8985 - Fix a typo that had prevented TPROXY-based transparent proxying
8986 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8987 Patch from "d4fq0fQAgoJ".
8989 o Minor features (security, windows):
8990 - Enable a couple of pieces of Windows hardening: one
8991 (HeapEnableTerminationOnCorruption) that has been on-by-default
8992 since Windows 8, and unavailable before Windows 7; and one
8993 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
8994 affect us, but shouldn't do any harm. Closes ticket 21953.
8996 o Minor features (config options):
8997 - Allow "%include" directives in torrc configuration files. These
8998 directives import the settings from other files, or from all the
8999 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
9000 - Make SAVECONF return an error when overwriting a torrc that has
9001 includes. Using SAVECONF with the FORCE option will allow it to
9002 overwrite torrc even if includes are used. Related to ticket 1922.
9003 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
9004 will work without the FORCE option. Related to ticket 1922.
9006 o Minor features (controller):
9007 - Warn the first time that a controller requests data in the long-
9008 deprecated 'GETINFO network-status' format. Closes ticket 21703.
9010 o Minor features (defaults):
9011 - The default value for UseCreateFast is now 0: clients which
9012 haven't yet received a consensus document will now use a proper
9013 ntor handshake to talk to their directory servers whenever they
9014 can. Closes ticket 21407.
9015 - Onion key rotation and expiry intervals are now defined as a
9016 network consensus parameter, per proposal 274. The default
9017 lifetime of an onion key is increased from 7 to 28 days. Old onion
9018 keys will expire after 7 days by default. This change will make
9019 consensus diffs much smaller, and save significant bandwidth.
9020 Closes ticket 21641.
9022 o Minor features (fallback directory list):
9023 - Update the fallback directory mirror whitelist and blacklist based
9024 on operator emails. Closes task 21121.
9025 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
9026 December 2016 (of which ~126 were still functional) with a list of
9027 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
9028 2017. Resolves ticket 21564.
9030 o Minor features (hidden services, logging):
9031 - Log a message when a hidden service descriptor has fewer
9032 introduction points than specified in
9033 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
9034 - Log a message when a hidden service reaches its introduction point
9035 circuit limit, and when that limit is reset. Follow up to ticket
9036 21594; closes ticket 21622.
9037 - Warn user if multiple entries in EntryNodes and at least one
9038 HiddenService are used together. Pinning EntryNodes along with a
9039 hidden service can be possibly harmful; for instance see ticket
9040 14917 or 21155. Closes ticket 21155.
9042 o Minor features (linux seccomp2 sandbox):
9043 - We now have a document storage backend compatible with the Linux
9044 seccomp2 sandbox. This backend is used for consensus documents and
9045 diffs between them; in the long term, we'd like to use it for
9046 unparseable directory material too. Closes ticket 21645
9047 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
9048 from 1MB to 16MB. This was necessary with the glibc allocator in
9049 order to allow worker threads to allocate more memory -- which in
9050 turn is necessary because of our new use of worker threads for
9051 compression. Closes ticket 22096.
9053 o Minor features (logging):
9054 - Log files are no longer created world-readable by default.
9055 (Previously, most distributors would store the logs in a non-
9056 world-readable location to prevent inappropriate access. This
9057 change is an extra precaution.) Closes ticket 21729; patch
9060 o Minor features (performance):
9061 - Our Keccak (SHA-3) implementation now accesses memory more
9062 efficiently, especially on little-endian systems. Closes
9064 - Add an O(1) implementation of channel_find_by_global_id(), to
9065 speed some controller functions.
9067 o Minor features (relay, configuration):
9068 - The MyFamily option may now be repeated as many times as desired,
9069 for relays that want to configure large families. Closes ticket
9070 4998; patch by Daniel Pinto.
9072 o Minor features (safety):
9073 - Add an explicit check to extrainfo_parse_entry_from_string() for
9074 NULL inputs. We don't believe this can actually happen, but it may
9075 help silence a warning from the Clang analyzer. Closes
9078 o Minor features (testing):
9079 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
9080 When Tor is compiled with this option, we disable a number of
9081 redundant memory-safety failsafes that are intended to stop bugs
9082 from becoming security issues. This makes it easier to hunt for
9083 bugs that would be security issues without the failsafes turned
9084 on. Closes ticket 21439.
9085 - Add a general event-tracing instrumentation support to Tor. This
9086 subsystem will enable developers and researchers to add fine-
9087 grained instrumentation to their Tor instances, for use when
9088 examining Tor network performance issues. There are no trace
9089 events yet, and event-tracing is off by default unless enabled at
9090 compile time. Implements ticket 13802.
9091 - Improve our version parsing tests: add tests for typical version
9092 components, add tests for invalid versions, including numeric
9093 range and non-numeric prefixes. Unit tests 21278, 21450, and
9094 21507. Partially implements 21470.
9096 o Minor bugfixes (bandwidth accounting):
9097 - Roll over monthly accounting at the configured hour and minute,
9098 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
9099 Found by Andrey Karpov with PVS-Studio.
9101 o Minor bugfixes (code correctness):
9102 - Accurately identify client connections by their lack of peer
9103 authentication. This means that we bail out earlier if asked to
9104 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
9107 o Minor bugfixes (configuration):
9108 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
9109 bug 22252; bugfix on 0.2.9.3-alpha.
9111 o Minor bugfixes (connection lifespan):
9112 - Allow more control over how long TLS connections are kept open:
9113 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
9114 single option called CircuitsAvailableTimeout. Also, allow the
9115 consensus to control the default values for both this preference
9116 and the lifespan of relay-to-relay connections. Fixes bug 17592;
9117 bugfix on 0.2.5.5-alpha.
9118 - Increase the initial circuit build timeout testing frequency, to
9119 help ensure that ReducedConnectionPadding clients finish learning
9120 a timeout before their orconn would expire. The initial testing
9121 rate was set back in the days of TAP and before the Tor Browser
9122 updater, when we had to be much more careful about new clients
9123 making lots of circuits. With this change, a circuit build timeout
9124 is learned in about 15-20 minutes, instead of 100-120 minutes.
9126 o Minor bugfixes (controller):
9127 - GETINFO onions/current and onions/detached no longer respond with
9128 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
9129 - Trigger HS descriptor events on the control port when the client
9130 fails to pick a hidden service directory for a hidden service.
9131 This can happen if all the hidden service directories are in
9132 ExcludeNodes, or they have all been queried within the last 15
9133 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
9135 o Minor bugfixes (directory authority):
9136 - When rejecting a router descriptor for running an obsolete version
9137 of Tor without ntor support, warn about the obsolete tor version,
9138 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
9139 - Prevent the shared randomness subsystem from asserting when
9140 initialized by a bridge authority with an incomplete configuration
9141 file. Fixes bug 21586; bugfix on 0.2.9.8.
9143 o Minor bugfixes (exit-side DNS):
9144 - Fix an untriggerable assertion that checked the output of a
9145 libevent DNS error, so that the assertion actually behaves as
9146 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
9147 Karpov using PVS-Studio.
9149 o Minor bugfixes (fallback directories):
9150 - Make the usage example in updateFallbackDirs.py actually work, and
9151 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
9152 - Decrease the guard flag average required to be a fallback. This
9153 allows us to keep relays that have their guard flag removed when
9154 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
9155 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
9156 bugfix on 0.2.8.1-alpha.
9157 - Make sure fallback directory mirrors have the same address, port,
9158 and relay identity key for at least 30 days before they are
9159 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
9161 o Minor bugfixes (hidden services):
9162 - Stop printing a cryptic warning when a hidden service gets a
9163 request to connect to a virtual port that it hasn't configured.
9164 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
9165 - Simplify hidden service descriptor creation by using an existing
9166 flag to check if an introduction point is established. Fixes bug
9167 21599; bugfix on 0.2.7.2-alpha.
9169 o Minor bugfixes (memory leak):
9170 - Fix a small memory leak at exit from the backtrace handler code.
9171 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
9173 o Minor bugfixes (protocol, logging):
9174 - Downgrade a log statement about unexpected relay cells from "bug"
9175 to "protocol warning", because there is at least one use case
9176 where it can be triggered by a buggy tor implementation. Fixes bug
9177 21293; bugfix on 0.1.1.14-alpha.
9179 o Minor bugfixes (testing):
9180 - Use unbuffered I/O for utility functions around the
9181 process_handle_t type. This fixes unit test failures reported on
9182 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
9183 - Make display of captured unit test log messages consistent. Fixes
9184 bug 21510; bugfix on 0.2.9.3-alpha.
9185 - Make test-network.sh always call chutney's test-network.sh.
9186 Previously, this only worked on systems which had bash installed,
9187 due to some bash-specific code in the script. Fixes bug 19699;
9188 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
9190 o Minor bugfixes (voting consistency):
9191 - Reject version numbers with non-numeric prefixes (such as +, -, or
9192 whitespace). Disallowing whitespace prevents differential version
9193 parsing between POSIX-based and Windows platforms. Fixes bug 21507
9194 and part of 21508; bugfix on 0.0.8pre1.
9196 o Minor bugfixes (windows, relay):
9197 - Resolve "Failure from drain_fd: No error" warnings on Windows
9198 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
9200 o Code simplification and refactoring:
9201 - Break up the 630-line function connection_dir_client_reached_eof()
9202 into a dozen smaller functions. This change should help
9203 maintainability and readability of the client directory code.
9204 - Isolate our use of the openssl headers so that they are only
9205 included from our crypto wrapper modules, and from tests that
9206 examine those modules' internals. Closes ticket 21841.
9207 - Simplify our API to launch directory requests, making it more
9208 extensible and less error-prone. Now it's easier to add extra
9209 headers to directory requests. Closes ticket 21646.
9210 - Our base64 decoding functions no longer overestimate the output
9211 space that they need when parsing unpadded inputs. Closes
9213 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
9214 Resolves ticket 22213.
9215 - The logic that directory caches use to spool request to clients,
9216 serving them one part at a time so as not to allocate too much
9217 memory, has been refactored for consistency. Previously there was
9218 a separate spooling implementation per type of spoolable data. Now
9219 there is one common spooling implementation, with extensible data
9220 types. Closes ticket 21651.
9221 - Tor's compression module now supports multiple backends. Part of
9222 the implementation for proposal 278; closes ticket 21663.
9225 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
9226 Closes ticket 21873.
9227 - Correct documentation about the default DataDirectory value.
9228 Closes ticket 21151.
9229 - Document the default behavior of NumEntryGuards and
9230 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
9232 - Document key=value pluggable transport arguments for Bridge lines
9233 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
9234 - Note that bandwidth-limiting options don't affect TCP headers or
9235 DNS. Closes ticket 17170.
9237 o Removed features (configuration options, all in ticket 22060):
9238 - These configuration options are now marked Obsolete, and no longer
9239 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
9240 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
9241 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
9242 in 0.2.9.2-alpha and have now been removed. The previous default
9243 behavior is now always chosen; the previous (less secure) non-
9244 default behavior is now unavailable.
9245 - CloseHSClientCircuitsImmediatelyOnTimeout and
9246 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
9247 0.2.9.2-alpha and now have been removed. HS circuits never close
9248 on circuit build timeout; they have a longer timeout period.
9249 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
9250 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
9251 (and others) to configure listen-only and advertise-only addresses.
9253 o Removed features (tools):
9254 - We've removed the tor-checkkey tool from src/tools. Long ago, we
9255 used it to help people detect RSA keys that were generated by
9256 versions of Debian affected by CVE-2008-0166. But those keys have
9257 been out of circulation for ages, and this tool is no longer
9258 required. Closes ticket 21842.
9261 Changes in version 0.3.0.7 - 2017-05-15
9262 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
9263 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
9264 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
9265 clients are not affected.
9267 o Major bugfixes (hidden service directory, security):
9268 - Fix an assertion failure in the hidden service directory code, which
9269 could be used by an attacker to remotely cause a Tor relay process to
9270 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
9271 should upgrade. This security issue is tracked as TROVE-2017-002.
9272 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
9275 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9278 o Minor features (future-proofing):
9279 - Tor no longer refuses to download microdescriptors or descriptors
9280 if they are listed as "published in the future". This change will
9281 eventually allow us to stop listing meaningful "published" dates
9282 in microdescriptor consensuses, and thereby allow us to reduce the
9283 resources required to download consensus diffs by over 50%.
9284 Implements part of ticket 21642; implements part of proposal 275.
9286 o Minor bugfixes (Linux seccomp2 sandbox):
9287 - The getpid() system call is now permitted under the Linux seccomp2
9288 sandbox, to avoid crashing with versions of OpenSSL (and other
9289 libraries) that attempt to learn the process's PID by using the
9290 syscall rather than the VDSO code. Fixes bug 21943; bugfix
9294 Changes in version 0.3.0.6 - 2017-04-26
9295 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
9297 With the 0.3.0 series, clients and relays now use Ed25519 keys to
9298 authenticate their link connections to relays, rather than the old
9299 RSA1024 keys that they used before. (Circuit crypto has been
9300 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
9301 the guard selection and replacement algorithm to behave more robustly
9302 in the presence of unreliable networks, and to resist guard-
9305 This series also includes numerous other small features and bugfixes,
9306 along with more groundwork for the upcoming hidden-services revamp.
9308 Per our stable release policy, we plan to support the Tor 0.3.0
9309 release series for at least the next nine months, or for three months
9310 after the first stable release of the 0.3.1 series: whichever is
9311 longer. If you need a release with long-term support, we recommend
9312 that you stay with the 0.2.9 series.
9314 Below are the changes since 0.3.0.5-rc. For a list of all changes
9315 since 0.2.9, see the ReleaseNotes file.
9317 o Minor features (geoip):
9318 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
9321 o Minor bugfixes (control port):
9322 - The GETINFO extra-info/digest/<digest> command was broken because
9323 of a wrong base16 decode return value check, introduced when
9324 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
9326 o Minor bugfixes (crash prevention):
9327 - Fix a (currently untriggerable, but potentially dangerous) crash
9328 bug when base32-encoding inputs whose sizes are not a multiple of
9329 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
9332 Changes in version 0.3.0.5-rc - 2017-04-05
9333 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
9334 0.3.0 release series.
9336 This is the second release candidate in the Tor 0.3.0 series, and has
9337 much fewer changes than the first. If we find no new bugs or
9338 regressions here, the first stable 0.3.0 release will be nearly
9341 o Major bugfixes (crash, directory connections):
9342 - Fix a rare crash when sending a begin cell on a circuit whose
9343 linked directory connection had already been closed. Fixes bug
9344 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
9346 o Major bugfixes (guard selection):
9347 - Fix a guard selection bug where Tor would refuse to bootstrap in
9348 some cases if the user swapped a bridge for another bridge in
9349 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
9350 Reported by "torvlnt33r".
9352 o Minor features (geoip):
9353 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
9356 o Minor bugfix (compilation):
9357 - Fix a warning when compiling hs_service.c. Previously, it had no
9358 exported symbols when compiled for libor.a, resulting in a
9359 compilation warning from clang. Fixes bug 21825; bugfix
9362 o Minor bugfixes (hidden services):
9363 - Make hidden services check for failed intro point connections,
9364 even when they have exceeded their intro point creation limit.
9365 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
9366 - Make hidden services with 8 to 10 introduction points check for
9367 failed circuits immediately after startup. Previously, they would
9368 wait for 5 minutes before performing their first checks. Fixes bug
9369 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
9371 o Minor bugfixes (memory leaks):
9372 - Fix a memory leak when using GETCONF on a port option. Fixes bug
9373 21682; bugfix on 0.3.0.3-alpha.
9375 o Minor bugfixes (relay):
9376 - Avoid a double-marked-circuit warning that could happen when we
9377 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
9380 o Minor bugfixes (tests):
9381 - Run the entry_guard_parse_from_state_full() test with the time set
9382 to a specific date. (The guard state that this test was parsing
9383 contained guards that had expired since the test was first
9384 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
9387 - Update the description of the directory server options in the
9388 manual page, to clarify that a relay no longer needs to set
9389 DirPort in order to be a directory cache. Closes ticket 21720.
9393 Changes in version 0.2.8.13 - 2017-03-03
9394 Tor 0.2.8.13 backports a security fix from later Tor
9395 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
9396 this release, if for some reason they cannot upgrade to a later
9397 release series, and if they build Tor with the --enable-expensive-hardening
9400 Note that support for Tor 0.2.8.x is ending next year: we will not issue
9401 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
9402 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9404 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9405 - Fix an integer underflow bug when comparing malformed Tor
9406 versions. This bug could crash Tor when built with
9407 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9408 0.2.9.8, which were built with -ftrapv by default. In other cases
9409 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9410 on 0.0.8pre1. Found by OSS-Fuzz.
9412 o Minor features (geoip):
9413 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9417 Changes in version 0.2.7.7 - 2017-03-03
9418 Tor 0.2.7.7 backports a number of security fixes from later Tor
9419 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
9420 this release, if for some reason they cannot upgrade to a later
9423 Note that support for Tor 0.2.7.x is ending this year: we will not issue
9424 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
9425 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9427 o Directory authority changes (backport from 0.2.8.5-rc):
9428 - Urras is no longer a directory authority. Closes ticket 19271.
9430 o Directory authority changes (backport from 0.2.9.2-alpha):
9431 - The "Tonga" bridge authority has been retired; the new bridge
9432 authority is "Bifroest". Closes tickets 19728 and 19690.
9434 o Directory authority key updates (backport from 0.2.8.1-alpha):
9435 - Update the V3 identity key for the dannenberg directory authority:
9436 it was changed on 18 November 2015. Closes task 17906. Patch
9439 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9440 - Fix a bug in parsing that could cause clients to read a single
9441 byte past the end of an allocated region. This bug could be used
9442 to cause hardened clients (built with --enable-expensive-hardening)
9443 to crash if they tried to visit a hostile hidden service. Non-
9444 hardened clients are only affected depending on the details of
9445 their platform's memory allocator. Fixes bug 21018; bugfix on
9446 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9447 2016-12-002 and as CVE-2016-1254.
9449 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9450 - Stop a crash that could occur when a client running with DNSPort
9451 received a query with multiple address types, and the first
9452 address type was not supported. Found and fixed by Scott Dial.
9453 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9454 - Prevent a class of security bugs caused by treating the contents
9455 of a buffer chunk as if they were a NUL-terminated string. At
9456 least one such bug seems to be present in all currently used
9457 versions of Tor, and would allow an attacker to remotely crash
9458 most Tor instances, especially those compiled with extra compiler
9459 hardening. With this defense in place, such bugs can't crash Tor,
9460 though we should still fix them as they occur. Closes ticket
9461 20384 (TROVE-2016-10-001).
9463 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9464 - Avoid a difficult-to-trigger heap corruption attack when extending
9465 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9466 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9467 Reported by Guido Vranken.
9469 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9470 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9471 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9473 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9474 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9475 pointer to the previous (uninitialized) key value. The impact here
9476 should be limited to a difficult-to-trigger crash, if OpenSSL is
9477 running an engine that makes key generation failures possible, or
9478 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9479 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9482 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9483 - Fix an integer underflow bug when comparing malformed Tor
9484 versions. This bug could crash Tor when built with
9485 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9486 0.2.9.8, which were built with -ftrapv by default. In other cases
9487 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9488 on 0.0.8pre1. Found by OSS-Fuzz.
9490 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9491 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9492 zero size. Check size argument to memwipe() for underflow. Fixes
9493 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9496 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9497 - Make Tor survive errors involving connections without a
9498 corresponding event object. Previously we'd fail with an
9499 assertion; now we produce a log message. Related to bug 16248.
9501 o Minor features (geoip):
9502 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9506 Changes in version 0.2.6.11 - 2017-03-03
9507 Tor 0.2.6.11 backports a number of security fixes from later Tor
9508 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
9509 this release, if for some reason they cannot upgrade to a later
9512 Note that support for Tor 0.2.6.x is ending this year: we will not issue
9513 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
9514 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9516 o Directory authority changes (backport from 0.2.8.5-rc):
9517 - Urras is no longer a directory authority. Closes ticket 19271.
9519 o Directory authority changes (backport from 0.2.9.2-alpha):
9520 - The "Tonga" bridge authority has been retired; the new bridge
9521 authority is "Bifroest". Closes tickets 19728 and 19690.
9523 o Directory authority key updates (backport from 0.2.8.1-alpha):
9524 - Update the V3 identity key for the dannenberg directory authority:
9525 it was changed on 18 November 2015. Closes task 17906. Patch
9528 o Major features (security fixes, backport from 0.2.9.4-alpha):
9529 - Prevent a class of security bugs caused by treating the contents
9530 of a buffer chunk as if they were a NUL-terminated string. At
9531 least one such bug seems to be present in all currently used
9532 versions of Tor, and would allow an attacker to remotely crash
9533 most Tor instances, especially those compiled with extra compiler
9534 hardening. With this defense in place, such bugs can't crash Tor,
9535 though we should still fix them as they occur. Closes ticket
9536 20384 (TROVE-2016-10-001).
9538 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9539 - Fix a bug in parsing that could cause clients to read a single
9540 byte past the end of an allocated region. This bug could be used
9541 to cause hardened clients (built with --enable-expensive-hardening)
9542 to crash if they tried to visit a hostile hidden service. Non-
9543 hardened clients are only affected depending on the details of
9544 their platform's memory allocator. Fixes bug 21018; bugfix on
9545 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9546 2016-12-002 and as CVE-2016-1254.
9548 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9549 - Stop a crash that could occur when a client running with DNSPort
9550 received a query with multiple address types, and the first
9551 address type was not supported. Found and fixed by Scott Dial.
9552 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9554 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9555 - Fix an error that could cause us to read 4 bytes before the
9556 beginning of an openssl string. This bug could be used to cause
9557 Tor to crash on systems with unusual malloc implementations, or
9558 systems with unusual hardening installed. Fixes bug 17404; bugfix
9561 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9562 - Avoid a difficult-to-trigger heap corruption attack when extending
9563 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9564 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9565 Reported by Guido Vranken.
9567 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9568 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9569 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9571 o Major bugfixes (guard selection, backport from 0.2.7.6):
9572 - Actually look at the Guard flag when selecting a new directory
9573 guard. When we implemented the directory guard design, we
9574 accidentally started treating all relays as if they have the Guard
9575 flag during guard selection, leading to weaker anonymity and worse
9576 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9579 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9580 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9581 pointer to the previous (uninitialized) key value. The impact here
9582 should be limited to a difficult-to-trigger crash, if OpenSSL is
9583 running an engine that makes key generation failures possible, or
9584 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9585 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9588 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9589 - Fix an integer underflow bug when comparing malformed Tor
9590 versions. This bug could crash Tor when built with
9591 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9592 0.2.9.8, which were built with -ftrapv by default. In other cases
9593 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9594 on 0.0.8pre1. Found by OSS-Fuzz.
9596 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9597 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9598 zero size. Check size argument to memwipe() for underflow. Fixes
9599 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9602 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9603 - Make Tor survive errors involving connections without a
9604 corresponding event object. Previously we'd fail with an
9605 assertion; now we produce a log message. Related to bug 16248.
9607 o Minor features (geoip):
9608 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9611 o Minor bugfixes (compilation, backport from 0.2.7.6):
9612 - Fix a compilation warning with Clang 3.6: Do not check the
9613 presence of an address which can never be NULL. Fixes bug 17781.
9616 Changes in version 0.2.5.13 - 2017-03-03
9617 Tor 0.2.5.13 backports a number of security fixes from later Tor
9618 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
9619 this release, if for some reason they cannot upgrade to a later
9622 Note that support for Tor 0.2.5.x is ending next year: we will not issue
9623 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
9624 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9626 o Directory authority changes (backport from 0.2.8.5-rc):
9627 - Urras is no longer a directory authority. Closes ticket 19271.
9629 o Directory authority changes (backport from 0.2.9.2-alpha):
9630 - The "Tonga" bridge authority has been retired; the new bridge
9631 authority is "Bifroest". Closes tickets 19728 and 19690.
9633 o Directory authority key updates (backport from 0.2.8.1-alpha):
9634 - Update the V3 identity key for the dannenberg directory authority:
9635 it was changed on 18 November 2015. Closes task 17906. Patch
9638 o Major features (security fixes, backport from 0.2.9.4-alpha):
9639 - Prevent a class of security bugs caused by treating the contents
9640 of a buffer chunk as if they were a NUL-terminated string. At
9641 least one such bug seems to be present in all currently used
9642 versions of Tor, and would allow an attacker to remotely crash
9643 most Tor instances, especially those compiled with extra compiler
9644 hardening. With this defense in place, such bugs can't crash Tor,
9645 though we should still fix them as they occur. Closes ticket
9646 20384 (TROVE-2016-10-001).
9648 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9649 - Fix a bug in parsing that could cause clients to read a single
9650 byte past the end of an allocated region. This bug could be used
9651 to cause hardened clients (built with --enable-expensive-hardening)
9652 to crash if they tried to visit a hostile hidden service. Non-
9653 hardened clients are only affected depending on the details of
9654 their platform's memory allocator. Fixes bug 21018; bugfix on
9655 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9656 2016-12-002 and as CVE-2016-1254.
9658 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9659 - Stop a crash that could occur when a client running with DNSPort
9660 received a query with multiple address types, and the first
9661 address type was not supported. Found and fixed by Scott Dial.
9662 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9664 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9665 - Fix an error that could cause us to read 4 bytes before the
9666 beginning of an openssl string. This bug could be used to cause
9667 Tor to crash on systems with unusual malloc implementations, or
9668 systems with unusual hardening installed. Fixes bug 17404; bugfix
9671 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9672 - Avoid a difficult-to-trigger heap corruption attack when extending
9673 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9674 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9675 Reported by Guido Vranken.
9677 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9678 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9679 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9681 o Major bugfixes (guard selection, backport from 0.2.7.6):
9682 - Actually look at the Guard flag when selecting a new directory
9683 guard. When we implemented the directory guard design, we
9684 accidentally started treating all relays as if they have the Guard
9685 flag during guard selection, leading to weaker anonymity and worse
9686 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9689 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9690 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9691 pointer to the previous (uninitialized) key value. The impact here
9692 should be limited to a difficult-to-trigger crash, if OpenSSL is
9693 running an engine that makes key generation failures possible, or
9694 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9695 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9698 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9699 - Fix an integer underflow bug when comparing malformed Tor
9700 versions. This bug could crash Tor when built with
9701 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9702 0.2.9.8, which were built with -ftrapv by default. In other cases
9703 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9704 on 0.0.8pre1. Found by OSS-Fuzz.
9706 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9707 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9708 zero size. Check size argument to memwipe() for underflow. Fixes
9709 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9712 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9713 - Make Tor survive errors involving connections without a
9714 corresponding event object. Previously we'd fail with an
9715 assertion; now we produce a log message. Related to bug 16248.
9717 o Minor features (geoip):
9718 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9721 o Minor bugfixes (compilation, backport from 0.2.7.6):
9722 - Fix a compilation warning with Clang 3.6: Do not check the
9723 presence of an address which can never be NULL. Fixes bug 17781.
9725 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
9726 - Check for failures from crypto_early_init, and refuse to continue.
9727 A previous typo meant that we could keep going with an
9728 uninitialized crypto library, and would have OpenSSL initialize
9729 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9730 when implementing ticket 4900. Patch by "teor".
9732 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9733 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9734 a client authorized hidden service. Fixes bug 15823; bugfix
9738 Changes in version 0.2.4.28 - 2017-03-03
9739 Tor 0.2.4.28 backports a number of security fixes from later Tor
9740 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
9741 this release, if for some reason they cannot upgrade to a later
9744 Note that support for Tor 0.2.4.x is ending soon: we will not issue
9745 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
9746 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
9748 o Directory authority changes (backport from 0.2.8.5-rc):
9749 - Urras is no longer a directory authority. Closes ticket 19271.
9751 o Directory authority changes (backport from 0.2.9.2-alpha):
9752 - The "Tonga" bridge authority has been retired; the new bridge
9753 authority is "Bifroest". Closes tickets 19728 and 19690.
9755 o Directory authority key updates (backport from 0.2.8.1-alpha):
9756 - Update the V3 identity key for the dannenberg directory authority:
9757 it was changed on 18 November 2015. Closes task 17906. Patch
9760 o Major features (security fixes, backport from 0.2.9.4-alpha):
9761 - Prevent a class of security bugs caused by treating the contents
9762 of a buffer chunk as if they were a NUL-terminated string. At
9763 least one such bug seems to be present in all currently used
9764 versions of Tor, and would allow an attacker to remotely crash
9765 most Tor instances, especially those compiled with extra compiler
9766 hardening. With this defense in place, such bugs can't crash Tor,
9767 though we should still fix them as they occur. Closes ticket
9768 20384 (TROVE-2016-10-001).
9770 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9771 - Fix a bug in parsing that could cause clients to read a single
9772 byte past the end of an allocated region. This bug could be used
9773 to cause hardened clients (built with --enable-expensive-hardening)
9774 to crash if they tried to visit a hostile hidden service. Non-
9775 hardened clients are only affected depending on the details of
9776 their platform's memory allocator. Fixes bug 21018; bugfix on
9777 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9778 2016-12-002 and as CVE-2016-1254.
9780 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9781 - Fix an error that could cause us to read 4 bytes before the
9782 beginning of an openssl string. This bug could be used to cause
9783 Tor to crash on systems with unusual malloc implementations, or
9784 systems with unusual hardening installed. Fixes bug 17404; bugfix
9787 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9788 - Avoid a difficult-to-trigger heap corruption attack when extending
9789 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9790 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9791 Reported by Guido Vranken.
9793 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9794 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9795 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9797 o Major bugfixes (guard selection, backport from 0.2.7.6):
9798 - Actually look at the Guard flag when selecting a new directory
9799 guard. When we implemented the directory guard design, we
9800 accidentally started treating all relays as if they have the Guard
9801 flag during guard selection, leading to weaker anonymity and worse
9802 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9805 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9806 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9807 pointer to the previous (uninitialized) key value. The impact here
9808 should be limited to a difficult-to-trigger crash, if OpenSSL is
9809 running an engine that makes key generation failures possible, or
9810 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9811 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9814 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9815 - Fix an integer underflow bug when comparing malformed Tor
9816 versions. This bug could crash Tor when built with
9817 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9818 0.2.9.8, which were built with -ftrapv by default. In other cases
9819 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9820 on 0.0.8pre1. Found by OSS-Fuzz.
9822 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9823 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9824 zero size. Check size argument to memwipe() for underflow. Fixes
9825 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9828 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9829 - Make Tor survive errors involving connections without a
9830 corresponding event object. Previously we'd fail with an
9831 assertion; now we produce a log message. Related to bug 16248.
9833 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
9834 - Make it harder for attackers to overload hidden services with
9835 introductions, by blocking multiple introduction requests on the
9836 same circuit. Resolves ticket 15515.
9838 o Minor features (geoip):
9839 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9842 o Minor bugfixes (compilation, backport from 0.2.7.6):
9843 - Fix a compilation warning with Clang 3.6: Do not check the
9844 presence of an address which can never be NULL. Fixes bug 17781.
9846 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9847 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9848 a client authorized hidden service. Fixes bug 15823; bugfix
9852 Changes in version 0.3.0.4-rc - 2017-03-01
9853 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
9854 0.3.0 release series, and introduces a few reliability features to
9855 keep them from coming back.
9857 This is the first release candidate in the Tor 0.3.0 series. If we
9858 find no new bugs or regressions here, the first stable 0.3.0 release
9859 will be nearly identical to it.
9861 o Major bugfixes (bridges):
9862 - When the same bridge is configured multiple times with the same
9863 identity, but at different address:port combinations, treat those
9864 bridge instances as separate guards. This fix restores the ability
9865 of clients to configure the same bridge with multiple pluggable
9866 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
9868 o Major bugfixes (hidden service directory v3):
9869 - Stop crashing on a failed v3 hidden service descriptor lookup
9870 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
9872 o Major bugfixes (parsing):
9873 - When parsing a malformed content-length field from an HTTP
9874 message, do not read off the end of the buffer. This bug was a
9875 potential remote denial-of-service attack against Tor clients and
9876 relays. A workaround was released in October 2016, to prevent this
9877 bug from crashing Tor. This is a fix for the underlying issue,
9878 which should no longer matter (if you applied the earlier patch).
9879 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
9880 using AFL (http://lcamtuf.coredump.cx/afl/).
9881 - Fix an integer underflow bug when comparing malformed Tor
9882 versions. This bug could crash Tor when built with
9883 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9884 0.2.9.8, which were built with -ftrapv by default. In other cases
9885 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9886 on 0.0.8pre1. Found by OSS-Fuzz.
9888 o Minor feature (protocol versioning):
9889 - Add new protocol version for proposal 224. HSIntro now advertises
9890 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
9892 o Minor features (directory authorities):
9893 - Directory authorities now reject descriptors that claim to be
9894 malformed versions of Tor. Helps prevent exploitation of
9896 - Reject version numbers with components that exceed INT32_MAX.
9897 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
9898 Fixes bug 21450; bugfix on 0.0.8pre1.
9899 - Directory authorities now reject relays running versions
9900 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
9901 suffer from bug 20499 and don't keep their consensus cache
9902 up-to-date. Resolves ticket 20509.
9904 o Minor features (geoip):
9905 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9908 o Minor features (reliability, crash):
9909 - Try better to detect problems in buffers where they might grow (or
9910 think they have grown) over 2 GB in size. Diagnostic for
9913 o Minor features (testing):
9914 - During 'make test-network-all', if tor logs any warnings, ask
9915 chutney to output them. Requires a recent version of chutney with
9916 the 21572 patch. Implements 21570.
9918 o Minor bugfixes (certificate expiration time):
9919 - Avoid using link certificates that don't become valid till some
9920 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
9922 o Minor bugfixes (code correctness):
9923 - Repair a couple of (unreachable or harmless) cases of the risky
9924 comparison-by-subtraction pattern that caused bug 21278.
9925 - Remove a redundant check for the UseEntryGuards option from the
9926 options_transition_affects_guards() function. Fixes bug 21492;
9927 bugfix on 0.3.0.1-alpha.
9929 o Minor bugfixes (directory mirrors):
9930 - Allow relays to use directory mirrors without a DirPort: these
9931 relays need to be contacted over their ORPorts using a begindir
9932 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
9933 - Clarify the message logged when a remote relay is unexpectedly
9934 missing an ORPort or DirPort: users were confusing this with a
9935 local port. Fixes another case of bug 20711; bugfix
9938 o Minor bugfixes (guards):
9939 - Don't warn about a missing guard state on timeout-measurement
9940 circuits: they aren't supposed to be using guards. Fixes an
9941 instance of bug 21007; bugfix on 0.3.0.1-alpha.
9942 - Silence a BUG() warning when attempting to use a guard whose
9943 descriptor we don't know, and make this scenario less likely to
9944 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
9946 o Minor bugfixes (hidden service):
9947 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
9948 cells. Previously, we were using sizeof() on a pointer, instead of
9949 the real destination buffer. Fortunately, that value was only used
9950 to double-check that there was enough room--which was already
9951 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
9953 o Minor bugfixes (testing):
9954 - Fix Raspbian build issues related to missing socket errno in
9955 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
9957 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
9958 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
9959 - Use bash in src/test/test-network.sh. This ensures we reliably
9960 call chutney's newer tools/test-network.sh when available. Fixes
9961 bug 21562; bugfix on 0.2.9.1-alpha.
9964 - Small fixes to the fuzzing documentation. Closes ticket 21472.
9967 Changes in version 0.2.9.10 - 2017-03-01
9968 Tor 0.2.9.10 backports a security fix from later Tor release. It also
9969 includes fixes for some major issues affecting directory authorities,
9970 LibreSSL compatibility, and IPv6 correctness.
9972 The Tor 0.2.9.x release series is now marked as a long-term-support
9973 series. We intend to backport security fixes to 0.2.9.x until at
9974 least January of 2020.
9976 o Major bugfixes (directory authority, 0.3.0.3-alpha):
9977 - During voting, when marking a relay as a probable sybil, do not
9978 clear its BadExit flag: sybils can still be bad in other ways
9979 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9982 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
9983 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9984 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9985 exit policy rejects that port on more than an IPv6 /16 of
9986 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9987 which rejected a relay's own IPv6 address by default. Fixes bug
9988 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9990 o Major bugfixes (parsing, also in 0.3.0.4-rc):
9991 - Fix an integer underflow bug when comparing malformed Tor
9992 versions. This bug could crash Tor when built with
9993 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9994 0.2.9.8, which were built with -ftrapv by default. In other cases
9995 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9996 on 0.0.8pre1. Found by OSS-Fuzz.
9998 o Minor features (directory authorities, also in 0.3.0.4-rc):
9999 - Directory authorities now reject descriptors that claim to be
10000 malformed versions of Tor. Helps prevent exploitation of
10002 - Reject version numbers with components that exceed INT32_MAX.
10003 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
10004 Fixes bug 21450; bugfix on 0.0.8pre1.
10006 o Minor features (geoip):
10007 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
10010 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
10011 - Autoconf now checks to determine if OpenSSL structures are opaque,
10012 instead of explicitly checking for OpenSSL version numbers. Part
10014 - Support building with recent LibreSSL code that uses opaque
10015 structures. Closes ticket 21359.
10017 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
10018 - Repair a couple of (unreachable or harmless) cases of the risky
10019 comparison-by-subtraction pattern that caused bug 21278.
10021 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
10022 - The tor-resolve command line tool now rejects hostnames over 255
10023 characters in length. Previously, it would silently truncate them,
10024 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
10025 Patch by "junglefowl".
10028 Changes in version 0.3.0.3-alpha - 2017-02-03
10029 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
10030 0.3.0.x development series, including some that could cause
10031 authorities to behave badly. There is also a fix for a longstanding
10032 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
10033 includes some smaller features and bugfixes.
10035 The Tor 0.3.0.x release series is now in patch-freeze: no additional
10036 features will be considered for inclusion in 0.3.0.x. We suspect that
10037 some bugs will probably remain, however, and we encourage people to
10040 o Major bugfixes (directory authority):
10041 - During voting, when marking a relay as a probable sybil, do not
10042 clear its BadExit flag: sybils can still be bad in other ways
10043 too. (We still clear the other flags.) Fixes bug 21108; bugfix
10045 - When deciding whether we have just found a router to be reachable,
10046 do not penalize it for not having performed an Ed25519 link
10047 handshake if it does not claim to support an Ed25519 handshake.
10048 Previously, we would treat such relays as non-running. Fixes bug
10049 21107; bugfix on 0.3.0.1-alpha.
10051 o Major bugfixes (entry guards):
10052 - Stop trying to build circuits through entry guards for which we
10053 have no descriptor. Also, stop crashing in the case that we *do*
10054 accidentally try to build a circuit in such a state. Fixes bug
10055 21242; bugfix on 0.3.0.1-alpha.
10057 o Major bugfixes (IPv6 Exits):
10058 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
10059 any IPv6 addresses. Instead, only reject a port over IPv6 if the
10060 exit policy rejects that port on more than an IPv6 /16 of
10061 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
10062 which rejected a relay's own IPv6 address by default. Fixes bug
10063 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
10065 o Minor feature (client):
10066 - Enable IPv6 traffic on the SocksPort by default. To disable this,
10067 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
10069 o Minor feature (fallback scripts):
10070 - Add a check_existing mode to updateFallbackDirs.py, which checks
10071 if fallbacks in the hard-coded list are working. Closes ticket
10072 20174. Patch by haxxpop.
10074 o Minor features (ciphersuite selection):
10075 - Clients now advertise a list of ciphersuites closer to the ones
10076 preferred by Firefox. Closes part of ticket 15426.
10077 - Allow relays to accept a wider range of ciphersuites, including
10078 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
10080 o Minor features (controller, configuration):
10081 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
10082 and so on, now comes with a __*Port variant that will not be saved
10083 to the torrc file by the controller's SAVECONF command. This
10084 change allows TorBrowser to set up a single-use domain socket for
10085 each time it launches Tor. Closes ticket 20956.
10086 - The GETCONF command can now query options that may only be
10087 meaningful in context-sensitive lists. This allows the controller
10088 to query the mixed SocksPort/__SocksPort style options introduced
10089 in feature 20956. Implements ticket 21300.
10091 o Minor features (portability, compilation):
10092 - Autoconf now checks to determine if OpenSSL structures are opaque,
10093 instead of explicitly checking for OpenSSL version numbers. Part
10095 - Support building with recent LibreSSL code that uses opaque
10096 structures. Closes ticket 21359.
10098 o Minor features (relay):
10099 - We now allow separation of exit and relay traffic to different
10100 source IP addresses, using the OutboundBindAddressExit and
10101 OutboundBindAddressOR options respectively. Closes ticket 17975.
10102 Written by Michael Sonntag.
10104 o Minor bugfix (logging):
10105 - Don't recommend the use of Tor2web in non-anonymous mode.
10106 Recommending Tor2web is a bad idea because the client loses all
10107 anonymity. Tor2web should only be used in specific cases by users
10108 who *know* and understand the issues. Fixes bug 21294; bugfix
10111 o Minor bugfixes (client):
10112 - Always recover from failures in extend_info_from_node(), in an
10113 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
10114 bugfix on 0.2.3.1-alpha.
10116 o Minor bugfixes (client, entry guards):
10117 - Fix a bug warning (with backtrace) when we fail a channel that
10118 circuits to fallback directories on it. Fixes bug 21128; bugfix
10120 - Fix a spurious bug warning (with backtrace) when removing an
10121 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
10122 - Fix a bug of the new guard algorithm where tor could stall for up
10123 to 10 minutes before retrying a guard after a long period of no
10124 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
10125 - Do not try to build circuits until we have descriptors for our
10126 primary entry guards. Related to fix for bug 21242.
10128 o Minor bugfixes (configure, autoconf):
10129 - Rename the configure option --enable-expensive-hardening to
10130 --enable-fragile-hardening. Expensive hardening makes the tor
10131 daemon abort when some kinds of issues are detected. Thus, it
10132 makes tor more at risk of remote crashes but safer against RCE or
10133 heartbleed bug category. We now try to explain this issue in a
10134 message from the configure script. Fixes bug 21290; bugfix
10137 o Minor bugfixes (controller):
10138 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
10139 20824; bugfix on 0.3.0.1-alpha.
10141 o Minor bugfixes (hidden service):
10142 - Clean up the code for expiring intro points with no associated
10143 circuits. It was causing, rarely, a service with some expiring
10144 introduction points to not open enough additional introduction
10145 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
10146 - Stop setting the torrc option HiddenServiceStatistics to "0" just
10147 because we're not a bridge or relay. Instead, we preserve whatever
10148 value the user set (or didn't set). Fixes bug 21150; bugfix
10150 - Resolve two possible underflows which could lead to creating and
10151 closing a lot of introduction point circuits in a non-stop loop.
10152 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
10154 o Minor bugfixes (portability):
10155 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
10156 It is supported by OpenBSD itself, and also by most OpenBSD
10157 variants (such as Bitrig). Fixes bug 20980; bugfix
10159 - When mapping a file of length greater than SIZE_MAX, do not
10160 silently truncate its contents. This issue could occur on 32 bit
10161 systems with large file support and files which are larger than 4
10162 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
10164 o Minor bugfixes (tor-resolve):
10165 - The tor-resolve command line tool now rejects hostnames over 255
10166 characters in length. Previously, it would silently truncate them,
10167 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
10168 Patch by "junglefowl".
10170 o Minor bugfixes (Windows services):
10171 - Be sure to initialize the monotonic time subsystem before using
10172 it, even when running as an NT service. Fixes bug 21356; bugfix
10176 Changes in version 0.3.0.2-alpha - 2017-01-23
10177 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
10178 cause relays and clients to crash, even if they were not built with
10179 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10180 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10181 version should upgrade.
10183 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
10184 time-to-live values, makes directory authorities enforce the 1-to-1
10185 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
10186 client-side onion service reachability bug, does better at selecting
10187 the set of fallback directories, and more.
10189 o Major bugfixes (security, also in 0.2.9.9):
10190 - Downgrade the "-ftrapv" option from "always on" to "only on when
10191 --enable-expensive-hardening is provided." This hardening option, like
10192 others, can turn survivable bugs into crashes--and having it on by
10193 default made a (relatively harmless) integer overflow bug into a
10194 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
10197 o Major features (security):
10198 - Change the algorithm used to decide DNS TTLs on client and server
10199 side, to better resist DNS-based correlation attacks like the
10200 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10201 Feamster. Now relays only return one of two possible DNS TTL
10202 values, and clients are willing to believe DNS TTL values up to 3
10203 hours long. Closes ticket 19769.
10205 o Major features (directory authority, security):
10206 - The default for AuthDirPinKeys is now 1: directory authorities
10207 will reject relays where the RSA identity key matches a previously
10208 seen value, but the Ed25519 key has changed. Closes ticket 18319.
10210 o Major bugfixes (client, guard, crash):
10211 - In circuit_get_global_origin_list(), return the actual list of
10212 origin circuits. The previous version of this code returned the
10213 list of all the circuits, and could have caused strange bugs,
10214 including possible crashes. Fixes bug 21118; bugfix
10217 o Major bugfixes (client, onion service, also in 0.2.9.9):
10218 - Fix a client-side onion service reachability bug, where multiple
10219 socks requests to an onion service (or a single slow request)
10220 could cause us to mistakenly mark some of the service's
10221 introduction points as failed, and we cache that failure so
10222 eventually we run out and can't reach the service. Also resolves a
10223 mysterious "Remote server sent bogus reason code 65021" log
10224 warning. The bug was introduced in ticket 17218, where we tried to
10225 remember the circuit end reason as a uint16_t, which mangled
10226 negative values. Partially fixes bug 21056 and fixes bug 20307;
10227 bugfix on 0.2.8.1-alpha.
10229 o Major bugfixes (DNS):
10230 - Fix a bug that prevented exit nodes from caching DNS records for
10231 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10233 o Minor features (controller):
10234 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
10235 shared-random values to the controller. Closes ticket 19925.
10237 o Minor features (entry guards):
10238 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
10239 break regression tests.
10240 - Require UseEntryGuards when UseBridges is set, in order to make
10241 sure bridges aren't bypassed. Resolves ticket 20502.
10243 o Minor features (fallback directories):
10244 - Select 200 fallback directories for each release. Closes
10246 - Allow 3 fallback relays per operator, which is safe now that we
10247 are choosing 200 fallback relays. Closes ticket 20912.
10248 - Exclude relays affected by bug 20499 from the fallback list.
10249 Exclude relays from the fallback list if they are running versions
10250 known to be affected by bug 20499, or if in our tests they deliver
10251 a stale consensus (i.e. one that expired more than 24 hours ago).
10252 Closes ticket 20539.
10253 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
10255 - Require fallback directories to have the same address and port for
10256 7 days (now that we have enough relays with this stability).
10257 Relays whose OnionOO stability timer is reset on restart by bug
10258 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
10259 this issue. Closes ticket 20880; maintains short-term fix
10261 - Require fallbacks to have flags for 90% of the time (weighted
10262 decaying average), rather than 95%. This allows at least 73% of
10263 clients to bootstrap in the first 5 seconds without contacting an
10264 authority. Part of ticket 18828.
10265 - Annotate updateFallbackDirs.py with the bandwidth and consensus
10266 weight for each candidate fallback. Closes ticket 20878.
10267 - Make it easier to change the output sort order of fallbacks.
10268 Closes ticket 20822.
10269 - Display the relay fingerprint when downloading consensuses from
10270 fallbacks. Closes ticket 20908.
10272 o Minor features (geoip, also in 0.2.9.9):
10273 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10276 o Minor features (next-gen onion service directories):
10277 - Remove the "EnableOnionServicesV3" consensus parameter that we
10278 introduced in 0.3.0.1-alpha: relays are now always willing to act
10279 as v3 onion service directories. Resolves ticket 19899.
10281 o Minor features (linting):
10282 - Enhance the changes file linter to warn on Tor versions that are
10283 prefixed with "tor-". Closes ticket 21096.
10285 o Minor features (logging):
10286 - In several places, describe unset ed25519 keys as "<unset>",
10287 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
10289 o Minor bugfix (control protocol):
10290 - The reply to a "GETINFO config/names" request via the control
10291 protocol now spells the type "Dependent" correctly. This is a
10292 breaking change in the control protocol. (The field seems to be
10293 ignored by the most common known controllers.) Fixes bug 18146;
10294 bugfix on 0.1.1.4-alpha.
10296 o Minor bugfixes (bug resilience):
10297 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
10298 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
10299 Hans Jerry Illikainen.
10301 o Minor bugfixes (build):
10302 - Replace obsolete Autoconf macros with their modern equivalent and
10303 prevent similar issues in the future. Fixes bug 20990; bugfix
10306 o Minor bugfixes (client, guards):
10307 - Fix bug where Tor would think that there are circuits waiting for
10308 better guards even though those circuits have been freed. Fixes
10309 bug 21142; bugfix on 0.3.0.1-alpha.
10311 o Minor bugfixes (config):
10312 - Don't assert on startup when trying to get the options list and
10313 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
10314 options so of course they aren't ready yet. Fixes bug 21062;
10315 bugfix on 0.2.9.3-alpha.
10317 o Minor bugfixes (controller):
10318 - Make the GETINFO interface for inquiring about entry guards
10319 support the new guards backend. Fixes bug 20823; bugfix
10322 o Minor bugfixes (dead code):
10323 - Remove a redundant check for PidFile changes at runtime in
10324 options_transition_allowed(): this check is already performed
10325 regardless of whether the sandbox is active. Fixes bug 21123;
10326 bugfix on 0.2.5.4-alpha.
10328 o Minor bugfixes (documentation):
10329 - Update the tor manual page to document every option that can not
10330 be changed while tor is running. Fixes bug 21122.
10332 o Minor bugfixes (fallback directories):
10333 - Stop failing when a relay has no uptime data in
10334 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
10335 - Avoid checking fallback candidates' DirPorts if they are down in
10336 OnionOO. When a relay operator has multiple relays, this
10337 prioritizes relays that are up over relays that are down. Fixes
10338 bug 20926; bugfix on 0.2.8.3-alpha.
10339 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
10340 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
10342 o Minor bugfixes (guards, bootstrapping):
10343 - When connecting to a directory guard during bootstrap, do not mark
10344 the guard as successful until we receive a good-looking directory
10345 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
10347 o Minor bugfixes (onion services):
10348 - Fix the config reload pruning of old vs new services so it
10349 actually works when both ephemeral and non-ephemeral services are
10350 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
10351 - Allow the number of introduction points to be as low as 0, rather
10352 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
10354 o Minor bugfixes (IPv6):
10355 - Make IPv6-using clients try harder to find an IPv6 directory
10356 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
10357 - When IPv6 addresses have not been downloaded yet (microdesc
10358 consensus documents don't list relay IPv6 addresses), use hard-
10359 coded addresses for authorities, fallbacks, and configured
10360 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
10361 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
10363 o Minor bugfixes (memory leaks):
10364 - Fix a memory leak when configuring hidden services. Fixes bug
10365 20987; bugfix on 0.3.0.1-alpha.
10367 o Minor bugfixes (portability, also in 0.2.9.9):
10368 - Avoid crashing when Tor is built using headers that contain
10369 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10370 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10372 - Fix Libevent detection on platforms without Libevent 1 headers
10373 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10375 o Minor bugfixes (relay):
10376 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
10377 initializing the keys would reset the DataDirectory to 0700
10378 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
10379 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
10381 o Minor bugfixes (testing):
10382 - Remove undefined behavior from the backtrace generator by removing
10383 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
10385 o Minor bugfixes (unit tests):
10386 - Allow the unit tests to pass even when DNS lookups of bogus
10387 addresses do not fail as expected. Fixes bug 20862 and 20863;
10388 bugfix on unit tests introduced in 0.2.8.1-alpha
10389 through 0.2.9.4-alpha.
10391 o Code simplification and refactoring:
10392 - Refactor code to manipulate global_origin_circuit_list into
10393 separate functions. Closes ticket 20921.
10395 o Documentation (formatting):
10396 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
10397 blocks were incorrectly appearing. Closes ticket 20885.
10399 o Documentation (man page):
10400 - Clarify many options in tor.1 and add some min/max values for
10401 HiddenService options. Closes ticket 21058.
10404 Changes in version 0.2.9.9 - 2017-01-23
10405 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
10406 cause relays and clients to crash, even if they were not built with
10407 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10408 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10409 version should upgrade.
10411 This release also resolves a client-side onion service reachability
10412 bug, and resolves a pair of small portability issues.
10414 o Major bugfixes (security):
10415 - Downgrade the "-ftrapv" option from "always on" to "only on when
10416 --enable-expensive-hardening is provided." This hardening option,
10417 like others, can turn survivable bugs into crashes -- and having
10418 it on by default made a (relatively harmless) integer overflow bug
10419 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
10420 bugfix on 0.2.9.1-alpha.
10422 o Major bugfixes (client, onion service):
10423 - Fix a client-side onion service reachability bug, where multiple
10424 socks requests to an onion service (or a single slow request)
10425 could cause us to mistakenly mark some of the service's
10426 introduction points as failed, and we cache that failure so
10427 eventually we run out and can't reach the service. Also resolves a
10428 mysterious "Remote server sent bogus reason code 65021" log
10429 warning. The bug was introduced in ticket 17218, where we tried to
10430 remember the circuit end reason as a uint16_t, which mangled
10431 negative values. Partially fixes bug 21056 and fixes bug 20307;
10432 bugfix on 0.2.8.1-alpha.
10434 o Minor features (geoip):
10435 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10438 o Minor bugfixes (portability):
10439 - Avoid crashing when Tor is built using headers that contain
10440 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10441 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10443 - Fix Libevent detection on platforms without Libevent 1 headers
10444 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10447 Changes in version 0.3.0.1-alpha - 2016-12-19
10448 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
10449 series. It strengthens Tor's link and circuit handshakes by
10450 identifying relays by their Ed25519 keys, improves the algorithm that
10451 clients use to choose and maintain their list of guards, and includes
10452 additional backend support for the next-generation hidden service
10453 design. It also contains numerous other small features and
10454 improvements to security, correctness, and performance.
10456 Below are the changes since 0.2.9.8.
10458 o Major features (guard selection algorithm):
10459 - Tor's guard selection algorithm has been redesigned from the
10460 ground up, to better support unreliable networks and restrictive
10461 sets of entry nodes, and to better resist guard-capture attacks by
10462 hostile local networks. Implements proposal 271; closes
10465 o Major features (next-generation hidden services):
10466 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
10467 prop224 aka "Next Generation Hidden Services". Service and clients
10468 don't use this functionality yet. Closes ticket 19043. Based on
10469 initial code by Alec Heifetz.
10470 - Relays now support the HSDir version 3 protocol, so that they can
10471 can store and serve v3 descriptors. This is part of the next-
10472 generation onion service work detailed in proposal 224. Closes
10475 o Major features (protocol, ed25519 identity keys):
10476 - Relays now use Ed25519 to prove their Ed25519 identities and to
10477 one another, and to clients. This algorithm is faster and more
10478 secure than the RSA-based handshake we've been doing until now.
10479 Implements the second big part of proposal 220; Closes
10481 - Clients now support including Ed25519 identity keys in the EXTEND2
10482 cells they generate. By default, this is controlled by a consensus
10483 parameter, currently disabled. You can turn this feature on for
10484 testing by setting ExtendByEd25519ID in your configuration. This
10485 might make your traffic appear different than the traffic
10486 generated by other users, however. Implements part of ticket
10487 15056; part of proposal 220.
10488 - Relays now understand requests to extend to other relays by their
10489 Ed25519 identity keys. When an Ed25519 identity key is included in
10490 an EXTEND2 cell, the relay will only extend the circuit if the
10491 other relay can prove ownership of that identity. Implements part
10492 of ticket 15056; part of proposal 220.
10494 o Major bugfixes (scheduler):
10495 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
10496 caused the channel scheduler to behave more or less randomly,
10497 rather than preferring channels with higher-priority circuits.
10498 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
10500 o Minor features (controller):
10501 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
10502 rather than "unrecognized." Closes ticket 20389; patch from
10505 o Minor features (diagnostic, directory client):
10506 - Warn when we find an unexpected inconsistency in directory
10507 download status objects. Prevents some negative consequences of
10510 o Minor features (directory authority):
10511 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
10512 default) to control whether authorities should try to probe relays
10513 by their Ed25519 link keys. This option will go away in a few
10514 releases--unless we encounter major trouble in our ed25519 link
10515 protocol rollout, in which case it will serve as a safety option.
10517 o Minor features (directory cache):
10518 - Relays and bridges will now refuse to serve the consensus they
10519 have if they know it is too old for a client to use. Closes
10522 o Minor features (ed25519 link handshake):
10523 - Advertise support for the ed25519 link handshake using the
10524 subprotocol-versions mechanism, so that clients can tell which
10525 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
10527 o Minor features (fingerprinting resistance, authentication):
10528 - Extend the length of RSA keys used for TLS link authentication to
10529 2048 bits. (These weren't used for forward secrecy; for forward
10530 secrecy, we used P256.) Closes ticket 13752.
10532 o Minor features (infrastructure):
10533 - Implement smartlist_add_strdup() function. Replaces the use of
10534 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
10536 o Minor bugfixes (client):
10537 - When clients that use bridges start up with a cached consensus on
10538 disk, they were ignoring it and downloading a new one. Now they
10539 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
10541 o Minor bugfixes (configuration):
10542 - Accept non-space whitespace characters after the severity level in
10543 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
10544 - Support "TByte" and "TBytes" units in options given in bytes.
10545 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
10546 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
10548 o Minor bugfixes (consensus weight):
10549 - Add new consensus method that initializes bw weights to 1 instead
10550 of 0. This prevents a zero weight from making it all the way to
10551 the end (happens in small testing networks) and causing an error.
10552 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
10554 o Minor bugfixes (descriptors):
10555 - Correctly recognise downloaded full descriptors as valid, even
10556 when using microdescriptors as circuits. This affects clients with
10557 FetchUselessDescriptors set, and may affect directory authorities.
10558 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
10560 o Minor bugfixes (directory system):
10561 - Download all consensus flavors, descriptors, and authority
10562 certificates when FetchUselessDescriptors is set, regardless of
10563 whether tor is a directory cache or not. Fixes bug 20667; bugfix
10564 on all recent tor versions.
10565 - Bridges and relays now use microdescriptors (like clients do)
10566 rather than old-style router descriptors. Now bridges will blend
10567 in with clients in terms of the circuits they build. Fixes bug
10568 6769; bugfix on 0.2.3.2-alpha.
10570 o Minor bugfixes (ed25519 certificates):
10571 - Correctly interpret ed25519 certificates that would expire some
10572 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
10574 o Minor bugfixes (hidden services):
10575 - Stop ignoring misconfigured hidden services. Instead, refuse to
10576 start tor until the misconfigurations have been corrected. Fixes
10577 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
10580 o Minor bugfixes (memory leak at exit):
10581 - Fix a small harmless memory leak at exit of the previously unused
10582 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
10585 o Minor bugfixes (util):
10586 - When finishing writing a file to disk, if we were about to replace
10587 the file with the temporary file created before and we fail to
10588 replace it, remove the temporary file so it doesn't stay on disk.
10589 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
10591 o Minor bugfixes (Windows):
10592 - Check for getpagesize before using it to mmap files. This fixes
10593 compilation in some MinGW environments. Fixes bug 20530; bugfix on
10594 0.1.2.1-alpha. Reported by "ice".
10596 o Code simplification and refactoring:
10597 - Abolish all global guard context in entrynodes.c; replace with new
10598 guard_selection_t structure as preparation for proposal 271.
10599 Closes ticket 19858.
10600 - Introduce rend_service_is_ephemeral() that tells if given onion
10601 service is ephemeral. Replace unclear NULL-checkings for service
10602 directory with this function. Closes ticket 20526.
10603 - Extract magic numbers in circuituse.c into defined variables.
10604 - Refactor circuit_is_available_for_use to remove unnecessary check.
10605 - Refactor circuit_predict_and_launch_new for readability and
10606 testability. Closes ticket 18873.
10607 - Refactor large if statement in purpose_needs_anonymity to use
10608 switch statement instead. Closes part of ticket 20077.
10609 - Refactor the hashing API to return negative values for errors, as
10610 is done as throughout the codebase. Closes ticket 20717.
10611 - Remove data structures that were used to index or_connection
10612 objects by their RSA identity digests. These structures are fully
10613 redundant with the similar structures used in the
10614 channel abstraction.
10615 - Remove duplicate code in the channel_write_*cell() functions.
10616 Closes ticket 13827; patch from Pingl.
10617 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
10618 use only purpose_needs_anonymity. Closes part of ticket 20077.
10619 - The code to generate and parse EXTEND and EXTEND2 cells has been
10620 replaced with code automatically generated by the
10624 - Include the "TBits" unit in Tor's man page. Fixes part of bug
10625 20622; bugfix on 0.2.5.1-alpha.
10626 - Change '1' to 'weight_scale' in consensus bw weights calculation
10627 comments, as that is reality. Closes ticket 20273. Patch
10629 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
10630 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
10632 - Stop the man page from incorrectly stating that HiddenServiceDir
10633 must already exist. Fixes 20486.
10634 - Clarify that when ClientRejectInternalAddresses is enabled (which
10635 is the default), multicast DNS hostnames for machines on the local
10636 network (of the form *.local) are also rejected. Closes
10639 o Removed features:
10640 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
10641 limit for relays running on a single IP applies to authority IP
10642 addresses as well as to non-authority IP addresses. Closes
10644 - The UseDirectoryGuards torrc option no longer exists: all users
10645 that use entry guards will also use directory guards. Related to
10646 proposal 271; implements part of ticket 20831.
10649 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
10650 from "overcaffeinated".
10651 - Perform the coding style checks when running the tests and fail
10652 when coding style violations are found. Closes ticket 5500.
10653 - Add tests for networkstatus_compute_bw_weights_v10.
10654 - Add unit tests circuit_predict_and_launch_new.
10655 - Extract dummy_origin_circuit_new so it can be used by other
10659 Changes in version 0.2.8.12 - 2016-12-19
10660 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
10661 below) where Tor clients could crash when attempting to visit a
10662 hostile hidden service. Clients are recommended to upgrade as packages
10663 become available for their systems.
10665 It also includes an updated list of fallback directories, backported
10668 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
10669 backported to 0.2.8 in the future.
10671 o Major bugfixes (parsing, security, backported from 0.2.9.8):
10672 - Fix a bug in parsing that could cause clients to read a single
10673 byte past the end of an allocated region. This bug could be used
10674 to cause hardened clients (built with --enable-expensive-hardening)
10675 to crash if they tried to visit a hostile hidden service. Non-
10676 hardened clients are only affected depending on the details of
10677 their platform's memory allocator. Fixes bug 21018; bugfix on
10678 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10679 2016-12-002 and as CVE-2016-1254.
10681 o Minor features (fallback directory list, backported from 0.2.9.8):
10682 - Replace the 81 remaining fallbacks of the 100 originally
10683 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10684 fallbacks (123 new, 54 existing, 27 removed) generated in December
10685 2016. Resolves ticket 20170.
10687 o Minor features (geoip, backported from 0.2.9.7-rc):
10688 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10692 Changes in version 0.2.9.8 - 2016-12-19
10693 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
10695 The Tor 0.2.9 series makes mandatory a number of security features
10696 that were formerly optional. It includes support for a new shared-
10697 randomness protocol that will form the basis for next generation
10698 hidden services, includes a single-hop hidden service mode for
10699 optimizing .onion services that don't actually want to be hidden,
10700 tries harder not to overload the directory authorities with excessive
10701 downloads, and supports a better protocol versioning scheme for
10702 improved compatibility with other implementations of the Tor protocol.
10704 And of course, there are numerous other bugfixes and improvements.
10706 This release also includes a fix for a medium-severity issue (bug
10707 21018 below) where Tor clients could crash when attempting to visit a
10708 hostile hidden service. Clients are recommended to upgrade as packages
10709 become available for their systems.
10711 Below are the changes since 0.2.9.7-rc. For a list of all changes
10712 since 0.2.8, see the ReleaseNotes file.
10714 o Major bugfixes (parsing, security):
10715 - Fix a bug in parsing that could cause clients to read a single
10716 byte past the end of an allocated region. This bug could be used
10717 to cause hardened clients (built with --enable-expensive-hardening)
10718 to crash if they tried to visit a hostile hidden service. Non-
10719 hardened clients are only affected depending on the details of
10720 their platform's memory allocator. Fixes bug 21018; bugfix on
10721 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10722 2016-12-002 and as CVE-2016-1254.
10724 o Minor features (fallback directory list):
10725 - Replace the 81 remaining fallbacks of the 100 originally
10726 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10727 fallbacks (123 new, 54 existing, 27 removed) generated in December
10728 2016. Resolves ticket 20170.
10731 Changes in version 0.2.9.7-rc - 2016-12-12
10732 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
10733 including a few that had prevented tests from passing on
10736 o Minor features (geoip):
10737 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10740 o Minor bugfix (build):
10741 - The current Git revision when building from a local repository is
10742 now detected correctly when using git worktrees. Fixes bug 20492;
10743 bugfix on 0.2.3.9-alpha.
10745 o Minor bugfixes (directory authority):
10746 - When computing old Tor protocol line version in protover, we were
10747 looking at 0.2.7.5 twice instead of a specific case for
10748 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
10750 o Minor bugfixes (download scheduling):
10751 - Resolve a "bug" warning when considering a download schedule whose
10752 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
10754 o Minor bugfixes (logging):
10755 - Downgrade a harmless log message about the
10756 pending_entry_connections list from "warn" to "info". Mitigates
10759 o Minor bugfixes (memory leak):
10760 - Fix a small memory leak when receiving AF_UNIX connections on a
10761 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
10762 - When moving a signed descriptor object from a source to an
10763 existing destination, free the allocated memory inside that
10764 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
10766 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
10767 - Fix a memory leak and use-after-free error when removing entries
10768 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
10769 0.2.5.5-alpha. Patch from "cypherpunks".
10771 o Minor bugfixes (portability):
10772 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
10773 Fixes bug 20935; bugfix on 0.2.9.6-rc.
10775 o Minor bugfixes (unit tests):
10776 - Stop expecting NetBSD unit tests to report success for ipfw. Part
10777 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
10778 - Fix tolerances in unit tests for monotonic time comparisons
10779 between nanoseconds and microseconds. Previously, we accepted a 10
10780 us difference only, which is not realistic on every platform's
10781 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
10782 - Remove a double-free in the single onion service unit test. Stop
10783 ignoring a return value. Make future changes less error-prone.
10784 Fixes bug 20864; bugfix on 0.2.9.6-rc.
10787 Changes in version 0.2.8.11 - 2016-12-08
10788 Tor 0.2.8.11 backports fixes for additional portability issues that
10789 could prevent Tor from building correctly on OSX Sierra, or with
10790 OpenSSL 1.1. Affected users should upgrade; others can safely stay
10793 o Minor bugfixes (portability):
10794 - Avoid compilation errors when building on OSX Sierra. Sierra began
10795 to support the getentropy() and clock_gettime() APIs, but created
10796 a few problems in doing so. Tor 0.2.9 has a more thorough set of
10797 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
10798 monotonic time interfaces. Fixes bug 20865. Bugfix
10801 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10802 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10803 architectures. Closes ticket 20588.
10806 Changes in version 0.2.8.10 - 2016-12-02
10807 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
10808 unusable after they left standby mode. It also backports fixes for
10809 a few portability issues and a small but problematic memory leak.
10811 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
10812 - When Tor leaves standby because of a new application request, open
10813 circuits as needed to serve that request. Previously, we would
10814 potentially wait a very long time. Fixes part of bug 19969; bugfix
10817 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
10818 - Clients now respond to new application stream requests immediately
10819 when they arrive, rather than waiting up to one second before
10820 starting to handle them. Fixes part of bug 19969; bugfix
10823 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
10824 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10825 successfully targeting earlier versions of OSX. Resolves
10828 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10829 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10830 20551; bugfix on 0.2.1.1-alpha.
10832 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
10833 - Work around a memory leak in OpenSSL 1.1 when encoding public
10834 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10836 o Minor features (geoip):
10837 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10840 Changes in version 0.2.9.6-rc - 2016-12-02
10841 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
10842 version. We hope that it will be ready to become stable soon, and we
10843 encourage everyone to test this release. If no showstopper bugs are
10844 found here, the next 0.2.9 release will be stable.
10846 o Major bugfixes (relay, resolver, logging):
10847 - For relays that don't know their own address, avoid attempting a
10848 local hostname resolve for each descriptor we download. This
10849 will cut down on the number of "Success: chose address 'x.x.x.x'"
10850 log lines, and also avoid confusing clock jumps if the resolver
10851 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
10853 o Minor bugfixes (client, fascistfirewall):
10854 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
10855 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
10857 o Minor bugfixes (hidden services):
10858 - Stop ignoring the anonymity status of saved keys for hidden
10859 services and single onion services when first starting tor.
10860 Instead, refuse to start tor if any hidden service key has been
10861 used in a different hidden service anonymity mode. Fixes bug
10862 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
10864 o Minor bugfixes (portability):
10865 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10866 successfully targeting earlier versions of OSX. Resolves
10868 - Run correctly when built on Windows build environments that
10869 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
10871 o Minor bugfixes (single onion services, Tor2web):
10872 - Stop complaining about long-term one-hop circuits deliberately
10873 created by single onion services and Tor2web. These log messages
10874 are intended to diagnose issue 8387, which relates to circuits
10875 hanging around forever for no reason. Fixes bug 20613; bugfix on
10876 0.2.9.1-alpha. Reported by "pastly".
10878 o Minor bugfixes (unit tests):
10879 - Stop spurious failures in the local interface address discovery
10880 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
10884 - Correct the minimum bandwidth value in torrc.sample, and queue a
10885 corresponding change for torrc.minimal. Closes ticket 20085.
10888 Changes in version 0.2.9.5-alpha - 2016-11-08
10889 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
10890 version. We believe one or two probably remain, and we encourage
10891 everyone to test this release.
10893 o Major bugfixes (client performance):
10894 - Clients now respond to new application stream requests immediately
10895 when they arrive, rather than waiting up to one second before
10896 starting to handle them. Fixes part of bug 19969; bugfix
10899 o Major bugfixes (client reliability):
10900 - When Tor leaves standby because of a new application request, open
10901 circuits as needed to serve that request. Previously, we would
10902 potentially wait a very long time. Fixes part of bug 19969; bugfix
10905 o Major bugfixes (download scheduling):
10906 - When using an exponential backoff schedule, do not give up on
10907 downloading just because we have failed a bunch of times. Since
10908 each delay is longer than the last, retrying indefinitely won't
10909 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
10910 - If a consensus expires while we are waiting for certificates to
10911 download, stop waiting for certificates.
10912 - If we stop waiting for certificates less than a minute after we
10913 started downloading them, do not consider the certificate download
10914 failure a separate failure. Fixes bug 20533; bugfix
10916 - Remove the maximum delay on exponential-backoff scheduling. Since
10917 we now allow an infinite number of failures (see ticket 20536), we
10918 must now allow the time to grow longer on each failure. Fixes part
10919 of bug 20534; bugfix on 0.2.9.1-alpha.
10920 - Make our initial download delays closer to those from 0.2.8. Fixes
10921 another part of bug 20534; bugfix on 0.2.9.1-alpha.
10922 - When determining when to download a directory object, handle times
10923 after 2038 if the operating system supports them. (Someday this
10924 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
10925 - When using exponential backoff in test networks, use a lower
10926 exponent, so the delays do not vary as much. This helps test
10927 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
10929 o Minor features (geoip):
10930 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10933 o Minor bugfixes (client directory scheduling):
10934 - Treat "relay too busy to answer request" as a failed request and a
10935 reason to back off on our retry frequency. This is safe now that
10936 exponential backoffs retry indefinitely, and avoids a bug where we
10937 would reset our download schedule erroneously. Fixes bug 20593;
10938 bugfix on 0.2.9.1-alpha.
10940 o Minor bugfixes (client, logging):
10941 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
10942 assume all nodes support EXTEND2. Use ntor whenever a key is
10943 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
10944 - On DNSPort, stop logging a BUG warning on a failed hostname
10945 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
10947 o Minor bugfixes (hidden services):
10948 - When configuring hidden services, check every hidden service
10949 directory's permissions. Previously, we only checked the last
10950 hidden service. Fixes bug 20529; bugfix the work to fix 13942
10953 o Minor bugfixes (portability):
10954 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10955 architectures. Closes ticket 20588.
10956 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
10957 removed the ECDH ciphers which caused the tests to fail on
10958 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
10959 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10960 20551; bugfix on 0.2.1.1-alpha.
10962 o Minor bugfixes (relay bootstrap):
10963 - Ensure relays don't make multiple connections during bootstrap.
10964 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
10966 o Minor bugfixes (relay):
10967 - Work around a memory leak in OpenSSL 1.1 when encoding public
10968 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10969 - Avoid a small memory leak when informing worker threads about
10970 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
10971 - Do not try to parallelize workers more than 16x without the user
10972 explicitly configuring us to do so, even if we do detect more than
10973 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10975 o Minor bugfixes (single onion services):
10976 - Start correctly when creating a single onion service in a
10977 directory that did not previously exist. Fixes bug 20484; bugfix
10980 o Minor bugfixes (testing):
10981 - Avoid a unit test failure on systems with over 16 detectable CPU
10982 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10985 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
10986 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
10987 - Module-level documentation for several more modules. Closes
10988 tickets 19287 and 19290.
10991 Changes in version 0.2.8.9 - 2016-10-17
10992 Tor 0.2.8.9 backports a fix for a security hole in previous versions
10993 of Tor that would allow a remote attacker to crash a Tor client,
10994 hidden service, relay, or authority. All Tor users should upgrade to
10995 this version, or to 0.2.9.4-alpha. Patches will be released for older
10998 o Major features (security fixes, also in 0.2.9.4-alpha):
10999 - Prevent a class of security bugs caused by treating the contents
11000 of a buffer chunk as if they were a NUL-terminated string. At
11001 least one such bug seems to be present in all currently used
11002 versions of Tor, and would allow an attacker to remotely crash
11003 most Tor instances, especially those compiled with extra compiler
11004 hardening. With this defense in place, such bugs can't crash Tor,
11005 though we should still fix them as they occur. Closes ticket
11006 20384 (TROVE-2016-10-001).
11008 o Minor features (geoip):
11009 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
11013 Changes in version 0.2.9.4-alpha - 2016-10-17
11014 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
11015 that would allow a remote attacker to crash a Tor client, hidden
11016 service, relay, or authority. All Tor users should upgrade to this
11017 version, or to 0.2.8.9. Patches will be released for older versions
11020 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
11021 previous versions of Tor, including the implementation of a feature to
11022 future- proof the Tor ecosystem against protocol changes, some bug
11023 fixes necessary for Tor Browser to use unix domain sockets correctly,
11024 and several portability improvements. We anticipate that this will be
11025 the last alpha in the Tor 0.2.9 series, and that the next release will
11026 be a release candidate.
11028 o Major features (security fixes):
11029 - Prevent a class of security bugs caused by treating the contents
11030 of a buffer chunk as if they were a NUL-terminated string. At
11031 least one such bug seems to be present in all currently used
11032 versions of Tor, and would allow an attacker to remotely crash
11033 most Tor instances, especially those compiled with extra compiler
11034 hardening. With this defense in place, such bugs can't crash Tor,
11035 though we should still fix them as they occur. Closes ticket
11036 20384 (TROVE-2016-10-001).
11038 o Major features (subprotocol versions):
11039 - Tor directory authorities now vote on a set of recommended
11040 subprotocol versions, and on a set of required subprotocol
11041 versions. Clients and relays that lack support for a _required_
11042 subprotocol version will not start; those that lack support for a
11043 _recommended_ subprotocol version will warn the user to upgrade.
11044 Closes ticket 19958; implements part of proposal 264.
11045 - Tor now uses "subprotocol versions" to indicate compatibility.
11046 Previously, versions of Tor looked at the declared Tor version of
11047 a relay to tell whether they could use a given feature. Now, they
11048 should be able to rely on its declared subprotocol versions. This
11049 change allows compatible implementations of the Tor protocol(s) to
11050 exist without pretending to be 100% bug-compatible with particular
11051 releases of Tor itself. Closes ticket 19958; implements part of
11054 o Minor feature (fallback directories):
11055 - Remove broken fallbacks from the hard-coded fallback directory
11056 list. Closes ticket 20190; patch by teor.
11058 o Minor features (client, directory):
11059 - Since authorities now omit all routers that lack the Running and
11060 Valid flags, we assume that any relay listed in the consensus must
11061 have those flags. Closes ticket 20001; implements part of
11064 o Minor features (compilation, portability):
11065 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
11068 o Minor features (development tools, etags):
11069 - Teach the "make tags" Makefile target how to correctly find
11070 "MOCK_IMPL" function definitions. Patch from nherring; closes
11073 o Minor features (geoip):
11074 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
11077 o Minor features (unix domain sockets):
11078 - When configuring a unix domain socket for a SocksPort,
11079 ControlPort, or Hidden service, you can now wrap the address in
11080 quotes, using C-style escapes inside the quotes. This allows unix
11081 domain socket paths to contain spaces.
11083 o Minor features (virtual addresses):
11084 - Increase the maximum number of bits for the IPv6 virtual network
11085 prefix from 16 to 104. In this way, the condition for address
11086 allocation is less restrictive. Closes ticket 20151; feature
11089 o Minor bugfixes (address discovery):
11090 - Stop reordering IP addresses returned by the OS. This makes it
11091 more likely that Tor will guess the same relay IP address every
11092 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
11093 Reported by René Mayrhofer, patch by "cypherpunks".
11095 o Minor bugfixes (client, unix domain sockets):
11096 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
11097 the client address is meaningless. Fixes bug 20261; bugfix
11100 o Minor bugfixes (compilation, OpenBSD):
11101 - Detect Libevent2 functions correctly on systems that provide
11102 libevent2, but where libevent1 is linked with -levent. Fixes bug
11103 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
11105 o Minor bugfixes (configuration):
11106 - When parsing quoted configuration values from the torrc file,
11107 handle windows line endings correctly. Fixes bug 19167; bugfix on
11108 0.2.0.16-alpha. Patch from "Pingl".
11110 o Minor bugfixes (getpass):
11111 - Defensively fix a non-triggerable heap corruption at do_getpass()
11112 to protect ourselves from mistakes in the future. Fixes bug
11113 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
11116 o Minor bugfixes (hidden service):
11117 - Allow hidden services to run on IPv6 addresses even when the
11118 IPv6Exit option is not set. Fixes bug 18357; bugfix
11122 - Add module-level internal documentation for 36 C files that
11123 previously didn't have a high-level overview. Closes ticket #20385.
11125 o Required libraries:
11126 - When building with OpenSSL, Tor now requires version 1.0.1 or
11127 later. OpenSSL 1.0.0 and earlier are no longer supported by the
11128 OpenSSL team, and should not be used. Closes ticket 20303.
11131 Changes in version 0.2.9.3-alpha - 2016-09-23
11132 Tor 0.2.9.3-alpha adds improved support for entities that want to make
11133 high-performance services available through the Tor .onion mechanism
11134 without themselves receiving anonymity as they host those services. It
11135 also tries harder to ensure that all steps on a circuit are using the
11136 strongest crypto possible, strengthens some TLS properties, and
11137 resolves several bugs -- including a pair of crash bugs from the 0.2.8
11138 series. Anybody running an earlier version of 0.2.9.x should upgrade.
11140 o Major bugfixes (crash, also in 0.2.8.8):
11141 - Fix a complicated crash bug that could affect Tor clients
11142 configured to use bridges when replacing a networkstatus consensus
11143 in which one of their bridges was mentioned. OpenBSD users saw
11144 more crashes here, but all platforms were potentially affected.
11145 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11147 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
11148 - Fix a timing-dependent assertion failure that could occur when we
11149 tried to flush from a circuit after having freed its cells because
11150 of an out-of-memory condition. Fixes bug 20203; bugfix on
11151 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11154 o Major features (circuit building, security):
11155 - Authorities, relays and clients now require ntor keys in all
11156 descriptors, for all hops (except for rare hidden service protocol
11157 cases), for all circuits, and for all other roles. Part of
11159 - Tor authorities, relays, and clients only use ntor, except for
11160 rare cases in the hidden service protocol. Part of ticket 19163.
11162 o Major features (single-hop "hidden" services):
11163 - Add experimental HiddenServiceSingleHopMode and
11164 HiddenServiceNonAnonymousMode options. When both are set to 1,
11165 every hidden service on a Tor instance becomes a non-anonymous
11166 Single Onion Service. Single Onions make one-hop (direct)
11167 connections to their introduction and renzedvous points. One-hop
11168 circuits make Single Onion servers easily locatable, but clients
11169 remain location-anonymous. This is compatible with the existing
11170 hidden service implementation, and works on the current tor
11171 network without any changes to older relays or clients. Implements
11172 proposal 260, completes ticket 17178. Patch by teor and asn.
11174 o Major features (resource management):
11175 - Tor can now notice it is about to run out of sockets, and
11176 preemptively close connections of lower priority. (This feature is
11177 off by default for now, since the current prioritizing method is
11178 yet not mature enough. You can enable it by setting
11179 "DisableOOSCheck 0", but watch out: it might close some sockets
11180 you would rather have it keep.) Closes ticket 18640.
11182 o Major bugfixes (circuit building):
11183 - Hidden service client-to-intro-point and service-to-rendezvous-
11184 point circuits use the TAP key supplied by the protocol, to avoid
11185 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
11187 o Major bugfixes (compilation, OpenBSD):
11188 - Fix a Libevent-detection bug in our autoconf script that would
11189 prevent Tor from linking successfully on OpenBSD. Patch from
11190 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
11192 o Major bugfixes (hidden services):
11193 - Clients now require hidden services to include the TAP keys for
11194 their intro points in the hidden service descriptor. This prevents
11195 an inadvertent upgrade to ntor, which a malicious hidden service
11196 could use to distinguish clients by consensus version. Fixes bug
11197 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
11199 o Minor features (security, TLS):
11200 - Servers no longer support clients that without AES ciphersuites.
11201 (3DES is no longer considered an acceptable cipher.) We believe
11202 that no such Tor clients currently exist, since Tor has required
11203 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
11205 o Minor feature (fallback directories):
11206 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11207 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11208 2016. Closes ticket 20190; patch by teor.
11210 o Minor features (geoip, also in 0.2.8.8):
11211 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11214 o Minor feature (port flags):
11215 - Add new flags to the *Port options to finer control over which
11216 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
11217 and the synthetic flag OnionTrafficOnly, which is equivalent to
11218 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
11219 18693; patch by "teor".
11221 o Minor features (directory authority):
11222 - After voting, if the authorities decide that a relay is not
11223 "Valid", they no longer include it in the consensus at all. Closes
11224 ticket 20002; implements part of proposal 272.
11226 o Minor features (testing):
11227 - Disable memory protections on OpenBSD when performing our unit
11228 tests for memwipe(). The test deliberately invokes undefined
11229 behavior, and the OpenBSD protections interfere with this. Patch
11230 from "rubiate". Closes ticket 20066.
11232 o Minor features (testing, ipv6):
11233 - Add the single-onion and single-onion-ipv6 chutney targets to
11234 "make test-network-all". This requires a recent chutney version
11235 with the single onion network flavours (git c72a652 or later).
11236 Closes ticket 20072; patch by teor.
11237 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
11238 tests. Remove bridges+hs, as it's somewhat redundant. This
11239 requires a recent chutney version that supports IPv6 clients,
11240 relays, and authorities. Closes ticket 20069; patch by teor.
11242 o Minor features (Tor2web):
11243 - Make Tor2web clients respect ReachableAddresses. This feature was
11244 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
11245 0.2.8.7. Implements feature 20034. Patch by teor.
11247 o Minor features (unit tests):
11248 - We've done significant work to make the unit tests run faster.
11249 - Our link-handshake unit tests now check that when invalid
11250 handshakes fail, they fail with the error messages we expected.
11251 - Our unit testing code that captures log messages no longer
11252 prevents them from being written out if the user asked for them
11253 (by passing --debug or --info or or --notice --warn to the "test"
11254 binary). This change prevents us from missing unexpected log
11255 messages simply because we were looking for others. Related to
11257 - The unit tests now log all warning messages with the "BUG" flag.
11258 Previously, they only logged errors by default. This change will
11259 help us make our testing code more correct, and make sure that we
11260 only hit this code when we mean to. In the meantime, however,
11261 there will be more warnings in the unit test logs than before.
11262 This is preparatory work for ticket 19999.
11263 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
11264 assertion as a test failure.
11266 o Minor bug fixes (circuits):
11267 - Use the CircuitBuildTimeout option whenever
11268 LearnCircuitBuildTimeout is disabled. Previously, we would respect
11269 the option when a user disabled it, but not when it was disabled
11270 because some other option was set. Fixes bug 20073; bugfix on
11271 0.2.4.12-alpha. Patch by teor.
11273 o Minor bugfixes (allocation):
11274 - Change how we allocate memory for large chunks on buffers, to
11275 avoid a (currently impossible) integer overflow, and to waste less
11276 space when allocating unusually large chunks. Fixes bug 20081;
11277 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
11278 - Always include orconfig.h before including any other C headers.
11279 Sometimes, it includes macros that affect the behavior of the
11280 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
11281 first version to use AC_USE_SYSTEM_EXTENSIONS).
11282 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
11283 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
11284 Patch from Gisle Vanem.
11285 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
11286 They apparently require a set of annotations that we aren't
11287 currently using, and they create false positives in our pthreads
11288 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
11290 o Minor bugfixes (directory authority):
11291 - Die with a more useful error when the operator forgets to place
11292 the authority_signing_key file into the keys directory. This
11293 avoids an uninformative assert & traceback about having an invalid
11294 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
11295 - When allowing private addresses, mark Exits that only exit to
11296 private locations as such. Fixes bug 20064; bugfix
11299 o Minor bugfixes (documentation):
11300 - Document the default PathsNeededToBuildCircuits value that's used
11301 by clients when the directory authorities don't set
11302 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
11303 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
11304 - Fix manual for the User option: it takes a username, not a UID.
11305 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
11308 o Minor bugfixes (hidden services):
11309 - Stop logging intro point details to the client log on certain
11310 error conditions. Fixed as part of bug 20012; bugfix on
11311 0.2.4.8-alpha. Patch by teor.
11313 o Minor bugfixes (IPv6, testing):
11314 - Check for IPv6 correctly on Linux when running test networks.
11315 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
11317 o Minor bugfixes (Linux seccomp2 sandbox):
11318 - Add permission to run the sched_yield() and sigaltstack() system
11319 calls, in order to support versions of Tor compiled with asan or
11320 ubsan code that use these calls. Now "sandbox 1" and
11321 "--enable-expensive-hardening" should be compatible on more
11322 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
11324 o Minor bugfixes (logging):
11325 - When logging a message from the BUG() macro, be explicit about
11326 what we were asserting. Previously we were confusing what we were
11327 asserting with what the bug was. Fixes bug 20093; bugfix
11329 - When we are unable to remove the bw_accounting file, do not warn
11330 if the reason we couldn't remove it was that it didn't exist.
11331 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
11333 o Minor bugfixes (option parsing):
11334 - Count unix sockets when counting client listeners (SOCKS, Trans,
11335 NATD, and DNS). This has no user-visible behaviour changes: these
11336 options are set once, and never read. Required for correct
11337 behaviour in ticket 17178. Fixes bug 19677; bugfix on
11338 0.2.6.3-alpha. Patch by teor.
11340 o Minor bugfixes (options):
11341 - Check the consistency of UseEntryGuards and EntryNodes more
11342 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
11344 - Stop changing the configured value of UseEntryGuards on
11345 authorities and Tor2web clients. Fixes bug 20074; bugfix on
11346 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
11349 o Minor bugfixes (Tor2web):
11350 - Prevent Tor2web clients running hidden services, these services
11351 are not anonymous due to the one-hop client paths. Fixes bug
11352 19678. Patch by teor.
11354 o Minor bugfixes (unit tests):
11355 - Fix a shared-random unit test that was failing on big endian
11356 architectures due to internal representation of a integer copied
11357 to a buffer. The test is changed to take a full 32 bytes of data
11358 and use the output of a python script that make the COMMIT and
11359 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
11361 - The tor_tls_server_info_callback unit test no longer crashes when
11362 debug-level logging is turned on. Fixes bug 20041; bugfix
11366 Changes in version 0.2.8.8 - 2016-09-23
11367 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
11368 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
11369 who select public relays as their bridges.
11371 o Major bugfixes (crash):
11372 - Fix a complicated crash bug that could affect Tor clients
11373 configured to use bridges when replacing a networkstatus consensus
11374 in which one of their bridges was mentioned. OpenBSD users saw
11375 more crashes here, but all platforms were potentially affected.
11376 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11378 o Major bugfixes (relay, OOM handler):
11379 - Fix a timing-dependent assertion failure that could occur when we
11380 tried to flush from a circuit after having freed its cells because
11381 of an out-of-memory condition. Fixes bug 20203; bugfix on
11382 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11385 o Minor feature (fallback directories):
11386 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11387 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11388 2016. Closes ticket 20190; patch by teor.
11390 o Minor features (geoip):
11391 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11395 Changes in version 0.2.9.2-alpha - 2016-08-24
11396 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
11397 several new features and bugfixes. It also includes an important
11398 authority update and an important bugfix from 0.2.8.7. Everyone who
11399 sets the ReachableAddresses option, and all bridges, are strongly
11400 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
11402 o Directory authority changes (also in 0.2.8.7):
11403 - The "Tonga" bridge authority has been retired; the new bridge
11404 authority is "Bifroest". Closes tickets 19728 and 19690.
11406 o Major bugfixes (client, security, also in 0.2.8.7):
11407 - Only use the ReachableAddresses option to restrict the first hop
11408 in a path. In earlier versions of 0.2.8.x, it would apply to
11409 every hop in the path, with a possible degradation in anonymity
11410 for anyone using an uncommon ReachableAddress setting. Fixes bug
11411 19973; bugfix on 0.2.8.2-alpha.
11413 o Major features (user interface):
11414 - Tor now supports the ability to declare options deprecated, so
11415 that we can recommend that people stop using them. Previously,
11416 this was done in an ad-hoc way. Closes ticket 19820.
11418 o Major bugfixes (directory downloads):
11419 - Avoid resetting download status for consensuses hourly, since we
11420 already have another, smarter retry mechanism. Fixes bug 8625;
11421 bugfix on 0.2.0.9-alpha.
11423 o Minor features (config):
11424 - Warn users when descriptor and port addresses are inconsistent.
11425 Mitigates bug 13953; patch by teor.
11427 o Minor features (geoip):
11428 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11431 o Minor features (user interface):
11432 - There is a new --list-deprecated-options command-line option to
11433 list all of the deprecated options. Implemented as part of
11436 o Minor bugfixes (code style):
11437 - Fix an integer signedness conversion issue in the case conversion
11438 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
11440 o Minor bugfixes (compilation):
11441 - Build correctly on versions of libevent2 without support for
11442 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
11444 - Fix a compilation warning on GCC versions before 4.6. Our
11445 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
11446 when it is also required as an argument to the compiler pragma.
11447 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
11449 o Minor bugfixes (compilation, also in 0.2.8.7):
11450 - Remove an inappropriate "inline" in tortls.c that was causing
11451 warnings on older versions of GCC. Fixes bug 19903; bugfix
11454 o Minor bugfixes (fallback directories, also in 0.2.8.7):
11455 - Avoid logging a NULL string pointer when loading fallback
11456 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11457 and 0.2.8.1-alpha. Report and patch by "rubiate".
11459 o Minor bugfixes (logging):
11460 - Log a more accurate message when we fail to dump a microdescriptor.
11461 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
11463 o Minor bugfixes (memory leak):
11464 - Fix a series of slow memory leaks related to parsing torrc files
11465 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
11467 o Deprecated features:
11468 - A number of DNS-cache-related sub-options for client ports are now
11469 deprecated for security reasons, and may be removed in a future
11470 version of Tor. (We believe that client-side DNS caching is a bad
11471 idea for anonymity, and you should not turn it on.) The options
11472 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
11473 UseIPv4Cache, and UseIPv6Cache.
11474 - A number of options are deprecated for security reasons, and may
11475 be removed in a future version of Tor. The options are:
11476 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
11477 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
11478 CloseHSClientCircuitsImmediatelyOnTimeout,
11479 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
11480 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
11481 UseNTorHandshake, and WarnUnsafeSocks.
11482 - The *ListenAddress options are now deprecated as unnecessary: the
11483 corresponding *Port options should be used instead. These options
11484 may someday be removed. The affected options are:
11485 ControlListenAddress, DNSListenAddress, DirListenAddress,
11486 NATDListenAddress, ORListenAddress, SocksListenAddress,
11487 and TransListenAddress.
11490 - Correct the IPv6 syntax in our documentation for the
11491 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
11494 - We no longer include the (dead, deprecated) bufferevent code in
11495 Tor. Closes ticket 19450. Based on a patch from U+039b.
11498 Changes in version 0.2.8.7 - 2016-08-24
11499 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
11500 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
11501 who sets the ReachableAddresses option, and all bridges, are strongly
11502 encouraged to upgrade.
11504 o Directory authority changes:
11505 - The "Tonga" bridge authority has been retired; the new bridge
11506 authority is "Bifroest". Closes tickets 19728 and 19690.
11508 o Major bugfixes (client, security):
11509 - Only use the ReachableAddresses option to restrict the first hop
11510 in a path. In earlier versions of 0.2.8.x, it would apply to
11511 every hop in the path, with a possible degradation in anonymity
11512 for anyone using an uncommon ReachableAddress setting. Fixes bug
11513 19973; bugfix on 0.2.8.2-alpha.
11515 o Minor features (geoip):
11516 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11519 o Minor bugfixes (compilation):
11520 - Remove an inappropriate "inline" in tortls.c that was causing
11521 warnings on older versions of GCC. Fixes bug 19903; bugfix
11524 o Minor bugfixes (fallback directories):
11525 - Avoid logging a NULL string pointer when loading fallback
11526 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11527 and 0.2.8.1-alpha. Report and patch by "rubiate".
11530 Changes in version 0.2.9.1-alpha - 2016-08-08
11531 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
11532 series. It improves our support for hardened builds and compiler
11533 warnings, deploys some critical infrastructure for improvements to
11534 hidden services, includes a new timing backend that we hope to use for
11535 better support for traffic padding, makes it easier for programmers to
11536 log unexpected events, and contains other small improvements to
11537 security, correctness, and performance.
11539 Below are the changes since 0.2.8.6.
11541 o New system requirements:
11542 - Tor now requires Libevent version 2.0.10-stable or later. Older
11543 versions of Libevent have less efficient backends for several
11544 platforms, and lack the DNS code that we use for our server-side
11545 DNS support. This implements ticket 19554.
11546 - Tor now requires zlib version 1.2 or later, for security,
11547 efficiency, and (eventually) gzip support. (Back when we started,
11548 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
11549 released in 2003. We recommend the latest version.)
11551 o Major features (build, hardening):
11552 - Tor now builds with -ftrapv by default on compilers that support
11553 it. This option detects signed integer overflow (which C forbids),
11554 and turns it into a hard-failure. We do not apply this option to
11555 code that needs to run in constant time to avoid side-channels;
11556 instead, we use -fwrapv in that code. Closes ticket 17983.
11557 - When --enable-expensive-hardening is selected, stop applying the
11558 clang/gcc sanitizers to code that needs to run in constant time.
11559 Although we are aware of no introduced side-channels, we are not
11560 able to prove that there are none. Related to ticket 17983.
11562 o Major features (compilation):
11563 - Our big list of extra GCC warnings is now enabled by default when
11564 building with GCC (or with anything like Clang that claims to be
11565 GCC-compatible). To make all warnings into fatal compilation
11566 errors, pass --enable-fatal-warnings to configure. Closes
11568 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
11569 turn on C and POSIX extensions. (Previously, we attempted to do
11570 this on an ad hoc basis.) Closes ticket 19139.
11572 o Major features (directory authorities, hidden services):
11573 - Directory authorities can now perform the shared randomness
11574 protocol specified by proposal 250. Using this protocol, directory
11575 authorities generate a global fresh random value every day. In the
11576 future, this value will be used by hidden services to select
11577 HSDirs. This release implements the directory authority feature;
11578 the hidden service side will be implemented in the future as part
11579 of proposal 224. Resolves ticket 16943; implements proposal 250.
11581 o Major features (downloading, random exponential backoff):
11582 - When we fail to download an object from a directory service, wait
11583 for an (exponentially increasing) randomized amount of time before
11584 retrying, rather than a fixed interval as we did before. This
11585 prevents a group of Tor instances from becoming too synchronized,
11586 or a single Tor instance from becoming too predictable, in its
11587 download schedule. Closes ticket 15942.
11589 o Major bugfixes (exit policies):
11590 - Avoid disclosing exit outbound bind addresses, configured port
11591 bind addresses, and local interface addresses in relay descriptors
11592 by default under ExitPolicyRejectPrivate. Instead, only reject
11593 these (otherwise unlisted) addresses if
11594 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
11595 0.2.7.2-alpha. Patch by teor.
11597 o Major bugfixes (hidden service client):
11598 - Allow Tor clients with appropriate controllers to work with
11599 FetchHidServDescriptors set to 0. Previously, this option also
11600 disabled descriptor cache lookup, thus breaking hidden services
11601 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
11603 o Minor features (build, hardening):
11604 - Detect and work around a libclang_rt problem that would prevent
11605 clang from finding __mulodi4() on some 32-bit platforms, and thus
11606 keep -ftrapv from linking on those systems. Closes ticket 19079.
11607 - When building on a system without runtime support for the runtime
11608 hardening options, try to log a useful warning at configuration
11609 time, rather than an incomprehensible warning at link time. If
11610 expensive hardening was requested, this warning becomes an error.
11611 Closes ticket 18895.
11613 o Minor features (code safety):
11614 - In our integer-parsing functions, ensure that maxiumum value we
11615 give is no smaller than the minimum value. Closes ticket 19063;
11618 o Minor features (controller):
11619 - Implement new GETINFO queries for all downloads that use
11620 download_status_t to schedule retries. This allows controllers to
11621 examine the schedule for pending downloads. Closes ticket 19323.
11622 - Allow controllers to configure basic client authorization on
11623 hidden services when they create them with the ADD_ONION control
11624 command. Implements ticket 15588. Patch by "special".
11625 - Fire a STATUS_SERVER controller event whenever the hibernation
11626 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
11628 o Minor features (directory authority):
11629 - Directory authorities now only give the Guard flag to a relay if
11630 they are also giving it the Stable flag. This change allows us to
11631 simplify path selection for clients. It should have minimal effect
11632 in practice, since >99% of Guards already have the Stable flag.
11633 Implements ticket 18624.
11634 - Directory authorities now write their v3-status-votes file out to
11635 disk earlier in the consensus process, so we have a record of the
11636 votes even if we abort the consensus process. Resolves
11639 o Minor features (hidden service):
11640 - Stop being so strict about the payload length of "rendezvous1"
11641 cells. We used to be locked in to the "TAP" handshake length, and
11642 now we can handle better handshakes like "ntor". Resolves
11645 o Minor features (infrastructure, time):
11646 - Tor now uses the operating system's monotonic timers (where
11647 available) for internal fine-grained timing. Previously we would
11648 look at the system clock, and then attempt to compensate for the
11649 clock running backwards. Closes ticket 18908.
11650 - Tor now includes an improved timer backend, so that we can
11651 efficiently support tens or hundreds of thousands of concurrent
11652 timers, as will be needed for some of our planned anti-traffic-
11653 analysis work. This code is based on William Ahern's "timeout.c"
11654 project, which implements a "tickless hierarchical timing wheel".
11655 Closes ticket 18365.
11657 o Minor features (logging):
11658 - Provide a more useful warning message when configured with an
11659 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
11660 - When dumping unparseable router descriptors, optionally store them
11661 in separate files, named by digest, up to a configurable size
11662 limit. You can change the size limit by setting the
11663 MaxUnparseableDescSizeToLog option, and disable this feature by
11664 setting that option to 0. Closes ticket 18322.
11665 - Add a set of macros to check nonfatal assertions, for internal
11666 use. Migrating more of our checks to these should help us avoid
11667 needless crash bugs. Closes ticket 18613.
11669 o Minor features (performance):
11670 - Changer the "optimistic data" extension from "off by default" to
11671 "on by default". The default was ordinarily overridden by a
11672 consensus option, but when clients were bootstrapping for the
11673 first time, they would not have a consensus to get the option
11674 from. Changing this default When fetching a consensus for the
11675 first time, use optimistic data. This saves a round-trip during
11676 startup. Closes ticket 18815.
11678 o Minor features (relay, usability):
11679 - When the directory authorities refuse a bad relay's descriptor,
11680 encourage the relay operator to contact us. Many relay operators
11681 won't notice this line in their logs, but it's a win if even a few
11682 learn why we don't like what their relay was doing. Resolves
11685 o Minor features (testing):
11686 - Let backtrace tests work correctly under AddressSanitizer. Fixes
11687 part of bug 18934; bugfix on 0.2.5.2-alpha.
11688 - Move the test-network.sh script to chutney, and modify tor's test-
11689 network.sh to call the (newer) chutney version when available.
11690 Resolves ticket 19116. Patch by teor.
11691 - Use the lcov convention for marking lines as unreachable, so that
11692 we don't count them when we're generating test coverage data.
11693 Update our coverage tools to understand this convention. Closes
11696 o Minor bugfixes (bootstrap):
11697 - Remember the directory we fetched the consensus or previous
11698 certificates from, and use it to fetch future authority
11699 certificates. This change improves bootstrapping performance.
11700 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
11702 o Minor bugfixes (build):
11703 - The test-stem and test-network makefile targets now depend only on
11704 the tor binary that they are testing. Previously, they depended on
11705 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
11706 patch from "cypherpunks".
11708 o Minor bugfixes (circuits):
11709 - Make sure extend_info_from_router() is only called on servers.
11710 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
11712 o Minor bugfixes (compilation):
11713 - When building with Clang, use a full set of GCC warnings.
11714 (Previously, we included only a subset, because of the way we
11715 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
11717 o Minor bugfixes (directory authority):
11718 - Authorities now sort the "package" lines in their votes, for ease
11719 of debugging. (They are already sorted in consensus documents.)
11720 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
11721 - When parsing a detached signature, make sure we use the length of
11722 the digest algorithm instead of an hardcoded DIGEST256_LEN in
11723 order to avoid comparing bytes out-of-bounds with a smaller digest
11724 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
11726 o Minor bugfixes (documentation):
11727 - Document the --passphrase-fd option in the tor manpage. Fixes bug
11728 19504; bugfix on 0.2.7.3-rc.
11729 - Fix the description of the --passphrase-fd option in the
11730 tor-gencert manpage. The option is used to pass the number of a
11731 file descriptor to read the passphrase from, not to read the file
11732 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
11734 o Minor bugfixes (ephemeral hidden service):
11735 - When deleting an ephemeral hidden service, close its intro points
11736 even if they are not completely open. Fixes bug 18604; bugfix
11739 o Minor bugfixes (guard selection):
11740 - Use a single entry guard even if the NumEntryGuards consensus
11741 parameter is not provided. Fixes bug 17688; bugfix
11743 - Don't mark guards as unreachable if connection_connect() fails.
11744 That function fails for local reasons, so it shouldn't reveal
11745 anything about the status of the guard. Fixes bug 14334; bugfix
11748 o Minor bugfixes (hidden service client):
11749 - Increase the minimum number of internal circuits we preemptively
11750 build from 2 to 3, so a circuit is available when a client
11751 connects to another onion service. Fixes bug 13239; bugfix
11754 o Minor bugfixes (logging):
11755 - When logging a directory ownership mismatch, log the owning
11756 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
11758 o Minor bugfixes (memory leaks):
11759 - Fix a small, uncommon memory leak that could occur when reading a
11760 truncated ed25519 key file. Fixes bug 18956; bugfix
11763 o Minor bugfixes (testing):
11764 - Allow clients to retry HSDirs much faster in test networks. Fixes
11765 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
11766 - Disable ASAN's detection of segmentation faults while running
11767 test_bt.sh, so that we can make sure that our own backtrace
11768 generation code works. Fixes another aspect of bug 18934; bugfix
11769 on 0.2.5.2-alpha. Patch from "cypherpunks".
11770 - Fix the test-network-all target on out-of-tree builds by using the
11771 correct path to the test driver script. Fixes bug 19421; bugfix
11774 o Minor bugfixes (time):
11775 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
11776 bugfix on all released tor versions.
11777 - When computing the difference between two times in milliseconds,
11778 we now round to the nearest millisecond correctly. Previously, we
11779 could sometimes round in the wrong direction. Fixes bug 19428;
11780 bugfix on 0.2.2.2-alpha.
11782 o Minor bugfixes (user interface):
11783 - Display a more accurate number of suppressed messages in the log
11784 rate-limiter. Previously, there was a potential integer overflow
11785 in the counter. Now, if the number of messages hits a maximum, the
11786 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
11788 - Fix a typo in the passphrase prompt for the ed25519 identity key.
11789 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
11791 o Code simplification and refactoring:
11792 - Remove redundant declarations of the MIN macro. Closes
11794 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
11795 Closes ticket 18462; patch from "icanhasaccount".
11796 - Split the 600-line directory_handle_command_get function into
11797 separate functions for different URL types. Closes ticket 16698.
11800 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
11801 ticket 19153. Patch from "U+039b".
11803 o Removed features:
11804 - Remove support for "GET /tor/bytes.txt" DirPort request, and
11805 "GETINFO dir-usage" controller request, which were only available
11806 via a compile-time option in Tor anyway. Feature was added in
11807 0.2.2.1-alpha. Resolves ticket 19035.
11808 - There is no longer a compile-time option to disable support for
11809 TransPort. (If you don't want TransPort; just don't use it.) Patch
11810 from "U+039b". Closes ticket 19449.
11813 - Run more workqueue tests as part of "make check". These had
11814 previously been implemented, but you needed to know special
11815 command-line options to enable them.
11816 - We now have unit tests for our code to reject zlib "compression
11817 bombs". (Fortunately, the code works fine.)
11820 Changes in version 0.2.8.6 - 2016-08-02
11822 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
11824 The Tor 0.2.8 series improves client bootstrapping performance,
11825 completes the authority-side implementation of improved identity
11826 keys for relays, and includes numerous bugfixes and performance
11827 improvements throughout the program. This release continues to
11828 improve the coverage of Tor's test suite. For a full list of
11829 changes since Tor 0.2.7, see the ReleaseNotes file.
11831 Changes since 0.2.8.5-rc:
11833 o Minor features (geoip):
11834 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
11837 o Minor bugfixes (compilation):
11838 - Fix a compilation warning in the unit tests on systems where char
11839 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
11841 o Minor bugfixes (fallback directories):
11842 - Remove 1 fallback that was on the hardcoded list, then opted-out,
11843 leaving 89 of the 100 fallbacks originally introduced in Tor
11844 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
11846 o Minor bugfixes (Linux seccomp2 sandbox):
11847 - Allow more syscalls when running with "Sandbox 1" enabled:
11848 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
11849 some systems, these are required for Tor to start. Fixes bug
11850 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
11851 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
11852 so that get_interface_address6_via_udp_socket_hack() can work.
11853 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
11856 Changes in version 0.2.8.5-rc - 2016-07-07
11857 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
11858 series. If we find no new bugs or regressions here, the first stable
11859 0.2.8 release will be identical to it. It has a few small bugfixes
11860 against previous versions.
11862 o Directory authority changes:
11863 - Urras is no longer a directory authority. Closes ticket 19271.
11865 o Major bugfixes (heartbeat):
11866 - Fix a regression that would crash Tor when the periodic
11867 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
11868 0.2.8.1-alpha. Reported by "kubaku".
11870 o Minor features (build):
11871 - Tor now again builds with the recent OpenSSL 1.1 development
11872 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
11873 - When building manual pages, set the timezone to "UTC", so that the
11874 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
11875 Patch from intrigeri.
11877 o Minor bugfixes (fallback directory selection):
11878 - Avoid errors during fallback selection if there are no eligible
11879 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
11882 o Minor bugfixes (IPv6, microdescriptors):
11883 - Don't check node addresses when we only have a routerstatus. This
11884 allows IPv6-only clients to bootstrap by fetching microdescriptors
11885 from fallback directory mirrors. (The microdescriptor consensus
11886 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
11889 o Minor bugfixes (logging):
11890 - Reduce pointlessly verbose log messages when directory servers
11891 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
11892 0.2.8.1-alpha. Patch by teor.
11893 - When a fallback directory changes its fingerprint from the hard-
11894 coded fingerprint, log a less severe, more explanatory log
11895 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
11897 o Minor bugfixes (Linux seccomp2 sandboxing):
11898 - Allow statistics to be written to disk when "Sandbox 1" is
11899 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
11900 0.2.6.1-alpha respectively.
11902 o Minor bugfixes (user interface):
11903 - Remove a warning message "Service [scrubbed] not found after
11904 descriptor upload". This message appears when one uses HSPOST
11905 control command to upload a service descriptor. Since there is
11906 only a descriptor and no service, showing this message is
11907 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
11909 o Fallback directory list:
11910 - Add a comment to the generated fallback directory list that
11911 explains how to comment out unsuitable fallbacks in a way that's
11912 compatible with the stem fallback parser.
11913 - Update fallback whitelist and blacklist based on relay operator
11914 emails. Blacklist unsuitable (non-working, over-volatile)
11915 fallbacks. Resolves ticket 19071. Patch by teor.
11916 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
11917 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
11918 ticket 19071; patch by teor.
11921 Changes in version 0.2.8.4-rc - 2016-06-15
11922 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
11923 If we find no new bugs or regressions here, the first stable 0.2.8
11924 release will be identical to it. It has a few small bugfixes against
11927 o Major bugfixes (user interface):
11928 - Correctly give a warning in the cases where a relay is specified
11929 by nickname, and one such relay is found, but it is not officially
11930 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
11932 o Minor features (build):
11933 - Tor now builds once again with the recent OpenSSL 1.1 development
11934 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
11936 o Minor features (geoip):
11937 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
11940 o Minor bugfixes (compilation):
11941 - Cause the unit tests to compile correctly on mingw64 versions that
11942 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
11944 o Minor bugfixes (downloading):
11945 - Predict more correctly whether we'll be downloading over HTTP when
11946 we determine the maximum length of a URL. This should avoid a
11947 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
11951 Changes in version 0.2.8.3-alpha - 2016-05-26
11952 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
11953 the course of the 0.2.8 development cycle. It improves the behavior of
11954 directory clients, fixes several crash bugs, fixes a gap in compiler
11955 hardening, and allows the full integration test suite to run on
11958 o Major bugfixes (security, client, DNS proxy):
11959 - Stop a crash that could occur when a client running with DNSPort
11960 received a query with multiple address types, and the first
11961 address type was not supported. Found and fixed by Scott Dial.
11962 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11964 o Major bugfixes (security, compilation):
11965 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
11966 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
11967 cause a compiler warning, thereby making other checks fail, and
11968 needlessly disabling compiler-hardening support. Fixes one case of
11969 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
11971 o Major bugfixes (security, directory authorities):
11972 - Fix a crash and out-of-bounds write during authority voting, when
11973 the list of relays includes duplicate ed25519 identity keys. Fixes
11974 bug 19032; bugfix on 0.2.8.2-alpha.
11976 o Major bugfixes (client, bootstrapping):
11977 - Check if bootstrap consensus downloads are still needed when the
11978 linked connection attaches. This prevents tor making unnecessary
11979 begindir-style connections, which are the only directory
11980 connections tor clients make since the fix for 18483 was merged.
11981 - Fix some edge cases where consensus download connections may not
11982 have been closed, even though they were not needed. Related to fix
11984 - Make relays retry consensus downloads the correct number of times,
11985 rather than the more aggressive client retry count. Fixes part of
11987 - Stop downloading consensuses when we have a consensus, even if we
11988 don't have all the certificates for it yet. Fixes bug 18809;
11989 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
11991 o Major bugfixes (directory mirrors):
11992 - Decide whether to advertise begindir support in the the same way
11993 we decide whether to advertise our DirPort. Allowing these
11994 decisions to become out-of-sync led to surprising behavior like
11995 advertising begindir support when hibernation made us not
11996 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
11999 o Major bugfixes (IPv6 bridges, client):
12000 - Actually use IPv6 addresses when selecting directory addresses for
12001 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
12004 o Major bugfixes (key management):
12005 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12006 pointer to the previous (uninitialized) key value. The impact here
12007 should be limited to a difficult-to-trigger crash, if OpenSSL is
12008 running an engine that makes key generation failures possible, or
12009 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12010 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12013 o Major bugfixes (testing):
12014 - Fix a bug that would block 'make test-network-all' on systems where
12015 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
12016 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
12017 bugfix on 0.2.8.1-alpha.
12019 o Minor features (clients):
12020 - Make clients, onion services, and bridge relays always use an
12021 encrypted begindir connection for directory requests. Resolves
12022 ticket 18483. Patch by "teor".
12024 o Minor features (fallback directory mirrors):
12025 - Give each fallback the same weight for client selection; restrict
12026 fallbacks to one per operator; report fallback directory detail
12027 changes when rebuilding list; add new fallback directory mirrors
12028 to the whitelist; and many other minor simplifications and fixes.
12029 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
12030 0.2.8.1-alpha; patch by "teor".
12031 - Replace the 21 fallbacks generated in January 2016 and included in
12032 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
12033 2016. Closes task 17158; patch by "teor".
12035 o Minor features (geoip):
12036 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
12039 o Minor bugfixes (assert, portability):
12040 - Fix an assertion failure in memarea.c on systems where "long" is
12041 shorter than the size of a pointer. Fixes bug 18716; bugfix
12044 o Minor bugfixes (bootstrap):
12045 - Consistently use the consensus download schedule for authority
12046 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
12048 o Minor bugfixes (build):
12049 - Remove a pair of redundant AM_CONDITIONAL declarations from
12050 configure.ac. Fixes one final case of bug 17744; bugfix
12052 - Resolve warnings when building on systems that are concerned with
12053 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
12055 - When libscrypt.h is found, but no libscrypt library can be linked,
12056 treat libscrypt as absent. Fixes bug 19161; bugfix
12059 o Minor bugfixes (client):
12060 - Turn all TestingClientBootstrap* into non-testing torrc options.
12061 This changes simply renames them by removing "Testing" in front of
12062 them and they do not require TestingTorNetwork to be enabled
12063 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
12064 - Make directory node selection more reliable, mainly for IPv6-only
12065 clients and clients with few reachable addresses. Fixes bug 18929;
12066 bugfix on 0.2.8.1-alpha. Patch by "teor".
12068 o Minor bugfixes (controller, microdescriptors):
12069 - Make GETINFO dir/status-vote/current/consensus conform to the
12070 control specification by returning "551 Could not open cached
12071 consensus..." when not caching consensuses. Fixes bug 18920;
12072 bugfix on 0.2.2.6-alpha.
12074 o Minor bugfixes (crypto, portability):
12075 - The SHA3 and SHAKE routines now produce the correct output on Big
12076 Endian systems. No code calls either algorithm yet, so this is
12077 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
12078 - Tor now builds again with the recent OpenSSL 1.1 development
12079 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
12082 o Minor bugfixes (directories):
12083 - When fetching extrainfo documents, compare their SHA256 digests
12084 and Ed25519 signing key certificates with the routerinfo that led
12085 us to fetch them, rather than with the most recent routerinfo.
12086 Otherwise we generate many spurious warnings about mismatches.
12087 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
12089 o Minor bugfixes (logging):
12090 - When we can't generate a signing key because OfflineMasterKey is
12091 set, do not imply that we should have been able to load it. Fixes
12092 bug 18133; bugfix on 0.2.7.2-alpha.
12093 - Stop periodic_event_dispatch() from blasting twelve lines per
12094 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
12095 - When rejecting a misformed INTRODUCE2 cell, only log at
12096 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
12098 o Minor bugfixes (pluggable transports):
12099 - Avoid reporting a spurious error when we decide that we don't need
12100 to terminate a pluggable transport because it has already exited.
12101 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
12103 o Minor bugfixes (pointer arithmetic):
12104 - Fix a bug in memarea_alloc() that could have resulted in remote
12105 heap write access, if Tor had ever passed an unchecked size to
12106 memarea_alloc(). Fortunately, all the sizes we pass to
12107 memarea_alloc() are pre-checked to be less than 128 kilobytes.
12108 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
12111 o Minor bugfixes (relays):
12112 - Consider more config options when relays decide whether to
12113 regenerate their descriptor. Fixes more of bug 12538; bugfix
12115 - Resolve some edge cases where we might launch an ORPort
12116 reachability check even when DisableNetwork is set. Noticed while
12117 fixing bug 18616; bugfix on 0.2.3.9-alpha.
12119 o Minor bugfixes (statistics):
12120 - We now include consensus downloads via IPv6 in our directory-
12121 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
12123 o Minor bugfixes (testing):
12124 - Allow directories in small networks to bootstrap by skipping
12125 DirPort checks when the consensus has no exits. Fixes bug 19003;
12126 bugfix on 0.2.8.1-alpha. Patch by teor.
12127 - Fix a small memory leak that would occur when the
12128 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
12129 bugfix on 0.2.5.2-alpha.
12131 o Minor bugfixes (time handling):
12132 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
12133 field. Otherwise, our unit tests crash on Windows. Fixes bug
12134 18977; bugfix on 0.2.2.25-alpha.
12137 - Document the contents of the 'datadir/keys' subdirectory in the
12138 manual page. Closes ticket 17621.
12139 - Stop recommending use of nicknames to identify relays in our
12140 MapAddress documentation. Closes ticket 18312.
12143 Changes in version 0.2.8.2-alpha - 2016-03-28
12144 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
12145 bugs in earlier versions of Tor, including some that prevented
12146 authorities using Tor 0.2.7.x from running correctly. IPv6 and
12147 directory support should also be much improved.
12149 o New system requirements:
12150 - Tor no longer supports versions of OpenSSL with a broken
12151 implementation of counter mode. (This bug was present in OpenSSL
12152 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
12153 longer runs with, these versions.
12154 - Tor no longer attempts to support platforms where the "time_t"
12155 type is unsigned. (To the best of our knowledge, only OpenVMS does
12156 this, and Tor has never actually built on OpenVMS.) Closes
12158 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
12159 later (released in 2008 and 2009 respectively). If you are
12160 building Tor from the git repository instead of from the source
12161 distribution, and your tools are older than this, you will need to
12162 upgrade. Closes ticket 17732.
12164 o Major bugfixes (security, pointers):
12165 - Avoid a difficult-to-trigger heap corruption attack when extending
12166 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12167 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12168 Reported by Guido Vranken.
12170 o Major bugfixes (bridges, pluggable transports):
12171 - Modify the check for OR connections to private addresses. Allow
12172 bridges on private addresses, including pluggable transports that
12173 ignore the (potentially private) address in the bridge line. Fixes
12174 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
12176 o Major bugfixes (compilation):
12177 - Repair hardened builds under the clang compiler. Previously, our
12178 use of _FORTIFY_SOURCE would conflict with clang's address
12179 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
12181 o Major bugfixes (crash on shutdown):
12182 - Correctly handle detaching circuits from muxes when shutting down.
12183 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
12184 - Fix an assert-on-exit bug related to counting memory usage in
12185 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
12187 o Major bugfixes (crash on startup):
12188 - Fix a segfault during startup: If a Unix domain socket was
12189 configured as listener (such as a ControlSocket or a SocksPort
12190 "unix:" socket), and tor was started as root but not configured to
12191 switch to another user, tor would segfault while trying to string
12192 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
12195 o Major bugfixes (dns proxy mode, crash):
12196 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12197 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12199 o Major bugfixes (relays, bridge clients):
12200 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
12201 bridge clients use the address configured in the bridge line.
12202 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
12205 o Major bugfixes (voting):
12206 - Actually enable support for authorities to match routers by their
12207 Ed25519 identities. Previously, the code had been written, but
12208 some debugging code that had accidentally been left in the
12209 codebase made it stay turned off. Fixes bug 17702; bugfix
12211 - When collating votes by Ed25519 identities, authorities now
12212 include a "NoEdConsensus" flag if the ed25519 value (or lack
12213 thereof) for a server does not reflect the majority consensus.
12214 Related to bug 17668; bugfix on 0.2.7.2-alpha.
12215 - When generating a vote with keypinning disabled, never include two
12216 entries for the same ed25519 identity. This bug was causing
12217 authorities to generate votes that they could not parse when a
12218 router violated key pinning by changing its RSA identity but
12219 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
12220 18318. Bugfix on 0.2.7.2-alpha.
12222 o Minor features (security, win32):
12223 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
12224 attack. Fixes bug 18123; bugfix on all tor versions. Patch
12227 o Minor features (bug-resistance):
12228 - Make Tor survive errors involving connections without a
12229 corresponding event object. Previously we'd fail with an
12230 assertion; now we produce a log message. Related to bug 16248.
12232 o Minor features (build):
12233 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
12234 as having possible IPFW support. Closes ticket 18448. Patch from
12235 Steven Chamberlain.
12237 o Minor features (code hardening):
12238 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
12239 level code, to harden against accidental failures to NUL-
12240 terminate. Part of ticket 17852. Patch from jsturgix. Found
12243 o Minor features (crypto):
12244 - Validate the hard-coded Diffie-Hellman parameters and ensure that
12245 p is a safe prime, and g is a suitable generator. Closes
12248 o Minor features (geoip):
12249 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
12252 o Minor features (hidden service directory):
12253 - Streamline relay-side hsdir handling: when relays consider whether
12254 to accept an uploaded hidden service descriptor, they no longer
12255 check whether they are one of the relays in the network that is
12256 "supposed" to handle that descriptor. Implements ticket 18332.
12258 o Minor features (IPv6):
12259 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
12260 to 1, tor prefers IPv6 directory addresses.
12261 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
12262 avoids using IPv4 for client OR and directory connections.
12263 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
12264 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
12265 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
12267 o Minor features (linux seccomp2 sandbox):
12268 - Reject attempts to change our Address with "Sandbox 1" enabled.
12269 Changing Address with Sandbox turned on would never actually work,
12270 but previously it would fail in strange and confusing ways. Found
12271 while fixing 18548.
12273 o Minor features (robustness):
12274 - Exit immediately with an error message if the code attempts to use
12275 Libevent without having initialized it. This should resolve some
12276 frequently-made mistakes in our unit tests. Closes ticket 18241.
12278 o Minor features (unix domain sockets):
12279 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
12280 Unix domain sockets without checking the permissions on the parent
12281 directory. (Tor checks permissions by default because some
12282 operating systems only check permissions on the parent directory.
12283 However, some operating systems do look at permissions on the
12284 socket, and tor's default check is unneeded.) Closes ticket 18458.
12287 o Minor bugfixes (exit policies, security):
12288 - Refresh an exit relay's exit policy when interface addresses
12289 change. Previously, tor only refreshed the exit policy when the
12290 configured external address changed. Fixes bug 18208; bugfix on
12291 0.2.7.3-rc. Patch by teor.
12293 o Minor bugfixes (security, hidden services):
12294 - Prevent hidden services connecting to client-supplied rendezvous
12295 addresses that are reserved as internal or multicast. Fixes bug
12296 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
12298 o Minor bugfixes (build):
12299 - Do not link the unit tests against both the testing and non-
12300 testing versions of the static libraries. Fixes bug 18490; bugfix
12302 - Avoid spurious failures from configure files related to calling
12303 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
12304 0.2.0.1-alpha. Patch from "cypherpunks".
12305 - Silence spurious clang-scan warnings in the ed25519_donna code by
12306 explicitly initializing some objects. Fixes bug 18384; bugfix on
12307 0.2.7.2-alpha. Patch by teor.
12309 o Minor bugfixes (client, bootstrap):
12310 - Count receipt of new microdescriptors as progress towards
12311 bootstrapping. Previously, with EntryNodes set, Tor might not
12312 successfully repopulate the guard set on bootstrapping. Fixes bug
12313 16825; bugfix on 0.2.3.1-alpha.
12315 o Minor bugfixes (code correctness):
12316 - Update to the latest version of Trunnel, which tries harder to
12317 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
12318 by clang address sanitizer. Fixes bug 18373; bugfix
12321 o Minor bugfixes (configuration):
12322 - Fix a tiny memory leak when parsing a port configuration ending in
12323 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
12325 o Minor bugfixes (containers):
12326 - If we somehow attempt to construct a heap with more than
12327 1073741822 elements, avoid an integer overflow when maintaining
12328 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
12330 o Minor bugfixes (correctness):
12331 - Fix a bad memory handling bug that would occur if we had queued a
12332 cell on a channel's incoming queue. Fortunately, we can't actually
12333 queue a cell like that as our code is constructed today, but it's
12334 best to avoid this kind of error, even if there isn't any code
12335 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
12337 o Minor bugfixes (directory):
12338 - When generating a URL for a directory server on an IPv6 address,
12339 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
12340 on 0.2.3.9-alpha. Patch from Malek.
12342 o Minor bugfixes (fallback directory mirrors):
12343 - When requesting extrainfo descriptors from a trusted directory
12344 server, check whether it is an authority or a fallback directory
12345 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
12346 0.2.4.7-alpha. Reported by atagar, patch by teor.
12348 o Minor bugfixes (hidden service, client):
12349 - Handle the case where the user makes several fast consecutive
12350 requests to the same .onion address. Previously, the first six
12351 requests would each trigger a descriptor fetch, each picking a
12352 directory (there are 6 overall) and the seventh one would fail
12353 because no directories were left, thereby triggering a close on
12354 all current directory connections asking for the hidden service.
12355 The solution here is to not close the connections if we have
12356 pending directory fetches. Fixes bug 15937; bugfix
12359 o Minor bugfixes (hidden service, control port):
12360 - Add the onion address to the HS_DESC event for the UPLOADED action
12361 both on success or failure. It was previously hardcoded with
12362 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
12364 o Minor bugfixes (hidden service, directory):
12365 - Bridges now refuse "rendezvous2" (hidden service descriptor)
12366 publish attempts. Suggested by ticket 18332.
12368 o Minor bugfixes (linux seccomp2 sandbox):
12369 - Allow the setrlimit syscall, and the prlimit and prlimit64
12370 syscalls, which some libc implementations use under the hood.
12371 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
12372 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
12373 enabled and no DNS resolvers configured. This should help TAILS
12374 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
12375 - Fix the sandbox's interoperability with unix domain sockets under
12376 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
12378 o Minor bugfixes (logging):
12379 - When logging information about an unparsable networkstatus vote or
12380 consensus, do not say "vote" when we mean consensus. Fixes bug
12381 18368; bugfix on 0.2.0.8-alpha.
12382 - Scrub service name in "unrecognized service ID" log messages.
12383 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
12384 - Downgrade logs and backtraces about IP versions to info-level.
12385 Only log backtraces once each time tor runs. Assists in diagnosing
12386 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
12387 Christian, patch by teor.
12389 o Minor bugfixes (memory safety):
12390 - Avoid freeing an uninitialized pointer when opening a socket fails
12391 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
12392 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
12394 - Correctly duplicate addresses in get_interface_address6_list().
12395 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
12396 patch by "cypherpunks".
12397 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
12399 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
12400 18672; bugfix on 0.2.5.1-alpha.
12402 o Minor bugfixes (private directory):
12403 - Prevent a race condition when creating private directories. Fixes
12404 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
12405 Patch from jsturgix. Found with Flawfinder.
12407 o Minor bugfixes (test networks, IPv6):
12408 - Allow internal IPv6 addresses in descriptors in test networks.
12409 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
12412 o Minor bugfixes (testing):
12413 - We no longer disable assertions in the unit tests when coverage is
12414 enabled. Instead, we require you to say --disable-asserts-in-tests
12415 to the configure script if you need assertions disabled in the
12416 unit tests (for example, if you want to perform branch coverage).
12417 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
12419 o Minor bugfixes (time parsing):
12420 - Avoid overflow in tor_timegm when parsing dates in and after 2038
12421 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
12422 0.0.2pre14. Patch by teor.
12424 o Minor bugfixes (tor-gencert):
12425 - Correctly handle the case where an authority operator enters a
12426 passphrase but sends an EOF before sending a newline. Fixes bug
12427 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
12429 o Code simplification and refactoring:
12430 - Quote all the string interpolations in configure.ac -- even those
12431 which we are pretty sure can't contain spaces. Closes ticket
12432 17744. Patch from zerosion.
12433 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
12434 inplace, so there's no need to have a separate implementation for
12435 the non-inplace code. Closes ticket 18258. Patch from Malek.
12436 - Simplify return types for some crypto functions that can't
12437 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
12440 - Change build messages to refer to "Fedora" instead of "Fedora
12441 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
12442 Patches from "icanhasaccount" and "cypherpunks".
12444 o Removed features:
12445 - We no longer maintain an internal freelist in memarea.c.
12446 Allocators should be good enough to make this code unnecessary,
12447 and it's doubtful that it ever had any performance benefit.
12450 - Fix several warnings from clang's address sanitizer produced in
12452 - Treat backtrace test failures as expected on FreeBSD until we
12453 solve bug 17808. Closes ticket 18204.
12456 Changes in version 0.2.8.1-alpha - 2016-02-04
12457 Tor 0.2.8.1-alpha is the first alpha release in its series. It
12458 includes numerous small features and bugfixes against previous Tor
12459 versions, and numerous small infrastructure improvements. The most
12460 notable features are a set of improvements to the directory subsystem.
12462 o Major features (security, Linux):
12463 - When Tor starts as root on Linux and is told to switch user ID, it
12464 can now retain the capability to bind to low ports. By default,
12465 Tor will do this only when it's switching user ID and some low
12466 ports have been configured. You can change this behavior with the
12467 new option KeepBindCapabilities. Closes ticket 8195.
12469 o Major features (directory system):
12470 - When bootstrapping multiple consensus downloads at a time, use the
12471 first one that starts downloading, and close the rest. This
12472 reduces failures when authorities or fallback directories are slow
12473 or down. Together with the code for feature 15775, this feature
12474 should reduces failures due to fallback churn. Implements ticket
12475 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
12476 "mikeperry" and "teor".
12477 - Include a trial list of 21 default fallback directories, generated
12478 in January 2016, based on an opt-in survey of suitable relays.
12479 Doing this should make clients bootstrap more quickly and reliably,
12480 and reduce the load on the directory authorities. Closes ticket
12481 15775. Patch by "teor".
12482 Candidates identified using an OnionOO script by "weasel", "teor",
12483 "gsathya", and "karsten".
12484 - Previously only relays that explicitly opened a directory port
12485 (DirPort) accepted directory requests from clients. Now all
12486 relays, with and without a DirPort, accept and serve tunneled
12487 directory requests that they receive through their ORPort. You can
12488 disable this behavior using the new DirCache option. Closes
12491 o Major key updates:
12492 - Update the V3 identity key for the dannenberg directory authority:
12493 it was changed on 18 November 2015. Closes task 17906. Patch
12496 o Minor features (security, clock):
12497 - Warn when the system clock appears to move back in time (when the
12498 state file was last written in the future). Tor doesn't know that
12499 consensuses have expired if the clock is in the past. Patch by
12500 "teor". Implements ticket 17188.
12502 o Minor features (security, exit policies):
12503 - ExitPolicyRejectPrivate now rejects more private addresses by
12504 default. Specifically, it now rejects the relay's outbound bind
12505 addresses (if configured), and the relay's configured port
12506 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
12507 0.2.0.11-alpha. Patch by "teor".
12509 o Minor features (security, memory erasure):
12510 - Set the unused entries in a smartlist to NULL. This helped catch
12511 a (harmless) bug, and shouldn't affect performance too much.
12512 Implements ticket 17026.
12513 - Use SecureMemoryWipe() function to securely clean memory on
12514 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
12515 Implements feature 17986.
12516 - Use explicit_bzero or memset_s when present. Previously, we'd use
12517 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
12518 from <logan@hackers.mu> and <selven@hackers.mu>.
12519 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12520 zero size. Check size argument to memwipe() for underflow. Fixes
12521 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12524 o Minor features (security, RNG):
12525 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
12526 positively are not allowed to fail. Previously we depended on
12527 internal details of OpenSSL's behavior. Closes ticket 17686.
12528 - Never use the system entropy output directly for anything besides
12529 seeding the PRNG. When we want to generate important keys, instead
12530 of using system entropy directly, we now hash it with the PRNG
12531 stream. This may help resist certain attacks based on broken OS
12532 entropy implementations. Closes part of ticket 17694.
12533 - Use modern system calls (like getentropy() or getrandom()) to
12534 generate strong entropy on platforms that have them. Closes
12537 o Minor features (accounting):
12538 - Added two modes to the AccountingRule option: One for limiting
12539 only the number of bytes sent ("AccountingRule out"), and one for
12540 limiting only the number of bytes received ("AccountingRule in").
12541 Closes ticket 15989; patch from "unixninja92".
12543 o Minor features (build):
12544 - Since our build process now uses "make distcheck", we no longer
12545 force "make dist" to depend on "make check". Closes ticket 17893;
12546 patch from "cypherpunks."
12547 - Tor now builds successfully with the recent OpenSSL 1.1
12548 development branch, and with the latest LibreSSL. Closes tickets
12549 17549, 17921, and 17984.
12551 o Minor features (controller):
12552 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
12553 tickets 16774 and 17817. Patch by George Tankersley.
12554 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
12555 service descriptor from a service's local hidden service
12556 descriptor cache. Closes ticket 14846.
12557 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
12558 controllers can examine the the reject rules added by
12559 ExitPolicyRejectPrivate. This makes it easier for stem to display
12562 o Minor features (crypto):
12563 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
12565 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
12566 - When allocating a digest state object, allocate no more space than
12567 we actually need. Previously, we would allocate as much space as
12568 the state for the largest algorithm would need. This change saves
12569 up to 672 bytes per circuit. Closes ticket 17796.
12570 - Improve performance when hashing non-multiple of 8 sized buffers,
12571 based on Andrew Moon's public domain SipHash-2-4 implementation.
12572 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
12574 o Minor features (directory downloads):
12575 - Wait for busy authorities and fallback directories to become non-
12576 busy when bootstrapping. (A similar change was made in 6c443e987d
12577 for directory caches chosen from the consensus.) Closes ticket
12578 17864; patch by "teor".
12579 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
12580 directory mirrors. The default is 1; set it to 0 to disable
12581 fallbacks. Implements ticket 17576. Patch by "teor".
12583 o Minor features (geoip):
12584 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
12587 o Minor features (IPv6):
12588 - Add an argument 'ipv6=address:orport' to the DirAuthority and
12589 FallbackDir torrc options, to specify an IPv6 address for an
12590 authority or fallback directory. Add hard-coded ipv6 addresses for
12591 directory authorities that have them. Closes ticket 17327; patch
12592 from Nick Mathewson and "teor".
12593 - Add address policy assume_action support for IPv6 addresses.
12594 - Limit IPv6 mask bits to 128.
12595 - Warn when comparing against an AF_UNSPEC address in a policy, it's
12596 almost always a bug. Closes ticket 17863; patch by "teor".
12597 - Allow users to configure directory authorities and fallback
12598 directory servers with IPv6 addresses and ORPorts. Resolves
12600 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
12601 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
12602 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
12603 17638; bugfix on 0.0.2pre8. Patch by "teor".
12605 o Minor features (logging):
12606 - When logging to syslog, allow a tag to be added to the syslog
12607 identity (the string prepended to every log message). The tag can
12608 be configured with SyslogIdentityTag and defaults to none. Setting
12609 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
12612 o Minor features (portability):
12613 - Use timingsafe_memcmp() where available. Closes ticket 17944;
12614 patch from <logan@hackers.mu>.
12616 o Minor features (relay, address discovery):
12617 - Add a family argument to get_interface_addresses_raw() and
12618 subfunctions to make network interface address interogation more
12619 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
12620 types of interfaces from the operating system. Resolves
12622 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
12623 fails to enumerate interface addresses using the platform-specific
12624 API, have it rely on the UDP socket fallback technique to try and
12625 find out what IP addresses (both IPv4 and IPv6) our machine has.
12626 Resolves ticket 17951.
12628 o Minor features (replay cache):
12629 - The replay cache now uses SHA256 instead of SHA1. Implements
12630 feature 8961. Patch by "teor", issue reported by "rransom".
12632 o Minor features (unix file permissions):
12633 - Defer creation of Unix sockets until after setuid. This avoids
12634 needing CAP_CHOWN and CAP_FOWNER when using systemd's
12635 CapabilityBoundingSet, or chown and fowner when using SELinux.
12636 Implements part of ticket 17562. Patch from Jamie Nguyen.
12637 - If any directory created by Tor is marked as group readable, the
12638 filesystem group is allowed to be either the default GID or the
12639 root user. Allowing root to read the DataDirectory prevents the
12640 need for CAP_READ_SEARCH when using systemd's
12641 CapabilityBoundingSet, or dac_read_search when using SELinux.
12642 Implements part of ticket 17562. Patch from Jamie Nguyen.
12643 - Introduce a new DataDirectoryGroupReadable option. If it is set to
12644 1, the DataDirectory will be made readable by the default GID.
12645 Implements part of ticket 17562. Patch from Jamie Nguyen.
12647 o Minor bugfixes (accounting):
12648 - The max bandwidth when using 'AccountRule sum' is now correctly
12649 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
12650 from "unixninja92".
12652 o Minor bugfixes (code correctness):
12653 - When closing an entry connection, generate a warning if we should
12654 have sent an end cell for it but we haven't. Fixes bug 17876;
12655 bugfix on 0.2.3.2-alpha.
12656 - Assert that allocated memory held by the reputation code is freed
12657 according to its internal counters. Fixes bug 17753; bugfix
12659 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
12662 o Minor bugfixes (compilation):
12663 - Mark all object files that include micro-revision.i as depending
12664 on it, so as to make parallel builds more reliable. Fixes bug
12665 17826; bugfix on 0.2.5.1-alpha.
12666 - Don't try to use the pthread_condattr_setclock() function unless
12667 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
12668 17819; bugfix on 0.2.6.3-alpha.
12669 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
12671 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12672 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12673 - Fix search for libevent libraries on OpenBSD (and other systems
12674 that install libevent 1 and libevent 2 in parallel). Fixes bug
12675 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
12676 - Isolate environment variables meant for tests from the rest of the
12677 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
12678 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
12680 - Remove config.log only from make distclean, not from make clean.
12681 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
12683 o Minor bugfixes (crypto):
12684 - Check the return value of HMAC() and assert on failure. Fixes bug
12685 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
12687 o Minor bugfixes (fallback directories):
12688 - Mark fallbacks as "too busy" when they return a 503 response,
12689 rather than just marking authorities. Fixes bug 17572; bugfix on
12690 0.2.4.7-alpha. Patch by "teor".
12692 o Minor bugfixes (IPv6):
12693 - Update the limits in max_dl_per_request for IPv6 address length.
12694 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
12696 o Minor bugfixes (linux seccomp2 sandbox):
12697 - Fix a crash when using offline master ed25519 keys with the Linux
12698 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
12700 o Minor bugfixes (logging):
12701 - In log messages that include a function name, use __FUNCTION__
12702 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
12703 with clang __PRETTY_FUNCTION__ has extra information we don't
12704 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
12706 - Remove needless quotes from a log message about unparseable
12707 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
12709 o Minor bugfixes (portability):
12710 - Remove an #endif from configure.ac so that we correctly detect the
12711 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
12714 o Minor bugfixes (relays):
12715 - Check that both the ORPort and DirPort (if present) are reachable
12716 before publishing a relay descriptor. Otherwise, relays publish a
12717 descriptor with DirPort 0 when the DirPort reachability test takes
12718 longer than the ORPort reachability test. Fixes bug 18050; bugfix
12719 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
12721 o Minor bugfixes (relays, hidden services):
12722 - Refuse connection requests to private OR addresses unless
12723 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
12724 then refuse to send any cells to a private address. Fixes bugs
12725 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
12727 o Minor bugfixes (safe logging):
12728 - When logging a malformed hostname received through socks4, scrub
12729 it if SafeLogging says we should. Fixes bug 17419; bugfix
12732 o Minor bugfixes (statistics code):
12733 - Consistently check for overflow in round_*_to_next_multiple_of
12734 functions, and add unit tests with additional and maximal values.
12735 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
12736 - Handle edge cases in the laplace functions: avoid division by
12737 zero, avoid taking the log of zero, and silence clang type
12738 conversion warnings using round and trunc. Add unit tests for edge
12739 cases with maximal values. Fixes part of bug 13192; bugfix
12742 o Minor bugfixes (testing):
12743 - The test for log_heartbeat was incorrectly failing in timezones
12744 with non-integer offsets. Instead of comparing the end of the time
12745 string against a constant, compare it to the output of
12746 format_local_iso_time when given the correct input. Fixes bug
12747 18039; bugfix on 0.2.5.4-alpha.
12748 - Make unit tests pass on IPv6-only systems, and systems without
12749 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
12750 bugfix on 0.2.7.3-rc. Patch by "teor".
12751 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
12753 - Check the full results of SHA256 and SHA512 digests in the unit
12754 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
12756 o Code simplification and refactoring:
12757 - Move logging of redundant policy entries in
12758 policies_parse_exit_policy_internal into its own function. Closes
12759 ticket 17608; patch from "juce".
12760 - Extract the more complicated parts of circuit_mark_for_close()
12761 into a new function that we run periodically before circuits are
12762 freed. This change removes more than half of the functions
12763 currently in the "blob". Closes ticket 17218.
12764 - Clean up a little duplicated code in
12765 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
12767 - Decouple the list of streams waiting to be attached to circuits
12768 from the overall connection list. This change makes it possible to
12769 attach streams quickly while simplifying Tor's callgraph and
12770 avoiding O(N) scans of the entire connection list. Closes
12772 - When a direct directory request fails immediately on launch,
12773 instead of relaunching that request from inside the code that
12774 launches it, instead mark the connection for teardown. This change
12775 simplifies Tor's callback and prevents the directory-request
12776 launching code from invoking itself recursively. Closes
12778 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
12779 use them. Closes ticket 17926.
12782 - Add a description of the correct use of the '--keygen' command-
12783 line option. Closes ticket 17583; based on text by 's7r'.
12784 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
12785 - Explain actual minima for BandwidthRate. Closes ticket 16382.
12786 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
12787 - Mention torspec URL in the manpage and point the reader to it
12788 whenever we mention a document that belongs in torspce. Fixes
12791 o Removed features:
12792 - Remove client-side support for connecting to Tor relays running
12793 versions of Tor before 0.2.3.6-alpha. These relays didn't support
12794 the v3 TLS handshake protocol, and are no longer allowed on the
12795 Tor network. Implements the client side of ticket 11150. Based on
12796 patches by Tom van der Woerdt.
12799 - Add unit tests to check for common RNG failure modes, such as
12800 returning all zeroes, identical values, or incrementing values
12801 (OpenSSL's rand_predictable feature). Patch by "teor".
12802 - Log more information when the backtrace tests fail. Closes ticket
12803 17892. Patch from "cypherpunks."
12804 - Always test both ed25519 backends, so that we can be sure that our
12805 batch-open replacement code works. Part of ticket 16794.
12806 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
12807 portion of ticket 16831.
12808 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
12809 util_format.c, directory.c, and options_validate.c. Closes tickets
12810 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
12812 - Unit tests for directory_handle_command_get. Closes ticket 17004.
12813 Patch from Reinaldo de Souza Jr.
12816 Changes in version 0.2.7.6 - 2015-12-10
12817 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
12818 well as a minor bug in hidden service reliability.
12820 o Major bugfixes (guard selection):
12821 - Actually look at the Guard flag when selecting a new directory
12822 guard. When we implemented the directory guard design, we
12823 accidentally started treating all relays as if they have the Guard
12824 flag during guard selection, leading to weaker anonymity and worse
12825 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12828 o Minor features (geoip):
12829 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
12832 o Minor bugfixes (compilation):
12833 - When checking for net/pfvar.h, include netinet/in.h if possible.
12834 This fixes transparent proxy detection on OpenBSD. Fixes bug
12835 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
12836 - Fix a compilation warning with Clang 3.6: Do not check the
12837 presence of an address which can never be NULL. Fixes bug 17781.
12839 o Minor bugfixes (correctness):
12840 - When displaying an IPv6 exit policy, include the mask bits
12841 correctly even when the number is greater than 31. Fixes bug
12842 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
12843 - The wrong list was used when looking up expired intro points in a
12844 rend service object, causing what we think could be reachability
12845 issues for hidden services, and triggering a BUG log. Fixes bug
12846 16702; bugfix on 0.2.7.2-alpha.
12847 - Fix undefined behavior in the tor_cert_checksig function. Fixes
12848 bug 17722; bugfix on 0.2.7.2-alpha.
12851 Changes in version 0.2.7.5 - 2015-11-20
12852 The Tor 0.2.7 release series is dedicated to the memory of Tor user
12853 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
12854 tirelessly to advocate human rights regardless of national borders,
12855 and oppose the encroachments of mass surveillance. He opposed national
12856 exceptionalism, he brought clarity to legal and policy debates, he
12857 understood and predicted the impact of mass surveillance on the world,
12858 and he laid the groundwork for resisting it. While serving on the Tor
12859 Project's board of directors, he brought us his uncompromising focus
12860 on technical excellence in the service of humankind. Caspar was an
12861 inimitable force for good and a wonderful friend. He was kind,
12862 humorous, generous, gallant, and believed we should protect one
12863 another without exception. We honor him here for his ideals, his
12864 efforts, and his accomplishments. Please honor his memory with works
12865 that would make him proud.
12867 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
12869 The 0.2.7 series adds a more secure identity key type for relays,
12870 improves cryptography performance, resolves several longstanding
12871 hidden-service performance issues, improves controller support for
12872 hidden services, and includes small bugfixes and performance
12873 improvements throughout the program. This release series also includes
12874 more tests than before, and significant simplifications to which parts
12875 of Tor invoke which others.
12877 (This release contains no code changes since 0.2.7.4-rc.)
12880 Changes in version 0.2.7.4-rc - 2015-10-21
12881 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
12882 fixes some important memory leaks, and a scary-looking (but mostly
12883 harmless in practice) invalid-read bug. It also has a few small
12884 bugfixes, notably fixes for compilation and portability on different
12885 platforms. If no further significant bounds are found, the next
12886 release will the the official stable release.
12888 o Major bugfixes (security, correctness):
12889 - Fix an error that could cause us to read 4 bytes before the
12890 beginning of an openssl string. This bug could be used to cause
12891 Tor to crash on systems with unusual malloc implementations, or
12892 systems with unusual hardening installed. Fixes bug 17404; bugfix
12895 o Major bugfixes (correctness):
12896 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
12897 bug 17401; bugfix on 0.2.7.3-rc.
12899 o Major bugfixes (memory leaks):
12900 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
12901 17398; bugfix on 0.2.6.1-alpha.
12902 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
12903 17402; bugfix on 0.2.7.3-rc.
12904 - Fix a memory leak when reading an expired signing key from disk.
12905 Fixes bug 17403; bugfix on 0.2.7.2-rc.
12907 o Minor features (geoIP):
12908 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
12911 o Minor bugfixes (compilation):
12912 - Repair compilation with the most recent (unreleased, alpha)
12913 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
12914 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
12915 17251; bugfix on 0.2.7.2-alpha.
12916 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12917 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12919 o Minor bugfixes (portability):
12920 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
12921 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
12924 o Minor bugfixes (sandbox):
12925 - Add the "hidserv-stats" filename to our sandbox filter for the
12926 HiddenServiceStatistics option to work properly. Fixes bug 17354;
12927 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
12929 o Minor bugfixes (testing):
12930 - Add unit tests for get_interface_address* failure cases. Fixes bug
12931 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
12932 - Fix breakage when running 'make check' with BSD make. Fixes bug
12933 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
12934 - Make the get_ifaddrs_* unit tests more tolerant of different
12935 network configurations. (Don't assume every test box has an IPv4
12936 address, and don't assume every test box has a non-localhost
12937 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
12938 - Skip backtrace tests when backtrace support is not compiled in.
12939 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
12943 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
12944 - Note that HiddenServicePorts can take a unix domain socket. Closes
12948 Changes in version 0.2.7.3-rc - 2015-09-25
12949 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
12950 contains numerous usability fixes for Ed25519 keys, safeguards against
12951 several misconfiguration problems, significant simplifications to
12952 Tor's callgraph, and numerous bugfixes and small features.
12954 This is the most tested release of Tor to date. The unit tests cover
12955 39.40% of the code, and the integration tests (accessible with "make
12956 test-full-online", requiring stem and chutney and a network
12957 connection) raise the coverage to 64.49%.
12959 o Major features (security, hidden services):
12960 - Hidden services, if using the EntryNodes option, are required to
12961 use more than one EntryNode, in order to avoid a guard discovery
12962 attack. (This would only affect people who had configured hidden
12963 services and manually specified the EntryNodes option with a
12964 single entry-node. The impact was that it would be easy to
12965 remotely identify the guard node used by such a hidden service.
12966 See ticket for more information.) Fixes ticket 14917.
12968 o Major features (Ed25519 keys, keypinning):
12969 - The key-pinning option on directory authorities is now advisory-
12970 only by default. In a future version, or when the AuthDirPinKeys
12971 option is set, pins are enforced again. Disabling key-pinning
12972 seemed like a good idea so that we can survive the fallout of any
12973 usability problems associated with Ed25519 keys. Closes
12976 o Major features (Ed25519 performance):
12977 - Improve the speed of Ed25519 operations and Curve25519 keypair
12978 generation when built targeting 32 bit x86 platforms with SSE2
12979 available. Implements ticket 16535.
12980 - Improve the runtime speed of Ed25519 signature verification by
12981 using Ed25519-donna's batch verification support. Implements
12984 o Major features (performance testing):
12985 - The test-network.sh script now supports performance testing.
12986 Requires corresponding chutney performance testing changes. Patch
12987 by "teor". Closes ticket 14175.
12989 o Major features (relay, Ed25519):
12990 - Significant usability improvements for Ed25519 key management. Log
12991 messages are better, and the code can recover from far more
12992 failure conditions. Thanks to "s7r" for reporting and diagnosing
12994 - Add a new OfflineMasterKey option to tell Tor never to try loading
12995 or generating a secret Ed25519 identity key. You can use this in
12996 combination with tor --keygen to manage offline and/or encrypted
12997 Ed25519 keys. Implements ticket 16944.
12998 - Add a --newpass option to allow changing or removing the
12999 passphrase of an encrypted key with tor --keygen. Implements part
13001 - On receiving a HUP signal, check to see whether the Ed25519
13002 signing key has changed, and reload it if so. Closes ticket 16790.
13004 o Major bugfixes (relay, Ed25519):
13005 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
13006 0.2.7.2-alpha. Reported by "s7r".
13007 - Improve handling of expired signing keys with offline master keys.
13008 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
13010 o Minor features (client-side privacy):
13011 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
13012 lifespan when IsolateSOCKSAuth and streams with SOCKS
13013 authentication are attached to the circuit. This allows
13014 applications like TorBrowser to manage circuit lifetime on their
13015 own. Implements feature 15482.
13016 - When logging malformed hostnames from SOCKS5 requests, respect
13017 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
13019 o Minor features (compilation):
13020 - Give a warning as early as possible when trying to build with an
13021 unsupported OpenSSL version. Closes ticket 16901.
13022 - Fail during configure if we're trying to build against an OpenSSL
13023 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
13024 which started requiring ECC.
13026 o Minor features (geoip):
13027 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
13030 o Minor features (hidden services):
13031 - Relays need to have the Fast flag to get the HSDir flag. As this
13032 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
13033 drop. This change should make some attacks against the hidden
13034 service directory system harder. Fixes ticket 15963.
13035 - Turn on hidden service statistics collection by setting the torrc
13036 option HiddenServiceStatistics to "1" by default. (This keeps
13037 track only of the fraction of traffic used by hidden services, and
13038 the total number of hidden services in existence.) Closes
13040 - Client now uses an introduction point failure cache to know when
13041 to fetch or keep a descriptor in their cache. Previously, failures
13042 were recorded implicitly, but not explicitly remembered. Closes
13045 o Minor features (testing, authorities, documentation):
13046 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
13047 explicitly manage consensus flags in testing networks. Patch by
13048 "robgjansen", modified by "teor". Implements part of ticket 14882.
13050 o Minor bugfixes (security, exit policies):
13051 - ExitPolicyRejectPrivate now also rejects the relay's published
13052 IPv6 address (if any), and any publicly routable IPv4 or IPv6
13053 addresses on any local interfaces. ticket 17027. Patch by "teor".
13054 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
13056 o Minor bug fixes (torrc exit policies):
13057 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
13058 produce IPv6 wildcard addresses. Previously they would produce
13059 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
13060 of bug 16069; bugfix on 0.2.4.7-alpha.
13061 - When parsing torrc ExitPolicies, we now warn for a number of cases
13062 where the user's intent is likely to differ from Tor's actual
13063 behavior. These include: using an IPv4 address with an accept6 or
13064 reject6 line; using "private" on an accept6 or reject6 line; and
13065 including any ExitPolicy lines after accept *:* or reject *:*.
13066 Related to ticket 16069.
13067 - When parsing torrc ExitPolicies, we now issue an info-level
13068 message when expanding an "accept/reject *" line to include both
13069 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
13070 - In each instance above, usage advice is provided to avoid the
13071 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
13072 16069; bugfix on 0.2.4.7-alpha.
13074 o Minor bugfixes (authority):
13075 - Don't assign "HSDir" to a router if it isn't Valid and Running.
13076 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
13077 - Downgrade log messages about Ed25519 key issues if they are in old
13078 cached router descriptors. Fixes part of bug 16286; bugfix
13080 - When we find an Ed25519 key issue in a cached descriptor, stop
13081 saying the descriptor was just "uploaded". Fixes another part of
13082 bug 16286; bugfix on 0.2.7.2-alpha.
13084 o Minor bugfixes (control port):
13085 - Repair a warning and a spurious result when getting the maximum
13086 number of file descriptors from the controller. Fixes bug 16697;
13087 bugfix on 0.2.7.2-alpha.
13089 o Minor bugfixes (correctness):
13090 - When calling channel_free_list(), avoid calling smartlist_remove()
13091 while inside a FOREACH loop. This partially reverts commit
13092 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
13093 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
13095 o Minor bugfixes (documentation):
13096 - Advise users on how to configure separate IPv4 and IPv6 exit
13097 policies in the manpage and sample torrcs. Related to ticket 16069.
13098 - Fix the usage message of tor-resolve(1) so that it no longer lists
13099 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
13100 - Fix an error in the manual page and comments for
13101 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
13102 required "ORPort connectivity". While this is true, it is in no
13103 way unique to the HSDir flag. Of all the flags, only HSDirs need a
13104 DirPort configured in order for the authorities to assign that
13105 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
13108 o Minor bugfixes (Ed25519):
13109 - Fix a memory leak when reading router descriptors with expired
13110 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
13112 o Minor bugfixes (linux seccomp2 sandbox):
13113 - Allow bridge authorities to run correctly under the seccomp2
13114 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
13115 - Allow routers with ed25519 keys to run correctly under the
13116 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
13118 o Minor bugfixes (open file limit):
13119 - Fix set_max_file_descriptors() to set by default the max open file
13120 limit to the current limit when setrlimit() fails. Fixes bug
13121 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
13123 o Minor bugfixes (portability):
13124 - Try harder to normalize the exit status of the Tor process to the
13125 standard-provided range. Fixes bug 16975; bugfix on every version
13127 - Check correctly for Windows socket errors in the workqueue
13128 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
13129 - Fix the behavior of crypto_rand_time_range() when told to consider
13130 times before 1970. (These times were possible when running in a
13131 simulated network environment where time()'s output starts at
13132 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
13133 - Restore correct operation of TLS client-cipher detection on
13134 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
13136 o Minor bugfixes (relay):
13137 - Ensure that worker threads actually exit when a fatal error or
13138 shutdown is indicated. This fix doesn't currently affect the
13139 behavior of Tor, because Tor workers never indicates fatal error
13140 or shutdown except in the unit tests. Fixes bug 16868; bugfix
13142 - Unblock threads before releasing the work queue mutex to ensure
13143 predictable scheduling behavior. Fixes bug 16644; bugfix
13146 o Code simplification and refactoring:
13147 - Change the function that's called when we need to retry all
13148 downloads so that it only reschedules the downloads to happen
13149 immediately, rather than launching them all at once itself. This
13150 further simplifies Tor's callgraph.
13151 - Move some format-parsing functions out of crypto.c and
13152 crypto_curve25519.c into crypto_format.c and/or util_format.c.
13153 - Move the client-only parts of init_keys() into a separate
13154 function. Closes ticket 16763.
13155 - Simplify the microdesc_free() implementation so that it no longer
13156 appears (to code analysis tools) to potentially invoke a huge
13157 suite of other microdesc functions.
13158 - Simply the control graph further by deferring the inner body of
13159 directory_all_unreachable() into a callback. Closes ticket 16762.
13160 - Treat the loss of an owning controller as equivalent to a SIGTERM
13161 signal. This removes a tiny amount of duplicated code, and
13162 simplifies our callgraph. Closes ticket 16788.
13163 - When generating an event to send to the controller, we no longer
13164 put the event over the network immediately. Instead, we queue
13165 these events, and use a Libevent callback to deliver them. This
13166 change simplifies Tor's callgraph by reducing the number of
13167 functions from which all other Tor functions are reachable. Closes
13169 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
13170 that try to scan or compile every file on Unix won't decide that
13172 - Remove the unused "nulterminate" argument from buf_pullup().
13175 - Recommend a 40 GB example AccountingMax in torrc.sample rather
13176 than a 4 GB max. Closes ticket 16742.
13177 - Include the TUNING document in our source tarball. It is referred
13178 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
13182 - The internal pure-C tor-fw-helper tool is now removed from the Tor
13183 distribution, in favor of the pure-Go clone available from
13184 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
13185 used by the C tor-fw-helper are not, in our opinion, very
13186 confidence- inspiring in their secure-programming techniques.
13187 Closes ticket 13338.
13188 - Remove the code that would try to aggressively flush controller
13189 connections while writing to them. This code was introduced in
13190 0.1.2.7-alpha, in order to keep output buffers from exceeding
13191 their limits. But there is no longer a maximum output buffer size,
13192 and flushing data in this way caused some undesirable recursions
13193 in our call graph. Closes ticket 16480.
13196 - Make "bridges+hs" the default test network. This tests almost all
13197 tor functionality during make test-network, while allowing tests
13198 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
13199 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
13200 (chutney). Patches by "teor".
13201 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
13202 by-side in the same parent directory. Closes ticket 16903. Patch
13204 - Use environment variables rather than autoconf substitutions to
13205 send variables from the build system to the test scripts. This
13206 change should be easier to maintain, and cause 'make distcheck' to
13207 work better than before. Fixes bug 17148.
13208 - Add a new set of callgraph analysis scripts that use clang to
13209 produce a list of which Tor functions are reachable from which
13210 other Tor functions. We're planning to use these to help simplify
13211 our code structure by identifying illogical dependencies.
13212 - Add new 'test-full' and 'test-full-online' targets to run all
13213 tests, including integration tests with stem and chutney.
13214 - Make the test-workqueue test work on Windows by initializing the
13215 network before we begin.
13216 - New make target (make test-network-all) to run multiple applicable
13217 chutney test cases. Patch from Teor; closes 16953.
13218 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
13219 functions in dns.c. Implements a portion of ticket 16831.
13220 - When building Tor with testing coverage enabled, run Chutney tests
13221 (if any) using the 'tor-cov' coverage binary.
13222 - When running test-network or test-stem, check for the absence of
13223 stem/chutney before doing any build operations.
13226 Changes in version 0.2.7.2-alpha - 2015-07-27
13227 This, the second alpha in the Tor 0.2.7 series, has a number of new
13228 features, including a way to manually pick the number of introduction
13229 points for hidden services, and the much stronger Ed25519 signing key
13230 algorithm for regular Tor relays (including support for encrypted
13231 offline identity keys in the new algorithm).
13233 Support for Ed25519 on relays is currently limited to signing router
13234 descriptors; later alphas in this series will extend Ed25519 key
13235 support to more parts of the Tor protocol.
13237 o Major features (Ed25519 identity keys, Proposal 220):
13238 - All relays now maintain a stronger identity key, using the Ed25519
13239 elliptic curve signature format. This master key is designed so
13240 that it can be kept offline. Relays also generate an online
13241 signing key, and a set of other Ed25519 keys and certificates.
13242 These are all automatically regenerated and rotated as needed.
13243 Implements part of ticket 12498.
13244 - Directory authorities now vote on Ed25519 identity keys along with
13245 RSA1024 keys. Implements part of ticket 12498.
13246 - Directory authorities track which Ed25519 identity keys have been
13247 used with which RSA1024 identity keys, and do not allow them to
13248 vary freely. Implements part of ticket 12498.
13249 - Microdescriptors now include Ed25519 identity keys. Implements
13250 part of ticket 12498.
13251 - Add support for offline encrypted Ed25519 master keys. To use this
13252 feature on your tor relay, run "tor --keygen" to make a new master
13253 key (or to make a new signing key if you already have a master
13254 key). Closes ticket 13642.
13256 o Major features (Hidden services):
13257 - Add the torrc option HiddenServiceNumIntroductionPoints, to
13258 specify a fixed number of introduction points. Its maximum value
13259 is 10 and default is 3. Using this option can increase a hidden
13260 service's reliability under load, at the cost of making it more
13261 visible that the hidden service is facing extra load. Closes
13263 - Remove the adaptive algorithm for choosing the number of
13264 introduction points, which used to change the number of
13265 introduction points (poorly) depending on the number of
13266 connections the HS sees. Closes ticket 4862.
13268 o Major features (onion key cross-certification):
13269 - Relay descriptors now include signatures of their own identity
13270 keys, made using the TAP and ntor onion keys. These signatures
13271 allow relays to prove ownership of their own onion keys. Because
13272 of this change, microdescriptors will no longer need to include
13273 RSA identity keys. Implements proposal 228; closes ticket 12499.
13275 o Major features (performance):
13276 - Improve the runtime speed of Ed25519 operations by using the
13277 public-domain Ed25519-donna by Andrew M. ("floodyberry").
13278 Implements ticket 16467.
13279 - Improve the runtime speed of the ntor handshake by using an
13280 optimized curve25519 basepoint scalarmult implementation from the
13281 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
13282 ideas by Adam Langley. Implements ticket 9663.
13284 o Major bugfixes (client-side privacy, also in 0.2.6.9):
13285 - Properly separate out each SOCKSPort when applying stream
13286 isolation. The error occurred because each port's session group
13287 was being overwritten by a default value when the listener
13288 connection was initialized. Fixes bug 16247; bugfix on
13289 0.2.6.3-alpha. Patch by "jojelino".
13291 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
13292 - Stop refusing to store updated hidden service descriptors on a
13293 client. This reverts commit 9407040c59218 (which indeed fixed bug
13294 14219, but introduced a major hidden service reachability
13295 regression detailed in bug 16381). This is a temporary fix since
13296 we can live with the minor issue in bug 14219 (it just results in
13297 some load on the network) but the regression of 16381 is too much
13298 of a setback. First-round fix for bug 16381; bugfix
13301 o Major bugfixes (hidden services):
13302 - When cannibalizing a circuit for an introduction point, always
13303 extend to the chosen exit node (creating a 4 hop circuit).
13304 Previously Tor would use the current circuit exit node, which
13305 changed the original choice of introduction point, and could cause
13306 the hidden service to skip excluded introduction points or
13307 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
13310 o Major bugfixes (open file limit):
13311 - The open file limit wasn't checked before calling
13312 tor_accept_socket_nonblocking(), which would make Tor exceed the
13313 limit. Now, before opening a new socket, Tor validates the open
13314 file limit just before, and if the max has been reached, return an
13315 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
13317 o Major bugfixes (stability, also in 0.2.6.10):
13318 - Stop crashing with an assertion failure when parsing certain kinds
13319 of malformed or truncated microdescriptors. Fixes bug 16400;
13320 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13321 by "cypherpunks_backup".
13322 - Stop random client-side assertion failures that could occur when
13323 connecting to a busy hidden service, or connecting to a hidden
13324 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13327 o Minor features (directory authorities, security, also in 0.2.6.9):
13328 - The HSDir flag given by authorities now requires the Stable flag.
13329 For the current network, this results in going from 2887 to 2806
13330 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13331 attack by raising the effort for a relay to become Stable to
13332 require at the very least 7 days, while maintaining the 96 hours
13333 uptime requirement for HSDir. Implements ticket 8243.
13335 o Minor features (client):
13336 - Relax the validation of hostnames in SOCKS5 requests, allowing the
13337 character '_' to appear, in order to cope with domains observed in
13338 the wild that are serving non-RFC compliant records. Resolves
13340 - Relax the validation done to hostnames in SOCKS5 requests, and
13341 allow a single trailing '.' to cope with clients that pass FQDNs
13342 using that syntax to explicitly indicate that the domain name is
13343 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
13344 - Add GroupWritable and WorldWritable options to unix-socket based
13345 SocksPort and ControlPort options. These options apply to a single
13346 socket, and override {Control,Socks}SocketsGroupWritable. Closes
13349 o Minor features (control protocol):
13350 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
13351 the control protocol. Resolves ticket 15358.
13353 o Minor features (directory authorities):
13354 - Directory authorities no longer vote against the "Fast", "Stable",
13355 and "HSDir" flags just because they were going to vote against
13356 "Running": if the consensus turns out to be that the router was
13357 running, then the authority's vote should count. Patch from Peter
13358 Retzlaff; closes issue 8712.
13360 o Minor features (geoip, also in 0.2.6.10):
13361 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13362 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13364 o Minor features (hidden services):
13365 - Add the new options "HiddenServiceMaxStreams" and
13366 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
13367 limit the maximum number of simultaneous streams per circuit, and
13368 optionally tear down the circuit when the limit is exceeded. Part
13371 o Minor features (portability):
13372 - Use C99 variadic macros when the compiler is not GCC. This avoids
13373 failing compilations on MSVC, and fixes a log-file-based race
13374 condition in our old workarounds. Original patch from Gisle Vanem.
13376 o Minor bugfixes (compilation, also in 0.2.6.9):
13377 - Build with --enable-systemd correctly when libsystemd is
13378 installed, but systemd is not. Fixes bug 16164; bugfix on
13379 0.2.6.3-alpha. Patch from Peter Palfrader.
13381 o Minor bugfixes (controller):
13382 - Add the descriptor ID in each HS_DESC control event. It was
13383 missing, but specified in control-spec.txt. Fixes bug 15881;
13384 bugfix on 0.2.5.2-alpha.
13386 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
13387 - Check for failures from crypto_early_init, and refuse to continue.
13388 A previous typo meant that we could keep going with an
13389 uninitialized crypto library, and would have OpenSSL initialize
13390 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13391 when implementing ticket 4900. Patch by "teor".
13393 o Minor bugfixes (hidden services):
13394 - Fix a crash when reloading configuration while at least one
13395 configured and one ephemeral hidden service exists. Fixes bug
13396 16060; bugfix on 0.2.7.1-alpha.
13397 - Avoid crashing with a double-free bug when we create an ephemeral
13398 hidden service but adding it fails for some reason. Fixes bug
13399 16228; bugfix on 0.2.7.1-alpha.
13401 o Minor bugfixes (Linux seccomp2 sandbox):
13402 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
13403 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
13405 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
13406 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13407 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13408 on 0.2.6.3-alpha. Patch from "teor".
13410 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
13411 - Fix sandboxing to work when running as a relay, by allowing the
13412 renaming of secret_id_key, and allowing the eventfd2 and futex
13413 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
13415 - Allow systemd connections to work with the Linux seccomp2 sandbox
13416 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13419 o Minor bugfixes (relay):
13420 - Fix a rarely-encountered memory leak when failing to initialize
13421 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
13422 from "cypherpunks".
13424 o Minor bugfixes (systemd):
13425 - Fix an accidental formatting error that broke the systemd
13426 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
13427 - Tor's systemd unit file no longer contains extraneous spaces.
13428 These spaces would sometimes confuse tools like deb-systemd-
13429 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
13431 o Minor bugfixes (tests):
13432 - Use the configured Python executable when running test-stem-full.
13433 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
13435 o Minor bugfixes (tests, also in 0.2.6.9):
13436 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13437 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13439 o Minor bugfixes (threads, comments):
13440 - Always initialize return value in compute_desc_id in rendcommon.c
13441 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13442 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
13443 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13444 - Remove undefined directive-in-macro in test_util_writepid clang
13445 3.7 complains that using a preprocessor directive inside a macro
13446 invocation in test_util_writepid in test_util.c is undefined.
13447 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13449 o Code simplification and refactoring:
13450 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
13451 to ensure they remain consistent and visible everywhere.
13452 - Remove some vestigial workarounds for the MSVC6 compiler. We
13453 haven't supported that in ages.
13454 - The link authentication code has been refactored for better
13455 testability and reliability. It now uses code generated with the
13456 "trunnel" binary encoding generator, to reduce the risk of bugs
13457 due to programmer error. Done as part of ticket 12498.
13460 - Include a specific and (hopefully) accurate documentation of the
13461 torrc file's meta-format in doc/torrc_format.txt. This is mainly
13462 of interest to people writing programs to parse or generate torrc
13463 files. This document is not a commitment to long-term
13464 compatibility; some aspects of the current format are a bit
13465 ridiculous. Closes ticket 2325.
13467 o Removed features:
13468 - Tor no longer supports copies of OpenSSL that are missing support
13469 for Elliptic Curve Cryptography. (We began using ECC when
13470 available in 0.2.4.8-alpha, for more safe and efficient key
13471 negotiation.) In particular, support for at least one of P256 or
13472 P224 is now required, with manual configuration needed if only
13473 P224 is available. Resolves ticket 16140.
13474 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
13475 on an operating system that has not upgraded to OpenSSL 1.0 or
13476 later, and you compile Tor from source, you will need to install a
13477 more recent OpenSSL to link Tor against.) These versions of
13478 OpenSSL are still supported by the OpenSSL, but the numerous
13479 cryptographic improvements in later OpenSSL releases makes them a
13480 clear choice. Resolves ticket 16034.
13481 - Remove the HidServDirectoryV2 option. Now all relays offer to
13482 store hidden service descriptors. Related to 16543.
13483 - Remove the VoteOnHidServDirectoriesV2 option, since all
13484 authorities have long set it to 1. Closes ticket 16543.
13487 - Document use of coverity, clang static analyzer, and clang dynamic
13488 undefined behavior and address sanitizers in doc/HACKING. Include
13489 detailed usage instructions in the blacklist. Patch by "teor".
13490 Closes ticket 15817.
13491 - The link authentication protocol code now has extensive tests.
13492 - The relay descriptor signature testing code now has
13494 - The test_workqueue program now runs faster, and is enabled by
13495 default as a part of "make check".
13496 - Now that OpenSSL has its own scrypt implementation, add an unit
13497 test that checks for interoperability between libscrypt_scrypt()
13498 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
13499 and rely on EVP_PBE_scrypt() whenever possible. Resolves
13503 Changes in version 0.2.6.10 - 2015-07-12
13504 Tor version 0.2.6.10 fixes some significant stability and hidden
13505 service client bugs, bulletproofs the cryptography init process, and
13506 fixes a bug when using the sandbox code with some older versions of
13507 Linux. Everyone running an older version, especially an older version
13508 of 0.2.6, should upgrade.
13510 o Major bugfixes (hidden service clients, stability):
13511 - Stop refusing to store updated hidden service descriptors on a
13512 client. This reverts commit 9407040c59218 (which indeed fixed bug
13513 14219, but introduced a major hidden service reachability
13514 regression detailed in bug 16381). This is a temporary fix since
13515 we can live with the minor issue in bug 14219 (it just results in
13516 some load on the network) but the regression of 16381 is too much
13517 of a setback. First-round fix for bug 16381; bugfix
13520 o Major bugfixes (stability):
13521 - Stop crashing with an assertion failure when parsing certain kinds
13522 of malformed or truncated microdescriptors. Fixes bug 16400;
13523 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13524 by "cypherpunks_backup".
13525 - Stop random client-side assertion failures that could occur when
13526 connecting to a busy hidden service, or connecting to a hidden
13527 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13530 o Minor features (geoip):
13531 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13532 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13534 o Minor bugfixes (crypto error-handling):
13535 - Check for failures from crypto_early_init, and refuse to continue.
13536 A previous typo meant that we could keep going with an
13537 uninitialized crypto library, and would have OpenSSL initialize
13538 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13539 when implementing ticket 4900. Patch by "teor".
13541 o Minor bugfixes (Linux seccomp2 sandbox):
13542 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13543 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13544 on 0.2.6.3-alpha. Patch from "teor".
13547 Changes in version 0.2.6.9 - 2015-06-11
13548 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
13549 requirements for receiving an HSDir flag, and addresses some other small
13550 bugs in the systemd and sandbox code. Clients using circuit isolation
13551 should upgrade; all directory authorities should upgrade.
13553 o Major bugfixes (client-side privacy):
13554 - Properly separate out each SOCKSPort when applying stream
13555 isolation. The error occurred because each port's session group was
13556 being overwritten by a default value when the listener connection
13557 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
13560 o Minor feature (directory authorities, security):
13561 - The HSDir flag given by authorities now requires the Stable flag.
13562 For the current network, this results in going from 2887 to 2806
13563 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13564 attack by raising the effort for a relay to become Stable which
13565 takes at the very least 7 days to do so and by keeping the 96
13566 hours uptime requirement for HSDir. Implements ticket 8243.
13568 o Minor bugfixes (compilation):
13569 - Build with --enable-systemd correctly when libsystemd is
13570 installed, but systemd is not. Fixes bug 16164; bugfix on
13571 0.2.6.3-alpha. Patch from Peter Palfrader.
13573 o Minor bugfixes (Linux seccomp2 sandbox):
13574 - Fix sandboxing to work when running as a relaymby renaming of
13575 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
13576 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
13577 - Allow systemd connections to work with the Linux seccomp2 sandbox
13578 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13581 o Minor bugfixes (tests):
13582 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13583 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13586 Changes in version 0.2.6.8 - 2015-05-21
13587 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
13588 fixes an authority-side bug in assigning the HSDir flag. All directory
13589 authorities should upgrade.
13591 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
13592 - Revert commit that made directory authorities assign the HSDir
13593 flag to relays without a DirPort; this was bad because such relays
13594 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13597 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13598 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13599 a client authorized hidden service. Fixes bug 15823; bugfix
13602 o Minor features (geoip):
13603 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13604 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13608 Changes in version 0.2.7.1-alpha - 2015-05-12
13609 Tor 0.2.7.1-alpha is the first alpha release in its series. It
13610 includes numerous small features and bugfixes against previous Tor
13611 versions, and numerous small infrastructure improvements. The most
13612 notable features are several new ways for controllers to interact with
13613 the hidden services subsystem.
13615 o New system requirements:
13616 - Tor no longer includes workarounds to support Libevent versions
13617 before 1.3e. Libevent 2.0 or later is recommended. Closes
13620 o Major features (controller):
13621 - Add the ADD_ONION and DEL_ONION commands that allow the creation
13622 and management of hidden services via the controller. Closes
13624 - New "GETINFO onions/current" and "GETINFO onions/detached"
13625 commands to get information about hidden services created via the
13626 controller. Part of ticket 6411.
13627 - New HSFETCH command to launch a request for a hidden service
13628 descriptor. Closes ticket 14847.
13629 - New HSPOST command to upload a hidden service descriptor. Closes
13630 ticket 3523. Patch by "DonnchaC".
13632 o Major bugfixes (hidden services):
13633 - Revert commit that made directory authorities assign the HSDir
13634 flag to relays without a DirPort; this was bad because such relays
13635 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13638 o Minor features (clock-jump tolerance):
13639 - Recover better when our clock jumps back many hours, like might
13640 happen for Tails or Whonix users who start with a very wrong
13641 hardware clock, use Tor to discover a more accurate time, and then
13642 fix their clock. Resolves part of ticket 8766.
13644 o Minor features (command-line interface):
13645 - Make --hash-password imply --hush to prevent unnecessary noise.
13646 Closes ticket 15542. Patch from "cypherpunks".
13647 - Print a warning whenever we find a relative file path being used
13648 as torrc option. Resolves issue 14018.
13650 o Minor features (controller):
13651 - Add DirAuthority lines for default directory authorities to the
13652 output of the "GETINFO config/defaults" command if not already
13653 present. Implements ticket 14840.
13654 - Controllers can now use "GETINFO hs/client/desc/id/..." to
13655 retrieve items from the client's hidden service descriptor cache.
13656 Closes ticket 14845.
13657 - Implement a new controller command "GETINFO status/fresh-relay-
13658 descs" to fetch a descriptor/extrainfo pair that was generated on
13659 demand just for the controller's use. Implements ticket 14784.
13661 o Minor features (DoS-resistance):
13662 - Make it harder for attackers to overload hidden services with
13663 introductions, by blocking multiple introduction requests on the
13664 same circuit. Resolves ticket 15515.
13666 o Minor features (geoip):
13667 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13668 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13671 o Minor features (HS popularity countermeasure):
13672 - To avoid leaking HS popularity, don't cycle the introduction point
13673 when we've handled a fixed number of INTRODUCE2 cells but instead
13674 cycle it when a random number of introductions is reached, thus
13675 making it more difficult for an attacker to find out the amount of
13676 clients that have used the introduction point for a specific HS.
13677 Closes ticket 15745.
13679 o Minor features (logging):
13680 - Include the Tor version in all LD_BUG log messages, since people
13681 tend to cut and paste those into the bugtracker. Implements
13684 o Minor features (pluggable transports):
13685 - When launching managed pluggable transports on Linux systems,
13686 attempt to have the kernel deliver a SIGTERM on tor exit if the
13687 pluggable transport process is still running. Resolves
13689 - When launching managed pluggable transports, setup a valid open
13690 stdin in the child process that can be used to detect if tor has
13691 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
13692 can be used by implementations to detect this new behavior.
13693 Resolves ticket 15435.
13695 o Minor features (testing):
13696 - Add a test to verify that the compiler does not eliminate our
13697 memwipe() implementation. Closes ticket 15377.
13698 - Add make rule `check-changes` to verify the format of changes
13699 files. Closes ticket 15180.
13700 - Add unit tests for control_event_is_interesting(). Add a compile-
13701 time check that the number of events doesn't exceed the capacity
13702 of control_event_t.event_mask. Closes ticket 15431, checks for
13703 bugs similar to 13085. Patch by "teor".
13704 - Command-line argument tests moved to Stem. Resolves ticket 14806.
13705 - Integrate the ntor, backtrace, and zero-length keys tests into the
13706 automake test suite. Closes ticket 15344.
13707 - Remove assertions during builds to determine Tor's test coverage.
13708 We don't want to trigger these even in assertions, so including
13709 them artificially makes our branch coverage look worse than it is.
13710 This patch provides the new test-stem-full and coverage-html-full
13711 configure options. Implements ticket 15400.
13713 o Minor bugfixes (build):
13714 - Improve out-of-tree builds by making non-standard rules work and
13715 clean up additional files and directories. Fixes bug 15053; bugfix
13718 o Minor bugfixes (command-line interface):
13719 - When "--quiet" is provided along with "--validate-config", do not
13720 write anything to stdout on success. Fixes bug 14994; bugfix
13722 - When complaining about bad arguments to "--dump-config", use
13723 stderr, not stdout.
13725 o Minor bugfixes (configuration, unit tests):
13726 - Only add the default fallback directories when the DirAuthorities,
13727 AlternateDirAuthority, and FallbackDir directory config options
13728 are set to their defaults. The default fallback directory list is
13729 currently empty, this fix will only change tor's behavior when it
13730 has default fallback directories. Includes unit tests for
13731 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
13732 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
13734 o Minor bugfixes (correctness):
13735 - For correctness, avoid modifying a constant string in
13736 handle_control_postdescriptor. Fixes bug 15546; bugfix
13738 - Remove side-effects from tor_assert() calls. This was harmless,
13739 because we never disable assertions, but it is bad style and
13740 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
13743 o Minor bugfixes (hidden service):
13744 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13745 a client authorized hidden service. Fixes bug 15823; bugfix
13747 - Remove an extraneous newline character from the end of hidden
13748 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
13750 o Minor bugfixes (interface):
13751 - Print usage information for --dump-config when it is used without
13752 an argument. Also, fix the error message to use different wording
13753 and add newline at the end. Fixes bug 15541; bugfix
13756 o Minor bugfixes (logs):
13757 - When building Tor under Clang, do not include an extra set of
13758 parentheses in log messages that include function names. Fixes bug
13759 15269; bugfix on every released version of Tor when compiled with
13760 recent enough Clang.
13762 o Minor bugfixes (network):
13763 - When attempting to use fallback technique for network interface
13764 lookup, disregard loopback and multicast addresses since they are
13765 unsuitable for public communications.
13767 o Minor bugfixes (statistics):
13768 - Disregard the ConnDirectionStatistics torrc options when Tor is
13769 not a relay since in that mode of operation no sensible data is
13770 being collected and because Tor might run into measurement hiccups
13771 when running as a client for some time, then becoming a relay.
13772 Fixes bug 15604; bugfix on 0.2.2.35.
13774 o Minor bugfixes (test networks):
13775 - When self-testing reachability, use ExtendAllowPrivateAddresses to
13776 determine if local/private addresses imply reachability. The
13777 previous fix used TestingTorNetwork, which implies
13778 ExtendAllowPrivateAddresses, but this excluded rare configurations
13779 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
13780 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
13781 issue discovered by CJ Ess.
13783 o Minor bugfixes (testing):
13784 - Check for matching value in server response in ntor_ref.py. Fixes
13785 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
13787 - Set the severity correctly when testing
13788 get_interface_addresses_ifaddrs() and
13789 get_interface_addresses_win32(), so that the tests fail gracefully
13790 instead of triggering an assertion. Fixes bug 15759; bugfix on
13791 0.2.6.3-alpha. Reported by Nicolas Derive.
13793 o Code simplification and refactoring:
13794 - Move the hacky fallback code out of get_interface_address6() into
13795 separate function and get it covered with unit-tests. Resolves
13797 - Refactor hidden service client-side cache lookup to intelligently
13798 report its various failure cases, and disentangle failure cases
13799 involving a lack of introduction points. Closes ticket 14391.
13800 - Use our own Base64 encoder instead of OpenSSL's, to allow more
13801 control over the output. Part of ticket 15652.
13804 - Improve the descriptions of statistics-related torrc options in
13805 the manpage to describe rationale and possible uses cases. Fixes
13807 - Improve the layout and formatting of ./configure --help messages.
13808 Closes ticket 15024. Patch from "cypherpunks".
13809 - Standardize on the term "server descriptor" in the manual page.
13810 Previously, we had used "router descriptor", "server descriptor",
13811 and "relay descriptor" interchangeably. Part of ticket 14987.
13814 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
13815 and always use the internal Base64 decoder. The internal decoder
13816 has been part of tor since 0.2.0.10-alpha, and no one should
13817 be using the OpenSSL one. Part of ticket 15652.
13818 - Remove the 'tor_strclear()' function; use memwipe() instead.
13819 Closes ticket 14922.
13821 o Removed features:
13822 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
13823 fingerprinting we now recommend pluggable transports; for forward-
13824 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
13825 - Remove the undocumented "--digests" command-line option. It
13826 complicated our build process, caused subtle build issues on
13827 multiple platforms, and is now redundant since we started
13828 including git version identifiers. Closes ticket 14742.
13829 - Tor no longer contains checks for ancient directory cache versions
13830 that didn't know about microdescriptors.
13831 - Tor no longer contains workarounds for stat files generated by
13832 super-old versions of Tor that didn't choose guards sensibly.
13835 Changes in version 0.2.4.27 - 2015-04-06
13836 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
13837 could be used by an attacker to crash hidden services, or crash clients
13838 visiting hidden services. Hidden services should upgrade as soon as
13839 possible; clients should upgrade whenever packages become available.
13841 This release also backports a simple improvement to make hidden
13842 services a bit less vulnerable to denial-of-service attacks.
13844 o Major bugfixes (security, hidden service):
13845 - Fix an issue that would allow a malicious client to trigger an
13846 assertion failure and halt a hidden service. Fixes bug 15600;
13847 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13848 - Fix a bug that could cause a client to crash with an assertion
13849 failure when parsing a malformed hidden service descriptor. Fixes
13850 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13852 o Minor features (DoS-resistance, hidden service):
13853 - Introduction points no longer allow multiple INTRODUCE1 cells to
13854 arrive on the same circuit. This should make it more expensive for
13855 attackers to overwhelm hidden services with introductions.
13856 Resolves ticket 15515.
13859 Changes in version 0.2.5.12 - 2015-04-06
13860 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
13861 could be used by an attacker to crash hidden services, or crash clients
13862 visiting hidden services. Hidden services should upgrade as soon as
13863 possible; clients should upgrade whenever packages become available.
13865 This release also backports a simple improvement to make hidden
13866 services a bit less vulnerable to denial-of-service attacks.
13868 o Major bugfixes (security, hidden service):
13869 - Fix an issue that would allow a malicious client to trigger an
13870 assertion failure and halt a hidden service. Fixes bug 15600;
13871 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13872 - Fix a bug that could cause a client to crash with an assertion
13873 failure when parsing a malformed hidden service descriptor. Fixes
13874 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13876 o Minor features (DoS-resistance, hidden service):
13877 - Introduction points no longer allow multiple INTRODUCE1 cells to
13878 arrive on the same circuit. This should make it more expensive for
13879 attackers to overwhelm hidden services with introductions.
13880 Resolves ticket 15515.
13883 Changes in version 0.2.6.7 - 2015-04-06
13884 Tor 0.2.6.7 fixes two security issues that could be used by an
13885 attacker to crash hidden services, or crash clients visiting hidden
13886 services. Hidden services should upgrade as soon as possible; clients
13887 should upgrade whenever packages become available.
13889 This release also contains two simple improvements to make hidden
13890 services a bit less vulnerable to denial-of-service attacks.
13892 o Major bugfixes (security, hidden service):
13893 - Fix an issue that would allow a malicious client to trigger an
13894 assertion failure and halt a hidden service. Fixes bug 15600;
13895 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13896 - Fix a bug that could cause a client to crash with an assertion
13897 failure when parsing a malformed hidden service descriptor. Fixes
13898 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13900 o Minor features (DoS-resistance, hidden service):
13901 - Introduction points no longer allow multiple INTRODUCE1 cells to
13902 arrive on the same circuit. This should make it more expensive for
13903 attackers to overwhelm hidden services with introductions.
13904 Resolves ticket 15515.
13905 - Decrease the amount of reattempts that a hidden service performs
13906 when its rendezvous circuits fail. This reduces the computational
13907 cost for running a hidden service under heavy load. Resolves
13911 Changes in version 0.2.6.6 - 2015-03-24
13912 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
13914 It adds numerous safety, security, correctness, and performance
13915 improvements. Client programs can be configured to use more kinds of
13916 sockets, AutomapHosts works better, the multithreading backend is
13917 improved, cell transmission is refactored, test coverage is much
13918 higher, more denial-of-service attacks are handled, guard selection is
13919 improved to handle long-term guards better, pluggable transports
13920 should work a bit better, and some annoying hidden service performance
13921 bugs should be addressed.
13923 o Minor bugfixes (portability):
13924 - Use the correct datatype in the SipHash-2-4 function to prevent
13925 compilers from assuming any sort of alignment. Fixes bug 15436;
13926 bugfix on 0.2.5.3-alpha.
13928 Changes in version 0.2.6.5-rc - 2015-03-18
13929 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
13930 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
13932 o Major bugfixes (client):
13933 - Avoid crashing when making certain configuration option changes on
13934 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
13937 o Major bugfixes (pluggable transports):
13938 - Initialize the extended OR Port authentication cookie before
13939 launching pluggable transports. This prevents a race condition
13940 that occurred when server-side pluggable transports would cache the
13941 authentication cookie before it has been (re)generated. Fixes bug
13942 15240; bugfix on 0.2.5.1-alpha.
13944 o Major bugfixes (portability):
13945 - Do not crash on startup when running on Solaris. Fixes a bug
13946 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
13949 o Minor features (heartbeat):
13950 - On relays, report how many connections we negotiated using each
13951 version of the Tor link protocols. This information will let us
13952 know if removing support for very old versions of the Tor
13953 protocols is harming the network. Closes ticket 15212.
13955 o Code simplification and refactoring:
13956 - Refactor main loop to extract the 'loop' part. This makes it
13957 easier to run Tor under Shadow. Closes ticket 15176.
13960 Changes in version 0.2.5.11 - 2015-03-17
13961 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
13963 It backports several bugfixes from the 0.2.6 branch, including a
13964 couple of medium-level security fixes for relays and exit nodes.
13965 It also updates the list of directory authorities.
13967 o Directory authority changes:
13968 - Remove turtles as a directory authority.
13969 - Add longclaw as a new (v3) directory authority. This implements
13970 ticket 13296. This keeps the directory authority count at 9.
13971 - The directory authority Faravahar has a new IP address. This
13972 closes ticket 14487.
13974 o Major bugfixes (crash, OSX, security):
13975 - Fix a remote denial-of-service opportunity caused by a bug in
13976 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13979 o Major bugfixes (relay, stability, possible security):
13980 - Fix a bug that could lead to a relay crashing with an assertion
13981 failure if a buffer of exactly the wrong layout was passed to
13982 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13983 0.2.0.10-alpha. Patch from 'cypherpunks'.
13984 - Do not assert if the 'data' pointer on a buffer is advanced to the
13985 very end of the buffer; log a BUG message instead. Only assert if
13986 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13988 o Major bugfixes (exit node stability):
13989 - Fix an assertion failure that could occur under high DNS load.
13990 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13991 diagnosed and fixed by "cypherpunks".
13993 o Major bugfixes (Linux seccomp2 sandbox):
13994 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13995 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13996 0.2.5.1-alpha. Patch from "sanic".
13998 o Minor features (controller):
13999 - New "GETINFO bw-event-cache" to get information about recent
14000 bandwidth events. Closes ticket 14128. Useful for controllers to
14001 get recent bandwidth history after the fix for ticket 13988.
14003 o Minor features (geoip):
14004 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14005 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14008 o Minor bugfixes (client, automapping):
14009 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14010 no value follows the option. Fixes bug 14142; bugfix on
14011 0.2.4.7-alpha. Patch by "teor".
14012 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14013 14195; bugfix on 0.1.0.1-rc.
14015 o Minor bugfixes (compilation):
14016 - Build without warnings with the stock OpenSSL srtp.h header, which
14017 has a duplicate declaration of SSL_get_selected_srtp_profile().
14018 Fixes bug 14220; this is OpenSSL's bug, not ours.
14020 o Minor bugfixes (directory authority):
14021 - Allow directory authorities to fetch more data from one another if
14022 they find themselves missing lots of votes. Previously, they had
14023 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14024 bugfix on 0.1.2.5-alpha.
14025 - Enlarge the buffer to read bwauth generated files to avoid an
14026 issue when parsing the file in dirserv_read_measured_bandwidths().
14027 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14029 o Minor bugfixes (statistics):
14030 - Increase period over which bandwidth observations are aggregated
14031 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
14033 o Minor bugfixes (preventative security, C safety):
14034 - When reading a hexadecimal, base-32, or base-64 encoded value from
14035 a string, always overwrite the whole output buffer. This prevents
14036 some bugs where we would look at (but fortunately, not reveal)
14037 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14041 Changes in version 0.2.4.26 - 2015-03-17
14042 Tor 0.2.4.26 includes an updated list of directory authorities. It
14043 also backports a couple of stability and security bugfixes from 0.2.5
14046 o Directory authority changes:
14047 - Remove turtles as a directory authority.
14048 - Add longclaw as a new (v3) directory authority. This implements
14049 ticket 13296. This keeps the directory authority count at 9.
14050 - The directory authority Faravahar has a new IP address. This
14051 closes ticket 14487.
14053 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
14054 - Fix an assertion failure that could occur under high DNS load.
14055 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14056 diagnosed and fixed by "cypherpunks".
14058 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
14059 - Fix a bug that could lead to a relay crashing with an assertion
14060 failure if a buffer of exactly the wrong layout was passed to
14061 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14062 0.2.0.10-alpha. Patch from 'cypherpunks'.
14063 - Do not assert if the 'data' pointer on a buffer is advanced to the
14064 very end of the buffer; log a BUG message instead. Only assert if
14065 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14067 o Minor features (geoip):
14068 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14069 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14072 Changes in version 0.2.6.4-rc - 2015-03-09
14073 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
14074 attacker might be able to use in order to crash certain Tor
14075 directories. It also resolves some minor issues left over from, or
14076 introduced in, Tor 0.2.6.3-alpha or earlier.
14078 o Major bugfixes (crash, OSX, security):
14079 - Fix a remote denial-of-service opportunity caused by a bug in
14080 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
14083 o Major bugfixes (relay, stability, possible security):
14084 - Fix a bug that could lead to a relay crashing with an assertion
14085 failure if a buffer of exactly the wrong layout is passed to
14086 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14087 0.2.0.10-alpha. Patch from "cypherpunks".
14088 - Do not assert if the 'data' pointer on a buffer is advanced to the
14089 very end of the buffer; log a BUG message instead. Only assert if
14090 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14092 o Major bugfixes (FreeBSD IPFW transparent proxy):
14093 - Fix address detection with FreeBSD transparent proxies, when
14094 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
14097 o Major bugfixes (Linux seccomp2 sandbox):
14098 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
14099 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
14101 - Allow AF_UNIX hidden services to be used with the seccomp2
14102 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
14103 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
14104 crash during attempts to call wait4. Fixes bug 15088; bugfix on
14105 0.2.5.1-alpha. Patch from "sanic".
14107 o Minor features (controller):
14108 - Messages about problems in the bootstrap process now include
14109 information about the server we were trying to connect to when we
14110 noticed the problem. Closes ticket 15006.
14112 o Minor features (geoip):
14113 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14114 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14117 o Minor features (logs):
14118 - Quiet some log messages in the heartbeat and at startup. Closes
14121 o Minor bugfixes (certificate handling):
14122 - If an authority operator accidentally makes a signing certificate
14123 with a future publication time, do not discard its real signing
14124 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
14125 - Remove any old authority certificates that have been superseded
14126 for at least two days. Previously, we would keep superseded
14127 certificates until they expired, if they were published close in
14128 time to the certificate that superseded them. Fixes bug 11454;
14129 bugfix on 0.2.1.8-alpha.
14131 o Minor bugfixes (compilation):
14132 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
14134 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
14137 o Minor bugfixes (testing):
14138 - Fix endianness issues in unit test for resolve_my_address() to
14139 have it pass on big endian systems. Fixes bug 14980; bugfix on
14141 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
14142 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
14143 - When running the new 'make test-stem' target, use the configured
14144 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
14145 from "cypherpunks".
14146 - When running the zero-length-keys tests, do not use the default
14147 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
14150 o Directory authority IP change:
14151 - The directory authority Faravahar has a new IP address. This
14152 closes ticket 14487.
14155 - Remove some lingering dead code that once supported mempools.
14156 Mempools were disabled by default in 0.2.5, and removed entirely
14157 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
14161 Changes in version 0.2.6.3-alpha - 2015-02-19
14162 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
14163 the 0.2.6.x series. It introduces support for more kinds of sockets,
14164 makes it harder to accidentally run an exit, improves our
14165 multithreading backend, incorporates several fixes for the
14166 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
14168 If no major regressions or security holes are found in this version,
14169 the next version will be a release candidate.
14171 o Deprecated versions:
14172 - Tor relays older than 0.2.4.18-rc are no longer allowed to
14173 advertise themselves on the network. Closes ticket 13555.
14175 o Major features (security, unix domain sockets):
14176 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
14177 applications can reach Tor without having to create AF_INET or
14178 AF_INET6 sockets, meaning they can completely disable their
14179 ability to make non-Tor network connections. To create a socket of
14180 this type, use "SocksPort unix:/path/to/socket". Implements
14182 - Support mapping hidden service virtual ports to AF_UNIX sockets.
14183 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
14184 Implements ticket 11485.
14186 o Major features (changed defaults):
14187 - Prevent relay operators from unintentionally running exits: When a
14188 relay is configured as an exit node, we now warn the user unless
14189 the "ExitRelay" option is set to 1. We warn even more loudly if
14190 the relay is configured with the default exit policy, since this
14191 can indicate accidental misconfiguration. Setting "ExitRelay 0"
14192 stops Tor from running as an exit relay. Closes ticket 10067.
14194 o Major features (directory system):
14195 - When downloading server- or microdescriptors from a directory
14196 server, we no longer launch multiple simultaneous requests to the
14197 same server. This reduces load on the directory servers,
14198 especially when directory guards are in use. Closes ticket 9969.
14199 - When downloading server- or microdescriptors over a tunneled
14200 connection, do not limit the length of our requests to what the
14201 Squid proxy is willing to handle. Part of ticket 9969.
14202 - Authorities can now vote on the correct digests and latest
14203 versions for different software packages. This allows packages
14204 that include Tor to use the Tor authority system as a way to get
14205 notified of updates and their correct digests. Implements proposal
14206 227. Closes ticket 10395.
14208 o Major features (guards):
14209 - Introduce the Guardfraction feature to improves load balancing on
14210 guard nodes. Specifically, it aims to reduce the traffic gap that
14211 guard nodes experience when they first get the Guard flag. This is
14212 a required step if we want to increase the guard lifetime to 9
14213 months or greater. Closes ticket 9321.
14215 o Major features (performance):
14216 - Make the CPU worker implementation more efficient by avoiding the
14217 kernel and lengthening pipelines. The original implementation used
14218 sockets to transfer data from the main thread to the workers, and
14219 didn't allow any thread to be assigned more than a single piece of
14220 work at once. The new implementation avoids communications
14221 overhead by making requests in shared memory, avoiding kernel IO
14222 where possible, and keeping more requests in flight at once.
14223 Implements ticket 9682.
14225 o Major features (relay):
14226 - Raise the minimum acceptable configured bandwidth rate for bridges
14227 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
14228 20 KiB/sec.) Closes ticket 13822.
14230 o Major bugfixes (exit node stability):
14231 - Fix an assertion failure that could occur under high DNS load.
14232 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14233 diagnosed and fixed by "cypherpunks".
14235 o Major bugfixes (mixed relay-client operation):
14236 - When running as a relay and client at the same time (not
14237 recommended), if we decide not to use a new guard because we want
14238 to retry older guards, only close the locally-originating circuits
14239 passing through that guard. Previously we would close all the
14240 circuits through that guard. Fixes bug 9819; bugfix on
14241 0.2.1.1-alpha. Reported by "skruffy".
14243 o Minor features (build):
14244 - New --disable-system-torrc compile-time option to prevent Tor from
14245 looking for the system-wide torrc or torrc-defaults files.
14246 Resolves ticket 13037.
14248 o Minor features (controller):
14249 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
14250 events so controllers can observe circuit isolation inputs. Closes
14252 - ControlPort now supports the unix:/path/to/socket syntax as an
14253 alternative to the ControlSocket option, for consistency with
14254 SocksPort and HiddenServicePort. Closes ticket 14451.
14255 - New "GETINFO bw-event-cache" to get information about recent
14256 bandwidth events. Closes ticket 14128. Useful for controllers to
14257 get recent bandwidth history after the fix for ticket 13988.
14259 o Minor features (Denial of service resistance):
14260 - Count the total number of bytes used storing hidden service
14261 descriptors against the value of MaxMemInQueues. If we're low on
14262 memory, and more than 20% of our memory is used holding hidden
14263 service descriptors, free them until no more than 10% of our
14264 memory holds hidden service descriptors. Free the least recently
14265 fetched descriptors first. Resolves ticket 13806.
14266 - When we have recently been under memory pressure (over 3/4 of
14267 MaxMemInQueues is allocated), then allocate smaller zlib objects
14268 for small requests. Closes ticket 11791.
14270 o Minor features (geoip):
14271 - Update geoip and geoip6 files to the January 7 2015 Maxmind
14272 GeoLite2 Country database.
14274 o Minor features (guard nodes):
14275 - Reduce the time delay before saving guard status to disk from 10
14276 minutes to 30 seconds (or from one hour to 10 minutes if
14277 AvoidDiskWrites is set). Closes ticket 12485.
14279 o Minor features (hidden service):
14280 - Make Sybil attacks against hidden services harder by changing the
14281 minimum time required to get the HSDir flag from 25 hours up to 96
14282 hours. Addresses ticket 14149.
14283 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
14284 services to disable the anti-scanning feature introduced in
14285 0.2.6.2-alpha. With this option not set, a connection to an
14286 unlisted port closes the circuit. With this option set, only a
14287 RELAY_DONE cell is sent. Closes ticket 14084.
14289 o Minor features (interface):
14290 - Implement "-f -" command-line option to read torrc configuration
14291 from standard input, if you don't want to store the torrc file in
14292 the file system. Implements feature 13865.
14294 o Minor features (logging):
14295 - Add a count of unique clients to the bridge heartbeat message.
14296 Resolves ticket 6852.
14297 - Suppress "router info incompatible with extra info" message when
14298 reading extrainfo documents from cache. (This message got loud
14299 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
14301 - Elevate hidden service authorized-client message from DEBUG to
14302 INFO. Closes ticket 14015.
14304 o Minor features (stability):
14305 - Add assertions in our hash-table iteration code to check for
14306 corrupted values that could cause infinite loops. Closes
14309 o Minor features (systemd):
14310 - Various improvements and modernizations in systemd hardening
14311 support. Closes ticket 13805. Patch from Craig Andrews.
14313 o Minor features (testing networks):
14314 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
14315 and the default on a testing network to 2 minutes. Drop the
14316 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
14317 keep the default on a testing network at 30 seconds. This reduces
14318 HS bootstrap time to around 25 seconds. Also, change the default
14319 time in test-network.sh to match. Closes ticket 13401. Patch
14321 - Create TestingDirAuthVoteHSDir to correspond to
14322 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
14323 HSDir flag for the listed relays regardless of uptime or ORPort
14324 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
14325 Partial implementation for ticket 14067. Patch by "teor".
14327 o Minor features (tor2web mode):
14328 - Introduce the config option Tor2webRendezvousPoints, which allows
14329 clients in Tor2webMode to select a specific Rendezvous Point to be
14330 used in HS circuits. This might allow better performance for
14331 Tor2Web nodes. Implements ticket 12844.
14333 o Minor bugfixes (client DNS):
14334 - Report the correct cached DNS expiration times on SOCKS port or in
14335 DNS replies. Previously, we would report everything as "never
14336 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
14337 - Avoid a small memory leak when we find a cached answer for a
14338 reverse DNS lookup in a client-side DNS cache. (Remember, client-
14339 side DNS caching is off by default, and is not recommended.) Fixes
14340 bug 14259; bugfix on 0.2.0.1-alpha.
14342 o Minor bugfixes (client, automapping):
14343 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14344 no value follows the option. Fixes bug 14142; bugfix on
14345 0.2.4.7-alpha. Patch by "teor".
14346 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14347 14195; bugfix on 0.1.0.1-rc.
14348 - Prevent changes to other options from removing the wildcard value
14349 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
14351 - Allow MapAddress and AutomapHostsOnResolve to work together when
14352 an address is mapped into another address type (like .onion) that
14353 must be automapped at resolve time. Fixes bug 7555; bugfix
14356 o Minor bugfixes (client, bridges):
14357 - When we are using bridges and we had a network connectivity
14358 problem, only retry connecting to our currently configured
14359 bridges, not all bridges we know about and remember using. Fixes
14360 bug 14216; bugfix on 0.2.2.17-alpha.
14362 o Minor bugfixes (client, IPv6):
14363 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
14364 flag is not set; and not because the NoIPv4Traffic flag was set.
14365 Previously we'd looked at the NoIPv4Traffic flag for both types of
14366 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
14368 o Minor bugfixes (compilation):
14369 - The address of an array in the middle of a structure will always
14370 be non-NULL. clang recognises this and complains. Disable the
14371 tautologous and redundant check to silence this warning. Fixes bug
14372 14001; bugfix on 0.2.1.2-alpha.
14373 - Avoid warnings when building with systemd 209 or later. Fixes bug
14374 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
14375 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
14376 Addresses ticket 14188.
14377 - Build without warnings with the stock OpenSSL srtp.h header, which
14378 has a duplicate declaration of SSL_get_selected_srtp_profile().
14379 Fixes bug 14220; this is OpenSSL's bug, not ours.
14380 - Do not compile any code related to Tor2Web mode when Tor2Web mode
14381 is not enabled at compile time. Previously, this code was included
14382 in a disabled state. See discussion on ticket 12844.
14383 - Remove the --disable-threads configure option again. It was
14384 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
14385 14819; bugfix on 0.2.6.2-alpha.
14387 o Minor bugfixes (controller):
14388 - Report "down" in response to the "GETINFO entry-guards" command
14389 when relays are down with an unreachable_since value. Previously,
14390 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
14391 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
14392 14116; bugfix on 0.2.2.9-alpha.
14393 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
14394 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
14396 o Minor bugfixes (directory authority):
14397 - Allow directory authorities to fetch more data from one another if
14398 they find themselves missing lots of votes. Previously, they had
14399 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14400 bugfix on 0.1.2.5-alpha.
14401 - Do not attempt to download extrainfo documents which we will be
14402 unable to validate with a matching server descriptor. Fixes bug
14403 13762; bugfix on 0.2.0.1-alpha.
14404 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
14405 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
14406 - Enlarge the buffer to read bwauth generated files to avoid an
14407 issue when parsing the file in dirserv_read_measured_bandwidths().
14408 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14410 o Minor bugfixes (file handling):
14411 - Stop failing when key files are zero-length. Instead, generate new
14412 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
14413 on all versions of Tor. Patch by "teor".
14414 - Stop generating a fresh .old RSA onion key file when the .old file
14415 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
14416 - Avoid overwriting .old key files with empty key files.
14417 - Skip loading zero-length extrainfo store, router store, stats,
14418 state, and key files.
14419 - Avoid crashing when trying to reload a torrc specified as a
14420 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
14423 o Minor bugfixes (hidden services):
14424 - Close the introduction circuit when we have no more usable intro
14425 points, instead of waiting for it to time out. This also ensures
14426 that no follow-up HS descriptor fetch is triggered when the
14427 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
14428 - When fetching a hidden service descriptor for a down service that
14429 was recently up, do not keep refetching until we try the same
14430 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
14431 - Successfully launch Tor with a nonexistent hidden service
14432 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
14433 14106; bugfix on 0.2.6.2-alpha.
14435 o Minor bugfixes (logging):
14436 - Avoid crashing when there are more log domains than entries in
14437 domain_list. Bugfix on 0.2.3.1-alpha.
14438 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
14440 - Don't log messages to stdout twice when starting up. Fixes bug
14441 13993; bugfix on 0.2.6.1-alpha.
14443 o Minor bugfixes (parsing):
14444 - Stop accepting milliseconds (or other junk) at the end of
14445 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
14446 - Support two-number and three-number version numbers correctly, in
14447 case we change the Tor versioning system in the future. Fixes bug
14448 13661; bugfix on 0.0.8pre1.
14450 o Minor bugfixes (path counting):
14451 - When deciding whether the consensus lists any exit nodes, count
14452 the number listed in the consensus, not the number we have
14453 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
14454 - When deciding whether we have any exit nodes, only examine
14455 ExitNodes when the ExitNodes option is actually set. Fixes part of
14456 bug 14918; bugfix on 0.2.6.2-alpha.
14457 - Get rid of redundant and possibly scary warnings that we are
14458 missing directory information while we bootstrap. Fixes part of
14459 bug 14918; bugfix on 0.2.6.2-alpha.
14461 o Minor bugfixes (portability):
14462 - Fix the ioctl()-based network interface lookup code so that it
14463 will work on systems that have variable-length struct ifreq, for
14465 - Fix scheduler compilation on targets where char is unsigned. Fixes
14466 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
14468 o Minor bugfixes (sandbox):
14469 - Allow glibc fatal errors to be sent to stderr before Tor exits.
14470 Previously, glibc would try to write them to /dev/tty, and the
14471 sandbox would trap the call and make Tor exit prematurely. Fixes
14472 bug 14759; bugfix on 0.2.5.1-alpha.
14474 o Minor bugfixes (shutdown):
14475 - When shutting down, always call event_del() on lingering read or
14476 write events before freeing them. Otherwise, we risk double-frees
14477 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
14480 o Minor bugfixes (small memory leaks):
14481 - Avoid leaking memory when using IPv6 virtual address mappings.
14482 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
14485 o Minor bugfixes (statistics):
14486 - Increase period over which bandwidth observations are aggregated
14487 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
14489 o Minor bugfixes (systemd support):
14490 - Fix detection and operation of systemd watchdog. Fixes part of bug
14491 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
14492 - Run correctly under systemd with the RunAsDaemon option set. Fixes
14493 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
14494 - Inform the systemd supervisor about more changes in the Tor
14495 process status. Implements part of ticket 14141. Patch from
14497 - Cause the "--disable-systemd" option to actually disable systemd
14498 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
14501 o Minor bugfixes (TLS):
14502 - Check more thoroughly throughout the TLS code for possible
14503 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
14505 o Minor bugfixes (transparent proxy):
14506 - Use getsockname, not getsockopt, to retrieve the address for a
14507 TPROXY-redirected connection. Fixes bug 13796; bugfix
14510 o Code simplification and refactoring:
14511 - Move fields related to isolating and configuring client ports into
14512 a shared structure. Previously, they were duplicated across
14513 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
14514 to copy them correctly had been the cause of at least one bug in
14515 the past. Closes ticket 8546.
14516 - Refactor the get_interface_addresses_raw() doom-function into
14517 multiple smaller and simpler subfunctions. Cover the resulting
14518 subfunctions with unit-tests. Fixes a significant portion of
14520 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
14521 only for version <= 0.2.2.24 which is now deprecated. Closes
14523 - Remove a test for a long-defunct broken version-one
14527 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
14528 for writing the OpenBSD-specific tips. Resolves ticket 13702.
14529 - Make the tor-resolve documentation match its help string and its
14530 options. Resolves part of ticket 14325.
14531 - Log a more useful error message from tor-resolve when failing to
14532 look up a hidden service address. Resolves part of ticket 14325.
14534 o Downgraded warnings:
14535 - Don't warn when we've attempted to contact a relay using the wrong
14536 ntor onion key. Closes ticket 9635.
14538 o Removed features:
14539 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
14540 longer silently accepted as an alias for "ExitNodes".
14541 - The --enable-mempool and --enable-buf-freelists options, which
14542 were originally created to work around bad malloc implementations,
14543 no longer exist. They were off-by-default in 0.2.5. Closes
14547 - Make the checkdir/perms test complete successfully even if the
14548 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
14549 - Test that tor does not fail when key files are zero-length. Check
14550 that tor generates new keys, and overwrites the empty key files.
14551 - Test that tor generates new keys when keys are missing
14552 (existing behavior).
14553 - Test that tor does not overwrite key files that already contain
14554 data (existing behavior). Tests bug 13111. Patch by "teor".
14555 - New "make test-stem" target to run stem integration tests.
14556 Requires that the "STEM_SOURCE_DIR" environment variable be set.
14557 Closes ticket 14107.
14558 - Make the test_cmdline_args.py script work correctly on Windows.
14559 Patch from Gisle Vanem.
14560 - Move the slower unit tests into a new "./src/test/test-slow"
14561 binary that can be run independently of the other tests. Closes
14563 - Avoid undefined behavior when sampling huge values from the
14564 Laplace distribution. This made unittests fail on Raspberry Pi.
14565 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
14568 Changes in version 0.2.6.2-alpha - 2014-12-31
14569 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
14570 It introduces a major new backend for deciding when to send cells on
14571 channels, which should lead down the road to big performance
14572 increases. It contains security and statistics features for better
14573 work on hidden services, and numerous bugfixes.
14575 This release contains many new unit tests, along with major
14576 performance improvements for running testing networks using Chutney.
14577 Thanks to a series of patches contributed by "teor", testing networks
14578 should now bootstrap in seconds, rather than minutes.
14580 o Major features (relay, infrastructure):
14581 - Complete revision of the code that relays use to decide which cell
14582 to send next. Formerly, we selected the best circuit to write on
14583 each channel, but we didn't select among channels in any
14584 sophisticated way. Now, we choose the best circuits globally from
14585 among those whose channels are ready to deliver traffic.
14587 This patch implements a new inter-cmux comparison API, a global
14588 high/low watermark mechanism and a global scheduler loop for
14589 transmission prioritization across all channels as well as among
14590 circuits on one channel. This schedule is currently tuned to
14591 (tolerantly) avoid making changes in network performance, but it
14592 should form the basis for major circuit performance increases in
14593 the future. Code by Andrea; tuning by Rob Jansen; implements
14596 o Major features (hidden services):
14597 - Make HS port scanning more difficult by immediately closing the
14598 circuit when a user attempts to connect to a nonexistent port.
14599 Closes ticket 13667.
14600 - Add a HiddenServiceStatistics option that allows Tor relays to
14601 gather and publish statistics about the overall size and volume of
14602 hidden service usage. Specifically, when this option is turned on,
14603 an HSDir will publish an approximate number of hidden services
14604 that have published descriptors to it the past 24 hours. Also, if
14605 a relay has acted as a hidden service rendezvous point, it will
14606 publish the approximate amount of rendezvous cells it has relayed
14607 the past 24 hours. The statistics themselves are obfuscated so
14608 that the exact values cannot be derived. For more details see
14609 proposal 238, "Better hidden service stats from Tor relays". This
14610 feature is currently disabled by default. Implements feature 13192.
14612 o Major bugfixes (client, automap):
14613 - Repair automapping with IPv6 addresses. This automapping should
14614 have worked previously, but one piece of debugging code that we
14615 inserted to detect a regression actually caused the regression to
14616 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
14617 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
14620 o Major bugfixes (hidden services):
14621 - When closing an introduction circuit that was opened in parallel
14622 with others, don't mark the introduction point as unreachable.
14623 Previously, the first successful connection to an introduction
14624 point would make the other introduction points get marked as
14625 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
14627 o Directory authority changes:
14628 - Remove turtles as a directory authority.
14629 - Add longclaw as a new (v3) directory authority. This implements
14630 ticket 13296. This keeps the directory authority count at 9.
14632 o Major removed features:
14633 - Tor clients no longer support connecting to hidden services
14634 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
14635 option has been removed. (There shouldn't be any hidden services
14636 running these versions on the network.) Closes ticket 7803.
14638 o Minor features (client):
14639 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
14640 is enabled, reject requests with IP addresses as hostnames.
14641 Resolves ticket 13315.
14643 o Minor features (controller):
14644 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
14645 write an unscheduled heartbeat message to the log. Implements
14648 o Minor features (geoip):
14649 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
14652 o Minor features (hidden services):
14653 - When re-enabling the network, don't try to build introduction
14654 circuits until we have successfully built a circuit. This makes
14655 hidden services come up faster when the network is re-enabled.
14656 Patch from "akwizgran". Closes ticket 13447.
14657 - When we fail to retrieve a hidden service descriptor, send the
14658 controller an "HS_DESC FAILED" controller event. Implements
14660 - New HiddenServiceDirGroupReadable option to cause hidden service
14661 directories and hostname files to be created group-readable. Patch
14662 from "anon", David Stainton, and "meejah". Closes ticket 11291.
14664 o Minor features (systemd):
14665 - Where supported, when running with systemd, report successful
14666 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
14667 - When running with systemd, support systemd watchdog messages. Part
14668 of ticket 11016. Patch by Michael Scherer.
14670 o Minor features (transparent proxy):
14671 - Update the transparent proxy option checks to allow for both ipfw
14672 and pf on OS X. Closes ticket 14002.
14673 - Use the correct option when using IPv6 with transparent proxy
14674 support on Linux. Resolves 13808. Patch by Francisco Blas
14677 o Minor bugfixes (preventative security, C safety):
14678 - When reading a hexadecimal, base-32, or base-64 encoded value from
14679 a string, always overwrite the whole output buffer. This prevents
14680 some bugs where we would look at (but fortunately, not reveal)
14681 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14683 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
14684 just the part that's used. This makes it harder for data leak bugs
14685 to occur in the event of other programming failures. Resolves
14688 o Minor bugfixes (client, microdescriptors):
14689 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
14690 computing which microdescriptors to download. This keeps us from
14691 erroneous download behavior if two microdescriptor digests ever
14692 have the same first 160 bits. Fixes part of bug 13399; bugfix
14694 - Reset a router's status if its microdescriptor digest changes,
14695 even if the first 160 bits remain the same. Fixes part of bug
14696 13399; bugfix on 0.2.3.1-alpha.
14698 o Minor bugfixes (compilation):
14699 - Silence clang warnings under --enable-expensive-hardening,
14700 including implicit truncation of 64 bit values to 32 bit, const
14701 char assignment to self, tautological compare, and additional
14702 parentheses around equality tests. Fixes bug 13577; bugfix
14704 - Fix a clang warning about checking whether an address in the
14705 middle of a structure is NULL. Fixes bug 14001; bugfix
14708 o Minor bugfixes (hidden services):
14709 - Correctly send a controller event when we find that a rendezvous
14710 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
14711 - Pre-check directory permissions for new hidden-services to avoid
14712 at least one case of "Bug: Acting on config options left us in a
14713 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
14714 - When adding a new hidden service (for example, via SETCONF), Tor
14715 no longer congratulates the user for running a relay. Fixes bug
14716 13941; bugfix on 0.2.6.1-alpha.
14717 - When fetching hidden service descriptors, we now check not only
14718 for whether we got the hidden service we had in mind, but also
14719 whether we got the particular descriptors we wanted. This prevents
14720 a class of inefficient but annoying DoS attacks by hidden service
14721 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
14724 o Minor bugfixes (Linux seccomp2 sandbox):
14725 - Make transparent proxy support work along with the seccomp2
14726 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
14727 by Francisco Blas Izquierdo Riera.
14728 - Fix a memory leak in tor-resolve when running with the sandbox
14729 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
14731 o Minor bugfixes (logging):
14732 - Downgrade warnings about RSA signature failures to info log level.
14733 Emit a warning when an extra info document is found incompatible
14734 with a corresponding router descriptor. Fixes bug 9812; bugfix
14736 - Make connection_ap_handshake_attach_circuit() log the circuit ID
14737 correctly. Fixes bug 13701; bugfix on 0.0.6.
14739 o Minor bugfixes (misc):
14740 - Stop allowing invalid address patterns like "*/24" that contain
14741 both a wildcard address and a bit prefix length. This affects all
14742 our address-range parsing code. Fixes bug 7484; bugfix
14745 o Minor bugfixes (testing networks, fast startup):
14746 - Allow Tor to build circuits using a consensus with no exits. If
14747 the consensus has no exits (typical of a bootstrapping test
14748 network), allow Tor to build circuits once enough descriptors have
14749 been downloaded. This assists in bootstrapping a testing Tor
14750 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
14752 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
14753 header to directory servers. This allows us to obtain consensuses
14754 promptly when the consensus interval is very short. This assists
14755 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
14756 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
14757 - Stop assuming that private addresses are local when checking
14758 reachability in a TestingTorNetwork. Instead, when testing, assume
14759 all OR connections are remote. (This is necessary due to many test
14760 scenarios running all relays on localhost.) This assists in
14761 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
14762 0.1.0.1-rc. Patch by "teor".
14763 - Avoid building exit circuits from a consensus with no exits. Now
14764 thanks to our fix for 13718, we accept a no-exit network as not
14765 wholly lost, but we need to remember not to try to build exit
14766 circuits on it. Closes ticket 13814; patch by "teor".
14767 - Stop requiring exits to have non-zero bandwithcapacity in a
14768 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
14769 ignore exit bandwidthcapacity. This assists in bootstrapping a
14770 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
14771 on 0.2.0.3-alpha. Patch by "teor".
14772 - Add "internal" to some bootstrap statuses when no exits are
14773 available. If the consensus does not contain Exits, Tor will only
14774 build internal circuits. In this case, relevant statuses will
14775 contain the word "internal" as indicated in the Tor control-
14776 spec.txt. When bootstrap completes, Tor will be ready to build
14777 internal circuits. If a future consensus contains Exits, exit
14778 circuits may become available. Fixes part of bug 13718; bugfix on
14779 0.2.4.10-alpha. Patch by "teor".
14780 - Decrease minimum consensus interval to 10 seconds when
14781 TestingTorNetwork is set, or 5 seconds for the first consensus.
14782 Fix assumptions throughout the code that assume larger intervals.
14783 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
14785 - Avoid excluding guards from path building in minimal test
14786 networks, when we're in a test network and excluding guards would
14787 exclude all relays. This typically occurs in incredibly small tor
14788 networks, and those using "TestingAuthVoteGuard *". Fixes part of
14789 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
14791 o Code simplification and refactoring:
14792 - Stop using can_complete_circuits as a global variable; access it
14793 with a function instead.
14794 - Avoid using operators directly as macro arguments: this lets us
14795 apply coccinelle transformations to our codebase more directly.
14796 Closes ticket 13172.
14797 - Combine the functions used to parse ClientTransportPlugin and
14798 ServerTransportPlugin into a single function. Closes ticket 6456.
14799 - Add inline functions and convenience macros for inspecting channel
14800 state. Refactor the code to use convenience macros instead of
14801 checking channel state directly. Fixes issue 7356.
14802 - Document all members of was_router_added_t and rename
14803 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
14804 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
14805 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
14806 constant instead of hardcoded value. Fixes issue 13840.
14807 - Refactor our generic strmap and digestmap types into a single
14808 implementation, so that we can add a new digest256map
14812 - Document the bridge-authority-only 'networkstatus-bridges' file.
14813 Closes ticket 13713; patch from "tom".
14814 - Fix typo in PredictedPortsRelevanceTime option description in
14815 manpage. Resolves issue 13707.
14816 - Stop suggesting that users specify relays by nickname: it isn't a
14817 good idea. Also, properly cross-reference how to specify relays in
14818 all parts of manual documenting options that take a list of
14819 relays. Closes ticket 13381.
14820 - Clarify the HiddenServiceDir option description in manpage to make
14821 it clear that relative paths are taken with respect to the current
14822 working directory. Also clarify that this behavior is not
14823 guaranteed to remain indefinitely. Fixes issue 13913.
14826 - New tests for many parts of channel, relay, and circuitmux
14827 functionality. Code by Andrea; part of 9262.
14828 - New tests for parse_transport_line(). Part of ticket 6456.
14829 - In the unit tests, use chgrp() to change the group of the unit
14830 test temporary directory to the current user, so that the sticky
14831 bit doesn't interfere with tests that check directory groups.
14833 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
14837 Changes in version 0.2.6.1-alpha - 2014-10-30
14838 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
14839 includes numerous code cleanups and new tests, and fixes a large
14840 number of annoying bugs. Out-of-memory conditions are handled better
14841 than in 0.2.5, pluggable transports have improved proxy support, and
14842 clients now use optimistic data for contacting hidden services. Also,
14843 we are now more robust to changes in what we consider a parseable
14844 directory object, so that tightening restrictions does not have a risk
14845 of introducing infinite download loops.
14847 This is the first alpha release in a new series, so expect there to be
14848 bugs. Users who would rather test out a more stable branch should stay
14849 with 0.2.5.x for now.
14851 o New compiler and system requirements:
14852 - Tor 0.2.6.x requires that your compiler support more of the C99
14853 language standard than before. The 'configure' script now detects
14854 whether your compiler supports C99 mid-block declarations and
14855 designated initializers. If it does not, Tor will not compile.
14857 We may revisit this requirement if it turns out that a significant
14858 number of people need to build Tor with compilers that don't
14859 bother implementing a 15-year-old standard. Closes ticket 13233.
14860 - Tor no longer supports systems without threading support. When we
14861 began working on Tor, there were several systems that didn't have
14862 threads, or where the thread support wasn't able to run the
14863 threads of a single process on multiple CPUs. That no longer
14864 holds: every system where Tor needs to run well now has threading
14865 support. Resolves ticket 12439.
14867 o Removed platform support:
14868 - We no longer include special code to build on Windows CE; as far
14869 as we know, nobody has used Tor on Windows CE in a very long time.
14870 Closes ticket 11446.
14872 o Major features (bridges):
14873 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
14874 transports if they are configured via the "TOR_PT_PROXY"
14875 environment variable. Implements proposal 232. Resolves
14878 o Major features (client performance, hidden services):
14879 - Allow clients to use optimistic data when connecting to a hidden
14880 service, which should remove a round-trip from hidden service
14881 initialization. See proposal 181 for details. Implements
14884 o Major features (directory system):
14885 - Upon receiving an unparseable directory object, if its digest
14886 matches what we expected, then don't try to download it again.
14887 Previously, when we got a descriptor we didn't like, we would keep
14888 trying to download it over and over. Closes ticket 11243.
14890 o Major features (sample torrc):
14891 - Add a new, infrequently-changed "torrc.minimal". This file is
14892 similar to torrc.sample, but it will change as infrequently as
14893 possible, for the benefit of users whose systems prompt them for
14894 intervention whenever a default configuration file is changed.
14895 Making this change allows us to update torrc.sample to be a more
14896 generally useful "sample torrc".
14898 o Major bugfixes (directory authorities):
14899 - Do not assign the HSDir flag to relays if they are not Valid, or
14900 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
14902 o Major bugfixes (directory bandwidth performance):
14903 - Don't flush the zlib buffer aggressively when compressing
14904 directory information for clients. This should save about 7% of
14905 the bandwidth currently used for compressed descriptors and
14906 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
14908 o Minor features (security, memory wiping):
14909 - Ensure we securely wipe keys from memory after
14910 crypto_digest_get_digest and init_curve25519_keypair_from_file
14911 have finished using them. Resolves ticket 13477.
14913 o Minor features (security, out-of-memory handling):
14914 - When handling an out-of-memory condition, allocate less memory for
14915 temporary data structures. Fixes issue 10115.
14916 - When handling an out-of-memory condition, consider more types of
14917 buffers, including those on directory connections, and zlib
14918 buffers. Resolves ticket 11792.
14921 - When identity keypair is generated for first time, log a
14922 congratulatory message that links to the new relay lifecycle
14923 document. Implements feature 10427.
14925 o Minor features (client):
14926 - Clients are now willing to send optimistic data (before they
14927 receive a 'connected' cell) to relays of any version. (Relays
14928 without support for optimistic data are no longer supported on the
14929 Tor network.) Resolves ticket 13153.
14931 o Minor features (directory authorities):
14932 - Don't list relays with a bandwidth estimate of 0 in the consensus.
14933 Implements a feature proposed during discussion of bug 13000.
14934 - In tor-gencert, report an error if the user provides the same
14935 argument more than once.
14936 - If a directory authority can't find a best consensus method in the
14937 votes that it holds, it now falls back to its favorite consensus
14938 method. Previously, it fell back to method 1. Neither of these is
14939 likely to get enough signatures, but "fall back to favorite"
14940 doesn't require us to maintain support an obsolete consensus
14941 method. Implements part of proposal 215.
14943 o Minor features (logging):
14944 - On Unix-like systems, you can now use named pipes as the target of
14945 the Log option, and other options that try to append to files.
14946 Closes ticket 12061. Patch from "carlo von lynX".
14947 - When opening a log file at startup, send it every log message that
14948 we generated between startup and opening it. Previously, log
14949 messages that were generated before opening the log file were only
14950 logged to stdout. Closes ticket 6938.
14951 - Add a TruncateLogFile option to overwrite logs instead of
14952 appending to them. Closes ticket 5583.
14954 o Minor features (portability, Solaris):
14955 - Threads are no longer disabled by default on Solaris; we believe
14956 that the versions of Solaris with broken threading support are all
14957 obsolete by now. Resolves ticket 9495.
14959 o Minor features (relay):
14960 - Re-check our address after we detect a changed IP address from
14961 getsockname(). This ensures that the controller command "GETINFO
14962 address" will report the correct value. Resolves ticket 11582.
14964 - A new AccountingRule option lets Relays set whether they'd like
14965 AccountingMax to be applied separately to inbound and outbound
14966 traffic, or applied to the sum of inbound and outbound traffic.
14967 Resolves ticket 961. Patch by "chobe".
14969 o Minor features (testing networks):
14970 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
14971 the "Exit" flag regardless of their uptime, bandwidth, or exit
14972 policy. TestingTorNetwork must be set for this option to have any
14973 effect. Previously, authorities would take up to 35 minutes to
14974 give nodes the Exit flag in a test network. Partially implements
14977 o Minor features (validation):
14978 - Check all date/time values passed to tor_timegm and
14979 parse_rfc1123_time for validity, taking leap years into account.
14980 Improves HTTP header validation. Implemented with bug 13476.
14981 - In correct_tm(), limit the range of values returned by system
14982 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
14983 This means we don't have to deal with negative or too large dates,
14984 even if a clock is wrong. Otherwise we might fail to read a file
14985 written by us which includes such a date. Fixes bug 13476.
14987 o Minor bugfixes (bridge clients):
14988 - When configured to use a bridge without an identity digest (not
14989 recommended), avoid launching an extra channel to it when
14990 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
14992 o Minor bugfixes (bridges):
14993 - When DisableNetwork is set, do not launch pluggable transport
14994 plugins, and if any are running, terminate them. Fixes bug 13213;
14995 bugfix on 0.2.3.6-alpha.
14997 o Minor bugfixes (C correctness):
14998 - Fix several instances of possible integer overflow/underflow/NaN.
14999 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
15001 - In circuit_build_times_calculate_timeout() in circuitstats.c,
15002 avoid dividing by zero in the pareto calculations. This traps
15003 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
15005 - Fix an integer overflow in format_time_interval(). Fixes bug
15006 13393; bugfix on 0.2.0.10-alpha.
15007 - Set the correct day of year value when the system's localtime(_r)
15008 or gmtime(_r) functions fail to set struct tm. Not externally
15009 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
15010 - Avoid unlikely signed integer overflow in tor_timegm on systems
15011 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
15013 o Minor bugfixes (client):
15014 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
15015 BadExit flag are not considered worthy candidates. Fixes bug
15016 13066; bugfix on 0.1.2.3-alpha.
15017 - Use the consensus schedule for downloading consensuses, and not
15018 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
15019 - Handle unsupported or malformed SOCKS5 requests properly by
15020 responding with the appropriate error message before closing the
15021 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
15023 o Minor bugfixes (client, torrc):
15024 - Stop modifying the value of our DirReqStatistics torrc option just
15025 because we're not a bridge or relay. This bug was causing Tor
15026 Browser users to write "DirReqStatistics 0" in their torrc files
15027 as if they had chosen to change the config. Fixes bug 4244; bugfix
15029 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
15030 that our options have changed every time we SIGHUP. Fixes bug
15031 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
15033 o Minor bugfixes (controller):
15034 - Return an error when the second or later arguments of the
15035 "setevents" controller command are invalid events. Previously we
15036 would return success while silently skipping invalid events. Fixes
15037 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
15039 o Minor bugfixes (directory system):
15040 - Always believe that v3 directory authorities serve extra-info
15041 documents, whether they advertise "caches-extra-info" or not.
15042 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
15043 - When running as a v3 directory authority, advertise that you serve
15044 extra-info documents so that clients who want them can find them
15045 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
15046 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
15047 Previously, directories offering BRIDGE_DIRINFO and some other
15048 flag (i.e. microdescriptors or extrainfo) would be ignored when
15049 looking for bridges. Partially fixes bug 13163; bugfix
15052 o Minor bugfixes (networking):
15053 - Check for orconns and use connection_or_close_for_error() rather
15054 than connection_mark_for_close() directly in the getsockopt()
15055 failure case of connection_handle_write_impl(). Fixes bug 11302;
15056 bugfix on 0.2.4.4-alpha.
15058 o Minor bugfixes (relay):
15059 - When generating our family list, remove spaces from around the
15060 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
15061 - If our previous bandwidth estimate was 0 bytes, allow publishing a
15062 new relay descriptor immediately. Fixes bug 13000; bugfix
15065 o Minor bugfixes (testing networks):
15066 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
15067 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
15068 - Stop using the default authorities in networks which provide both
15069 AlternateDirAuthority and AlternateBridgeAuthority. Partially
15070 fixes bug 13163; bugfix on 0.2.0.13-alpha.
15072 o Minor bugfixes (testing):
15073 - Stop spawn test failures due to a race condition between the
15074 SIGCHLD handler updating the process status, and the test reading
15075 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
15077 o Minor bugfixes (testing, Windows):
15078 - Avoid passing an extra backslash when creating a temporary
15079 directory for running the unit tests on Windows. Fixes bug 12392;
15080 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
15082 o Minor bugfixes (windows):
15083 - Remove code to special-case handling of NTE_BAD_KEYSET when
15084 acquiring windows CryptoAPI context. This error can't actually
15085 occur for the parameters we're providing. Fixes bug 10816; bugfix
15088 o Minor bugfixes (zlib):
15089 - Avoid truncating a zlib stream when trying to finalize it with an
15090 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
15093 - Allow our configure script to build correctly with autoconf 2.62
15094 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
15095 - Improve the error message from ./configure to make it clear that
15096 when asciidoc has not been found, the user will have to either add
15097 --disable-asciidoc argument or install asciidoc. Resolves
15100 o Code simplification and refactoring:
15101 - Change the entry_is_live() function to take named bitfield
15102 elements instead of an unnamed list of booleans. Closes
15104 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
15105 Resolves ticket 12205.
15106 - Use calloc and reallocarray functions instead of multiply-
15107 then-malloc. This makes it less likely for us to fall victim to an
15108 integer overflow attack when allocating. Resolves ticket 12855.
15109 - Use the standard macro name SIZE_MAX, instead of our
15111 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
15112 functions which take them as arguments. Replace 0 with NO_DIRINFO
15113 in a function call for clarity. Seeks to prevent future issues
15115 - Avoid 4 null pointer errors under clang static analysis by using
15116 tor_assert() to prove that the pointers aren't null. Fixes
15118 - Rework the API of policies_parse_exit_policy() to use a bitmask to
15119 represent parsing options, instead of a confusing mess of
15120 booleans. Resolves ticket 8197.
15121 - Introduce a helper function to parse ExitPolicy in
15122 or_options_t structure.
15125 - Add a doc/TUNING document with tips for handling large numbers of
15126 TCP connections when running busy Tor relay. Update the warning
15127 message to point to this file when running out of sockets
15128 operating system is allowing to use simultaneously. Resolves
15131 o Removed features:
15132 - We no longer remind the user about configuration options that have
15133 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
15134 - Remove our old, non-weighted bandwidth-based node selection code.
15135 Previously, we used it as a fallback when we couldn't perform
15136 weighted bandwidth-based node selection. But that would only
15137 happen in the cases where we had no consensus, or when we had a
15138 consensus generated by buggy or ancient directory authorities. In
15139 either case, it's better to use the more modern, better maintained
15140 algorithm, with reasonable defaults for the weights. Closes
15142 - Remove the --disable-curve25519 configure option. Relays and
15143 clients now are required to support curve25519 and the
15145 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
15146 used to be deprecated synonyms for "StrictNodes", are now marked
15147 obsolete. Resolves ticket 12226.
15148 - Clients don't understand the BadDirectory flag in the consensus
15149 anymore, and ignore it.
15152 - Refactor the function that chooses guard nodes so that it can more
15153 easily be tested; write some tests for it.
15154 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
15155 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
15156 - Create unit tests for format_time_interval(). With bug 13393.
15157 - Add unit tests for tor_timegm signed overflow, tor_timegm and
15158 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
15159 tests (visible) fixes in bug 13476.
15160 - Add a "coverage-html" make target to generate HTML-visualized
15161 coverage results when building with --enable-coverage. (Requires
15162 lcov.) Patch from Kevin Murray.
15163 - Enable the backtrace handler (where supported) when running the
15165 - Revise all unit tests that used the legacy test_* macros to
15166 instead use the recommended tt_* macros. This patch was generated
15167 with coccinelle, to avoid manual errors. Closes ticket 13119.
15169 o Distribution (systemd):
15170 - systemd unit file: only allow tor to write to /var/lib/tor and
15171 /var/log/tor. The rest of the filesystem is accessible for reading
15172 only. Patch by intrigeri; resolves ticket 12751.
15173 - systemd unit file: ensure that the process and all its children
15174 can never gain new privileges. Patch by intrigeri; resolves
15176 - systemd unit file: set up /var/run/tor as writable for the Tor
15177 service. Patch by intrigeri; resolves ticket 13196.
15179 o Removed features (directory authorities):
15180 - Remove code that prevented authorities from listing Tor relays
15181 affected by CVE-2011-2769 as guards. These relays are already
15182 rejected altogether due to the minimum version requirement of
15183 0.2.3.16-alpha. Closes ticket 13152.
15184 - The "AuthDirRejectUnlisted" option no longer has any effect, as
15185 the fingerprints file (approved-routers) has been deprecated.
15186 - Directory authorities do not support being Naming dirauths anymore.
15187 The "NamingAuthoritativeDir" config option is now obsolete.
15188 - Directory authorities do not support giving out the BadDirectory
15190 - Directory authorities no longer advertise or support consensus
15191 methods 1 through 12 inclusive. These consensus methods were
15192 obsolete and/or insecure: maintaining the ability to support them
15193 served no good purpose. Implements part of proposal 215; closes
15196 o Testing (test-network.sh):
15197 - Stop using "echo -n", as some shells' built-in echo doesn't
15198 support "-n". Instead, use "/bin/echo -n". Partially fixes
15200 - Stop an apparent test-network hang when used with make -j2. Fixes
15202 - Add a --delay option to test-network.sh, which configures the
15203 delay before the chutney network tests for data transmission.
15204 Partially implements ticket 13161.
15207 Changes in version 0.2.5.10 - 2014-10-24
15208 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
15210 It adds several new security features, including improved
15211 denial-of-service resistance for relays, new compiler hardening
15212 options, and a system-call sandbox for hardened installations on Linux
15213 (requires seccomp2). The controller protocol has several new features,
15214 resolving IPv6 addresses should work better than before, and relays
15215 should be a little more CPU-efficient. We've added support for more
15216 OpenBSD and FreeBSD transparent proxy types. We've improved the build
15217 system and testing infrastructure to allow unit testing of more parts
15218 of the Tor codebase. Finally, we've addressed several nagging pluggable
15219 transport usability issues, and included numerous other small bugfixes
15220 and features mentioned below.
15222 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
15223 have accumulated many known flaws; everyone should upgrade.
15225 o Deprecated versions:
15226 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
15227 attention for some while.
15230 Changes in version 0.2.5.9-rc - 2014-10-20
15231 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
15232 series. It disables SSL3 in response to the recent "POODLE" attack
15233 (even though POODLE does not affect Tor). It also works around a crash
15234 bug caused by some operating systems' response to the "POODLE" attack
15235 (which does affect Tor). It also contains a few miscellaneous fixes.
15237 o Major security fixes:
15238 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15239 today support TLS 1.0 or later, so we can safely turn off support
15240 for this old (and insecure) protocol. Fixes bug 13426.
15242 o Major bugfixes (openssl bug workaround):
15243 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15244 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15245 13471. This is a workaround for an OpenSSL bug.
15248 - Disable the sandbox name resolver cache when running tor-resolve:
15249 tor-resolve doesn't use the sandbox code, and turning it on was
15250 breaking attempts to do tor-resolve on a non-default server on
15251 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
15253 o Compilation fixes:
15254 - Build and run correctly on systems like OpenBSD-current that have
15255 patched OpenSSL to remove get_cipher_by_char and/or its
15256 implementations. Fixes issue 13325.
15258 o Downgraded warnings:
15259 - Downgrade the severity of the 'unexpected sendme cell from client'
15260 from 'warn' to 'protocol warning'. Closes ticket 8093.
15263 Changes in version 0.2.4.25 - 2014-10-20
15264 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
15265 (even though POODLE does not affect Tor). It also works around a crash
15266 bug caused by some operating systems' response to the "POODLE" attack
15267 (which does affect Tor).
15269 o Major security fixes (also in 0.2.5.9-rc):
15270 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15271 today support TLS 1.0 or later, so we can safely turn off support
15272 for this old (and insecure) protocol. Fixes bug 13426.
15274 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
15275 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15276 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15277 13471. This is a workaround for an OpenSSL bug.
15280 Changes in version 0.2.5.8-rc - 2014-09-22
15281 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
15282 series. It fixes a bug that affects consistency and speed when
15283 connecting to hidden services, and it updates the location of one of
15284 the directory authorities.
15287 - Clients now send the correct address for their chosen rendezvous
15288 point when trying to access a hidden service. They used to send
15289 the wrong address, which would still work some of the time because
15290 they also sent the identity digest of the rendezvous point, and if
15291 the hidden service happened to try connecting to the rendezvous
15292 point from a relay that already had a connection open to it,
15293 the relay would reuse that connection. Now connections to hidden
15294 services should be more robust and faster. Also, this bug meant
15295 that clients were leaking to the hidden service whether they were
15296 on a little-endian (common) or big-endian (rare) system, which for
15297 some users might have reduced their anonymity. Fixes bug 13151;
15298 bugfix on 0.2.1.5-alpha.
15300 o Directory authority changes:
15301 - Change IP address for gabelmoo (v3 directory authority).
15304 Changes in version 0.2.4.24 - 2014-09-22
15305 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
15306 connecting to hidden services, and it updates the location of one of
15307 the directory authorities.
15310 - Clients now send the correct address for their chosen rendezvous
15311 point when trying to access a hidden service. They used to send
15312 the wrong address, which would still work some of the time because
15313 they also sent the identity digest of the rendezvous point, and if
15314 the hidden service happened to try connecting to the rendezvous
15315 point from a relay that already had a connection open to it,
15316 the relay would reuse that connection. Now connections to hidden
15317 services should be more robust and faster. Also, this bug meant
15318 that clients were leaking to the hidden service whether they were
15319 on a little-endian (common) or big-endian (rare) system, which for
15320 some users might have reduced their anonymity. Fixes bug 13151;
15321 bugfix on 0.2.1.5-alpha.
15323 o Directory authority changes:
15324 - Change IP address for gabelmoo (v3 directory authority).
15326 o Minor features (geoip):
15327 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15331 Changes in version 0.2.5.7-rc - 2014-09-11
15332 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
15333 release series, and some long-standing bugs related to ORPort reachability
15334 testing and failure to send CREATE cells. It is the first release
15335 candidate for the Tor 0.2.5.x series.
15337 o Major bugfixes (client, startup):
15338 - Start making circuits as soon as DisabledNetwork is turned off.
15339 When Tor started with DisabledNetwork set, it would correctly
15340 conclude that it shouldn't build circuits, but it would mistakenly
15341 cache this conclusion, and continue believing it even when
15342 DisableNetwork is set to 0. Fixes the bug introduced by the fix
15343 for bug 11200; bugfix on 0.2.5.4-alpha.
15344 - Resume expanding abbreviations for command-line options. The fix
15345 for bug 4647 accidentally removed our hack from bug 586 that
15346 rewrote HashedControlPassword to __HashedControlSessionPassword
15347 when it appears on the commandline (which allowed the user to set
15348 her own HashedControlPassword in the torrc file while the
15349 controller generates a fresh session password for each run). Fixes
15350 bug 12948; bugfix on 0.2.5.1-alpha.
15351 - Warn about attempts to run hidden services and relays in the same
15352 process: that's probably not a good idea. Closes ticket 12908.
15354 o Major bugfixes (relay):
15355 - Avoid queuing or sending destroy cells for circuit ID zero when we
15356 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
15357 Found and fixed by "cypherpunks".
15358 - Fix ORPort reachability detection on relays running behind a
15359 proxy, by correctly updating the "local" mark on the controlling
15360 channel when changing the address of an or_connection_t after the
15361 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
15363 o Minor features (bridge):
15364 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
15365 cookie file for the ExtORPort g+r by default.
15367 o Minor features (geoip):
15368 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15371 o Minor bugfixes (logging):
15372 - Reduce the log severity of the "Pluggable transport proxy does not
15373 provide any needed transports and will not be launched." message,
15374 since Tor Browser includes several ClientTransportPlugin lines in
15375 its torrc-defaults file, leading every Tor Browser user who looks
15376 at her logs to see these notices and wonder if they're dangerous.
15377 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
15378 - Downgrade "Unexpected onionskin length after decryption" warning
15379 to a protocol-warn, since there's nothing relay operators can do
15380 about a client that sends them a malformed create cell. Resolves
15381 bug 12996; bugfix on 0.0.6rc1.
15382 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
15383 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
15384 - When logging information about an EXTEND2 or EXTENDED2 cell, log
15385 their names correctly. Fixes part of bug 12700; bugfix
15387 - When logging information about a relay cell whose command we don't
15388 recognize, log its command as an integer. Fixes part of bug 12700;
15389 bugfix on 0.2.1.10-alpha.
15390 - Escape all strings from the directory connection before logging
15391 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
15393 o Minor bugfixes (controller):
15394 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
15395 bug 12864; bugfix on 0.2.5.1-alpha.
15396 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
15397 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
15400 o Minor bugfixes (compilation):
15401 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
15402 bugfix on 0.2.5.5-alpha.
15403 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
15404 0.2.5.1-alpha. Patch from "NewEraCracker".
15405 - In routerlist_assert_ok(), don't take the address of a
15406 routerinfo's cache_info member unless that routerinfo is non-NULL.
15407 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
15408 - Fix a large number of false positive warnings from the clang
15409 analyzer static analysis tool. This should make real warnings
15410 easier for clang analyzer to find. Patch from "teor". Closes
15413 o Distribution (systemd):
15414 - Verify configuration file via ExecStartPre in the systemd unit
15415 file. Patch from intrigeri; resolves ticket 12730.
15416 - Explicitly disable RunAsDaemon in the systemd unit file. Our
15417 current systemd unit uses "Type = simple", so systemd does not
15418 expect tor to fork. If the user has "RunAsDaemon 1" in their
15419 torrc, then things won't work as expected. This is e.g. the case
15420 on Debian (and derivatives), since there we pass "--defaults-torrc
15421 /usr/share/tor/tor-service-defaults-torrc" (that contains
15422 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
15426 - Adjust the URLs in the README to refer to the new locations of
15427 several documents on the website. Fixes bug 12830. Patch from
15429 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
15433 Changes in version 0.2.5.6-alpha - 2014-07-28
15434 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
15435 risk from guard rotation, and fixes a variety of other issues to get
15436 us closer to a release candidate.
15438 o Major features (also in 0.2.4.23):
15439 - Make the number of entry guards configurable via a new
15440 NumEntryGuards consensus parameter, and the number of directory
15441 guards configurable via a new NumDirectoryGuards consensus
15442 parameter. Implements ticket 12688.
15444 o Major bugfixes (also in 0.2.4.23):
15445 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15446 implementation that caused incorrect results on 32-bit
15447 implementations when certain malformed inputs were used along with
15448 a small class of private ntor keys. This bug does not currently
15449 appear to allow an attacker to learn private keys or impersonate a
15450 Tor server, but it could provide a means to distinguish 32-bit Tor
15451 implementations from 64-bit Tor implementations. Fixes bug 12694;
15452 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15456 - Perform circuit cleanup operations even when circuit
15457 construction operations are disabled (because the network is
15458 disabled, or because there isn't enough directory information).
15459 Previously, when we were not building predictive circuits, we
15460 were not closing expired circuits either. Fixes bug 8387; bugfix on
15461 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
15462 became more strict about when we have "enough directory information
15463 to build circuits".
15466 - Authorities now assign the Guard flag to the fastest 25% of the
15467 network (it used to be the fastest 50%). Also raise the consensus
15468 weight that guarantees the Guard flag from 250 to 2000. For the
15469 current network, this results in about 1100 guards, down from 2500.
15470 This step paves the way for moving the number of entry guards
15471 down to 1 (proposal 236) while still providing reasonable expected
15472 performance for most users. Implements ticket 12690.
15473 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15475 - Slightly enhance the diagnostic message for bug 12184.
15477 o Minor bugfixes (also in 0.2.4.23):
15478 - Warn and drop the circuit if we receive an inbound 'relay early'
15479 cell. Those used to be normal to receive on hidden service circuits
15480 due to bug 1038, but the buggy Tor versions are long gone from
15481 the network so we can afford to resume watching for them. Resolves
15482 the rest of bug 1038; bugfix on 0.2.1.19.
15483 - Correct a confusing error message when trying to extend a circuit
15484 via the control protocol but we don't know a descriptor or
15485 microdescriptor for one of the specified relays. Fixes bug 12718;
15486 bugfix on 0.2.3.1-alpha.
15489 - Fix compilation when building with bufferevents enabled. (This
15490 configuration is still not expected to work, however.)
15491 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
15492 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
15494 - Compile correctly with builds and forks of OpenSSL (such as
15495 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
15496 0.2.1.1-alpha. Patch from "dhill".
15499 Changes in version 0.2.4.23 - 2014-07-28
15500 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
15501 guard rotation, and also backports several important fixes from the
15502 Tor 0.2.5 alpha release series.
15505 - Clients now look at the "usecreatefast" consensus parameter to
15506 decide whether to use CREATE_FAST or CREATE cells for the first hop
15507 of their circuit. This approach can improve security on connections
15508 where Tor's circuit handshake is stronger than the available TLS
15509 connection security levels, but the tradeoff is more computational
15510 load on guard relays. Implements proposal 221. Resolves ticket 9386.
15511 - Make the number of entry guards configurable via a new
15512 NumEntryGuards consensus parameter, and the number of directory
15513 guards configurable via a new NumDirectoryGuards consensus
15514 parameter. Implements ticket 12688.
15517 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15518 implementation that caused incorrect results on 32-bit
15519 implementations when certain malformed inputs were used along with
15520 a small class of private ntor keys. This bug does not currently
15521 appear to allow an attacker to learn private keys or impersonate a
15522 Tor server, but it could provide a means to distinguish 32-bit Tor
15523 implementations from 64-bit Tor implementations. Fixes bug 12694;
15524 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15528 - Warn and drop the circuit if we receive an inbound 'relay early'
15529 cell. Those used to be normal to receive on hidden service circuits
15530 due to bug 1038, but the buggy Tor versions are long gone from
15531 the network so we can afford to resume watching for them. Resolves
15532 the rest of bug 1038; bugfix on 0.2.1.19.
15533 - Correct a confusing error message when trying to extend a circuit
15534 via the control protocol but we don't know a descriptor or
15535 microdescriptor for one of the specified relays. Fixes bug 12718;
15536 bugfix on 0.2.3.1-alpha.
15537 - Avoid an illegal read from stack when initializing the TLS
15538 module using a version of OpenSSL without all of the ciphers
15539 used by the v2 link handshake. Fixes bug 12227; bugfix on
15540 0.2.4.8-alpha. Found by "starlight".
15543 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15547 Changes in version 0.2.5.5-alpha - 2014-06-18
15548 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
15549 0.2.5.x release series, including a couple of DoS issues, some
15550 performance regressions, a large number of bugs affecting the Linux
15551 seccomp2 sandbox code, and various other bugfixes. It also adds
15552 diagnostic bugfixes for a few tricky issues that we're trying to
15555 o Major features (security, traffic analysis resistance):
15556 - Several major improvements to the algorithm used to decide when to
15557 close TLS connections. Previous versions of Tor closed connections
15558 at a fixed interval after the last time a non-padding cell was
15559 sent over the connection, regardless of the target of the
15560 connection. Now, we randomize the intervals by adding up to 50% of
15561 their base value, we measure the length of time since connection
15562 last had at least one circuit, and we allow connections to known
15563 ORs to remain open a little longer (15 minutes instead of 3
15564 minutes minimum). These changes should improve Tor's resistance
15565 against some kinds of traffic analysis, and lower some overhead
15566 from needlessly closed connections. Fixes ticket 6799.
15567 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
15569 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
15570 - Fix a memory leak that could occur if a microdescriptor parse
15571 fails during the tokenizing step. This bug could enable a memory
15572 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15575 o Major bugfixes (security, directory authorities):
15576 - Directory authorities now include a digest of each relay's
15577 identity key as a part of its microdescriptor.
15579 This is a workaround for bug 11743 (reported by "cypherpunks"),
15580 where Tor clients do not support receiving multiple
15581 microdescriptors with the same SHA256 digest in the same
15582 consensus. When clients receive a consensus like this, they only
15583 use one of the relays. Without this fix, a hostile relay could
15584 selectively disable some client use of target relays by
15585 constructing a router descriptor with a different identity and the
15586 same microdescriptor parameters and getting the authorities to
15587 list it in a microdescriptor consensus. This fix prevents an
15588 attacker from causing a microdescriptor collision, because the
15589 router's identity is not forgeable.
15591 o Major bugfixes (relay):
15592 - Use a direct dirport connection when uploading non-anonymous
15593 descriptors to the directory authorities. Previously, relays would
15594 incorrectly use tunnel connections under a fairly wide variety of
15595 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
15596 - When a circuit accidentally has the same circuit ID for its
15597 forward and reverse direction, correctly detect the direction of
15598 cells using that circuit. Previously, this bug made roughly one
15599 circuit in a million non-functional. Fixes bug 12195; this is a
15600 bugfix on every version of Tor.
15602 o Major bugfixes (client, pluggable transports):
15603 - When managing pluggable transports, use OS notification facilities
15604 to learn if they have crashed, and don't attempt to kill any
15605 process that has already exited. Fixes bug 8746; bugfix
15608 o Minor features (diagnostic):
15609 - When logging a warning because of bug 7164, additionally check the
15610 hash table for consistency (as proposed on ticket 11737). This may
15611 help diagnose bug 7164.
15612 - When we log a heartbeat, log how many one-hop circuits we have
15613 that are at least 30 minutes old, and log status information about
15614 a few of them. This is an attempt to track down bug 8387.
15615 - When encountering an unexpected CR while writing text to a file on
15616 Windows, log the name of the file. Should help diagnosing
15618 - Give more specific warnings when a client notices that an onion
15619 handshake has failed. Fixes ticket 9635.
15620 - Add significant new logging code to attempt to diagnose bug 12184,
15621 where relays seem to run out of available circuit IDs.
15622 - Improve the diagnostic log message for bug 8387 even further to
15623 try to improve our odds of figuring out why one-hop directory
15624 circuits sometimes do not get closed.
15626 o Minor features (security, memory management):
15627 - Memory allocation tricks (mempools and buffer freelists) are now
15628 disabled by default. You can turn them back on with
15629 --enable-mempools and --enable-buf-freelists respectively. We're
15630 disabling these features because malloc performance is good enough
15631 on most platforms, and a similar feature in OpenSSL exacerbated
15632 exploitation of the Heartbleed attack. Resolves ticket 11476.
15634 o Minor features (security):
15635 - Apply the secure SipHash-2-4 function to the hash table mapping
15636 circuit IDs and channels to circuits. We missed this one when we
15637 were converting all the other hash functions to use SipHash back
15638 in 0.2.5.3-alpha. Resolves ticket 11750.
15640 o Minor features (build):
15641 - The configure script has a --disable-seccomp option to turn off
15642 support for libseccomp on systems that have it, in case it (or
15643 Tor's use of it) is broken. Resolves ticket 11628.
15645 o Minor features (other):
15646 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
15649 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
15650 - When running a hidden service, do not allow TunneledDirConns 0;
15651 this will keep the hidden service from running, and also
15652 make it publish its descriptors directly over HTTP. Fixes bug 10849;
15653 bugfix on 0.2.1.1-alpha.
15655 o Minor bugfixes (performance):
15656 - Avoid a bug where every successful connection made us recompute
15657 the flag telling us whether we have sufficient information to
15658 build circuits. Previously, we would forget our cached value
15659 whenever we successfully opened a channel (or marked a router as
15660 running or not running for any other reason), regardless of
15661 whether we had previously believed the router to be running. This
15662 forced us to run an expensive update operation far too often.
15663 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
15664 - Avoid using tor_memeq() for checking relay cell integrity. This
15665 removes a possible performance bottleneck. Fixes part of bug
15666 12169; bugfix on 0.2.1.31.
15668 o Minor bugfixes (compilation):
15669 - Fix compilation of test_status.c when building with MVSC. Bugfix
15670 on 0.2.5.4-alpha. Patch from Gisle Vanem.
15671 - Resolve GCC complaints on OpenBSD about discarding constness in
15672 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
15673 on 0.1.1.23. Patch from Dana Koch.
15674 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
15675 treatment of long and time_t as comparable types. Fixes part of
15676 bug 11633. Patch from Dana Koch.
15677 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
15678 11623; bugfix on 0.2.5.3-alpha.
15679 - When deciding whether to build the 64-bit curve25519
15680 implementation, detect platforms where we can compile 128-bit
15681 arithmetic but cannot link it. Fixes bug 11729; bugfix on
15682 0.2.4.8-alpha. Patch from "conradev".
15683 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
15684 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
15685 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
15688 o Minor bugfixes (Directory server):
15689 - When sending a compressed set of descriptors or microdescriptors,
15690 make sure to finalize the zlib stream. Previously, we would write
15691 all the compressed data, but if the last descriptor we wanted to
15692 send was missing or too old, we would not mark the stream as
15693 finished. This caused problems for decompression tools. Fixes bug
15694 11648; bugfix on 0.1.1.23.
15696 o Minor bugfixes (Linux seccomp sandbox):
15697 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
15698 11622; bugfix on 0.2.5.1-alpha.
15699 - Avoid crashing when re-opening listener ports with the seccomp
15700 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
15701 - Avoid crashing with the seccomp sandbox enabled along with
15702 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
15703 - When we receive a SIGHUP with the sandbox enabled, correctly
15704 support rotating our log files. Fixes bug 12032; bugfix
15706 - Avoid crash when running with sandboxing enabled and
15707 DirReqStatistics not disabled. Fixes bug 12035; bugfix
15709 - Fix a "BUG" warning when trying to write bridge-stats files with
15710 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
15712 - Prevent the sandbox from crashing on startup when run with the
15713 --enable-expensive-hardening configuration option. Fixes bug
15714 11477; bugfix on 0.2.5.4-alpha.
15715 - When running with DirPortFrontPage and sandboxing both enabled,
15716 reload the DirPortFrontPage correctly when restarting. Fixes bug
15717 12028; bugfix on 0.2.5.1-alpha.
15718 - Don't try to enable the sandbox when using the Tor binary to check
15719 its configuration, hash a passphrase, or so on. Doing so was
15720 crashing on startup for some users. Fixes bug 11609; bugfix
15722 - Avoid warnings when running with sandboxing and node statistics
15723 enabled at the same time. Fixes part of 12064; bugfix on
15724 0.2.5.1-alpha. Patch from Michael Wolf.
15725 - Avoid warnings when running with sandboxing enabled at the same
15726 time as cookie authentication, hidden services, or directory
15727 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
15728 - Do not allow options that require calls to exec to be enabled
15729 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
15730 bug 12043; bugfix on 0.2.5.1-alpha.
15731 - Handle failures in getpwnam()/getpwuid() when running with the
15732 User option set and the Linux syscall sandbox enabled. Fixes bug
15733 11946; bugfix on 0.2.5.1-alpha.
15734 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
15735 to avoid calling getaddrinfo() after installing the sandbox
15736 filters. Previously, it preloaded a cache with the IPv4 address
15737 for our hostname, and nothing else. Now, it loads the cache with
15738 every address that it used to initialize the Tor process. Fixes
15739 bug 11970; bugfix on 0.2.5.1-alpha.
15741 o Minor bugfixes (pluggable transports):
15742 - Enable the ExtORPortCookieAuthFile option, to allow changing the
15743 default location of the authentication token for the extended OR
15744 Port as used by sever-side pluggable transports. We had
15745 implemented this option before, but the code to make it settable
15746 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
15747 - Avoid another 60-second delay when starting Tor in a pluggable-
15748 transport-using configuration when we already have cached
15749 descriptors for our bridges. Fixes bug 11965; bugfix
15752 o Minor bugfixes (client):
15753 - Avoid "Tried to open a socket with DisableNetwork set" warnings
15754 when starting a client with bridges configured and DisableNetwork
15755 set. (Tor launcher starts Tor with DisableNetwork set the first
15756 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
15758 o Minor bugfixes (testing):
15759 - The Python parts of the test scripts now work on Python 3 as well
15760 as Python 2, so systems where '/usr/bin/python' is Python 3 will
15761 no longer have the tests break. Fixes bug 11608; bugfix
15763 - When looking for versions of python that we could run the tests
15764 with, check for "python2.7" and "python3.3"; previously we were
15765 only looking for "python", "python2", and "python3". Patch from
15766 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
15767 - Fix all valgrind warnings produced by the unit tests. There were
15768 over a thousand memory leak warnings previously, mostly produced
15769 by forgetting to free things in the unit test code. Fixes bug
15770 11618, bugfixes on many versions of Tor.
15772 o Minor bugfixes (tor-fw-helper):
15773 - Give a correct log message when tor-fw-helper fails to launch.
15774 (Previously, we would say something like "tor-fw-helper sent us a
15775 string we could not parse".) Fixes bug 9781; bugfix
15778 o Minor bugfixes (relay, threading):
15779 - Check return code on spawn_func() in cpuworker code, so that we
15780 don't think we've spawned a nonworking cpuworker and write junk to
15781 it forever. Fix related to bug 4345; bugfix on all released Tor
15782 versions. Found by "skruffy".
15783 - Use a pthread_attr to make sure that spawn_func() cannot return an
15784 error while at the same time launching a thread. Fix related to
15785 bug 4345; bugfix on all released Tor versions. Reported
15788 o Minor bugfixes (relay, oom prevention):
15789 - Correctly detect the total available system memory. We tried to do
15790 this in 0.2.5.4-alpha, but the code was set up to always return an
15791 error value, even on success. Fixes bug 11805; bugfix
15794 o Minor bugfixes (relay, other):
15795 - We now drop CREATE cells for already-existent circuit IDs and for
15796 zero-valued circuit IDs, regardless of other factors that might
15797 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
15799 - Avoid an illegal read from stack when initializing the TLS module
15800 using a version of OpenSSL without all of the ciphers used by the
15801 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
15803 - When rejecting DATA cells for stream_id zero, still count them
15804 against the circuit's deliver window so that we don't fail to send
15805 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
15807 o Minor bugfixes (logging):
15808 - Fix a misformatted log message about delayed directory fetches.
15809 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
15810 - Squelch a spurious LD_BUG message "No origin circuit for
15811 successful SOCKS stream" in certain hidden service failure cases;
15815 - Include a tor.service file in contrib/dist for use with systemd.
15816 Some distributions will be able to use this file unmodified;
15817 others will need to tweak it, or write their own. Patch from Jamie
15818 Nguyen; resolves ticket 8368.
15821 - Clean up several option names in the manpage to match their real
15822 names, add the missing documentation for a couple of testing and
15823 directory authority options, remove the documentation for a
15824 V2-directory fetching option that no longer exists. Resolves
15826 - Correct the documentation so that it lists the correct directory
15827 for the stats files. (They are in a subdirectory called "stats",
15829 - In the manpage, move more authority-only options into the
15830 directory authority section so that operators of regular directory
15831 caches don't get confused.
15834 - The contrib directory has been sorted and tidied. Before, it was
15835 an unsorted dumping ground for useful and not-so-useful things.
15836 Now, it is divided based on functionality, and the items which
15837 seemed to be nonfunctional or useless have been removed. Resolves
15838 ticket 8966; based on patches from "rl1987".
15841 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
15842 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
15843 - The TunnelDirConns and PreferTunnelledDirConns options no longer
15844 exist; tunneled directory connections have been available since
15845 0.1.2.5-alpha, and turning them off is not a good idea. This is a
15846 brute-force fix for 10849, where "TunnelDirConns 0" would break
15850 Changes in version 0.2.4.22 - 2014-05-16
15851 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
15852 alpha release series. These include blocking all authority signing
15853 keys that may have been affected by the OpenSSL "heartbleed" bug,
15854 choosing a far more secure set of TLS ciphersuites by default, closing
15855 a couple of memory leaks that could be used to run a target relay out
15856 of RAM, and several others.
15858 o Major features (security, backport from 0.2.5.4-alpha):
15859 - Block authority signing keys that were used on authorities
15860 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15861 don't have any evidence that these keys _were_ compromised; we're
15862 doing this to be prudent.) Resolves ticket 11464.
15864 o Major bugfixes (security, OOM):
15865 - Fix a memory leak that could occur if a microdescriptor parse
15866 fails during the tokenizing step. This bug could enable a memory
15867 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15870 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
15871 - The relay ciphersuite list is now generated automatically based on
15872 uniform criteria, and includes all OpenSSL ciphersuites with
15873 acceptable strength and forward secrecy. Previously, we had left
15874 some perfectly fine ciphersuites unsupported due to omission or
15875 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15876 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15877 - Relays now trust themselves to have a better view than clients of
15878 which TLS ciphersuites are better than others. (Thanks to bug
15879 11513, the relay list is now well-considered, whereas the client
15880 list has been chosen mainly for anti-fingerprinting purposes.)
15881 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
15882 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
15883 AES128. Resolves ticket 11528.
15884 - Clients now try to advertise the same list of ciphersuites as
15885 Firefox 28. This change enables selection of (fast) GCM
15886 ciphersuites, disables some strange old ciphers, and stops
15887 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
15888 Resolves ticket 11438.
15890 o Minor bugfixes (configuration, security):
15891 - When running a hidden service, do not allow TunneledDirConns 0:
15892 trying to set that option together with a hidden service would
15893 otherwise prevent the hidden service from running, and also make
15894 it publish its descriptors directly over HTTP. Fixes bug 10849;
15895 bugfix on 0.2.1.1-alpha.
15897 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
15898 - Avoid sending a garbage value to the controller when a circuit is
15899 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
15901 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
15902 - Stop leaking memory when we successfully resolve a PTR record.
15903 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
15905 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
15906 - Avoid 60-second delays in the bootstrapping process when Tor is
15907 launching for a second time while using bridges. Fixes bug 9229;
15908 bugfix on 0.2.0.3-alpha.
15910 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
15911 - Give the correct URL in the warning message when trying to run a
15912 relay on an ancient version of Windows. Fixes bug 9393.
15914 o Minor bugfixes (compilation):
15915 - Fix a compilation error when compiling with --disable-curve25519.
15916 Fixes bug 9700; bugfix on 0.2.4.17-rc.
15919 - Downgrade the warning severity for the the "md was still
15920 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
15921 for trying to diagnose this bug, and the current warning in
15922 earlier versions of tor achieves nothing useful. Addresses warning
15925 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
15926 - When we run out of usable circuit IDs on a channel, log only one
15927 warning for the whole channel, and describe how many circuits
15928 there were on the channel. Fixes part of ticket 11553.
15930 o Minor features (security, backport from 0.2.5.4-alpha):
15931 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
15932 leave the default at 8GBytes), to better support Raspberry Pi
15933 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
15935 o Documentation (backport from 0.2.5.4-alpha):
15936 - Correctly document that we search for a system torrc file before
15937 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
15941 Changes in version 0.2.5.4-alpha - 2014-04-25
15942 Tor 0.2.5.4-alpha includes several security and performance
15943 improvements for clients and relays, including blacklisting authority
15944 signing keys that were used while susceptible to the OpenSSL
15945 "heartbleed" bug, fixing two expensive functions on busy relays,
15946 improved TLS ciphersuite preference lists, support for run-time
15947 hardening on compilers that support AddressSanitizer, and more work on
15948 the Linux sandbox code.
15950 There are also several usability fixes for clients (especially clients
15951 that use bridges), two new TransPort protocols supported (one on
15952 OpenBSD, one on FreeBSD), and various other bugfixes.
15954 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
15955 have accumulated many known flaws; everyone should upgrade.
15957 o Major features (security):
15958 - If you don't specify MaxMemInQueues yourself, Tor now tries to
15959 pick a good value based on your total system memory. Previously,
15960 the default was always 8 GB. You can still override the default by
15961 setting MaxMemInQueues yourself. Resolves ticket 11396.
15962 - Block authority signing keys that were used on authorities
15963 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15964 don't have any evidence that these keys _were_ compromised; we're
15965 doing this to be prudent.) Resolves ticket 11464.
15967 o Major features (relay performance):
15968 - Speed up server-side lookups of rendezvous and introduction point
15969 circuits by using hashtables instead of linear searches. These
15970 functions previously accounted between 3 and 7% of CPU usage on
15971 some busy relays. Resolves ticket 9841.
15972 - Avoid wasting CPU when extending a circuit over a channel that is
15973 nearly out of circuit IDs. Previously, we would do a linear scan
15974 over possible circuit IDs before finding one or deciding that we
15975 had exhausted our possibilities. Now, we try at most 64 random
15976 circuit IDs before deciding that we probably won't succeed. Fixes
15977 a possible root cause of ticket 11553.
15979 o Major features (seccomp2 sandbox, Linux only):
15980 - The seccomp2 sandbox can now run a test network for multiple hours
15981 without crashing. The sandbox is still experimental, and more bugs
15982 will probably turn up. To try it, enable "Sandbox 1" on a Linux
15983 host. Resolves ticket 11351.
15984 - Strengthen sandbox code: the sandbox can now test the arguments
15985 for rename(), and blocks _sysctl() entirely. Resolves another part
15987 - When the sandbox blocks a system call, it now tries to log a stack
15988 trace before exiting. Resolves ticket 11465.
15990 o Major bugfixes (TLS cipher selection):
15991 - The relay ciphersuite list is now generated automatically based on
15992 uniform criteria, and includes all OpenSSL ciphersuites with
15993 acceptable strength and forward secrecy. Previously, we had left
15994 some perfectly fine ciphersuites unsupported due to omission or
15995 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15996 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15997 - Relays now trust themselves to have a better view than clients of
15998 which TLS ciphersuites are better than others. (Thanks to bug
15999 11513, the relay list is now well-considered, whereas the client
16000 list has been chosen mainly for anti-fingerprinting purposes.)
16001 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
16002 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
16003 AES128. Resolves ticket 11528.
16004 - Clients now try to advertise the same list of ciphersuites as
16005 Firefox 28. This change enables selection of (fast) GCM
16006 ciphersuites, disables some strange old ciphers, and stops
16007 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
16008 Resolves ticket 11438.
16010 o Major bugfixes (bridge client):
16011 - Avoid 60-second delays in the bootstrapping process when Tor is
16012 launching for a second time while using bridges. Fixes bug 9229;
16013 bugfix on 0.2.0.3-alpha.
16015 o Minor features (transparent proxy, *BSD):
16016 - Support FreeBSD's ipfw firewall interface for TransPort ports on
16017 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
16018 10267; patch from "yurivict".
16019 - Support OpenBSD's divert-to rules with the pf firewall for
16020 transparent proxy ports. To enable it, set "TransProxyType
16021 pf-divert". This allows Tor to run a TransPort transparent proxy
16022 port on OpenBSD 4.4 or later without root privileges. See the
16023 pf.conf(5) manual page for information on configuring pf to use
16024 divert-to rules. Closes ticket 10896; patch from Dana Koch.
16026 o Minor features (security):
16027 - New --enable-expensive-hardening option to enable security
16028 hardening options that consume nontrivial amounts of CPU and
16029 memory. Right now, this includes AddressSanitizer and UbSan, which
16030 are supported in newer versions of GCC and Clang. Closes ticket
16033 o Minor features (log verbosity):
16034 - Demote the message that we give when a flushing connection times
16035 out for too long from NOTICE to INFO. It was usually meaningless.
16036 Resolves ticket 5286.
16037 - Don't log so many notice-level bootstrapping messages at startup
16038 about downloading descriptors. Previously, we'd log a notice
16039 whenever we learned about more routers. Now, we only log a notice
16040 at every 5% of progress. Fixes bug 9963.
16041 - Warn less verbosely when receiving a malformed
16042 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
16043 - When we run out of usable circuit IDs on a channel, log only one
16044 warning for the whole channel, and describe how many circuits
16045 there were on the channel. Fixes part of ticket 11553.
16047 o Minor features (relay):
16048 - If a circuit timed out for at least 3 minutes, check if we have a
16049 new external IP address, and publish a new descriptor with the new
16050 IP address if it changed. Resolves ticket 2454.
16052 o Minor features (controller):
16053 - Make the entire exit policy available from the control port via
16054 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
16056 - Because of the fix for ticket 11396, the real limit for memory
16057 usage may no longer match the configured MaxMemInQueues value. The
16058 real limit is now exposed via GETINFO limits/max-mem-in-queues.
16060 o Minor features (bridge client):
16061 - Report a more useful failure message when we can't connect to a
16062 bridge because we don't have the right pluggable transport
16063 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
16065 o Minor features (diagnostic):
16066 - Add more log messages to diagnose bug 7164, which causes
16067 intermittent "microdesc_free() called but md was still referenced"
16068 warnings. We now include more information, to figure out why we
16069 might be cleaning a microdescriptor for being too old if it's
16070 still referenced by a live node_t object.
16072 o Minor bugfixes (client, DNSPort):
16073 - When using DNSPort, try to respond to AAAA requests with AAAA
16074 answers. Previously, we hadn't looked at the request type when
16075 deciding which answer type to prefer. Fixes bug 10468; bugfix on
16077 - When receiving a DNS query for an unsupported record type, reply
16078 with no answer rather than with a NOTIMPL error. This behavior
16079 isn't correct either, but it will break fewer client programs, we
16080 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
16083 o Minor bugfixes (exit relay):
16084 - Stop leaking memory when we successfully resolve a PTR record.
16085 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
16087 o Minor bugfixes (bridge client):
16088 - Stop accepting bridge lines containing hostnames. Doing so would
16089 cause clients to perform DNS requests on the hostnames, which was
16090 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
16091 - Avoid a 60-second delay in the bootstrapping process when a Tor
16092 client with pluggable transports re-reads its configuration at
16093 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
16095 o Minor bugfixes (client, logging during bootstrap):
16096 - Warn only once if we start logging in an unsafe way. Previously,
16097 we complain as many times as we had problems. Fixes bug 9870;
16098 bugfix on 0.2.5.1-alpha.
16099 - Only report the first fatal bootstrap error on a given OR
16100 connection. This stops us from telling the controller bogus error
16101 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
16102 - Be more helpful when trying to run sandboxed on Linux without
16103 libseccomp. Instead of saying "Sandbox is not implemented on this
16104 platform", we now explain that we need to be built with
16105 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
16106 - Avoid generating spurious warnings when starting with
16107 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
16110 o Minor bugfixes (closing OR connections):
16111 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
16112 check if it's an or_connection_t and correctly call
16113 connection_or_close_for_error() rather than
16114 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
16116 - When closing all connections on setting DisableNetwork to 1, use
16117 connection_or_close_normally() rather than closing OR connections
16118 out from under the channel layer. Fixes bug 11306; bugfix on
16121 o Minor bugfixes (controller):
16122 - Avoid sending a garbage value to the controller when a circuit is
16123 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
16125 o Minor bugfixes (tor-fw-helper):
16126 - Allow tor-fw-helper to build again by adding src/ext to its
16127 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
16129 o Minor bugfixes (bridges):
16130 - Avoid potential crashes or bad behavior when launching a
16131 server-side managed proxy with ORPort or ExtORPort temporarily
16132 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
16134 o Minor bugfixes (platform-specific):
16135 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
16136 bug 11426; bugfix on 0.2.5.3-alpha.
16137 - When dumping a malformed directory object to disk, save it in
16138 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
16140 - Don't report failures from make_socket_reuseable() on incoming
16141 sockets on OSX: this can happen when incoming connections close
16142 early. Fixes bug 10081.
16144 o Minor bugfixes (trivial memory leaks):
16145 - Fix a small memory leak when signing a directory object. Fixes bug
16146 11275; bugfix on 0.2.4.13-alpha.
16147 - Free placeholder entries in our circuit table at exit; fixes a
16148 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
16149 - Don't re-initialize a second set of OpenSSL mutexes when starting
16150 up. Previously, we'd make one set of mutexes, and then immediately
16151 replace them with another. Fixes bug 11726; bugfix on
16153 - Resolve some memory leaks found by coverity in the unit tests, on
16154 exit in tor-gencert, and on a failure to compute digests for our
16155 own keys when generating a v3 networkstatus vote. These leaks
16156 should never have affected anyone in practice.
16158 o Minor bugfixes (hidden service):
16159 - Only retry attempts to connect to a chosen rendezvous point 8
16160 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
16162 o Minor bugfixes (misc code correctness):
16163 - Fix various instances of undefined behavior in channeltls.c,
16164 tor_memmem(), and eventdns.c that would cause us to construct
16165 pointers to memory outside an allocated object. (These invalid
16166 pointers were not accessed, but C does not even allow them to
16167 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
16168 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
16169 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
16170 fix some miscellaneous errors in our tests and codebase. Fixes bug
16171 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
16172 - Always check return values for unlink, munmap, UnmapViewOfFile;
16173 check strftime return values more often. In some cases all we can
16174 do is report a warning, but this may help prevent deeper bugs from
16175 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
16177 - Fix numerous warnings from the clang "scan-build" static analyzer.
16178 Some of these are programming style issues; some of them are false
16179 positives that indicated awkward code; some are undefined behavior
16180 cases related to constructing (but not using) invalid pointers;
16181 some are assumptions about API behavior; some are (harmlessly)
16182 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
16183 correct; and one or two are genuine bugs that weren't reachable
16184 from the rest of the program. Fixes bug 8793; bugfixes on many,
16188 - Build the torify.1 manpage again. Previously, we were only trying
16189 to build it when also building tor-fw-helper. That's why we didn't
16190 notice that we'd broken the ability to build it. Fixes bug 11321;
16191 bugfix on 0.2.5.1-alpha.
16192 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
16193 11061; bugfix on 0.2.4.7-alpha.
16194 - Correctly document that we search for a system torrc file before
16195 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16197 - Resolve warnings from Doxygen.
16199 o Code simplifications and refactoring:
16200 - Remove is_internal_IP() function. Resolves ticket 4645.
16201 - Remove unused function circuit_dump_by_chan from circuitlist.c.
16202 Closes issue 9107; patch from "marek".
16203 - Change our use of the ENUM_BF macro to avoid declarations that
16206 o Deprecated versions:
16207 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
16208 attention for some while. Directory authorities no longer accept
16209 descriptors from relays running any version of Tor prior to Tor
16210 0.2.3.16-alpha. Resolves ticket 11149.
16213 - New macros in test.h to simplify writing mock-functions for unit
16214 tests. Part of ticket 11507. Patch from Dana Koch.
16215 - Complete tests for the status.c module. Resolves ticket 11507.
16216 Patch from Dana Koch.
16219 - Remove all code for the long unused v1 directory protocol.
16220 Resolves ticket 11070.
16223 Changes in version 0.2.5.3-alpha - 2014-03-22
16224 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
16225 two new anti-DoS features for Tor relays, resolves a bug that kept
16226 SOCKS5 support for IPv6 from working, fixes several annoying usability
16227 issues for bridge users, and removes more old code for unused
16230 The Tor 0.2.5.x release series is now in patch-freeze: no feature
16231 patches not already written will be considered for inclusion in 0.2.5.x.
16233 o Major features (relay security, DoS-resistance):
16234 - When deciding whether we have run out of memory and we need to
16235 close circuits, also consider memory allocated in buffers for
16236 streams attached to each circuit.
16238 This change, which extends an anti-DoS feature introduced in
16239 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
16240 better resist more memory-based DoS attacks than before. Since the
16241 MaxMemInCellQueues option now applies to all queues, it is renamed
16242 to MaxMemInQueues. This feature fixes bug 10169.
16243 - Avoid hash-flooding denial-of-service attacks by using the secure
16244 SipHash-2-4 hash function for our hashtables. Without this
16245 feature, an attacker could degrade performance of a targeted
16246 client or server by flooding their data structures with a large
16247 number of entries to be stored at the same hash table position,
16248 thereby slowing down the Tor instance. With this feature, hash
16249 table positions are derived from a randomized cryptographic key,
16250 and an attacker cannot predict which entries will collide. Closes
16252 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
16253 the default at 8GBytes), to better support Raspberry Pi users. Fixes
16254 bug 9686; bugfix on 0.2.4.14-alpha.
16256 o Minor features (bridges, pluggable transports):
16257 - Bridges now write the SHA1 digest of their identity key
16258 fingerprint (that is, a hash of a hash of their public key) to
16259 notice-level logs, and to a new hashed-fingerprint file. This
16260 information will help bridge operators look up their bridge in
16261 Globe and similar tools. Resolves ticket 10884.
16262 - Improve the message that Tor displays when running as a bridge
16263 using pluggable transports without an Extended ORPort listener.
16264 Also, log the message in the log file too. Resolves ticket 11043.
16266 o Minor features (other):
16267 - Add a new option, PredictedPortsRelevanceTime, to control how long
16268 after having received a request to connect to a given port Tor
16269 will try to keep circuits ready in anticipation of future requests
16270 for that port. Patch from "unixninja92"; implements ticket 9176.
16271 - Generate a warning if any ports are listed in the SocksPolicy,
16272 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
16273 AuthDirBadExit options. (These options only support address
16274 ranges.) Fixes part of ticket 11108.
16275 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
16278 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
16279 - Build without warnings under clang 3.4. (We have some macros that
16280 define static functions only some of which will get used later in
16281 the module. Starting with clang 3.4, these give a warning unless the
16282 unused attribute is set on them.) Resolves ticket 10904.
16283 - Fix build warnings about missing "a2x" comment when building the
16284 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16285 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16287 o Minor bugfixes (client):
16288 - Improve the log message when we can't connect to a hidden service
16289 because all of the hidden service directory nodes hosting its
16290 descriptor are excluded. Improves on our fix for bug 10722, which
16291 was a bugfix on 0.2.0.10-alpha.
16292 - Raise a control port warning when we fail to connect to all of
16293 our bridges. Previously, we didn't inform the controller, and
16294 the bootstrap process would stall. Fixes bug 11069; bugfix on
16296 - Exit immediately when a process-owning controller exits.
16297 Previously, tor relays would wait for a little while after their
16298 controller exited, as if they had gotten an INT signal -- but this
16299 was problematic, since there was no feedback for the user. To do a
16300 clean shutdown, controllers should send an INT signal and give Tor
16301 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
16302 - Stop attempting to connect to bridges before our pluggable
16303 transports are configured (harmless but resulted in some erroneous
16304 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
16305 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
16306 generating incorrect SOCKS5 responses, and confusing client
16307 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
16309 o Minor bugfixes (relays and bridges):
16310 - Avoid crashing on a malformed resolv.conf file when running a
16311 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
16312 - Non-exit relays no longer launch mock DNS requests to check for
16313 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
16314 non-exit relays stopped servicing DNS requests. Fixes bug 965;
16315 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
16316 - Bridges now report complete directory request statistics. Related
16317 to bug 5824; bugfix on 0.2.2.1-alpha.
16318 - Bridges now never collect statistics that were designed for
16319 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
16320 - Stop giving annoying warning messages when we decide not to launch
16321 a pluggable transport proxy that we don't need (because there are
16322 no bridges configured to use it). Resolves ticket 5018; bugfix
16324 - Give the correct URL in the warning message when trying to run a
16325 relay on an ancient version of Windows. Fixes bug 9393.
16327 o Minor bugfixes (backtrace support):
16328 - Support automatic backtraces on more platforms by using the
16329 "-fasynchronous-unwind-tables" compiler option. This option is
16330 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
16331 is on by default and table generation is not. This doesn't yet
16332 add Windows support; only Linux, OSX, and some BSDs are affected.
16333 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
16334 - Avoid strange behavior if two threads hit failed assertions at the
16335 same time and both try to log backtraces at once. (Previously, if
16336 this had happened, both threads would have stored their intermediate
16337 results in the same buffer, and generated junk outputs.) Reported by
16338 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
16339 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
16340 0.2.5.2-alpha; patch from Nick Hopper.
16342 o Minor bugfixes (unit tests):
16343 - Fix a small bug in the unit tests that might have made the tests
16344 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
16345 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
16348 - Remove all remaining code related to version-0 hidden service
16349 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
16350 the rest of bug 10841.
16353 - Document in the manpage that "KBytes" may also be written as
16354 "kilobytes" or "KB", that "Kbits" may also be written as
16355 "kilobits", and so forth. Closes ticket 9222.
16356 - Document that the ClientOnly config option overrides ORPort.
16357 Our old explanation made ClientOnly sound as though it did
16358 nothing at all. Resolves bug 9059.
16359 - Explain that SocksPolicy, DirPolicy, and similar options don't
16360 take port arguments. Fixes the other part of ticket 11108.
16361 - Fix a comment about the rend_server_descriptor_t.protocols field
16362 to more accurately describe its range. Also, make that field
16363 unsigned, to more accurately reflect its usage. Fixes bug 9099;
16364 bugfix on 0.2.1.5-alpha.
16365 - Fix the manpage's description of HiddenServiceAuthorizeClient:
16366 the maximum client name length is 16, not 19. Fixes bug 11118;
16367 bugfix on 0.2.1.6-alpha.
16369 o Code simplifications and refactoring:
16370 - Get rid of router->address, since in all cases it was just the
16371 string representation of router->addr. Resolves ticket 5528.
16373 o Test infrastructure:
16374 - Update to the latest version of tinytest.
16375 - Improve the tinytest implementation of string operation tests so
16376 that comparisons with NULL strings no longer crash the tests; they
16377 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
16380 Changes in version 0.2.4.21 - 2014-02-28
16381 Tor 0.2.4.21 further improves security against potential adversaries who
16382 find breaking 1024-bit crypto doable, and backports several stability
16383 and robustness patches from the 0.2.5 branch.
16385 o Major features (client security):
16386 - When we choose a path for a 3-hop circuit, make sure it contains
16387 at least one relay that supports the NTor circuit extension
16388 handshake. Otherwise, there is a chance that we're building
16389 a circuit that's worth attacking by an adversary who finds
16390 breaking 1024-bit crypto doable, and that chance changes the game
16391 theory. Implements ticket 9777.
16394 - Do not treat streams that fail with reason
16395 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16396 since it could also indicate an ENETUNREACH connection error. Fixes
16397 part of bug 10777; bugfix on 0.2.4.8-alpha.
16399 o Code simplification and refactoring:
16400 - Remove data structures which were introduced to implement the
16401 CellStatistics option: they are now redundant with the new timestamp
16402 field in the regular packed_cell_t data structure, which we did
16403 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
16406 - Always clear OpenSSL bignums before freeing them -- even bignums
16407 that don't contain secrets. Resolves ticket 10793. Patch by
16409 - Build without warnings under clang 3.4. (We have some macros that
16410 define static functions only some of which will get used later in
16411 the module. Starting with clang 3.4, these give a warning unless the
16412 unused attribute is set on them.) Resolves ticket 10904.
16413 - Update geoip and geoip6 files to the February 7 2014 Maxmind
16414 GeoLite2 Country database.
16417 - Set the listen() backlog limit to the largest actually supported
16418 on the system, not to the value in a header file. Fixes bug 9716;
16419 bugfix on every released Tor.
16420 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16421 exit node as a NOROUTE error, not an INTERNAL error, since they
16422 can apparently happen when trying to connect to the wrong sort
16423 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16424 - Fix build warnings about missing "a2x" comment when building the
16425 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16426 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16427 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16428 not entirely remove it from the connection lists. Fixes bug 9602;
16429 bugfix on 0.2.4.4-alpha.
16430 - Fix a segmentation fault in our benchmark code when running with
16431 Fedora's OpenSSL package, or any other OpenSSL that provides
16432 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16433 - Turn "circuit handshake stats since last time" log messages into a
16434 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16436 o Documentation fixes:
16437 - Document that all but one DirPort entry must have the NoAdvertise
16438 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16441 Changes in version 0.2.5.2-alpha - 2014-02-13
16442 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
16443 like the "poor random number generation" fix and the "building too many
16444 circuits" fix. It also further improves security against potential
16445 adversaries who find breaking 1024-bit crypto doable, and launches
16446 pluggable transports on demand (which gets us closer to integrating
16447 pluggable transport support by default -- not to be confused with Tor
16448 bundles enabling pluggable transports and bridges by default).
16450 o Major features (client security):
16451 - When we choose a path for a 3-hop circuit, make sure it contains
16452 at least one relay that supports the NTor circuit extension
16453 handshake. Otherwise, there is a chance that we're building
16454 a circuit that's worth attacking by an adversary who finds
16455 breaking 1024-bit crypto doable, and that chance changes the game
16456 theory. Implements ticket 9777.
16457 - Clients now look at the "usecreatefast" consensus parameter to
16458 decide whether to use CREATE_FAST or CREATE cells for the first hop
16459 of their circuit. This approach can improve security on connections
16460 where Tor's circuit handshake is stronger than the available TLS
16461 connection security levels, but the tradeoff is more computational
16462 load on guard relays. Implements proposal 221. Resolves ticket 9386.
16464 o Major features (bridges):
16465 - Don't launch pluggable transport proxies if we don't have any
16466 bridges configured that would use them. Now we can list many
16467 pluggable transports, and Tor will dynamically start one when it
16468 hears a bridge address that needs it. Resolves ticket 5018.
16469 - The bridge directory authority now assigns status flags (Stable,
16470 Guard, etc) to bridges based on thresholds calculated over all
16471 Running bridges. Now bridgedb can finally make use of its features
16472 to e.g. include at least one Stable bridge in its answers. Fixes
16475 o Major features (other):
16476 - Extend ORCONN controller event to include an "ID" parameter,
16477 and add four new controller event types CONN_BW, CIRC_BW,
16478 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
16479 The new events are emitted in private Tor networks only, with the
16480 goal of being able to better track performance and load during
16481 full-network simulations. Implements proposal 218 and ticket 7359.
16482 - On some platforms (currently: recent OSX versions, glibc-based
16483 platforms that support the ELF format, and a few other
16484 Unix-like operating systems), Tor can now dump stack traces
16485 when a crash occurs or an assertion fails. By default, traces
16486 are dumped to stderr (if possible) and to any logs that are
16487 reporting errors. Implements ticket 9299.
16490 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16491 not entirely remove it from the connection lists. Fixes bug 9602;
16492 bugfix on 0.2.4.4-alpha.
16493 - Do not treat streams that fail with reason
16494 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16495 since it could also indicate an ENETUNREACH connection error. Fixes
16496 part of bug 10777; bugfix on 0.2.4.8-alpha.
16498 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16499 - Do not allow OpenSSL engines to replace the PRNG, even when
16500 HardwareAccel is set. The only default builtin PRNG engine uses
16501 the Intel RDRAND instruction to replace the entire PRNG, and
16502 ignores all attempts to seed it with more entropy. That's
16503 cryptographically stupid: the right response to a new alleged
16504 entropy source is never to discard all previously used entropy
16505 sources. Fixes bug 10402; works around behavior introduced in
16506 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16508 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16509 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16510 - Avoid launching spurious extra circuits when a stream is pending.
16511 This fixes a bug where any circuit that _wasn't_ unusable for new
16512 streams would be treated as if it were, causing extra circuits to
16513 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16515 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16516 - No longer stop reading or writing on cpuworker connections when
16517 our rate limiting buckets go empty. Now we should handle circuit
16518 handshake requests more promptly. Resolves bug 9731.
16519 - Stop trying to bootstrap all our directory information from
16520 only our first guard. Discovered while fixing bug 9946; bugfix
16523 o Minor features (bridges, pluggable transports):
16524 - Add threshold cutoffs to the networkstatus document created by
16525 the Bridge Authority. Fixes bug 1117.
16526 - On Windows, spawn background processes using the CREATE_NO_WINDOW
16527 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
16528 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
16529 Vidalia set this option for us.) Implements ticket 10297.
16531 o Minor features (security):
16532 - Always clear OpenSSL bignums before freeing them -- even bignums
16533 that don't contain secrets. Resolves ticket 10793. Patch by
16536 o Minor features (config options and command line):
16537 - Add an --allow-missing-torrc commandline option that tells Tor to
16538 run even if the configuration file specified by -f is not available.
16539 Implements ticket 10060.
16540 - Add support for the TPROXY transparent proxying facility on Linux.
16541 See documentation for the new TransProxyType option for more
16542 details. Implementation by "thomo". Closes ticket 10582.
16544 o Minor features (controller):
16545 - Add a new "HS_DESC" controller event that reports activities
16546 related to hidden service descriptors. Resolves ticket 8510.
16547 - New "DROPGUARDS" controller command to forget all current entry
16548 guards. Not recommended for ordinary use, since replacing guards
16549 too frequently makes several attacks easier. Resolves ticket 9934;
16552 o Minor features (build):
16553 - Assume that a user using ./configure --host wants to cross-compile,
16554 and give an error if we cannot find a properly named
16555 tool-chain. Add a --disable-tool-name-check option to proceed
16556 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
16557 - If we run ./configure and the compiler recognizes -fstack-protector
16558 but the linker rejects it, warn the user about a potentially missing
16559 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
16561 o Minor features (testing):
16562 - If Python is installed, "make check" now runs extra tests beyond
16563 the unit test scripts.
16564 - When bootstrapping a test network, sometimes very few relays get
16565 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
16566 specify a set of relays which should be voted Guard regardless of
16567 their uptime or bandwidth. Addresses ticket 9206.
16569 o Minor features (log messages):
16570 - When ServerTransportPlugin is set on a bridge, Tor can write more
16571 useful statistics about bridge use in its extrainfo descriptors,
16572 but only if the Extended ORPort ("ExtORPort") is set too. Add a
16573 log message to inform the user in this case. Resolves ticket 9651.
16574 - When receiving a new controller connection, log the origin address.
16575 Resolves ticket 9698; patch from "sigpipe".
16576 - When logging OpenSSL engine status at startup, log the status of
16577 more engines. Fixes ticket 10043; patch from Joshua Datko.
16578 - Turn "circuit handshake stats since last time" log messages into a
16579 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16581 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16582 - Improve the circuit queue out-of-memory handler. Previously, when
16583 we ran low on memory, we'd close whichever circuits had the most
16584 queued cells. Now, we close those that have the *oldest* queued
16585 cells, on the theory that those are most responsible for us
16586 running low on memory. Based on analysis from a forthcoming paper
16587 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16588 - Generate bootstrapping status update events correctly when fetching
16589 microdescriptors. Fixes bug 9927.
16590 - Update to the October 2 2013 Maxmind GeoLite Country database.
16592 o Minor bugfixes (clients):
16593 - When closing a channel that has already been open, do not close
16594 pending circuits that were waiting to connect to the same relay.
16595 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
16598 o Minor bugfixes (relays):
16599 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16600 exit node as a NOROUTE error, not an INTERNAL error, since they
16601 can apparently happen when trying to connect to the wrong sort
16602 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16604 o Minor bugfixes (bridges):
16605 - Fix a bug where the first connection works to a bridge that uses a
16606 pluggable transport with client-side parameters, but we don't send
16607 the client-side parameters on subsequent connections. (We don't
16608 use any pluggable transports with client-side parameters yet,
16609 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
16610 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
16612 o Minor bugfixes (node selection):
16613 - If ExcludeNodes is set, consider non-excluded hidden service
16614 directory servers before excluded ones. Do not consider excluded
16615 hidden service directory servers at all if StrictNodes is
16616 set. (Previously, we would sometimes decide to connect to those
16617 servers, and then realize before we initiated a connection that
16618 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
16619 Reported by "mr-4".
16620 - If we set the ExitNodes option but it doesn't include any nodes
16621 that have the Exit flag, we would choose not to bootstrap. Now we
16622 bootstrap so long as ExitNodes includes nodes which can exit to
16623 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
16625 o Minor bugfixes (controller and command-line):
16626 - If changing a config option via "setconf" fails in a recoverable
16627 way, we used to nonetheless write our new control ports to the
16628 file described by the "ControlPortWriteToFile" option. Now we only
16629 write out that file if we successfully switch to the new config
16630 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
16631 - When a command-line option such as --version or --help that
16632 ordinarily implies --hush appears on the command line along with
16633 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
16634 only if it appeared later on the command line. Fixes bug 9578;
16635 bugfix on 0.2.5.1-alpha.
16637 o Minor bugfixes (code correctness):
16638 - Previously we used two temporary files when writing descriptors to
16639 disk; now we only use one. Fixes bug 1376.
16640 - Remove an erroneous (but impossible and thus harmless) pointer
16641 comparison that would have allowed compilers to skip a bounds
16642 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
16643 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
16644 - Fix an always-true assertion in pluggable transports code so it
16645 actually checks what it was trying to check. Fixes bug 10046;
16646 bugfix on 0.2.3.9-alpha. Found by "dcb".
16648 o Minor bugfixes (protocol correctness):
16649 - When receiving a VERSIONS cell with an odd number of bytes, close
16650 the connection immediately since the cell is malformed. Fixes bug
16651 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
16654 o Minor bugfixes (build):
16655 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
16656 turned off (that is, without support for v2 link handshakes). Fixes
16657 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
16658 - Fix compilation warnings and startup issues when running with
16659 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
16661 - Fix compilation on Solaris 9, which didn't like us having an
16662 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
16664 o Minor bugfixes (testing):
16665 - Fix a segmentation fault in our benchmark code when running with
16666 Fedora's OpenSSL package, or any other OpenSSL that provides
16667 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16669 o Minor bugfixes (log messages):
16670 - Fix a bug where clients using bridges would report themselves
16671 as 50% bootstrapped even without a live consensus document.
16672 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
16673 - Suppress a warning where, if there's only one directory authority
16674 in the network, we would complain that votes and signatures cannot
16675 be uploaded to other directory authorities. Fixes bug 10842;
16676 bugfix on 0.2.2.26-beta.
16677 - Report bootstrapping progress correctly when we're downloading
16678 microdescriptors. We had updated our "do we have enough microdescs
16679 to begin building circuits?" logic most recently in 0.2.4.10-alpha
16680 (see bug 5956), but we left the bootstrap status event logic at
16681 "how far through getting 1/4 of them are we?" Fixes bug 9958;
16682 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
16684 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16685 - Avoid a crash bug when starting with a corrupted microdescriptor
16686 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16687 - If we fail to dump a previously cached microdescriptor to disk, avoid
16688 freeing duplicate data later on. Fixes bug 10423; bugfix on
16689 0.2.4.13-alpha. Spotted by "bobnomnom".
16691 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16692 - Correctly log long IPv6 exit policies, instead of truncating them
16693 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16694 - Our default TLS ecdhe groups were backwards: we meant to be using
16695 P224 for relays (for performance win) and P256 for bridges (since
16696 it is more common in the wild). Instead we had it backwards. After
16697 reconsideration, we decided that the default should be P256 on all
16698 hosts, since its security is probably better, and since P224 is
16699 reportedly used quite little in the wild. Found by "skruffy" on
16700 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16701 - Free directory authority certificate download statuses on exit
16702 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16704 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16705 - If the guard we choose first doesn't answer, we would try the
16706 second guard, but once we connected to the second guard we would
16707 abandon it and retry the first one, slowing down bootstrapping.
16708 The fix is to treat all our initially chosen guards as acceptable
16709 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16710 - Fix an assertion failure that would occur when disabling the
16711 ORPort setting on a running Tor process while accounting was
16712 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16713 - When examining the list of network interfaces to find our address,
16714 do not consider non-running or disabled network interfaces. Fixes
16715 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16716 - Avoid an off-by-one error when checking buffer boundaries when
16717 formatting the exit status of a pluggable transport helper.
16718 This is probably not an exploitable bug, but better safe than
16719 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16722 o Removed code and features:
16723 - Clients now reject any directory authority certificates lacking
16724 a dir-key-crosscert element. These have been included since
16725 0.2.1.9-alpha, so there's no real reason for them to be optional
16726 any longer. Completes proposal 157. Resolves ticket 10162.
16727 - Remove all code that existed to support the v2 directory system,
16728 since there are no longer any v2 directory authorities. Resolves
16730 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
16731 options, which were used for designating authorities as "Hidden
16732 service authorities". There has been no use of hidden service
16733 authorities since 0.2.2.1-alpha, when we stopped uploading or
16734 downloading v0 hidden service descriptors. Fixes bug 10881; also
16735 part of a fix for bug 10841.
16737 o Code simplification and refactoring:
16738 - Remove some old fallback code designed to keep Tor clients working
16739 in a network with only two working relays. Elsewhere in the code we
16740 have long since stopped supporting such networks, so there wasn't
16741 much point in keeping it around. Addresses ticket 9926.
16742 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
16743 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
16744 - Remove data structures which were introduced to implement the
16745 CellStatistics option: they are now redundant with the addition
16746 of a timestamp to the regular packed_cell_t data structure, which
16747 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
16750 o Documentation (man page) fixes:
16751 - Update manpage to describe some of the files you can expect to
16752 find in Tor's DataDirectory. Addresses ticket 9839.
16753 - Document that all but one DirPort entry must have the NoAdvertise
16754 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16756 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16757 - Clarify the usage and risks of setting the ContactInfo torrc line
16758 for your relay or bridge. Resolves ticket 9854.
16759 - Add anchors to the manpage so we can link to the html version of
16760 the documentation for specific options. Resolves ticket 9866.
16761 - Replace remaining references to DirServer in man page and
16762 log entries. Resolves ticket 10124.
16765 - Make the "tor-gencert" tool used by directory authority operators
16766 create 2048-bit signing keys by default (rather than 1024-bit, since
16767 1024-bit is uncomfortably small these days). Addresses ticket 10324.
16770 Changes in version 0.2.4.20 - 2013-12-22
16771 Tor 0.2.4.20 fixes potentially poor random number generation for users
16772 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
16773 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
16774 and 4) have no state file in their DataDirectory (as would happen on
16775 first start). Users who generated relay or hidden service identity
16776 keys in such a situation should discard them and generate new ones.
16778 This release also fixes a logic error that caused Tor clients to build
16779 many more preemptive circuits than they actually need.
16782 - Do not allow OpenSSL engines to replace the PRNG, even when
16783 HardwareAccel is set. The only default builtin PRNG engine uses
16784 the Intel RDRAND instruction to replace the entire PRNG, and
16785 ignores all attempts to seed it with more entropy. That's
16786 cryptographically stupid: the right response to a new alleged
16787 entropy source is never to discard all previously used entropy
16788 sources. Fixes bug 10402; works around behavior introduced in
16789 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16791 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16792 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16793 - Avoid launching spurious extra circuits when a stream is pending.
16794 This fixes a bug where any circuit that _wasn't_ unusable for new
16795 streams would be treated as if it were, causing extra circuits to
16796 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16799 - Avoid a crash bug when starting with a corrupted microdescriptor
16800 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16801 - If we fail to dump a previously cached microdescriptor to disk, avoid
16802 freeing duplicate data later on. Fixes bug 10423; bugfix on
16803 0.2.4.13-alpha. Spotted by "bobnomnom".
16806 Changes in version 0.2.4.19 - 2013-12-11
16807 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
16808 (1986-2013). Aaron worked on diverse projects including helping to guide
16809 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
16810 transparency to the U.S government's PACER documents, and contributing
16811 design and development for Tor and Tor2Web. Aaron was one of the latest
16812 martyrs in our collective fight for civil liberties and human rights,
16813 and his death is all the more painful because he was one of us.
16815 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
16816 a new circuit handshake and link encryption that use ECC to provide
16817 better security and efficiency; makes relays better manage circuit
16818 creation requests; uses "directory guards" to reduce client enumeration
16819 risks; makes bridges collect and report statistics about the pluggable
16820 transports they support; cleans up and improves our geoip database;
16821 gets much closer to IPv6 support for clients, bridges, and relays; makes
16822 directory authorities use measured bandwidths rather than advertised
16823 ones when computing flags and thresholds; disables client-side DNS
16824 caching to reduce tracking risks; and fixes a big bug in bridge
16825 reachability testing. This release introduces two new design
16826 abstractions in the code: a new "channel" abstraction between circuits
16827 and or_connections to allow for implementing alternate relay-to-relay
16828 transports, and a new "circuitmux" abstraction storing the queue of
16829 circuits for a channel. The release also includes many stability,
16830 security, and privacy fixes.
16833 Changes in version 0.2.4.18-rc - 2013-11-16
16834 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
16835 series. It takes a variety of fixes from the 0.2.5.x branch to improve
16836 stability, performance, and better handling of edge cases.
16839 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16840 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16841 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16842 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16843 them to solve bug 6033.)
16846 - No longer stop reading or writing on cpuworker connections when
16847 our rate limiting buckets go empty. Now we should handle circuit
16848 handshake requests more promptly. Resolves bug 9731.
16849 - If we are unable to save a microdescriptor to the journal, do not
16850 drop it from memory and then reattempt downloading it. Fixes bug
16851 9645; bugfix on 0.2.2.6-alpha.
16852 - Stop trying to bootstrap all our directory information from
16853 only our first guard. Discovered while fixing bug 9946; bugfix
16855 - The new channel code sometimes lost track of in-progress circuits,
16856 causing long-running clients to stop building new circuits. The
16857 fix is to always call circuit_n_chan_done(chan, 0) from
16858 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16860 o Minor bugfixes (on 0.2.4.x):
16861 - Correctly log long IPv6 exit policies, instead of truncating them
16862 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16863 - Our default TLS ecdhe groups were backwards: we meant to be using
16864 P224 for relays (for performance win) and P256 for bridges (since
16865 it is more common in the wild). Instead we had it backwards. After
16866 reconsideration, we decided that the default should be P256 on all
16867 hosts, since its security is probably better, and since P224 is
16868 reportedly used quite little in the wild. Found by "skruffy" on
16869 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16870 - Free directory authority certificate download statuses on exit
16871 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16873 o Minor bugfixes (on 0.2.3.x and earlier):
16874 - If the guard we choose first doesn't answer, we would try the
16875 second guard, but once we connected to the second guard we would
16876 abandon it and retry the first one, slowing down bootstrapping.
16877 The fix is to treat all our initially chosen guards as acceptable
16878 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16879 - Fix an assertion failure that would occur when disabling the
16880 ORPort setting on a running Tor process while accounting was
16881 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16882 - When examining the list of network interfaces to find our address,
16883 do not consider non-running or disabled network interfaces. Fixes
16884 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16885 - Avoid an off-by-one error when checking buffer boundaries when
16886 formatting the exit status of a pluggable transport helper.
16887 This is probably not an exploitable bug, but better safe than
16888 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16891 o Minor features (protecting client timestamps):
16892 - Clients no longer send timestamps in their NETINFO cells. These were
16893 not used for anything, and they provided one small way for clients
16894 to be distinguished from each other as they moved from network to
16895 network or behind NAT. Implements part of proposal 222.
16896 - Clients now round timestamps in INTRODUCE cells down to the nearest
16897 10 minutes. If a new Support022HiddenServices option is set to 0, or
16898 if it's set to "auto" and the feature is disabled in the consensus,
16899 the timestamp is sent as 0 instead. Implements part of proposal 222.
16900 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16901 a big deal from a security point of view, but it achieves no actual
16902 good purpose, and isn't needed. Implements part of proposal 222.
16903 - Reduce down accuracy of timestamps in hidden service descriptors.
16904 Implements part of proposal 222.
16906 o Minor features (other):
16907 - Improve the circuit queue out-of-memory handler. Previously, when
16908 we ran low on memory, we'd close whichever circuits had the most
16909 queued cells. Now, we close those that have the *oldest* queued
16910 cells, on the theory that those are most responsible for us
16911 running low on memory. Based on analysis from a forthcoming paper
16912 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16913 - Generate bootstrapping status update events correctly when fetching
16914 microdescriptors. Fixes bug 9927.
16915 - Update to the October 2 2013 Maxmind GeoLite Country database.
16917 o Documentation fixes:
16918 - Clarify the usage and risks of setting the ContactInfo torrc line
16919 for your relay or bridge. Resolves ticket 9854.
16920 - Add anchors to the manpage so we can link to the html version of
16921 the documentation for specific options. Resolves ticket 9866.
16922 - Replace remaining references to DirServer in man page and
16923 log entries. Resolves ticket 10124.
16926 Changes in version 0.2.5.1-alpha - 2013-10-02
16927 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
16928 on Linux, allows bridges that offer pluggable transports to report usage
16929 statistics, fixes many issues to make testing easier, and provides
16930 a pile of minor features and bugfixes that have been waiting for a
16931 release of the new branch.
16933 This is the first alpha release in a new series, so expect there to
16934 be bugs. Users who would rather test out a more stable branch should
16935 stay with 0.2.4.x for now.
16937 o Major features (security):
16938 - Use the seccomp2 syscall filtering facility on Linux to limit
16939 which system calls Tor can invoke. This is an experimental,
16940 Linux-only feature to provide defense-in-depth against unknown
16941 attacks. To try turning it on, set "Sandbox 1" in your torrc
16942 file. Please be ready to report bugs. We hope to add support
16943 for better sandboxing in the future, including more fine-grained
16944 filters, better division of responsibility, and support for more
16945 platforms. This work has been done by Cristian-Matei Toader for
16946 Google Summer of Code.
16947 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16948 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16949 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16950 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16951 them to solve bug 6033.)
16953 o Major features (other):
16954 - Add support for passing arguments to managed pluggable transport
16955 proxies. Implements ticket 3594.
16956 - Bridges now track GeoIP information and the number of their users
16957 even when pluggable transports are in use, and report usage
16958 statistics in their extra-info descriptors. Resolves tickets 4773
16960 - Make testing Tor networks bootstrap better: lower directory fetch
16961 retry schedules and maximum interval without directory requests,
16962 and raise maximum download tries. Implements ticket 6752.
16963 - Add make target 'test-network' to run tests on a Chutney network.
16964 Implements ticket 8530.
16965 - The ntor handshake is now on-by-default, no matter what the
16966 directory authorities recommend. Implements ticket 8561.
16969 - Instead of writing destroy cells directly to outgoing connection
16970 buffers, queue them and intersperse them with other outgoing cells.
16971 This can prevent a set of resource starvation conditions where too
16972 many pending destroy cells prevent data cells from actually getting
16973 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
16974 bugfix on 0.2.0.1-alpha.
16975 - If we are unable to save a microdescriptor to the journal, do not
16976 drop it from memory and then reattempt downloading it. Fixes bug
16977 9645; bugfix on 0.2.2.6-alpha.
16978 - The new channel code sometimes lost track of in-progress circuits,
16979 causing long-running clients to stop building new circuits. The
16980 fix is to always call circuit_n_chan_done(chan, 0) from
16981 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16984 - Tor now builds each source file in two modes: a mode that avoids
16985 exposing identifiers needlessly, and another mode that exposes
16986 more identifiers for testing. This lets the compiler do better at
16987 optimizing the production code, while enabling us to take more
16988 radical measures to let the unit tests test things.
16989 - The production builds no longer include functions used only in
16990 the unit tests; all functions exposed from a module only for
16991 unit-testing are now static in production builds.
16992 - Add an --enable-coverage configuration option to make the unit
16993 tests (and a new src/or/tor-cov target) to build with gcov test
16997 - We now have rudimentary function mocking support that our unit
16998 tests can use to test functions in isolation. Function mocking
16999 lets the tests temporarily replace a function's dependencies with
17000 stub functions, so that the tests can check the function without
17001 invoking the other functions it calls.
17002 - Add more unit tests for the <circid,channel>->circuit map, and
17003 the destroy-cell-tracking code to fix bug 7912.
17004 - Unit tests for failing cases of the TAP onion handshake.
17005 - More unit tests for address-manipulation functions.
17007 o Minor features (protecting client timestamps):
17008 - Clients no longer send timestamps in their NETINFO cells. These were
17009 not used for anything, and they provided one small way for clients
17010 to be distinguished from each other as they moved from network to
17011 network or behind NAT. Implements part of proposal 222.
17012 - Clients now round timestamps in INTRODUCE cells down to the nearest
17013 10 minutes. If a new Support022HiddenServices option is set to 0, or
17014 if it's set to "auto" and the feature is disabled in the consensus,
17015 the timestamp is sent as 0 instead. Implements part of proposal 222.
17016 - Stop sending timestamps in AUTHENTICATE cells. This is not such
17017 a big deal from a security point of view, but it achieves no actual
17018 good purpose, and isn't needed. Implements part of proposal 222.
17019 - Reduce down accuracy of timestamps in hidden service descriptors.
17020 Implements part of proposal 222.
17022 o Minor features (config options):
17023 - Config (torrc) lines now handle fingerprints which are missing
17024 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
17025 - Support a --dump-config option to print some or all of the
17026 configured options. Mainly useful for debugging the command-line
17027 option parsing code. Helps resolve ticket 4647.
17028 - Raise awareness of safer logging: notify user of potentially
17029 unsafe config options, like logging more verbosely than severity
17030 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
17031 - Add a new configuration option TestingV3AuthVotingStartOffset
17032 that bootstraps a network faster by changing the timing for
17033 consensus votes. Addresses ticket 8532.
17034 - Add a new torrc option "ServerTransportOptions" that allows
17035 bridge operators to pass configuration parameters to their
17036 pluggable transports. Resolves ticket 8929.
17037 - The config (torrc) file now accepts bandwidth and space limits in
17038 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
17039 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
17042 o Minor features (build):
17043 - Add support for `--library-versions` flag. Implements ticket 6384.
17044 - Return the "unexpected sendme" warnings to a warn severity, but make
17045 them rate limited, to help diagnose ticket 8093.
17046 - Detect a missing asciidoc, and warn the user about it, during
17047 configure rather than at build time. Fixes issue 6506. Patch from
17050 o Minor features (other):
17051 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
17052 sockets in a single system call. Implements ticket 5129.
17053 - Log current accounting state (bytes sent and received + remaining
17054 time for the current accounting period) in the relay's heartbeat
17055 message. Implements ticket 5526; patch from Peter Retzlaff.
17056 - Implement the TRANSPORT_LAUNCHED control port event that
17057 notifies controllers about new launched pluggable
17058 transports. Resolves ticket 5609.
17059 - If we're using the pure-C 32-bit curve25519_donna implementation
17060 of curve25519, build it with the -fomit-frame-pointer option to
17061 make it go faster on register-starved hosts. This improves our
17062 handshake performance by about 6% on i386 hosts without nacl.
17063 Closes ticket 8109.
17064 - Update to the September 4 2013 Maxmind GeoLite Country database.
17067 - Set the listen() backlog limit to the largest actually supported
17068 on the system, not to the value in a header file. Fixes bug 9716;
17069 bugfix on every released Tor.
17070 - No longer accept malformed http headers when parsing urls from
17071 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
17072 bugfix on 0.0.6pre1.
17073 - In munge_extrainfo_into_routerinfo(), check the return value of
17074 memchr(). This would have been a serious issue if we ever passed
17075 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
17077 - On the chance that somebody manages to build Tor on a
17078 platform where time_t is unsigned, correct the way that
17079 microdesc_add_to_cache() handles negative time arguments.
17080 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
17081 - Reject relative control socket paths and emit a warning. Previously,
17082 single-component control socket paths would be rejected, but Tor
17083 would not log why it could not validate the config. Fixes bug 9258;
17084 bugfix on 0.2.3.16-alpha.
17086 o Minor bugfixes (command line):
17087 - Use a single command-line parser for parsing torrc options on the
17088 command line and for finding special command-line options to avoid
17089 inconsistent behavior for torrc option arguments that have the same
17090 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
17092 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
17093 9573; bugfix on 0.0.9pre5.
17095 o Minor fixes (build, auxiliary programs):
17096 - Stop preprocessing the "torify" script with autoconf, since
17097 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
17099 - The tor-fw-helper program now follows the standard convention and
17100 exits with status code "0" on success. Fixes bug 9030; bugfix on
17101 0.2.3.1-alpha. Patch by Arlo Breault.
17102 - Corrected ./configure advice for what openssl dev package you should
17103 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
17105 o Minor code improvements:
17106 - Remove constants and tests for PKCS1 padding; it's insecure and
17107 shouldn't be used for anything new. Fixes bug 8792; patch
17109 - Remove instances of strcpy() from the unit tests. They weren't
17110 hurting anything, since they were only in the unit tests, but it's
17111 embarrassing to have strcpy() in the code at all, and some analysis
17112 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
17113 0.2.3.8-alpha. Patch from Arlo Breault.
17115 o Removed features:
17116 - Remove migration code from when we renamed the "cached-routers"
17117 file to "cached-descriptors" back in 0.2.0.8-alpha. This
17118 incidentally resolves ticket 6502 by cleaning up the related code
17119 a bit. Patch from Akshay Hebbar.
17121 o Code simplification and refactoring:
17122 - Extract the common duplicated code for creating a subdirectory
17123 of the data directory and writing to a file in it. Fixes ticket
17124 4282; patch from Peter Retzlaff.
17125 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
17126 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
17127 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
17128 - Add a set of accessor functions for the circuit timeout data
17129 structure. Fixes ticket 6153; patch from "piet".
17130 - Clean up exit paths from connection_listener_new(). Closes ticket
17131 8789. Patch from Arlo Breault.
17132 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
17133 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
17134 - Use a doubly-linked list to implement the global circuit list.
17135 Resolves ticket 9108. Patch from Marek Majkowski.
17136 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
17139 Changes in version 0.2.4.17-rc - 2013-09-05
17140 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
17141 series. It adds an emergency step to help us tolerate the massive
17142 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
17143 circuit-level handshakes now effectively jump the queue compared to
17144 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
17145 big bug hindering bridge reachability tests.
17148 - Relays now process the new "NTor" circuit-level handshake requests
17149 with higher priority than the old "TAP" circuit-level handshake
17150 requests. We still process some TAP requests to not totally starve
17151 0.2.3 clients when NTor becomes popular. A new consensus parameter
17152 "NumNTorsPerTAP" lets us tune the balance later if we need to.
17153 Implements ticket 9574.
17156 - If the circuit build timeout logic is disabled (via the consensus,
17157 or because we are an authority), then don't build testing circuits.
17158 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
17159 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
17160 previously they did not, which prevented them from receiving
17161 successful connections from relays for self-test or bandwidth
17162 testing. Also, when a relay is extending a circuit to a bridge,
17163 it needs to send a NETINFO cell, even when the bridge hasn't sent
17164 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
17165 - If the time to download the next old-style networkstatus is in
17166 the future, do not decline to consider whether to download the
17167 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
17171 - Avoid double-closing the listener socket in our socketpair()
17172 replacement (used on Windows) in the case where the addresses on
17173 our opened sockets don't match what we expected. Fixes bug 9400;
17174 bugfix on 0.0.2pre7. Found by Coverity.
17176 o Minor fixes (config options):
17177 - Avoid overflows when the user sets MaxCircuitDirtiness to a
17178 ridiculously high value, by imposing a (ridiculously high) 30-day
17179 maximum on MaxCircuitDirtiness.
17180 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
17181 message is logged at notice, not at info.
17182 - Warn and fail if a server is configured not to advertise any
17183 ORPorts at all. (We need *something* to put in our descriptor,
17184 or we just won't work.)
17187 - Track how many "TAP" and "NTor" circuit handshake requests we get,
17188 and how many we complete, and log it every hour to help relay
17189 operators follow trends in network load. Addresses ticket 9658.
17190 - Update to the August 7 2013 Maxmind GeoLite Country database.
17193 Changes in version 0.2.4.16-rc - 2013-08-10
17194 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
17195 series. It fixes several crash bugs in the 0.2.4 branch.
17198 - Fix a bug in the voting algorithm that could yield incorrect results
17199 when a non-naming authority declared too many flags. Fixes bug 9200;
17200 bugfix on 0.2.0.3-alpha.
17201 - Fix an uninitialized read that could in some cases lead to a remote
17202 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
17203 Anybody running a hidden service on the experimental 0.2.4.x
17204 branch should upgrade. (This is, so far as we know, unrelated to
17206 - Avoid an assertion failure when processing DNS replies without the
17207 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
17208 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
17209 0.2.4.15-rc. Found by stem integration tests.
17212 - Fix an invalid memory read that occurred when a pluggable
17213 transport proxy failed its configuration protocol.
17214 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
17215 - When evaluating whether to use a connection that we haven't
17216 decided is canonical using a recent link protocol version,
17217 decide that it's canonical only if it used address _does_
17218 match the desired address. Fixes bug 9309; bugfix on
17219 0.2.4.4-alpha. Reported by skruffy.
17220 - Make the default behavior of NumDirectoryGuards be to track
17221 NumEntryGuards. Now a user who changes only NumEntryGuards will get
17222 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
17223 - Fix a spurious compilation warning with some older versions of
17224 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
17227 - Update to the July 3 2013 Maxmind GeoLite Country database.
17230 Changes in version 0.2.4.15-rc - 2013-07-01
17231 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
17232 series. It fixes a few smaller bugs, but generally appears stable.
17233 Please test it and let us know whether it is!
17236 - When receiving a new configuration file via the control port's
17237 LOADCONF command, do not treat the defaults file as absent.
17238 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
17241 - Issue a warning when running with the bufferevents backend enabled.
17242 It's still not stable, and people should know that they're likely
17243 to hit unexpected problems. Closes ticket 9147.
17246 Changes in version 0.2.4.14-alpha - 2013-06-18
17247 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
17248 present in 0.2.4.13-alpha.
17251 - When we have too much memory queued in circuits (according to a new
17252 MaxMemInCellQueues option), close the circuits consuming the most
17253 memory. This prevents us from running out of memory as a relay if
17254 circuits fill up faster than they can be drained. Fixes bug 9063;
17255 bugfix on the 54th commit of Tor. This bug is a further fix beyond
17256 bug 6252, whose fix was merged into 0.2.3.21-rc.
17258 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
17259 where we tried to solve this issue simply by imposing an upper limit
17260 on the number of queued cells for a single circuit. That approach
17261 proved to be problematic, since there are ways to provoke clients to
17262 send a number of cells in excess of any such reasonable limit. Fixes
17263 bug 9072; bugfix on 0.2.4.13-alpha.
17265 - Limit hidden service descriptors to at most ten introduction
17266 points, to slow one kind of guard enumeration. Fixes bug 9002;
17267 bugfix on 0.1.1.11-alpha.
17270 Changes in version 0.2.4.13-alpha - 2013-06-14
17271 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
17272 vulnerabilities, makes socks5 username/password circuit isolation
17273 actually actually work (this time for sure!), and cleans up a bunch
17274 of other issues in preparation for a release candidate.
17276 o Major bugfixes (robustness):
17277 - Close any circuit that has too many cells queued on it. Fixes
17278 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
17279 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
17280 - Prevent the get_freelists() function from running off the end of
17281 the list of freelists if it somehow gets an unrecognized
17282 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
17284 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
17285 when an exit connection with optimistic data succeeds immediately
17286 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
17288 - Fix a directory authority crash bug when building a consensus
17289 using an older consensus as its basis. Fixes bug 8833. Bugfix
17293 - Avoid a memory leak where we would leak a consensus body when we
17294 find that a consensus which we couldn't previously verify due to
17295 missing certificates is now verifiable. Fixes bug 8719; bugfix
17297 - We used to always request authority certificates by identity digest,
17298 meaning we'd get the newest one even when we wanted one with a
17299 different signing key. Then we would complain about being given
17300 a certificate we already had, and never get the one we really
17301 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
17302 resource to request the one we want. Fixes bug 5595; bugfix on
17304 - Follow the socks5 protocol when offering username/password
17305 authentication. The fix for bug 8117 exposed this bug, and it
17306 turns out real-world applications like Pidgin do care. Bugfix on
17307 0.2.3.2-alpha; fixes bug 8879.
17308 - Prevent failures on Windows Vista and later when rebuilding the
17309 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
17310 bugfix on 0.2.4.12-alpha.
17313 - Fix an impossible buffer overrun in the AES unit tests. Fixes
17314 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
17315 - If for some reason we fail to write a microdescriptor while
17316 rebuilding the cache, do not let the annotations from that
17317 microdescriptor linger in the cache file, and do not let the
17318 microdescriptor stay recorded as present in its old location.
17319 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
17320 - Fix a memory leak that would occur whenever a configuration
17321 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
17322 - Paste the description for PathBias parameters from the man
17323 page into or.h, so the code documents them too. Fixes bug 7982;
17324 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
17325 - Relays now treat a changed IPv6 ORPort as sufficient reason to
17326 publish an updated descriptor. Fixes bug 6026; bugfix on
17328 - When launching a resolve request on behalf of an AF_UNIX control
17329 socket, omit the address field of the new entry connection, used in
17330 subsequent controller events, rather than letting tor_dup_addr()
17331 set it to "<unknown address type>". Fixes bug 8639; bugfix on
17334 o Minor bugfixes (log messages):
17335 - Fix a scaling issue in the path bias accounting code that
17336 resulted in "Bug:" log messages from either
17337 pathbias_scale_close_rates() or pathbias_count_build_success().
17338 This represents a bugfix on a previous bugfix: the original fix
17339 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
17341 - Give a less useless error message when the user asks for an IPv4
17342 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
17346 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
17347 to tolerate bug 8093 for now.
17348 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
17349 in directory authority votes to describe whether they have enough
17350 measured bandwidths to ignore advertised (relay descriptor)
17351 bandwidth claims. Resolves ticket 8711.
17352 - Update to the June 5 2013 Maxmind GeoLite Country database.
17354 o Removed documentation:
17355 - Remove some of the older contents of doc/ as obsolete; move others
17356 to torspec.git. Fixes bug 8965.
17358 o Code simplification and refactoring:
17359 - Avoid using character buffers when constructing most directory
17360 objects: this approach was unwieldy and error-prone. Instead,
17361 build smartlists of strings, and concatenate them when done.
17364 Changes in version 0.2.4.12-alpha - 2013-04-18
17365 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
17366 process for lengthening the guard rotation period, makes directory
17367 authority opinions in the consensus a bit less gameable, makes socks5
17368 username/password circuit isolation actually work, and fixes a wide
17369 variety of other issues.
17372 - Raise the default time that a client keeps an entry guard from
17373 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
17374 2012 paper. (We would make it even longer, but we need better client
17375 load balancing first.) Also, make the guard lifetime controllable
17376 via a new GuardLifetime torrc option and a GuardLifetime consensus
17377 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
17378 - Directory authorities now prefer using measured bandwidths to
17379 advertised ones when computing flags and thresholds. Resolves
17381 - Directory authorities that have more than a threshold number
17382 of relays with measured bandwidths now treat relays with unmeasured
17383 bandwidths as having bandwidth 0. Resolves ticket 8435.
17385 o Major bugfixes (assert / resource use):
17386 - Avoid a bug where our response to TLS renegotiation under certain
17387 network conditions could lead to a busy-loop, with 100% CPU
17388 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
17389 - Avoid an assertion when we discover that we'd like to write a cell
17390 onto a closing connection: just discard the cell. Fixes another
17391 case of bug 7350; bugfix on 0.2.4.4-alpha.
17393 o Major bugfixes (client-side privacy):
17394 - When we mark a circuit as unusable for new circuits, have it
17395 continue to be unusable for new circuits even if MaxCircuitDirtiness
17396 is increased too much at the wrong time, or the system clock jumps
17397 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
17398 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
17399 which have resolved to internal addresses") is set, apply that
17400 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
17401 - When an exit relay rejects a stream with reason "exit policy", but
17402 we only know an exit policy summary (e.g. from the microdesc
17403 consensus) for it, do not mark the relay as useless for all exiting.
17404 Instead, mark just the circuit as unsuitable for that particular
17405 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
17406 - Allow applications to get proper stream isolation with
17407 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
17408 username/password authentication also offer "no authentication". Tor
17409 had previously preferred "no authentication", so the applications
17410 never actually sent Tor their auth details. Now Tor selects
17411 username/password authentication if it's offered. You can disable
17412 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
17413 bug 8117; bugfix on 0.2.3.3-alpha.
17415 o Major bugfixes (other):
17416 - When unable to find any working directory nodes to use as a
17417 directory guard, give up rather than adding the same non-working
17418 nodes to the directory guard list over and over. Fixes bug 8231;
17419 bugfix on 0.2.4.8-alpha.
17422 - Reject as invalid most directory objects containing a NUL.
17423 Belt-and-suspender fix for bug 8037.
17424 - In our testsuite, create temporary directories with a bit more
17425 entropy in their name to make name collisions less likely. Fixes
17427 - Add CACHED keyword to ADDRMAP events in the control protocol
17428 to indicate whether a DNS result will be cached or not. Resolves
17430 - Update to the April 3 2013 Maxmind GeoLite Country database.
17432 o Minor features (build):
17433 - Detect and reject attempts to build Tor with threading support
17434 when OpenSSL has been compiled without threading support.
17436 - Clarify that when autoconf is checking for nacl, it is checking
17437 specifically for nacl with a fast curve25519 implementation.
17439 - Warn if building on a platform with an unsigned time_t: there
17440 are too many places where Tor currently assumes that time_t can
17441 hold negative values. We'd like to fix them all, but probably
17444 o Minor bugfixes (build):
17445 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
17446 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
17447 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
17448 - Add the old src/or/micro-revision.i filename to CLEANFILES.
17449 On the off chance that somebody has one, it will go away as soon
17450 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
17451 - Build Tor correctly on 32-bit platforms where the compiler can build
17452 but not run code using the "uint128_t" construction. Fixes bug 8587;
17453 bugfix on 0.2.4.8-alpha.
17454 - Fix compilation warning with some versions of clang that would
17455 prefer the -Wswitch-enum compiler flag to warn about switch
17456 statements with missing enum values, even if those switch
17457 statements have a "default:" statement. Fixes bug 8598; bugfix
17460 o Minor bugfixes (protocol):
17461 - Fix the handling of a TRUNCATE cell when it arrives while the
17462 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
17463 - Fix a misframing issue when reading the version numbers in a
17464 VERSIONS cell. Previously we would recognize [00 01 00 02] as
17465 'version 1, version 2, and version 0x100', when it should have
17466 only included versions 1 and 2. Fixes bug 8059; bugfix on
17467 0.2.0.10-alpha. Reported pseudonymously.
17468 - Make the format and order of STREAM events for DNS lookups
17469 consistent among the various ways to launch DNS lookups. Fixes
17470 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
17471 - Correct our check for which versions of Tor support the EXTEND2
17472 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
17473 later, when support was really added in version 0.2.4.8-alpha.
17474 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
17476 o Minor bugfixes (other):
17477 - Correctly store microdescriptors and extrainfo descriptors with
17478 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
17479 Bug reported by "cypherpunks".
17480 - Increase the width of the field used to remember a connection's
17481 link protocol version to two bytes. Harmless for now, since the
17482 only currently recognized versions are one byte long. Reported
17483 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
17484 - If the state file's path bias counts are invalid (presumably from a
17485 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
17486 additional checks and log messages to the scaling of Path Bias
17487 counts, in case there still are remaining issues with scaling.
17488 Should help resolve bug 8235.
17489 - Eliminate several instances where we use "Nickname=ID" to refer to
17490 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
17491 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
17492 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
17494 o Minor bugfixes (syscalls):
17495 - Always check the return values of functions fcntl() and
17496 setsockopt(). We don't believe these are ever actually failing in
17497 practice, but better safe than sorry. Also, checking these return
17498 values should please analysis tools like Coverity. Patch from
17499 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
17500 - Use direct writes rather than stdio when building microdescriptor
17501 caches, in an attempt to mitigate bug 8031, or at least make it
17504 o Minor bugfixes (config):
17505 - When rejecting a configuration because we were unable to parse a
17506 quoted string, log an actual error message. Fixes bug 7950; bugfix
17508 - Behave correctly when the user disables LearnCircuitBuildTimeout
17509 but doesn't tell us what they would like the timeout to be. Fixes
17510 bug 6304; bugfix on 0.2.2.14-alpha.
17511 - When autodetecting the number of CPUs, use the number of available
17512 CPUs in preference to the number of configured CPUs. Inform the
17513 user if this reduces the number of available CPUs. Fixes bug 8002;
17514 bugfix on 0.2.3.1-alpha.
17515 - Make it an error when you set EntryNodes but disable UseGuardNodes,
17516 since it will (surprisingly to some users) ignore EntryNodes. Fixes
17517 bug 8180; bugfix on 0.2.3.11-alpha.
17518 - Allow TestingTorNetworks to override the 4096-byte minimum for
17519 the Fast threshold. Otherwise they can't bootstrap until they've
17520 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
17521 - Fix some logic errors when the user manually overrides the
17522 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
17525 o Minor bugfixes (log messages to help diagnose bugs):
17526 - If we fail to free a microdescriptor because of bug 7164, log
17527 the filename and line number from which we tried to free it.
17528 - Add another diagnostic to the heartbeat message: track and log
17529 overhead that TLS is adding to the data we write. If this is
17530 high, we are sending too little data to SSL_write at a time.
17531 Diagnostic for bug 7707.
17532 - Add more detail to a log message about relaxed timeouts, to help
17534 - Warn more aggressively when flushing microdescriptors to a
17535 microdescriptor cache fails, in an attempt to mitigate bug 8031,
17536 or at least make it more diagnosable.
17537 - Improve debugging output to help track down bug 8185 ("Bug:
17538 outgoing relay cell has n_chan==NULL. Dropping.")
17539 - Log the purpose of a path-bias testing circuit correctly.
17540 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
17542 o Minor bugfixes (0.2.4.x log messages that were too noisy):
17543 - Don't attempt to relax the timeout of already opened 1-hop circuits.
17544 They might never timeout. This should eliminate some/all cases of
17545 the relaxed timeout log message.
17546 - Use circuit creation time for network liveness evaluation. This
17547 should eliminate warning log messages about liveness caused
17548 by changes in timeout evaluation. Fixes bug 6572; bugfix on
17550 - Reduce a path bias length check from notice to info. The message
17551 is triggered when creating controller circuits. Fixes bug 8196;
17552 bugfix on 0.2.4.8-alpha.
17553 - Fix a path state issue that triggered a notice during relay startup.
17554 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
17555 - Reduce occurrences of warns about circuit purpose in
17556 connection_ap_expire_building(). Fixes bug 8477; bugfix on
17559 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
17560 - If we encounter a write failure on a SOCKS connection before we
17561 finish our SOCKS handshake, don't warn that we closed the
17562 connection before we could send a SOCKS reply. Fixes bug 8427;
17563 bugfix on 0.1.0.1-rc.
17564 - Correctly recognize that [::1] is a loopback address. Fixes
17565 bug 8377; bugfix on 0.2.1.3-alpha.
17566 - Fix a directory authority warn caused when we have a large amount
17567 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
17568 - Don't log inappropriate heartbeat messages when hibernating: a
17569 hibernating node is _expected_ to drop out of the consensus,
17570 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
17571 bugfix on 0.2.3.1-alpha.
17572 - Don't complain about bootstrapping problems while hibernating.
17573 These complaints reflect a general code problem, but not one
17574 with any problematic effects (no connections are actually
17575 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
17577 o Documentation fixes:
17578 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
17579 names match. Fixes bug 7768.
17580 - Make the torify manpage no longer refer to tsocks; torify hasn't
17581 supported tsocks since 0.2.3.14-alpha.
17582 - Make the tor manpage no longer reference tsocks.
17583 - Fix the GeoIPExcludeUnknown documentation to refer to
17584 ExcludeExitNodes rather than the currently nonexistent
17585 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
17588 - The tor-tsocks.conf is no longer distributed or installed. We
17589 recommend that tsocks users use torsocks instead. Resolves
17593 Changes in version 0.2.4.11-alpha - 2013-03-11
17594 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
17595 more robust, makes hidden service authentication work again, and
17596 resolves a DPI fingerprint for Tor's SSL transport.
17598 o Major features (directory authorities):
17599 - Directory authorities now support a new consensus method (17)
17600 where they cap the published bandwidth of servers for which
17601 insufficient bandwidth measurements exist. Fixes part of bug 2286.
17602 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
17603 serve any v2 directory information. Now we can test disabling the
17604 old deprecated v2 directory format, and see whether doing so has
17605 any effect on network load. Begins to fix bug 6783.
17606 - Directory authorities now include inside each vote a statement of
17607 the performance thresholds they used when assigning flags.
17608 Implements ticket 8151.
17610 o Major bugfixes (directory authorities):
17611 - Stop marking every relay as having been down for one hour every
17612 time we restart a directory authority. These artificial downtimes
17613 were messing with our Stable and Guard flag calculations. Fixes
17614 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
17616 o Major bugfixes (hidden services):
17617 - Allow hidden service authentication to succeed again. When we
17618 refactored the hidden service introduction code back
17619 in 0.2.4.1-alpha, we didn't update the code that checks
17620 whether authentication information is present, causing all
17621 authentication checks to return "false". Fix for bug 8207; bugfix
17622 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
17624 o Minor features (relays, bridges):
17625 - Make bridge relays check once a minute for whether their IP
17626 address has changed, rather than only every 15 minutes. Resolves
17627 bugs 1913 and 1992.
17628 - Refactor resolve_my_address() so it returns the method by which we
17629 decided our public IP address (explicitly configured, resolved from
17630 explicit hostname, guessed from interfaces, learned by gethostname).
17631 Now we can provide more helpful log messages when a relay guesses
17632 its IP address incorrectly (e.g. due to unexpected lines in
17633 /etc/hosts). Resolves ticket 2267.
17634 - Teach bridge-using clients to avoid 0.2.2 bridges when making
17635 microdescriptor-related dir requests, and only fall back to normal
17636 descriptors if none of their bridges can handle microdescriptors
17637 (as opposed to the fix in ticket 4013, which caused them to fall
17638 back to normal descriptors if *any* of their bridges preferred
17639 them). Resolves ticket 4994.
17640 - Randomize the lifetime of our SSL link certificate, so censors can't
17641 use the static value for filtering Tor flows. Resolves ticket 8443;
17642 related to ticket 4014 which was included in 0.2.2.33.
17643 - Support a new version of the link protocol that allows 4-byte circuit
17644 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
17645 a possible resource exhaustion issue. Closes ticket 7351; implements
17648 o Minor features (portability):
17649 - Tweak the curve25519-donna*.c implementations to tolerate systems
17650 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
17651 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
17652 the signs of types during autoconf. This is better than our old
17653 approach, which didn't work when cross-compiling.
17654 - Detect the sign of enum values, rather than assuming that MSC is the
17655 only compiler where enum types are all signed. Fixes bug 7727;
17656 bugfix on 0.2.4.10-alpha.
17658 o Minor features (other):
17659 - Say "KBytes" rather than "KB" in the man page (for various values
17660 of K), to further reduce confusion about whether Tor counts in
17661 units of memory or fractions of units of memory. Resolves ticket 7054.
17662 - Clear the high bit on curve25519 public keys before passing them to
17663 our backend, in case we ever wind up using a backend that doesn't do
17664 so itself. If we used such a backend, and *didn't* clear the high bit,
17665 we could wind up in a situation where users with such backends would
17666 be distinguishable from users without. Fixes bug 8121; bugfix on
17668 - Update to the March 6 2013 Maxmind GeoLite Country database.
17670 o Minor bugfixes (clients):
17671 - When we receive a RELAY_END cell with the reason DONE, or with no
17672 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
17673 status as "connection refused". Previously we reported these cases
17674 as success but then immediately closed the connection. Fixes bug
17675 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
17676 - Downgrade an assertion in connection_ap_expire_beginning to an
17677 LD_BUG message. The fix for bug 8024 should prevent this message
17678 from displaying, but just in case, a warn that we can diagnose
17679 is better than more assert crashes. Fixes bug 8065; bugfix on
17681 - Lower path use bias thresholds to .80 for notice and .60 for warn.
17682 Also make the rate limiting flags for the path use bias log messages
17683 independent from the original path bias flags. Fixes bug 8161;
17684 bugfix on 0.2.4.10-alpha.
17686 o Minor bugfixes (relays):
17687 - Stop trying to resolve our hostname so often (e.g. every time we
17688 think about doing a directory fetch). Now we reuse the cached
17689 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
17690 and 2410 (bugfix on 0.1.2.2-alpha).
17691 - Stop sending a stray "(null)" in some cases for the server status
17692 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
17694 - When choosing which stream on a formerly stalled circuit to wake
17695 first, make better use of the platform's weak RNG. Previously,
17696 we had been using the % ("modulo") operator to try to generate a
17697 1/N chance of picking each stream, but this behaves badly with
17698 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
17700 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
17701 Irix's random() only return 15 bits; Solaris's random() returns more
17702 bits but its RAND_MAX says it only returns 15, and so on. Motivated
17703 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
17705 o Minor bugfixes (directory authorities):
17706 - Directory authorities now use less space when formatting identical
17707 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
17710 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
17711 - Avoid leaking memory if we fail to compute a consensus signature
17712 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
17713 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
17715 - Fix a memory leak during safe-cookie controller authentication.
17716 Bugfix on 0.2.3.13-alpha.
17717 - Avoid memory leak of IPv6 policy content if we fail to format it into
17718 a router descriptor. Bugfix on 0.2.4.7-alpha.
17720 o Minor bugfixes (other code correctness issues):
17721 - Avoid a crash if we fail to generate an extrainfo descriptor.
17722 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
17723 this is CID 718634.
17724 - When detecting the largest possible file descriptor (in order to
17725 close all file descriptors when launching a new program), actually
17726 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
17727 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
17729 - Fix a copy-and-paste error when adding a missing A1 to a routerset
17730 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
17731 Bugfix on 0.2.4.10-alpha.
17732 - Fix an impossible-to-trigger integer overflow when estimating how
17733 long our onionskin queue would take. (This overflow would require us
17734 to accept 4 million onionskins before processing 100 of them.) Fixes
17735 bug 8210; bugfix on 0.2.4.10-alpha.
17737 o Code simplification and refactoring:
17738 - Add a wrapper function for the common "log a message with a
17742 Changes in version 0.2.4.10-alpha - 2013-02-04
17743 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
17744 certain attacks that flood the network with relays; changes the queue
17745 for circuit create requests from a sized-based limit to a time-based
17746 limit; resumes building with MSVC on Windows; and fixes a wide variety
17749 o Major bugfixes (directory authority):
17750 - When computing directory thresholds, ignore any rejected-as-sybil
17751 nodes during the computation so that they can't influence Fast,
17752 Guard, etc. (We should have done this for proposal 109.) Fixes
17754 - When marking a node as a likely sybil, reset its uptime metrics
17755 to zero, so that it cannot time towards getting marked as Guard,
17756 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
17760 - When a TLS write is partially successful but incomplete, remember
17761 that the flushed part has been flushed, and notice that bytes were
17762 actually written. Reported and fixed pseudonymously. Fixes bug
17763 7708; bugfix on Tor 0.1.0.5-rc.
17764 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
17765 ID: these could be used to create unexpected streams and circuits
17766 which would count as "present" to some parts of Tor but "absent"
17767 to others, leading to zombie circuits and streams or to a bandwidth
17768 denial-of-service. Fixes bug 7889; bugfix on every released version
17769 of Tor. Reported by "oftc_must_be_destroyed".
17770 - Rename all macros in our local copy of queue.h to begin with "TOR_".
17771 This change seems the only good way to permanently prevent conflicts
17772 with queue.h on various operating systems. Fixes bug 8107; bugfix
17775 o Major features (relay):
17776 - Instead of limiting the number of queued onionskins (aka circuit
17777 create requests) to a fixed, hard-to-configure number, we limit
17778 the size of the queue based on how many we expect to be able to
17779 process in a given amount of time. We estimate the time it will
17780 take to process an onionskin based on average processing time
17781 of previous onionskins. Closes ticket 7291. You'll never have to
17782 configure MaxOnionsPending again.
17784 o Major features (portability):
17785 - Resume building correctly with MSVC and Makefile.nmake. This patch
17786 resolves numerous bugs and fixes reported by ultramage, including
17787 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
17788 - Make the ntor and curve25519 code build correctly with MSVC.
17789 Fix on 0.2.4.8-alpha.
17792 - When directory authorities are computing thresholds for flags,
17793 never let the threshold for the Fast flag fall below 4096
17794 bytes. Also, do not consider nodes with extremely low bandwidths
17795 when deciding thresholds for various directory flags. This change
17796 should raise our threshold for Fast relays, possibly in turn
17797 improving overall network performance; see ticket 1854. Resolves
17799 - The Tor client now ignores sub-domain components of a .onion
17800 address. This change makes HTTP "virtual" hosting
17801 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
17802 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
17803 hosted on the same hidden service. Implements proposal 204.
17804 - We compute the overhead from passing onionskins back and forth to
17805 cpuworkers, and report it when dumping statistics in response to
17806 SIGUSR1. Supports ticket 7291.
17808 o Minor features (path selection):
17809 - When deciding whether we have enough descriptors to build circuits,
17810 instead of looking at raw relay counts, look at which fraction
17811 of (bandwidth-weighted) paths we're able to build. This approach
17812 keeps clients from building circuits if their paths are likely to
17813 stand out statistically. The default fraction of paths needed is
17814 taken from the consensus directory; you can override it with the
17815 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
17816 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
17817 and we have GeoIP information, also exclude all nodes with unknown
17818 countries "??" and "A1". This behavior is controlled by the
17819 new GeoIPExcludeUnknown option: you can make such nodes always
17820 excluded with "GeoIPExcludeUnknown 1", and disable the feature
17821 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
17822 gets you the default behavior. Implements feature 7706.
17823 - Path Use Bias: Perform separate accounting for successful circuit
17824 use. Keep separate statistics on stream attempt rates versus stream
17825 success rates for each guard. Provide configurable thresholds to
17826 determine when to emit log messages or disable use of guards that
17827 fail too many stream attempts. Resolves ticket 7802.
17829 o Minor features (log messages):
17830 - When learning a fingerprint for a bridge, log its corresponding
17831 transport type. Implements ticket 7896.
17832 - Improve the log message when "Bug/attack: unexpected sendme cell
17833 from client" occurs, to help us track bug 8093.
17836 - Remove a couple of extraneous semicolons that were upsetting the
17837 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
17838 bugfix on 0.2.2.1-alpha.
17839 - Remove a source of rounding error during path bias count scaling;
17840 don't count cannibalized circuits as used for path bias until we
17841 actually try to use them; and fix a circuit_package_relay_cell()
17842 warning message about n_chan==NULL. Fixes bug 7802.
17843 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
17844 actually link against nacl when we're configured to use it. Fixes
17845 bug 7972; bugfix on 0.2.4.8-alpha.
17846 - Compile correctly with the --disable-curve25519 option. Fixes
17847 bug 8153; bugfix on 0.2.4.8-alpha.
17849 o Build improvements:
17850 - Do not report status verbosely from autogen.sh unless the -v flag
17851 is specified. Fixes issue 4664. Patch from Onizuka.
17852 - Replace all calls to snprintf() outside of src/ext with
17853 tor_snprintf(). Also remove the #define to replace snprintf with
17854 _snprintf on Windows; they have different semantics, and all of
17855 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
17856 - Try to detect if we are ever building on a platform where
17857 memset(...,0,...) does not set the value of a double to 0.0. Such
17858 platforms are permitted by the C standard, though in practice
17859 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
17860 currently support them, but it's better to detect them and fail
17861 than to perform erroneously.
17863 o Removed features:
17864 - Stop exporting estimates of v2 and v3 directory traffic shares
17865 in extrainfo documents. They were unneeded and sometimes inaccurate.
17866 Also stop exporting any v2 directory request statistics. Resolves
17868 - Drop support for detecting and warning about versions of Libevent
17869 before 1.3e. Nothing reasonable ships with them any longer;
17870 warning the user about them shouldn't be needed. Resolves ticket
17873 o Code simplifications and refactoring:
17874 - Rename "isin" functions to "contains", for grammar. Resolves
17876 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
17877 with the natural logarithm function from the system libm. Resolves
17881 Changes in version 0.2.4.9-alpha - 2013-01-15
17882 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
17883 work more robustly.
17886 - Fix backward compatibility logic when receiving an embedded ntor
17887 handshake tunneled in a CREATE cell. This clears up the "Bug:
17888 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
17892 Changes in version 0.2.4.8-alpha - 2013-01-14
17893 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
17894 risks, adds a new stronger and faster circuit handshake, and offers
17895 stronger and faster link encryption when both sides support it.
17898 - Preliminary support for directory guards (proposal 207): when
17899 possible, clients now use their entry guards for non-anonymous
17900 directory requests. This can help prevent client enumeration. Note
17901 that this behavior only works when we have a usable consensus
17902 directory, and when options about what to download are more or less
17903 standard. In the future we should re-bootstrap from our guards,
17904 rather than re-bootstrapping from the preconfigured list of
17905 directory sources that ships with Tor. Resolves ticket 6526.
17906 - Tor relays and clients now support a better CREATE/EXTEND cell
17907 format, allowing the sender to specify multiple address, identity,
17908 and handshake types. Implements Robert Ransom's proposal 200;
17909 closes ticket 7199.
17911 o Major features (new circuit handshake):
17912 - Tor now supports a new circuit extension handshake designed by Ian
17913 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
17914 circuit extension handshake, later called "TAP", was a bit slow
17915 (especially on the relay side), had a fragile security proof, and
17916 used weaker keys than we'd now prefer. The new circuit handshake
17917 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
17918 function, making it significantly more secure than the older
17919 handshake, and significantly faster. Tor can use one of two built-in
17920 pure-C curve25519-donna implementations by Adam Langley, or it
17921 can link against the "nacl" library for a tuned version if present.
17923 The built-in version is very fast for 64-bit systems when building
17924 with GCC. The built-in 32-bit version is still faster than the
17925 old TAP protocol, but using libnacl is better on most such hosts.
17927 Clients don't currently use this protocol by default, since
17928 comparatively few clients support it so far. To try it, set
17929 UseNTorHandshake to 1.
17931 Implements proposal 216; closes ticket 7202.
17933 o Major features (better link encryption):
17934 - Relays can now enable the ECDHE TLS ciphersuites when available
17935 and appropriate. These ciphersuites let us negotiate forward-secure
17936 TLS secret keys more safely and more efficiently than with our
17937 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
17938 public relays prefer the (faster) P224 group, and bridges prefer
17939 the (more common) P256 group; you can override this with the
17942 Enabling these ciphers was a little tricky, since for a long time,
17943 clients had been claiming to support them without actually doing
17944 so, in order to foil fingerprinting. But with the client-side
17945 implementation of proposal 198 in 0.2.3.17-beta, clients can now
17946 match the ciphers from recent Firefox versions *and* list the
17947 ciphers they actually mean, so relays can believe such clients
17948 when they advertise ECDHE support in their TLS ClientHello messages.
17950 This feature requires clients running 0.2.3.17-beta or later,
17951 and requires both sides to be running OpenSSL 1.0.0 or later
17952 with ECC support. OpenSSL 1.0.1, with the compile-time option
17953 "enable-ec_nistp_64_gcc_128", is highly recommended.
17955 Implements the relay side of proposal 198; closes ticket 7200.
17958 - Avoid crashing when, as a relay without IPv6-exit support, a
17959 client insists on getting an IPv6 address or nothing. Fixes bug
17960 7814; bugfix on 0.2.4.7-alpha.
17963 - Improve circuit build timeout handling for hidden services.
17964 In particular: adjust build timeouts more accurately depending
17965 upon the number of hop-RTTs that a particular circuit type
17966 undergoes. Additionally, launch intro circuits in parallel
17967 if they timeout, and take the first one to reply as valid.
17968 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
17969 separate error codes; or at least, don't break for that reason.
17970 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
17971 - Update to the January 2 2013 Maxmind GeoLite Country database.
17973 o Minor features (testing):
17974 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
17975 (P-256) Diffie-Hellman handshakes to src/or/bench.
17976 - Add benchmark functions to test onion handshake performance.
17978 o Minor features (path bias detection):
17979 - Alter the Path Bias log messages to be more descriptive in terms
17980 of reporting timeouts and other statistics.
17981 - Create three levels of Path Bias log messages, as opposed to just
17982 two. These are configurable via consensus as well as via the torrc
17983 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
17984 The default values are 0.70, 0.50, and 0.30 respectively.
17985 - Separate the log message levels from the decision to drop guards,
17986 which also is available via torrc option PathBiasDropGuards.
17987 PathBiasDropGuards still defaults to 0 (off).
17988 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
17989 in combination with PathBiasExtremeRate.
17990 - Increase the default values for PathBiasScaleThreshold and
17991 PathBiasCircThreshold from (200, 20) to (300, 150).
17992 - Add in circuit usage accounting to path bias. If we try to use a
17993 built circuit but fail for any reason, it counts as path bias.
17994 Certain classes of circuits where the adversary gets to pick your
17995 destination node are exempt from this accounting. Usage accounting
17996 can be specifically disabled via consensus parameter or torrc.
17997 - Convert all internal path bias state to double-precision floating
17998 point, to avoid roundoff error and other issues.
17999 - Only record path bias information for circuits that have completed
18000 *two* hops. Assuming end-to-end tagging is the attack vector, this
18001 makes us more resilient to ambient circuit failure without any
18002 detection capability loss.
18004 o Minor bugfixes (log messages):
18005 - Rate-limit the "No circuits are opened. Relaxed timeout for a
18006 circuit with channel state open..." message to once per hour to
18007 keep it from filling the notice logs. Mitigates bug 7799 but does
18008 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
18009 - Avoid spurious warnings when configuring multiple client ports of
18010 which only some are nonlocal. Previously, we had claimed that some
18011 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
18014 o Code simplifications and refactoring:
18015 - Get rid of a couple of harmless clang warnings, where we compared
18016 enums to ints. These warnings are newly introduced in clang 3.2.
18017 - Split the onion.c file into separate modules for the onion queue
18018 and the different handshakes it supports.
18019 - Remove the marshalling/unmarshalling code for sending requests to
18020 cpuworkers over a socket, and instead just send structs. The
18021 recipient will always be the same Tor binary as the sender, so
18022 any encoding is overkill.
18025 Changes in version 0.2.4.7-alpha - 2012-12-24
18026 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
18027 directory mirrors for more robust bootstrapping; fixes more issues where
18028 clients with changing network conditions refuse to make any circuits;
18029 adds initial support for exiting to IPv6 addresses; resumes being able
18030 to update our GeoIP database, and includes the geoip6 file this time;
18031 turns off the client-side DNS cache by default due to privacy risks;
18032 and fixes a variety of other issues.
18034 o Major features (client resilience):
18035 - Add a new "FallbackDir" torrc option to use when we can't use
18036 a directory mirror from the consensus (either because we lack a
18037 consensus, or because they're all down). Currently, all authorities
18038 are fallbacks by default, and there are no other default fallbacks,
18039 but that will change. This option will allow us to give clients a
18040 longer list of servers to try to get a consensus from when first
18041 connecting to the Tor network, and thereby reduce load on the
18042 directory authorities. Implements proposal 206, "Preconfigured
18043 directory sources for bootstrapping". We also removed the old
18044 "FallbackNetworkstatus" option, since we never got it working well
18045 enough to use it. Closes bug 572.
18046 - If we have no circuits open, use a relaxed timeout (the
18047 95-percentile cutoff) until a circuit succeeds. This heuristic
18048 should allow Tor to succeed at building circuits even when the
18049 network connection drastically changes. Should help with bug 3443.
18051 o Major features (IPv6):
18052 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
18053 connectivity, then set the IPv6Exit flag to 1. Also make sure your
18054 exit policy reads as you would like: the address * applies to all
18055 address families, whereas *4 is IPv4 address only, and *6 is IPv6
18056 addresses only. On the client side, you'll need to wait until the
18057 authorities have upgraded, wait for enough exits to support IPv6,
18058 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
18059 ticket 5547, implements proposal 117 as revised in proposal 208.
18061 We DO NOT recommend that clients with actual anonymity needs start
18062 using IPv6 over Tor yet, since not enough exits support it yet.
18064 o Major features (geoip database):
18065 - Maxmind began labelling Tor relays as being in country "A1",
18066 which breaks by-country node selection inside Tor. Now we use a
18067 script to replace "A1" ("Anonymous Proxy") entries in our geoip
18068 file with real country codes. This script fixes about 90% of "A1"
18069 entries automatically and uses manual country code assignments to
18070 fix the remaining 10%. See src/config/README.geoip for details.
18071 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
18072 Country database, as modified above.
18074 o Major bugfixes (client-side DNS):
18075 - Turn off the client-side DNS cache by default. Updating and using
18076 the DNS cache is now configurable on a per-client-port
18077 level. SOCKSPort, DNSPort, etc lines may now contain
18078 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
18079 cache these types of DNS answers when we receive them from an
18080 exit node in response to an application request on this port, and
18081 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
18082 cached DNS answers of these types, we shouldn't use them. It's
18083 potentially risky to use cached DNS answers at the client, since
18084 doing so can indicate to one exit what answers we've gotten
18085 for DNS lookups in the past. With IPv6, this becomes especially
18086 problematic. Using cached DNS answers for requests on the same
18087 circuit would present less linkability risk, since all traffic
18088 on a circuit is already linkable, but it would also provide
18089 little performance benefit: the exit node caches DNS replies
18090 too. Implements a simplified version of Proposal 205. Implements
18093 o Major bugfixes (other):
18094 - Alter circuit build timeout measurement to start at the point
18095 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
18096 initialization). This should make our timeout measurements more
18097 uniform. Previously, we were sometimes including ORconn setup time
18098 in our circuit build time measurements. Should resolve bug 3443.
18099 - Fix an assertion that could trigger in hibernate_go_dormant() when
18100 closing an or_connection_t: call channel_mark_for_close() rather
18101 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
18103 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
18104 7655; bugfix on 0.2.4.6-alpha.
18107 - Add a new torrc option "ServerTransportListenAddr" to let bridge
18108 operators select the address where their pluggable transports will
18109 listen for connections. Resolves ticket 7013.
18110 - Allow an optional $ before the node identity digest in the
18111 controller command GETINFO ns/id/<identity>, for consistency with
18112 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
18113 - Log packaged cell fullness as part of the heartbeat message.
18114 Diagnosis to try to determine the extent of bug 7743.
18116 o Minor features (IPv6):
18117 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
18118 prefer to hand out virtual IPv6 addresses, since there are more of
18119 them and we can't run out. To override this behavior and make IPv4
18120 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
18121 or DNSPort you're using for resolving. Implements ticket 7571.
18122 - AutomapHostsOnResolve responses are now randomized, to avoid
18123 annoying situations where Tor is restarted and applications
18124 connect to the wrong addresses.
18125 - Never try more than 1000 times to pick a new virtual address when
18126 AutomapHostsOnResolve is set. That's good enough so long as we
18127 aren't close to handing out our entire virtual address space;
18128 if you're getting there, it's best to switch to IPv6 virtual
18132 - The ADDRMAP command can no longer generate an ill-formed error
18133 code on a failed MAPADDRESS. It now says "internal" rather than
18134 an English sentence fragment with spaces in the middle. Bugfix on
18135 Tor 0.2.0.19-alpha.
18136 - Fix log messages and comments to avoid saying "GMT" when we mean
18137 "UTC". Fixes bug 6113.
18138 - Compile on win64 using mingw64. Fixes bug 7260; patches from
18140 - Fix a crash when debugging unit tests on Windows: deallocate a
18141 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
18142 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
18145 - The DirServer option is now DirAuthority, for consistency with
18146 current naming patterns. You can still use the old DirServer form.
18148 o Code simplification and refactoring:
18149 - Move the client-side address-map/virtual-address/DNS-cache code
18150 out of connection_edge.c into a new addressmap.c module.
18151 - Remove unused code for parsing v1 directories and "running routers"
18152 documents. Fixes bug 6887.
18155 Changes in version 0.2.3.25 - 2012-11-19
18156 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
18157 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
18158 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
18159 programmer, and friend. Unstinting in his dedication to the cause of
18160 freedom, he inspired and helped many of us as we began our work on
18161 anonymity, and inspires us still. Please honor his memory by writing
18162 software to protect people's freedoms, and by helping others to do so.
18164 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
18165 significantly reduced directory overhead (via microdescriptors),
18166 enormous crypto performance improvements for fast relays on new
18167 enough hardware, a new v3 TLS handshake protocol that can better
18168 resist fingerprinting, support for protocol obfuscation plugins (aka
18169 pluggable transports), better scalability for hidden services, IPv6
18170 support for bridges, performance improvements like allowing clients
18171 to skip the first round-trip on the circuit ("optimistic data") and
18172 refilling token buckets more often, a new "stream isolation" design
18173 to isolate different applications on different circuits, and many
18174 stability, security, and privacy fixes.
18177 - Tor tries to wipe potentially sensitive data after using it, so
18178 that if some subsequent security failure exposes Tor's memory,
18179 the damage will be limited. But we had a bug where the compiler
18180 was eliminating these wipe operations when it decided that the
18181 memory was no longer visible to a (correctly running) program,
18182 hence defeating our attempt at defense in depth. We fix that
18183 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18184 is unlikely to optimize away. Future versions of Tor may use
18185 a less ridiculously heavy approach for this. Fixes bug 7352.
18186 Reported in an article by Andrey Karpov.
18189 - Fix a harmless bug when opting against publishing a relay descriptor
18190 because DisableNetwork is set. Fixes bug 7464; bugfix on
18194 Changes in version 0.2.4.6-alpha - 2012-11-13
18195 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
18196 makes our defense-in-depth memory wiping more reliable, and begins to
18197 count IPv6 addresses in bridge statistics,
18200 - Fix an assertion failure that could occur when closing a connection
18201 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
18203 - Tor tries to wipe potentially sensitive data after using it, so
18204 that if some subsequent security failure exposes Tor's memory,
18205 the damage will be limited. But we had a bug where the compiler
18206 was eliminating these wipe operations when it decided that the
18207 memory was no longer visible to a (correctly running) program,
18208 hence defeating our attempt at defense in depth. We fix that
18209 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18210 is unlikely to optimize away. Future versions of Tor may use
18211 a less ridiculously heavy approach for this. Fixes bug 7352.
18212 Reported in an article by Andrey Karpov.
18215 - Add GeoIP database for IPv6 addresses. The new config option
18217 - Bridge statistics now count bridge clients connecting over IPv6:
18218 bridge statistics files now list "bridge-ip-versions" and
18219 extra-info documents list "geoip6-db-digest". The control protocol
18220 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
18221 implementation by "shkoo", addressing ticket 5055.
18224 - Warn when we are binding low ports when hibernation is enabled;
18225 previously we had warned when we were _advertising_ low ports with
18226 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
18227 - Fix a harmless bug when opting against publishing a relay descriptor
18228 because DisableNetwork is set. Fixes bug 7464; bugfix on
18230 - Add warning message when a managed proxy dies during configuration.
18231 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
18232 - Fix a linking error when building tor-fw-helper without miniupnp.
18233 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
18234 - Check for closing an or_connection_t without going through correct
18235 channel functions; emit a warning and then call
18236 connection_or_close_for_error() so we don't assert as in bugs 7212
18238 - Compile correctly on compilers without C99 designated initializer
18239 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
18240 - Avoid a possible assert that can occur when channel_send_destroy() is
18241 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
18242 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
18243 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
18244 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
18245 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
18247 o Code simplification and refactoring:
18248 - Start using OpenBSD's implementation of queue.h, so that we don't
18249 need to hand-roll our own pointer and list structures whenever we
18250 need them. (We can't rely on a sys/queue.h, since some operating
18251 systems don't have them, and the ones that do have them don't all
18252 present the same extensions.)
18255 Changes in version 0.2.4.5-alpha - 2012-10-25
18256 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
18257 two important security vulnerabilities that could lead to remotely
18258 triggerable relay crashes, fix a major bug that was preventing clients
18259 from choosing suitable exit nodes, and refactor some of our code.
18261 o Major bugfixes (security, also in 0.2.3.24-rc):
18262 - Fix a group of remotely triggerable assertion failures related to
18263 incorrect link protocol negotiation. Found, diagnosed, and fixed
18264 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18266 - Fix a denial of service attack by which any directory authority
18267 could crash all the others, or by which a single v2 directory
18268 authority could crash everybody downloading v2 directory
18269 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18271 o Major bugfixes (also in 0.2.3.24-rc):
18272 - When parsing exit policy summaries from microdescriptors, we had
18273 previously been ignoring the last character in each one, so that
18274 "accept 80,443,8080" would be treated by clients as indicating
18275 a node that allows access to ports 80, 443, and 808. That would
18276 lead to clients attempting connections that could never work,
18277 and ignoring exit nodes that would support their connections. Now
18278 clients parse these exit policy summaries correctly. Fixes bug 7192;
18279 bugfix on 0.2.3.1-alpha.
18281 o Minor bugfixes (also in 0.2.3.24-rc):
18282 - Clients now consider the ClientRejectInternalAddresses config option
18283 when using a microdescriptor consensus stanza to decide whether
18284 an exit relay would allow exiting to an internal address. Fixes
18285 bug 7190; bugfix on 0.2.3.1-alpha.
18288 - Only disable TLS session ticket support when running as a TLS
18289 server. Now clients will blend better with regular Firefox
18290 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
18292 o Code simplification and refactoring:
18293 - Start using OpenBSD's implementation of queue.h (originally by
18295 - Move the entry node code from circuitbuild.c to its own file.
18296 - Move the circuit build timeout tracking code from circuitbuild.c
18300 Changes in version 0.2.3.24-rc - 2012-10-25
18301 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
18302 could lead to remotely triggerable relay crashes, and fixes
18303 a major bug that was preventing clients from choosing suitable exit
18306 o Major bugfixes (security):
18307 - Fix a group of remotely triggerable assertion failures related to
18308 incorrect link protocol negotiation. Found, diagnosed, and fixed
18309 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18311 - Fix a denial of service attack by which any directory authority
18312 could crash all the others, or by which a single v2 directory
18313 authority could crash everybody downloading v2 directory
18314 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18317 - When parsing exit policy summaries from microdescriptors, we had
18318 previously been ignoring the last character in each one, so that
18319 "accept 80,443,8080" would be treated by clients as indicating
18320 a node that allows access to ports 80, 443, and 808. That would
18321 lead to clients attempting connections that could never work,
18322 and ignoring exit nodes that would support their connections. Now
18323 clients parse these exit policy summaries correctly. Fixes bug 7192;
18324 bugfix on 0.2.3.1-alpha.
18327 - Clients now consider the ClientRejectInternalAddresses config option
18328 when using a microdescriptor consensus stanza to decide whether
18329 an exit relay would allow exiting to an internal address. Fixes
18330 bug 7190; bugfix on 0.2.3.1-alpha.
18333 Changes in version 0.2.4.4-alpha - 2012-10-20
18334 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
18335 vulnerability introduced by a change in OpenSSL, fixes a remotely
18336 triggerable assert, and adds new channel_t and circuitmux_t abstractions
18337 that will make it easier to test new connection transport and cell
18338 scheduling algorithms.
18340 o New directory authorities (also in 0.2.3.23-rc):
18341 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18342 authority. Closes ticket 5749.
18344 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
18345 - Disable TLS session tickets. OpenSSL's implementation was giving
18346 our TLS session keys the lifetime of our TLS context objects, when
18347 perfect forward secrecy would want us to discard anything that
18348 could decrypt a link connection as soon as the link connection
18349 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18350 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18351 - Discard extraneous renegotiation attempts once the V3 link
18352 protocol has been initiated. Failure to do so left us open to
18353 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18354 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18356 o Internal abstraction features:
18357 - Introduce new channel_t abstraction between circuits and
18358 or_connection_t to allow for implementing alternate OR-to-OR
18359 transports. A channel_t is an abstract object which can either be a
18360 cell-bearing channel, which is responsible for authenticating and
18361 handshaking with the remote OR and transmitting cells to and from
18362 it, or a listening channel, which spawns new cell-bearing channels
18363 at the request of remote ORs. Implements part of ticket 6465.
18364 - Also new is the channel_tls_t subclass of channel_t, adapting it
18365 to the existing or_connection_t code. The V2/V3 protocol handshaking
18366 code which formerly resided in command.c has been moved below the
18367 channel_t abstraction layer and may be found in channeltls.c now.
18368 Implements the rest of ticket 6465.
18369 - Introduce new circuitmux_t storing the queue of circuits for
18370 a channel; this encapsulates and abstracts the queue logic and
18371 circuit selection policy, and allows the latter to be overridden
18372 easily by switching out a policy object. The existing EWMA behavior
18373 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
18375 o Required libraries:
18376 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
18377 strongly recommended.
18380 - Warn users who run hidden services on a Tor client with
18381 UseEntryGuards disabled that their hidden services will be
18382 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
18383 attack which motivated Tor to support entry guards in the first
18384 place). Resolves ticket 6889.
18385 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
18386 dhill. Resolves ticket 6982.
18387 - Option OutboundBindAddress can be specified multiple times and
18388 accepts IPv6 addresses. Resolves ticket 6876.
18390 o Minor bugfixes (also in 0.2.3.23-rc):
18391 - Don't serve or accept v2 hidden service descriptors over a
18392 relay's DirPort. It's never correct to do so, and disabling it
18393 might make it more annoying to exploit any bugs that turn up in the
18394 descriptor-parsing code. Fixes bug 7149.
18395 - Fix two cases in src/or/transports.c where we were calling
18396 fmt_addr() twice in a parameter list. Bug found by David
18397 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18398 - Fix memory leaks whenever we logged any message about the "path
18399 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18400 - When relays refuse a "create" cell because their queue of pending
18401 create cells is too big (typically because their cpu can't keep up
18402 with the arrival rate), send back reason "resource limit" rather
18403 than reason "internal", so network measurement scripts can get a
18404 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
18407 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
18408 - Free some more still-in-use memory at exit, to make hunting for
18409 memory leaks easier. Resolves bug 7029.
18410 - When a Tor client gets a "truncated" relay cell, the first byte of
18411 its payload specifies why the circuit was truncated. We were
18412 ignoring this 'reason' byte when tearing down the circuit, resulting
18413 in the controller not being told why the circuit closed. Now we
18414 pass the reason from the truncated cell to the controller. Bugfix
18415 on 0.1.2.3-alpha; fixes bug 7039.
18416 - Downgrade "Failed to hand off onionskin" messages to "debug"
18417 severity, since they're typically redundant with the "Your computer
18418 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
18419 - Make clients running with IPv6 bridges connect over IPv6 again,
18420 even without setting new config options ClientUseIPv6 and
18421 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
18422 - Use square brackets around IPv6 addresses in numerous places
18423 that needed them, including log messages, HTTPS CONNECT proxy
18424 requests, TransportProxy statefile entries, and pluggable transport
18425 extra-info lines. Fixes bug 7011; patch by David Fifield.
18427 o Code refactoring and cleanup:
18428 - Source files taken from other packages now reside in src/ext;
18429 previously they were scattered around the rest of Tor.
18430 - Avoid use of reserved identifiers in our C code. The C standard
18431 doesn't like us declaring anything that starts with an
18432 underscore, so let's knock it off before we get in trouble. Fix
18433 for bug 1031; bugfix on the first Tor commit.
18436 Changes in version 0.2.3.23-rc - 2012-10-20
18437 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
18438 vulnerability introduced by a change in OpenSSL, and fixes a variety
18439 of smaller bugs in preparation for the release.
18441 o New directory authorities:
18442 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18443 authority. Closes ticket 5749.
18445 o Major bugfixes (security/privacy):
18446 - Disable TLS session tickets. OpenSSL's implementation was giving
18447 our TLS session keys the lifetime of our TLS context objects, when
18448 perfect forward secrecy would want us to discard anything that
18449 could decrypt a link connection as soon as the link connection
18450 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18451 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18452 - Discard extraneous renegotiation attempts once the V3 link
18453 protocol has been initiated. Failure to do so left us open to
18454 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18455 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18458 - Fix a possible crash bug when checking for deactivated circuits
18459 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18460 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18462 o Minor bugfixes (on 0.2.3.x):
18463 - Fix two cases in src/or/transports.c where we were calling
18464 fmt_addr() twice in a parameter list. Bug found by David
18465 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18466 - Convert an assert in the pathbias code to a log message. The assert
18467 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18468 bugfix on 0.2.3.17-beta.
18469 - Fix memory leaks whenever we logged any message about the "path
18470 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18472 o Minor bugfixes (on 0.2.2.x and earlier):
18473 - Don't serve or accept v2 hidden service descriptors over a relay's
18474 DirPort. It's never correct to do so, and disabling it might
18475 make it more annoying to exploit any bugs that turn up in the
18476 descriptor-parsing code. Fixes bug 7149.
18477 - When relays refuse a "create" cell because their queue of pending
18478 create cells is too big (typically because their cpu can't keep up
18479 with the arrival rate), send back reason "resource limit" rather
18480 than reason "internal", so network measurement scripts can get a
18481 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
18482 - Correct file sizes when reading binary files on Cygwin, to avoid
18483 a bug where Tor would fail to read its state file. Fixes bug 6844;
18484 bugfix on 0.1.2.7-alpha.
18485 - Avoid undefined behavior when parsing the list of supported
18486 rendezvous/introduction protocols in a hidden service descriptor.
18487 Previously, Tor would have confused (as-yet-unused) protocol version
18488 numbers greater than 32 with lower ones on many platforms. Fixes
18489 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18491 o Documentation fixes:
18492 - Clarify that hidden services are TCP only. Fixes bug 6024.
18495 Changes in version 0.2.4.3-alpha - 2012-09-22
18496 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
18497 assertion, resumes letting relays test reachability of their DirPort,
18498 and cleans up a bunch of smaller bugs.
18501 - Fix an assertion failure in tor_timegm() that could be triggered
18502 by a badly formatted directory object. Bug found by fuzzing with
18503 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18506 - Fix a possible crash bug when checking for deactivated circuits
18507 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18508 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18509 - Allow routers to detect that their own DirPorts are running. When
18510 we removed support for versions_supports_begindir, we also
18511 accidentally removed the mechanism we used to self-test our
18512 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
18513 bugfix on 0.2.4.2-alpha.
18515 o Security features:
18516 - Switch to a completely time-invariant approach for picking nodes
18517 weighted by bandwidth. Our old approach would run through the
18518 part of the loop after it had made its choice slightly slower
18519 than it ran through the part of the loop before it had made its
18520 choice. Addresses ticket 6538.
18521 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
18522 by tor2web clients allows hidden services to identify tor2web
18523 clients through their repeated selection of the same rendezvous
18524 and introduction point circuit endpoints (their guards). Resolves
18528 - Enable Tor to read configuration, state, and key information from
18529 a FIFO. Previously Tor would only read from files with a positive
18530 stat.st_size. Code from meejah; fixes bug 6044.
18533 - Correct file sizes when reading binary files on Cygwin, to avoid
18534 a bug where Tor would fail to read its state file. Fixes bug 6844;
18535 bugfix on 0.1.2.7-alpha.
18536 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
18537 bugfix on 0.2.0.3-alpha.
18538 - When complaining about a client port on a public address, log
18539 which address we're complaining about. Fixes bug 4020; bugfix on
18540 0.2.3.3-alpha. Patch by Tom Fitzhenry.
18541 - Convert an assert in the pathbias code to a log message. The assert
18542 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18543 bugfix on 0.2.3.17-beta.
18544 - Our new buildsystem was overzealous about rebuilding manpages: it
18545 would rebuild them all whenever any one of them changed. Now our
18546 dependency checking should be correct. Fixes bug 6843; bugfix on
18548 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
18549 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
18550 - Correct log printout about which address family is preferred
18551 when connecting to a bridge with both an IPv4 and IPv6 OR port.
18552 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
18554 o Minor bugfixes (code cleanliness):
18555 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
18556 with large values. This situation was untriggered, but nevertheless
18557 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
18558 - Reject consensus votes with more than 64 known-flags. We aren't even
18559 close to that limit yet, and our code doesn't handle it correctly.
18560 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
18561 - Avoid undefined behavior when parsing the list of supported
18562 rendezvous/introduction protocols in a hidden service descriptor.
18563 Previously, Tor would have confused (as-yet-unused) protocol version
18564 numbers greater than 32 with lower ones on many platforms. Fixes
18565 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18566 - Fix handling of rendezvous client authorization types over 8.
18567 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
18568 - Fix building with older versions of GCC (2.95, for one) that don't
18569 like preprocessor directives inside macro arguments. Found by
18570 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
18571 - Switch weighted node selection rule from using a list of doubles
18572 to using a list of int64_t. This change should make the process
18573 slightly easier to debug and maintain. Needed to finish ticket 6538.
18575 o Code simplification and refactoring:
18576 - Move the generic "config" code into a new file, and have "config.c"
18577 hold only torrc- and state-related code. Resolves ticket 6823.
18578 - Move the core of our "choose a weighted element at random" logic
18579 into its own function, and give it unit tests. Now the logic is
18580 testable, and a little less fragile too.
18581 - Removed the testing_since field of node_t, which hasn't been used
18582 for anything since 0.2.0.9-alpha.
18584 o Documentation fixes:
18585 - Clarify that hidden services are TCP only. Fixes bug 6024.
18586 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
18590 Changes in version 0.2.3.22-rc - 2012-09-11
18591 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
18595 - Fix an assertion failure in tor_timegm() that could be triggered
18596 by a badly formatted directory object. Bug found by fuzzing with
18597 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18600 - Avoid segfault when starting up having run with an extremely old
18601 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18605 Changes in version 0.2.2.39 - 2012-09-11
18606 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
18610 - Fix an assertion failure in tor_timegm() that could be triggered
18611 by a badly formatted directory object. Bug found by fuzzing with
18612 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18613 - Do not crash when comparing an address with port value 0 to an
18614 address policy. This bug could have been used to cause a remote
18615 assertion failure by or against directory authorities, or to
18616 allow some applications to crash clients. Fixes bug 6690; bugfix
18620 Changes in version 0.2.4.2-alpha - 2012-09-10
18621 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
18622 raises the default rate limiting even more, and makes the bootstrapping
18623 log messages less noisy.
18626 - Automatically forward the TCP ports of pluggable transport
18627 proxies using tor-fw-helper if PortForwarding is enabled. Implements
18631 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
18632 to 1GB/1GB. The previous defaults were intended to be "basically
18633 infinite", but it turns out they're now limiting our 100mbit+
18634 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
18635 last time we raised it).
18638 - Detect when we're running with a version of OpenSSL other than the
18639 one we compiled with. This has occasionally given people hard-to-
18641 - Log fewer lines at level "notice" about our OpenSSL and Libevent
18642 versions and capabilities when everything is going right. Resolves
18643 part of ticket 6736.
18644 - Directory authorities no long accept descriptors for any version of
18645 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
18646 These versions are insecure, unsupported, or both. Implements
18650 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
18651 to start with a triple-underscore so the controller won't touch it.
18652 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
18653 - Avoid segfault when starting up having run with an extremely old
18654 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18656 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
18657 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
18658 - Don't follow the NULL pointer if microdescriptor generation fails.
18659 (This does not appear to be triggerable, but it's best to be safe.)
18660 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
18661 - Fix mis-declared dependencies on src/common/crypto.c and
18662 src/or/tor_main.c that could break out-of-tree builds under some
18663 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
18664 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
18665 6778; bugfix on 0.2.4.1-alpha.
18666 - Fix a harmless (in this case) build warning for implicitly
18667 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
18669 o Removed features:
18670 - Now that all versions before 0.2.2.x are disallowed, we no longer
18671 need to work around their missing features. Thus we can remove a
18672 bunch of compatibility code.
18674 o Code refactoring:
18675 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
18676 TCP ports to forward. In the past it only accepted two ports:
18677 the ORPort and the DirPort.
18680 Changes in version 0.2.4.1-alpha - 2012-09-05
18681 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
18682 bridgedb; lets relays use IPv6 addresses and directory authorities
18683 advertise them; and switches to a cleaner build interface.
18685 This is the first alpha release in a new series, so expect there to
18686 be bugs. Users who would rather test out a more stable branch should
18687 stay with 0.2.3.x for now.
18689 o Major features (bridges):
18690 - Bridges now report the pluggable transports they support to the
18691 bridge authority, so it can pass the supported transports on to
18692 bridgedb and/or eventually do reachability testing. Implements
18695 o Major features (IPv6):
18696 - Bridge authorities now accept IPv6 bridge addresses and include
18697 them in network status documents. Implements ticket 5534.
18698 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
18699 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
18700 to happen. Implements ticket 5535.
18701 - All kind of relays, not just bridges, can now advertise an IPv6
18702 OR port. Implements ticket 6362.
18703 - Directory authorities vote on IPv6 OR ports using the new consensus
18704 method 14. Implements ticket 6363.
18706 o Major features (build):
18707 - Switch to a nonrecursive Makefile structure. Now instead of each
18708 Makefile.am invoking other Makefile.am's, there is a master
18709 Makefile.am that includes the others. This change makes our build
18710 process slightly more maintainable, and improves parallelism for
18711 building with make -j. Original patch by Stewart Smith; various
18712 fixes by Jim Meyering.
18713 - Where available, we now use automake's "silent" make rules by
18714 default, so that warnings are easier to spot. You can get the old
18715 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
18717 o Minor features (code security and spec conformance):
18718 - Clear keys and key-derived material left on the stack in
18719 rendservice.c and rendclient.c. Check return value of
18720 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
18721 These fixes should make us more forward-secure against cold-boot
18722 attacks and the like. Fixes bug 2385.
18723 - Reject EXTEND cells sent to nonexistent streams. According to the
18724 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
18725 we were only checking for stream IDs that were currently in use.
18726 Found while hunting for more instances of bug 6271. Bugfix on
18727 0.0.2pre8, which introduced incremental circuit construction.
18729 o Minor features (streamlining);
18730 - No longer include the "opt" prefix when generating routerinfos
18731 or v2 directories: it has been needless since Tor 0.1.2. Closes
18733 - Remove some now-needless code that tried to aggressively flush
18734 OR connections as data was added to them. Since 0.2.0.1-alpha, our
18735 cell queue logic has saved us from the failure mode that this code
18736 was supposed to prevent. Removing this code will limit the number
18737 of baroque control flow paths through Tor's network logic. Reported
18738 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
18740 o Minor features (controller):
18741 - Add a "GETINFO signal/names" control port command. Implements
18743 - Provide default values for all options via "GETINFO config/defaults".
18744 Implements ticket 4971.
18746 o Minor features (IPv6):
18747 - New config option "AuthDirHasIPv6Connectivity 1" that directory
18748 authorities should set if they have IPv6 connectivity and want to
18749 do reachability tests for IPv6 relays. Implements feature 5974.
18750 - A relay with an IPv6 OR port now sends that address in NETINFO
18751 cells (in addition to its other address). Implements ticket 6364.
18753 o Minor features (log messages):
18754 - Omit the first heartbeat log message, because it never has anything
18755 useful to say, and it clutters up the bootstrapping messages.
18756 Resolves ticket 6758.
18757 - Don't log about reloading the microdescriptor cache at startup. Our
18758 bootstrap warnings are supposed to tell the user when there's a
18759 problem, and our bootstrap notices say when there isn't. Resolves
18760 ticket 6759; bugfix on 0.2.2.6-alpha.
18761 - Don't log "I learned some more directory information" when we're
18762 reading cached directory information. Reserve it for when new
18763 directory information arrives in response to a fetch. Resolves
18765 - Prevent rounding error in path bias counts when scaling
18766 them down, and use the correct scale factor default. Also demote
18767 some path bias related log messages down a level and make others
18768 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
18769 - We no longer warn so much when generating manpages from their
18772 o Code simplifications and refactoring:
18773 - Enhance our internal sscanf replacement so that we can eliminate
18774 the last remaining uses of the system sscanf. (Though those uses
18775 of sscanf were safe, sscanf itself is generally error prone, so
18776 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
18778 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
18779 - Move last_reachable and testing_since from routerinfo_t to node_t.
18780 Implements ticket 5529.
18781 - Add replaycache_t structure, functions and unit tests, then refactor
18782 rend_service_introduce() to be more clear to read, improve, debug,
18783 and test. Resolves bug 6177.
18784 - Finally remove support for malloc_good_size and malloc_usable_size.
18785 We had hoped that these functions would let us eke a little more
18786 memory out of our malloc implementation. Unfortunately, the only
18787 implementations that provided these functions are also ones that
18788 are already efficient about not overallocation: they never got us
18789 more than 7 or so bytes per allocation. Removing them saves us a
18790 little code complexity and a nontrivial amount of build complexity.
18792 o New requirements:
18793 - Tor maintainers now require Automake version 1.9 or later to build
18794 Tor from the Git repository. (Automake is not required when building
18795 from a source distribution.)
18798 Changes in version 0.2.3.21-rc - 2012-09-05
18799 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
18800 series. It fixes a trio of potential security bugs, fixes a bug where
18801 we were leaving some of the fast relays out of the microdescriptor
18802 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
18803 and cleans up other smaller issues.
18805 o Major bugfixes (security):
18806 - Tear down the circuit if we get an unexpected SENDME cell. Clients
18807 could use this trick to make their circuits receive cells faster
18808 than our flow control would have allowed, or to gum up the network,
18809 or possibly to do targeted memory denial-of-service attacks on
18810 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
18811 from July 2002, before the release of Tor 0.0.0. We had committed
18812 this patch previously, but we had to revert it because of bug 6271.
18813 Now that 6271 is fixed, this patch appears to work.
18814 - Reject any attempt to extend to an internal address. Without
18815 this fix, a router could be used to probe addresses on an internal
18816 network to see whether they were accepting connections. Fixes bug
18817 6710; bugfix on 0.0.8pre1.
18818 - Do not crash when comparing an address with port value 0 to an
18819 address policy. This bug could have been used to cause a remote
18820 assertion failure by or against directory authorities, or to
18821 allow some applications to crash clients. Fixes bug 6690; bugfix
18825 - Remove the upper bound on microdescriptor length. We were hitting
18826 the limit for routers with complex exit policies or family
18827 declarations, causing clients to not use them. Fixes the first
18828 piece of bug 6404; fix on 0.2.2.6-alpha.
18829 - Detect "ORPort 0" as meaning, uniformly, that we're not running
18830 as a relay. Previously, some of our code would treat the presence
18831 of any ORPort line as meaning that we should act like a relay,
18832 even though our new listener code would correctly not open any
18833 ORPorts for ORPort 0. Similar bugs in other Port options are also
18834 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
18837 - Avoid a pair of double-free and use-after-mark bugs that can
18838 occur with certain timings in canceled and re-received DNS
18839 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
18840 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
18841 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
18842 - Allow one-hop directory fetching circuits the full "circuit build
18843 timeout" period, rather than just half of it, before failing them
18844 and marking the relay down. This fix should help reduce cases where
18845 clients declare relays (or worse, bridges) unreachable because
18846 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
18847 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
18849 - Authorities no longer include any router in their microdescriptor
18850 consensuses for which they couldn't generate or agree on a
18851 microdescriptor. Fixes the second piece of bug 6404; fix on
18853 - Detect and reject attempts to specify both "FooPort" and
18854 "FooPort 0" in the same configuration domain. (It's still okay
18855 to have a FooPort in your configuration file, and use "FooPort 0"
18856 on the command line to disable it.) Fixes the second half of bug
18857 6507; bugfix on 0.2.3.3-alpha.
18858 - Make wildcarded addresses (that is, ones beginning with "*.") work
18859 when provided via the controller's MapAddress command. Previously,
18860 they were accepted, but we never actually noticed that they were
18861 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
18862 - Avoid crashing on a malformed state file where EntryGuardPathBias
18863 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
18864 - Add a (probably redundant) memory clear between iterations of
18865 the router status voting loop, to prevent future coding errors
18866 where data might leak between iterations of the loop. Resolves
18869 o Minor bugfixes (log messages):
18870 - Downgrade "set buildtimeout to low value" messages to "info"
18871 severity; they were never an actual problem, there was never
18872 anything reasonable to do about them, and they tended to spam logs
18873 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
18874 - Downgrade path-bias warning messages to "info". We'll try to get
18875 them working better in 0.2.4. Add internal circuit construction
18876 state to protect against the noisy warn message "Unexpectedly high
18877 circuit_successes". Also add some additional rate-limited notice
18878 messages to help determine the root cause of the warn. Fixes bug
18879 6475. Bugfix against 0.2.3.17-beta.
18880 - Move log message when unable to find a microdesc in a routerstatus
18881 entry to parse time. Previously we'd spam this warning every time
18882 we tried to figure out which microdescriptors to download. Fixes
18883 the third piece of bug 6404; fix on 0.2.3.18-rc.
18886 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
18887 change when the authority is deciding whether to accept a newly
18888 uploaded descriptor. Implements ticket 6423.
18889 - Add missing documentation for consensus and microdesc files.
18890 Resolves ticket 6732.
18893 Changes in version 0.2.2.38 - 2012-08-12
18894 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
18895 attack that could in theory leak path information.
18898 - Avoid an uninitialized memory read when reading a vote or consensus
18899 document that has an unrecognized flavor name. This read could
18900 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18901 - Try to leak less information about what relays a client is
18902 choosing to a side-channel attacker. Previously, a Tor client would
18903 stop iterating through the list of available relays as soon as it
18904 had chosen one, thus finishing a little earlier when it picked
18905 a router earlier in the list. If an attacker can recover this
18906 timing information (nontrivial but not proven to be impossible),
18907 they could learn some coarse-grained information about which relays
18908 a client was picking (middle nodes in particular are likelier to
18909 be affected than exits). The timing attack might be mitigated by
18910 other factors (see bug 6537 for some discussion), but it's best
18911 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18914 Changes in version 0.2.3.20-rc - 2012-08-05
18915 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
18916 series. It fixes a pair of code security bugs and a potential anonymity
18917 issue, updates our RPM spec files, and cleans up other smaller issues.
18920 - Avoid read-from-freed-memory and double-free bugs that could occur
18921 when a DNS request fails while launching it. Fixes bug 6480;
18922 bugfix on 0.2.0.1-alpha.
18923 - Avoid an uninitialized memory read when reading a vote or consensus
18924 document that has an unrecognized flavor name. This read could
18925 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18926 - Try to leak less information about what relays a client is
18927 choosing to a side-channel attacker. Previously, a Tor client would
18928 stop iterating through the list of available relays as soon as it
18929 had chosen one, thus finishing a little earlier when it picked
18930 a router earlier in the list. If an attacker can recover this
18931 timing information (nontrivial but not proven to be impossible),
18932 they could learn some coarse-grained information about which relays
18933 a client was picking (middle nodes in particular are likelier to
18934 be affected than exits). The timing attack might be mitigated by
18935 other factors (see bug 6537 for some discussion), but it's best
18936 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18939 - Try to make the warning when giving an obsolete SOCKSListenAddress
18940 a little more useful.
18941 - Terminate active server managed proxies if Tor stops being a
18942 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
18943 - Provide a better error message about possible OSX Asciidoc failure
18944 reasons. Fixes bug 6436.
18945 - Warn when Tor is configured to use accounting in a way that can
18946 link a hidden service to some other hidden service or public
18947 address. Resolves ticket 6490.
18950 - Check return value of fputs() when writing authority certificate
18951 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
18952 - Ignore ServerTransportPlugin lines when Tor is not configured as
18953 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
18954 - When disabling guards for having too high a proportion of failed
18955 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
18959 - Update our default RPM spec files to work with mock and rpmbuild
18960 on RHEL/Fedora. They have an updated set of dependencies and
18961 conflicts, a fix for an ancient typo when creating the "_tor"
18962 user, and better instructions. Thanks to Ondrej Mikle for the
18963 patch series. Fixes bug 6043.
18966 - Make it possible to set the TestingTorNetwork configuration
18967 option using AlternateDirAuthority and AlternateBridgeAuthority
18968 as an alternative to setting DirServer. Addresses ticket 6377.
18971 - Clarify the documentation for the Alternate*Authority options.
18973 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
18975 o Code simplification and refactoring:
18976 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
18977 10 lines. Also, don't nest them. Doing so in the past has
18978 led to hard-to-debug code. The new style is to use the
18979 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
18982 Changes in version 0.2.3.19-rc - 2012-07-06
18983 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
18984 series. It fixes the compile on Windows, reverts to a GeoIP database
18985 that isn't as broken, and fixes a flow control bug that has been around
18986 since the beginning of Tor.
18989 - Fix a bug handling SENDME cells on nonexistent streams that could
18990 result in bizarre window values. Report and patch contributed
18991 pseudonymously. Fixes part of bug 6271. This bug was introduced
18992 before the first Tor release, in svn commit r152.
18993 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
18994 June 2012 database, Maxmind marked many Tor relays as country "A1",
18995 which will cause risky behavior for clients that set EntryNodes
18996 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
18997 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
18998 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
19001 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
19002 bugfix on 0.2.1.10-alpha.
19005 Changes in version 0.2.3.18-rc - 2012-06-28
19006 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
19007 series. It fixes a few smaller bugs, but generally appears stable.
19008 Please test it and let us know whether it is!
19011 - Allow wildcarded mapaddress targets to be specified on the
19012 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
19013 - Make our linker option detection code more robust against linkers
19014 such as on FreeBSD 8, where a bad combination of options completes
19015 successfully but makes an unrunnable binary. Fixes bug 6173;
19016 bugfix on 0.2.3.17-beta.
19018 o Minor bugfixes (on 0.2.2.x and earlier):
19019 - Avoid a false positive in the util/threads unit test by increasing
19020 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
19021 - Replace "Sending publish request" log messages with "Launching
19022 upload", so that they no longer confusingly imply that we're
19023 sending something to a directory we might not even be connected
19024 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
19025 - Make sure to set *socket_error in all error cases in
19026 connection_connect(), so it can't produce a warning about
19027 errno being zero from errno_to_orconn_end_reason(). Bugfix on
19028 0.2.1.1-alpha; resolves ticket 6028.
19029 - Downgrade "Got a certificate, but we already have it" log messages
19030 from warning to info, except when we're a dirauth. Fixes bug 5238;
19031 bugfix on 0.2.1.7-alpha.
19032 - When checking for requested signatures on the latest consensus
19033 before serving it to a client, make sure to check the right
19034 consensus flavor. Bugfix on 0.2.2.6-alpha.
19035 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
19036 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
19038 o Minor bugfixes (on 0.2.3.x):
19039 - Make format_helper_exit_status() avoid unnecessary space padding
19040 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
19042 - Downgrade a message about cleaning the microdescriptor cache to
19043 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
19044 - Log a BUG message at severity INFO if we have a networkstatus with
19045 a missing entry for some microdescriptor. Continues on a patch
19047 - Improve the log message when a managed proxy fails to launch. Fixes
19048 bug 5099; bugfix on 0.2.3.6-alpha.
19049 - Don't do DNS lookups when parsing corrupted managed proxy protocol
19050 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
19051 - When formatting wildcarded address mappings for the controller,
19052 be sure to include "*." as appropriate. Partially fixes bug 6244;
19053 bugfix on 0.2.3.9-alpha.
19054 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
19055 Bugfix on 0.2.3.13-alpha.
19056 - Stop logging messages about running with circuit timeout learning
19057 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
19058 - Disable a spurious warning about reading on a marked and flushing
19059 connection. We shouldn't be doing that, but apparently we
19060 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
19061 - Fix a bug that stopped AllowDotExit from working on addresses
19062 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
19065 o Code simplification, refactoring, unit tests:
19066 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
19067 Libevent's notion of cached time when possible.
19068 - Remove duplicate code for invoking getrlimit() from control.c.
19069 - Add a unit test for the environment_variable_names_equal function.
19072 - Document the --defaults-torrc option, and the new (in 0.2.3)
19073 semantics for overriding, extending, and clearing lists of
19074 options. Closes bug 4748.
19077 Changes in version 0.2.3.17-beta - 2012-06-15
19078 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
19079 gets our TLS handshake back on track for being able to blend in with
19080 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
19081 with Vidalia, and otherwise continues to get us closer to a release
19085 - Enable gcc and ld hardening by default. Resolves ticket 5210.
19086 - Update TLS cipher list to match Firefox 8 and later. Resolves
19088 - Implement the client side of proposal 198: remove support for
19089 clients falsely claiming to support standard ciphersuites that
19090 they can actually provide. As of modern OpenSSL versions, it's not
19091 necessary to fake any standard ciphersuite, and doing so prevents
19092 us from using better ciphersuites in the future, since servers
19093 can't know whether an advertised ciphersuite is really supported or
19094 not. Some hosts -- notably, ones with very old versions of OpenSSL
19095 or where OpenSSL has been built with ECC disabled -- will stand
19096 out because of this change; TBB users should not be affected.
19099 - Change the default value for DynamicDHGroups (introduced in
19100 0.2.3.9-alpha) to 0. This feature can make Tor relays less
19101 identifiable by their use of the mod_ssl DH group, but at
19102 the cost of some usability (#4721) and bridge tracing (#6087)
19103 regressions. Resolves ticket 5598.
19104 - Send a CRLF at the end of each STATUS_* control protocol event. This
19105 bug tickled a bug in Vidalia which would make it freeze. Fixes
19106 bug 6094; bugfix on 0.2.3.16-alpha.
19109 - Disable writing on marked-for-close connections when they are
19110 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
19111 bug 5263; bugfix on 0.0.2pre13, where we first added a special
19112 case for flushing marked connections.
19113 - Detect SSL handshake even when the initial attempt to write the
19114 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
19115 - Change the AllowDotExit rules so they should actually work.
19116 We now enforce AllowDotExit only immediately after receiving an
19117 address via SOCKS or DNSPort: other sources are free to provide
19118 .exit addresses after the resolution occurs. Fixes bug 3940;
19119 bugfix on 0.2.2.1-alpha.
19120 - Fix a (harmless) integer overflow in cell statistics reported by
19121 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
19122 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
19123 right places and never depends on the consensus parameters or
19124 computes adaptive timeouts when it is disabled. Fixes bug 5049;
19125 bugfix on 0.2.2.14-alpha.
19126 - When building Tor on Windows with -DUNICODE (not default), ensure
19127 that error messages, filenames, and DNS server names are always
19128 NUL-terminated when we convert them to a single-byte encoding.
19129 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
19130 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
19131 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
19132 - Fix an edge case where TestingTorNetwork is set but the authorities
19133 and relays all have an uptime of zero, where the private Tor network
19134 could briefly lack support for hidden services. Fixes bug 3886;
19135 bugfix on 0.2.2.18-alpha.
19136 - Correct the manpage's descriptions for the default values of
19137 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
19139 - Fix the documentation for the --hush and --quiet command line
19140 options, which changed their behavior back in 0.2.3.3-alpha.
19141 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
19145 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
19146 more information to it, so that we can track it down in case it
19147 returns again. Mitigates bug 5235.
19148 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
19149 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
19150 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
19151 - Warn the user when HTTPProxy, but no other proxy type, is
19152 configured. This can cause surprising behavior: it doesn't send
19153 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
19154 directory traffic only. Resolves ticket 4663.
19155 - Issue a notice if a guard completes less than 40% of your circuits.
19156 Threshold is configurable by torrc option PathBiasNoticeRate and
19157 consensus parameter pb_noticepct. There is additional, off-by-
19158 default code to disable guards which fail too many circuits.
19159 Addresses ticket 5458.
19160 - Update to the June 6 2012 Maxmind GeoLite Country database.
19162 o Code simplifications and refactoring:
19163 - Remove validate_pluggable_transports_config(): its warning
19164 message is now handled by connection_or_connect().
19167 Changes in version 0.2.2.37 - 2012-06-06
19168 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
19169 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19173 - Work around a bug in OpenSSL that broke renegotiation with TLS
19174 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19175 the v2 Tor connection protocol when both sides were using OpenSSL
19176 1.0.1 would fail. Resolves ticket 6033.
19177 - When waiting for a client to renegotiate, don't allow it to add
19178 any bytes to the input buffer. This fixes a potential DoS issue.
19179 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19180 - Fix an edge case where if we fetch or publish a hidden service
19181 descriptor, we might build a 4-hop circuit and then use that circuit
19182 for exiting afterwards -- even if the new last hop doesn't obey our
19183 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19186 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19187 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19190 - Tell GCC and Clang to check for any errors in format strings passed
19191 to the tor_v*(print|scan)f functions.
19194 Changes in version 0.2.3.16-alpha - 2012-06-05
19195 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
19196 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19197 currently). It also fixes a variety of smaller bugs and other cleanups
19198 that get us closer to a release candidate.
19200 o Major bugfixes (general):
19201 - Work around a bug in OpenSSL that broke renegotiation with TLS
19202 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19203 the v2 Tor connection protocol when both sides were using OpenSSL
19204 1.0.1 would fail. Resolves ticket 6033.
19205 - When waiting for a client to renegotiate, don't allow it to add
19206 any bytes to the input buffer. This fixes a potential DoS issue.
19207 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19208 - Pass correct OR address to managed proxies (like obfsproxy),
19209 even when ORListenAddress is used. Fixes bug 4865; bugfix on
19211 - The advertised platform of a router now includes only its operating
19212 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
19213 service pack level (for Windows) or its CPU architecture (for Unix).
19214 We also no longer include the "git-XYZ" tag in the version. Resolves
19217 o Major bugfixes (clients):
19218 - If we are unable to find any exit that supports our predicted ports,
19219 stop calling them predicted, so that we don't loop and build
19220 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
19221 which introduced predicted ports.
19222 - Fix an edge case where if we fetch or publish a hidden service
19223 descriptor, we might build a 4-hop circuit and then use that circuit
19224 for exiting afterwards -- even if the new last hop doesn't obey our
19225 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19226 - Check at each new consensus whether our entry guards were picked
19227 long enough ago that we should rotate them. Previously, we only
19228 did this check at startup, which could lead to us holding a guard
19229 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
19230 - When fetching a bridge descriptor from a bridge authority,
19231 always do so anonymously, whether we have been able to open
19232 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
19233 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
19234 but we'll need to wait for bug 6010 before it's actually usable.
19236 o Major bugfixes (directory authorities):
19237 - When computing weight parameters, behave more robustly in the
19238 presence of a bad bwweightscale value. Previously, the authorities
19239 would crash if they agreed on a sufficiently broken weight_scale
19240 value: now, they use a reasonable default and carry on. Partial
19241 fix for 5786; bugfix on 0.2.2.17-alpha.
19242 - Check more thoroughly to prevent a rogue authority from
19243 double-voting on any consensus directory parameter. Previously,
19244 authorities would crash in this case if the total number of
19245 votes for any parameter exceeded the number of active voters,
19246 but would let it pass otherwise. Partial fix for bug 5786; bugfix
19250 - Rate-limit log messages when asked to connect anonymously to
19251 a private address. When these hit, they tended to hit fast and
19252 often. Also, don't bother trying to connect to addresses that we
19253 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
19254 reply makes us think we have been lied to, even when the address the
19255 client tried to connect to was "localhost." Resolves ticket 2822.
19256 - Allow packagers to insert an extra string in server descriptor
19257 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
19258 Resolves the rest of ticket 2988.
19259 - Raise the threshold of server descriptors needed (75%) and exit
19260 server descriptors needed (50%) before we will declare ourselves
19261 bootstrapped. This will make clients start building circuits a
19262 little later, but makes the initially constructed circuits less
19263 skewed and less in conflict with further directory fetches. Fixes
19265 - Close any connection that sends unrecognized junk before the
19266 handshake. Solves an issue noted in bug 4369.
19267 - Improve log messages about managed transports. Resolves ticket 5070.
19268 - Tag a bridge's descriptor as "never to be sent unencrypted".
19269 This shouldn't matter, since bridges don't open non-anonymous
19270 connections to the bridge authority and don't allow unencrypted
19271 directory connections from clients, but we might as well make
19272 sure. Closes bug 5139.
19273 - Expose our view of whether we have gone dormant to the controller,
19274 via a new "GETINFO dormant" value. Torbutton and other controllers
19275 can use this to avoid doing periodic requests through Tor while
19276 it's dormant (bug 4718). Fixes bug 5954.
19277 - Tell GCC and Clang to check for any errors in format strings passed
19278 to the tor_v*(print|scan)f functions.
19279 - Update to the May 1 2012 Maxmind GeoLite Country database.
19281 o Minor bugfixes (already included in 0.2.2.36):
19282 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19283 Fixes bug 5346; bugfix on 0.0.8pre3.
19284 - Correct parsing of certain date types in parse_http_time().
19285 Without this patch, If-Modified-Since would behave
19286 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19287 Esteban Manchado Velázques.
19288 - Make our number-parsing functions always treat too-large values
19289 as an error, even when those values exceed the width of the
19290 underlying type. Previously, if the caller provided these
19291 functions with minima or maxima set to the extreme values of the
19292 underlying integer type, these functions would return those
19293 values on overflow rather than treating overflow as an error.
19294 Fixes part of bug 5786; bugfix on 0.0.9.
19295 - If we hit the error case where routerlist_insert() replaces an
19296 existing (old) server descriptor, make sure to remove that
19297 server descriptor from the old_routers list. Fix related to bug
19298 1776. Bugfix on 0.2.2.18-alpha.
19299 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19300 circuits. Fixes issue 5259.
19302 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
19303 - Prevent a null-pointer dereference when receiving a data cell
19304 for a nonexistent stream when the circuit in question has an
19305 empty deliver window. We don't believe this is triggerable,
19306 since we don't currently allow deliver windows to become empty,
19307 but the logic is tricky enough that it's better to make the code
19308 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
19309 - Fix a memory leak when trying to launch a DNS request when the
19310 network is disabled or the nameservers are unconfigurable. Fixes
19311 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
19312 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
19313 - Don't hold a Windows file handle open for every file mapping;
19314 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
19316 - Avoid O(n^2) performance characteristics when parsing a large
19317 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
19318 - Format more doubles with %f, not %lf. Patch from grarpamp to make
19319 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
19321 - Make our replacement implementation of strtok_r() compatible with
19322 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
19323 bugfix on 0.2.2.1-alpha.
19324 - Fix a NULL-pointer dereference on a badly formed
19325 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
19326 bugfix on 0.2.2.9-alpha.
19327 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19328 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19329 - Defensively refactor rend_mid_rendezvous() so that protocol
19330 violations and length checks happen in the beginning. Fixes
19332 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
19333 that IPv6 stuff will compile on MSVC, and compilation issues
19334 will be easier to track down. Fixes bug 5861.
19336 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
19337 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
19338 resource exhaustion, so that clients can adjust their load to
19339 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
19340 started using END_STREAM_REASON_RESOURCELIMIT.
19341 - Don't check for whether the address we're using for outbound
19342 connections has changed until after the outbound connection has
19343 completed. On Windows, getsockname() doesn't succeed until the
19344 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
19345 - If the configuration tries to set MyFamily on a bridge, refuse to
19346 do so, and warn about the security implications. Fixes bug 4657;
19347 bugfix on 0.2.0.3-alpha.
19348 - If the client fails to set a reasonable set of ciphersuites
19349 during its v2 handshake renegotiation, allow the renegotiation to
19350 continue nevertheless (i.e. send all the required certificates).
19351 Fixes bug 4591; bugfix on 0.2.0.20-rc.
19352 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
19353 option is set to 0 (which Vidalia version 0.2.16 now does when
19354 a SAVECONF attempt fails), perform other actions that SIGHUP
19355 usually causes (like reopening the logs). Fixes bug 5095; bugfix
19357 - If we fail to write a microdescriptor to the disk cache, do not
19358 continue replacing the old microdescriptor file. Fixes bug 2954;
19359 bugfix on 0.2.2.6-alpha.
19360 - Exit nodes don't need to fetch certificates for authorities that
19361 they don't recognize; only directory authorities, bridges,
19362 and caches need to do that. Fixes part of bug 2297; bugfix on
19364 - Correctly handle checking the permissions on the parent
19365 directory of a control socket in the root directory. Bug found
19366 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
19368 - When told to add a bridge with the same digest as a preexisting
19369 bridge but a different addr:port, change the addr:port as
19370 requested. Previously we would not notice the change. Fixes half
19371 of bug 5603; fix on 0.2.2.26-beta.
19372 - End AUTHCHALLENGE error messages (in the control protocol) with
19373 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
19375 o Minor bugfixes (on 0.2.3.x):
19376 - Turn an assertion (that the number of handshakes received as a
19377 server is not < 1) into a warning. Fixes bug 4873; bugfix on
19379 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
19380 we had reversed them when the answer was cached.) Fixes bug
19381 5723; bugfix on 0.2.3.1-alpha.
19382 - Work correctly on Linux systems with accept4 support advertised in
19383 their headers, but without accept4 support in the kernel. Fix
19384 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
19385 - When told to add a bridge with the same addr:port as a preexisting
19386 bridge but a different transport, change the transport as
19387 requested. Previously we would not notice the change. Fixes half
19388 of bug 5603; fix on 0.2.3.2-alpha.
19389 - Avoid a "double-reply" warning when replying to a SOCKS request
19390 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
19391 bugfix on 0.2.3.4-alpha.
19392 - Fix a bug where a bridge authority crashes if it has seen no
19393 directory requests when it's time to write statistics to disk.
19394 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
19396 - Don't try to open non-control listeners when DisableNetwork is set.
19397 Previously, we'd open all listeners, then immediately close them.
19398 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
19399 - Don't abort the managed proxy protocol if the managed proxy
19400 sends us an unrecognized line; ignore it instead. Fixes bug
19401 5910; bugfix on 0.2.3.9-alpha.
19402 - Fix a compile warning in crypto.c when compiling with clang 3.1.
19403 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
19404 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
19405 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
19406 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
19407 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
19408 - Resolve numerous small warnings and build issues with MSVC. Resolves
19411 o Documentation fixes:
19412 - Improve the manual's documentation for the NT Service command-line
19413 options. Addresses ticket 3964.
19414 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
19415 - Document the changes to the ORPort and DirPort options, and the
19416 fact that {OR/Dir}ListenAddress is now unnecessary (and
19417 therefore deprecated). Resolves ticket 5597.
19420 - Remove the torrc.bridge file: we don't use it for anything, and
19421 it had become badly desynchronized from torrc.sample. Resolves
19425 Changes in version 0.2.2.36 - 2012-05-24
19426 Tor 0.2.2.36 updates the addresses for two of the eight directory
19427 authorities, fixes some potential anonymity and security issues,
19428 and fixes several crash bugs.
19430 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
19431 known flaws, and nobody should be using them. You should upgrade. If
19432 you're using a Linux or BSD and its packages are obsolete, stop using
19433 those packages and upgrade anyway.
19435 o Directory authority changes:
19436 - Change IP address for maatuska (v3 directory authority).
19437 - Change IP address for ides (v3 directory authority), and rename
19441 - When building or running with any version of OpenSSL earlier
19442 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19443 versions have a bug (CVE-2011-4576) in which their block cipher
19444 padding includes uninitialized data, potentially leaking sensitive
19445 information to any peer with whom they make a SSLv3 connection. Tor
19446 does not use SSL v3 by default, but a hostile client or server
19447 could force an SSLv3 connection in order to gain information that
19448 they shouldn't have been able to get. The best solution here is to
19449 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19450 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19451 to make sure that the bug can't happen.
19452 - Never use a bridge or a controller-supplied node as an exit, even
19453 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19454 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19455 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19456 - Only build circuits if we have a sufficient threshold of the total
19457 descriptors that are marked in the consensus with the "Exit"
19458 flag. This mitigates an attack proposed by wanoskarnet, in which
19459 all of a client's bridges collude to restrict the exit nodes that
19460 the client knows about. Fixes bug 5343.
19461 - Provide controllers with a safer way to implement the cookie
19462 authentication mechanism. With the old method, if another locally
19463 running program could convince a controller that it was the Tor
19464 process, then that program could trick the controller into telling
19465 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19466 authentication method uses a challenge-response approach to prevent
19467 this attack. Fixes bug 5185; implements proposal 193.
19470 - Avoid logging uninitialized data when unable to decode a hidden
19471 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19472 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19473 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19475 - Fix builds when the path to sed, openssl, or sha1sum contains
19476 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19478 - Correct our replacements for the timeradd() and timersub() functions
19479 on platforms that lack them (for example, Windows). The timersub()
19480 function is used when expiring circuits, while timeradd() is
19481 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19482 bugfix on 0.2.2.24-alpha.
19483 - Fix the SOCKET_OK test that we use to tell when socket
19484 creation fails so that it works on Win64. Fixes part of bug 4533;
19485 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19488 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19489 Fixes bug 5346; bugfix on 0.0.8pre3.
19490 - Make our number-parsing functions always treat too-large values
19491 as an error, even when those values exceed the width of the
19492 underlying type. Previously, if the caller provided these
19493 functions with minima or maxima set to the extreme values of the
19494 underlying integer type, these functions would return those
19495 values on overflow rather than treating overflow as an error.
19496 Fixes part of bug 5786; bugfix on 0.0.9.
19497 - Older Linux kernels erroneously respond to strange nmap behavior
19498 by having accept() return successfully with a zero-length
19499 socket. When this happens, just close the connection. Previously,
19500 we would try harder to learn the remote address: but there was
19501 no such remote address to learn, and our method for trying to
19502 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19503 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19504 - Correct parsing of certain date types in parse_http_time().
19505 Without this patch, If-Modified-Since would behave
19506 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19507 Esteban Manchado Velázques.
19508 - Change the BridgePassword feature (part of the "bridge community"
19509 design, which is not yet implemented) to use a time-independent
19510 comparison. The old behavior might have allowed an adversary
19511 to use timing to guess the BridgePassword value. Fixes bug 5543;
19512 bugfix on 0.2.0.14-alpha.
19513 - Detect and reject certain misformed escape sequences in
19514 configuration values. Previously, these values would cause us
19515 to crash if received in a torrc file or over an authenticated
19516 control port. Bug found by Esteban Manchado Velázquez, and
19517 independently by Robert Connolly from Matta Consulting who further
19518 noted that it allows a post-authentication heap overflow. Patch
19519 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19520 bugfix on 0.2.0.16-alpha.
19521 - Fix a compile warning when using the --enable-openbsd-malloc
19522 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19523 - During configure, detect when we're building with clang version
19524 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19525 CFLAGS. clang doesn't support them yet.
19526 - When sending an HTTP/1.1 proxy request, include a Host header.
19527 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19528 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
19529 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
19530 - If we hit the error case where routerlist_insert() replaces an
19531 existing (old) server descriptor, make sure to remove that
19532 server descriptor from the old_routers list. Fix related to bug
19533 1776. Bugfix on 0.2.2.18-alpha.
19535 o Minor bugfixes (documentation and log messages):
19536 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19537 Fixes bug 4856; bugfix on Tor 0.0.6.
19538 - Update "ClientOnly" man page entry to explain that there isn't
19539 really any point to messing with it. Resolves ticket 5005.
19540 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19541 directory authority option (introduced in Tor 0.2.2.34).
19542 - Downgrade the "We're missing a certificate" message from notice
19543 to info: people kept mistaking it for a real problem, whereas it
19544 is seldom the problem even when we are failing to bootstrap. Fixes
19545 bug 5067; bugfix on 0.2.0.10-alpha.
19546 - Correctly spell "connect" in a log message on failure to create a
19547 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
19548 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19549 circuits. Fixes issue 5259.
19552 - Directory authorities now reject versions of Tor older than
19553 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19554 inclusive. These versions accounted for only a small fraction of
19555 the Tor network, and have numerous known security issues. Resolves
19557 - Update to the May 1 2012 Maxmind GeoLite Country database.
19560 - When sending or relaying a RELAY_EARLY cell, we used to convert
19561 it to a RELAY cell if the connection was using the v1 link
19562 protocol. This was a workaround for older versions of Tor, which
19563 didn't handle RELAY_EARLY cells properly. Now that all supported
19564 versions can handle RELAY_EARLY cells, and now that we're enforcing
19565 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19566 remove this workaround. Addresses bug 4786.
19569 Changes in version 0.2.3.15-alpha - 2012-04-30
19570 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
19571 the development branch build on Windows again.
19573 o Minor bugfixes (on 0.2.2.x and earlier):
19574 - Make sure that there are no unhandled pending TLS errors before
19575 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
19576 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
19577 Bugfix on 0.1.0.5-rc; fixes bug 4528.
19578 - Fix an assert that directory authorities could trigger on sighup
19579 during some configuration state transitions. We now don't treat
19580 it as a fatal error when the new descriptor we just generated in
19581 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
19582 - After we pick a directory mirror, we would refuse to use it if
19583 it's in our ExcludeExitNodes list, resulting in mysterious failures
19584 to bootstrap for people who just wanted to avoid exiting from
19585 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
19586 - When building with --enable-static-tor on OpenBSD, do not
19587 erroneously attempt to link -lrt. Fixes bug 5103.
19589 o Minor bugfixes (on 0.2.3.x):
19590 - When Tor is built with kernel headers from a recent (last few
19591 years) Linux kernel, do not fail to run on older (pre-2.6.28
19592 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
19593 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
19594 and 0.2.3.12-alpha.
19595 - Fix compilation with miniupnpc version 1.6; patch from
19596 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
19597 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
19598 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
19599 - Fix compilation on platforms without unistd.h, or where environ
19600 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
19603 - Directory authorities are now a little more lenient at accepting
19604 older router descriptors, or newer router descriptors that don't
19605 make big changes. This should help ameliorate past and future
19606 issues where routers think they have uploaded valid descriptors,
19607 but the authorities don't think so. Fix for ticket 2479.
19608 - Make the code that clients use to detect an address change be
19609 IPv6-aware, so that it won't fill clients' logs with error
19610 messages when trying to get the IPv4 address of an IPv6
19611 connection. Implements ticket 5537.
19613 o Removed features:
19614 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
19615 authorities needed to use it for a while to keep the network working
19616 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
19617 that was six months ago. As of now, it should no longer be needed
19621 Changes in version 0.2.3.14-alpha - 2012-04-23
19622 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
19623 candidate. It also dramatically speeds up AES: fast relays should
19624 consider switching to the newer OpenSSL library.
19626 o Directory authority changes:
19627 - Change IP address for ides (v3 directory authority), and rename
19631 - Avoid logging uninitialized data when unable to decode a hidden
19632 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19633 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19634 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19636 - If authorities are unable to get a v2 consensus document from other
19637 directory authorities, they no longer fall back to fetching
19638 them from regular directory caches. Fixes bug 5635; bugfix on
19639 0.2.2.26-beta, where routers stopped downloading v2 consensus
19640 documents entirely.
19641 - When we start a Tor client with a normal consensus already cached,
19642 be willing to download a microdescriptor consensus. Fixes bug 4011;
19643 fix on 0.2.3.1-alpha.
19645 o Major features (performance):
19646 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
19647 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
19648 vectorized AES implementations as appropriate. These can be much,
19649 much faster than other AES implementations.
19651 o Minor bugfixes (0.2.2.x and earlier):
19652 - Don't launch more than 10 service-side introduction-point circuits
19653 for a hidden service in five minutes. Previously, we would consider
19654 launching more introduction-point circuits if at least one second
19655 had passed without any introduction-point circuits failing. Fixes
19656 bug 4607; bugfix on 0.0.7pre1.
19657 - Change the BridgePassword feature (part of the "bridge community"
19658 design, which is not yet implemented) to use a time-independent
19659 comparison. The old behavior might have allowed an adversary
19660 to use timing to guess the BridgePassword value. Fixes bug 5543;
19661 bugfix on 0.2.0.14-alpha.
19662 - Enforce correct return behavior of tor_vsscanf() when the '%%'
19663 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
19664 - When sending an HTTP/1.1 proxy request, include a Host header.
19665 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19666 - Don't log that we have "decided to publish new relay descriptor"
19667 unless we are actually publishing a descriptor. Fixes bug 3942;
19668 bugfix on 0.2.2.28-beta.
19670 o Minor bugfixes (0.2.3.x):
19671 - Fix a bug where a bridge authority crashes (on a failed assert)
19672 if it has seen no directory requests when it's time to write
19673 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
19674 - Fix bug stomping on ORPort option NoListen and ignoring option
19675 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
19676 - In the testsuite, provide a large enough buffer in the tor_sscanf
19677 unit test. Otherwise we'd overrun that buffer and crash during
19678 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
19680 - Make sure we create the keys directory if it doesn't exist and we're
19681 about to store the dynamic Diffie-Hellman parameters. Fixes bug
19682 5572; bugfix on 0.2.3.13-alpha.
19683 - Fix a small memory leak when trying to decode incorrect base16
19684 authenticator during SAFECOOKIE authentication. Found by
19685 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
19688 - Add more information to a log statement that might help track down
19689 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
19690 non-IP address" messages (or any Bug messages, for that matter!),
19691 please let us know about it.
19692 - Relays now understand an IPv6 address when they get one from a
19693 directory server. Resolves ticket 4875.
19694 - Resolve IPv6 addresses in bridge and entry statistics to country
19695 code "??" which means we at least count them. Resolves ticket 5053;
19696 improves on 0.2.3.9-alpha.
19697 - Update to the April 3 2012 Maxmind GeoLite Country database.
19698 - Begin a doc/state-contents.txt file to explain the contents of
19699 the Tor state file. Fixes bug 2987.
19701 o Default torrc changes:
19702 - Stop listing "socksport 9050" in torrc.sample. We open a socks
19703 port on 9050 by default anyway, so this should not change anything
19705 - Stop mentioning the deprecated *ListenAddress options in
19706 torrc.sample. Fixes bug 5438.
19707 - Document unit of bandwidth related options in sample torrc.
19710 o Removed features:
19711 - The "torify" script no longer supports the "tsocks" socksifier
19712 tool, since tsocks doesn't support DNS and UDP right for Tor.
19713 Everyone should be using torsocks instead. Fixes bugs 3530 and
19714 5180. Based on a patch by "ugh".
19716 o Code refactoring:
19717 - Change the symmetric cipher interface so that creating and
19718 initializing a stream cipher are no longer separate functions.
19719 - Remove all internal support for unpadded RSA. We never used it, and
19720 it would be a bad idea to start.
19723 Changes in version 0.2.3.13-alpha - 2012-03-26
19724 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
19725 in managed pluggable transports, as well as providing other cleanups
19726 that get us closer to a release candidate.
19728 o Directory authority changes:
19729 - Change IP address for maatuska (v3 directory authority).
19732 - Provide controllers with a safer way to implement the cookie
19733 authentication mechanism. With the old method, if another locally
19734 running program could convince a controller that it was the Tor
19735 process, then that program could trick the controller into telling
19736 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19737 authentication method uses a challenge-response approach to prevent
19738 this attack. Fixes bug 5185, implements proposal 193.
19739 - Never use a bridge or a controller-supplied node as an exit, even
19740 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19741 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19742 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19743 - Only build circuits if we have a sufficient threshold of the total
19744 descriptors that are marked in the consensus with the "Exit"
19745 flag. This mitigates an attack proposed by wanoskarnet, in which
19746 all of a client's bridges collude to restrict the exit nodes that
19747 the client knows about. Fixes bug 5343.
19749 o Major bugfixes (on Tor 0.2.3.x):
19750 - Avoid an assert when managed proxies like obfsproxy are configured,
19751 and we receive HUP signals or setconf attempts too rapidly. This
19752 situation happens most commonly when Vidalia tries to attach to
19753 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
19754 bugfix on 0.2.3.6-alpha.
19755 - Fix a relay-side pluggable transports bug where managed proxies were
19756 unreachable from the Internet, because Tor asked them to bind on
19757 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
19758 - Stop discarding command-line arguments when TestingTorNetwork
19759 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
19760 0.2.3.9-alpha, where task 4552 added support for two layers of
19762 - Resume allowing the unit tests to run in gdb. This was accidentally
19763 made impossible when the DisableDebuggerAttachment option was
19764 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
19765 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
19766 0.2.3.11-alpha. Reported by Anthony G. Basile.
19768 o Minor bugfixes (on 0.2.2.x and earlier):
19769 - Ensure we don't cannibalize circuits that are longer than three hops
19770 already, so we don't end up making circuits with 5 or more
19771 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
19772 0.1.0.1-rc which introduced cannibalization.
19773 - Detect and reject certain misformed escape sequences in
19774 configuration values. Previously, these values would cause us
19775 to crash if received in a torrc file or over an authenticated
19776 control port. Bug found by Esteban Manchado Velázquez, and
19777 independently by Robert Connolly from Matta Consulting who further
19778 noted that it allows a post-authentication heap overflow. Patch
19779 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19780 bugfix on 0.2.0.16-alpha.
19781 - Fix a compile warning when using the --enable-openbsd-malloc
19782 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19783 - Directory caches no longer refuse to clean out descriptors because
19784 of missing v2 networkstatus documents, unless they're configured
19785 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
19786 0.2.2.26-beta. Patch by Daniel Bryg.
19787 - Update to the latest version of the tinytest unit testing framework.
19788 This includes a couple of bugfixes that can be relevant for
19789 running forked unit tests on Windows, and removes all reserved
19792 o Minor bugfixes (on 0.2.3.x):
19793 - On a failed pipe() call, don't leak file descriptors. Fixes bug
19794 4296; bugfix on 0.2.3.1-alpha.
19795 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
19796 until after we have received a CERTS cell. Fixes bug 4361; bugfix
19797 on 0.2.3.6-alpha. Patch by "frosty".
19798 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
19799 option, so that the IP stack doesn't decide to use it for IPv4
19800 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
19801 - Ensure that variables set in Tor's environment cannot override
19802 environment variables that Tor passes to a managed
19803 pluggable-transport proxy. Previously, Tor would pass every
19804 variable in its environment to managed proxies along with the new
19805 ones, in such a way that on many operating systems, the inherited
19806 environment variables would override those which Tor tried to
19807 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
19808 bugfix on 0.2.3.9-alpha for Windows.
19811 - A wide variety of new unit tests by Esteban Manchado Velázquez.
19812 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
19813 - Update to the March 6 2012 Maxmind GeoLite Country database.
19816 Changes in version 0.2.3.12-alpha - 2012-02-13
19817 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
19818 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
19819 when Tor is configured to use a pluggable transport like obfsproxy.
19822 - Fix builds when the path to sed, openssl, or sha1sum contains
19823 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19825 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
19826 connections. This change should allow busy exit relays to stop
19827 running out of available sockets as quickly. Fixes bug 4950;
19828 bugfix on 0.2.2.26-beta.
19829 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
19830 would ask the bridge for microdescriptors, which are only supported
19831 in 0.2.3.x, and then fail to bootstrap when it didn't get the
19832 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
19833 - Properly set up obfsproxy's environment when in managed mode. The
19834 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
19835 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
19836 5076 and 5082; bugfix on 0.2.3.6-alpha.
19839 - Use the dead_strip option when building Tor on OS X. This reduces
19840 binary size by almost 19% when linking openssl and libevent
19841 statically, which we do for Tor Browser Bundle.
19842 - Fix broken URLs in the sample torrc file, and tell readers about
19843 the OutboundBindAddress, ExitPolicyRejectPrivate, and
19844 PublishServerDescriptor options. Addresses bug 4652.
19845 - Update to the February 7 2012 Maxmind GeoLite Country database.
19848 - Downgrade the "We're missing a certificate" message from notice
19849 to info: people kept mistaking it for a real problem, whereas it
19850 is seldom the problem even when we are failing to bootstrap. Fixes
19851 bug 5067; bugfix on 0.2.0.10-alpha.
19852 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
19853 managed pluggable transport server proxy's environment.
19854 Previously, we would put it there, even though Tor doesn't
19855 implement an 'extended server port' yet, and even though Tor
19856 almost certainly isn't listening at that address. For now, we set
19857 it to an empty string to avoid crashing older obfsproxies. Bugfix
19859 - Log the heartbeat message every HeartbeatPeriod seconds, not every
19860 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
19861 0.2.3.1-alpha. Bug reported by Scott Bennett.
19862 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
19863 bugfix on 0.2.3.11-alpha.
19864 - Update "ClientOnly" man page entry to explain that there isn't
19865 really any point to messing with it. Resolves ticket 5005.
19866 - Use the correct CVE number for CVE-2011-4576 in our comments and
19867 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
19870 o Code simplifications and refactoring:
19871 - Use the _WIN32 macro throughout our code to detect Windows.
19872 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
19876 Changes in version 0.2.3.11-alpha - 2012-01-22
19877 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
19878 the last step of the plan to limit maximum circuit length, includes
19879 a wide variety of hidden service performance and correctness fixes,
19880 works around an OpenSSL security flaw if your distro is too stubborn
19881 to upgrade, and fixes a bunch of smaller issues.
19884 - Now that Tor 0.2.0.x is completely deprecated, enable the final
19885 part of "Proposal 110: Avoiding infinite length circuits" by
19886 refusing all circuit-extend requests that do not use a relay_early
19887 cell. This change helps Tor resist a class of denial-of-service
19888 attacks by limiting the maximum circuit length.
19889 - Adjust the number of introduction points that a hidden service
19890 will try to maintain based on how long its introduction points
19891 remain in use and how many introductions they handle. Fixes
19893 - Try to use system facilities for enumerating local interface
19894 addresses, before falling back to our old approach (which was
19895 binding a UDP socket, and calling getsockname() on it). That
19896 approach was scaring OS X users whose draconian firewall
19897 software warned about binding to UDP sockets, regardless of
19898 whether packets were sent. Now we try to use getifaddrs(),
19899 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
19900 system supports. Resolves ticket 1827.
19902 o Major security workaround:
19903 - When building or running with any version of OpenSSL earlier
19904 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19905 versions have a bug (CVE-2011-4576) in which their block cipher
19906 padding includes uninitialized data, potentially leaking sensitive
19907 information to any peer with whom they make a SSLv3 connection. Tor
19908 does not use SSL v3 by default, but a hostile client or server
19909 could force an SSLv3 connection in order to gain information that
19910 they shouldn't have been able to get. The best solution here is to
19911 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19912 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19913 to make sure that the bug can't happen.
19916 - Fix the SOCKET_OK test that we use to tell when socket
19917 creation fails so that it works on Win64. Fixes part of bug 4533;
19918 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19919 - Correct our replacements for the timeradd() and timersub() functions
19920 on platforms that lack them (for example, Windows). The timersub()
19921 function is used when expiring circuits, while timeradd() is
19922 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19923 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
19924 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
19925 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
19926 bug at runtime, not compile time, because some distributions hack
19927 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
19928 on 0.2.3.9-alpha. Found by Pascal.
19930 o Minor features (controller):
19931 - Use absolute path names when reporting the torrc filename in the
19932 control protocol, so a controller can more easily find the torrc
19933 file. Resolves bug 1101.
19934 - Extend the control protocol to report flags that control a circuit's
19935 path selection in CIRC events and in replies to 'GETINFO
19936 circuit-status'. Implements part of ticket 2411.
19937 - Extend the control protocol to report the hidden service address
19938 and current state of a hidden-service-related circuit in CIRC
19939 events and in replies to 'GETINFO circuit-status'. Implements part
19941 - When reporting the path to the cookie file to the controller,
19942 give an absolute path. Resolves ticket 4881.
19943 - Allow controllers to request an event notification whenever a
19944 circuit is cannibalized or its purpose is changed. Implements
19945 part of ticket 3457.
19946 - Include the creation time of a circuit in CIRC and CIRC2
19947 control-port events and the list produced by the 'GETINFO
19948 circuit-status' control-port command.
19950 o Minor features (directory authorities):
19951 - Directory authorities now reject versions of Tor older than
19952 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19953 inclusive. These versions accounted for only a small fraction of
19954 the Tor network, and have numerous known security issues. Resolves
19956 - Authority operators can now vote for all relays in a given
19957 set of countries to be BadDir/BadExit/Invalid/Rejected.
19958 - Provide two consensus parameters (FastFlagMinThreshold and
19959 FastFlagMaxThreshold) to control the range of allowable bandwidths
19960 for the Fast directory flag. These allow authorities to run
19961 experiments on appropriate requirements for being a "Fast" node.
19962 The AuthDirFastGuarantee config value still applies. Implements
19964 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19965 directory authority option (introduced in Tor 0.2.2.34).
19967 o Minor features (other):
19968 - Don't disable the DirPort when we cannot exceed our AccountingMax
19969 limit during this interval because the effective bandwidthrate is
19970 low enough. This is useful in a situation where AccountMax is only
19971 used as an additional safeguard or to provide statistics.
19972 - Prepend an informative header to generated dynamic_dh_params files.
19973 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
19974 EntryNodes will have no effect. Resolves issue 2571.
19975 - Log more useful messages when we fail to disable debugger
19977 - Log which authority we're missing votes from when we go to fetch
19978 them from the other auths.
19979 - Log (at debug level) whenever a circuit's purpose is changed.
19980 - Add missing documentation for the MaxClientCircuitsPending,
19981 UseMicrodescriptors, UserspaceIOCPBuffers, and
19982 _UseFilteringSSLBufferevents options, all introduced during
19983 the 0.2.3.x series.
19984 - Update to the January 3 2012 Maxmind GeoLite Country database.
19986 o Minor bugfixes (hidden services):
19987 - Don't close hidden service client circuits which have almost
19988 finished connecting to their destination when they reach
19989 the normal circuit-build timeout. Previously, we would close
19990 introduction circuits which are waiting for an acknowledgement
19991 from the introduction point, and rendezvous circuits which have
19992 been specified in an INTRODUCE1 cell sent to a hidden service,
19993 after the normal CBT. Now, we mark them as 'timed out', and launch
19994 another rendezvous attempt in parallel. This behavior change can
19995 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
19996 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
19997 - Don't close hidden-service-side rendezvous circuits when they
19998 reach the normal circuit-build timeout. This behavior change can
19999 be disabled using the new
20000 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
20001 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
20002 - Make sure we never mark the wrong rendezvous circuit as having
20003 had its introduction cell acknowledged by the introduction-point
20004 relay. Previously, when we received an INTRODUCE_ACK cell on a
20005 client-side hidden-service introduction circuit, we might have
20006 marked a rendezvous circuit other than the one we specified in
20007 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
20008 a warning message and interfered with the hidden service
20009 connection-establishment process. Fixes bug 4759; bugfix on
20010 0.2.3.3-alpha, when we added the stream-isolation feature which
20011 might cause Tor to open multiple rendezvous circuits for the same
20013 - Don't trigger an assertion failure when we mark a new client-side
20014 hidden-service introduction circuit for close during the process
20015 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
20018 o Minor bugfixes (log messages):
20019 - Correctly spell "connect" in a log message on failure to create a
20020 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
20022 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
20023 Fixes bug 4856; bugfix on Tor 0.0.6.
20024 - Fix the log message describing how we work around discovering
20025 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
20026 4837; bugfix on 0.2.2.9-alpha.
20027 - When logging about a disallowed .exit name, do not also call it
20028 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
20030 o Minor bugfixes (build fixes):
20031 - During configure, detect when we're building with clang version
20032 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
20033 CFLAGS. clang doesn't support them yet.
20034 - During configure, search for library containing cos function as
20035 libm lives in libcore on some platforms (BeOS/Haiku). Linking
20036 against libm was hard-coded before. Fixes the first part of bug
20037 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
20039 - Detect attempts to build Tor on (as yet hypothetical) versions
20040 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
20041 fix for bug 4533. Bugfix on 0.2.2.28-beta.
20042 - Preprocessor directives should not be put inside the arguments
20043 of a macro. This would break compilation with GCC releases prior
20044 to version 3.3. We would never recommend such an old GCC version,
20045 but it is apparently required for binary compatibility on some
20046 platforms (namely, certain builds of Haiku). Fixes the other part
20047 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
20050 o Minor bugfixes (other):
20051 - Older Linux kernels erroneously respond to strange nmap behavior
20052 by having accept() return successfully with a zero-length
20053 socket. When this happens, just close the connection. Previously,
20054 we would try harder to learn the remote address: but there was
20055 no such remote address to learn, and our method for trying to
20056 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
20057 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
20058 - Fix null-pointer access that could occur if TLS allocation failed.
20059 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
20060 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
20061 accidentally been reverted.
20062 - Fix our implementation of crypto_random_hostname() so it can't
20063 overflow on ridiculously large inputs. (No Tor version has ever
20064 provided this kind of bad inputs, but let's be correct in depth.)
20065 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
20066 - Find more places in the code that should have been testing for
20067 invalid sockets using the SOCKET_OK macro. Required for a fix
20068 for bug 4533. Bugfix on 0.2.2.28-beta.
20069 - Fix an assertion failure when, while running with bufferevents, a
20070 connection finishes connecting after it is marked for close, but
20071 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
20072 - test_util_spawn_background_ok() hardcoded the expected value
20073 for ENOENT to 2. This isn't portable as error numbers are
20074 platform specific, and particularly the hurd has ENOENT at
20075 0x40000002. Construct expected string at runtime, using the correct
20076 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
20077 - Reject attempts to disable DisableDebuggerAttachment while Tor is
20078 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
20079 - Use an appropriate-width type for sockets in tor-fw-helper on
20080 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
20083 - When sending or relaying a RELAY_EARLY cell, we used to convert
20084 it to a RELAY cell if the connection was using the v1 link
20085 protocol. This was a workaround for older versions of Tor, which
20086 didn't handle RELAY_EARLY cells properly. Now that all supported
20087 versions can handle RELAY_EARLY cells, and now that we're enforcing
20088 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
20089 remove this workaround. Addresses bug 4786.
20091 o Code simplifications and refactoring:
20092 - Use OpenSSL's built-in SSL_state_string_long() instead of our
20093 own homebrewed ssl_state_to_string() replacement. Patch from
20094 Emile Snyder. Fixes bug 4653.
20095 - Use macros to indicate OpenSSL versions, so we don't need to worry
20096 about accidental hexadecimal bit shifts.
20097 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
20099 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
20100 - Use the smartlist_add_asprintf() alias more consistently.
20101 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
20102 invalid value, rather than just -1.
20103 - Rename a handful of old identifiers, mostly related to crypto
20104 structures and crypto functions. By convention, our "create an
20105 object" functions are called "type_new()", our "free an object"
20106 functions are called "type_free()", and our types indicate that
20107 they are types only with a final "_t". But a handful of older
20108 types and functions broke these rules, with function names like
20109 "type_create" or "subsystem_op_type", or with type names like
20113 Changes in version 0.2.3.10-alpha - 2011-12-16
20114 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
20115 Tor's buffers code. Absolutely everybody should upgrade.
20117 The bug relied on an incorrect calculation when making data continuous
20118 in one of our IO buffers, if the first chunk of the buffer was
20119 misaligned by just the wrong amount. The miscalculation would allow an
20120 attacker to overflow a piece of heap-allocated memory. To mount this
20121 attack, the attacker would need to either open a SOCKS connection to
20122 Tor's SocksPort (usually restricted to localhost), or target a Tor
20123 instance configured to make its connections through a SOCKS proxy
20124 (which Tor does not do by default).
20126 Good security practice requires that all heap-overflow bugs should be
20127 presumed to be exploitable until proven otherwise, so we are treating
20128 this as a potential code execution attack. Please upgrade immediately!
20129 This bug does not affect bufferevents-based builds of Tor. Special
20130 thanks to "Vektor" for reporting this issue to us!
20132 This release also contains a few minor bugfixes for issues discovered
20136 - Fix a heap overflow bug that could occur when trying to pull
20137 data into the first chunk of a buffer, when that chunk had
20138 already had some data drained from it. Fixes CVE-2011-2778;
20139 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20142 - If we can't attach streams to a rendezvous circuit when we
20143 finish connecting to a hidden service, clear the rendezvous
20144 circuit's stream-isolation state and try to attach streams
20145 again. Previously, we cleared rendezvous circuits' isolation
20146 state either too early (if they were freshly built) or not at all
20147 (if they had been built earlier and were cannibalized). Bugfix on
20148 0.2.3.3-alpha; fixes bug 4655.
20149 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
20150 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
20151 - Fix an assertion failure when a relay with accounting enabled
20152 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
20155 - Update to the December 6 2011 Maxmind GeoLite Country database.
20158 Changes in version 0.2.2.35 - 2011-12-16
20159 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
20160 buffers code. Absolutely everybody should upgrade.
20162 The bug relied on an incorrect calculation when making data continuous
20163 in one of our IO buffers, if the first chunk of the buffer was
20164 misaligned by just the wrong amount. The miscalculation would allow an
20165 attacker to overflow a piece of heap-allocated memory. To mount this
20166 attack, the attacker would need to either open a SOCKS connection to
20167 Tor's SocksPort (usually restricted to localhost), or target a Tor
20168 instance configured to make its connections through a SOCKS proxy
20169 (which Tor does not do by default).
20171 Good security practice requires that all heap-overflow bugs should be
20172 presumed to be exploitable until proven otherwise, so we are treating
20173 this as a potential code execution attack. Please upgrade immediately!
20174 This bug does not affect bufferevents-based builds of Tor. Special
20175 thanks to "Vektor" for reporting this issue to us!
20177 Tor 0.2.2.35 also fixes several bugs in previous versions, including
20178 crash bugs for unusual configurations, and a long-term bug that
20179 would prevent Tor from starting on Windows machines with draconian
20182 With this release, we remind everyone that 0.2.0.x has reached its
20183 formal end-of-life. Those Tor versions have many known flaws, and
20184 nobody should be using them. You should upgrade -- ideally to the
20185 0.2.2.x series. If you're using a Linux or BSD and its packages are
20186 obsolete, stop using those packages and upgrade anyway.
20188 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
20189 longer receive support after some time in early 2012.
20192 - Fix a heap overflow bug that could occur when trying to pull
20193 data into the first chunk of a buffer, when that chunk had
20194 already had some data drained from it. Fixes CVE-2011-2778;
20195 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20196 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20197 that it doesn't attempt to allocate a socketpair. This could cause
20198 some problems on Windows systems with overzealous firewalls. Fix for
20199 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20201 - If we mark an OR connection for close based on a cell we process,
20202 don't process any further cells on it. We already avoid further
20203 reads on marked-for-close connections, but now we also discard the
20204 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20205 which was the first version where we might mark a connection for
20206 close based on processing a cell on it.
20207 - Correctly sanity-check that we don't underflow on a memory
20208 allocation (and then assert) for hidden service introduction
20209 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20210 bugfix on 0.2.1.5-alpha.
20211 - Fix a memory leak when we check whether a hidden service
20212 descriptor has any usable introduction points left. Fixes bug
20213 4424. Bugfix on 0.2.2.25-alpha.
20214 - Don't crash when we're running as a relay and don't have a GeoIP
20215 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
20216 we've had in the 0.2.3.x branch already.
20217 - When running as a client, do not print a misleading (and plain
20218 wrong) log message that we're collecting "directory request"
20219 statistics: clients don't collect statistics. Also don't create a
20220 useless (because empty) stats file in the stats/ directory. Fixes
20221 bug 4353; bugfix on 0.2.2.34.
20224 - Detect failure to initialize Libevent. This fix provides better
20225 detection for future instances of bug 4457.
20226 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20227 function. This was eating up hideously large amounts of time on some
20228 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20229 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20230 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20232 - Don't warn about unused log_mutex in log.c when building with
20233 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20234 0.1.0.6-rc which introduced --disable-threads.
20235 - When configuring, starting, or stopping an NT service, stop
20236 immediately after the service configuration attempt has succeeded
20237 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20238 - When sending a NETINFO cell, include the original address
20239 received for the other side, not its canonical address. Found
20240 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20241 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
20242 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20243 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20244 occurred when a client tried to fetch a descriptor for a bridge
20245 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20246 - Backport fixes for a pair of compilation warnings on Windows.
20247 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
20248 - If we had ever tried to call tor_addr_to_str on an address of
20249 unknown type, we would have done a strdup on an uninitialized
20250 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20251 Reported by "troll_un".
20252 - Correctly detect and handle transient lookup failures from
20253 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20254 Reported by "troll_un".
20255 - Fix null-pointer access that could occur if TLS allocation failed.
20256 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20257 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20258 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20261 - Add two new config options for directory authorities:
20262 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20263 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20264 that is always sufficient to satisfy the bandwidth requirement for
20265 the Guard flag. Now it will be easier for researchers to simulate
20266 Tor networks with different values. Resolves ticket 4484.
20267 - When Tor ignores a hidden service specified in its configuration,
20268 include the hidden service's directory in the warning message.
20269 Previously, we would only tell the user that some hidden service
20270 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20271 - Update to the December 6 2011 Maxmind GeoLite Country database.
20273 o Packaging changes:
20274 - Make it easier to automate expert package builds on Windows,
20275 by removing an absolute path from makensis.exe command.
20278 Changes in version 0.2.1.32 - 2011-12-16
20279 Tor 0.2.1.32 backports important security and privacy fixes for
20280 oldstable. This release is intended only for package maintainers and
20281 others who cannot use the 0.2.2 stable series. All others should be
20282 using Tor 0.2.2.x or newer.
20284 The Tor 0.2.1.x series will reach formal end-of-life some time in
20285 early 2012; we will stop releasing patches for it then.
20287 o Major bugfixes (also included in 0.2.2.x):
20288 - Correctly sanity-check that we don't underflow on a memory
20289 allocation (and then assert) for hidden service introduction
20290 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20291 bugfix on 0.2.1.5-alpha.
20292 - Fix a heap overflow bug that could occur when trying to pull
20293 data into the first chunk of a buffer, when that chunk had
20294 already had some data drained from it. Fixes CVE-2011-2778;
20295 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20298 - Update to the December 6 2011 Maxmind GeoLite Country database.
20301 Changes in version 0.2.3.9-alpha - 2011-12-08
20302 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
20303 a "DisableNetwork" security feature that bundles can use to avoid
20304 touching the network until bridges are configured, moves forward on
20305 the pluggable transport design, fixes a flaw in the hidden service
20306 design that unnecessarily prevented clients with wrong clocks from
20307 reaching hidden services, and fixes a wide variety of other issues.
20310 - Clients can now connect to private bridges over IPv6. Bridges
20311 still need at least one IPv4 address in order to connect to
20312 other relays. Note that we don't yet handle the case where the
20313 user has two bridge lines for the same bridge (one IPv4, one
20314 IPv6). Implements parts of proposal 186.
20315 - New "DisableNetwork" config option to prevent Tor from launching any
20316 connections or accepting any connections except on a control port.
20317 Bundles and controllers can set this option before letting Tor talk
20318 to the rest of the network, for example to prevent any connections
20319 to a non-bridge address. Packages like Orbot can also use this
20320 option to instruct Tor to save power when the network is off.
20321 - Clients and bridges can now be configured to use a separate
20322 "transport" proxy. This approach makes the censorship arms race
20323 easier by allowing bridges to use protocol obfuscation plugins. It
20324 implements the "managed proxy" part of proposal 180 (ticket 3472).
20325 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
20326 implementation. It makes AES_CTR about 7% faster than our old one
20327 (which was about 10% faster than the one OpenSSL used to provide).
20328 Resolves ticket 4526.
20329 - Add a "tor2web mode" for clients that want to connect to hidden
20330 services non-anonymously (and possibly more quickly). As a safety
20331 measure to try to keep users from turning this on without knowing
20332 what they are doing, tor2web mode must be explicitly enabled at
20333 compile time, and a copy of Tor compiled to run in tor2web mode
20334 cannot be used as a normal Tor client. Implements feature 2553.
20335 - Add experimental support for running on Windows with IOCP and no
20336 kernel-space socket buffers. This feature is controlled by a new
20337 "UserspaceIOCPBuffers" config option (off by default), which has
20338 no effect unless Tor has been built with support for bufferevents,
20339 is running on Windows, and has enabled IOCP. This may, in the long
20340 run, help solve or mitigate bug 98.
20341 - Use a more secure consensus parameter voting algorithm. Now at
20342 least three directory authorities or a majority of them must
20343 vote on a given parameter before it will be included in the
20344 consensus. Implements proposal 178.
20347 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
20348 They used to check that the timestamp was within 30 minutes
20349 of their system clock, so they could cap the size of their
20350 replay-detection cache, but that approach unnecessarily refused
20351 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
20352 the v3 intro-point protocol (the first one which sent a timestamp
20353 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
20354 - Only use the EVP interface when AES acceleration is enabled,
20355 to avoid a 5-7% performance regression. Resolves issue 4525;
20356 bugfix on 0.2.3.8-alpha.
20358 o Privacy/anonymity features (bridge detection):
20359 - Make bridge SSL certificates a bit more stealthy by using random
20360 serial numbers, in the same fashion as OpenSSL when generating
20361 self-signed certificates. Implements ticket 4584.
20362 - Introduce a new config option "DynamicDHGroups", enabled by
20363 default, which provides each bridge with a unique prime DH modulus
20364 to be used during SSL handshakes. This option attempts to help
20365 against censors who might use the Apache DH modulus as a static
20366 identifier for bridges. Addresses ticket 4548.
20368 o Minor features (new/different config options):
20369 - New configuration option "DisableDebuggerAttachment" (on by default)
20370 to prevent basic debugging attachment attempts by other processes.
20371 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
20372 - Allow MapAddress directives to specify matches against super-domains,
20373 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
20374 Implements issue 933.
20375 - Slightly change behavior of "list" options (that is, config
20376 options that can appear more than once) when they appear both in
20377 torrc and on the command line. Previously, the command-line options
20378 would be appended to the ones from torrc. Now, the command-line
20379 options override the torrc options entirely. This new behavior
20380 allows the user to override list options (like exit policies and
20381 ports to listen on) from the command line, rather than simply
20382 appending to the list.
20383 - You can get the old (appending) command-line behavior for "list"
20384 options by prefixing the option name with a "+".
20385 - You can remove all the values for a "list" option from the command
20386 line without adding any new ones by prefixing the option name
20388 - Add experimental support for a "defaults" torrc file to be parsed
20389 before the regular torrc. Torrc options override the defaults file's
20390 options in the same way that the command line overrides the torrc.
20391 The SAVECONF controller command saves only those options which
20392 differ between the current configuration and the defaults file. HUP
20393 reloads both files. (Note: This is an experimental feature; its
20394 behavior will probably be refined in future 0.2.3.x-alpha versions
20395 to better meet packagers' needs.) Implements task 4552.
20398 - Try to make the introductory warning message that Tor prints on
20399 startup more useful for actually finding help and information.
20400 Resolves ticket 2474.
20401 - Running "make version" now displays the version of Tor that
20402 we're about to build. Idea from katmagic; resolves issue 4400.
20403 - Expire old or over-used hidden service introduction points.
20404 Required by fix for bug 3460.
20405 - Move the replay-detection cache for the RSA-encrypted parts of
20406 INTRODUCE2 cells to the introduction point data structures.
20407 Previously, we would use one replay-detection cache per hidden
20408 service. Required by fix for bug 3460.
20409 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
20410 public key replay-detection cache from 60 minutes to 5 minutes. This
20411 replay-detection cache is now used only to detect multiple
20412 INTRODUCE2 cells specifying the same rendezvous point, so we can
20413 avoid launching multiple simultaneous attempts to connect to it.
20415 o Minor bugfixes (on Tor 0.2.2.x and earlier):
20416 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20417 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20419 - Fix a minor formatting issue in one of tor-gencert's error messages.
20421 - Prevent a false positive from the check-spaces script, by disabling
20422 the "whitespace between function name and (" check for functions
20424 - Fix a log message suggesting that people contact a non-existent
20425 email address. Fixes bug 3448.
20426 - Fix null-pointer access that could occur if TLS allocation failed.
20427 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20428 - Report a real bootstrap problem to the controller on router
20429 identity mismatch. Previously we just said "foo", which probably
20430 made a lot of sense at the time. Fixes bug 4169; bugfix on
20432 - If we had ever tried to call tor_addr_to_str() on an address of
20433 unknown type, we would have done a strdup() on an uninitialized
20434 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20435 Reported by "troll_un".
20436 - Correctly detect and handle transient lookup failures from
20437 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20438 Reported by "troll_un".
20439 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20440 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20441 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
20442 bug 4532; found by "troll_un".
20444 o Minor bugfixes (on Tor 0.2.3.x):
20445 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
20447 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
20448 circuit for use as a hidden service client's rendezvous point.
20449 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
20450 with help from wanoskarnet.
20451 - Restore behavior of overriding SocksPort, ORPort, and similar
20452 options from the command line. Bugfix on 0.2.3.3-alpha.
20455 - Properly handle the case where the build-tree is not the same
20456 as the source tree when generating src/common/common_sha1.i,
20457 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
20458 bugfix on 0.2.0.1-alpha.
20460 o Code simplifications, cleanups, and refactorings:
20461 - Remove the pure attribute from all functions that used it
20462 previously. In many cases we assigned it incorrectly, because the
20463 functions might assert or call impure functions, and we don't have
20464 evidence that keeping the pure attribute is worthwhile. Implements
20465 changes suggested in ticket 4421.
20466 - Remove some dead code spotted by coverity. Fixes cid 432.
20467 Bugfix on 0.2.3.1-alpha, closes bug 4637.
20470 Changes in version 0.2.3.8-alpha - 2011-11-22
20471 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
20472 socketpair-related bug that has been bothering Windows users. It adds
20473 support to serve microdescriptors to controllers, so Vidalia's network
20474 map can resume listing relays (once Vidalia implements its side),
20475 and adds better support for hardware AES acceleration. Finally, it
20476 starts the process of adjusting the bandwidth cutoff for getting the
20477 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
20478 that tiny relays harm performance more than they help network capacity.
20481 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20482 that it doesn't attempt to allocate a socketpair. This could cause
20483 some problems on Windows systems with overzealous firewalls. Fix for
20484 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20486 - Correctly sanity-check that we don't underflow on a memory
20487 allocation (and then assert) for hidden service introduction
20488 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20489 bugfix on 0.2.1.5-alpha.
20490 - Remove the artificially low cutoff of 20KB to guarantee the Fast
20491 flag. In the past few years the average relay speed has picked
20492 up, and while the "top 7/8 of the network get the Fast flag" and
20493 "all relays with 20KB or more of capacity get the Fast flag" rules
20494 used to have the same result, now the top 7/8 of the network has
20495 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
20496 - Fix a rare assertion failure when checking whether a v0 hidden
20497 service descriptor has any usable introduction points left, and
20498 we don't have enough information to build a circuit to the first
20499 intro point named in the descriptor. The HS client code in
20500 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
20501 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
20502 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
20503 - Make bridge authorities not crash when they are asked for their own
20504 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
20505 - When running as a client, do not print a misleading (and plain
20506 wrong) log message that we're collecting "directory request"
20507 statistics: clients don't collect statistics. Also don't create a
20508 useless (because empty) stats file in the stats/ directory. Fixes
20509 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
20512 - Allow Tor controllers like Vidalia to obtain the microdescriptor
20513 for a relay by identity digest or nickname. Previously,
20514 microdescriptors were only available by their own digests, so a
20515 controller would have to ask for and parse the whole microdescriptor
20516 consensus in order to look up a single relay's microdesc. Fixes
20517 bug 3832; bugfix on 0.2.3.1-alpha.
20518 - Use OpenSSL's EVP interface for AES encryption, so that all AES
20519 operations can use hardware acceleration (if present). Resolves
20522 o Minor bugfixes (on 0.2.2.x and earlier):
20523 - Detect failure to initialize Libevent. This fix provides better
20524 detection for future instances of bug 4457.
20525 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20526 function. This was eating up hideously large amounts of time on some
20527 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20528 - Don't warn about unused log_mutex in log.c when building with
20529 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20530 0.1.0.6-rc which introduced --disable-threads.
20531 - Allow manual 'authenticate' commands to the controller interface
20532 from netcat (nc) as well as telnet. We were rejecting them because
20533 they didn't come with the expected whitespace at the end of the
20534 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
20535 - Fix some (not actually triggerable) buffer size checks in usage of
20536 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
20538 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
20539 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
20540 - When configuring, starting, or stopping an NT service, stop
20541 immediately after the service configuration attempt has succeeded
20542 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20543 - When sending a NETINFO cell, include the original address
20544 received for the other side, not its canonical address. Found
20545 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20546 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
20547 can pick them up when the tests aren't disabled. Bugfix on
20548 0.2.2.4-alpha which introduced tinytest.
20549 - Fix a memory leak when we check whether a hidden service
20550 descriptor has any usable introduction points left. Fixes bug
20551 4424. Bugfix on 0.2.2.25-alpha.
20552 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20553 occurred when a client tried to fetch a descriptor for a bridge
20554 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20556 o Minor bugfixes (on 0.2.3.x):
20557 - Make util unit tests build correctly with MSVC. Bugfix on
20558 0.2.3.3-alpha. Patch by Gisle Vanem.
20559 - Successfully detect AUTH_CHALLENGE cells with no recognized
20560 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
20561 Found by frosty_un.
20562 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
20563 it should still send a NETINFO cell to allow the connection to
20564 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
20566 - Log less loudly when we get an invalid authentication certificate
20567 from a source other than a directory authority: it's not unusual
20568 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
20570 - Tolerate servers with more clock skew in their authentication
20571 certificates than previously. Fixes bug 4371; bugfix on
20573 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
20574 on 0.2.3.4-alpha and 0.2.3.6-alpha.
20577 - Add two new config options for directory authorities:
20578 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20579 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20580 that is always sufficient to satisfy the bandwidth requirement for
20581 the Guard flag. Now it will be easier for researchers to simulate
20582 Tor networks with different values. Resolves ticket 4484.
20583 - When Tor ignores a hidden service specified in its configuration,
20584 include the hidden service's directory in the warning message.
20585 Previously, we would only tell the user that some hidden service
20586 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20587 - When we fail to initialize Libevent, retry with IOCP disabled so we
20588 don't need to turn on multi-threading support in Libevent, which in
20589 turn requires a working socketpair(). This is a workaround for bug
20590 4457, which affects Libevent versions from 2.0.1-alpha through
20592 - Detect when we try to build on a platform that doesn't define
20593 AF_UNSPEC to 0. We don't work there, so refuse to compile.
20594 - Update to the November 1 2011 Maxmind GeoLite Country database.
20596 o Packaging changes:
20597 - Make it easier to automate expert package builds on Windows,
20598 by removing an absolute path from makensis.exe command.
20600 o Code simplifications and refactoring:
20601 - Remove some redundant #include directives throughout the code.
20602 Patch from Andrea Gelmini.
20603 - Unconditionally use OpenSSL's AES implementation instead of our
20604 old built-in one. OpenSSL's AES has been better for a while, and
20605 relatively few servers should still be on any version of OpenSSL
20606 that doesn't have good optimized assembly AES.
20607 - Use the name "CERTS" consistently to refer to the new cell type;
20608 we were calling it CERT in some places and CERTS in others.
20611 - Numerous new unit tests for functions in util.c and address.c by
20613 - The long-disabled benchmark tests are now split into their own
20614 ./src/test/bench binary.
20615 - The benchmark tests can now use more accurate timers than
20616 gettimeofday() when such timers are available.
20619 Changes in version 0.2.3.7-alpha - 2011-10-30
20620 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
20621 the new v3 handshake. It also resolves yet another bridge address
20625 - If we mark an OR connection for close based on a cell we process,
20626 don't process any further cells on it. We already avoid further
20627 reads on marked-for-close connections, but now we also discard the
20628 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20629 which was the first version where we might mark a connection for
20630 close based on processing a cell on it.
20631 - Fix a double-free bug that would occur when we received an invalid
20632 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
20633 bugfix on 0.2.3.6-alpha.
20634 - Bridges no longer include their address in NETINFO cells on outgoing
20635 OR connections, to allow them to blend in better with clients.
20636 Removes another avenue for enumerating bridges. Reported by
20637 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
20638 cells were introduced.
20641 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
20642 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20645 Changes in version 0.2.3.6-alpha - 2011-10-26
20646 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
20647 anonymity vulnerability where an attacker can deanonymize Tor
20648 users. Everybody should upgrade.
20650 This release also features support for a new v3 connection handshake
20651 protocol, and fixes to make hidden service connections more robust.
20654 - Implement a new handshake protocol (v3) for authenticating Tors to
20655 each other over TLS. It should be more resistant to fingerprinting
20656 than previous protocols, and should require less TLS hacking for
20657 future Tor implementations. Implements proposal 176.
20658 - Allow variable-length padding cells to disguise the length of
20659 Tor's TLS records. Implements part of proposal 184.
20661 o Privacy/anonymity fixes (clients):
20662 - Clients and bridges no longer send TLS certificate chains on
20663 outgoing OR connections. Previously, each client or bridge would
20664 use the same cert chain for all outgoing OR connections until
20665 its IP address changes, which allowed any relay that the client
20666 or bridge contacted to determine which entry guards it is using.
20667 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20668 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20669 no longer considers that connection as suitable for satisfying a
20670 circuit EXTEND request. Now relays can protect clients from the
20671 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20672 - Directory authorities no longer assign the Guard flag to relays
20673 that haven't upgraded to the above "refuse EXTEND requests
20674 to client connections" fix. Now directory authorities can
20675 protect clients from the CVE-2011-2768 issue even if neither
20676 the clients nor the relays have upgraded yet. There's a new
20677 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20678 to let us transition smoothly, else tomorrow there would be no
20681 o Major bugfixes (hidden services):
20682 - Improve hidden service robustness: when an attempt to connect to
20683 a hidden service ends, be willing to refetch its hidden service
20684 descriptors from each of the HSDir relays responsible for them
20685 immediately. Previously, we would not consider refetching the
20686 service's descriptors from each HSDir for 15 minutes after the last
20687 fetch, which was inconvenient if the hidden service was not running
20688 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
20689 - When one of a hidden service's introduction points appears to be
20690 unreachable, stop trying it. Previously, we would keep trying
20691 to build circuits to the introduction point until we lost the
20692 descriptor, usually because the user gave up and restarted Tor.
20693 Partly fixes bug 3825.
20694 - Don't launch a useless circuit after failing to use one of a
20695 hidden service's introduction points. Previously, we would
20696 launch a new introduction circuit, but not set the hidden service
20697 which that circuit was intended to connect to, so it would never
20698 actually be used. A different piece of code would then create a
20699 new introduction circuit correctly. Bug reported by katmagic and
20700 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20702 o Major bugfixes (other):
20703 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20704 that they initiated. Relays could distinguish incoming bridge
20705 connections from client connections, creating another avenue for
20706 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20707 Found by "frosty_un".
20708 - Don't update the AccountingSoftLimitHitAt state file entry whenever
20709 tor gets started. This prevents a wrong average bandwidth
20710 estimate, which would cause relays to always start a new accounting
20711 interval at the earliest possible moment. Fixes bug 2003; bugfix
20712 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
20713 immensely in tracking this bug down.
20714 - Fix a crash bug when changing node restrictions while a DNS lookup
20715 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20718 o Minor bugfixes (on 0.2.2.x and earlier):
20719 - When a hidden service turns an extra service-side introduction
20720 circuit into a general-purpose circuit, free the rend_data and
20721 intro_key fields first, so we won't leak memory if the circuit
20722 is cannibalized for use as another service-side introduction
20723 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20724 - Rephrase the log message emitted if the TestSocks check is
20725 successful. Patch from Fabian Keil; fixes bug 4094.
20726 - Bridges now skip DNS self-tests, to act a little more stealthily.
20727 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20728 bridges. Patch by "warms0x".
20729 - Remove a confusing dollar sign from the example fingerprint in the
20730 man page, and also make the example fingerprint a valid one. Fixes
20731 bug 4309; bugfix on 0.2.1.3-alpha.
20732 - Fix internal bug-checking logic that was supposed to catch
20733 failures in digest generation so that it will fail more robustly
20734 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20735 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20736 - Report any failure in init_keys() calls launched because our
20737 IP address has changed. Spotted by Coverity Scan. Bugfix on
20738 0.1.1.4-alpha; fixes CID 484.
20740 o Minor bugfixes (on 0.2.3.x):
20741 - Fix a bug in configure.in that kept it from building a configure
20742 script with autoconf versions earlier than 2.61. Fixes bug 2430;
20743 bugfix on 0.2.3.1-alpha.
20744 - Don't warn users that they are exposing a client port to the
20745 Internet if they have specified an RFC1918 address. Previously,
20746 we would warn if the user had specified any non-loopback
20747 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
20748 - Fix memory leaks in the failing cases of the new SocksPort and
20749 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
20750 fixes coverity CIDs 485, 486, and 487.
20753 - When a hidden service's introduction point times out, consider
20754 trying it again during the next attempt to connect to the
20755 HS. Previously, we would not try it again unless a newly fetched
20756 descriptor contained it. Required by fixes for bugs 1297 and 3825.
20757 - The next version of Windows will be called Windows 8, and it has
20758 a major version of 6, minor version of 2. Correctly identify that
20759 version instead of calling it "Very recent version". Resolves
20760 ticket 4153; reported by funkstar.
20761 - The Bridge Authority now writes statistics on how many bridge
20762 descriptors it gave out in total, and how many unique descriptors
20763 it gave out. It also lists how often the most and least commonly
20764 fetched descriptors were given out, as well as the median and
20765 25th/75th percentile. Implements tickets 4200 and 4294.
20766 - Update to the October 4 2011 Maxmind GeoLite Country database.
20768 o Code simplifications and refactoring:
20769 - Remove some old code to remember statistics about which descriptors
20770 we've served as a directory mirror. The feature wasn't used and
20771 is outdated now that microdescriptors are around.
20772 - Rename Tor functions that turn strings into addresses, so that
20773 "parse" indicates that no hostname resolution occurs, and
20774 "lookup" indicates that hostname resolution may occur. This
20775 should help prevent mistakes in the future. Fixes bug 3512.
20778 Changes in version 0.2.2.34 - 2011-10-26
20779 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
20780 can deanonymize Tor users. Everybody should upgrade.
20782 The attack relies on four components: 1) Clients reuse their TLS cert
20783 when talking to different relays, so relays can recognize a user by
20784 the identity key in her cert. 2) An attacker who knows the client's
20785 identity key can probe each guard relay to see if that identity key
20786 is connected to that guard relay right now. 3) A variety of active
20787 attacks in the literature (starting from "Low-Cost Traffic Analysis
20788 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
20789 discover the guard relays that a Tor user visiting the website is using.
20790 4) Clients typically pick three guards at random, so the set of guards
20791 for a given user could well be a unique fingerprint for her. This
20792 release fixes components #1 and #2, which is enough to block the attack;
20793 the other two remain as open research problems. Special thanks to
20794 "frosty_un" for reporting the issue to us!
20796 Clients should upgrade so they are no longer recognizable by the TLS
20797 certs they present. Relays should upgrade so they no longer allow a
20798 remote attacker to probe them to test whether unpatched clients are
20799 currently connected to them.
20801 This release also fixes several vulnerabilities that allow an attacker
20802 to enumerate bridge relays. Some bridge enumeration attacks still
20803 remain; see for example proposal 188.
20805 o Privacy/anonymity fixes (clients):
20806 - Clients and bridges no longer send TLS certificate chains on
20807 outgoing OR connections. Previously, each client or bridge would
20808 use the same cert chain for all outgoing OR connections until
20809 its IP address changes, which allowed any relay that the client
20810 or bridge contacted to determine which entry guards it is using.
20811 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20812 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20813 no longer considers that connection as suitable for satisfying a
20814 circuit EXTEND request. Now relays can protect clients from the
20815 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20816 - Directory authorities no longer assign the Guard flag to relays
20817 that haven't upgraded to the above "refuse EXTEND requests
20818 to client connections" fix. Now directory authorities can
20819 protect clients from the CVE-2011-2768 issue even if neither
20820 the clients nor the relays have upgraded yet. There's a new
20821 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20822 to let us transition smoothly, else tomorrow there would be no
20825 o Privacy/anonymity fixes (bridge enumeration):
20826 - Bridge relays now do their directory fetches inside Tor TLS
20827 connections, like all the other clients do, rather than connecting
20828 directly to the DirPort like public relays do. Removes another
20829 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20830 - Bridges relays now build circuits for themselves in a more similar
20831 way to how clients build them. Removes another avenue for
20832 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20833 when bridges were introduced.
20834 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20835 that they initiated. Relays could distinguish incoming bridge
20836 connections from client connections, creating another avenue for
20837 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20838 Found by "frosty_un".
20841 - Fix a crash bug when changing node restrictions while a DNS lookup
20842 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20844 - Don't launch a useless circuit after failing to use one of a
20845 hidden service's introduction points. Previously, we would
20846 launch a new introduction circuit, but not set the hidden service
20847 which that circuit was intended to connect to, so it would never
20848 actually be used. A different piece of code would then create a
20849 new introduction circuit correctly. Bug reported by katmagic and
20850 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20853 - Change an integer overflow check in the OpenBSD_Malloc code so
20854 that GCC is less likely to eliminate it as impossible. Patch
20855 from Mansour Moufid. Fixes bug 4059.
20856 - When a hidden service turns an extra service-side introduction
20857 circuit into a general-purpose circuit, free the rend_data and
20858 intro_key fields first, so we won't leak memory if the circuit
20859 is cannibalized for use as another service-side introduction
20860 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20861 - Bridges now skip DNS self-tests, to act a little more stealthily.
20862 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20863 bridges. Patch by "warms0x".
20864 - Fix internal bug-checking logic that was supposed to catch
20865 failures in digest generation so that it will fail more robustly
20866 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20867 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20868 - Report any failure in init_keys() calls launched because our
20869 IP address has changed. Spotted by Coverity Scan. Bugfix on
20870 0.1.1.4-alpha; fixes CID 484.
20872 o Minor bugfixes (log messages and documentation):
20873 - Remove a confusing dollar sign from the example fingerprint in the
20874 man page, and also make the example fingerprint a valid one. Fixes
20875 bug 4309; bugfix on 0.2.1.3-alpha.
20876 - The next version of Windows will be called Windows 8, and it has
20877 a major version of 6, minor version of 2. Correctly identify that
20878 version instead of calling it "Very recent version". Resolves
20879 ticket 4153; reported by funkstar.
20880 - Downgrade log messages about circuit timeout calibration from
20881 "notice" to "info": they don't require or suggest any human
20882 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20883 bugfix on 0.2.2.14-alpha.
20886 - Turn on directory request statistics by default and include them in
20887 extra-info descriptors. Don't break if we have no GeoIP database.
20888 Backported from 0.2.3.1-alpha; implements ticket 3951.
20889 - Update to the October 4 2011 Maxmind GeoLite Country database.
20892 Changes in version 0.2.1.31 - 2011-10-26
20893 Tor 0.2.1.31 backports important security and privacy fixes for
20894 oldstable. This release is intended only for package maintainers and
20895 others who cannot use the 0.2.2 stable series. All others should be
20896 using Tor 0.2.2.x or newer.
20898 o Security fixes (also included in 0.2.2.x):
20899 - Replace all potentially sensitive memory comparison operations
20900 with versions whose runtime does not depend on the data being
20901 compared. This will help resist a class of attacks where an
20902 adversary can use variations in timing information to learn
20903 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20904 implementation by Robert Ransom based partially on code by DJB.)
20905 - Fix an assert in parsing router descriptors containing IPv6
20906 addresses. This one took down the directory authorities when
20907 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
20909 o Privacy/anonymity fixes (also included in 0.2.2.x):
20910 - Clients and bridges no longer send TLS certificate chains on
20911 outgoing OR connections. Previously, each client or bridge would
20912 use the same cert chain for all outgoing OR connections until
20913 its IP address changes, which allowed any relay that the client
20914 or bridge contacted to determine which entry guards it is using.
20915 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20916 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20917 no longer considers that connection as suitable for satisfying a
20918 circuit EXTEND request. Now relays can protect clients from the
20919 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20920 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20921 that they initiated. Relays could distinguish incoming bridge
20922 connections from client connections, creating another avenue for
20923 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20924 Found by "frosty_un".
20925 - When receiving a hidden service descriptor, check that it is for
20926 the hidden service we wanted. Previously, Tor would store any
20927 hidden service descriptors that a directory gave it, whether it
20928 wanted them or not. This wouldn't have let an attacker impersonate
20929 a hidden service, but it did let directories pre-seed a client
20930 with descriptors that it didn't want. Bugfix on 0.0.6.
20931 - Avoid linkability based on cached hidden service descriptors: forget
20932 all hidden service descriptors cached as a client when processing a
20933 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20934 - Make the bridge directory authority refuse to answer directory
20935 requests for "all" descriptors. It used to include bridge
20936 descriptors in its answer, which was a major information leak.
20937 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20938 - Don't attach new streams to old rendezvous circuits after SIGNAL
20939 NEWNYM. Previously, we would keep using an existing rendezvous
20940 circuit if it remained open (i.e. if it were kept open by a
20941 long-lived stream, or if a new stream were attached to it before
20942 Tor could notice that it was old and no longer in use). Bugfix on
20943 0.1.1.15-rc; fixes bug 3375.
20945 o Minor bugfixes (also included in 0.2.2.x):
20946 - When we restart our relay, we might get a successful connection
20947 from the outside before we've started our reachability tests,
20948 triggering a warning: "ORPort found reachable, but I have no
20949 routerinfo yet. Failing to inform controller of success." This
20950 bug was harmless unless Tor is running under a controller
20951 like Vidalia, in which case the controller would never get a
20952 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20954 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20955 enabled. Fixes bug 1526.
20956 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20957 anything since 0.2.1.16-rc.
20958 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20959 None of the cases where we did this before were wrong, but by making
20960 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20961 - Fix a rare crash bug that could occur when a client was configured
20962 with a large number of bridges. Fixes bug 2629; bugfix on
20963 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20964 - Correct the warning displayed when a rendezvous descriptor exceeds
20965 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20967 - Fix an uncommon assertion failure when running with DNSPort under
20968 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20969 - When warning about missing zlib development packages during compile,
20970 give the correct package names. Bugfix on 0.2.0.1-alpha.
20971 - Require that introduction point keys and onion keys have public
20972 exponent 65537. Bugfix on 0.2.0.10-alpha.
20973 - Do not crash when our configuration file becomes unreadable, for
20974 example due to a permissions change, between when we start up
20975 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20977 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20979 - Always NUL-terminate the sun_path field of a sockaddr_un before
20980 passing it to the kernel. (Not a security issue: kernels are
20981 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20982 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20983 - Don't stack-allocate the list of supplementary GIDs when we're
20984 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20985 could take up to 256K, which is way too much stack. Found by
20986 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20988 o Minor bugfixes (only in 0.2.1.x):
20989 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
20990 rely on them. Bugfix on 0.2.1.30.
20991 - Use git revisions instead of svn revisions when generating our
20992 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20994 o Minor features (also included in 0.2.2.x):
20995 - Adjust the expiration time on our SSL session certificates to
20996 better match SSL certs seen in the wild. Resolves ticket 4014.
20997 - Allow nameservers with IPv6 address. Resolves bug 2574.
20998 - Update to the October 4 2011 Maxmind GeoLite Country database.
21001 Changes in version 0.2.3.5-alpha - 2011-09-28
21002 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
21003 bridge relays; fixes an assertion error that many users started hitting
21004 today; and adds the ability to refill token buckets more often than
21005 once per second, allowing significant performance improvements.
21008 - Bridge relays now do their directory fetches inside Tor TLS
21009 connections, like all the other clients do, rather than connecting
21010 directly to the DirPort like public relays do. Removes another
21011 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
21012 - Bridges relays now build circuits for themselves in a more similar
21013 way to how clients build them. Removes another avenue for
21014 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
21015 when bridges were introduced.
21018 - Fix an "Assertion md->held_by_node == 1 failed" error that could
21019 occur when the same microdescriptor was referenced by two node_t
21020 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
21022 o Major features (networking):
21023 - Add a new TokenBucketRefillInterval option to refill token buckets
21024 more frequently than once per second. This should improve network
21025 performance, alleviate queueing problems, and make traffic less
21026 bursty. Implements proposal 183; closes ticket 3630. Design by
21027 Florian Tschorsch and Björn Scheuermann; implementation by
21031 - Change an integer overflow check in the OpenBSD_Malloc code so
21032 that GCC is less likely to eliminate it as impossible. Patch
21033 from Mansour Moufid. Fixes bug 4059.
21035 o Minor bugfixes (usability):
21036 - Downgrade log messages about circuit timeout calibration from
21037 "notice" to "info": they don't require or suggest any human
21038 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
21039 bugfix on 0.2.2.14-alpha.
21041 o Minor features (diagnostics):
21042 - When the system call to create a listener socket fails, log the
21043 error message explaining why. This may help diagnose bug 4027.
21046 Changes in version 0.2.3.4-alpha - 2011-09-13
21047 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
21048 tweak to Tor's TLS handshake that makes relays and bridges that run
21049 this new version reachable from Iran again. It also fixes a few new
21050 bugs in 0.2.3.x, and teaches relays to recognize when they're not
21051 listed in the network consensus and republish.
21053 o Major bugfixes (also part of 0.2.2.33):
21054 - Avoid an assertion failure when reloading a configuration with
21055 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21056 3923; bugfix on 0.2.2.25-alpha.
21058 o Minor features (security, also part of 0.2.2.33):
21059 - Check for replays of the public-key encrypted portion of an
21060 INTRODUCE1 cell, in addition to the current check for replays of
21061 the g^x value. This prevents a possible class of active attacks
21062 by an attacker who controls both an introduction point and a
21063 rendezvous point, and who uses the malleability of AES-CTR to
21064 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21065 that these attacks are infeasible (requiring the attacker to send
21066 on the order of zettabytes of altered cells in a short interval),
21067 but we'd rather block them off in case there are any classes of
21068 this attack that we missed. Reported by Willem Pinckaers.
21070 o Minor features (also part of 0.2.2.33):
21071 - Adjust the expiration time on our SSL session certificates to
21072 better match SSL certs seen in the wild. Resolves ticket 4014.
21073 - Change the default required uptime for a relay to be accepted as
21074 a HSDir (hidden service directory) from 24 hours to 25 hours.
21075 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21076 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21077 authorities to abstain from voting on assignment of the HSDir
21078 consensus flag. Related to bug 2649.
21079 - Update to the September 6 2011 Maxmind GeoLite Country database.
21081 o Minor bugfixes (also part of 0.2.2.33):
21082 - Demote the 'replay detected' log message emitted when a hidden
21083 service receives the same Diffie-Hellman public key in two different
21084 INTRODUCE2 cells to info level. A normal Tor client can cause that
21085 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21086 fixes part of bug 2442.
21087 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21088 level. There is nothing that a hidden service's operator can do
21089 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21091 - Clarify a log message specifying the characters permitted in
21092 HiddenServiceAuthorizeClient client names. Previously, the log
21093 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21094 given the impression that every ASCII character between "+" and "_"
21095 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21097 o Build fixes (also part of 0.2.2.33):
21098 - Clean up some code issues that prevented Tor from building on older
21099 BSDs. Fixes bug 3894; reported by "grarpamp".
21100 - Search for a platform-specific version of "ar" when cross-compiling.
21101 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21104 - Fix a bug where the SocksPort option (for example) would get
21105 ignored and replaced by the default if a SocksListenAddress
21106 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
21110 - Relays now try regenerating and uploading their descriptor more
21111 frequently if they are not listed in the consensus, or if the
21112 version of their descriptor listed in the consensus is too
21113 old. This fix should prevent situations where a server declines
21114 to re-publish itself because it has done so too recently, even
21115 though the authorities decided not to list its recent-enough
21116 descriptor. Fix for bug 3327.
21119 - Relays now include a reason for regenerating their descriptors
21120 in an HTTP header when uploading to the authorities. This will
21121 make it easier to debug descriptor-upload issues in the future.
21122 - When starting as root and then changing our UID via the User
21123 control option, and we have a ControlSocket configured, make sure
21124 that the ControlSocket is owned by the same account that Tor will
21125 run under. Implements ticket 3421; fix by Jérémy Bobbio.
21128 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
21129 utility function used in the control-port code). This shouldn't
21130 ever happen unless Tor is completely out of memory, but if it did
21131 happen and Tor somehow recovered from it, Tor could have sent a log
21132 message to a control port in the middle of a reply to a controller
21133 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
21134 - Make 'FetchUselessDescriptors' cause all descriptor types and
21135 all consensus types (including microdescriptors) to get fetched.
21136 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
21138 o Code refactoring:
21139 - Make a new "entry connection" struct as an internal subtype of "edge
21140 connection", to simplify the code and make exit connections smaller.
21143 Changes in version 0.2.2.33 - 2011-09-13
21144 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
21145 TLS handshake that makes relays and bridges that run this new version
21146 reachable from Iran again.
21149 - Avoid an assertion failure when reloading a configuration with
21150 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21151 3923; bugfix on 0.2.2.25-alpha.
21153 o Minor features (security):
21154 - Check for replays of the public-key encrypted portion of an
21155 INTRODUCE1 cell, in addition to the current check for replays of
21156 the g^x value. This prevents a possible class of active attacks
21157 by an attacker who controls both an introduction point and a
21158 rendezvous point, and who uses the malleability of AES-CTR to
21159 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21160 that these attacks are infeasible (requiring the attacker to send
21161 on the order of zettabytes of altered cells in a short interval),
21162 but we'd rather block them off in case there are any classes of
21163 this attack that we missed. Reported by Willem Pinckaers.
21166 - Adjust the expiration time on our SSL session certificates to
21167 better match SSL certs seen in the wild. Resolves ticket 4014.
21168 - Change the default required uptime for a relay to be accepted as
21169 a HSDir (hidden service directory) from 24 hours to 25 hours.
21170 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21171 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21172 authorities to abstain from voting on assignment of the HSDir
21173 consensus flag. Related to bug 2649.
21174 - Update to the September 6 2011 Maxmind GeoLite Country database.
21176 o Minor bugfixes (documentation and log messages):
21177 - Correct the man page to explain that HashedControlPassword and
21178 CookieAuthentication can both be set, in which case either method
21179 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21180 when we decided to allow these config options to both be set. Issue
21181 raised by bug 3898.
21182 - Demote the 'replay detected' log message emitted when a hidden
21183 service receives the same Diffie-Hellman public key in two different
21184 INTRODUCE2 cells to info level. A normal Tor client can cause that
21185 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21186 fixes part of bug 2442.
21187 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21188 level. There is nothing that a hidden service's operator can do
21189 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21191 - Clarify a log message specifying the characters permitted in
21192 HiddenServiceAuthorizeClient client names. Previously, the log
21193 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21194 given the impression that every ASCII character between "+" and "_"
21195 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21198 - Provide a substitute implementation of lround() for MSVC, which
21199 apparently lacks it. Patch from Gisle Vanem.
21200 - Clean up some code issues that prevented Tor from building on older
21201 BSDs. Fixes bug 3894; reported by "grarpamp".
21202 - Search for a platform-specific version of "ar" when cross-compiling.
21203 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21206 Changes in version 0.2.3.3-alpha - 2011-09-01
21207 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
21208 security, and provides client-side support for the microdescriptor
21209 and optimistic data features introduced earlier in the 0.2.3.x
21210 series. It also includes numerous critical bugfixes in the (optional)
21211 bufferevent-based networking backend.
21213 o Major features (stream isolation):
21214 - You can now configure Tor so that streams from different
21215 applications are isolated on different circuits, to prevent an
21216 attacker who sees your streams as they leave an exit node from
21217 linking your sessions to one another. To do this, choose some way
21218 to distinguish the applications: have them connect to different
21219 SocksPorts, or have one of them use SOCKS4 while the other uses
21220 SOCKS5, or have them pass different authentication strings to the
21221 SOCKS proxy. Then, use the new SocksPort syntax to configure the
21222 degree of isolation you need. This implements Proposal 171.
21223 - There's a new syntax for specifying multiple client ports (such as
21224 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
21225 multiple *Port entries with full addr:port syntax on each.
21226 The old *ListenAddress format is still supported, but you can't
21227 mix it with the new *Port syntax.
21229 o Major features (other):
21230 - Enable microdescriptor fetching by default for clients. This allows
21231 clients to download a much smaller amount of directory information.
21232 To disable it (and go back to the old-style consensus and
21233 descriptors), set "UseMicrodescriptors 0" in your torrc file.
21234 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
21235 "PortForwarding" config option), now supports Windows.
21236 - When using an exit relay running 0.2.3.x, clients can now
21237 "optimistically" send data before the exit relay reports that
21238 the stream has opened. This saves a round trip when starting
21239 connections where the client speaks first (such as web browsing).
21240 This behavior is controlled by a consensus parameter (currently
21241 disabled). To turn it on or off manually, use the "OptimisticData"
21242 torrc option. Implements proposal 181; code by Ian Goldberg.
21244 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
21245 - When using IOCP on Windows, we need to enable Libevent windows
21247 - The IOCP backend now works even when the user has not specified
21248 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
21249 Fixes part of bug 3752.
21250 - Correctly record the bytes we've read and written when using
21251 bufferevents, so that we can include them in our bandwidth history
21252 and advertised bandwidth. Fixes bug 3803.
21253 - Apply rate-limiting only at the bottom of a chain of filtering
21254 bufferevents. This prevents us from filling up internal read
21255 buffers and violating rate-limits when filtering bufferevents
21256 are enabled. Fixes part of bug 3804.
21257 - Add high-watermarks to the output buffers for filtered
21258 bufferevents. This prevents us from filling up internal write
21259 buffers and wasting CPU cycles when filtering bufferevents are
21260 enabled. Fixes part of bug 3804.
21261 - Correctly notice when data has been written from a bufferevent
21262 without flushing it completely. Fixes bug 3805.
21263 - Fix a bug where server-side tunneled bufferevent-based directory
21264 streams would get closed prematurely. Fixes bug 3814.
21265 - Fix a use-after-free error with per-connection rate-limiting
21266 buckets. Fixes bug 3888.
21268 o Major bugfixes (also part of 0.2.2.31-rc):
21269 - If we're configured to write our ControlPorts to disk, only write
21270 them after switching UID and creating the data directory. This way,
21271 we don't fail when starting up with a nonexistent DataDirectory
21272 and a ControlPortWriteToFile setting based on that directory. Fixes
21273 bug 3747; bugfix on Tor 0.2.2.26-beta.
21276 - Added a new CONF_CHANGED event so that controllers can be notified
21277 of any configuration changes made by other controllers, or by the
21278 user. Implements ticket 1692.
21279 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
21280 leak when using bufferevents, and lets Libevent worry about how to
21281 best copy data out of a buffer.
21282 - Replace files in stats/ rather than appending to them. Now that we
21283 include statistics in extra-info descriptors, it makes no sense to
21284 keep old statistics forever. Implements ticket 2930.
21286 o Minor features (build compatibility):
21287 - Limited, experimental support for building with nmake and MSVC.
21288 - Provide a substitute implementation of lround() for MSVC, which
21289 apparently lacks it. Patch from Gisle Vanem.
21291 o Minor features (also part of 0.2.2.31-rc):
21292 - Update to the August 2 2011 Maxmind GeoLite Country database.
21294 o Minor bugfixes (on 0.2.3.x-alpha):
21295 - Fix a spurious warning when parsing SOCKS requests with
21296 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
21297 - Get rid of a harmless warning that could happen on relays running
21298 with bufferevents. The warning was caused by someone doing an http
21299 request to a relay's orport. Also don't warn for a few related
21300 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
21302 o Minor bugfixes (on 2.2.x and earlier):
21303 - Correct the man page to explain that HashedControlPassword and
21304 CookieAuthentication can both be set, in which case either method
21305 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21306 when we decided to allow these config options to both be set. Issue
21307 raised by bug 3898.
21308 - The "--quiet" and "--hush" options now apply not only to Tor's
21309 behavior before logs are configured, but also to Tor's behavior in
21310 the absence of configured logs. Fixes bug 3550; bugfix on
21313 o Minor bugfixes (also part of 0.2.2.31-rc):
21314 - Write several files in text mode, on OSes that distinguish text
21315 mode from binary mode (namely, Windows). These files are:
21316 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21317 that collect those statistics; 'client_keys' and 'hostname' for
21318 hidden services that use authentication; and (in the tor-gencert
21319 utility) newly generated identity and signing keys. Previously,
21320 we wouldn't specify text mode or binary mode, leading to an
21321 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21322 the DirRecordUsageByCountry option which would have triggered
21323 the assertion failure was added), although this assertion failure
21324 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21325 - Selectively disable deprecation warnings on OS X because Lion
21326 started deprecating the shipped copy of openssl. Fixes bug 3643.
21327 - Remove an extra pair of quotation marks around the error
21328 message in control-port STATUS_GENERAL BUG events. Bugfix on
21329 0.1.2.6-alpha; fixes bug 3732.
21330 - When unable to format an address as a string, report its value
21331 as "???" rather than reusing the last formatted address. Bugfix
21334 o Code simplifications and refactoring:
21335 - Rewrite the listener-selection logic so that parsing which ports
21336 we want to listen on is now separate from binding to the ports
21340 - Building Tor with bufferevent support now requires Libevent
21341 2.0.13-stable or later. Previous versions of Libevent had bugs in
21342 SSL-related bufferevents and related issues that would make Tor
21343 work badly with bufferevents. Requiring 2.0.13-stable also allows
21344 Tor with bufferevents to take advantage of Libevent APIs
21345 introduced after 2.0.8-rc.
21348 Changes in version 0.2.2.32 - 2011-08-27
21349 The Tor 0.2.2 release series is dedicated to the memory of Andreas
21350 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
21351 a founder of the PETS community, a leader in our field, a mentor,
21352 and a friend. He left us with these words: "I had the possibility
21353 to contribute to this world that is not as it should be. I hope I
21354 could help in some areas to make the world a better place, and that
21355 I could also encourage other people to be engaged in improving the
21356 world. Please, stay engaged. This world needs you, your love, your
21357 initiative -- now I cannot be part of that anymore."
21359 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
21360 ready. More than two years in the making, this release features improved
21361 client performance and hidden service reliability, better compatibility
21362 for Android, correct behavior for bridges that listen on more than
21363 one address, more extensible and flexible directory object handling,
21364 better reporting of network statistics, improved code security, and
21365 many many other features and bugfixes.
21368 Changes in version 0.2.2.31-rc - 2011-08-17
21369 Tor 0.2.2.31-rc is the second and hopefully final release candidate
21370 for the Tor 0.2.2.x series.
21373 - Remove an extra pair of quotation marks around the error
21374 message in control-port STATUS_GENERAL BUG events. Bugfix on
21375 0.1.2.6-alpha; fixes bug 3732.
21376 - If we're configured to write our ControlPorts to disk, only write
21377 them after switching UID and creating the data directory. This way,
21378 we don't fail when starting up with a nonexistent DataDirectory
21379 and a ControlPortWriteToFile setting based on that directory. Fixes
21380 bug 3747; bugfix on Tor 0.2.2.26-beta.
21383 - Update to the August 2 2011 Maxmind GeoLite Country database.
21386 - Allow GETINFO fingerprint to return a fingerprint even when
21387 we have not yet built a router descriptor. Fixes bug 3577;
21388 bugfix on 0.2.0.1-alpha.
21389 - Write several files in text mode, on OSes that distinguish text
21390 mode from binary mode (namely, Windows). These files are:
21391 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21392 that collect those statistics; 'client_keys' and 'hostname' for
21393 hidden services that use authentication; and (in the tor-gencert
21394 utility) newly generated identity and signing keys. Previously,
21395 we wouldn't specify text mode or binary mode, leading to an
21396 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21397 the DirRecordUsageByCountry option which would have triggered
21398 the assertion failure was added), although this assertion failure
21399 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21400 - Selectively disable deprecation warnings on OS X because Lion
21401 started deprecating the shipped copy of openssl. Fixes bug 3643.
21402 - When unable to format an address as a string, report its value
21403 as "???" rather than reusing the last formatted address. Bugfix
21407 Changes in version 0.2.3.2-alpha - 2011-07-18
21408 Tor 0.2.3.2-alpha introduces two new experimental features:
21409 microdescriptors and pluggable transports. It also continues cleaning
21410 up a variety of recently introduced features.
21413 - Clients can now use microdescriptors instead of regular descriptors
21414 to build circuits. Microdescriptors are authority-generated
21415 summaries of regular descriptors' contents, designed to change
21416 very rarely (see proposal 158 for details). This feature is
21417 designed to save bandwidth, especially for clients on slow internet
21418 connections. It's off by default for now, since nearly no caches
21419 support it, but it will be on-by-default for clients in a future
21420 version. You can use the UseMicrodescriptors option to turn it on.
21421 - Tor clients using bridges can now be configured to use a separate
21422 'transport' proxy for each bridge. This approach helps to resist
21423 censorship by allowing bridges to use protocol obfuscation
21424 plugins. It implements part of proposal 180. Implements ticket 2841.
21425 - While we're trying to bootstrap, record how many TLS connections
21426 fail in each state, and report which states saw the most failures
21427 in response to any bootstrap failures. This feature may speed up
21428 diagnosis of censorship events. Implements ticket 3116.
21430 o Major bugfixes (on 0.2.3.1-alpha):
21431 - When configuring a large set of nodes in EntryNodes (as with
21432 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
21433 random subset to be guards, and choose them in random
21434 order. Fixes bug 2798.
21435 - Tor could crash when remembering a consensus in a non-used consensus
21436 flavor without having a current consensus set. Fixes bug 3361.
21437 - Comparing an unknown address to a microdescriptor's shortened exit
21438 policy would always give a "rejected" result. Fixes bug 3599.
21439 - Using microdescriptors as a client no longer prevents Tor from
21440 uploading and downloading hidden service descriptors. Fixes
21444 - Allow nameservers with IPv6 address. Resolves bug 2574.
21445 - Accept attempts to include a password authenticator in the
21446 handshake, as supported by SOCKS5. This handles SOCKS clients that
21447 don't know how to omit a password when authenticating. Resolves
21449 - When configuring a large set of nodes in EntryNodes, and there are
21450 enough of them listed as Guard so that we don't need to consider
21451 the non-guard entries, prefer the ones listed with the Guard flag.
21452 - Check for and recover from inconsistency in the microdescriptor
21453 cache. This will make it harder for us to accidentally free a
21454 microdescriptor without removing it from the appropriate data
21455 structures. Fixes issue 3135; issue noted by "wanoskarnet".
21456 - Log SSL state transitions at log level DEBUG, log domain
21457 HANDSHAKE. This can be useful for debugging censorship events.
21458 Implements ticket 3264.
21459 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
21460 implements ticket 3439.
21462 o Minor bugfixes (on 0.2.3.1-alpha):
21463 - Do not free all general-purpose regular descriptors just
21464 because microdescriptor use is enabled. Fixes bug 3113.
21465 - Correctly link libevent_openssl when --enable-static-libevent
21466 is passed to configure. Fixes bug 3118.
21467 - Bridges should not complain during their heartbeat log messages that
21468 they are unlisted in the consensus: that's more or less the point
21469 of being a bridge. Fixes bug 3183.
21470 - Report a SIGNAL event to controllers when acting on a delayed
21471 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
21472 event to the controller if we acted on a SIGNAL NEWNYM command
21473 immediately, and otherwise not report a SIGNAL event for the
21474 command at all. Fixes bug 3349.
21475 - Fix a crash when handling the SIGNAL controller command or
21476 reporting ERR-level status events with bufferevents enabled. Found
21477 by Robert Ransom. Fixes bug 3367.
21478 - Always ship the tor-fw-helper manpage in our release tarballs.
21479 Fixes bug 3389. Reported by Stephen Walker.
21480 - Fix a class of double-mark-for-close bugs when bufferevents
21481 are enabled. Fixes bug 3403.
21482 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
21483 - Add SIGNAL to the list returned by the 'GETINFO events/names'
21484 control-port command. Fixes part of bug 3465.
21485 - Prevent using negative indices during unit test runs when read_all()
21486 fails. Spotted by coverity.
21487 - Fix a rare memory leak when checking the nodelist without it being
21488 present. Found by coverity.
21489 - Only try to download a microdescriptor-flavored consensus from
21490 a directory cache that provides them.
21492 o Minor bugfixes (on 0.2.2.x and earlier):
21493 - Assert that hidden-service-related operations are not performed
21494 using single-hop circuits. Previously, Tor would assert that
21495 client-side streams are not attached to single-hop circuits,
21496 but not that other sensitive operations on the client and service
21497 side are not performed using single-hop circuits. Fixes bug 3332;
21499 - Don't publish a new relay descriptor when we reload our onion key,
21500 unless the onion key has actually changed. Fixes bug 3263 and
21501 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
21502 - Allow GETINFO fingerprint to return a fingerprint even when
21503 we have not yet built a router descriptor. Fixes bug 3577;
21504 bugfix on 0.2.0.1-alpha.
21505 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
21506 on 0.2.2.4-alpha; fixes bug 3427.
21508 o Code simplification and refactoring:
21509 - Use tor_sscanf() in place of scanf() in more places through the
21510 code. This makes us a little more locale-independent, and
21511 should help shut up code-analysis tools that can't tell
21512 a safe sscanf string from a dangerous one.
21513 - Use tt_assert(), not tor_assert(), for checking for test failures.
21514 This makes the unit tests more able to go on in the event that
21516 - Split connection_about_to_close() into separate functions for each
21520 - On Windows, we now define the _WIN32_WINNT macros only if they
21521 are not already defined. This lets the person building Tor decide,
21522 if they want, to require a later version of Windows.
21525 Changes in version 0.2.2.30-rc - 2011-07-07
21526 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
21527 series. It fixes a few smaller bugs, but generally appears stable.
21528 Please test it and let us know whether it is!
21531 - Send a SUCCEEDED stream event to the controller when a reverse
21532 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
21533 discovered by katmagic.
21534 - Always NUL-terminate the sun_path field of a sockaddr_un before
21535 passing it to the kernel. (Not a security issue: kernels are
21536 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21537 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21538 - Don't stack-allocate the list of supplementary GIDs when we're
21539 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21540 could take up to 256K, which is way too much stack. Found by
21541 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21542 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
21543 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
21544 fixes part of bug 3465.
21545 - Fix a memory leak when receiving a descriptor for a hidden
21546 service we didn't ask for. Found by Coverity; CID #30. Bugfix
21550 - Update to the July 1 2011 Maxmind GeoLite Country database.
21553 Changes in version 0.2.2.29-beta - 2011-06-20
21554 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
21555 have bridge lines in their torrc but don't want to use them; gets
21556 us closer to having the control socket feature working on Debian;
21557 and fixes a variety of smaller bugs.
21560 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
21561 When we changed the default behavior to "use bridges if any
21562 are listed in the torrc", we surprised users who had bridges
21563 in their torrc files but who didn't actually want to use them.
21564 Partial resolution for bug 3354.
21567 - Don't attach new streams to old rendezvous circuits after SIGNAL
21568 NEWNYM. Previously, we would keep using an existing rendezvous
21569 circuit if it remained open (i.e. if it were kept open by a
21570 long-lived stream, or if a new stream were attached to it before
21571 Tor could notice that it was old and no longer in use). Bugfix on
21572 0.1.1.15-rc; fixes bug 3375.
21575 - Fix a bug when using ControlSocketsGroupWritable with User. The
21576 directory's group would be checked against the current group, not
21577 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
21578 bugfix on 0.2.2.26-beta.
21579 - Make connection_printf_to_buf()'s behavior sane. Its callers
21580 expect it to emit a CRLF iff the format string ends with CRLF;
21581 it actually emitted a CRLF iff (a) the format string ended with
21582 CRLF or (b) the resulting string was over 1023 characters long or
21583 (c) the format string did not end with CRLF *and* the resulting
21584 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
21585 fixes part of bug 3407.
21586 - Make send_control_event_impl()'s behavior sane. Its callers
21587 expect it to always emit a CRLF at the end of the string; it
21588 might have emitted extra control characters as well. Bugfix on
21589 0.1.1.9-alpha; fixes another part of bug 3407.
21590 - Make crypto_rand_int() check the value of its input correctly.
21591 Previously, it accepted values up to UINT_MAX, but could return a
21592 negative number if given a value above INT_MAX+1. Found by George
21593 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
21594 - Avoid a segfault when reading a malformed circuit build state
21595 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
21597 - When asked about a DNS record type we don't support via a
21598 client DNSPort, reply with NOTIMPL rather than an empty
21599 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
21600 - Fix a rare memory leak during stats writing. Found by coverity.
21603 - Update to the June 1 2011 Maxmind GeoLite Country database.
21605 o Code simplifications and refactoring:
21606 - Remove some dead code as indicated by coverity.
21607 - Remove a few dead assignments during router parsing. Found by
21609 - Add some forgotten return value checks during unit tests. Found
21611 - Don't use 1-bit wide signed bit fields. Found by coverity.
21614 Changes in version 0.2.2.28-beta - 2011-06-04
21615 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
21616 fixed a big bug in whether relays stay in the consensus consistently,
21617 we moved closer to handling bridges and hidden services correctly,
21618 and we started the process of better handling the dreaded "my Vidalia
21619 died, and now my Tor demands a password when I try to reconnect to it"
21623 - Don't decide to make a new descriptor when receiving a HUP signal.
21624 This bug has caused a lot of 0.2.2.x relays to disappear from the
21625 consensus periodically. Fixes the most common case of triggering
21626 bug 1810; bugfix on 0.2.2.7-alpha.
21627 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
21628 - Don't try to build descriptors if "ORPort auto" is set and we
21629 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
21631 - Resolve a crash that occurred when setting BridgeRelay to 1 with
21632 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
21633 - Apply circuit timeouts to opened hidden-service-related circuits
21634 based on the correct start time. Previously, we would apply the
21635 circuit build timeout based on time since the circuit's creation;
21636 it was supposed to be applied based on time since the circuit
21637 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
21638 - Use the same circuit timeout for client-side introduction
21639 circuits as for other four-hop circuits, rather than the timeout
21640 for single-hop directory-fetch circuits; the shorter timeout may
21641 have been appropriate with the static circuit build timeout in
21642 0.2.1.x and earlier, but caused many hidden service access attempts
21643 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
21644 on 0.2.2.2-alpha; fixes another part of bug 1297.
21645 - In ticket 2511 we fixed a case where you could use an unconfigured
21646 bridge if you had configured it as a bridge the last time you ran
21647 Tor. Now fix another edge case: if you had configured it as a bridge
21648 but then switched to a different bridge via the controller, you
21649 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
21653 - Add an __OwningControllerProcess configuration option and a
21654 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
21655 that when it exits, Tor will shut down. Implements feature 3049.
21656 - If "UseBridges 1" is set and no bridges are configured, Tor will
21657 now refuse to build any circuits until some bridges are set.
21658 If "UseBridges auto" is set, Tor will use bridges if they are
21659 configured and we are not running as a server, but otherwise will
21660 make circuits as usual. The new default is "auto". Patch by anonym,
21661 so the Tails LiveCD can stop automatically revealing you as a Tor
21665 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21666 - Remove a trailing asterisk from "exit-policy/default" in the
21667 output of the control port command "GETINFO info/names". Bugfix
21669 - Use a wide type to hold sockets when built for 64-bit Windows builds.
21671 - Warn when the user configures two HiddenServiceDir lines that point
21672 to the same directory. Bugfix on 0.0.6 (the version introducing
21673 HiddenServiceDir); fixes bug 3289.
21674 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
21675 part of bug 2748; bugfix on 0.2.0.10-alpha.
21676 - Log malformed requests for rendezvous descriptors as protocol
21677 warnings, not warnings. Also, use a more informative log message
21678 in case someone sees it at log level warning without prior
21679 info-level messages. Fixes the other part of bug 2748; bugfix
21681 - Clear the table recording the time of the last request for each
21682 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
21683 Previously, we would clear our HS descriptor cache on SIGNAL
21684 NEWNYM, but if we had previously retrieved a descriptor (or tried
21685 to) from every directory responsible for it, we would refuse to
21686 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
21688 - Fix a log message that said "bits" while displaying a value in
21689 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
21691 - When checking for 1024-bit keys, check for 1024 bits, not 128
21692 bytes. This allows Tor to correctly discard keys of length 1017
21693 through 1023. Bugfix on 0.0.9pre5.
21696 - Relays now log the reason for publishing a new relay descriptor,
21697 so we have a better chance of hunting down instances of bug 1810.
21698 Resolves ticket 3252.
21699 - Revise most log messages that refer to nodes by nickname to
21700 instead use the "$key=nickname at address" format. This should be
21701 more useful, especially since nicknames are less and less likely
21702 to be unique. Resolves ticket 3045.
21703 - Log (at info level) when purging pieces of hidden-service-client
21704 state because of SIGNAL NEWNYM.
21707 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21708 anything since 0.2.1.16-rc.
21711 Changes in version 0.2.2.27-beta - 2011-05-18
21712 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
21713 release, and also adds a few more general bugfixes.
21716 - Fix a crash bug when changing bridges in a running Tor process.
21717 Fixes bug 3213; bugfix on 0.2.2.26-beta.
21718 - When the controller configures a new bridge, don't wait 10 to 60
21719 seconds before trying to fetch its descriptor. Bugfix on
21720 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
21723 - Require that onion keys have exponent 65537 in microdescriptors too.
21724 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
21725 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
21726 Changed the limit to 512 characters by removing base64 newlines.
21727 Fixes bug 2752. Fix by Michael Yakubovich.
21728 - When a client starts or stops using bridges, never use a circuit
21729 that was built before the configuration change. This behavior could
21730 put at risk a user who uses bridges to ensure that her traffic
21731 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
21735 Changes in version 0.2.2.26-beta - 2011-05-17
21736 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
21737 also introduces a new "socksport auto" approach that should make it
21738 easier to run multiple Tors on the same system, and does a lot of
21739 cleanup to get us closer to a release candidate.
21741 o Security/privacy fixes:
21742 - Replace all potentially sensitive memory comparison operations
21743 with versions whose runtime does not depend on the data being
21744 compared. This will help resist a class of attacks where an
21745 adversary can use variations in timing information to learn
21746 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21747 implementation by Robert Ransom based partially on code by DJB.)
21748 - When receiving a hidden service descriptor, check that it is for
21749 the hidden service we wanted. Previously, Tor would store any
21750 hidden service descriptors that a directory gave it, whether it
21751 wanted them or not. This wouldn't have let an attacker impersonate
21752 a hidden service, but it did let directories pre-seed a client
21753 with descriptors that it didn't want. Bugfix on 0.0.6.
21754 - On SIGHUP, do not clear out all TrackHostExits mappings, client
21755 DNS cache entries, and virtual address mappings: that's what
21756 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
21759 - The options SocksPort, ControlPort, and so on now all accept a
21760 value "auto" that opens a socket on an OS-selected port. A
21761 new ControlPortWriteToFile option tells Tor to write its
21762 actual control port or ports to a chosen file. If the option
21763 ControlPortFileGroupReadable is set, the file is created as
21764 group-readable. Now users can run two Tor clients on the same
21765 system without needing to manually mess with parameters. Resolves
21766 part of ticket 3076.
21767 - Set SO_REUSEADDR on all sockets, not just listeners. This should
21768 help busy exit nodes avoid running out of useable ports just
21769 because all the ports have been used in the near past. Resolves
21773 - New "GETINFO net/listeners/(type)" controller command to return
21774 a list of addresses and ports that are bound for listeners for a
21775 given connection type. This is useful when the user has configured
21776 "SocksPort auto" and the controller needs to know which port got
21777 chosen. Resolves another part of ticket 3076.
21778 - Add a new ControlSocketsGroupWritable configuration option: when
21779 it is turned on, ControlSockets are group-writeable by the default
21780 group of the current user. Patch by Jérémy Bobbio; implements
21782 - Tor now refuses to create a ControlSocket in a directory that is
21783 world-readable (or group-readable if ControlSocketsGroupWritable
21784 is 0). This is necessary because some operating systems do not
21785 enforce permissions on an AF_UNIX sockets. Permissions on the
21786 directory holding the socket, however, seems to work everywhere.
21787 - Rate-limit a warning about failures to download v2 networkstatus
21788 documents. Resolves part of bug 1352.
21789 - Backport code from 0.2.3.x that allows directory authorities to
21790 clean their microdescriptor caches. Needed to resolve bug 2230.
21791 - When an HTTPS proxy reports "403 Forbidden", we now explain
21792 what it means rather than calling it an unexpected status code.
21793 Closes bug 2503. Patch from Michael Yakubovich.
21794 - Update to the May 1 2011 Maxmind GeoLite Country database.
21797 - Authorities now clean their microdesc cache periodically and when
21798 reading from disk initially, not only when adding new descriptors.
21799 This prevents a bug where we could lose microdescriptors. Bugfix
21800 on 0.2.2.6-alpha. Fixes bug 2230.
21801 - Do not crash when our configuration file becomes unreadable, for
21802 example due to a permissions change, between when we start up
21803 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21805 - Avoid a bug that would keep us from replacing a microdescriptor
21806 cache on Windows. (We would try to replace the file while still
21807 holding it open. That's fine on Unix, but Windows doesn't let us
21808 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
21809 - Add missing explanations for the authority-related torrc options
21810 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
21811 man page. Resolves issue 2379.
21812 - As an authority, do not upload our own vote or signature set to
21813 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
21814 it would get flagged as a duplicate. Resolves bug 3026.
21815 - Accept hidden service descriptors if we think we might be a hidden
21816 service directory, regardless of what our consensus says. This
21817 helps robustness, since clients and hidden services can sometimes
21818 have a more up-to-date view of the network consensus than we do,
21819 and if they think that the directory authorities list us a HSDir,
21820 we might actually be one. Related to bug 2732; bugfix on
21822 - When a controller changes TrackHostExits, remove mappings for
21823 hosts that should no longer have their exits tracked. Bugfix on
21825 - When a controller changes VirtualAddrNetwork, remove any mappings
21826 for hosts that were automapped to the old network. Bugfix on
21828 - When a controller changes one of the AutomapHosts* options, remove
21829 any mappings for hosts that should no longer be automapped. Bugfix
21831 - Do not reset the bridge descriptor download status every time we
21832 re-parse our configuration or get a configuration change. Fixes
21833 bug 3019; bugfix on 0.2.0.3-alpha.
21835 o Minor bugfixes (code cleanup):
21836 - When loading the microdesc journal, remember its current size.
21837 In 0.2.2, this helps prevent the microdesc journal from growing
21838 without limit on authorities (who are the only ones to use it in
21839 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21840 Fix posted by "cypherpunks."
21841 - The microdesc journal is supposed to get rebuilt only if it is
21842 at least _half_ the length of the store, not _twice_ the length
21843 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21844 - Fix a potential null-pointer dereference while computing a
21845 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
21847 - Avoid a possible null-pointer dereference when rebuilding the mdesc
21848 cache without actually having any descriptors to cache. Bugfix on
21849 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
21850 - If we fail to compute the identity digest of a v3 legacy keypair,
21851 warn, and don't use a buffer-full of junk instead. Bugfix on
21852 0.2.1.1-alpha; fixes bug 3106.
21853 - Resolve an untriggerable issue in smartlist_string_num_isin(),
21854 where if the function had ever in the future been used to check
21855 for the presence of a too-large number, it would have given an
21856 incorrect result. (Fortunately, we only used it for 16-bit
21857 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
21858 - Require that introduction point keys and onion handshake keys
21859 have a public exponent of 65537. Starts to fix bug 3207; bugfix
21862 o Removed features:
21863 - Caches no longer download and serve v2 networkstatus documents
21864 unless FetchV2Networkstatus flag is set: these documents haven't
21865 haven't been used by clients or relays since 0.2.0.x. Resolves
21869 Changes in version 0.2.3.1-alpha - 2011-05-05
21870 Tor 0.2.3.1-alpha adds some new experimental features, including support
21871 for an improved network IO backend, IOCP networking on Windows,
21872 microdescriptor caching, "fast-start" support for streams, and automatic
21873 home router configuration. There are also numerous internal improvements
21874 to try to make the code easier for developers to work with.
21876 This is the first alpha release in a new series, so expect there to be
21877 bugs. Users who would rather test out a more stable branch should
21878 stay with 0.2.2.x for now.
21881 - Tor can now optionally build with the "bufferevents" buffered IO
21882 backend provided by Libevent 2. To use this feature, make sure you
21883 have the latest possible version of Libevent, and pass the
21884 --enable-bufferevents flag to configure when building Tor from
21885 source. This feature will make our networking code more flexible,
21886 let us stack layers on each other, and let us use more efficient
21887 zero-copy transports where available.
21888 - As an experimental feature, Tor can use IOCP for networking on Windows.
21889 Once this code is tuned and optimized, it promises much better
21890 performance than the select-based backend we've used in the past. To
21891 try this feature, you must build Tor with Libevent 2, configure Tor
21892 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
21893 your torrc. There are known bugs here: only try this if you can help
21894 debug it as it breaks.
21895 - The EntryNodes option can now include country codes like {de} or IP
21896 addresses or network masks. Previously we had disallowed these options
21897 because we didn't have an efficient way to keep the list up to
21898 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
21899 - Exit nodes now accept and queue data on not-yet-connected streams.
21900 Previously, the client wasn't allowed to send data until the stream was
21901 connected, which slowed down all connections. This change will enable
21902 clients to perform a "fast-start" on streams and send data without
21903 having to wait for a confirmation that the stream has opened. (Patch
21904 from Ian Goldberg; implements the server side of Proposal 174.)
21905 - Tor now has initial support for automatic port mapping on the many
21906 home routers that support NAT-PMP or UPnP. (Not yet supported on
21907 Windows). To build the support code, you'll need to have libnatpnp
21908 library and/or the libminiupnpc library, and you'll need to enable the
21909 feature specifically by passing "--enable-upnp" and/or
21910 "--enable-natpnp" to configure. To turn it on, use the new
21911 PortForwarding option.
21912 - Caches now download, cache, and serve multiple "flavors" of the
21913 consensus, including a flavor that describes microdescriptors.
21914 - Caches now download, cache, and serve microdescriptors -- small
21915 summaries of router descriptors that are authenticated by all of the
21916 directory authorities. Once enough caches are running this code,
21917 clients will be able to save significant amounts of directory bandwidth
21918 by downloading microdescriptors instead of router descriptors.
21921 - Make logging resolution configurable with a new LogTimeGranularity
21922 option, and change the default from 1 millisecond to 1 second.
21923 Implements enhancement 1668.
21924 - We log which torrc file we're using on startup. Implements ticket
21926 - Ordinarily, Tor does not count traffic from private addresses (like
21927 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
21928 There is now a new option, CountPrivateBandwidth, to disable this
21929 behavior. Patch from Daniel Cagara.
21930 - New --enable-static-tor configure option for building Tor as
21931 statically as possible. Idea, general hackery and thoughts from
21932 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
21934 - If you set the NumCPUs option to 0, Tor will now try to detect how
21935 many CPUs you have. This is the new default behavior.
21936 - Turn on directory request statistics by default and include them in
21937 extra-info descriptors. Don't break if we have no GeoIP database.
21938 - Relays that set "ConnDirectionStatistics 1" write statistics on the
21939 bidirectional use of connections to disk every 24 hours.
21940 - Add a GeoIP file digest to the extra-info descriptor. Implements
21942 - The NodeFamily option -- which let you declare that you want to
21943 consider nodes to be part of a family whether they list themselves
21944 that way or not -- now allows IP address ranges and country codes.
21945 - Add a new 'Heartbeat' log message type to periodically log a message
21946 describing Tor's status at level Notice. This feature is meant for
21947 operators who log at notice, and want to make sure that their Tor
21948 server is still working. Implementation by George Kadianakis.
21950 o Minor bugfixes (on 0.2.2.25-alpha):
21951 - When loading the microdesc journal, remember its current size.
21952 In 0.2.2, this helps prevent the microdesc journal from growing
21953 without limit on authorities (who are the only ones to use it in
21954 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21955 Fix posted by "cypherpunks."
21956 - The microdesc journal is supposed to get rebuilt only if it is
21957 at least _half_ the length of the store, not _twice_ the length
21958 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21959 - If as an authority we fail to compute the identity digest of a v3
21960 legacy keypair, warn, and don't use a buffer-full of junk instead.
21961 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
21962 - Authorities now clean their microdesc cache periodically and when
21963 reading from disk initially, not only when adding new descriptors.
21964 This prevents a bug where we could lose microdescriptors. Bugfix
21967 o Minor features (controller):
21968 - Add a new SIGNAL event to the controller interface so that
21969 controllers can be notified when Tor handles a signal. Resolves
21970 issue 1955. Patch by John Brooks.
21971 - Add a new GETINFO option to get total bytes read and written. Patch
21972 from pipe, revised by atagar. Resolves ticket 2345.
21973 - Implement some GETINFO controller fields to provide information about
21974 the Tor process's pid, euid, username, and resource limits.
21977 - Our build system requires automake 1.6 or later to create the
21978 Makefile.in files. Previously, you could have used 1.4.
21979 This only affects developers and people building Tor from git;
21980 people who build Tor from the source distribution without changing
21981 the Makefile.am files should be fine.
21982 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
21983 so on. This is more robust against some of the failure modes
21984 associated with running the autotools pieces on their own.
21986 o Minor packaging issues:
21987 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
21988 already created. Patch from Andreas Stieger. Fixes bug 2573.
21990 o Code simplifications and refactoring:
21991 - A major revision to our internal node-selecting and listing logic.
21992 Tor already had at least two major ways to look at the question of
21993 "which Tor servers do we know about": a list of router descriptors,
21994 and a list of entries in the current consensus. With
21995 microdescriptors, we're adding a third. Having so many systems
21996 without an abstraction layer over them was hurting the codebase.
21997 Now, we have a new "node_t" abstraction that presents a consistent
21998 interface to a client's view of a Tor node, and holds (nearly) all
21999 of the mutable state formerly in routerinfo_t and routerstatus_t.
22000 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
22001 no longer link against Libevent: they never used it, but
22002 our library structure used to force them to link it.
22004 o Removed features:
22005 - Remove some old code to work around even older versions of Tor that
22006 used forked processes to handle DNS requests. Such versions of Tor
22007 are no longer in use as servers.
22009 o Documentation fixes:
22010 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
22011 - Add missing documentation for the authority-related torrc options
22012 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
22016 Changes in version 0.2.2.25-alpha - 2011-04-29
22017 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
22018 robust, routers no longer overreport their bandwidth, Win7 should crash
22019 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
22020 now prevents hidden service-related activity from being linkable. It
22021 provides more information to Vidalia so you can see if your bridge is
22022 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
22023 StrictNodes configuration options to make them more reliable, more
22024 understandable, and more regularly applied. If you use those options,
22025 please see the revised documentation for them in the manual page.
22028 - Relays were publishing grossly inflated bandwidth values because
22029 they were writing their state files wrong--now they write the
22030 correct value. Also, resume reading bandwidth history from the
22031 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
22032 - Improve hidden service robustness: When we find that we have
22033 extended a hidden service's introduction circuit to a relay not
22034 listed as an introduction point in the HS descriptor we currently
22035 have, retry with an introduction point from the current
22036 descriptor. Previously we would just give up. Fixes bugs 1024 and
22037 1930; bugfix on 0.2.0.10-alpha.
22038 - Clients now stop trying to use an exit node associated with a given
22039 destination by TrackHostExits if they fail to reach that exit node.
22040 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
22041 - Fix crash bug on platforms where gmtime and localtime can return
22042 NULL. Windows 7 users were running into this one. Fixes part of bug
22043 2077. Bugfix on all versions of Tor. Found by boboper.
22045 o Security and stability fixes:
22046 - Don't double-free a parsable, but invalid, microdescriptor, even if
22047 it is followed in the blob we're parsing by an unparsable
22048 microdescriptor. Fixes an issue reported in a comment on bug 2954.
22049 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
22050 - If the Nickname configuration option isn't given, Tor would pick a
22051 nickname based on the local hostname as the nickname for a relay.
22052 Because nicknames are not very important in today's Tor and the
22053 "Unnamed" nickname has been implemented, this is now problematic
22054 behavior: It leaks information about the hostname without being
22055 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
22056 introduced the Unnamed nickname. Reported by tagnaq.
22057 - Fix an uncommon assertion failure when running with DNSPort under
22058 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
22059 - Avoid linkability based on cached hidden service descriptors: forget
22060 all hidden service descriptors cached as a client when processing a
22061 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
22064 - Export GeoIP information on bridge usage to controllers even if we
22065 have not yet been running for 24 hours. Now Vidalia bridge operators
22066 can get more accurate and immediate feedback about their
22067 contributions to the network.
22069 o Major features and bugfixes (node selection):
22070 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
22071 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
22072 options. Previously, we had been ambiguous in describing what
22073 counted as an "exit" node, and what operations exactly "StrictNodes
22074 0" would permit. This created confusion when people saw nodes built
22075 through unexpected circuits, and made it hard to tell real bugs from
22076 surprises. Now the intended behavior is:
22077 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
22078 a node that delivers user traffic outside the Tor network.
22079 . "Entry", in the context of EntryNodes, means a node used as the
22080 first hop of a multihop circuit. It doesn't include direct
22081 connections to directory servers.
22082 . "ExcludeNodes" applies to all nodes.
22083 . "StrictNodes" changes the behavior of ExcludeNodes only. When
22084 StrictNodes is set, Tor should avoid all nodes listed in
22085 ExcludeNodes, even when it will make user requests fail. When
22086 StrictNodes is *not* set, then Tor should follow ExcludeNodes
22087 whenever it can, except when it must use an excluded node to
22088 perform self-tests, connect to a hidden service, provide a
22089 hidden service, fulfill a .exit request, upload directory
22090 information, or fetch directory information.
22091 Collectively, the changes to implement the behavior fix bug 1090.
22092 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
22093 a node is listed in both, it's treated as excluded.
22094 - ExcludeNodes now applies to directory nodes -- as a preference if
22095 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
22096 Don't exclude all the directory authorities and set StrictNodes to 1
22097 unless you really want your Tor to break.
22098 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
22099 - ExcludeExitNodes now overrides .exit requests.
22100 - We don't use bridges listed in ExcludeNodes.
22101 - When StrictNodes is 1:
22102 . We now apply ExcludeNodes to hidden service introduction points
22103 and to rendezvous points selected by hidden service users. This
22104 can make your hidden service less reliable: use it with caution!
22105 . If we have used ExcludeNodes on ourself, do not try relay
22106 reachability self-tests.
22107 . If we have excluded all the directory authorities, we will not
22108 even try to upload our descriptor if we're a relay.
22109 . Do not honor .exit requests to an excluded node.
22110 - Remove a misfeature that caused us to ignore the Fast/Stable flags
22111 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
22112 - When the set of permitted nodes changes, we now remove any mappings
22113 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
22115 - We never cannibalize a circuit that had excluded nodes on it, even
22116 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
22117 - Revert a change where we would be laxer about attaching streams to
22118 circuits than when building the circuits. This was meant to prevent
22119 a set of bugs where streams were never attachable, but our improved
22120 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
22121 - Keep track of how many times we launch a new circuit to handle a
22122 given stream. Too many launches could indicate an inconsistency
22123 between our "launch a circuit to handle this stream" logic and our
22124 "attach this stream to one of the available circuits" logic.
22125 - Improve log messages related to excluded nodes.
22128 - Fix a spurious warning when moving from a short month to a long
22129 month on relays with month-based BandwidthAccounting. Bugfix on
22130 0.2.2.17-alpha; fixes bug 3020.
22131 - When a client finds that an origin circuit has run out of 16-bit
22132 stream IDs, we now mark it as unusable for new streams. Previously,
22133 we would try to close the entire circuit. Bugfix on 0.0.6.
22134 - Add a forgotten cast that caused a compile warning on OS X 10.6.
22135 Bugfix on 0.2.2.24-alpha.
22136 - Be more careful about reporting the correct error from a failed
22137 connect() system call. Under some circumstances, it was possible to
22138 look at an incorrect value for errno when sending the end reason.
22139 Bugfix on 0.1.0.1-rc.
22140 - Correctly handle an "impossible" overflow cases in connection byte
22141 counting, where we write or read more than 4GB on an edge connection
22142 in a single second. Bugfix on 0.1.2.8-beta.
22143 - Correct the warning displayed when a rendezvous descriptor exceeds
22144 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
22146 - Clients and hidden services now use HSDir-flagged relays for hidden
22147 service descriptor downloads and uploads even if the relays have no
22148 DirPort set and the client has disabled TunnelDirConns. This will
22149 eventually allow us to give the HSDir flag to relays with no
22150 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
22151 - Downgrade "no current certificates known for authority" message from
22152 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
22153 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
22154 2917. Bugfix on 0.1.1.1-alpha.
22155 - Only limit the lengths of single HS descriptors, even when multiple
22156 HS descriptors are published to an HSDir relay in a single POST
22157 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
22158 - Write the current time into the LastWritten line in our state file,
22159 rather than the time from the previous write attempt. Also, stop
22160 trying to use a time of -1 in our log statements. Fixes bug 3039;
22161 bugfix on 0.2.2.14-alpha.
22162 - Be more consistent in our treatment of file system paths. "~" should
22163 get expanded to the user's home directory in the Log config option.
22164 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
22165 feature for the -f and --DataDirectory options.
22168 - Make sure every relay writes a state file at least every 12 hours.
22169 Previously, a relay could go for weeks without writing its state
22170 file, and on a crash could lose its bandwidth history, capacity
22171 estimates, client country statistics, and so on. Addresses bug 3012.
22172 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
22173 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
22174 clients are already deprecated because of security bugs.
22175 - Don't allow v0 hidden service authorities to act as clients.
22176 Required by fix for bug 3000.
22177 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
22178 by fix for bug 3000.
22179 - Ensure that no empty [dirreq-](read|write)-history lines are added
22180 to an extrainfo document. Implements ticket 2497.
22182 o Code simplification and refactoring:
22183 - Remove workaround code to handle directory responses from servers
22184 that had bug 539 (they would send HTTP status 503 responses _and_
22185 send a body too). Since only server versions before
22186 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
22187 keep the workaround in place.
22188 - Remove the old 'fuzzy time' logic. It was supposed to be used for
22189 handling calculations where we have a known amount of clock skew and
22190 an allowed amount of unknown skew. But we only used it in three
22191 places, and we never adjusted the known/unknown skew values. This is
22192 still something we might want to do someday, but if we do, we'll
22193 want to do it differently.
22194 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
22195 None of the cases where we did this before were wrong, but by making
22196 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
22197 - Use GetTempDir to find the proper temporary directory location on
22198 Windows when generating temporary files for the unit tests. Patch by
22202 Changes in version 0.2.2.24-alpha - 2011-04-08
22203 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
22204 prevented Tor clients from effectively using "multihomed" bridges,
22205 that is, bridges that listen on multiple ports or IP addresses so users
22206 can continue to use some of their addresses even if others get blocked.
22209 - Fix a bug where bridge users who configure the non-canonical
22210 address of a bridge automatically switch to its canonical
22211 address. If a bridge listens at more than one address, it should be
22212 able to advertise those addresses independently and any non-blocked
22213 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
22215 - If you configured Tor to use bridge A, and then quit and
22216 configured Tor to use bridge B instead, it would happily continue
22217 to use bridge A if it's still reachable. While this behavior is
22218 a feature if your goal is connectivity, in some scenarios it's a
22219 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
22220 - Directory authorities now use data collected from their own
22221 uptime observations when choosing whether to assign the HSDir flag
22222 to relays, instead of trusting the uptime value the relay reports in
22223 its descriptor. This change helps prevent an attack where a small
22224 set of nodes with frequently-changing identity keys can blackhole
22225 a hidden service. (Only authorities need upgrade; others will be
22226 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
22229 - When we restart our relay, we might get a successful connection
22230 from the outside before we've started our reachability tests,
22231 triggering a warning: "ORPort found reachable, but I have no
22232 routerinfo yet. Failing to inform controller of success." This
22233 bug was harmless unless Tor is running under a controller
22234 like Vidalia, in which case the controller would never get a
22235 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
22237 - Make directory authorities more accurate at recording when
22238 relays that have failed several reachability tests became
22239 unreachable, so we can provide more accuracy at assigning Stable,
22240 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
22241 - Fix an issue that prevented static linking of libevent on
22242 some platforms (notably Linux). Fixes bug 2698; bugfix on
22243 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
22244 the --with-static-libevent configure option).
22245 - We now ask the other side of a stream (the client or the exit)
22246 for more data on that stream when the amount of queued data on
22247 that stream dips low enough. Previously, we wouldn't ask the
22248 other side for more data until either it sent us more data (which
22249 it wasn't supposed to do if it had exhausted its window!) or we
22250 had completely flushed all our queued data. This flow control fix
22251 should improve throughput. Fixes bug 2756; bugfix on the earliest
22252 released versions of Tor (svn commit r152).
22253 - Avoid a double-mark-for-free warning when failing to attach a
22254 transparent proxy connection. (We thought we had fixed this in
22255 0.2.2.23-alpha, but it turns out our fix was checking the wrong
22256 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
22257 bug) and 0.2.2.23-alpha (the incorrect fix).
22258 - When warning about missing zlib development packages during compile,
22259 give the correct package names. Bugfix on 0.2.0.1-alpha.
22262 - Directory authorities now log the source of a rejected POSTed v3
22263 networkstatus vote.
22264 - Make compilation with clang possible when using
22265 --enable-gcc-warnings by removing two warning options that clang
22266 hasn't implemented yet and by fixing a few warnings. Implements
22268 - When expiring circuits, use microsecond timers rather than
22269 one-second timers. This can avoid an unpleasant situation where a
22270 circuit is launched near the end of one second and expired right
22271 near the beginning of the next, and prevent fluctuations in circuit
22273 - Use computed circuit-build timeouts to decide when to launch
22274 parallel introduction circuits for hidden services. (Previously,
22275 we would retry after 15 seconds.)
22276 - Update to the April 1 2011 Maxmind GeoLite Country database.
22279 - Create the /var/run/tor directory on startup on OpenSUSE if it is
22280 not already created. Patch from Andreas Stieger. Fixes bug 2573.
22282 o Documentation changes:
22283 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
22284 - Resolve all doxygen warnings except those for missing documentation.
22286 - Add doxygen documentation for more functions, fields, and types.
22289 Changes in version 0.2.2.23-alpha - 2011-03-08
22290 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
22291 they restart they don't lose their bandwidth capacity estimate. This
22292 release also fixes a diverse set of user-facing bugs, ranging from
22293 relays overrunning their rate limiting to clients falsely warning about
22294 clock skew to bridge descriptor leaks by our bridge directory authority.
22297 - Stop sending a CLOCK_SKEW controller status event whenever
22298 we fetch directory information from a relay that has a wrong clock.
22299 Instead, only inform the controller when it's a trusted authority
22300 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22301 the rest of bug 1074.
22302 - Fix an assert in parsing router descriptors containing IPv6
22303 addresses. This one took down the directory authorities when
22304 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
22305 - Make the bridge directory authority refuse to answer directory
22306 requests for "all" descriptors. It used to include bridge
22307 descriptors in its answer, which was a major information leak.
22308 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
22309 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22310 Tor would ignore their RelayBandwidthBurst setting,
22311 potentially using more bandwidth than expected. Bugfix on
22312 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22313 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22314 hidserv" in her torrc. The 'hidserv' argument never controlled
22315 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22318 - Relays now save observed peak bandwidth throughput rates to their
22319 state file (along with total usage, which was already saved)
22320 so that they can determine their correct estimated bandwidth on
22321 restart. Resolves bug 1863, where Tor relays would reset their
22322 estimated bandwidth to 0 after restarting.
22323 - Directory authorities now take changes in router IP address and
22324 ORPort into account when determining router stability. Previously,
22325 if a router changed its IP or ORPort, the authorities would not
22326 treat it as having any downtime for the purposes of stability
22327 calculation, whereas clients would experience downtime since the
22328 change could take a while to propagate to them. Resolves issue 1035.
22329 - Enable Address Space Layout Randomization (ASLR) and Data Execution
22330 Prevention (DEP) by default on Windows to make it harder for
22331 attackers to exploit vulnerabilities. Patch from John Brooks.
22333 o Minor bugfixes (on 0.2.1.x and earlier):
22334 - Fix a rare crash bug that could occur when a client was configured
22335 with a large number of bridges. Fixes bug 2629; bugfix on
22336 0.2.1.2-alpha. Bugfix by trac user "shitlei".
22337 - Avoid a double mark-for-free warning when failing to attach a
22338 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
22340 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
22341 found by "cypherpunks". This bug was introduced before the first
22342 Tor release, in svn commit r110.
22343 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
22344 don't mention them in the manpage. Fixes bug 2450; issue
22345 spotted by keb and G-Lo.
22346 - Fix a bug in bandwidth history state parsing that could have been
22347 triggered if a future version of Tor ever changed the timing
22348 granularity at which bandwidth history is measured. Bugfix on
22349 Tor 0.1.1.11-alpha.
22350 - When a relay decides that its DNS is too broken for it to serve
22351 as an exit server, it advertised itself as a non-exit, but
22352 continued to act as an exit. This could create accidental
22353 partitioning opportunities for users. Instead, if a relay is
22354 going to advertise reject *:* as its exit policy, it should
22355 really act with exit policy "reject *:*". Fixes bug 2366.
22356 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
22357 - In the special case where you configure a public exit relay as your
22358 bridge, Tor would be willing to use that exit relay as the last
22359 hop in your circuit as well. Now we fail that circuit instead.
22360 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
22361 - Fix a bug with our locking implementation on Windows that couldn't
22362 correctly detect when a file was already locked. Fixes bug 2504,
22363 bugfix on 0.2.1.6-alpha.
22364 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
22365 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
22367 - Set target port in get_interface_address6() correctly. Bugfix
22368 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
22369 - Directory authorities are now more robust to hops back in time
22370 when calculating router stability. Previously, if a run of uptime
22371 or downtime appeared to be negative, the calculation could give
22372 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
22374 - Fix an assert that got triggered when using the TestingTorNetwork
22375 configuration option and then issuing a GETINFO config-text control
22376 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
22378 o Minor bugfixes (on 0.2.2.x):
22379 - Clients should not weight BadExit nodes as Exits in their node
22380 selection. Similarly, directory authorities should not count BadExit
22381 bandwidth as Exit bandwidth when computing bandwidth-weights.
22382 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
22383 - Correctly clear our dir_read/dir_write history when there is an
22384 error parsing any bw history value from the state file. Bugfix on
22385 Tor 0.2.2.15-alpha.
22386 - Resolve a bug in verifying signatures of directory objects
22387 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
22388 Fixes bug 2409. Found by "piebeer".
22389 - Bridge authorities no longer crash on SIGHUP when they try to
22390 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
22394 - Log less aggressively about circuit timeout changes, and improve
22395 some other circuit timeout messages. Resolves bug 2004.
22396 - Log a little more clearly about the times at which we're no longer
22397 accepting new connections. Resolves bug 2181.
22398 - Reject attempts at the client side to open connections to private
22399 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
22400 a randomly chosen exit node. Attempts to do so are always
22401 ill-defined, generally prevented by exit policies, and usually
22402 in error. This will also help to detect loops in transparent
22403 proxy configurations. You can disable this feature by setting
22404 "ClientRejectInternalAddresses 0" in your torrc.
22405 - Always treat failure to allocate an RSA key as an unrecoverable
22407 - Update to the March 1 2011 Maxmind GeoLite Country database.
22409 o Minor features (log subsystem):
22410 - Add documentation for configuring logging at different severities in
22411 different log domains. We've had this feature since 0.2.1.1-alpha,
22412 but for some reason it never made it into the manpage. Fixes
22414 - Make it simpler to specify "All log domains except for A and B".
22415 Previously you needed to say "[*,~A,~B]". Now you can just say
22417 - Add a "LogMessageDomains 1" option to include the domains of log
22418 messages along with the messages. Without this, there's no way
22419 to use log domains without reading the source or doing a lot
22422 o Packaging changes:
22423 - Stop shipping the Tor specs files and development proposal documents
22424 in the tarball. They are now in a separate git repository at
22425 git://git.torproject.org/torspec.git
22428 Changes in version 0.2.1.30 - 2011-02-23
22429 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
22430 change is a slight tweak to Tor's TLS handshake that makes relays
22431 and bridges that run this new version reachable from Iran again.
22432 We don't expect this tweak will win the arms race long-term, but it
22433 buys us time until we roll out a better solution.
22436 - Stop sending a CLOCK_SKEW controller status event whenever
22437 we fetch directory information from a relay that has a wrong clock.
22438 Instead, only inform the controller when it's a trusted authority
22439 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22440 the rest of bug 1074.
22441 - Fix a bounds-checking error that could allow an attacker to
22442 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22443 Found by "piebeer".
22444 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22445 Tor would ignore their RelayBandwidthBurst setting,
22446 potentially using more bandwidth than expected. Bugfix on
22447 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22448 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22449 hidserv" in her torrc. The 'hidserv' argument never controlled
22450 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22453 - Adjust our TLS Diffie-Hellman parameters to match those used by
22455 - Update to the February 1 2011 Maxmind GeoLite Country database.
22458 - Check for and reject overly long directory certificates and
22459 directory tokens before they have a chance to hit any assertions.
22460 Bugfix on 0.2.1.28. Found by "doorss".
22461 - Bring the logic that gathers routerinfos and assesses the
22462 acceptability of circuits into line. This prevents a Tor OP from
22463 getting locked in a cycle of choosing its local OR as an exit for a
22464 path (due to a .exit request) and then rejecting the circuit because
22465 its OR is not listed yet. It also prevents Tor clients from using an
22466 OR running in the same instance as an exit (due to a .exit request)
22467 if the OR does not meet the same requirements expected of an OR
22468 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22470 o Packaging changes:
22471 - Stop shipping the Tor specs files and development proposal documents
22472 in the tarball. They are now in a separate git repository at
22473 git://git.torproject.org/torspec.git
22474 - Do not include Git version tags as though they are SVN tags when
22475 generating a tarball from inside a repository that has switched
22476 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
22479 Changes in version 0.2.2.22-alpha - 2011-01-25
22480 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
22481 main other change is a slight tweak to Tor's TLS handshake that makes
22482 relays and bridges that run this new version reachable from Iran again.
22483 We don't expect this tweak will win the arms race long-term, but it
22484 will buy us a bit more time until we roll out a better solution.
22487 - Fix a bounds-checking error that could allow an attacker to
22488 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22489 Found by "piebeer".
22490 - Don't assert when changing from bridge to relay or vice versa
22491 via the controller. The assert happened because we didn't properly
22492 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
22493 bug 2433. Reported by bastik.
22496 - Adjust our TLS Diffie-Hellman parameters to match those used by
22498 - Provide a log message stating which geoip file we're parsing
22499 instead of just stating that we're parsing the geoip file.
22500 Implements ticket 2432.
22503 - Check for and reject overly long directory certificates and
22504 directory tokens before they have a chance to hit any assertions.
22505 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
22508 Changes in version 0.2.2.21-alpha - 2011-01-15
22509 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
22510 continues our recent code security audit work. The main fix resolves
22511 a remote heap overflow vulnerability that can allow remote code
22512 execution (CVE-2011-0427). Other fixes address a variety of assert
22513 and crash bugs, most of which we think are hard to exploit remotely.
22515 o Major bugfixes (security), also included in 0.2.1.29:
22516 - Fix a heap overflow bug where an adversary could cause heap
22517 corruption. This bug probably allows remote code execution
22518 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22520 - Prevent a denial-of-service attack by disallowing any
22521 zlib-compressed data whose compression factor is implausibly
22522 high. Fixes part of bug 2324; reported by "doorss".
22523 - Zero out a few more keys in memory before freeing them. Fixes
22524 bug 2384 and part of bug 2385. These key instances found by
22525 "cypherpunks", based on Andrew Case's report about being able
22526 to find sensitive data in Tor's memory space if you have enough
22527 permissions. Bugfix on 0.0.2pre9.
22529 o Major bugfixes (crashes), also included in 0.2.1.29:
22530 - Prevent calls to Libevent from inside Libevent log handlers.
22531 This had potential to cause a nasty set of crashes, especially
22532 if running Libevent with debug logging enabled, and running
22533 Tor with a controller watching for low-severity log messages.
22534 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22535 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22536 underflow errors there too. Fixes the other part of bug 2324.
22537 - Fix a bug where we would assert if we ever had a
22538 cached-descriptors.new file (or another file read directly into
22539 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22540 on 0.2.1.25. Found by doorss.
22541 - Fix some potential asserts and parsing issues with grossly
22542 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22545 o Minor bugfixes (other), also included in 0.2.1.29:
22546 - Fix a bug with handling misformed replies to reverse DNS lookup
22547 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22548 bug reported by doorss.
22549 - Fix compilation on mingw when a pthreads compatibility library
22550 has been installed. (We don't want to use it, so we shouldn't
22551 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22552 - Fix a bug where we would declare that we had run out of virtual
22553 addresses when the address space was only half-exhausted. Bugfix
22555 - Correctly handle the case where AutomapHostsOnResolve is set but
22556 no virtual addresses are available. Fixes bug 2328; bugfix on
22557 0.1.2.1-alpha. Bug found by doorss.
22558 - Correctly handle wrapping around when we run out of virtual
22559 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
22561 o Minor features, also included in 0.2.1.29:
22562 - Update to the January 1 2011 Maxmind GeoLite Country database.
22563 - Introduce output size checks on all of our decryption functions.
22565 o Build changes, also included in 0.2.1.29:
22566 - Tor does not build packages correctly with Automake 1.6 and earlier;
22567 added a check to Makefile.am to make sure that we're building with
22568 Automake 1.7 or later.
22569 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22570 because we built it with a too-old version of automake. Thus that
22571 release broke ./configure --enable-openbsd-malloc, which is popular
22572 among really fast exit relays on Linux.
22574 o Major bugfixes, new in 0.2.2.21-alpha:
22575 - Prevent crash/heap corruption when the cbtnummodes consensus
22576 parameter is set to 0 or large values. Fixes bug 2317; bugfix
22579 o Major features, new in 0.2.2.21-alpha:
22580 - Introduce minimum/maximum values that clients will believe
22581 from the consensus. Now we'll have a better chance to avoid crashes
22582 or worse when a consensus param has a weird value.
22584 o Minor features, new in 0.2.2.21-alpha:
22585 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
22586 used on bridges, and it makes bridge scanning somewhat easier.
22587 - If writing the state file to disk fails, wait up to an hour before
22588 retrying again, rather than trying again each second. Fixes bug
22589 2346; bugfix on Tor 0.1.1.3-alpha.
22590 - Make Libevent log messages get delivered to controllers later,
22591 and not from inside the Libevent log handler. This prevents unsafe
22592 reentrant Libevent calls while still letting the log messages
22594 - Detect platforms that brokenly use a signed size_t, and refuse to
22595 build there. Found and analyzed by doorss and rransom.
22596 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
22599 o Minor bugfixes, new in 0.2.2.21-alpha:
22600 - Handle SOCKS messages longer than 128 bytes long correctly, rather
22601 than waiting forever for them to finish. Fixes bug 2330; bugfix
22602 on 0.2.0.16-alpha. Found by doorss.
22603 - Add assertions to check for overflow in arguments to
22604 base32_encode() and base32_decode(); fix a signed-unsigned
22605 comparison there too. These bugs are not actually reachable in Tor,
22606 but it's good to prevent future errors too. Found by doorss.
22607 - Correctly detect failures to create DNS requests when using Libevent
22608 versions before v2. (Before Libevent 2, we used our own evdns
22609 implementation. Its return values for Libevent's evdns_resolve_*()
22610 functions are not consistent with those from Libevent.) Fixes bug
22611 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
22613 o Documentation, new in 0.2.2.21-alpha:
22614 - Document the default socks host and port (127.0.0.1:9050) for
22618 Changes in version 0.2.1.29 - 2011-01-15
22619 Tor 0.2.1.29 continues our recent code security audit work. The main
22620 fix resolves a remote heap overflow vulnerability that can allow remote
22621 code execution. Other fixes address a variety of assert and crash bugs,
22622 most of which we think are hard to exploit remotely.
22624 o Major bugfixes (security):
22625 - Fix a heap overflow bug where an adversary could cause heap
22626 corruption. This bug probably allows remote code execution
22627 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22629 - Prevent a denial-of-service attack by disallowing any
22630 zlib-compressed data whose compression factor is implausibly
22631 high. Fixes part of bug 2324; reported by "doorss".
22632 - Zero out a few more keys in memory before freeing them. Fixes
22633 bug 2384 and part of bug 2385. These key instances found by
22634 "cypherpunks", based on Andrew Case's report about being able
22635 to find sensitive data in Tor's memory space if you have enough
22636 permissions. Bugfix on 0.0.2pre9.
22638 o Major bugfixes (crashes):
22639 - Prevent calls to Libevent from inside Libevent log handlers.
22640 This had potential to cause a nasty set of crashes, especially
22641 if running Libevent with debug logging enabled, and running
22642 Tor with a controller watching for low-severity log messages.
22643 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22644 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22645 underflow errors there too. Fixes the other part of bug 2324.
22646 - Fix a bug where we would assert if we ever had a
22647 cached-descriptors.new file (or another file read directly into
22648 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22649 on 0.2.1.25. Found by doorss.
22650 - Fix some potential asserts and parsing issues with grossly
22651 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22654 o Minor bugfixes (other):
22655 - Fix a bug with handling misformed replies to reverse DNS lookup
22656 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22657 bug reported by doorss.
22658 - Fix compilation on mingw when a pthreads compatibility library
22659 has been installed. (We don't want to use it, so we shouldn't
22660 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22661 - Fix a bug where we would declare that we had run out of virtual
22662 addresses when the address space was only half-exhausted. Bugfix
22664 - Correctly handle the case where AutomapHostsOnResolve is set but
22665 no virtual addresses are available. Fixes bug 2328; bugfix on
22666 0.1.2.1-alpha. Bug found by doorss.
22667 - Correctly handle wrapping around to when we run out of virtual
22668 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
22669 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22670 because we built it with a too-old version of automake. Thus that
22671 release broke ./configure --enable-openbsd-malloc, which is popular
22672 among really fast exit relays on Linux.
22675 - Update to the January 1 2011 Maxmind GeoLite Country database.
22676 - Introduce output size checks on all of our decryption functions.
22679 - Tor does not build packages correctly with Automake 1.6 and earlier;
22680 added a check to Makefile.am to make sure that we're building with
22681 Automake 1.7 or later.
22684 Changes in version 0.2.2.20-alpha - 2010-12-17
22685 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
22686 exploitable bugs. We also fix a variety of other significant bugs,
22687 change the IP address for one of our directory authorities, and update
22688 the minimum version that Tor relays must run to join the network.
22691 - Fix a remotely exploitable bug that could be used to crash instances
22692 of Tor remotely by overflowing on the heap. Remote-code execution
22693 hasn't been confirmed, but can't be ruled out. Everyone should
22694 upgrade. Bugfix on the 0.1.1 series and later.
22695 - Fix a bug that could break accounting on 64-bit systems with large
22696 time_t values, making them hibernate for impossibly long intervals.
22697 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
22698 - Fix a logic error in directory_fetches_from_authorities() that
22699 would cause all _non_-exits refusing single-hop-like circuits
22700 to fetch from authorities, when we wanted to have _exits_ fetch
22701 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
22703 - Fix a stream fairness bug that would cause newer streams on a given
22704 circuit to get preference when reading bytes from the origin or
22705 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
22706 introduced before the first Tor release, in svn revision r152.
22708 o Directory authority changes:
22709 - Change IP address and ports for gabelmoo (v3 directory authority).
22712 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
22713 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
22714 - Fix an off-by-one error in calculating some controller command
22715 argument lengths. Fortunately, this mistake is harmless since
22716 the controller code does redundant NUL termination too. Found by
22717 boboper. Bugfix on 0.1.1.1-alpha.
22718 - Do not dereference NULL if a bridge fails to build its
22719 extra-info descriptor. Found by an anonymous commenter on
22720 Trac. Bugfix on 0.2.2.19-alpha.
22723 - Update to the December 1 2010 Maxmind GeoLite Country database.
22724 - Directory authorities now reject relays running any versions of
22725 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
22726 known bugs that keep RELAY_EARLY cells from working on rendezvous
22727 circuits. Followup to fix for bug 2081.
22728 - Directory authorities now reject relays running any version of Tor
22729 older than 0.2.0.26-rc. That version is the earliest that fetches
22730 current directory information correctly. Fixes bug 2156.
22731 - Report only the top 10 ports in exit-port stats in order not to
22732 exceed the maximum extra-info descriptor length of 50 KB. Implements
22736 Changes in version 0.2.1.28 - 2010-12-17
22737 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
22738 exploitable bugs. We also took this opportunity to change the IP address
22739 for one of our directory authorities, and to update the geoip database
22743 - Fix a remotely exploitable bug that could be used to crash instances
22744 of Tor remotely by overflowing on the heap. Remote-code execution
22745 hasn't been confirmed, but can't be ruled out. Everyone should
22746 upgrade. Bugfix on the 0.1.1 series and later.
22748 o Directory authority changes:
22749 - Change IP address and ports for gabelmoo (v3 directory authority).
22752 - Update to the December 1 2010 Maxmind GeoLite Country database.
22755 Changes in version 0.2.1.27 - 2010-11-23
22756 Yet another OpenSSL security patch broke its compatibility with Tor:
22757 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
22758 also took this opportunity to fix several crash bugs, integrate a new
22759 directory authority, and update the bundled GeoIP database.
22762 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22763 No longer set the tlsext_host_name extension on server SSL objects;
22764 but continue to set it on client SSL objects. Our goal in setting
22765 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22766 bugfix on 0.2.1.1-alpha.
22767 - Do not log messages to the controller while shrinking buffer
22768 freelists. Doing so would sometimes make the controller connection
22769 try to allocate a buffer chunk, which would mess up the internals
22770 of the freelist and cause an assertion failure. Fixes bug 1125;
22771 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22772 - Learn our external IP address when we're a relay or bridge, even if
22773 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22774 where we introduced bridge relays that don't need to publish to
22775 be useful. Fixes bug 2050.
22776 - Do even more to reject (and not just ignore) annotations on
22777 router descriptors received anywhere but from the cache. Previously
22778 we would ignore such annotations at first, but cache them to disk
22779 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22780 - When you're using bridges and your network goes away and your
22781 bridges get marked as down, recover when you attempt a new socks
22782 connection (if the network is back), rather than waiting up to an
22783 hour to try fetching new descriptors for your bridges. Bugfix on
22784 0.2.0.3-alpha; fixes bug 1981.
22787 - Move to the November 2010 Maxmind GeoLite country db (rather
22788 than the June 2009 ip-to-country GeoIP db) for our statistics that
22789 count how many users relays are seeing from each country. Now we'll
22790 have more accurate data, especially for many African countries.
22792 o New directory authorities:
22793 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22797 - Fix an assertion failure that could occur in directory caches or
22798 bridge users when using a very short voting interval on a testing
22799 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
22801 - Enforce multiplicity rules when parsing annotations. Bugfix on
22802 0.2.0.8-alpha. Found by piebeer.
22803 - Allow handshaking OR connections to take a full KeepalivePeriod
22804 seconds to handshake. Previously, we would close them after
22805 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22806 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22808 - When building with --enable-gcc-warnings on OpenBSD, disable
22809 warnings in system headers. This makes --enable-gcc-warnings
22810 pass on OpenBSD 4.8.
22813 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22814 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22815 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22816 Servers can start sending this code when enough clients recognize
22817 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
22818 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22819 Patch from mingw-san.
22822 - Remove the old debian/ directory from the main Tor distribution.
22823 The official Tor-for-debian git repository lives at the URL
22824 https://git.torproject.org/debian/tor.git
22825 - Stop shipping the old doc/website/ directory in the tarball. We
22826 changed the website format in late 2010, and what we shipped in
22827 0.2.1.26 really wasn't that useful anyway.
22830 Changes in version 0.2.2.19-alpha - 2010-11-22
22831 Yet another OpenSSL security patch broke its compatibility with Tor:
22832 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
22835 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22836 No longer set the tlsext_host_name extension on server SSL objects;
22837 but continue to set it on client SSL objects. Our goal in setting
22838 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22839 bugfix on 0.2.1.1-alpha.
22842 - Try harder not to exceed the maximum length of 50 KB when writing
22843 statistics to extra-info descriptors. This bug was triggered by very
22844 fast relays reporting exit-port, entry, and dirreq statistics.
22845 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
22846 - Publish a router descriptor even if generating an extra-info
22847 descriptor fails. Previously we would not publish a router
22848 descriptor without an extra-info descriptor; this can cause fast
22849 exit relays collecting exit-port statistics to drop from the
22850 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
22853 Changes in version 0.2.2.18-alpha - 2010-11-16
22854 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
22855 us lately, makes unpublished bridge relays able to detect their IP
22856 address, and fixes a wide variety of other bugs to get us much closer
22857 to a stable release.
22860 - Do even more to reject (and not just ignore) annotations on
22861 router descriptors received anywhere but from the cache. Previously
22862 we would ignore such annotations at first, but cache them to disk
22863 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22864 - Do not log messages to the controller while shrinking buffer
22865 freelists. Doing so would sometimes make the controller connection
22866 try to allocate a buffer chunk, which would mess up the internals
22867 of the freelist and cause an assertion failure. Fixes bug 1125;
22868 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22869 - Learn our external IP address when we're a relay or bridge, even if
22870 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22871 where we introduced bridge relays that don't need to publish to
22872 be useful. Fixes bug 2050.
22873 - Maintain separate TLS contexts and certificates for incoming and
22874 outgoing connections in bridge relays. Previously we would use the
22875 same TLS contexts and certs for incoming and outgoing connections.
22876 Bugfix on 0.2.0.3-alpha; addresses bug 988.
22877 - Maintain separate identity keys for incoming and outgoing TLS
22878 contexts in bridge relays. Previously we would use the same
22879 identity keys for incoming and outgoing TLS contexts. Bugfix on
22880 0.2.0.3-alpha; addresses the other half of bug 988.
22881 - Avoid an assertion failure when we as an authority receive a
22882 duplicate upload of a router descriptor that we already have,
22883 but which we previously considered an obsolete descriptor.
22884 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
22885 - Avoid a crash bug triggered by looking at a dangling pointer while
22886 setting the network status consensus. Found by Robert Ransom.
22887 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
22888 - Fix a logic error where servers that _didn't_ act as exits would
22889 try to keep their server lists more aggressively up to date than
22890 exits, when it was supposed to be the other way around. Bugfix
22893 o Minor bugfixes (on Tor 0.2.1.x and earlier):
22894 - When we're trying to guess whether we know our IP address as
22895 a relay, we would log various ways that we failed to guess
22896 our address, but never log that we ended up guessing it
22897 successfully. Now add a log line to help confused and anxious
22898 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
22899 - Bring the logic that gathers routerinfos and assesses the
22900 acceptability of circuits into line. This prevents a Tor OP from
22901 getting locked in a cycle of choosing its local OR as an exit for a
22902 path (due to a .exit request) and then rejecting the circuit because
22903 its OR is not listed yet. It also prevents Tor clients from using an
22904 OR running in the same instance as an exit (due to a .exit request)
22905 if the OR does not meet the same requirements expected of an OR
22906 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22907 - Correctly describe errors that occur when generating a TLS object.
22908 Previously we would attribute them to a failure while generating a
22909 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
22911 - Enforce multiplicity rules when parsing annotations. Bugfix on
22912 0.2.0.8-alpha. Found by piebeer.
22913 - Fix warnings that newer versions of autoconf produced during
22914 ./autogen.sh. These warnings appear to be harmless in our case,
22915 but they were extremely verbose. Fixes bug 2020.
22917 o Minor bugfixes (on Tor 0.2.2.x):
22918 - Enable protection of small arrays whenever we build with gcc
22919 hardening features, not only when also building with warnings
22920 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
22923 - Make hidden services work better in private Tor networks by not
22924 requiring any uptime to join the hidden service descriptor
22925 DHT. Implements ticket 2088.
22926 - Rate-limit the "your application is giving Tor only an IP address"
22927 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
22928 - When AllowSingleHopExits is set, print a warning to explain to the
22929 relay operator why most clients are avoiding her relay.
22930 - Update to the November 1 2010 Maxmind GeoLite Country database.
22932 o Code simplifications and refactoring:
22933 - When we fixed bug 1038 we had to put in a restriction not to send
22934 RELAY_EARLY cells on rend circuits. This was necessary as long
22935 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
22936 active. Now remove this obsolete check. Resolves bug 2081.
22937 - Some options used different conventions for uppercasing of acronyms
22938 when comparing manpage and source. Fix those in favor of the
22939 manpage, as it makes sense to capitalize acronyms.
22940 - Remove the torrc.complete file. It hasn't been kept up to date
22941 and users will have better luck checking out the manpage.
22942 - Remove the obsolete "NoPublish" option; it has been flagged
22943 as obsolete and has produced a warning since 0.1.1.18-rc.
22944 - Remove everything related to building the expert bundle for OS X.
22945 It has confused many users, doesn't work right on OS X 10.6,
22946 and is hard to get rid of once installed. Resolves bug 1274.
22949 Changes in version 0.2.2.17-alpha - 2010-09-30
22950 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
22951 to use one-hop circuits (which can put the exit relays at higher risk,
22952 plus unbalance the network); fixes a big bug in bandwidth accounting
22953 for relays that want to limit their monthly bandwidth use; fixes a
22954 big pile of bugs in how clients tolerate temporary network failure;
22955 and makes our adaptive circuit build timeout feature (which improves
22956 client performance if your network is fast while not breaking things
22957 if your network is slow) better handle bad networks.
22960 - Exit relays now try harder to block exit attempts from unknown
22961 relays, to make it harder for people to use them as one-hop proxies
22962 a la tortunnel. Controlled by the refuseunknownexits consensus
22963 parameter (currently enabled), or you can override it on your
22964 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
22966 o Major bugfixes (0.2.1.x and earlier):
22967 - Fix a bug in bandwidth accounting that could make us use twice
22968 the intended bandwidth when our interval start changes due to
22969 daylight saving time. Now we tolerate skew in stored vs computed
22970 interval starts: if the start of the period changes by no more than
22971 50% of the period's duration, we remember bytes that we transferred
22972 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
22973 - Always search the Windows system directory for system DLLs, and
22974 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
22975 - When you're using bridges and your network goes away and your
22976 bridges get marked as down, recover when you attempt a new socks
22977 connection (if the network is back), rather than waiting up to an
22978 hour to try fetching new descriptors for your bridges. Bugfix on
22979 0.2.0.3-alpha; fixes bug 1981.
22981 o Major bugfixes (on 0.2.2.x):
22982 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
22984 - Fix a segfault that could happen when operating a bridge relay with
22985 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
22986 - The consensus bandwidth-weights (used by clients to choose fast
22987 relays) entered an unexpected edge case in September where
22988 Exits were much scarcer than Guards, resulting in bad weight
22989 recommendations. Now we compute them using new constraints that
22990 should succeed in all cases. Also alter directory authorities to
22991 not include the bandwidth-weights line if they fail to produce
22992 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
22993 - When weighting bridges during path selection, we used to trust
22994 the bandwidths they provided in their descriptor, only capping them
22995 at 10MB/s. This turned out to be problematic for two reasons:
22996 Bridges could claim to handle a lot more traffic then they
22997 actually would, thus making more clients pick them and have a
22998 pretty effective DoS attack. The other issue is that new bridges
22999 that might not have a good estimate for their bw capacity yet
23000 would not get used at all unless no other bridges are available
23001 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
23003 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
23004 - Ignore cannibalized circuits when recording circuit build times.
23005 This should provide for a minor performance improvement for hidden
23006 service users using 0.2.2.14-alpha, and should remove two spurious
23007 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
23008 - Simplify the logic that causes us to decide if the network is
23009 unavailable for purposes of recording circuit build times. If we
23010 receive no cells whatsoever for the entire duration of a circuit's
23011 full measured lifetime, the network is probably down. Also ignore
23012 one-hop directory fetching circuit timeouts when calculating our
23013 circuit build times. These changes should hopefully reduce the
23014 cases where we see ridiculous circuit build timeouts for people
23015 with spotty wireless connections. Fixes part of bug 1772; bugfix
23017 - Prevent the circuit build timeout from becoming larger than
23018 the maximum build time we have ever seen. Also, prevent the time
23019 period for measurement circuits from becoming larger than twice that
23020 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
23023 - When we run out of directory information such that we can't build
23024 circuits, but then get enough that we can build circuits, log when
23025 we actually construct a circuit, so the user has a better chance of
23026 knowing what's going on. Fixes bug 1362.
23027 - Be more generous with how much bandwidth we'd use up (with
23028 accounting enabled) before entering "soft hibernation". Previously,
23029 we'd refuse new connections and circuits once we'd used up 95% of
23030 our allotment. Now, we use up 95% of our allotment, AND make sure
23031 that we have no more than 500MB (or 3 hours of expected traffic,
23032 whichever is lower) remaining before we enter soft hibernation.
23033 - If we've configured EntryNodes and our network goes away and/or all
23034 our entrynodes get marked down, optimistically retry them all when
23035 a new socks application request appears. Fixes bug 1882.
23036 - Add some more defensive programming for architectures that can't
23037 handle unaligned integer accesses. We don't know of any actual bugs
23038 right now, but that's the best time to fix them. Fixes bug 1943.
23039 - Support line continuations in the torrc config file. If a line
23040 ends with a single backslash character, the newline is ignored, and
23041 the configuration value is treated as continuing on the next line.
23044 o Minor bugfixes (on 0.2.1.x and earlier):
23045 - For bandwidth accounting, calculate our expected bandwidth rate
23046 based on the time during which we were active and not in
23047 soft-hibernation during the last interval. Previously, we were
23048 also considering the time spent in soft-hibernation. If this
23049 was a long time, we would wind up underestimating our bandwidth
23050 by a lot, and skewing our wakeup time towards the start of the
23051 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
23053 o Minor bugfixes (on 0.2.2.x):
23054 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
23055 which were disabled by the circuit build timeout changes in
23056 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
23057 - Make sure we don't warn about missing bandwidth weights when
23058 choosing bridges or other relays not in the consensus. Bugfix on
23059 0.2.2.10-alpha; fixes bug 1805.
23060 - In our logs, do not double-report signatures from unrecognized
23061 authorities both as "from unknown authority" and "not
23062 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
23065 Changes in version 0.2.2.16-alpha - 2010-09-17
23066 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
23067 evident at exit relays), and also continues to resolve all the little
23068 bugs that have been filling up trac lately.
23070 o Major bugfixes (stream-level fairness):
23071 - When receiving a circuit-level SENDME for a blocked circuit, try
23072 to package cells fairly from all the streams that had previously
23073 been blocked on that circuit. Previously, we had started with the
23074 oldest stream, and allowed each stream to potentially exhaust
23075 the circuit's package window. This gave older streams on any
23076 given circuit priority over newer ones. Fixes bug 1937. Detected
23077 originally by Camilo Viecco. This bug was introduced before the
23078 first Tor release, in svn commit r152: it is the new winner of
23079 the longest-lived bug prize.
23080 - When the exit relay got a circuit-level sendme cell, it started
23081 reading on the exit streams, even if had 500 cells queued in the
23082 circuit queue already, so the circuit queue just grew and grew in
23083 some cases. We fix this by not re-enabling reading on receipt of a
23084 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
23085 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
23087 - Newly created streams were allowed to read cells onto circuits,
23088 even if the circuit's cell queue was blocked and waiting to drain.
23089 This created potential unfairness, as older streams would be
23090 blocked, but newer streams would gladly fill the queue completely.
23091 We add code to detect this situation and prevent any stream from
23092 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
23096 - Update to the September 1 2010 Maxmind GeoLite Country database.
23097 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
23098 not. This would lead to a cookie that is still not group readable.
23099 Closes bug 1843. Suggested by katmagic.
23100 - When logging a rate-limited warning, we now mention how many messages
23101 got suppressed since the last warning.
23102 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
23103 do individual connection-level rate limiting of clients. The torrc
23104 config options with the same names trump the consensus params, if
23105 both are present. Replaces the old "bwconnrate" and "bwconnburst"
23106 consensus params which were broken from 0.2.2.7-alpha through
23107 0.2.2.14-alpha. Closes bug 1947.
23108 - When a router changes IP address or port, authorities now launch
23109 a new reachability test for it. Implements ticket 1899.
23110 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
23111 2 no signature, 4 required" messages about consensus signatures
23112 easier to read, and make sure they get logged at the same severity
23113 as the messages explaining which keys are which. Fixes bug 1290.
23114 - Don't warn when we have a consensus that we can't verify because
23115 of missing certificates, unless those certificates are ones
23116 that we have been trying and failing to download. Fixes bug 1145.
23117 - If you configure your bridge with a known identity fingerprint,
23118 and the bridge authority is unreachable (as it is in at least
23119 one country now), fall back to directly requesting the descriptor
23120 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
23122 - When building with --enable-gcc-warnings on OpenBSD, disable
23123 warnings in system headers. This makes --enable-gcc-warnings
23124 pass on OpenBSD 4.8.
23126 o Minor bugfixes (on 0.2.1.x and earlier):
23127 - Authorities will now attempt to download consensuses if their
23128 own efforts to make a live consensus have failed. This change
23129 means authorities that restart will fetch a valid consensus, and
23130 it means authorities that didn't agree with the current consensus
23131 will still fetch and serve it if it has enough signatures. Bugfix
23132 on 0.2.0.9-alpha; fixes bug 1300.
23133 - Ensure DNS requests launched by "RESOLVE" commands from the
23134 controller respect the __LeaveStreamsUnattached setconf options. The
23135 same goes for requests launched via DNSPort or transparent
23136 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
23137 - Allow handshaking OR connections to take a full KeepalivePeriod
23138 seconds to handshake. Previously, we would close them after
23139 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
23140 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
23142 - Rate-limit "Failed to hand off onionskin" warnings.
23143 - Never relay a cell for a circuit we have already destroyed.
23144 Between marking a circuit as closeable and finally closing it,
23145 it may have been possible for a few queued cells to get relayed,
23146 even though they would have been immediately dropped by the next
23147 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
23148 - Never queue a cell for a circuit that's already been marked
23150 - Never vote for a server as "Running" if we have a descriptor for
23151 it claiming to be hibernating, and that descriptor was published
23152 more recently than our last contact with the server. Bugfix on
23153 0.2.0.3-alpha; fixes bug 911.
23154 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
23157 o Minor bugfixes (on 0.2.2.x):
23158 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
23159 down if a directory fetch fails and you've configured either
23160 bridges or EntryNodes. The intent was to mark the relay as down
23161 _unless_ you're using bridges or EntryNodes, since if you are
23162 then you could quickly run out of entry points.
23163 - Fix the Windows directory-listing code. A bug introduced in
23164 0.2.2.14-alpha could make Windows directory servers forget to load
23165 some of their cached v2 networkstatus files.
23166 - Really allow clients to use relays as bridges. Fixes bug 1776;
23167 bugfix on 0.2.2.15-alpha.
23168 - Demote a warn to info that happens when the CellStatistics option
23169 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
23170 Reported by Moritz Bartl.
23171 - On Windows, build correctly either with or without Unicode support.
23172 This is necessary so that Tor can support fringe platforms like
23173 Windows 98 (which has no Unicode), or Windows CE (which has no
23174 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
23177 - Add a unit test for cross-platform directory-listing code.
23180 Changes in version 0.2.2.15-alpha - 2010-08-18
23181 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
23182 fixes a variety of other bugs that were preventing performance
23183 experiments from moving forward, fixes several bothersome memory leaks,
23184 and generally closes a lot of smaller bugs that have been filling up
23188 - Stop assigning the HSDir flag to relays that disable their
23189 DirPort (and thus will refuse to answer directory requests). This
23190 fix should dramatically improve the reachability of hidden services:
23191 hidden services and hidden service clients pick six HSDir relays
23192 to store and retrieve the hidden service descriptor, and currently
23193 about half of the HSDir relays will refuse to work. Bugfix on
23194 0.2.0.10-alpha; fixes part of bug 1693.
23195 - The PerConnBWRate and Burst config options, along with the
23196 bwconnrate and bwconnburst consensus params, initialized each conn's
23197 token bucket values only when the connection is established. Now we
23198 update them if the config options change, and update them every time
23199 we get a new consensus. Otherwise we can encounter an ugly edge
23200 case where we initialize an OR conn to client-level bandwidth,
23201 but then later the relay joins the consensus and we leave it
23202 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
23203 - Fix a regression that caused Tor to rebind its ports if it receives
23204 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
23207 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
23208 should give us approximately 40-50% more Guard-flagged nodes,
23209 improving the anonymity the Tor network can provide and also
23210 decreasing the dropoff in throughput that relays experience when
23211 they first get the Guard flag.
23212 - Allow enabling or disabling the *Statistics config options while
23216 - Update to the August 1 2010 Maxmind GeoLite Country database.
23217 - Have the controller interface give a more useful message than
23218 "Internal Error" in response to failed GETINFO requests.
23219 - Warn when the same option is provided more than once in a torrc
23220 file, on the command line, or in a single SETCONF statement, and
23221 the option is one that only accepts a single line. Closes bug 1384.
23222 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
23223 Patch from mingw-san.
23224 - Add support for the country code "{??}" in torrc options like
23225 ExcludeNodes, to indicate all routers of unknown country. Closes
23227 - Relays report the number of bytes spent on answering directory
23228 requests in extra-info descriptors similar to {read,write}-history.
23229 Implements enhancement 1790.
23231 o Minor bugfixes (on 0.2.1.x and earlier):
23232 - Complain if PublishServerDescriptor is given multiple arguments that
23233 include 0 or 1. This configuration will be rejected in the future.
23234 Bugfix on 0.2.0.1-alpha; closes bug 1107.
23235 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
23236 Bugfix on 0.2.0.13-alpha; closes bug 928.
23237 - Change "Application request when we're believed to be offline."
23238 notice to "Application request when we haven't used client
23239 functionality lately.", to clarify that it's not an error. Bugfix
23240 on 0.0.9.3; fixes bug 1222.
23241 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
23242 would return "551 Internal error" rather than "552 Unrecognized key
23243 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
23244 - Users can't configure a regular relay to be their bridge. It didn't
23245 work because when Tor fetched the bridge descriptor, it found
23246 that it already had it, and didn't realize that the purpose of the
23247 descriptor had changed. Now we replace routers with a purpose other
23248 than bridge with bridge descriptors when fetching them. Bugfix on
23249 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
23250 refetch the descriptor with router purpose 'general', disabling
23252 - Fix a rare bug in rend_fn unit tests: we would fail a test when
23253 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
23254 on 0.2.0.10-alpha; fixes bug 1808.
23255 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
23256 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
23257 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
23258 Servers can start sending this code when enough clients recognize
23259 it. Also update the spec to reflect this new reason. Bugfix on
23260 0.1.0.1-rc; fixes part of bug 1793.
23261 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
23262 when we switch from being a public relay to a bridge. Otherwise
23263 there will still be clients that see the relay in their consensus,
23264 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
23266 - Instead of giving an assertion failure on an internal mismatch
23267 on estimated freelist size, just log a BUG warning and try later.
23268 Mitigates but does not fix bug 1125.
23269 - Fix an assertion failure that could occur in caches or bridge users
23270 when using a very short voting interval on a testing network.
23271 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
23273 o Minor bugfixes (on 0.2.2.x):
23274 - Alter directory authorities to always consider Exit-flagged nodes
23275 as potential Guard nodes in their votes. The actual decision to
23276 use Exits as Guards is done in the consensus bandwidth weights.
23277 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
23278 - When the controller is reporting the purpose of circuits that
23279 didn't finish building before the circuit build timeout, it was
23280 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
23281 - Our libevent version parsing code couldn't handle versions like
23282 1.4.14b-stable and incorrectly warned the user about using an
23283 old and broken version of libevent. Treat 1.4.14b-stable like
23284 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
23286 - Don't use substitution references like $(VAR:MOD) when
23287 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
23288 '$(:x)' to 'x' rather than the empty string. This bites us in
23289 doc/ when configured with --disable-asciidoc. Bugfix on
23290 0.2.2.9-alpha; fixes bug 1773.
23291 - Remove a spurious hidden service server-side log notice about
23292 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
23294 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
23296 - Correctly report written bytes on linked connections. Found while
23297 implementing 1790. Bugfix on 0.2.2.4-alpha.
23298 - Fix three memory leaks: one in circuit_build_times_parse_state(),
23299 one in dirvote_add_signatures_to_pending_consensus(), and one every
23300 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
23301 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
23303 o Code simplifications and refactoring:
23304 - Take a first step towards making or.h smaller by splitting out
23305 function definitions for all source files in src/or/. Leave
23306 structures and defines in or.h for now.
23307 - Remove a bunch of unused function declarations as well as a block of
23308 #if 0'd code from the unit tests. Closes bug 1824.
23309 - New unit tests for exit-port history statistics; refactored exit
23310 statistics code to be more easily tested.
23311 - Remove the old debian/ directory from the main Tor distribution.
23312 The official Tor-for-debian git repository lives at the URL
23313 https://git.torproject.org/debian/tor.git
23316 Changes in version 0.2.2.14-alpha - 2010-07-12
23317 Tor 0.2.2.14-alpha greatly improves client-side handling of
23318 circuit build timeouts, which are used to estimate speed and improve
23319 performance. We also move to a much better GeoIP database, port Tor to
23320 Windows CE, introduce new compile flags that improve code security,
23321 add an eighth v3 directory authority, and address a lot of more
23325 - Tor directory authorities no longer crash when started with a
23326 cached-microdesc-consensus file in their data directory. Bugfix
23327 on 0.2.2.6-alpha; fixes bug 1532.
23328 - Treat an unset $HOME like an empty $HOME rather than triggering an
23329 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
23330 - Ignore negative and large circuit build timeout values that can
23331 happen during a suspend or hibernate. These values caused various
23332 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
23333 - Alter calculation of Pareto distribution parameter 'Xm' for
23334 Circuit Build Timeout learning to use the weighted average of the
23335 top N=3 modes (because we have three entry guards). Considering
23336 multiple modes should improve the timeout calculation in some cases,
23337 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
23339 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
23340 right censored distribution model. This approach improves over the
23341 synthetic timeout generation approach that was producing insanely
23342 high timeout values. Now we calculate build timeouts using truncated
23343 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
23344 - Do not close circuits that are under construction when they reach
23345 the circuit build timeout. Instead, leave them building (but do not
23346 use them) for up until the time corresponding to the 95th percentile
23347 on the Pareto CDF or 60 seconds, whichever is greater. This is done
23348 to provide better data for the new Pareto model. This percentile
23349 can be controlled by the consensus.
23352 - Move to the June 2010 Maxmind GeoLite country db (rather than the
23353 June 2009 ip-to-country GeoIP db) for our statistics that count
23354 how many users relays are seeing from each country. Now we have
23355 more accurate data for many African countries.
23356 - Port Tor to build and run correctly on Windows CE systems, using
23357 the wcecompat library. Contributed by Valerio Lupi.
23358 - New "--enable-gcc-hardening" ./configure flag (off by default)
23359 to turn on gcc compile time hardening options. It ensures
23360 that signed ints have defined behavior (-fwrapv), enables
23361 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
23362 with canaries (-fstack-protector-all), turns on ASLR protection if
23363 supported by the kernel (-fPIE, -pie), and adds additional security
23364 related warnings. Verified to work on Mac OS X and Debian Lenny.
23365 - New "--enable-linker-hardening" ./configure flag (off by default)
23366 to turn on ELF specific hardening features (relro, now). This does
23367 not work with Mac OS X or any other non-ELF binary format.
23369 o New directory authorities:
23370 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
23374 - New config option "WarnUnsafeSocks 0" disables the warning that
23375 occurs whenever Tor receives a socks handshake using a version of
23376 the socks protocol that can only provide an IP address (rather
23377 than a hostname). Setups that do DNS locally over Tor are fine,
23378 and we shouldn't spam the logs in that case.
23379 - Convert the HACKING file to asciidoc, and add a few new sections
23380 to it, explaining how we use Git, how we make changelogs, and
23381 what should go in a patch.
23382 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
23383 event, to give information on the current rate of circuit timeouts
23384 over our stored history.
23385 - Add ability to disable circuit build time learning via consensus
23386 parameter and via a LearnCircuitBuildTimeout config option. Also
23387 automatically disable circuit build time calculation if we are
23388 either a AuthoritativeDirectory, or if we fail to write our state
23389 file. Fixes bug 1296.
23390 - More gracefully handle corrupt state files, removing asserts
23391 in favor of saving a backup and resetting state.
23392 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
23396 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
23398 - When a2x fails, mention that the user could disable manpages instead
23399 of trying to fix their asciidoc installation.
23400 - Where available, use Libevent 2.0's periodic timers so that our
23401 once-per-second cleanup code gets called even more closely to
23402 once per second than it would otherwise. Fixes bug 943.
23403 - If you run a bridge that listens on multiple IP addresses, and
23404 some user configures a bridge address that uses a different IP
23405 address than your bridge writes in its router descriptor, and the
23406 user doesn't specify an identity key, their Tor would discard the
23407 descriptor because "it isn't one of our configured bridges", and
23408 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
23409 Bugfix on 0.2.0.3-alpha.
23410 - If OpenSSL fails to make a duplicate of a private or public key, log
23411 an error message and try to exit cleanly. May help with debugging
23412 if bug 1209 ever remanifests.
23413 - Save a couple bytes in memory allocation every time we escape
23414 certain characters in a string. Patch from Florian Zumbiehl.
23415 - Make it explicit that we don't cannibalize one-hop circuits. This
23416 happens in the wild, but doesn't turn out to be a problem because
23417 we fortunately don't use those circuits. Many thanks to outofwords
23418 for the initial analysis and to swissknife who confirmed that
23419 two-hop circuits are actually created.
23420 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
23421 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
23422 - Eliminate a case where a circuit build time warning was displayed
23423 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
23426 Changes in version 0.2.1.26 - 2010-05-02
23427 Tor 0.2.1.26 addresses the recent connection and memory overload
23428 problems we've been seeing on relays, especially relays with their
23429 DirPort open. If your relay has been crashing, or you turned it off
23430 because it used too many resources, give this release a try.
23432 This release also fixes yet another instance of broken OpenSSL libraries
23433 that was causing some relays to drop out of the consensus.
23436 - Teach relays to defend themselves from connection overload. Relays
23437 now close idle circuits early if it looks like they were intended
23438 for directory fetches. Relays are also more aggressive about closing
23439 TLS connections that have no circuits on them. Such circuits are
23440 unlikely to be re-used, and tens of thousands of them were piling
23441 up at the fast relays, causing the relays to run out of sockets
23442 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23443 their directory fetches over TLS).
23444 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23445 that claim to be earlier than 0.9.8m, but which have in reality
23446 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23447 behavior. Possible fix for some cases of bug 1346.
23448 - Directory mirrors were fetching relay descriptors only from v2
23449 directory authorities, rather than v3 authorities like they should.
23450 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23451 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23454 - Finally get rid of the deprecated and now harmful notion of "clique
23455 mode", where directory authorities maintain TLS connections to
23459 - In the util/threads test, no longer free the test_mutex before all
23460 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23461 - The master thread could starve the worker threads quite badly on
23462 certain systems, causing them to run only partially in the allowed
23463 window. This resulted in test failures. Now the master thread sleeps
23464 occasionally for a few microseconds while the two worker-threads
23465 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23468 Changes in version 0.2.2.13-alpha - 2010-04-24
23469 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
23470 problems we've been seeing on relays, especially relays with their
23471 DirPort open. If your relay has been crashing, or you turned it off
23472 because it used too many resources, give this release a try.
23475 - Teach relays to defend themselves from connection overload. Relays
23476 now close idle circuits early if it looks like they were intended
23477 for directory fetches. Relays are also more aggressive about closing
23478 TLS connections that have no circuits on them. Such circuits are
23479 unlikely to be re-used, and tens of thousands of them were piling
23480 up at the fast relays, causing the relays to run out of sockets
23481 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23482 their directory fetches over TLS).
23485 - Finally get rid of the deprecated and now harmful notion of "clique
23486 mode", where directory authorities maintain TLS connections to
23488 - Directory authorities now do an immediate reachability check as soon
23489 as they hear about a new relay. This change should slightly reduce
23490 the time between setting up a relay and getting listed as running
23491 in the consensus. It should also improve the time between setting
23492 up a bridge and seeing use by bridge users.
23493 - Directory authorities no longer launch a TLS connection to every
23494 relay as they startup. Now that we have 2k+ descriptors cached,
23495 the resulting network hiccup is becoming a burden. Besides,
23496 authorities already avoid voting about Running for the first half
23497 hour of their uptime.
23500 Changes in version 0.2.2.12-alpha - 2010-04-20
23501 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
23502 handle and vote on descriptors. It was causing relays to drop out of
23506 - Many relays have been falling out of the consensus lately because
23507 not enough authorities know about their descriptor for them to get
23508 a majority of votes. When we deprecated the v2 directory protocol,
23509 we got rid of the only way that v3 authorities can hear from each
23510 other about other descriptors. Now authorities examine every v3
23511 vote for new descriptors, and fetch them from that authority. Bugfix
23513 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
23514 and a warning in or.h related to bandwidth_weight_rule_t that
23515 prevented clean compile on OS X. Fixes bug 1363; bugfix on
23517 - Fix a segfault on relays when DirReqStatistics is enabled
23518 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
23522 - Demote a confusing TLS warning that relay operators might get when
23523 someone tries to talk to their OrPort. It is neither the operator's
23524 fault nor can they do anything about it. Fixes bug 1364; bugfix
23528 Changes in version 0.2.2.11-alpha - 2010-04-15
23529 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
23530 libraries that was causing some relays to drop out of the consensus.
23533 - Directory mirrors were fetching relay descriptors only from v2
23534 directory authorities, rather than v3 authorities like they should.
23535 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23536 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23537 - Fix a parsing error that made every possible value of
23538 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
23539 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
23540 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
23541 about the option without breaking older ones.
23542 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23543 that claim to be earlier than 0.9.8m, but which have in reality
23544 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23545 behavior. Possible fix for some cases of bug 1346.
23548 - Experiment with a more aggressive approach to preventing clients
23549 from making one-hop exit streams. Exit relays who want to try it
23550 out can set "RefuseUnknownExits 1" in their torrc, and then look
23551 for "Attempt by %s to open a stream" log messages. Let us know
23553 - Add support for statically linking zlib by specifying
23554 --enable-static-zlib, to go with our support for statically linking
23555 openssl and libevent. Resolves bug 1358.
23558 - Fix a segfault that happens whenever a Tor client that is using
23559 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
23561 - When we cleaned up the contrib/tor-exit-notice.html file, we left
23562 out the first line. Fixes bug 1295.
23563 - When building the manpage from a tarball, we required asciidoc, but
23564 the asciidoc -> roff/html conversion was already done for the
23565 tarball. Make 'make' complain only when we need asciidoc (either
23566 because we're compiling directly from git, or because we altered
23567 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
23568 - When none of the directory authorities vote on any params, Tor
23569 segfaulted when trying to make the consensus from the votes. We
23570 didn't trigger the bug in practice, because authorities do include
23571 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
23574 - In the util/threads test, no longer free the test_mutex before all
23575 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23576 - The master thread could starve the worker threads quite badly on
23577 certain systems, causing them to run only partially in the allowed
23578 window. This resulted in test failures. Now the master thread sleeps
23579 occasionally for a few microseconds while the two worker-threads
23580 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23583 Changes in version 0.2.2.10-alpha - 2010-03-07
23584 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
23585 could prevent relays from guessing their IP address correctly. It also
23586 starts the groundwork for another client-side performance boost, since
23587 currently we're not making efficient use of relays that have both the
23588 Guard flag and the Exit flag.
23591 - Fix a regression from our patch for bug 1244 that caused relays
23592 to guess their IP address incorrectly if they didn't set Address
23593 in their torrc and/or their address fails to resolve. Bugfix on
23594 0.2.2.9-alpha; fixes bug 1269.
23596 o Major features (performance):
23597 - Directory authorities now compute consensus weightings that instruct
23598 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
23599 and no flag. Clients that use these weightings will distribute
23600 network load more evenly across these different relay types. The
23601 weightings are in the consensus so we can change them globally in
23602 the future. Extra thanks to "outofwords" for finding some nasty
23603 security bugs in the first implementation of this feature.
23605 o Minor features (performance):
23606 - Always perform router selections using weighted relay bandwidth,
23607 even if we don't need a high capacity circuit at the time. Non-fast
23608 circuits now only differ from fast ones in that they can use relays
23609 not marked with the Fast flag. This "feature" could turn out to
23610 be a horrible bug; we should investigate more before it goes into
23614 - Allow disabling building of the manpages. Skipping the manpage
23615 speeds up the build considerably.
23617 o Minor bugfixes (on 0.2.2.x):
23618 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
23619 Bugfix on 0.2.2.9-alpha.
23620 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
23621 config option. Bugfix on 0.2.2.7-alpha.
23622 - Ship the asciidoc-helper file in the tarball, so that people can
23623 build from source if they want to, and touching the .1.txt files
23624 doesn't break the build. Bugfix on 0.2.2.9-alpha.
23626 o Minor bugfixes (on 0.2.1.x or earlier):
23627 - Fix a dereference-then-NULL-check sequence when publishing
23628 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23630 - Fix another dereference-then-NULL-check sequence. Bugfix on
23631 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23632 - Make sure we treat potentially not NUL-terminated strings correctly.
23633 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23635 o Code simplifications and refactoring:
23636 - Fix some urls in the exit notice file and make it XHTML1.1 strict
23637 compliant. Based on a patch from Christian Kujau.
23638 - Don't use sed in asciidoc-helper anymore.
23639 - Make the build process fail if asciidoc cannot be found and
23640 building with asciidoc isn't disabled.
23643 Changes in version 0.2.2.9-alpha - 2010-02-22
23644 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
23645 location of a directory authority, and cleans up a bunch of small bugs.
23647 o Directory authority changes:
23648 - Change IP address for dannenberg (v3 directory authority), and
23649 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23650 service directory authority) from the list.
23653 - Make Tor work again on the latest OS X: when deciding whether to
23654 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23655 version at run-time, not compile time. We need to do this because
23656 Apple doesn't update its dev-tools headers when it updates its
23657 libraries in a security patch.
23658 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23659 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23660 a memory leak when requesting a hidden service descriptor we've
23661 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23663 - Authorities could be tricked into giving out the Exit flag to relays
23664 that didn't allow exiting to any ports. This bug could screw
23665 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
23666 1238. Bug discovered by Martin Kowalczyk.
23667 - When freeing a session key, zero it out completely. We only zeroed
23668 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23669 patched by ekir. Fixes bug 1254.
23672 - Fix static compilation by listing the openssl libraries in the right
23673 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
23674 - Resume handling .exit hostnames in a special way: originally we
23675 stripped the .exit part and used the requested exit relay. In
23676 0.2.2.1-alpha we stopped treating them in any special way, meaning
23677 if you use a .exit address then Tor will pass it on to the exit
23678 relay. Now we reject the .exit stream outright, since that behavior
23679 might be more expected by the user. Found and diagnosed by Scott
23680 Bennett and Downie on or-talk.
23681 - Don't spam the controller with events when we have no file
23682 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
23683 for log messages was already solved from bug 748.)
23684 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
23686 - Make the DNSPort option work with libevent 2.x. Don't alter the
23687 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
23688 - Emit a GUARD DROPPED controller event for a case we missed.
23689 - Make more fields in the controller protocol case-insensitive, since
23690 control-spec.txt said they were.
23691 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23692 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23693 - Fix a spec conformance issue: the network-status-version token
23694 must be the first token in a v3 consensus or vote. Discovered by
23695 parakeep. Bugfix on 0.2.0.3-alpha.
23697 o Code simplifications and refactoring:
23698 - Generate our manpage and HTML documentation using Asciidoc. This
23699 change should make it easier to maintain the documentation, and
23700 produce nicer HTML.
23701 - Remove the --enable-iphone option. According to reports from Marco
23702 Bonetti, Tor builds fine without any special tweaking on recent
23703 iPhone SDK versions.
23704 - Removed some unnecessary files from the source distribution. The
23705 AUTHORS file has now been merged into the people page on the
23706 website. The roadmaps and design doc can now be found in the
23707 projects directory in svn.
23708 - Enabled various circuit build timeout constants to be controlled
23709 by consensus parameters. Also set better defaults for these
23710 parameters based on experimentation on broadband and simulated
23711 high latency links.
23714 - The 'EXTENDCIRCUIT' control port command can now be used with
23715 a circ id of 0 and no path. This feature will cause Tor to build
23716 a new 'fast' general purpose circuit using its own path selection
23718 - Added a BUILDTIMEOUT_SET controller event to describe changes
23719 to the circuit build timeout.
23720 - Future-proof the controller protocol a bit by ignoring keyword
23721 arguments we do not recognize.
23722 - Expand homedirs passed to tor-checkkey. This should silence a
23723 coverity complaint about passing a user-supplied string into
23724 open() without checking it.
23727 Changes in version 0.2.1.25 - 2010-03-16
23728 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
23729 prevent relays from guessing their IP address correctly. It also fixes
23730 several minor potential security bugs.
23733 - Fix a regression from our patch for bug 1244 that caused relays
23734 to guess their IP address incorrectly if they didn't set Address
23735 in their torrc and/or their address fails to resolve. Bugfix on
23736 0.2.1.23; fixes bug 1269.
23737 - When freeing a session key, zero it out completely. We only zeroed
23738 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23739 patched by ekir. Fixes bug 1254.
23742 - Fix a dereference-then-NULL-check sequence when publishing
23743 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23745 - Fix another dereference-then-NULL-check sequence. Bugfix on
23746 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23747 - Make sure we treat potentially not NUL-terminated strings correctly.
23748 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23752 Changes in version 0.2.1.24 - 2010-02-21
23753 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
23757 - Work correctly out-of-the-box with even more vendor-patched versions
23758 of OpenSSL. In particular, make it so Debian and OS X don't need
23759 customized patches to run/build.
23762 Changes in version 0.2.1.23 - 2010-02-13
23763 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
23764 again on the latest OS X, and updates the location of a directory
23767 o Major bugfixes (performance):
23768 - We were selecting our guards uniformly at random, and then weighting
23769 which of our guards we'd use uniformly at random. This imbalance
23770 meant that Tor clients were severely limited on throughput (and
23771 probably latency too) by the first hop in their circuit. Now we
23772 select guards weighted by currently advertised bandwidth. We also
23773 automatically discard guards picked using the old algorithm. Fixes
23774 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23777 - Make Tor work again on the latest OS X: when deciding whether to
23778 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23779 version at run-time, not compile time. We need to do this because
23780 Apple doesn't update its dev-tools headers when it updates its
23781 libraries in a security patch.
23782 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23783 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23784 a memory leak when requesting a hidden service descriptor we've
23785 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23788 o Directory authority changes:
23789 - Change IP address for dannenberg (v3 directory authority), and
23790 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23791 service directory authority) from the list.
23794 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23795 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23798 - Avoid a mad rush at the beginning of each month when each client
23799 rotates half of its guards. Instead we spread the rotation out
23800 throughout the month, but we still avoid leaving a precise timestamp
23801 in the state file about when we first picked the guard. Improves
23802 over the behavior introduced in 0.1.2.17.
23805 Changes in version 0.2.2.8-alpha - 2010-01-26
23806 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
23807 causing bridge relays to disappear. If you're running a bridge,
23811 - Fix a memory corruption bug on bridges that occurred during the
23812 inclusion of stats data in extra-info descriptors. Also fix the
23813 interface for geoip_get_bridge_stats* to prevent similar bugs in
23814 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
23815 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
23818 - Ignore OutboundBindAddress when connecting to localhost.
23819 Connections to localhost need to come _from_ localhost, or else
23820 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
23824 Changes in version 0.2.2.7-alpha - 2010-01-19
23825 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
23826 as laying the groundwork for further relay-side performance fixes. It
23827 also starts cleaning up client behavior with respect to the EntryNodes,
23828 ExitNodes, and StrictNodes config options.
23830 This release also rotates two directory authority keys, due to a
23831 security breach of some of the Torproject servers.
23833 o Directory authority changes:
23834 - Rotate keys (both v3 identity and relay identity) for moria1
23837 o Major features (performance):
23838 - We were selecting our guards uniformly at random, and then weighting
23839 which of our guards we'd use uniformly at random. This imbalance
23840 meant that Tor clients were severely limited on throughput (and
23841 probably latency too) by the first hop in their circuit. Now we
23842 select guards weighted by currently advertised bandwidth. We also
23843 automatically discard guards picked using the old algorithm. Fixes
23844 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23845 - When choosing which cells to relay first, relays can now favor
23846 circuits that have been quiet recently, to provide lower latency
23847 for low-volume circuits. By default, relays enable or disable this
23848 feature based on a setting in the consensus. You can override
23849 this default by using the new "CircuitPriorityHalflife" config
23850 option. Design and code by Ian Goldberg, Can Tang, and Chris
23852 - Add separate per-conn write limiting to go with the per-conn read
23853 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
23854 but never per-conn write limits.
23855 - New consensus params "bwconnrate" and "bwconnburst" to let us
23856 rate-limit client connections as they enter the network. It's
23857 controlled in the consensus so we can turn it on and off for
23858 experiments. It's starting out off. Based on proposal 163.
23860 o Major features (relay selection options):
23861 - Switch to a StrictNodes config option, rather than the previous
23862 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
23863 "StrictExcludeNodes" option.
23864 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
23865 change during a config reload, mark and discard all our origin
23866 circuits. This fix should address edge cases where we change the
23867 config options and but then choose a circuit that we created before
23869 - If EntryNodes or ExitNodes are set, be more willing to use an
23870 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
23872 - Make EntryNodes config option much more aggressive even when
23873 StrictNodes is not set. Before it would prepend your requested
23874 entrynodes to your list of guard nodes, but feel free to use others
23875 after that. Now it chooses only from your EntryNodes if any of
23876 those are available, and only falls back to others if a) they're
23877 all down and b) StrictNodes is not set.
23878 - Now we refresh your entry guards from EntryNodes at each consensus
23879 fetch -- rather than just at startup and then they slowly rot as
23880 the network changes.
23883 - Stop bridge directory authorities from answering dbg-stability.txt
23884 directory queries, which would let people fetch a list of all
23885 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23888 - Log a notice when we get a new control connection. Now it's easier
23889 for security-conscious users to recognize when a local application
23890 is knocking on their controller door. Suggested by bug 1196.
23891 - New config option "CircuitStreamTimeout" to override our internal
23892 timeout schedule for how many seconds until we detach a stream from
23893 a circuit and try a new circuit. If your network is particularly
23894 slow, you might want to set this to a number like 60.
23895 - New controller command "getinfo config-text". It returns the
23896 contents that Tor would write if you send it a SAVECONF command,
23897 so the controller can write the file to disk itself.
23898 - New options for SafeLogging to allow scrubbing only log messages
23899 generated while acting as a relay.
23900 - Ship the bridges spec file in the tarball too.
23901 - Avoid a mad rush at the beginning of each month when each client
23902 rotates half of its guards. Instead we spread the rotation out
23903 throughout the month, but we still avoid leaving a precise timestamp
23904 in the state file about when we first picked the guard. Improves
23905 over the behavior introduced in 0.1.2.17.
23907 o Minor bugfixes (compiling):
23908 - Fix compilation on OS X 10.3, which has a stub mlockall() but
23909 hides it. Bugfix on 0.2.2.6-alpha.
23910 - Fix compilation on Solaris by removing support for the
23911 DisableAllSwap config option. Solaris doesn't have an rlimit for
23912 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
23915 o Minor bugfixes (crashes):
23916 - Do not segfault when writing buffer stats when we haven't observed
23917 a single circuit to report about. Found by Fabian Lanze. Bugfix on
23919 - If we're in the pathological case where there's no exit bandwidth
23920 but there is non-exit bandwidth, or no guard bandwidth but there
23921 is non-guard bandwidth, don't crash during path selection. Bugfix
23923 - Fix an impossible-to-actually-trigger buffer overflow in relay
23924 descriptor generation. Bugfix on 0.1.0.15.
23926 o Minor bugfixes (privacy):
23927 - Fix an instance where a Tor directory mirror might accidentally
23928 log the IP address of a misbehaving Tor client. Bugfix on
23930 - Don't list Windows capabilities in relay descriptors. We never made
23931 use of them, and maybe it's a bad idea to publish them. Bugfix
23934 o Minor bugfixes (other):
23935 - Resolve an edge case in path weighting that could make us misweight
23936 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
23937 - Fix statistics on client numbers by country as seen by bridges that
23938 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
23939 intervals instead of variable 12-to-48-hour intervals.
23940 - After we free an internal connection structure, overwrite it
23941 with a different memory value than we use for overwriting a freed
23942 internal circuit structure. Should help with debugging. Suggested
23944 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
23947 o Removed features:
23948 - Remove the HSAuthorityRecordStats option that version 0 hidden
23949 service authorities could have used to track statistics of overall
23950 hidden service usage.
23953 Changes in version 0.2.1.22 - 2010-01-19
23954 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
23955 authorities -- it would tell you its whole history of bridge descriptors
23956 if you make the right directory request. This stable update also
23957 rotates two of the seven v3 directory authority keys and locations.
23959 o Directory authority changes:
23960 - Rotate keys (both v3 identity and relay identity) for moria1
23964 - Stop bridge directory authorities from answering dbg-stability.txt
23965 directory queries, which would let people fetch a list of all
23966 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23969 Changes in version 0.2.1.21 - 2009-12-21
23970 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
23971 library. If you use Tor on Linux / Unix and you're getting SSL
23972 renegotiation errors, upgrading should help. We also recommend an
23973 upgrade if you're an exit relay.
23976 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23977 handshake from working unless we explicitly tell OpenSSL that we
23978 are using SSL renegotiation safely. We are, of course, but OpenSSL
23979 0.9.8l won't work unless we say we are.
23980 - Avoid crashing if the client is trying to upload many bytes and the
23981 circuit gets torn down at the same time, or if the flip side
23982 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
23985 - Do not refuse to learn about authority certs and v2 networkstatus
23986 documents that are older than the latest consensus. This bug might
23987 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23988 Spotted and fixed by xmux.
23989 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
23990 trigger platform-specific option misparsing case found by Coverity
23992 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
23993 trigger assert. Fixes bug 1173.
23996 Changes in version 0.2.2.6-alpha - 2009-11-19
23997 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
23998 support for the new lower-footprint "microdescriptor" directory design,
23999 future-proofing our consensus format against new hash functions or
24000 other changes, and an Android port. It also makes Tor compatible with
24001 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
24004 - Directory authorities can now create, vote on, and serve multiple
24005 parallel formats of directory data as part of their voting process.
24006 Partially implements Proposal 162: "Publish the consensus in
24008 - Directory authorities can now agree on and publish small summaries
24009 of router information that clients can use in place of regular
24010 server descriptors. This transition will eventually allow clients
24011 to use far less bandwidth for downloading information about the
24012 network. Begins the implementation of Proposal 158: "Clients
24013 download consensus + microdescriptors".
24014 - The directory voting system is now extensible to use multiple hash
24015 algorithms for signatures and resource selection. Newer formats
24016 are signed with SHA256, with a possibility for moving to a better
24017 hash algorithm in the future.
24018 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
24019 current and future memory pages via mlockall(). On supported
24020 platforms (modern Linux and probably BSD but not Windows or OS X),
24021 this should effectively disable any and all attempts to page out
24022 memory. This option requires that you start your Tor as root --
24023 if you use DisableAllSwap, please consider using the User option
24024 to properly reduce the privileges of your Tor.
24025 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
24026 to help Tor build correctly for Android phones.
24029 - Work around a security feature in OpenSSL 0.9.8l that prevents our
24030 handshake from working unless we explicitly tell OpenSSL that we
24031 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
24032 won't work unless we say we are.
24035 - Fix a crash bug when trying to initialize the evdns module in
24036 Libevent 2. Bugfix on 0.2.1.16-rc.
24037 - Stop logging at severity 'warn' when some other Tor client tries
24038 to establish a circuit with us using weak DH keys. It's a protocol
24039 violation, but that doesn't mean ordinary users need to hear about
24040 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
24041 - Do not refuse to learn about authority certs and v2 networkstatus
24042 documents that are older than the latest consensus. This bug might
24043 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
24044 Spotted and fixed by xmux.
24045 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
24046 - If all authorities restart at once right before a consensus vote,
24047 nobody will vote about "Running", and clients will get a consensus
24048 with no usable relays. Instead, authorities refuse to build a
24049 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
24050 - If your relay can't keep up with the number of incoming create
24051 cells, it would log one warning per failure into your logs. Limit
24052 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
24053 - Bridges now use "reject *:*" as their default exit policy. Bugfix
24054 on 0.2.0.3-alpha; fixes bug 1113.
24055 - Fix a memory leak on directory authorities during voting that was
24056 introduced in 0.2.2.1-alpha. Found via valgrind.
24059 Changes in version 0.2.1.20 - 2009-10-15
24060 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
24061 services at once, prepares for more performance improvements, and
24062 fixes a bunch of smaller bugs.
24064 The Windows and OS X bundles also include a more recent Vidalia,
24065 and switch from Privoxy to Polipo.
24067 The OS X installers are now drag and drop. It's best to un-install
24068 Tor/Vidalia and then install this new bundle, rather than upgrade. If
24069 you want to upgrade, you'll need to update the paths for Tor and Polipo
24070 in the Vidalia Settings window.
24073 - Send circuit or stream sendme cells when our window has decreased
24074 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24075 by Karsten when testing the "reduce circuit window" performance
24076 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24077 before the release of Tor 0.0.0. This is the new winner of the
24079 - Fix a remotely triggerable memory leak when a consensus document
24080 contains more than one signature from the same voter. Bugfix on
24082 - Avoid segfault in rare cases when finishing an introduction circuit
24083 as a client and finding out that we don't have an introduction key
24084 for it. Fixes bug 1073. Reported by Aaron Swartz.
24087 - Tor now reads the "circwindow" parameter out of the consensus,
24088 and uses that value for its circuit package window rather than the
24089 default of 1000 cells. Begins the implementation of proposal 168.
24091 o New directory authorities:
24092 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24094 - Move moria1 and tonga to alternate IP addresses.
24097 - Fix a signed/unsigned compile warning in 0.2.1.19.
24098 - Fix possible segmentation fault on directory authorities. Bugfix on
24100 - Fix an extremely rare infinite recursion bug that could occur if
24101 we tried to log a message after shutting down the log subsystem.
24102 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24103 - Fix an obscure bug where hidden services on 64-bit big-endian
24104 systems might mis-read the timestamp in v3 introduce cells, and
24105 refuse to connect back to the client. Discovered by "rotor".
24106 Bugfix on 0.2.1.6-alpha.
24107 - We were triggering a CLOCK_SKEW controller status event whenever
24108 we connect via the v2 connection protocol to any relay that has
24109 a wrong clock. Instead, we should only inform the controller when
24110 it's a trusted authority that claims our clock is wrong. Bugfix
24111 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24112 - We were telling the controller about CHECKING_REACHABILITY and
24113 REACHABILITY_FAILED status events whenever we launch a testing
24114 circuit or notice that one has failed. Instead, only tell the
24115 controller when we want to inform the user of overall success or
24116 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24118 - Don't warn when we're using a circuit that ends with a node
24119 excluded in ExcludeExitNodes, but the circuit is not used to access
24120 the outside world. This should help fix bug 1090. Bugfix on
24122 - Work around a small memory leak in some versions of OpenSSL that
24123 stopped the memory used by the hostname TLS extension from being
24127 - Add a "getinfo status/accepted-server-descriptor" controller
24128 command, which is the recommended way for controllers to learn
24129 whether our server descriptor has been successfully received by at
24130 least on directory authority. Un-recommend good-server-descriptor
24131 getinfo and status events until we have a better design for them.
24134 Changes in version 0.2.2.5-alpha - 2009-10-11
24135 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
24138 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
24140 o Directory authorities:
24141 - Temporarily (just for this release) move dizum to an alternate
24145 Changes in version 0.2.2.4-alpha - 2009-10-10
24146 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
24147 introduces a new unit test framework, shifts directry authority
24148 addresses around to reduce the impact from recent blocking events,
24149 and fixes a few smaller bugs.
24152 - Fix several more asserts in the circuit_build_times code, for
24153 example one that causes Tor to fail to start once we have
24154 accumulated 5000 build times in the state file. Bugfixes on
24155 0.2.2.2-alpha; fixes bug 1108.
24157 o New directory authorities:
24158 - Move moria1 and Tonga to alternate IP addresses.
24161 - Log SSL state transitions at debug level during handshake, and
24162 include SSL states in error messages. This may help debug future
24163 SSL handshake issues.
24164 - Add a new "Handshake" log domain for activities that happen
24165 during the TLS handshake.
24166 - Revert to the "June 3 2009" ip-to-country file. The September one
24167 seems to have removed most US IP addresses.
24168 - Directory authorities now reject Tor relays with versions less than
24169 0.1.2.14. This step cuts out four relays from the current network,
24170 none of which are very big.
24173 - Fix a couple of smaller issues with gathering statistics. Bugfixes
24175 - Fix two memory leaks in the error case of
24176 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
24177 - Don't count one-hop circuits when we're estimating how long it
24178 takes circuits to build on average. Otherwise we'll set our circuit
24179 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
24180 - Directory authorities no longer change their opinion of, or vote on,
24181 whether a router is Running, unless they have themselves been
24182 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
24185 o Code simplifications and refactoring:
24186 - Revise our unit tests to use the "tinytest" framework, so we
24187 can run tests in their own processes, have smarter setup/teardown
24188 code, and so on. The unit test code has moved to its own
24189 subdirectory, and has been split into multiple modules.
24192 Changes in version 0.2.2.3-alpha - 2009-09-23
24193 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
24196 - Fix an overzealous assert in our new circuit build timeout code.
24197 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
24200 - If the networkstatus consensus tells us that we should use a
24201 negative circuit package window, ignore it. Otherwise we'll
24202 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
24205 Changes in version 0.2.2.2-alpha - 2009-09-21
24206 Tor 0.2.2.2-alpha introduces our latest performance improvement for
24207 clients: Tor tracks the average time it takes to build a circuit, and
24208 avoids using circuits that take too long to build. For fast connections,
24209 this feature can cut your expected latency in half. For slow or flaky
24210 connections, it could ruin your Tor experience. Let us know if it does!
24213 - Tor now tracks how long it takes to build client-side circuits
24214 over time, and adapts its timeout to local network performance.
24215 Since a circuit that takes a long time to build will also provide
24216 bad performance, we get significant latency improvements by
24217 discarding the slowest 20% of circuits. Specifically, Tor creates
24218 circuits more aggressively than usual until it has enough data
24219 points for a good timeout estimate. Implements proposal 151.
24220 We are especially looking for reports (good and bad) from users with
24221 both EDGE and broadband connections that can move from broadband
24222 to EDGE and find out if the build-time data in the .tor/state gets
24223 reset without loss of Tor usability. You should also see a notice
24224 log message telling you that Tor has reset its timeout.
24225 - Directory authorities can now vote on arbitrary integer values as
24226 part of the consensus process. This is designed to help set
24227 network-wide parameters. Implements proposal 167.
24228 - Tor now reads the "circwindow" parameter out of the consensus,
24229 and uses that value for its circuit package window rather than the
24230 default of 1000 cells. Begins the implementation of proposal 168.
24233 - Fix a remotely triggerable memory leak when a consensus document
24234 contains more than one signature from the same voter. Bugfix on
24238 - Fix an extremely rare infinite recursion bug that could occur if
24239 we tried to log a message after shutting down the log subsystem.
24240 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24241 - Fix parsing for memory or time units given without a space between
24242 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
24243 - A networkstatus vote must contain exactly one signature. Spec
24244 conformance issue. Bugfix on 0.2.0.3-alpha.
24245 - Fix an obscure bug where hidden services on 64-bit big-endian
24246 systems might mis-read the timestamp in v3 introduce cells, and
24247 refuse to connect back to the client. Discovered by "rotor".
24248 Bugfix on 0.2.1.6-alpha.
24249 - We were triggering a CLOCK_SKEW controller status event whenever
24250 we connect via the v2 connection protocol to any relay that has
24251 a wrong clock. Instead, we should only inform the controller when
24252 it's a trusted authority that claims our clock is wrong. Bugfix
24253 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24254 - We were telling the controller about CHECKING_REACHABILITY and
24255 REACHABILITY_FAILED status events whenever we launch a testing
24256 circuit or notice that one has failed. Instead, only tell the
24257 controller when we want to inform the user of overall success or
24258 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24260 - Don't warn when we're using a circuit that ends with a node
24261 excluded in ExcludeExitNodes, but the circuit is not used to access
24262 the outside world. This should help fix bug 1090, but more problems
24263 remain. Bugfix on 0.2.1.6-alpha.
24264 - Work around a small memory leak in some versions of OpenSSL that
24265 stopped the memory used by the hostname TLS extension from being
24267 - Make our 'torify' script more portable; if we have only one of
24268 'torsocks' or 'tsocks' installed, don't complain to the user;
24269 and explain our warning about tsocks better.
24272 - Add a "getinfo status/accepted-server-descriptor" controller
24273 command, which is the recommended way for controllers to learn
24274 whether our server descriptor has been successfully received by at
24275 least on directory authority. Un-recommend good-server-descriptor
24276 getinfo and status events until we have a better design for them.
24277 - Update to the "September 4 2009" ip-to-country file.
24280 Changes in version 0.2.2.1-alpha - 2009-08-26
24281 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
24282 Tor clients to bootstrap on networks where only port 80 is reachable,
24283 makes it more straightforward to support hardware crypto accelerators,
24284 and starts the groundwork for gathering stats safely at relays.
24287 - Start the process of disabling ".exit" address notation, since it
24288 can be used for a variety of esoteric application-level attacks
24289 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
24292 o New directory authorities:
24293 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24297 - New AccelName and AccelDir options add support for dynamic OpenSSL
24298 hardware crypto acceleration engines.
24299 - Tor now supports tunneling all of its outgoing connections over
24300 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
24301 configuration options. Code by Christopher Davis.
24304 - Send circuit or stream sendme cells when our window has decreased
24305 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24306 by Karsten when testing the "reduce circuit window" performance
24307 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24308 before the release of Tor 0.0.0. This is the new winner of the
24311 o New options for gathering stats safely:
24312 - Directory mirrors that set "DirReqStatistics 1" write statistics
24313 about directory requests to disk every 24 hours. As compared to the
24314 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
24315 1) stats are written to disk exactly every 24 hours; 2) estimated
24316 shares of v2 and v3 requests are determined as mean values, not at
24317 the end of a measurement period; 3) unresolved requests are listed
24318 with country code '??'; 4) directories also measure download times.
24319 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
24320 number of exit streams and transferred bytes per port to disk every
24322 - Relays that set "CellStatistics 1" write statistics on how long
24323 cells spend in their circuit queues to disk every 24 hours.
24324 - Entry nodes that set "EntryStatistics 1" write statistics on the
24325 rough number and origins of connecting clients to disk every 24
24327 - Relays that write any of the above statistics to disk and set
24328 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
24329 their extra-info documents.
24332 - New --digests command-line switch to output the digests of the
24333 source files Tor was built with.
24334 - The "torify" script now uses torsocks where available.
24335 - The memarea code now uses a sentinel value at the end of each area
24336 to make sure nothing writes beyond the end of an area. This might
24337 help debug some conceivable causes of bug 930.
24338 - Time and memory units in the configuration file can now be set to
24339 fractional units. For example, "2.5 GB" is now a valid value for
24341 - Certain Tor clients (such as those behind check.torproject.org) may
24342 want to fetch the consensus in an extra early manner. To enable this
24343 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
24344 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
24345 as only certain clients who must have this information sooner should
24347 - Instead of adding the svn revision to the Tor version string, report
24348 the git commit (when we're building from a git checkout).
24351 - If any of the v3 certs we download are unparseable, we should
24352 actually notice the failure so we don't retry indefinitely. Bugfix
24353 on 0.2.0.x; reported by "rotator".
24354 - If the cached cert file is unparseable, warn but don't exit.
24355 - Fix possible segmentation fault on directory authorities. Bugfix on
24357 - When Tor fails to parse a descriptor of any kind, dump it to disk.
24358 Might help diagnosing bug 1051.
24360 o Deprecated and removed features:
24361 - The controller no longer accepts the old obsolete "addr-mappings/"
24362 or "unregistered-servers-" GETINFO values.
24363 - Hidden services no longer publish version 0 descriptors, and clients
24364 do not request or use version 0 descriptors. However, the old hidden
24365 service authorities still accept and serve version 0 descriptors
24366 when contacted by older hidden services/clients.
24367 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
24368 always on; using them is necessary for correct forward-compatible
24370 - Remove support for .noconnect style addresses. Nobody was using
24371 them, and they provided another avenue for detecting Tor users
24372 via application-level web tricks.
24374 o Packaging changes:
24375 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
24376 installer bundles. See
24377 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
24378 for details of what's new in Vidalia 0.2.3.
24379 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
24380 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
24381 configuration file, rather than the old Privoxy.
24382 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
24383 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
24384 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
24385 better compatibility with OS X 10.6, aka Snow Leopard.
24386 - OS X Vidalia Bundle: The multi-package installer is now replaced
24387 by a simple drag and drop to the /Applications folder. This change
24388 occurred with the upgrade to Vidalia 0.2.3.
24391 Changes in version 0.2.1.19 - 2009-07-28
24392 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
24393 services on Tor 0.2.1.3-alpha through 0.2.1.18.
24396 - Make accessing hidden services on 0.2.1.x work right again.
24397 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
24398 part of patch provided by "optimist".
24401 - When a relay/bridge is writing out its identity key fingerprint to
24402 the "fingerprint" file and to its logs, write it without spaces. Now
24403 it will look like the fingerprints in our bridges documentation,
24404 and confuse fewer users.
24407 - Relays no longer publish a new server descriptor if they change
24408 their MaxAdvertisedBandwidth config option but it doesn't end up
24409 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
24410 fixes bug 1026. Patch from Sebastian.
24411 - Avoid leaking memory every time we get a create cell but we have
24412 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
24413 fixes bug 1034. Reported by BarkerJr.
24416 Changes in version 0.2.1.18 - 2009-07-24
24417 Tor 0.2.1.18 lays the foundations for performance improvements,
24418 adds status events to help users diagnose bootstrap problems, adds
24419 optional authentication/authorization for hidden services, fixes a
24420 variety of potential anonymity problems, and includes a huge pile of
24421 other features and bug fixes.
24424 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
24427 Changes in version 0.2.1.17-rc - 2009-07-07
24428 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
24429 candidate for the 0.2.1.x series. It lays the groundwork for further
24430 client performance improvements, and also fixes a big bug with directory
24431 authorities that were causing them to assign Guard and Stable flags
24434 The Windows bundles also finally include the geoip database that we
24435 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
24436 should actually install Torbutton rather than giving you a cryptic
24437 failure message (oops).
24440 - Clients now use the bandwidth values in the consensus, rather than
24441 the bandwidth values in each relay descriptor. This approach opens
24442 the door to more accurate bandwidth estimates once the directory
24443 authorities start doing active measurements. Implements more of
24447 - When Tor clients restart after 1-5 days, they discard all their
24448 cached descriptors as too old, but they still use the cached
24449 consensus document. This approach is good for robustness, but
24450 bad for performance: since they don't know any bandwidths, they
24451 end up choosing at random rather than weighting their choice by
24452 speed. Fixed by the above feature of putting bandwidths in the
24453 consensus. Bugfix on 0.2.0.x.
24454 - Directory authorities were neglecting to mark relays down in their
24455 internal histories if the relays fall off the routerlist without
24456 ever being found unreachable. So there were relays in the histories
24457 that haven't been seen for eight months, and are listed as being
24458 up for eight months. This wreaked havoc on the "median wfu"
24459 and "median mtbf" calculations, in turn making Guard and Stable
24460 flags very wrong, hurting network performance. Fixes bugs 696 and
24461 969. Bugfix on 0.2.0.6-alpha.
24464 - Serve the DirPortFrontPage page even when we have been approaching
24465 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
24466 - The control port would close the connection before flushing long
24467 replies, such as the network consensus, if a QUIT command was issued
24468 before the reply had completed. Now, the control port flushes all
24469 pending replies before closing the connection. Also fixed a spurious
24470 warning when a QUIT command is issued after a malformed or rejected
24471 AUTHENTICATE command, but before the connection was closed. Patch
24472 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
24473 - When we can't find an intro key for a v2 hidden service descriptor,
24474 fall back to the v0 hidden service descriptor and log a bug message.
24475 Workaround for bug 1024.
24476 - Fix a log message that did not respect the SafeLogging option.
24480 - If we're a relay and we change our IP address, be more verbose
24481 about the reason that made us change. Should help track down
24482 further bugs for relays on dynamic IP addresses.
24485 Changes in version 0.2.0.35 - 2009-06-24
24487 - Avoid crashing in the presence of certain malformed descriptors.
24488 Found by lark, and by automated fuzzing.
24489 - Fix an edge case where a malicious exit relay could convince a
24490 controller that the client's DNS question resolves to an internal IP
24491 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24494 - Finally fix the bug where dynamic-IP relays disappear when their
24495 IP address changes: directory mirrors were mistakenly telling
24496 them their old address if they asked via begin_dir, so they
24497 never got an accurate answer about their new address, so they
24498 just vanished after a day. For belt-and-suspenders, relays that
24499 don't set Address in their config now avoid using begin_dir for
24500 all direct connections. Should fix bugs 827, 883, and 900.
24501 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24502 that would occur on some exit nodes when DNS failures and timeouts
24503 occurred in certain patterns. Fix for bug 957.
24506 - When starting with a cache over a few days old, do not leak
24507 memory for the obsolete router descriptors in it. Bugfix on
24508 0.2.0.33; fixes bug 672.
24509 - Hidden service clients didn't use a cached service descriptor that
24510 was older than 15 minutes, but wouldn't fetch a new one either,
24511 because there was already one in the cache. Now, fetch a v2
24512 descriptor unless the same descriptor was added to the cache within
24513 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24516 Changes in version 0.2.1.16-rc - 2009-06-20
24517 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
24518 a bunch of minor bugs.
24521 - Fix an edge case where a malicious exit relay could convince a
24522 controller that the client's DNS question resolves to an internal IP
24523 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24525 o Major performance improvements (on 0.2.0.x):
24526 - Disable and refactor some debugging checks that forced a linear scan
24527 over the whole server-side DNS cache. These accounted for over 50%
24528 of CPU time on a relatively busy exit node's gprof profile. Found
24530 - Disable some debugging checks that appeared in exit node profile
24534 - Update to the "June 3 2009" ip-to-country file.
24535 - Do not have tor-resolve automatically refuse all .onion addresses;
24536 if AutomapHostsOnResolve is set in your torrc, this will work fine.
24538 o Minor bugfixes (on 0.2.0.x):
24539 - Log correct error messages for DNS-related network errors on
24541 - Fix a race condition that could cause crashes or memory corruption
24542 when running as a server with a controller listening for log
24544 - Avoid crashing when we have a policy specified in a DirPolicy or
24545 SocksPolicy or ReachableAddresses option with ports set on it,
24546 and we re-load the policy. May fix bug 996.
24547 - Hidden service clients didn't use a cached service descriptor that
24548 was older than 15 minutes, but wouldn't fetch a new one either,
24549 because there was already one in the cache. Now, fetch a v2
24550 descriptor unless the same descriptor was added to the cache within
24551 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24553 o Minor bugfixes (on 0.2.1.x):
24554 - Don't warn users about low port and hibernation mix when they
24555 provide a *ListenAddress directive to fix that. Bugfix on
24557 - When switching back and forth between bridge mode, do not start
24558 gathering GeoIP data until two hours have passed.
24559 - Do not complain that the user has requested an excluded node as
24560 an exit when the node is not really an exit. This could happen
24561 because the circuit was for testing, or an introduction point.
24565 Changes in version 0.2.1.15-rc - 2009-05-25
24566 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
24567 series. It fixes a major bug on fast exit relays, as well as a variety
24568 of more minor bugs.
24570 o Major bugfixes (on 0.2.0.x):
24571 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24572 that would occur on some exit nodes when DNS failures and timeouts
24573 occurred in certain patterns. Fix for bug 957.
24575 o Minor bugfixes (on 0.2.0.x):
24576 - Actually return -1 in the error case for read_bandwidth_usage().
24577 Harmless bug, since we currently don't care about the return value
24578 anywhere. Bugfix on 0.2.0.9-alpha.
24579 - Provide a more useful log message if bug 977 (related to buffer
24580 freelists) ever reappears, and do not crash right away.
24581 - Fix an assertion failure on 64-bit platforms when we allocated
24582 memory right up to the end of a memarea, then realigned the memory
24583 one step beyond the end. Fixes a possible cause of bug 930.
24584 - Protect the count of open sockets with a mutex, so we can't
24585 corrupt it when two threads are closing or opening sockets at once.
24586 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
24587 - Don't allow a bridge to publish its router descriptor to a
24588 non-bridge directory authority. Fixes part of bug 932.
24589 - When we change to or from being a bridge, reset our counts of
24590 client usage by country. Fixes bug 932.
24591 - Fix a bug that made stream bandwidth get misreported to the
24593 - Stop using malloc_usable_size() to use more area than we had
24594 actually allocated: it was safe, but made valgrind really unhappy.
24595 - Fix a memory leak when v3 directory authorities load their keys
24596 and cert from disk. Bugfix on 0.2.0.1-alpha.
24598 o Minor bugfixes (on 0.2.1.x):
24599 - Fix use of freed memory when deciding to mark a non-addable
24600 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
24603 Changes in version 0.2.1.14-rc - 2009-04-12
24604 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
24605 series. It begins fixing some major performance problems, and also
24606 finally addresses the bug that was causing relays on dynamic IP
24607 addresses to fall out of the directory.
24610 - Clients replace entry guards that were chosen more than a few months
24611 ago. This change should significantly improve client performance,
24612 especially once more people upgrade, since relays that have been
24613 a guard for a long time are currently overloaded.
24615 o Major bugfixes (on 0.2.0):
24616 - Finally fix the bug where dynamic-IP relays disappear when their
24617 IP address changes: directory mirrors were mistakenly telling
24618 them their old address if they asked via begin_dir, so they
24619 never got an accurate answer about their new address, so they
24620 just vanished after a day. For belt-and-suspenders, relays that
24621 don't set Address in their config now avoid using begin_dir for
24622 all direct connections. Should fix bugs 827, 883, and 900.
24623 - Relays were falling out of the networkstatus consensus for
24624 part of a day if they changed their local config but the
24625 authorities discarded their new descriptor as "not sufficiently
24626 different". Now directory authorities accept a descriptor as changed
24627 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
24628 patch by Sebastian.
24629 - Avoid crashing in the presence of certain malformed descriptors.
24630 Found by lark, and by automated fuzzing.
24633 - When generating circuit events with verbose nicknames for
24634 controllers, try harder to look up nicknames for routers on a
24635 circuit. (Previously, we would look in the router descriptors we had
24636 for nicknames, but not in the consensus.) Partial fix for bug 941.
24637 - If the bridge config line doesn't specify a port, assume 443.
24638 This makes bridge lines a bit smaller and easier for users to
24640 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
24641 bytes (aka 20KB/s), to match our documentation. Also update
24642 directory authorities so they always assign the Fast flag to relays
24643 with 20KB/s of capacity. Now people running relays won't suddenly
24644 find themselves not seeing any use, if the network gets faster
24646 - Update to the "April 3 2009" ip-to-country file.
24649 - Avoid trying to print raw memory to the logs when we decide to
24650 give up on downloading a given relay descriptor. Bugfix on
24652 - In tor-resolve, when the Tor client to use is specified by
24653 <hostname>:<port>, actually use the specified port rather than
24654 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
24655 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
24656 - When starting with a cache over a few days old, do not leak
24657 memory for the obsolete router descriptors in it. Bugfix on
24659 - Avoid double-free on list of successfully uploaded hidden
24660 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
24661 - Change memarea_strndup() implementation to work even when
24662 duplicating a string at the end of a page. This bug was
24663 harmless for now, but could have meant crashes later. Fix by
24664 lark. Bugfix on 0.2.1.1-alpha.
24665 - Limit uploaded directory documents to be 16M rather than 500K.
24666 The directory authorities were refusing v3 consensus votes from
24667 other authorities, since the votes are now 504K. Fixes bug 959;
24668 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
24669 - Directory authorities should never send a 503 "busy" response to
24670 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
24674 Changes in version 0.2.1.13-alpha - 2009-03-09
24675 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
24676 cleanups. We're finally getting close to a release candidate.
24679 - Correctly update the list of which countries we exclude as
24680 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
24681 lark. Bugfix on 0.2.1.6-alpha.
24683 o Minor bugfixes (on 0.2.0.x and earlier):
24684 - Automatically detect MacOSX versions earlier than 10.4.0, and
24685 disable kqueue from inside Tor when running with these versions.
24686 We previously did this from the startup script, but that was no
24687 help to people who didn't use the startup script. Resolves bug 863.
24688 - When we had picked an exit node for a connection, but marked it as
24689 "optional", and it turned out we had no onion key for the exit,
24690 stop wanting that exit and try again. This situation may not
24691 be possible now, but will probably become feasible with proposal
24692 158. Spotted by rovv. Fixes another case of bug 752.
24693 - Clients no longer cache certificates for authorities they do not
24694 recognize. Bugfix on 0.2.0.9-alpha.
24695 - When we can't transmit a DNS request due to a network error, retry
24696 it after a while, and eventually transmit a failing response to
24697 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
24698 - If the controller claimed responsibility for a stream, but that
24699 stream never finished making its connection, it would live
24700 forever in circuit_wait state. Now we close it after SocksTimeout
24701 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
24702 - Drop begin cells to a hidden service if they come from the middle
24703 of a circuit. Patch from lark.
24704 - When we erroneously receive two EXTEND cells for the same circuit
24705 ID on the same connection, drop the second. Patch from lark.
24706 - Fix a crash that occurs on exit nodes when a nameserver request
24707 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
24708 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
24710 - Do not assume that a stack-allocated character array will be
24711 64-bit aligned on platforms that demand that uint64_t access is
24712 aligned. Possible fix for bug 604.
24713 - Parse dates and IPv4 addresses in a locale- and libc-independent
24714 manner, to avoid platform-dependent behavior on malformed input.
24715 - Build correctly when configured to build outside the main source
24716 path. Patch from Michael Gold.
24717 - We were already rejecting relay begin cells with destination port
24718 of 0. Now also reject extend cells with destination port or address
24719 of 0. Suggested by lark.
24721 o Minor bugfixes (on 0.2.1.x):
24722 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
24723 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
24724 - If we're an exit node, scrub the IP address to which we are exiting
24725 in the logs. Bugfix on 0.2.1.8-alpha.
24728 - On Linux, use the prctl call to re-enable core dumps when the user
24730 - New controller event NEWCONSENSUS that lists the networkstatus
24731 lines for every recommended relay. Now controllers like Torflow
24732 can keep up-to-date on which relays they should be using.
24733 - Update to the "February 26 2009" ip-to-country file.
24736 Changes in version 0.2.0.34 - 2009-02-08
24737 Tor 0.2.0.34 features several more security-related fixes. You should
24738 upgrade, especially if you run an exit relay (remote crash) or a
24739 directory authority (remote infinite loop), or you're on an older
24740 (pre-XP) or not-recently-patched Windows (remote exploit).
24742 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
24743 have many known flaws, and nobody should be using them. You should
24744 upgrade. If you're using a Linux or BSD and its packages are obsolete,
24745 stop using those packages and upgrade anyway.
24748 - Fix an infinite-loop bug on handling corrupt votes under certain
24749 circumstances. Bugfix on 0.2.0.8-alpha.
24750 - Fix a temporary DoS vulnerability that could be performed by
24751 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24752 - Avoid a potential crash on exit nodes when processing malformed
24753 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
24754 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24755 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24758 - Fix compilation on systems where time_t is a 64-bit integer.
24759 Patch from Matthias Drochner.
24760 - Don't consider expiring already-closed client connections. Fixes
24761 bug 893. Bugfix on 0.0.2pre20.
24764 Changes in version 0.2.1.12-alpha - 2009-02-08
24765 Tor 0.2.1.12-alpha features several more security-related fixes. You
24766 should upgrade, especially if you run an exit relay (remote crash) or
24767 a directory authority (remote infinite loop), or you're on an older
24768 (pre-XP) or not-recently-patched Windows (remote exploit). It also
24769 includes a big pile of minor bugfixes and cleanups.
24772 - Fix an infinite-loop bug on handling corrupt votes under certain
24773 circumstances. Bugfix on 0.2.0.8-alpha.
24774 - Fix a temporary DoS vulnerability that could be performed by
24775 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24776 - Avoid a potential crash on exit nodes when processing malformed
24777 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
24780 - Let controllers actually ask for the "clients_seen" event for
24781 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
24782 reported by Matt Edman.
24783 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
24785 - Fix a bug in address parsing that was preventing bridges or hidden
24786 service targets from being at IPv6 addresses.
24787 - Solve a bug that kept hardware crypto acceleration from getting
24788 enabled when accounting was turned on. Fixes bug 907. Bugfix on
24790 - Remove a bash-ism from configure.in to build properly on non-Linux
24791 platforms. Bugfix on 0.2.1.1-alpha.
24792 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
24793 headers. Bugfix on 0.2.0.10-alpha.
24794 - Don't consider expiring already-closed client connections. Fixes
24795 bug 893. Bugfix on 0.0.2pre20.
24796 - Fix another interesting corner-case of bug 891 spotted by rovv:
24797 Previously, if two hosts had different amounts of clock drift, and
24798 one of them created a new connection with just the wrong timing,
24799 the other might decide to deprecate the new connection erroneously.
24800 Bugfix on 0.1.1.13-alpha.
24801 - Resolve a very rare crash bug that could occur when the user forced
24802 a nameserver reconfiguration during the middle of a nameserver
24803 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
24804 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
24805 Bugfix on 0.2.1.7-alpha.
24806 - If we're using bridges and our network goes away, be more willing
24807 to forgive our bridges and try again when we get an application
24808 request. Bugfix on 0.2.0.x.
24811 - Support platforms where time_t is 64 bits long. (Congratulations,
24812 NetBSD!) Patch from Matthias Drochner.
24813 - Add a 'getinfo status/clients-seen' controller command, in case
24814 controllers want to hear clients_seen events but connect late.
24817 - Disable GCC's strict alias optimization by default, to avoid the
24818 likelihood of its introducing subtle bugs whenever our code violates
24819 the letter of C99's alias rules.
24822 Changes in version 0.2.0.33 - 2009-01-21
24823 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
24824 useful to users. It also finally fixes a bug where a relay or client
24825 that's been off for many days would take a long time to bootstrap.
24827 This update also fixes an important security-related bug reported by
24828 Ilja van Sprundel. You should upgrade. (We'll send out more details
24829 about the bug once people have had some time to upgrade.)
24832 - Fix a heap-corruption bug that may be remotely triggerable on
24833 some platforms. Reported by Ilja van Sprundel.
24836 - When a stream at an exit relay is in state "resolving" or
24837 "connecting" and it receives an "end" relay cell, the exit relay
24838 would silently ignore the end cell and not close the stream. If
24839 the client never closes the circuit, then the exit relay never
24840 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
24841 reported by "wood".
24842 - When sending CREATED cells back for a given circuit, use a 64-bit
24843 connection ID to find the right connection, rather than an addr:port
24844 combination. Now that we can have multiple OR connections between
24845 the same ORs, it is no longer possible to use addr:port to uniquely
24846 identify a connection.
24847 - Bridge relays that had DirPort set to 0 would stop fetching
24848 descriptors shortly after startup, and then briefly resume
24849 after a new bandwidth test and/or after publishing a new bridge
24850 descriptor. Bridge users that try to bootstrap from them would
24851 get a recent networkstatus but would get descriptors from up to
24852 18 hours earlier, meaning most of the descriptors were obsolete
24853 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24854 - Prevent bridge relays from serving their 'extrainfo' document
24855 to anybody who asks, now that extrainfo docs include potentially
24856 sensitive aggregated client geoip summaries. Bugfix on
24858 - If the cached networkstatus consensus is more than five days old,
24859 discard it rather than trying to use it. In theory it could be
24860 useful because it lists alternate directory mirrors, but in practice
24861 it just means we spend many minutes trying directory mirrors that
24862 are long gone from the network. Also discard router descriptors as
24863 we load them if they are more than five days old, since the onion
24864 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
24867 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24868 could make gcc generate non-functional binary search code. Bugfix
24870 - Build correctly on platforms without socklen_t.
24871 - Compile without warnings on solaris.
24872 - Avoid potential crash on internal error during signature collection.
24873 Fixes bug 864. Patch from rovv.
24874 - Correct handling of possible malformed authority signing key
24875 certificates with internal signature types. Fixes bug 880.
24876 Bugfix on 0.2.0.3-alpha.
24877 - Fix a hard-to-trigger resource leak when logging credential status.
24879 - When we can't initialize DNS because the network is down, do not
24880 automatically stop Tor from starting. Instead, we retry failed
24881 dns_init() every 10 minutes, and change the exit policy to reject
24882 *:* until one succeeds. Fixes bug 691.
24883 - Use 64 bits instead of 32 bits for connection identifiers used with
24884 the controller protocol, to greatly reduce risk of identifier reuse.
24885 - When we're choosing an exit node for a circuit, and we have
24886 no pending streams, choose a good general exit rather than one that
24887 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
24888 - Fix another case of assuming, when a specific exit is requested,
24889 that we know more than the user about what hosts it allows.
24890 Fixes one case of bug 752. Patch from rovv.
24891 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24892 seconds. Warn the user if lower values are given in the
24893 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24894 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24895 user if lower values are given in the configuration. Bugfix on
24896 0.1.1.17-rc. Patch by Sebastian.
24897 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
24898 the cache because we already had a v0 descriptor with the same ID.
24899 Bugfix on 0.2.0.18-alpha.
24900 - Fix a race condition when freeing keys shared between main thread
24901 and CPU workers that could result in a memory leak. Bugfix on
24902 0.1.0.1-rc. Fixes bug 889.
24903 - Send a valid END cell back when a client tries to connect to a
24904 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
24905 840. Patch from rovv.
24906 - Check which hops rendezvous stream cells are associated with to
24907 prevent possible guess-the-streamid injection attacks from
24908 intermediate hops. Fixes another case of bug 446. Based on patch
24910 - If a broken client asks a non-exit router to connect somewhere,
24911 do not even do the DNS lookup before rejecting the connection.
24912 Fixes another case of bug 619. Patch from rovv.
24913 - When a relay gets a create cell it can't decrypt (e.g. because it's
24914 using the wrong onion key), we were dropping it and letting the
24915 client time out. Now actually answer with a destroy cell. Fixes
24916 bug 904. Bugfix on 0.0.2pre8.
24918 o Minor bugfixes (hidden services):
24919 - Do not throw away existing introduction points on SIGHUP. Bugfix on
24920 0.0.6pre1. Patch by Karsten. Fixes bug 874.
24923 - Report the case where all signatures in a detached set are rejected
24924 differently than the case where there is an error handling the
24926 - When we realize that another process has modified our cached
24927 descriptors, print out a more useful error message rather than
24928 triggering an assertion. Fixes bug 885. Patch from Karsten.
24929 - Implement the 0x20 hack to better resist DNS poisoning: set the
24930 case on outgoing DNS requests randomly, and reject responses that do
24931 not match the case correctly. This logic can be disabled with the
24932 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
24933 of servers that do not reliably preserve case in replies. See
24934 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
24936 - Check DNS replies for more matching fields to better resist DNS
24938 - Never use OpenSSL compression: it wastes RAM and CPU trying to
24939 compress cells, which are basically all encrypted, compressed, or
24943 Changes in version 0.2.1.11-alpha - 2009-01-20
24944 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
24945 week it will take a long time to bootstrap again" bug. It also fixes
24946 an important security-related bug reported by Ilja van Sprundel. You
24947 should upgrade. (We'll send out more details about the bug once people
24948 have had some time to upgrade.)
24951 - Fix a heap-corruption bug that may be remotely triggerable on
24952 some platforms. Reported by Ilja van Sprundel.
24955 - Discard router descriptors as we load them if they are more than
24956 five days old. Otherwise if Tor is off for a long time and then
24957 starts with cached descriptors, it will try to use the onion
24958 keys in those obsolete descriptors when building circuits. Bugfix
24959 on 0.2.0.x. Fixes bug 887.
24962 - Try to make sure that the version of Libevent we're running with
24963 is binary-compatible with the one we built with. May address bug
24965 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
24966 for bug 905. Bugfix on 0.2.1.7-alpha.
24967 - Add a new --enable-local-appdata configuration switch to change
24968 the default location of the datadir on win32 from APPDATA to
24969 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
24970 entirely. Patch from coderman.
24973 - Make outbound DNS packets respect the OutboundBindAddress setting.
24974 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
24975 - When our circuit fails at the first hop (e.g. we get a destroy
24976 cell back), avoid using that OR connection anymore, and also
24977 tell all the one-hop directory requests waiting for it that they
24978 should fail. Bugfix on 0.2.1.3-alpha.
24979 - In the torify(1) manpage, mention that tsocks will leak your
24983 Changes in version 0.2.1.10-alpha - 2009-01-06
24984 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
24985 would make the bridge relay not so useful if it had DirPort set to 0,
24986 and one that could let an attacker learn a little bit of information
24987 about the bridge's users), and a bug that would cause your Tor relay
24988 to ignore a circuit create request it can't decrypt (rather than reply
24989 with an error). It also fixes a wide variety of other bugs.
24992 - If the cached networkstatus consensus is more than five days old,
24993 discard it rather than trying to use it. In theory it could
24994 be useful because it lists alternate directory mirrors, but in
24995 practice it just means we spend many minutes trying directory
24996 mirrors that are long gone from the network. Helps bug 887 a bit;
24998 - Bridge relays that had DirPort set to 0 would stop fetching
24999 descriptors shortly after startup, and then briefly resume
25000 after a new bandwidth test and/or after publishing a new bridge
25001 descriptor. Bridge users that try to bootstrap from them would
25002 get a recent networkstatus but would get descriptors from up to
25003 18 hours earlier, meaning most of the descriptors were obsolete
25004 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
25005 - Prevent bridge relays from serving their 'extrainfo' document
25006 to anybody who asks, now that extrainfo docs include potentially
25007 sensitive aggregated client geoip summaries. Bugfix on
25011 - New controller event "clients_seen" to report a geoip-based summary
25012 of which countries we've seen clients from recently. Now controllers
25013 like Vidalia can show bridge operators that they're actually making
25015 - Build correctly against versions of OpenSSL 0.9.8 or later built
25016 without support for deprecated functions.
25017 - Update to the "December 19 2008" ip-to-country file.
25019 o Minor bugfixes (on 0.2.0.x):
25020 - Authorities now vote for the Stable flag for any router whose
25021 weighted MTBF is at least 5 days, regardless of the mean MTBF.
25022 - Do not remove routers as too old if we do not have any consensus
25023 document. Bugfix on 0.2.0.7-alpha.
25024 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
25025 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
25026 - When an exit relay resolves a stream address to a local IP address,
25027 do not just keep retrying that same exit relay over and
25028 over. Instead, just close the stream. Addresses bug 872. Bugfix
25029 on 0.2.0.32. Patch from rovv.
25030 - If a hidden service sends us an END cell, do not consider
25031 retrying the connection; just close it. Patch from rovv.
25032 - When we made bridge authorities stop serving bridge descriptors over
25033 unencrypted links, we also broke DirPort reachability testing for
25034 bridges. So bridges with a non-zero DirPort were printing spurious
25035 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
25036 - When a relay gets a create cell it can't decrypt (e.g. because it's
25037 using the wrong onion key), we were dropping it and letting the
25038 client time out. Now actually answer with a destroy cell. Fixes
25039 bug 904. Bugfix on 0.0.2pre8.
25040 - Squeeze 2-5% out of client performance (according to oprofile) by
25041 improving the implementation of some policy-manipulation functions.
25043 o Minor bugfixes (on 0.2.1.x):
25044 - Make get_interface_address() function work properly again; stop
25045 guessing the wrong parts of our address as our address.
25046 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
25047 send on that circuit. Otherwise we might violate the proposal-110
25048 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
25050 - When we're sending non-EXTEND cells to the first hop in a circuit,
25051 for example to use an encrypted directory connection, we don't need
25052 to use RELAY_EARLY cells: the first hop knows what kind of cell
25053 it is, and nobody else can even see the cell type. Conserving
25054 RELAY_EARLY cells makes it easier to cannibalize circuits like
25056 - Stop logging nameserver addresses in reverse order.
25057 - If we are retrying a directory download slowly over and over, do
25058 not automatically give up after the 254th failure. Bugfix on
25060 - Resume reporting accurate "stream end" reasons to the local control
25061 port. They were lost in the changes for Proposal 148. Bugfix on
25064 o Deprecated and removed features:
25065 - The old "tor --version --version" command, which would print out
25066 the subversion "Id" of most of the source files, is now removed. It
25067 turned out to be less useful than we'd expected, and harder to
25070 o Code simplifications and refactoring:
25071 - Change our header file guard macros to be less likely to conflict
25072 with system headers. Adam Langley noticed that we were conflicting
25073 with log.h on Android.
25074 - Tool-assisted documentation cleanup. Nearly every function or
25075 static variable in Tor should have its own documentation now.
25078 Changes in version 0.2.1.9-alpha - 2008-12-25
25079 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
25081 o New directory authorities:
25082 - gabelmoo (the authority run by Karsten Loesing) now has a new
25086 - Never use a connection with a mismatched address to extend a
25087 circuit, unless that connection is canonical. A canonical
25088 connection is one whose address is authenticated by the router's
25089 identity key, either in a NETINFO cell or in a router descriptor.
25090 - Avoid a possible memory corruption bug when receiving hidden service
25091 descriptors. Bugfix on 0.2.1.6-alpha.
25094 - Fix a logic error that would automatically reject all but the first
25095 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
25096 part of bug 813/868. Bug spotted by coderman.
25097 - When a stream at an exit relay is in state "resolving" or
25098 "connecting" and it receives an "end" relay cell, the exit relay
25099 would silently ignore the end cell and not close the stream. If
25100 the client never closes the circuit, then the exit relay never
25101 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
25102 reported by "wood".
25103 - When we can't initialize DNS because the network is down, do not
25104 automatically stop Tor from starting. Instead, retry failed
25105 dns_init() every 10 minutes, and change the exit policy to reject
25106 *:* until one succeeds. Fixes bug 691.
25109 - Give a better error message when an overzealous init script says
25110 "sudo -u username tor --user username". Makes Bug 882 easier for
25112 - When a directory authority gives us a new guess for our IP address,
25113 log which authority we used. Hopefully this will help us debug
25114 the recent complaints about bad IP address guesses.
25115 - Detect svn revision properly when we're using git-svn.
25116 - Try not to open more than one descriptor-downloading connection
25117 to an authority at once. This should reduce load on directory
25118 authorities. Fixes bug 366.
25119 - Add cross-certification to newly generated certificates, so that
25120 a signing key is enough information to look up a certificate.
25121 Partial implementation of proposal 157.
25122 - Start serving certificates by <identity digest, signing key digest>
25123 pairs. Partial implementation of proposal 157.
25124 - Clients now never report any stream end reason except 'MISC'.
25125 Implements proposal 148.
25126 - On platforms with a maximum syslog string length, truncate syslog
25127 messages to that length ourselves, rather than relying on the
25128 system to do it for us.
25129 - Optimize out calls to time(NULL) that occur for every IO operation,
25130 or for every cell. On systems where time() is a slow syscall,
25131 this fix will be slightly helpful.
25132 - Exit servers can now answer resolve requests for ip6.arpa addresses.
25133 - When we download a descriptor that we then immediately (as
25134 a directory authority) reject, do not retry downloading it right
25135 away. Should save some bandwidth on authorities. Fix for bug
25136 888. Patch by Sebastian Hahn.
25137 - When a download gets us zero good descriptors, do not notify
25138 Tor that new directory information has arrived.
25139 - Avoid some nasty corner cases in the logic for marking connections
25140 as too old or obsolete or noncanonical for circuits. Partial
25143 o Minor features (controller):
25144 - New CONSENSUS_ARRIVED event to note when a new consensus has
25145 been fetched and validated.
25146 - When we realize that another process has modified our cached
25147 descriptors file, print out a more useful error message rather
25148 than triggering an assertion. Fixes bug 885. Patch from Karsten.
25149 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
25150 controllers to prevent SIGHUP from reloading the
25151 configuration. Fixes bug 856.
25154 - Resume using the correct "REASON=" stream when telling the
25155 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
25156 - When a canonical connection appears later in our internal list
25157 than a noncanonical one for a given OR ID, always use the
25158 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
25160 - Clip the MaxCircuitDirtiness config option to a minimum of 10
25161 seconds. Warn the user if lower values are given in the
25162 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
25163 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
25164 user if lower values are given in the configuration. Bugfix on
25165 0.1.1.17-rc. Patch by Sebastian.
25166 - Fix a race condition when freeing keys shared between main thread
25167 and CPU workers that could result in a memory leak. Bugfix on
25168 0.1.0.1-rc. Fixes bug 889.
25170 o Minor bugfixes (hidden services):
25171 - Do not throw away existing introduction points on SIGHUP (bugfix on
25172 0.0.6pre1); also, do not stall hidden services because we're
25173 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
25174 by John Brooks. Patch by Karsten. Fixes bug 874.
25175 - Fix a memory leak when we decline to add a v2 rendezvous
25176 descriptor to the cache because we already had a v0 descriptor
25177 with the same ID. Bugfix on 0.2.0.18-alpha.
25179 o Deprecated and removed features:
25180 - RedirectExits has been removed. It was deprecated since
25182 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
25183 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
25184 - Cell pools are now always enabled; --disable-cell-pools is ignored.
25186 o Code simplifications and refactoring:
25187 - Rename the confusing or_is_obsolete field to the more appropriate
25188 is_bad_for_new_circs, and move it to or_connection_t where it
25190 - Move edge-only flags from connection_t to edge_connection_t: not
25191 only is this better coding, but on machines of plausible alignment,
25192 it should save 4-8 bytes per connection_t. "Every little bit helps."
25193 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
25194 for consistency; keep old option working for backward compatibility.
25195 - Simplify the code for finding connections to use for a circuit.
25198 Changes in version 0.2.1.8-alpha - 2008-12-08
25199 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
25200 builds better on unusual platforms like Solaris and old OS X, and
25201 fixes a variety of other issues.
25204 - New DirPortFrontPage option that takes an html file and publishes
25205 it as "/" on the DirPort. Now relay operators can provide a
25206 disclaimer without needing to set up a separate webserver. There's
25207 a sample disclaimer in contrib/tor-exit-notice.html.
25210 - When the client is choosing entry guards, now it selects at most
25211 one guard from a given relay family. Otherwise we could end up with
25212 all of our entry points into the network run by the same operator.
25213 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
25216 - Fix a DOS opportunity during the voting signature collection process
25217 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25218 - Fix a possible segfault when establishing an exit connection. Bugfix
25222 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
25224 - Made Tor a little less aggressive about deleting expired
25225 certificates. Partial fix for bug 854.
25226 - Stop doing unaligned memory access that generated bus errors on
25227 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
25228 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
25229 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
25230 - Make USR2 log-level switch take effect immediately. Bugfix on
25232 - If one win32 nameserver fails to get added, continue adding the
25233 rest, and don't automatically fail.
25234 - Use fcntl() for locking when flock() is not available. Should fix
25235 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
25236 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
25237 could make gcc generate non-functional binary search code. Bugfix
25239 - Build correctly on platforms without socklen_t.
25240 - Avoid potential crash on internal error during signature collection.
25241 Fixes bug 864. Patch from rovv.
25242 - Do not use C's stdio library for writing to log files. This will
25243 improve logging performance by a minute amount, and will stop
25244 leaking fds when our disk is full. Fixes bug 861.
25245 - Stop erroneous use of O_APPEND in cases where we did not in fact
25246 want to re-seek to the end of a file before every last write().
25247 - Correct handling of possible malformed authority signing key
25248 certificates with internal signature types. Fixes bug 880. Bugfix
25250 - Fix a hard-to-trigger resource leak when logging credential status.
25254 - Directory mirrors no longer fetch the v1 directory or
25255 running-routers files. They are obsolete, and nobody asks for them
25256 anymore. This is the first step to making v1 authorities obsolete.
25258 o Minor features (controller):
25259 - Return circuit purposes in response to GETINFO circuit-status. Fixes
25263 Changes in version 0.2.0.32 - 2008-11-20
25264 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
25265 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25266 a smaller security flaw that might allow an attacker to access local
25267 services, further improves hidden service performance, and fixes a
25268 variety of other issues.
25271 - The "User" and "Group" config options did not clear the
25272 supplementary group entries for the Tor process. The "User" option
25273 is now more robust, and we now set the groups to the specified
25274 user's primary group. The "Group" option is now ignored. For more
25275 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25276 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25277 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
25278 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25279 consistently obeyed: if an exit relay refuses a stream because its
25280 exit policy doesn't allow it, we would remember what IP address
25281 the relay said the destination address resolves to, even if it's
25282 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25285 - Fix a DOS opportunity during the voting signature collection process
25286 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25288 o Major bugfixes (hidden services):
25289 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25290 we were failing the whole hidden service request when the v0
25291 descriptor fetch fails, even if the v2 fetch is still pending and
25292 might succeed. Similarly, if the last v2 fetch fails, we were
25293 failing the whole hidden service request even if a v0 fetch is
25294 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25295 - When extending a circuit to a hidden service directory to upload a
25296 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25297 requests failed, because the router descriptor has not been
25298 downloaded yet. In these cases, do not attempt to upload the
25299 rendezvous descriptor, but wait until the router descriptor is
25300 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
25301 descriptor from a hidden service directory for which the router
25302 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
25306 - Fix several infrequent memory leaks spotted by Coverity.
25307 - When testing for libevent functions, set the LDFLAGS variable
25308 correctly. Found by Riastradh.
25309 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25310 bootstrapping with tunneled directory connections. Bugfix on
25311 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25312 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25313 and we know that server B rejects most-but-not all connections to
25314 port 80, we would previously reject the connection. Now, we assume
25315 the user knows what they were asking for. Fixes bug 752. Bugfix
25316 on 0.0.9rc5. Diagnosed by BarkerJr.
25317 - If we overrun our per-second write limits a little, count this as
25318 having used up our write allocation for the second, and choke
25319 outgoing directory writes. Previously, we had only counted this when
25320 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
25321 Bugfix on 0.2.0.x (??).
25322 - Remove the old v2 directory authority 'lefkada' from the default
25323 list. It has been gone for many months.
25324 - Stop doing unaligned memory access that generated bus errors on
25325 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
25326 - Make USR2 log-level switch take effect immediately. Bugfix on
25329 o Minor bugfixes (controller):
25330 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
25331 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
25334 Changes in version 0.2.1.7-alpha - 2008-11-08
25335 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
25336 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25337 a smaller security flaw that might allow an attacker to access local
25338 services, adds better defense against DNS poisoning attacks on exit
25339 relays, further improves hidden service performance, and fixes a
25340 variety of other issues.
25343 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25344 consistently obeyed: if an exit relay refuses a stream because its
25345 exit policy doesn't allow it, we would remember what IP address
25346 the relay said the destination address resolves to, even if it's
25347 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25348 - The "User" and "Group" config options did not clear the
25349 supplementary group entries for the Tor process. The "User" option
25350 is now more robust, and we now set the groups to the specified
25351 user's primary group. The "Group" option is now ignored. For more
25352 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25353 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25354 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
25355 - Do not use or believe expired v3 authority certificates. Patch
25356 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
25359 - Now NodeFamily and MyFamily config options allow spaces in
25360 identity fingerprints, so it's easier to paste them in.
25361 Suggested by Lucky Green.
25362 - Implement the 0x20 hack to better resist DNS poisoning: set the
25363 case on outgoing DNS requests randomly, and reject responses that do
25364 not match the case correctly. This logic can be disabled with the
25365 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
25366 of servers that do not reliably preserve case in replies. See
25367 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
25369 - Preserve case in replies to DNSPort requests in order to support
25370 the 0x20 hack for resisting DNS poisoning attacks.
25372 o Hidden service performance improvements:
25373 - When the client launches an introduction circuit, retry with a
25374 new circuit after 30 seconds rather than 60 seconds.
25375 - Launch a second client-side introduction circuit in parallel
25376 after a delay of 15 seconds (based on work by Christian Wilms).
25377 - Hidden services start out building five intro circuits rather
25378 than three, and when the first three finish they publish a service
25379 descriptor using those. Now we publish our service descriptor much
25380 faster after restart.
25383 - Minor fix in the warning messages when you're having problems
25384 bootstrapping; also, be more forgiving of bootstrap problems when
25385 we're still making incremental progress on a given bootstrap phase.
25386 - When we're choosing an exit node for a circuit, and we have
25387 no pending streams, choose a good general exit rather than one that
25388 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
25389 - Send a valid END cell back when a client tries to connect to a
25390 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
25391 840. Patch from rovv.
25392 - If a broken client asks a non-exit router to connect somewhere,
25393 do not even do the DNS lookup before rejecting the connection.
25394 Fixes another case of bug 619. Patch from rovv.
25395 - Fix another case of assuming, when a specific exit is requested,
25396 that we know more than the user about what hosts it allows.
25397 Fixes another case of bug 752. Patch from rovv.
25398 - Check which hops rendezvous stream cells are associated with to
25399 prevent possible guess-the-streamid injection attacks from
25400 intermediate hops. Fixes another case of bug 446. Based on patch
25402 - Avoid using a negative right-shift when comparing 32-bit
25403 addresses. Possible fix for bug 845 and bug 811.
25404 - Make the assert_circuit_ok() function work correctly on circuits that
25405 have already been marked for close.
25406 - Fix read-off-the-end-of-string error in unit tests when decoding
25407 introduction points.
25408 - Fix uninitialized size field for memory area allocation: may improve
25409 memory performance during directory parsing.
25410 - Treat duplicate certificate fetches as failures, so that we do
25411 not try to re-fetch an expired certificate over and over and over.
25412 - Do not say we're fetching a certificate when we'll in fact skip it
25413 because of a pending download.
25416 Changes in version 0.2.1.6-alpha - 2008-09-30
25417 Tor 0.2.1.6-alpha further improves performance and robustness of
25418 hidden services, starts work on supporting per-country relay selection,
25419 and fixes a variety of smaller issues.
25422 - Implement proposal 121: make it possible to build hidden services
25423 that only certain clients are allowed to connect to. This is
25424 enforced at several points, so that unauthorized clients are unable
25425 to send INTRODUCE cells to the service, or even (depending on the
25426 type of authentication) to learn introduction points. This feature
25427 raises the bar for certain kinds of active attacks against hidden
25428 services. Code by Karsten Loesing.
25429 - Relays now store and serve v2 hidden service descriptors by default,
25430 i.e., the new default value for HidServDirectoryV2 is 1. This is
25431 the last step in proposal 114, which aims to make hidden service
25432 lookups more reliable.
25433 - Start work to allow node restrictions to include country codes. The
25434 syntax to exclude nodes in a country with country code XX is
25435 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
25436 refinement to decide what config options should take priority if
25437 you ask to both use a particular node and exclude it.
25438 - Allow ExitNodes list to include IP ranges and country codes, just
25439 like the Exclude*Nodes lists. Patch from Robert Hogan.
25442 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
25443 Tor to fail to start if you had it configured to use a bridge
25444 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
25445 - When extending a circuit to a hidden service directory to upload a
25446 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25447 requests failed, because the router descriptor had not been
25448 downloaded yet. In these cases, we now wait until the router
25449 descriptor is downloaded, and then retry. Likewise, clients
25450 now skip over a hidden service directory if they don't yet have
25451 its router descriptor, rather than futilely requesting it and
25452 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
25454 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25455 we were failing the whole hidden service request when the v0
25456 descriptor fetch fails, even if the v2 fetch is still pending and
25457 might succeed. Similarly, if the last v2 fetch fails, we were
25458 failing the whole hidden service request even if a v0 fetch is
25459 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25460 - DNS replies need to have names matching their requests, but
25461 these names should be in the questions section, not necessarily
25462 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
25465 - Update to the "September 1 2008" ip-to-country file.
25466 - Allow ports 465 and 587 in the default exit policy again. We had
25467 rejected them in 0.1.0.15, because back in 2005 they were commonly
25468 misconfigured and ended up as spam targets. We hear they are better
25469 locked down these days.
25470 - Use a lockfile to make sure that two Tor processes are not
25471 simultaneously running with the same datadir.
25472 - Serve the latest v3 networkstatus consensus via the control
25473 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
25474 - Better logging about stability/reliability calculations on directory
25476 - Drop the requirement to have an open dir port for storing and
25477 serving v2 hidden service descriptors.
25478 - Directory authorities now serve a /tor/dbg-stability.txt URL to
25479 help debug WFU and MTBF calculations.
25480 - Implement most of Proposal 152: allow specialized servers to permit
25481 single-hop circuits, and clients to use those servers to build
25482 single-hop circuits when using a specialized controller. Patch
25483 from Josh Albrecht. Resolves feature request 768.
25484 - Add a -p option to tor-resolve for specifying the SOCKS port: some
25485 people find host:port too confusing.
25486 - Make TrackHostExit mappings expire a while after their last use, not
25487 after their creation. Patch from Robert Hogan.
25488 - Provide circuit purposes along with circuit events to the controller.
25491 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
25493 - Fixed some memory leaks -- some quite frequent, some almost
25494 impossible to trigger -- based on results from Coverity.
25495 - When testing for libevent functions, set the LDFLAGS variable
25496 correctly. Found by Riastradh.
25497 - Fix an assertion bug in parsing policy-related options; possible fix
25499 - Catch and report a few more bootstrapping failure cases when Tor
25500 fails to establish a TCP connection. Cleanup on 0.2.1.x.
25501 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25502 bootstrapping with tunneled directory connections. Bugfix on
25503 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25504 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25505 and we know that server B rejects most-but-not all connections to
25506 port 80, we would previously reject the connection. Now, we assume
25507 the user knows what they were asking for. Fixes bug 752. Bugfix
25508 on 0.0.9rc5. Diagnosed by BarkerJr.
25509 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
25510 service directories if they have no advertised dir port. Bugfix
25512 - If we overrun our per-second write limits a little, count this as
25513 having used up our write allocation for the second, and choke
25514 outgoing directory writes. Previously, we had only counted this when
25515 we had met our limits precisely. Fixes bug 824. Patch by rovv.
25516 Bugfix on 0.2.0.x (??).
25517 - Avoid a "0 divided by 0" calculation when calculating router uptime
25518 at directory authorities. Bugfix on 0.2.0.8-alpha.
25519 - Make DNS resolved controller events into "CLOSED", not
25520 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
25522 - Fix a bug where an unreachable relay would establish enough
25523 reachability testing circuits to do a bandwidth test -- if
25524 we already have a connection to the middle hop of the testing
25525 circuit, then it could establish the last hop by using the existing
25526 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
25527 circuits no longer use entry guards in 0.2.1.3-alpha.
25528 - If we have correct permissions on $datadir, we complain to stdout
25529 and fail to start. But dangerous permissions on
25530 $datadir/cached-status/ would cause us to open a log and complain
25531 there. Now complain to stdout and fail to start in both cases. Fixes
25532 bug 820, reported by seeess.
25533 - Remove the old v2 directory authority 'lefkada' from the default
25534 list. It has been gone for many months.
25536 o Code simplifications and refactoring:
25537 - Revise the connection_new functions so that a more typesafe variant
25538 exists. This will work better with Coverity, and let us find any
25539 actual mistakes we're making here.
25540 - Refactor unit testing logic so that dmalloc can be used sensibly
25541 with unit tests to check for memory leaks.
25542 - Move all hidden-service related fields from connection and circuit
25543 structure to substructures: this way they won't eat so much memory.
25546 Changes in version 0.2.0.31 - 2008-09-03
25547 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
25548 a big bug we're seeing where in rare cases traffic from one Tor stream
25549 gets mixed into another stream, and fixes a variety of smaller issues.
25552 - Make sure that two circuits can never exist on the same connection
25553 with the same circuit ID, even if one is marked for close. This
25554 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
25555 - Relays now reject risky extend cells: if the extend cell includes
25556 a digest of all zeroes, or asks to extend back to the relay that
25557 sent the extend cell, tear down the circuit. Ideas suggested
25559 - If not enough of our entry guards are available so we add a new
25560 one, we might use the new one even if it overlapped with the
25561 current circuit's exit relay (or its family). Anonymity bugfix
25562 pointed out by rovv.
25565 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25566 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25567 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25568 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25569 - Pick size of default geoip filename string correctly on windows.
25570 Fixes bug 806. Bugfix on 0.2.0.30.
25571 - Make the autoconf script accept the obsolete --with-ssl-dir
25572 option as an alias for the actually-working --with-openssl-dir
25573 option. Fix the help documentation to recommend --with-openssl-dir.
25574 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25575 - When using the TransPort option on OpenBSD, and using the User
25576 option to change UID and drop privileges, make sure to open
25577 /dev/pf before dropping privileges. Fixes bug 782. Patch from
25578 Christopher Davis. Bugfix on 0.1.2.1-alpha.
25579 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25580 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25581 on the client side when connecting to a hidden service. Bugfix
25582 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25583 - When closing an application-side connection because its circuit is
25584 getting torn down, generate the stream event correctly. Bugfix on
25585 0.1.2.x. Anonymous patch.
25588 Changes in version 0.2.1.5-alpha - 2008-08-31
25589 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
25590 in a lot of the infrastructure for adding authorization to hidden
25591 services, lays the groundwork for having clients read their load
25592 balancing information out of the networkstatus consensus rather than
25593 the individual router descriptors, addresses two potential anonymity
25594 issues, and fixes a variety of smaller issues.
25597 - Convert many internal address representations to optionally hold
25599 - Generate and accept IPv6 addresses in many protocol elements.
25600 - Make resolver code handle nameservers located at ipv6 addresses.
25601 - Begin implementation of proposal 121 ("Client authorization for
25602 hidden services"): configure hidden services with client
25603 authorization, publish descriptors for them, and configure
25604 authorization data for hidden services at clients. The next
25605 step is to actually access hidden services that perform client
25607 - More progress toward proposal 141: Network status consensus
25608 documents and votes now contain bandwidth information for each
25609 router and a summary of that router's exit policy. Eventually this
25610 will be used by clients so that they do not have to download every
25611 known descriptor before building circuits.
25613 o Major bugfixes (on 0.2.0.x and before):
25614 - When sending CREATED cells back for a given circuit, use a 64-bit
25615 connection ID to find the right connection, rather than an addr:port
25616 combination. Now that we can have multiple OR connections between
25617 the same ORs, it is no longer possible to use addr:port to uniquely
25618 identify a connection.
25619 - Relays now reject risky extend cells: if the extend cell includes
25620 a digest of all zeroes, or asks to extend back to the relay that
25621 sent the extend cell, tear down the circuit. Ideas suggested
25623 - If not enough of our entry guards are available so we add a new
25624 one, we might use the new one even if it overlapped with the
25625 current circuit's exit relay (or its family). Anonymity bugfix
25626 pointed out by rovv.
25629 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25630 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25631 - When using the TransPort option on OpenBSD, and using the User
25632 option to change UID and drop privileges, make sure to open /dev/pf
25633 before dropping privileges. Fixes bug 782. Patch from Christopher
25634 Davis. Bugfix on 0.1.2.1-alpha.
25635 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25636 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25637 - Add a missing safe_str() call for a debug log message.
25638 - Use 64 bits instead of 32 bits for connection identifiers used with
25639 the controller protocol, to greatly reduce risk of identifier reuse.
25640 - Make the autoconf script accept the obsolete --with-ssl-dir
25641 option as an alias for the actually-working --with-openssl-dir
25642 option. Fix the help documentation to recommend --with-openssl-dir.
25643 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25646 - Rate-limit too-many-sockets messages: when they happen, they happen
25647 a lot. Resolves bug 748.
25648 - Resist DNS poisoning a little better by making sure that names in
25649 answer sections match.
25650 - Print the SOCKS5 error message string as well as the error code
25651 when a tor-resolve request fails. Patch from Jacob.
25654 Changes in version 0.2.1.4-alpha - 2008-08-04
25655 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
25658 - The address part of exit policies was not correctly written
25659 to router descriptors. This generated router descriptors that failed
25660 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
25662 - Tor triggered a false assert when extending a circuit to a relay
25663 but we already have a connection open to that relay. Noticed by
25664 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
25667 - Fix a hidden service logging bug: in some edge cases, the router
25668 descriptor of a previously picked introduction point becomes
25669 obsolete and we need to give up on it rather than continually
25670 complaining that it has become obsolete. Observed by xiando. Bugfix
25673 o Removed features:
25674 - Take out the TestVia config option, since it was a workaround for
25675 a bug that was fixed in Tor 0.1.1.21.
25678 Changes in version 0.2.1.3-alpha - 2008-08-03
25679 Tor 0.2.1.3-alpha implements most of the pieces to prevent
25680 infinite-length circuit attacks (see proposal 110); fixes a bug that
25681 might cause exit relays to corrupt streams they send back; allows
25682 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
25683 ExcludeExitNodes config options; and fixes a big pile of bugs.
25685 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
25686 - Send a bootstrap problem "warn" event on the first problem if the
25687 reason is NO_ROUTE (that is, our network is down).
25690 - Implement most of proposal 110: The first K cells to be sent
25691 along a circuit are marked as special "early" cells; only K "early"
25692 cells will be allowed. Once this code is universal, we can block
25693 certain kinds of DOS attack by requiring that EXTEND commands must
25694 be sent using an "early" cell.
25697 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25698 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25699 on the client side when connecting to a hidden service. Bugfix
25700 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25701 - Ensure that two circuits can never exist on the same connection
25702 with the same circuit ID, even if one is marked for close. This
25703 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
25706 - When relays do their initial bandwidth measurement, don't limit
25707 to just our entry guards for the test circuits. Otherwise we tend
25708 to have multiple test circuits going through a single entry guard,
25709 which makes our bandwidth test less accurate. Fixes part of bug 654;
25710 patch contributed by Josh Albrecht.
25711 - Add an ExcludeExitNodes option so users can list a set of nodes
25712 that should be be excluded from the exit node position, but
25713 allowed elsewhere. Implements proposal 151.
25714 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
25715 ExcludeNodes and ExcludeExitNodes lists.
25716 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
25717 be more efficient. Formerly it was quadratic in the number of
25718 servers; now it should be linear. Fixes bug 509.
25719 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
25720 and n_conn_id_digest fields into a separate structure that's
25721 only needed when the circuit has not yet attached to an n_conn.
25724 - Change the contrib/tor.logrotate script so it makes the new
25725 logs as "_tor:_tor" rather than the default, which is generally
25726 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
25727 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25728 warnings (occasionally), but it can also cause the compiler to
25729 eliminate error-checking code. Suggested by Peter Gutmann.
25730 - When a hidden service is giving up on an introduction point candidate
25731 that was not included in the last published rendezvous descriptor,
25732 don't reschedule publication of the next descriptor. Fixes bug 763.
25734 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
25735 HiddenServiceExcludeNodes as obsolete: they never worked properly,
25736 and nobody claims to be using them. Fixes bug 754. Bugfix on
25737 0.1.0.1-rc. Patch from Christian Wilms.
25738 - Fix a small alignment and memory-wasting bug on buffer chunks.
25741 o Minor bugfixes (controller):
25742 - When closing an application-side connection because its circuit
25743 is getting torn down, generate the stream event correctly.
25744 Bugfix on 0.1.2.x. Anonymous patch.
25746 o Removed features:
25747 - Remove all backward-compatibility code to support relays running
25748 versions of Tor so old that they no longer work at all on the
25752 Changes in version 0.2.0.30 - 2008-07-15
25754 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25755 warnings (occasionally), but it can also cause the compiler to
25756 eliminate error-checking code. Suggested by Peter Gutmann.
25759 Changes in version 0.2.0.29-rc - 2008-07-08
25760 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
25761 hidden-service performance bugs, and fixes a bunch of smaller bugs.
25764 - If you have more than one bridge but don't know their keys,
25765 you would only launch a request for the descriptor of the first one
25766 on your list. (Tor considered launching requests for the others, but
25767 found that it already had a connection on the way for $0000...0000
25768 so it didn't open another.) Bugfix on 0.2.0.x.
25769 - If you have more than one bridge but don't know their keys, and the
25770 connection to one of the bridges failed, you would cancel all
25771 pending bridge connections. (After all, they all have the same
25772 digest.) Bugfix on 0.2.0.x.
25773 - When a hidden service was trying to establish an introduction point,
25774 and Tor had built circuits preemptively for such purposes, we
25775 were ignoring all the preemptive circuits and launching a new one
25776 instead. Bugfix on 0.2.0.14-alpha.
25777 - When a hidden service was trying to establish an introduction point,
25778 and Tor *did* manage to reuse one of the preemptively built
25779 circuits, it didn't correctly remember which one it used,
25780 so it asked for another one soon after, until there were no
25781 more preemptive circuits, at which point it launched one from
25782 scratch. Bugfix on 0.0.9.x.
25783 - Make directory servers include the X-Your-Address-Is: http header in
25784 their responses even for begin_dir conns. Now clients who only
25785 ever use begin_dir connections still have a way to learn their IP
25786 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
25789 - Fix a macro/CPP interaction that was confusing some compilers:
25790 some GCCs don't like #if/#endif pairs inside macro arguments.
25792 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
25793 Fixes bug 704; fix from Steven Murdoch.
25794 - When opening /dev/null in finish_daemonize(), do not pass the
25795 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
25796 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
25797 - Correctly detect transparent proxy support on Linux hosts that
25798 require in.h to be included before netfilter_ipv4.h. Patch
25800 - Disallow session resumption attempts during the renegotiation
25801 stage of the v2 handshake protocol. Clients should never be trying
25802 session resumption at this point, but apparently some did, in
25803 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
25804 found by Geoff Goodell.
25807 Changes in version 0.2.1.2-alpha - 2008-06-20
25808 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
25809 make it easier to set up your own private Tor network; fixes several
25810 big bugs with using more than one bridge relay; fixes a big bug with
25811 offering hidden services quickly after Tor starts; and uses a better
25812 API for reporting potential bootstrapping problems to the controller.
25815 - New TestingTorNetwork config option to allow adjustment of
25816 previously constant values that, while reasonable, could slow
25817 bootstrapping. Implements proposal 135. Patch from Karsten.
25820 - If you have more than one bridge but don't know their digests,
25821 you would only learn a request for the descriptor of the first one
25822 on your list. (Tor considered launching requests for the others, but
25823 found that it already had a connection on the way for $0000...0000
25824 so it didn't open another.) Bugfix on 0.2.0.x.
25825 - If you have more than one bridge but don't know their digests,
25826 and the connection to one of the bridges failed, you would cancel
25827 all pending bridge connections. (After all, they all have the
25828 same digest.) Bugfix on 0.2.0.x.
25829 - When establishing a hidden service, introduction points that
25830 originate from cannibalized circuits are completely ignored and not
25831 included in rendezvous service descriptors. This might be another
25832 reason for delay in making a hidden service available. Bugfix
25833 from long ago (0.0.9.x?)
25836 - Allow OpenSSL to use dynamic locks if it wants.
25837 - When building a consensus, do not include routers that are down.
25838 This will cut down 30% to 40% on consensus size. Implements
25840 - In directory authorities' approved-routers files, allow
25841 fingerprints with or without space.
25842 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
25843 controller can query our current bootstrap state in case it attaches
25844 partway through and wants to catch up.
25845 - Send an initial "Starting" bootstrap status event, so we have a
25846 state to start out in.
25849 - Asking for a conditional consensus at .../consensus/<fingerprints>
25850 would crash a dirserver if it did not already have a
25851 consensus. Bugfix on 0.2.1.1-alpha.
25852 - Clean up some macro/CPP interactions: some GCC versions don't like
25853 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
25856 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
25857 - Directory authorities shouldn't complain about bootstrapping
25858 problems just because they do a lot of reachability testing and
25859 some of the connection attempts fail.
25860 - Start sending "count" and "recommendation" key/value pairs in
25861 bootstrap problem status events, so the controller can hear about
25862 problems even before Tor decides they're worth reporting for sure.
25863 - If you're using bridges, generate "bootstrap problem" warnings
25864 as soon as you run out of working bridges, rather than waiting
25865 for ten failures -- which will never happen if you have less than
25867 - If we close our OR connection because there's been a circuit
25868 pending on it for too long, we were telling our bootstrap status
25869 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
25872 Changes in version 0.2.1.1-alpha - 2008-06-13
25873 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
25874 were making the Tor process bloat especially on Linux; makes our TLS
25875 handshake blend in better; sends "bootstrap phase" status events to
25876 the controller, so it can keep the user informed of progress (and
25877 problems) fetching directory information and establishing circuits;
25878 and adds a variety of smaller features.
25881 - More work on making our TLS handshake blend in: modify the list
25882 of ciphers advertised by OpenSSL in client mode to even more
25883 closely resemble a common web browser. We cheat a little so that
25884 we can advertise ciphers that the locally installed OpenSSL doesn't
25886 - Start sending "bootstrap phase" status events to the controller,
25887 so it can keep the user informed of progress fetching directory
25888 information and establishing circuits. Also inform the controller
25889 if we think we're stuck at a particular bootstrap phase. Implements
25891 - Resume using OpenSSL's RAND_poll() for better (and more portable)
25892 cross-platform entropy collection again. We used to use it, then
25893 stopped using it because of a bug that could crash systems that
25894 called RAND_poll when they had a lot of fds open. It looks like the
25895 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
25896 at startup, and to call RAND_poll() when we reseed later only if
25897 we have a non-buggy OpenSSL version.
25900 - When we choose to abandon a new entry guard because we think our
25901 older ones might be better, close any circuits pending on that
25902 new entry guard connection. This fix should make us recover much
25903 faster when our network is down and then comes back. Bugfix on
25904 0.1.2.8-beta; found by lodger.
25906 o Memory fixes and improvements:
25907 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
25908 to avoid unused RAM in buffer chunks and memory pools.
25909 - Speed up parsing and cut down on memory fragmentation by using
25910 stack-style allocations for parsing directory objects. Previously,
25911 this accounted for over 40% of allocations from within Tor's code
25912 on a typical directory cache.
25913 - Use a Bloom filter rather than a digest-based set to track which
25914 descriptors we need to keep around when we're cleaning out old
25915 router descriptors. This speeds up the computation significantly,
25916 and may reduce fragmentation.
25917 - Reduce the default smartlist size from 32 to 16; it turns out that
25918 most smartlists hold around 8-12 elements tops.
25919 - Make dumpstats() log the fullness and size of openssl-internal
25921 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
25922 patch to their OpenSSL, turn it on to save memory on servers. This
25923 patch will (with any luck) get included in a mainline distribution
25925 - Never use OpenSSL compression: it wastes RAM and CPU trying to
25926 compress cells, which are basically all encrypted, compressed,
25930 - Stop reloading the router list from disk for no reason when we
25931 run out of reachable directory mirrors. Once upon a time reloading
25932 it would set the 'is_running' flag back to 1 for them. It hasn't
25933 done that for a long time.
25934 - In very rare situations new hidden service descriptors were
25935 published earlier than 30 seconds after the last change to the
25936 service. (We currently think that a hidden service descriptor
25937 that's been stable for 30 seconds is worth publishing.)
25940 - Allow separate log levels to be configured for different logging
25941 domains. For example, this allows one to log all notices, warnings,
25942 or errors, plus all memory management messages of level debug or
25943 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
25944 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
25945 and stop using a warning that had become unfixably verbose under
25947 - New --hush command-line option similar to --quiet. While --quiet
25948 disables all logging to the console on startup, --hush limits the
25949 output to messages of warning and error severity.
25950 - Servers support a new URL scheme for consensus downloads that
25951 allows the client to specify which authorities are trusted.
25952 The server then only sends the consensus if the client will trust
25953 it. Otherwise a 404 error is sent back. Clients use this
25954 new scheme when the server supports it (meaning it's running
25955 0.2.1.1-alpha or later). Implements proposal 134.
25956 - New configure/torrc options (--enable-geoip-stats,
25957 DirRecordUsageByCountry) to record how many IPs we've served
25958 directory info to in each country code, how many status documents
25959 total we've sent to each country code, and what share of the total
25960 directory requests we should expect to see.
25961 - Use the TLS1 hostname extension to more closely resemble browser
25963 - Lots of new unit tests.
25964 - Add a macro to implement the common pattern of iterating through
25965 two parallel lists in lockstep.
25968 Changes in version 0.2.0.28-rc - 2008-06-13
25969 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
25970 performance bug, and fixes a bunch of smaller bugs.
25973 - Fix a bug where, when we were choosing the 'end stream reason' to
25974 put in our relay end cell that we send to the exit relay, Tor
25975 clients on Windows were sometimes sending the wrong 'reason'. The
25976 anonymity problem is that exit relays may be able to guess whether
25977 the client is running Windows, thus helping partition the anonymity
25978 set. Down the road we should stop sending reasons to exit relays,
25979 or otherwise prevent future versions of this bug.
25982 - While setting up a hidden service, some valid introduction circuits
25983 were overlooked and abandoned. This might be the reason for
25984 the long delay in making a hidden service available. Bugfix on
25988 - Update to the "June 9 2008" ip-to-country file.
25989 - Run 'make test' as part of 'make dist', so we stop releasing so
25990 many development snapshots that fail their unit tests.
25993 - When we're checking if we have enough dir info for each relay
25994 to begin establishing circuits, make sure that we actually have
25995 the descriptor listed in the consensus, not just any descriptor.
25997 - Bridge relays no longer print "xx=0" in their extrainfo document
25998 for every single country code in the geoip db. Bugfix on
26000 - Only warn when we fail to load the geoip file if we were planning to
26001 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
26002 - If we change our MaxAdvertisedBandwidth and then reload torrc,
26003 Tor won't realize it should publish a new relay descriptor. Fixes
26004 bug 688, reported by mfr. Bugfix on 0.1.2.x.
26005 - When we haven't had any application requests lately, don't bother
26006 logging that we have expired a bunch of descriptors. Bugfix
26008 - Make relay cells written on a connection count as non-padding when
26009 tracking how long a connection has been in use. Bugfix on
26010 0.2.0.1-alpha. Spotted by lodger.
26011 - Fix unit tests in 0.2.0.27-rc.
26012 - Fix compile on Windows.
26015 Changes in version 0.2.0.27-rc - 2008-06-03
26016 Tor 0.2.0.27-rc adds a few features we left out of the earlier
26017 release candidates. In particular, we now include an IP-to-country
26018 GeoIP database, so controllers can easily look up what country a
26019 given relay is in, and so bridge relays can give us some sanitized
26020 summaries about which countries are making use of bridges. (See proposal
26021 126-geoip-fetching.txt for details.)
26024 - Include an IP-to-country GeoIP file in the tarball, so bridge
26025 relays can report sanitized summaries of the usage they're seeing.
26028 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
26029 Robert Hogan. Fixes the first part of bug 681.
26030 - Make bridge authorities never serve extrainfo docs.
26031 - Add support to detect Libevent versions in the 1.4.x series
26033 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
26034 - Include a new contrib/tor-exit-notice.html file that exit relay
26035 operators can put on their website to help reduce abuse queries.
26038 - When tunneling an encrypted directory connection, and its first
26039 circuit fails, do not leave it unattached and ask the controller
26040 to deal. Fixes the second part of bug 681.
26041 - Make bridge authorities correctly expire old extrainfo documents
26045 Changes in version 0.2.0.26-rc - 2008-05-13
26046 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
26047 in Debian's OpenSSL packages. All users running any 0.2.0.x version
26048 should upgrade, whether they're running Debian or not.
26050 o Major security fixes:
26051 - Use new V3 directory authority keys on the tor26, gabelmoo, and
26052 moria1 V3 directory authorities. The old keys were generated with
26053 a vulnerable version of Debian's OpenSSL package, and must be
26054 considered compromised. Other authorities' keys were not generated
26055 with an affected version of OpenSSL.
26058 - List authority signatures as "unrecognized" based on DirServer
26059 lines, not on cert cache. Bugfix on 0.2.0.x.
26062 - Add a new V3AuthUseLegacyKey option to make it easier for
26063 authorities to change their identity keys if they have to.
26066 Changes in version 0.2.0.25-rc - 2008-04-23
26067 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
26070 - Remember to initialize threading before initializing logging.
26071 Otherwise, many BSD-family implementations will crash hard on
26072 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
26075 - Authorities correctly free policies on bad servers on
26076 exit. Fixes bug 672. Bugfix on 0.2.0.x.
26079 Changes in version 0.2.0.24-rc - 2008-04-22
26080 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
26081 v3 directory authority, makes relays with dynamic IP addresses and no
26082 DirPort notice more quickly when their IP address changes, fixes a few
26083 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
26085 o New directory authorities:
26086 - Take lefkada out of the list of v3 directory authorities, since
26087 it has been down for months.
26088 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
26092 - Detect address changes more quickly on non-directory mirror
26093 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
26095 o Minor features (security):
26096 - Reject requests for reverse-dns lookup of names that are in
26097 a private address space. Patch from lodger.
26098 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
26101 o Minor bugfixes (crashes):
26102 - Avoid a rare assert that can trigger when Tor doesn't have much
26103 directory information yet and it tries to fetch a v2 hidden
26104 service descriptor. Fixes bug 651, reported by nwf.
26105 - Initialize log mutex before initializing dmalloc. Otherwise,
26106 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
26107 - Use recursive pthread mutexes in order to avoid deadlock when
26108 logging debug-level messages to a controller. Bug spotted by nwf,
26109 bugfix on 0.2.0.16-alpha.
26111 o Minor bugfixes (resource management):
26112 - Keep address policies from leaking memory: start their refcount
26113 at 1, not 2. Bugfix on 0.2.0.16-alpha.
26114 - Free authority certificates on exit, so they don't look like memory
26115 leaks. Bugfix on 0.2.0.19-alpha.
26116 - Free static hashtables for policy maps and for TLS connections on
26117 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
26118 - Avoid allocating extra space when computing consensuses on 64-bit
26119 platforms. Bug spotted by aakova.
26121 o Minor bugfixes (misc):
26122 - Do not read the configuration file when we've only been told to
26123 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
26124 based on patch from Sebastian Hahn.
26125 - Exit relays that are used as a client can now reach themselves
26126 using the .exit notation, rather than just launching an infinite
26127 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
26128 - When attempting to open a logfile fails, tell us why.
26129 - Fix a dumb bug that was preventing us from knowing that we should
26130 preemptively build circuits to handle expected directory requests.
26131 Fixes bug 660. Bugfix on 0.1.2.x.
26132 - Warn less verbosely about clock skew from netinfo cells from
26133 untrusted sources. Fixes bug 663.
26134 - Make controller stream events for DNS requests more consistent,
26135 by adding "new stream" events for DNS requests, and removing
26136 spurious "stream closed" events" for cached reverse resolves.
26137 Patch from mwenge. Fixes bug 646.
26138 - Correctly notify one-hop connections when a circuit build has
26139 failed. Possible fix for bug 669. Found by lodger.
26142 Changes in version 0.2.0.23-rc - 2008-03-24
26143 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
26144 makes bootstrapping faster if the first directory mirror you contact
26145 is down. The bundles also include the new Vidalia 0.1.2 release.
26148 - When a tunneled directory request is made to a directory server
26149 that's down, notice after 30 seconds rather than 120 seconds. Also,
26150 fail any begindir streams that are pending on it, so they can
26151 retry elsewhere. This was causing multi-minute delays on bootstrap.
26154 Changes in version 0.2.0.22-rc - 2008-03-18
26155 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
26156 enables encrypted directory connections by default for non-relays, fixes
26157 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
26158 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
26161 - Enable encrypted directory connections by default for non-relays,
26162 so censor tools that block Tor directory connections based on their
26163 plaintext patterns will no longer work. This means Tor works in
26164 certain censored countries by default again.
26167 - Make sure servers always request certificates from clients during
26168 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
26169 - Do not enter a CPU-eating loop when a connection is closed in
26170 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
26171 diagnosed by lodger; bugfix on 0.2.0.20-rc.
26172 - Fix assertion failure that could occur when a blocked circuit
26173 became unblocked, and it had pending client DNS requests. Bugfix
26174 on 0.2.0.1-alpha. Fixes bug 632.
26176 o Minor bugfixes (on 0.1.2.x):
26177 - Generate "STATUS_SERVER" events rather than misspelled
26178 "STATUS_SEVER" events. Caught by mwenge.
26179 - When counting the number of bytes written on a TLS connection,
26180 look at the BIO actually used for writing to the network, not
26181 at the BIO used (sometimes) to buffer data for the network.
26182 Looking at different BIOs could result in write counts on the
26183 order of ULONG_MAX. Fixes bug 614.
26184 - On Windows, correctly detect errors when listing the contents of
26185 a directory. Fix from lodger.
26187 o Minor bugfixes (on 0.2.0.x):
26188 - Downgrade "sslv3 alert handshake failure" message to INFO.
26189 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
26190 left BandwidthRate and BandwidthBurst at the default, we would be
26191 silently limited by those defaults. Now raise them to match the
26192 RelayBandwidth* values.
26193 - Fix the SVK version detection logic to work correctly on a branch.
26194 - Make --enable-openbsd-malloc work correctly on Linux with alpha
26195 CPUs. Fixes bug 625.
26196 - Logging functions now check that the passed severity is sane.
26197 - Use proper log levels in the testsuite call of
26198 get_interface_address6().
26199 - When using a nonstandard malloc, do not use the platform values for
26200 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
26201 - Make the openbsd malloc code use 8k pages on alpha CPUs and
26203 - Detect mismatched page sizes when using --enable-openbsd-malloc.
26204 - Avoid double-marked-for-close warning when certain kinds of invalid
26205 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
26206 for bug 617. Bugfix on 0.2.0.1-alpha.
26207 - Make sure that the "NULL-means-reject *:*" convention is followed by
26208 all the policy manipulation functions, avoiding some possible crash
26209 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
26210 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
26211 actually works, and doesn't warn about every single reverse lookup.
26212 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
26215 - Only log guard node status when guard node status has changed.
26216 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
26217 make "INFO" 75% less verbose.
26220 Changes in version 0.2.0.21-rc - 2008-03-02
26221 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
26222 makes Tor work well with Vidalia again, fixes a rare assert bug,
26223 and fixes a pair of more minor bugs. The bundles also include Vidalia
26224 0.1.0 and Torbutton 1.1.16.
26227 - The control port should declare that it requires password auth
26228 when HashedControlSessionPassword is set too. Patch from Matt Edman;
26229 bugfix on 0.2.0.20-rc. Fixes bug 615.
26230 - Downgrade assert in connection_buckets_decrement() to a log message.
26231 This may help us solve bug 614, and in any case will make its
26232 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
26233 - We were sometimes miscounting the number of bytes read from the
26234 network, causing our rate limiting to not be followed exactly.
26235 Bugfix on 0.2.0.16-alpha. Reported by lodger.
26238 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
26239 OpenSSL versions should have been working fine. Diagnosis and patch
26240 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
26241 Bugfix on 0.2.0.20-rc.
26244 Changes in version 0.2.0.20-rc - 2008-02-24
26245 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
26246 makes more progress towards normalizing Tor's TLS handshake, makes
26247 hidden services work better again, helps relays bootstrap if they don't
26248 know their IP address, adds optional support for linking in openbsd's
26249 allocator or tcmalloc, allows really fast relays to scale past 15000
26250 sockets, and fixes a bunch of minor bugs reported by Veracode.
26253 - Enable the revised TLS handshake based on the one designed by
26254 Steven Murdoch in proposal 124, as revised in proposal 130. It
26255 includes version negotiation for OR connections as described in
26256 proposal 105. The new handshake is meant to be harder for censors
26257 to fingerprint, and it adds the ability to detect certain kinds of
26258 man-in-the-middle traffic analysis attacks. The version negotiation
26259 feature will allow us to improve Tor's link protocol more safely
26261 - Choose which bridge to use proportional to its advertised bandwidth,
26262 rather than uniformly at random. This should speed up Tor for
26263 bridge users. Also do this for people who set StrictEntryNodes.
26264 - When a TrackHostExits-chosen exit fails too many times in a row,
26265 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
26268 - Resolved problems with (re-)fetching hidden service descriptors.
26269 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
26270 and 0.2.0.19-alpha.
26271 - If we only ever used Tor for hidden service lookups or posts, we
26272 would stop building circuits and start refusing connections after
26273 24 hours, since we falsely believed that Tor was dormant. Reported
26274 by nwf; bugfix on 0.1.2.x.
26275 - Servers that don't know their own IP address should go to the
26276 authorities for their first directory fetch, even if their DirPort
26277 is off or if they don't know they're reachable yet. This will help
26278 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
26279 - When counting the number of open sockets, count not only the number
26280 of sockets we have received from the socket() call, but also
26281 the number we've gotten from accept() and socketpair(). This bug
26282 made us fail to count all sockets that we were using for incoming
26283 connections. Bugfix on 0.2.0.x.
26284 - Fix code used to find strings within buffers, when those strings
26285 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
26286 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
26287 - Add a new __HashedControlSessionPassword option for controllers
26288 to use for one-off session password hashes that shouldn't get
26289 saved to disk by SAVECONF --- Vidalia users were accumulating a
26290 pile of HashedControlPassword lines in their torrc files, one for
26291 each time they had restarted Tor and then clicked Save. Make Tor
26292 automatically convert "HashedControlPassword" to this new option but
26293 only when it's given on the command line. Partial fix for bug 586.
26295 o Minor features (performance):
26296 - Tune parameters for cell pool allocation to minimize amount of
26298 - Add OpenBSD malloc code from phk as an optional malloc
26299 replacement on Linux: some glibc libraries do very poorly
26300 with Tor's memory allocation patterns. Pass
26301 --enable-openbsd-malloc to get the replacement malloc code.
26302 - Add a --with-tcmalloc option to the configure script to link
26303 against tcmalloc (if present). Does not yet search for
26304 non-system include paths.
26305 - Stop imposing an arbitrary maximum on the number of file descriptors
26306 used for busy servers. Bug reported by Olaf Selke; patch from
26309 o Minor features (other):
26310 - When SafeLogging is disabled, log addresses along with all TLS
26312 - When building with --enable-gcc-warnings, check for whether Apple's
26313 warning "-Wshorten-64-to-32" is available.
26314 - Add a --passphrase-fd argument to the tor-gencert command for
26317 o Minor bugfixes (memory leaks and code problems):
26318 - We were leaking a file descriptor if Tor started with a zero-length
26319 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
26320 - Detect size overflow in zlib code. Reported by Justin Ferguson and
26322 - We were comparing the raw BridgePassword entry with a base64'ed
26323 version of it, when handling a "/tor/networkstatus-bridges"
26324 directory request. Now compare correctly. Noticed by Veracode.
26325 - Recover from bad tracked-since value in MTBF-history file.
26326 Should fix bug 537.
26327 - Alter the code that tries to recover from unhandled write
26328 errors, to not try to flush onto a socket that's given us
26329 unhandled errors. Bugfix on 0.1.2.x.
26330 - Make Unix controlsockets work correctly on OpenBSD. Patch from
26331 tup. Bugfix on 0.2.0.3-alpha.
26333 o Minor bugfixes (other):
26334 - If we have an extra-info document for our server, always make
26335 it available on the control port, even if we haven't gotten
26336 a copy of it from an authority yet. Patch from mwenge.
26337 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
26338 - Directory mirrors no longer include a guess at the client's IP
26339 address if the connection appears to be coming from the same /24
26340 network; it was producing too many wrong guesses.
26341 - Make the new hidden service code respect the SafeLogging setting.
26342 Bugfix on 0.2.0.x. Patch from Karsten.
26343 - When starting as an authority, do not overwrite all certificates
26344 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
26345 - If we're trying to flush the last bytes on a connection (for
26346 example, when answering a directory request), reset the
26347 time-to-give-up timeout every time we manage to write something
26348 on the socket. Bugfix on 0.1.2.x.
26349 - Change the behavior of "getinfo status/good-server-descriptor"
26350 so it doesn't return failure when any authority disappears.
26351 - Even though the man page said that "TrackHostExits ." should
26352 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
26353 - Report TLS "zero return" case as a "clean close" and "IO error"
26354 as a "close". Stop calling closes "unexpected closes": existing
26355 Tors don't use SSL_close(), so having a connection close without
26356 the TLS shutdown handshake is hardly unexpected.
26357 - Send NAMESERVER_STATUS messages for a single failed nameserver
26360 o Code simplifications and refactoring:
26361 - Remove the tor_strpartition function: its logic was confused,
26362 and it was only used for one thing that could be implemented far
26366 Changes in version 0.2.0.19-alpha - 2008-02-09
26367 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
26368 handshake, makes path selection for relays more secure and IP address
26369 guessing more robust, and generally fixes a lot of bugs in preparation
26370 for calling the 0.2.0 branch stable.
26373 - Do not include recognizeable strings in the commonname part of
26374 Tor's x509 certificates.
26377 - If we're a relay, avoid picking ourselves as an introduction point,
26378 a rendezvous point, or as the final hop for internal circuits. Bug
26379 reported by taranis and lodger. Bugfix on 0.1.2.x.
26380 - Patch from "Andrew S. Lists" to catch when we contact a directory
26381 mirror at IP address X and he says we look like we're coming from
26382 IP address X. Bugfix on 0.1.2.x.
26384 o Minor features (security):
26385 - Be more paranoid about overwriting sensitive memory on free(),
26386 as a defensive programming tactic to ensure forward secrecy.
26388 o Minor features (directory authority):
26389 - Actually validate the options passed to AuthDirReject,
26390 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
26391 - Reject router descriptors with out-of-range bandwidthcapacity or
26392 bandwidthburst values.
26394 o Minor features (controller):
26395 - Reject controller commands over 1MB in length. This keeps rogue
26396 processes from running us out of memory.
26398 o Minor features (misc):
26399 - Give more descriptive well-formedness errors for out-of-range
26400 hidden service descriptor/protocol versions.
26401 - Make memory debugging information describe more about history
26402 of cell allocation, so we can help reduce our memory use.
26404 o Deprecated features (controller):
26405 - The status/version/num-versioning and status/version/num-concurring
26406 GETINFO options are no longer useful in the v3 directory protocol:
26407 treat them as deprecated, and warn when they're used.
26410 - When our consensus networkstatus has been expired for a while, stop
26411 being willing to build circuits using it. Fixes bug 401. Bugfix
26413 - Directory caches now fetch certificates from all authorities
26414 listed in a networkstatus consensus, even when they do not
26415 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
26416 - When connecting to a bridge without specifying its key, insert
26417 the connection into the identity-to-connection map as soon as
26418 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
26419 - Detect versions of OS X where malloc_good_size() is present in the
26420 library but never actually declared. Resolves bug 587. Bugfix
26422 - Stop incorrectly truncating zlib responses to directory authority
26423 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
26424 - Stop recommending that every server operator send mail to tor-ops.
26425 Resolves bug 597. Bugfix on 0.1.2.x.
26426 - Don't trigger an assert if we start a directory authority with a
26427 private IP address (like 127.0.0.1).
26428 - Avoid possible failures when generating a directory with routers
26429 with over-long versions strings, or too many flags set. Bugfix
26431 - If an attempt to launch a DNS resolve request over the control
26432 port fails because we have overrun the limit on the number of
26433 connections, tell the controller that the request has failed.
26434 - Avoid using too little bandwidth when our clock skips a few
26435 seconds. Bugfix on 0.1.2.x.
26436 - Fix shell error when warning about missing packages in configure
26437 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
26438 - Do not become confused when receiving a spurious VERSIONS-like
26439 cell from a confused v1 client. Bugfix on 0.2.0.x.
26440 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
26441 introduction points for a hidden service have failed. Patch from
26442 Karsten Loesing. Bugfix on 0.2.0.x.
26444 o Code simplifications and refactoring:
26445 - Remove some needless generality from cpuworker code, for improved
26447 - Stop overloading the circuit_t.onionskin field for both "onionskin
26448 from a CREATE cell that we are waiting for a cpuworker to be
26449 assigned" and "onionskin from an EXTEND cell that we are going to
26450 send to an OR as soon as we are connected". Might help with bug 600.
26451 - Add an in-place version of aes_crypt() so that we can avoid doing a
26452 needless memcpy() call on each cell payload.
26455 Changes in version 0.2.0.18-alpha - 2008-01-25
26456 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
26457 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
26458 that can warn or reject connections to ports generally associated with
26459 vulnerable-plaintext protocols.
26461 o New directory authorities:
26462 - Set up dannenberg (run by CCC) as the sixth v3 directory
26466 - Fix a major memory leak when attempting to use the v2 TLS
26467 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
26468 - We accidentally enabled the under-development v2 TLS handshake
26469 code, which was causing log entries like "TLS error while
26470 renegotiating handshake". Disable it again. Resolves bug 590.
26471 - We were computing the wrong Content-Length: header for directory
26472 responses that need to be compressed on the fly, causing clients
26473 asking for those items to always fail. Bugfix on 0.2.0.x; partially
26477 - Avoid going directly to the directory authorities even if you're a
26478 relay, if you haven't found yourself reachable yet or if you've
26479 decided not to advertise your dirport yet. Addresses bug 556.
26480 - If we've gone 12 hours since our last bandwidth check, and we
26481 estimate we have less than 50KB bandwidth capacity but we could
26482 handle more, do another bandwidth test.
26483 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
26484 Tor can warn and/or refuse connections to ports commonly used with
26485 vulnerable-plaintext protocols. Currently we warn on ports 23,
26486 109, 110, and 143, but we don't reject any.
26489 - When we setconf ClientOnly to 1, close any current OR and Dir
26490 listeners. Reported by mwenge.
26491 - When we get a consensus that's been signed by more people than
26492 we expect, don't log about it; it's not a big deal. Reported
26496 - Don't answer "/tor/networkstatus-bridges" directory requests if
26497 the request isn't encrypted.
26498 - Make "ClientOnly 1" config option disable directory ports too.
26499 - Patches from Karsten Loesing to make v2 hidden services more
26500 robust: work even when there aren't enough HSDir relays available;
26501 retry when a v2 rend desc fetch fails; but don't retry if we
26502 already have a usable v0 rend desc.
26505 Changes in version 0.2.0.17-alpha - 2008-01-17
26506 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
26509 - Make the tor-gencert man page get included correctly in the tarball.
26512 Changes in version 0.2.0.16-alpha - 2008-01-17
26513 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
26514 Loesing, and generally cleans up a lot of features and minor bugs.
26516 o New directory authorities:
26517 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
26520 o Major performance improvements:
26521 - Switch our old ring buffer implementation for one more like that
26522 used by free Unix kernels. The wasted space in a buffer with 1mb
26523 of data will now be more like 8k than 1mb. The new implementation
26524 also avoids realloc();realloc(); patterns that can contribute to
26525 memory fragmentation.
26528 - Configuration files now accept C-style strings as values. This
26529 helps encode characters not allowed in the current configuration
26530 file format, such as newline or #. Addresses bug 557.
26531 - Although we fixed bug 539 (where servers would send HTTP status 503
26532 responses _and_ send a body too), there are still servers out
26533 there that haven't upgraded. Therefore, make clients parse such
26534 bodies when they receive them.
26535 - When we're not serving v2 directory information, there is no reason
26536 to actually keep any around. Remove the obsolete files and directory
26537 on startup if they are very old and we aren't going to serve them.
26539 o Minor performance improvements:
26540 - Reference-count and share copies of address policy entries; only 5%
26541 of them were actually distinct.
26542 - Never walk through the list of logs if we know that no log is
26543 interested in a given message.
26546 - When an authority has not signed a consensus, do not try to
26547 download a nonexistent "certificate with key 00000000". Bugfix
26548 on 0.2.0.x. Fixes bug 569.
26549 - Fix a rare assert error when we're closing one of our threads:
26550 use a mutex to protect the list of logs, so we never write to the
26551 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
26552 bug 575, which is kind of the revenge of bug 222.
26553 - Patch from Karsten Loesing to complain less at both the client
26554 and the relay when a relay used to have the HSDir flag but doesn't
26555 anymore, and we try to upload a hidden service descriptor.
26556 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
26558 - Do not try to download missing certificates until we have tried
26559 to check our fallback consensus. Fixes bug 583.
26560 - Make bridges round reported GeoIP stats info up to the nearest
26561 estimate, not down. Now we can distinguish between "0 people from
26562 this country" and "1 person from this country".
26563 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
26564 - Avoid possible segfault if key generation fails in
26565 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
26566 - Avoid segfault in the case where a badly behaved v2 versioning
26567 directory sends a signed networkstatus with missing client-versions.
26569 - Avoid segfaults on certain complex invocations of
26570 router_get_by_hexdigest(). Bugfix on 0.1.2.
26571 - Correct bad index on array access in parse_http_time(). Bugfix
26573 - Fix possible bug in vote generation when server versions are present
26574 but client versions are not.
26575 - Fix rare bug on REDIRECTSTREAM control command when called with no
26576 port set: it could erroneously report an error when none had
26578 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
26579 compressing large objects and find ourselves with more than 4k
26580 left over. Bugfix on 0.2.0.
26581 - Fix a small memory leak when setting up a hidden service.
26582 - Fix a few memory leaks that could in theory happen under bizarre
26584 - Fix an assert if we post a general-purpose descriptor via the
26585 control port but that descriptor isn't mentioned in our current
26586 network consensus. Bug reported by Jon McLachlan; bugfix on
26589 o Minor features (controller):
26590 - Get NS events working again. Patch from tup.
26591 - The GETCONF command now escapes and quotes configuration values
26592 that don't otherwise fit into the torrc file.
26593 - The SETCONF command now handles quoted values correctly.
26595 o Minor features (directory authorities):
26596 - New configuration options to override default maximum number of
26597 servers allowed on a single IP address. This is important for
26598 running a test network on a single host.
26599 - Actually implement the -s option to tor-gencert.
26600 - Add a manual page for tor-gencert.
26602 o Minor features (bridges):
26603 - Bridge authorities no longer serve bridge descriptors over
26604 unencrypted connections.
26606 o Minor features (other):
26607 - Add hidden services and DNSPorts to the list of things that make
26608 Tor accept that it has running ports. Change starting Tor with no
26609 ports from a fatal error to a warning; we might change it back if
26610 this turns out to confuse anybody. Fixes bug 579.
26613 Changes in version 0.1.2.19 - 2008-01-17
26614 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
26615 exit policy a little bit more conservative so it's safer to run an
26616 exit relay on a home system, and fixes a variety of smaller issues.
26619 - Exit policies now reject connections that are addressed to a
26620 relay's public (external) IP address too, unless
26621 ExitPolicyRejectPrivate is turned off. We do this because too
26622 many relays are running nearby to services that trust them based
26623 on network address.
26626 - When the clock jumps forward a lot, do not allow the bandwidth
26627 buckets to become negative. Fixes bug 544.
26628 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26629 on every successful resolve. Reported by Mike Perry.
26630 - Purge old entries from the "rephist" database and the hidden
26631 service descriptor database even when DirPort is zero.
26632 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26633 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26634 crashing or mis-answering these requests.
26635 - When we decide to send a 503 response to a request for servers, do
26636 not then also send the server descriptors: this defeats the whole
26637 purpose. Fixes bug 539.
26640 - Changing the ExitPolicyRejectPrivate setting should cause us to
26641 rebuild our server descriptor.
26642 - Fix handling of hex nicknames when answering controller requests for
26643 networkstatus by name, or when deciding whether to warn about
26644 unknown routers in a config option. (Patch from mwenge.)
26645 - Fix a couple of hard-to-trigger autoconf problems that could result
26646 in really weird results on platforms whose sys/types.h files define
26647 nonstandard integer types.
26648 - Don't try to create the datadir when running --verify-config or
26649 --hash-password. Resolves bug 540.
26650 - If we were having problems getting a particular descriptor from the
26651 directory caches, and then we learned about a new descriptor for
26652 that router, we weren't resetting our failure count. Reported
26654 - Although we fixed bug 539 (where servers would send HTTP status 503
26655 responses _and_ send a body too), there are still servers out there
26656 that haven't upgraded. Therefore, make clients parse such bodies
26657 when they receive them.
26658 - Run correctly on systems where rlim_t is larger than unsigned long.
26659 This includes some 64-bit systems.
26660 - Run correctly on platforms (like some versions of OS X 10.5) where
26661 the real limit for number of open files is OPEN_FILES, not rlim_max
26662 from getrlimit(RLIMIT_NOFILES).
26663 - Avoid a spurious free on base64 failure.
26664 - Avoid segfaults on certain complex invocations of
26665 router_get_by_hexdigest().
26666 - Fix rare bug on REDIRECTSTREAM control command when called with no
26667 port set: it could erroneously report an error when none had
26671 Changes in version 0.2.0.15-alpha - 2007-12-25
26672 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
26673 features added in 0.2.0.13-alpha.
26676 - Fix several remotely triggerable asserts based on DirPort requests
26677 for a v2 or v3 networkstatus object before we were prepared. This
26678 was particularly bad for 0.2.0.13 and later bridge relays, who
26679 would never have a v2 networkstatus and would thus always crash
26680 when used. Bugfixes on 0.2.0.x.
26681 - Estimate the v3 networkstatus size more accurately, rather than
26682 estimating it at zero bytes and giving it artificially high priority
26683 compared to other directory requests. Bugfix on 0.2.0.x.
26686 - Fix configure.in logic for cross-compilation.
26687 - When we load a bridge descriptor from the cache, and it was
26688 previously unreachable, mark it as retriable so we won't just
26689 ignore it. Also, try fetching a new copy immediately. Bugfixes
26691 - The bridge GeoIP stats were counting other relays, for example
26692 self-reachability and authority-reachability tests.
26695 - Support compilation to target iPhone; patch from cjacker huang.
26696 To build for iPhone, pass the --enable-iphone option to configure.
26699 Changes in version 0.2.0.14-alpha - 2007-12-23
26701 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
26702 without a datadirectory from a previous Tor install. Reported
26704 - Fix a crash when we fetch a descriptor that turns out to be
26705 unexpected (it used to be in our networkstatus when we started
26706 fetching it, but it isn't in our current networkstatus), and we
26707 aren't using bridges. Bugfix on 0.2.0.x.
26708 - Fix a crash when accessing hidden services: it would work the first
26709 time you use a given introduction point for your service, but
26710 on subsequent requests we'd be using garbage memory. Fixed by
26711 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
26712 - Fix a crash when we load a bridge descriptor from disk but we don't
26713 currently have a Bridge line for it in our torrc. Bugfix on
26717 - If bridge authorities set BridgePassword, they will serve a
26718 snapshot of known bridge routerstatuses from their DirPort to
26719 anybody who knows that password. Unset by default.
26722 - Make the unit tests build again.
26723 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
26724 - Make PublishServerDescriptor default to 1, so the default doesn't
26725 have to change as we invent new directory protocol versions.
26726 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
26727 be included unless sys/time.h is already included. Fixes
26728 bug 553. Bugfix on 0.2.0.x.
26729 - If we receive a general-purpose descriptor and then receive an
26730 identical bridge-purpose descriptor soon after, don't discard
26731 the next one as a duplicate.
26734 - If BridgeRelay is set to 1, then the default for
26735 PublishServerDescriptor is now "bridge" rather than "v2,v3".
26736 - If the user sets RelayBandwidthRate but doesn't set
26737 RelayBandwidthBurst, then make them equal rather than erroring out.
26740 Changes in version 0.2.0.13-alpha - 2007-12-21
26741 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
26742 Goodell, fixes many more bugs, and adds a lot of infrastructure for
26745 o New directory authorities:
26746 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
26750 - Only update guard status (usable / not usable) once we have
26751 enough directory information. This was causing us to always pick
26752 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
26753 causing us to discard all our guards on startup if we hadn't been
26754 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
26755 - Purge old entries from the "rephist" database and the hidden
26756 service descriptor databases even when DirPort is zero. Bugfix
26758 - We were ignoring our RelayBandwidthRate for the first 30 seconds
26759 after opening a circuit -- even a relayed circuit. Bugfix on
26761 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26762 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26763 crashing or mis-answering these types of requests.
26764 - Relays were publishing their server descriptor to v1 and v2
26765 directory authorities, but they didn't try publishing to v3-only
26766 authorities. Fix this; and also stop publishing to v1 authorities.
26768 - When we were reading router descriptors from cache, we were ignoring
26769 the annotations -- so for example we were reading in bridge-purpose
26770 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
26771 - When we decided to send a 503 response to a request for servers, we
26772 were then also sending the server descriptors: this defeats the
26773 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
26776 - Bridge relays now behave like clients with respect to time
26777 intervals for downloading new consensus documents -- otherwise they
26778 stand out. Bridge users now wait until the end of the interval,
26779 so their bridge relay will be sure to have a new consensus document.
26780 - Three new config options (AlternateDirAuthority,
26781 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
26782 user selectively replace the default directory authorities by type,
26783 rather than the all-or-nothing replacement that DirServer offers.
26784 - Tor can now be configured to read a GeoIP file from disk in one
26785 of two formats. This can be used by controllers to map IP addresses
26786 to countries. Eventually, it may support exit-by-country.
26787 - When possible, bridge relays remember which countries users
26788 are coming from, and report aggregate information in their
26789 extra-info documents, so that the bridge authorities can learn
26790 where Tor is blocked.
26791 - Bridge directory authorities now do reachability testing on the
26792 bridges they know. They provide router status summaries to the
26793 controller via "getinfo ns/purpose/bridge", and also dump summaries
26794 to a file periodically.
26795 - Stop fetching directory info so aggressively if your DirPort is
26796 on but your ORPort is off; stop fetching v2 dir info entirely.
26797 You can override these choices with the new FetchDirInfoEarly
26801 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
26802 consensus documents when there are too many relays at a single
26803 IP address. Now clear it in v2 network status documents too, and
26804 also clear it in routerinfo_t when the relay is no longer listed
26805 in the relevant networkstatus document.
26806 - Don't crash if we get an unexpected value for the
26807 PublishServerDescriptor config option. Reported by Matt Edman;
26808 bugfix on 0.2.0.9-alpha.
26809 - Our new v2 hidden service descriptor format allows descriptors
26810 that have no introduction points. But Tor crashed when we tried
26811 to build a descriptor with no intro points (and it would have
26812 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
26813 by Karsten Loesing.
26814 - Fix building with dmalloc 5.5.2 with glibc.
26815 - Reject uploaded descriptors and extrainfo documents if they're
26816 huge. Otherwise we'll cache them all over the network and it'll
26817 clog everything up. Reported by Aljosha Judmayer.
26818 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
26819 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
26820 - When the DANGEROUS_VERSION controller status event told us we're
26821 running an obsolete version, it used the string "OLD" to describe
26822 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
26823 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
26824 - If we can't expand our list of entry guards (e.g. because we're
26825 using bridges or we have StrictEntryNodes set), don't mark relays
26826 down when they fail a directory request. Otherwise we're too quick
26827 to mark all our entry points down. Bugfix on 0.1.2.x.
26828 - Fix handling of hex nicknames when answering controller requests for
26829 networkstatus by name, or when deciding whether to warn about unknown
26830 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
26831 - Fix a couple of hard-to-trigger autoconf problems that could result
26832 in really weird results on platforms whose sys/types.h files define
26833 nonstandard integer types. Bugfix on 0.1.2.x.
26834 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
26835 - Don't crash on name lookup when we have no current consensus. Fixes
26836 bug 538; bugfix on 0.2.0.x.
26837 - Only Tors that want to mirror the v2 directory info should
26838 create the "cached-status" directory in their datadir. (All Tors
26839 used to create it.) Bugfix on 0.2.0.9-alpha.
26840 - Directory authorities should only automatically download Extra Info
26841 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
26844 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
26845 consumers. (We already do this on HUP.)
26846 - Authorities and caches fetch the v2 networkstatus documents
26847 less often, now that v3 is encouraged.
26848 - Add a new config option BridgeRelay that specifies you want to
26849 be a bridge relay. Right now the only difference is that it makes
26850 you answer begin_dir requests, and it makes you cache dir info,
26851 even if your DirPort isn't on.
26852 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
26853 ask about source, timestamp of arrival, purpose, etc. We need
26854 something like this to help Vidalia not do GeoIP lookups on bridge
26856 - Allow multiple HashedControlPassword config lines, to support
26857 multiple controller passwords.
26858 - Authorities now decide whether they're authoritative for a given
26859 router based on the router's purpose.
26860 - New config options AuthDirBadDir and AuthDirListBadDirs for
26861 authorities to mark certain relays as "bad directories" in the
26862 networkstatus documents. Also supports the "!baddir" directive in
26863 the approved-routers file.
26866 Changes in version 0.2.0.12-alpha - 2007-11-16
26867 This twelfth development snapshot fixes some more build problems as
26868 well as a few minor bugs.
26871 - Make it build on OpenBSD again. Patch from tup.
26872 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
26873 package-building for Red Hat, OS X, etc.
26875 o Minor bugfixes (on 0.1.2.x):
26876 - Changing the ExitPolicyRejectPrivate setting should cause us to
26877 rebuild our server descriptor.
26879 o Minor bugfixes (on 0.2.0.x):
26880 - When we're lacking a consensus, don't try to perform rendezvous
26881 operations. Reported by Karsten Loesing.
26882 - Fix a small memory leak whenever we decide against using a
26883 newly picked entry guard. Reported by Mike Perry.
26884 - When authorities detected more than two relays running on the same
26885 IP address, they were clearing all the status flags but forgetting
26886 to clear the "hsdir" flag. So clients were being told that a
26887 given relay was the right choice for a v2 hsdir lookup, yet they
26888 never had its descriptor because it was marked as 'not running'
26890 - If we're trying to fetch a bridge descriptor and there's no way
26891 the bridge authority could help us (for example, we don't know
26892 a digest, or there is no bridge authority), don't be so eager to
26893 fall back to asking the bridge authority.
26894 - If we're using bridges or have strictentrynodes set, and our
26895 chosen exit is in the same family as all our bridges/entry guards,
26896 then be flexible about families.
26899 - When we negotiate a v2 link-layer connection (not yet implemented),
26900 accept RELAY_EARLY cells and turn them into RELAY cells if we've
26901 negotiated a v1 connection for their next step. Initial code for
26905 Changes in version 0.2.0.11-alpha - 2007-11-12
26906 This eleventh development snapshot fixes some build problems with
26907 the previous snapshot. It also includes a more secure-by-default exit
26908 policy for relays, fixes an enormous memory leak for exit relays, and
26909 fixes another bug where servers were falling out of the directory list.
26912 - Exit policies now reject connections that are addressed to a
26913 relay's public (external) IP address too, unless
26914 ExitPolicyRejectPrivate is turned off. We do this because too
26915 many relays are running nearby to services that trust them based
26916 on network address. Bugfix on 0.1.2.x.
26919 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26920 on every successful resolve. Reported by Mike Perry; bugfix
26922 - On authorities, never downgrade to old router descriptors simply
26923 because they're listed in the consensus. This created a catch-22
26924 where we wouldn't list a new descriptor because there was an
26925 old one in the consensus, and we couldn't get the new one in the
26926 consensus because we wouldn't list it. Possible fix for bug 548.
26927 Also, this might cause bug 543 to appear on authorities; if so,
26928 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
26930 o Packaging fixes on 0.2.0.10-alpha:
26931 - We were including instructions about what to do with the
26932 src/config/fallback-consensus file, but we weren't actually
26933 including it in the tarball. Disable all of that for now.
26936 - Allow people to say PreferTunnelledDirConns rather than
26937 PreferTunneledDirConns, for those alternate-spellers out there.
26940 - Don't reevaluate all the information from our consensus document
26941 just because we've downloaded a v2 networkstatus that we intend
26942 to cache. Fixes bug 545; bugfix on 0.2.0.x.
26945 Changes in version 0.2.0.10-alpha - 2007-11-10
26946 This tenth development snapshot adds a third v3 directory authority
26947 run by Mike Perry, adds most of Karsten Loesing's new hidden service
26948 descriptor format, fixes a bad crash bug and new bridge bugs introduced
26949 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
26950 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
26951 addresses many more minor issues.
26953 o New directory authorities:
26954 - Set up ides (run by Mike Perry) as the third v3 directory authority.
26957 - Allow tunnelled directory connections to ask for an encrypted
26958 "begin_dir" connection or an anonymized "uses a full Tor circuit"
26959 connection independently. Now we can make anonymized begin_dir
26960 connections for (e.g.) more secure hidden service posting and
26962 - More progress on proposal 114: code from Karsten Loesing to
26963 implement new hidden service descriptor format.
26964 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
26965 accommodate the growing number of servers that use the default
26966 and are reaching it.
26967 - Directory authorities use a new formula for selecting which nodes
26968 to advertise as Guards: they must be in the top 7/8 in terms of
26969 how long we have known about them, and above the median of those
26970 nodes in terms of weighted fractional uptime.
26971 - Make "not enough dir info yet" warnings describe *why* Tor feels
26972 it doesn't have enough directory info yet.
26975 - Stop servers from crashing if they set a Family option (or
26976 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
26978 - Make bridge users work again -- the move to v3 directories in
26979 0.2.0.9-alpha had introduced a number of bugs that made bridges
26980 no longer work for clients.
26981 - When the clock jumps forward a lot, do not allow the bandwidth
26982 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
26984 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
26985 - When the consensus lists a router descriptor that we previously were
26986 mirroring, but that we considered non-canonical, reload the
26987 descriptor as canonical. This fixes bug 543 where Tor servers
26988 would start complaining after a few days that they don't have
26989 enough directory information to build a circuit.
26990 - Consider replacing the current consensus when certificates arrive
26991 that make the pending consensus valid. Previously, we were only
26992 considering replacement when the new certs _didn't_ help.
26993 - Fix an assert error on startup if we didn't already have the
26994 consensus and certs cached in our datadirectory: we were caching
26995 the consensus in consensus_waiting_for_certs but then free'ing it
26997 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
26998 Request) if we need more v3 certs but we've already got pending
26999 requests for all of them.
27000 - Correctly back off from failing certificate downloads. Fixes
27002 - Authorities don't vote on the Running flag if they have been running
27003 for less than 30 minutes themselves. Fixes bug 547, where a newly
27004 started authority would vote that everyone was down.
27006 o New requirements:
27007 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
27008 it, it had no AES, and it hasn't seen any security patches since
27012 - Clients now hold circuitless TLS connections open for 1.5 times
27013 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
27014 rebuild a new circuit over them within that timeframe. Previously,
27015 they held them open only for KeepalivePeriod (5 minutes).
27016 - Use "If-Modified-Since" to avoid retrieving consensus
27017 networkstatuses that we already have.
27018 - When we have no consensus, check FallbackNetworkstatusFile (defaults
27019 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
27020 we start knowing some directory caches.
27021 - When we receive a consensus from the future, warn about skew.
27022 - Improve skew reporting: try to give the user a better log message
27023 about how skewed they are, and how much this matters.
27024 - When we have a certificate for an authority, believe that
27025 certificate's claims about the authority's IP address.
27026 - New --quiet command-line option to suppress the default console log.
27027 Good in combination with --hash-password.
27028 - Authorities send back an X-Descriptor-Not-New header in response to
27029 an accepted-but-discarded descriptor upload. Partially implements
27031 - Make the log message for "tls error. breaking." more useful.
27032 - Better log messages about certificate downloads, to attempt to
27033 track down the second incarnation of bug 546.
27035 o Minor features (bridges):
27036 - If bridge users set UpdateBridgesFromAuthority, but the digest
27037 they ask for is a 404 from the bridge authority, they now fall
27038 back to trying the bridge directly.
27039 - Bridges now use begin_dir to publish their server descriptor to
27040 the bridge authority, even when they haven't set TunnelDirConns.
27042 o Minor features (controller):
27043 - When reporting clock skew, and we know that the clock is _at least
27044 as skewed_ as some value, but we don't know the actual value,
27045 report the value as a "minimum skew."
27048 - Update linux-tor-prio.sh script to allow QoS based on the uid of
27049 the Tor process. Patch from Marco Bonetti with tweaks from Mike
27053 - Refuse to start if both ORPort and UseBridges are set. Bugfix
27054 on 0.2.0.x, suggested by Matt Edman.
27055 - Don't stop fetching descriptors when FetchUselessDescriptors is
27056 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
27057 reported by tup and ioerror.
27058 - Better log message on vote from unknown authority.
27059 - Don't log "Launching 0 request for 0 router" message.
27061 o Minor bugfixes (memory leaks):
27062 - Stop leaking memory every time we parse a v3 certificate. Bugfix
27064 - Stop leaking memory every time we load a v3 certificate. Bugfix
27065 on 0.2.0.1-alpha. Fixes bug 536.
27066 - Stop leaking a cached networkstatus on exit. Bugfix on
27068 - Stop leaking voter information every time we free a consensus.
27069 Bugfix on 0.2.0.3-alpha.
27070 - Stop leaking signed data every time we check a voter signature.
27071 Bugfix on 0.2.0.3-alpha.
27072 - Stop leaking a signature every time we fail to parse a consensus or
27073 a vote. Bugfix on 0.2.0.3-alpha.
27074 - Stop leaking v2_download_status_map on shutdown. Bugfix on
27076 - Stop leaking conn->nickname every time we make a connection to a
27077 Tor relay without knowing its expected identity digest (e.g. when
27078 using bridges). Bugfix on 0.2.0.3-alpha.
27080 - Minor bugfixes (portability):
27081 - Run correctly on platforms where rlim_t is larger than unsigned
27082 long, and/or where the real limit for number of open files is
27083 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
27084 particular, these may be needed for OS X 10.5.
27087 Changes in version 0.1.2.18 - 2007-10-28
27088 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
27089 hidden service introduction that were causing huge delays, and a big
27090 bug that was causing some servers to disappear from the network status
27091 lists for a few hours each day.
27093 o Major bugfixes (crashes):
27094 - If a connection is shut down abruptly because of something that
27095 happened inside connection_flushed_some(), do not call
27096 connection_finished_flushing(). Should fix bug 451:
27097 "connection_stop_writing: Assertion conn->write_event failed"
27098 Bugfix on 0.1.2.7-alpha.
27099 - Fix possible segfaults in functions called from
27100 rend_process_relay_cell().
27102 o Major bugfixes (hidden services):
27103 - Hidden services were choosing introduction points uniquely by
27104 hexdigest, but when constructing the hidden service descriptor
27105 they merely wrote the (potentially ambiguous) nickname.
27106 - Clients now use the v2 intro format for hidden service
27107 connections: they specify their chosen rendezvous point by identity
27108 digest rather than by (potentially ambiguous) nickname. These
27109 changes could speed up hidden service connections dramatically.
27111 o Major bugfixes (other):
27112 - Stop publishing a new server descriptor just because we get a
27113 HUP signal. This led (in a roundabout way) to some servers getting
27114 dropped from the networkstatus lists for a few hours each day.
27115 - When looking for a circuit to cannibalize, consider family as well
27116 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27117 circuit cannibalization).
27118 - When a router wasn't listed in a new networkstatus, we were leaving
27119 the flags for that router alone -- meaning it remained Named,
27120 Running, etc -- even though absence from the networkstatus means
27121 that it shouldn't be considered to exist at all anymore. Now we
27122 clear all the flags for routers that fall out of the networkstatus
27123 consensus. Fixes bug 529.
27126 - Don't try to access (or alter) the state file when running
27127 --list-fingerprint or --verify-config or --hash-password. Resolves
27129 - When generating information telling us how to extend to a given
27130 router, do not try to include the nickname if it is
27131 absent. Resolves bug 467.
27132 - Fix a user-triggerable segfault in expand_filename(). (There isn't
27133 a way to trigger this remotely.)
27134 - When sending a status event to the controller telling it that an
27135 OR address is reachable, set the port correctly. (Previously we
27136 were reporting the dir port.)
27137 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27138 command. Bugfix on 0.1.2.17.
27139 - When loading bandwidth history, do not believe any information in
27140 the future. Fixes bug 434.
27141 - When loading entry guard information, do not believe any information
27143 - When we have our clock set far in the future and generate an
27144 onion key, then re-set our clock to be correct, we should not stop
27145 the onion key from getting rotated.
27146 - On some platforms, accept() can return a broken address. Detect
27147 this more quietly, and deal accordingly. Fixes bug 483.
27148 - It's not actually an error to find a non-pending entry in the DNS
27149 cache when canceling a pending resolve. Don't log unless stuff
27150 is fishy. Resolves bug 463.
27151 - Don't reset trusted dir server list when we set a configuration
27152 option. Patch from Robert Hogan.
27153 - Don't try to create the datadir when running --verify-config or
27154 --hash-password. Resolves bug 540.
27157 Changes in version 0.2.0.9-alpha - 2007-10-24
27158 This ninth development snapshot switches clients to the new v3 directory
27159 system; allows servers to be listed in the network status even when they
27160 have the same nickname as a registered server; and fixes many other
27161 bugs including a big one that was causing some servers to disappear
27162 from the network status lists for a few hours each day.
27164 o Major features (directory system):
27165 - Clients now download v3 consensus networkstatus documents instead
27166 of v2 networkstatus documents. Clients and caches now base their
27167 opinions about routers on these consensus documents. Clients only
27168 download router descriptors listed in the consensus.
27169 - Authorities now list servers who have the same nickname as
27170 a different named server, but list them with a new flag,
27171 "Unnamed". Now we can list servers that happen to pick the same
27172 nickname as a server that registered two years ago and then
27173 disappeared. Partially implements proposal 122.
27174 - If the consensus lists a router as "Unnamed", the name is assigned
27175 to a different router: do not identify the router by that name.
27176 Partially implements proposal 122.
27177 - Authorities can now come to a consensus on which method to use to
27178 compute the consensus. This gives us forward compatibility.
27181 - Stop publishing a new server descriptor just because we HUP or
27182 when we find our DirPort to be reachable but won't actually publish
27183 it. New descriptors without any real changes are dropped by the
27184 authorities, and can screw up our "publish every 18 hours" schedule.
27186 - When a router wasn't listed in a new networkstatus, we were leaving
27187 the flags for that router alone -- meaning it remained Named,
27188 Running, etc -- even though absence from the networkstatus means
27189 that it shouldn't be considered to exist at all anymore. Now we
27190 clear all the flags for routers that fall out of the networkstatus
27191 consensus. Fixes bug 529; bugfix on 0.1.2.x.
27192 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
27193 extrainfo documents and then discard them immediately for not
27194 matching the latest router. Bugfix on 0.2.0.1-alpha.
27196 o Minor features (v3 directory protocol):
27197 - Allow tor-gencert to generate a new certificate without replacing
27199 - Allow certificates to include an address.
27200 - When we change our directory-cache settings, reschedule all voting
27201 and download operations.
27202 - Reattempt certificate downloads immediately on failure, as long as
27203 we haven't failed a threshold number of times yet.
27204 - Delay retrying consensus downloads while we're downloading
27205 certificates to verify the one we just got. Also, count getting a
27206 consensus that we already have (or one that isn't valid) as a failure,
27207 and count failing to get the certificates after 20 minutes as a
27209 - Build circuits and download descriptors even if our consensus is a
27210 little expired. (This feature will go away once authorities are
27213 o Minor features (router descriptor cache):
27214 - If we find a cached-routers file that's been sitting around for more
27215 than 28 days unmodified, then most likely it's a leftover from
27216 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
27218 - When we (as a cache) download a descriptor because it was listed
27219 in a consensus, remember when the consensus was supposed to expire,
27220 and don't expire the descriptor until then.
27222 o Minor features (performance):
27223 - Call routerlist_remove_old_routers() much less often. This should
27224 speed startup, especially on directory caches.
27225 - Don't try to launch new descriptor downloads quite so often when we
27226 already have enough directory information to build circuits.
27227 - Base64 decoding was actually showing up on our profile when parsing
27228 the initial descriptor file; switch to an in-process all-at-once
27229 implementation that's about 3.5x times faster than calling out to
27232 o Minor features (compilation):
27233 - Detect non-ASCII platforms (if any still exist) and refuse to
27234 build there: some of our code assumes that 'A' is 65 and so on.
27236 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
27237 - Make the "next period" votes into "current period" votes immediately
27238 after publishing the consensus; avoid a heisenbug that made them
27239 stick around indefinitely.
27240 - When we discard a vote as a duplicate, do not report this as
27242 - Treat missing v3 keys or certificates as an error when running as a
27243 v3 directory authority.
27244 - When we're configured to be a v3 authority, but we're only listed
27245 as a non-v3 authority in our DirServer line for ourself, correct
27247 - If an authority doesn't have a qualified hostname, just put
27248 its address in the vote. This fixes the problem where we referred to
27249 "moria on moria:9031."
27250 - Distinguish between detached signatures for the wrong period, and
27251 detached signatures for a divergent vote.
27252 - Fix a small memory leak when computing a consensus.
27253 - When there's no consensus, we were forming a vote every 30
27254 minutes, but writing the "valid-after" line in our vote based
27255 on our configured V3AuthVotingInterval: so unless the intervals
27256 matched up, we immediately rejected our own vote because it didn't
27257 start at the voting interval that caused us to construct a vote.
27259 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
27260 - Delete unverified-consensus when the real consensus is set.
27261 - Consider retrying a consensus networkstatus fetch immediately
27262 after one fails: don't wait 60 seconds to notice.
27263 - When fetching a consensus as a cache, wait until a newer consensus
27264 should exist before trying to replace the current one.
27265 - Use a more forgiving schedule for retrying failed consensus
27266 downloads than for other types.
27268 o Minor bugfixes (other directory issues):
27269 - Correct the implementation of "download votes by digest." Bugfix on
27271 - Authorities no longer send back "400 you're unreachable please fix
27272 it" errors to Tor servers that aren't online all the time. We're
27273 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
27275 o Minor bugfixes (controller):
27276 - Don't reset trusted dir server list when we set a configuration
27277 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
27278 - Respond to INT and TERM SIGNAL commands before we execute the
27279 signal, in case the signal shuts us down. We had a patch in
27280 0.1.2.1-alpha that tried to do this by queueing the response on
27281 the connection's buffer before shutting down, but that really
27282 isn't the same thing at all. Bug located by Matt Edman.
27284 o Minor bugfixes (misc):
27285 - Correctly check for bad options to the "PublishServerDescriptor"
27286 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
27287 - Stop leaking memory on failing case of base32_decode, and make
27288 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
27289 - Don't try to download extrainfo documents when we're trying to
27290 fetch enough directory info to build a circuit: having enough
27291 info should get priority. Bugfix on 0.2.0.x.
27292 - Don't complain that "your server has not managed to confirm that its
27293 ports are reachable" if we haven't been able to build any circuits
27294 yet. Bug found by spending four hours without a v3 consensus. Bugfix
27296 - Detect the reason for failing to mmap a descriptor file we just
27297 wrote, and give a more useful log message. Fixes bug 533. Bugfix
27300 o Code simplifications and refactoring:
27301 - Remove support for the old bw_accounting file: we've been storing
27302 bandwidth accounting information in the state file since
27303 0.1.2.5-alpha. This may result in bandwidth accounting errors
27304 if you try to upgrade from 0.1.1.x or earlier, or if you try to
27305 downgrade to 0.1.1.x or earlier.
27306 - New convenience code to locate a file within the DataDirectory.
27307 - Move non-authority functionality out of dirvote.c.
27308 - Refactor the arguments for router_pick_{directory_|trusteddir}server
27309 so that they all take the same named flags.
27312 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
27313 Unix users an easy way to script their Tor process (e.g. by
27314 adjusting bandwidth based on the time of the day).
27317 Changes in version 0.2.0.8-alpha - 2007-10-12
27318 This eighth development snapshot fixes a crash bug that's been bothering
27319 us since February 2007, lets bridge authorities store a list of bridge
27320 descriptors they've seen, gets v3 directory voting closer to working,
27321 starts caching v3 directory consensus documents on directory mirrors,
27322 and fixes a variety of smaller issues including some minor memory leaks.
27324 o Major features (router descriptor cache):
27325 - Store routers in a file called cached-descriptors instead of in
27326 cached-routers. Initialize cached-descriptors from cached-routers
27327 if the old format is around. The new format allows us to store
27328 annotations along with descriptors.
27329 - Use annotations to record the time we received each descriptor, its
27330 source, and its purpose.
27331 - Disable the SETROUTERPURPOSE controller command: it is now
27333 - Controllers should now specify cache=no or cache=yes when using
27334 the +POSTDESCRIPTOR command.
27335 - Bridge authorities now write bridge descriptors to disk, meaning
27336 we can export them to other programs and begin distributing them
27339 o Major features (directory authorities):
27340 - When a v3 authority is missing votes or signatures, it now tries
27342 - Directory authorities track weighted fractional uptime as well as
27343 weighted mean-time-between failures. WFU is suitable for deciding
27344 whether a node is "usually up", while MTBF is suitable for deciding
27345 whether a node is "likely to stay up." We need both, because
27346 "usually up" is a good requirement for guards, while "likely to
27347 stay up" is a good requirement for long-lived connections.
27349 o Major features (v3 directory system):
27350 - Caches now download v3 network status documents as needed,
27351 and download the descriptors listed in them.
27352 - All hosts now attempt to download and keep fresh v3 authority
27353 certificates, and re-attempt after failures.
27354 - More internal-consistency checks for vote parsing.
27356 o Major bugfixes (crashes):
27357 - If a connection is shut down abruptly because of something that
27358 happened inside connection_flushed_some(), do not call
27359 connection_finished_flushing(). Should fix bug 451. Bugfix on
27362 o Major bugfixes (performance):
27363 - Fix really bad O(n^2) performance when parsing a long list of
27364 routers: Instead of searching the entire list for an "extra-info "
27365 string which usually wasn't there, once for every routerinfo
27366 we read, just scan lines forward until we find one we like.
27368 - When we add data to a write buffer in response to the data on that
27369 write buffer getting low because of a flush, do not consider the
27370 newly added data as a candidate for immediate flushing, but rather
27371 make it wait until the next round of writing. Otherwise, we flush
27372 and refill recursively, and a single greedy TLS connection can
27373 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
27375 o Minor features (v3 authority system):
27376 - Add more ways for tools to download the votes that lead to the
27378 - Send a 503 when low on bandwidth and a vote, consensus, or
27379 certificate is requested.
27380 - If-modified-since is now implemented properly for all kinds of
27381 certificate requests.
27383 o Minor bugfixes (network statuses):
27384 - Tweak the implementation of proposal 109 slightly: allow at most
27385 two Tor servers on the same IP address, except if it's the location
27386 of a directory authority, in which case allow five. Bugfix on
27389 o Minor bugfixes (controller):
27390 - When sending a status event to the controller telling it that an
27391 OR address is reachable, set the port correctly. (Previously we
27392 were reporting the dir port.) Bugfix on 0.1.2.x.
27394 o Minor bugfixes (v3 directory system):
27395 - Fix logic to look up a cert by its signing key digest. Bugfix on
27397 - Only change the reply to a vote to "OK" if it's not already
27398 set. This gets rid of annoying "400 OK" log messages, which may
27399 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
27400 - When we get a valid consensus, recompute the voting schedule.
27401 - Base the valid-after time of a vote on the consensus voting
27402 schedule, not on our preferred schedule.
27403 - Make the return values and messages from signature uploads and
27404 downloads more sensible.
27405 - Fix a memory leak when serving votes and consensus documents, and
27406 another when serving certificates.
27408 o Minor bugfixes (performance):
27409 - Use a slightly simpler string hashing algorithm (copying Python's
27410 instead of Java's) and optimize our digest hashing algorithm to take
27411 advantage of 64-bit platforms and to remove some possibly-costly
27413 - Fix a minor memory leak whenever we parse guards from our state
27414 file. Bugfix on 0.2.0.7-alpha.
27415 - Fix a minor memory leak whenever we write out a file. Bugfix on
27417 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27418 command. Bugfix on 0.2.0.5-alpha.
27420 o Minor bugfixes (portability):
27421 - On some platforms, accept() can return a broken address. Detect
27422 this more quietly, and deal accordingly. Fixes bug 483.
27423 - Stop calling tor_strlower() on uninitialized memory in some cases.
27424 Bugfix in 0.2.0.7-alpha.
27426 o Minor bugfixes (usability):
27427 - Treat some 403 responses from directory servers as INFO rather than
27428 WARN-severity events.
27429 - It's not actually an error to find a non-pending entry in the DNS
27430 cache when canceling a pending resolve. Don't log unless stuff is
27431 fishy. Resolves bug 463.
27433 o Minor bugfixes (anonymity):
27434 - Never report that we've used more bandwidth than we're willing to
27435 relay: it leaks how much non-relay traffic we're using. Resolves
27437 - When looking for a circuit to cannibalize, consider family as well
27438 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27439 circuit cannibalization).
27441 o Code simplifications and refactoring:
27442 - Make a bunch of functions static. Remove some dead code.
27443 - Pull out about a third of the really big routerlist.c; put it in a
27444 new module, networkstatus.c.
27445 - Merge the extra fields in local_routerstatus_t back into
27446 routerstatus_t: we used to need one routerstatus_t for each
27447 authority's opinion, plus a local_routerstatus_t for the locally
27448 computed consensus opinion. To save space, we put the locally
27449 modified fields into local_routerstatus_t, and only the common
27450 stuff into routerstatus_t. But once v3 directories are in use,
27451 clients and caches will no longer need to hold authority opinions;
27452 thus, the rationale for keeping the types separate is now gone.
27453 - Make the code used to reschedule and reattempt downloads more
27455 - Turn all 'Are we a directory server/mirror?' logic into a call to
27457 - Remove the code to generate the oldest (v1) directory format.
27458 The code has been disabled since 0.2.0.5-alpha.
27461 Changes in version 0.2.0.7-alpha - 2007-09-21
27462 This seventh development snapshot makes bridges work again, makes bridge
27463 authorities work for the first time, fixes two huge performance flaws
27464 in hidden services, and fixes a variety of minor issues.
27466 o New directory authorities:
27467 - Set up moria1 and tor26 as the first v3 directory authorities. See
27468 doc/spec/dir-spec.txt for details on the new directory design.
27470 o Major bugfixes (crashes):
27471 - Fix possible segfaults in functions called from
27472 rend_process_relay_cell(). Bugfix on 0.1.2.x.
27474 o Major bugfixes (bridges):
27475 - Fix a bug that made servers send a "404 Not found" in response to
27476 attempts to fetch their server descriptor. This caused Tor servers
27477 to take many minutes to establish reachability for their DirPort,
27478 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
27479 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
27480 users configure that and specify a bridge with an identity
27481 fingerprint, now they will lookup the bridge descriptor at the
27482 default bridge authority via a one-hop tunnel, but once circuits
27483 are established they will switch to a three-hop tunnel for later
27484 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
27486 o Major bugfixes (hidden services):
27487 - Hidden services were choosing introduction points uniquely by
27488 hexdigest, but when constructing the hidden service descriptor
27489 they merely wrote the (potentially ambiguous) nickname.
27490 - Clients now use the v2 intro format for hidden service
27491 connections: they specify their chosen rendezvous point by identity
27492 digest rather than by (potentially ambiguous) nickname. Both
27493 are bugfixes on 0.1.2.x, and they could speed up hidden service
27494 connections dramatically. Thanks to Karsten Loesing.
27496 o Minor features (security):
27497 - As a client, do not believe any server that tells us that an
27498 address maps to an internal address space.
27499 - Make it possible to enable HashedControlPassword and
27500 CookieAuthentication at the same time.
27502 o Minor features (guard nodes):
27503 - Tag every guard node in our state file with the version that
27504 we believe added it, or with our own version if we add it. This way,
27505 if a user temporarily runs an old version of Tor and then switches
27506 back to a new one, she doesn't automatically lose her guards.
27508 o Minor features (speed):
27509 - When implementing AES counter mode, update only the portions of the
27510 counter buffer that need to change, and don't keep separate
27511 network-order and host-order counters when they are the same (i.e.,
27512 on big-endian hosts.)
27514 o Minor features (controller):
27515 - Accept LF instead of CRLF on controller, since some software has a
27516 hard time generating real Internet newlines.
27517 - Add GETINFO values for the server status events
27518 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
27521 o Removed features:
27522 - Routers no longer include bandwidth-history lines in their
27523 descriptors; this information is already available in extra-info
27524 documents, and including it in router descriptors took up 60%
27525 (!) of compressed router descriptor downloads. Completes
27526 implementation of proposal 104.
27527 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
27528 and TorControl.py, as they use the old v0 controller protocol,
27529 and are obsoleted by TorFlow anyway.
27530 - Drop support for v1 rendezvous descriptors, since we never used
27531 them anyway, and the code has probably rotted by now. Based on
27532 patch from Karsten Loesing.
27533 - On OSX, stop warning the user that kqueue support in libevent is
27534 "experimental", since it seems to have worked fine for ages.
27537 - When generating information telling us how to extend to a given
27538 router, do not try to include the nickname if it is absent. Fixes
27539 bug 467. Bugfix on 0.2.0.3-alpha.
27540 - Fix a user-triggerable (but not remotely-triggerable) segfault
27541 in expand_filename(). Bugfix on 0.1.2.x.
27542 - Fix a memory leak when freeing incomplete requests from DNSPort.
27543 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
27544 - Don't try to access (or alter) the state file when running
27545 --list-fingerprint or --verify-config or --hash-password. (Resolves
27546 bug 499.) Bugfix on 0.1.2.x.
27547 - Servers used to decline to publish their DirPort if their
27548 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
27549 were below a threshold. Now they only look at BandwidthRate and
27550 RelayBandwidthRate. Bugfix on 0.1.2.x.
27551 - Remove an optimization in the AES counter-mode code that assumed
27552 that the counter never exceeded 2^68. When the counter can be set
27553 arbitrarily as an IV (as it is by Karsten's new hidden services
27554 code), this assumption no longer holds. Bugfix on 0.1.2.x.
27555 - Resume listing "AUTHORITY" flag for authorities in network status.
27556 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
27558 o Code simplifications and refactoring:
27559 - Revamp file-writing logic so we don't need to have the entire
27560 contents of a file in memory at once before we write to disk. Tor,
27562 - Turn "descriptor store" into a full-fledged type.
27563 - Move all NT services code into a separate source file.
27564 - Unify all code that computes medians, percentile elements, etc.
27565 - Get rid of a needless malloc when parsing address policies.
27568 Changes in version 0.1.2.17 - 2007-08-30
27569 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
27570 X bundles. Vidalia 0.0.14 makes authentication required for the
27571 ControlPort in the default configuration, which addresses important
27572 security risks. Everybody who uses Vidalia (or another controller)
27575 In addition, this Tor update fixes major load balancing problems with
27576 path selection, which should speed things up a lot once many people
27579 o Major bugfixes (security):
27580 - We removed support for the old (v0) control protocol. It has been
27581 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
27582 become more of a headache than it's worth.
27584 o Major bugfixes (load balancing):
27585 - When choosing nodes for non-guard positions, weight guards
27586 proportionally less, since they already have enough load. Patch
27588 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27589 will allow fast Tor servers to get more attention.
27590 - When we're upgrading from an old Tor version, forget our current
27591 guards and pick new ones according to the new weightings. These
27592 three load balancing patches could raise effective network capacity
27593 by a factor of four. Thanks to Mike Perry for measurements.
27595 o Major bugfixes (stream expiration):
27596 - Expire not-yet-successful application streams in all cases if
27597 they've been around longer than SocksTimeout. Right now there are
27598 some cases where the stream will live forever, demanding a new
27599 circuit every 15 seconds. Fixes bug 454; reported by lodger.
27601 o Minor features (controller):
27602 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27603 is valid before any authentication has been received. It tells
27604 a controller what kind of authentication is expected, and what
27605 protocol is spoken. Implements proposal 119.
27607 o Minor bugfixes (performance):
27608 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
27609 greatly speeding up loading cached-routers from disk on startup.
27610 - Disable sentinel-based debugging for buffer code: we squashed all
27611 the bugs that this was supposed to detect a long time ago, and now
27612 its only effect is to change our buffer sizes from nice powers of
27613 two (which platform mallocs tend to like) to values slightly over
27614 powers of two (which make some platform mallocs sad).
27616 o Minor bugfixes (misc):
27617 - If exit bandwidth ever exceeds one third of total bandwidth, then
27618 use the correct formula to weight exit nodes when choosing paths.
27619 Based on patch from Mike Perry.
27620 - Choose perfectly fairly among routers when choosing by bandwidth and
27621 weighting by fraction of bandwidth provided by exits. Previously, we
27622 would choose with only approximate fairness, and correct ourselves
27623 if we ran off the end of the list.
27624 - If we require CookieAuthentication but we fail to write the
27625 cookie file, we would warn but not exit, and end up in a state
27626 where no controller could authenticate. Now we exit.
27627 - If we require CookieAuthentication, stop generating a new cookie
27628 every time we change any piece of our config.
27629 - Refuse to start with certain directory authority keys, and
27630 encourage people using them to stop.
27631 - Terminate multi-line control events properly. Original patch
27633 - Fix a minor memory leak when we fail to find enough suitable
27634 servers to choose a circuit.
27635 - Stop leaking part of the descriptor when we run into a particularly
27636 unparseable piece of it.
27639 Changes in version 0.2.0.6-alpha - 2007-08-26
27640 This sixth development snapshot features a new Vidalia version in the
27641 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
27642 the ControlPort in the default configuration, which addresses important
27645 In addition, this snapshot fixes major load balancing problems
27646 with path selection, which should speed things up a lot once many
27647 people have upgraded. The directory authorities also use a new
27648 mean-time-between-failure approach to tracking which servers are stable,
27649 rather than just looking at the most recent uptime.
27651 o New directory authorities:
27652 - Set up Tonga as the default bridge directory authority.
27655 - Directory authorities now track servers by weighted
27656 mean-times-between-failures. When we have 4 or more days of data,
27657 use measured MTBF rather than declared uptime to decide whether
27658 to call a router Stable. Implements proposal 108.
27660 o Major bugfixes (load balancing):
27661 - When choosing nodes for non-guard positions, weight guards
27662 proportionally less, since they already have enough load. Patch
27664 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27665 will allow fast Tor servers to get more attention.
27666 - When we're upgrading from an old Tor version, forget our current
27667 guards and pick new ones according to the new weightings. These
27668 three load balancing patches could raise effective network capacity
27669 by a factor of four. Thanks to Mike Perry for measurements.
27671 o Major bugfixes (descriptor parsing):
27672 - Handle unexpected whitespace better in malformed descriptors. Bug
27673 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
27676 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
27677 GETINFO for Torstat to use until it can switch to using extrainfos.
27678 - Optionally (if built with -DEXPORTMALLINFO) export the output
27679 of mallinfo via http, as tor/mallinfo.txt. Only accessible
27683 - Do not intermix bridge routers with controller-added
27684 routers. (Bugfix on 0.2.0.x)
27685 - Do not fail with an assert when accept() returns an unexpected
27686 address family. Addresses but does not wholly fix bug 483. (Bugfix
27688 - Let directory authorities startup even when they can't generate
27689 a descriptor immediately, e.g. because they don't know their
27691 - Stop putting the authentication cookie in a file called "0"
27692 in your working directory if you don't specify anything for the
27693 new CookieAuthFile option. Reported by Matt Edman.
27694 - Make it possible to read the PROTOCOLINFO response in a way that
27695 conforms to our control-spec. Reported by Matt Edman.
27696 - Fix a minor memory leak when we fail to find enough suitable
27697 servers to choose a circuit. Bugfix on 0.1.2.x.
27698 - Stop leaking part of the descriptor when we run into a particularly
27699 unparseable piece of it. Bugfix on 0.1.2.x.
27700 - Unmap the extrainfo cache file on exit.
27703 Changes in version 0.2.0.5-alpha - 2007-08-19
27704 This fifth development snapshot fixes compilation on Windows again;
27705 fixes an obnoxious client-side bug that slowed things down and put
27706 extra load on the network; gets us closer to using the v3 directory
27707 voting scheme; makes it easier for Tor controllers to use cookie-based
27708 authentication; and fixes a variety of other bugs.
27710 o Removed features:
27711 - Version 1 directories are no longer generated in full. Instead,
27712 authorities generate and serve "stub" v1 directories that list
27713 no servers. This will stop Tor versions 0.1.0.x and earlier from
27714 working, but (for security reasons) nobody should be running those
27717 o Major bugfixes (compilation, 0.2.0.x):
27718 - Try to fix Win32 compilation again: improve checking for IPv6 types.
27719 - Try to fix MSVC compilation: build correctly on platforms that do
27720 not define s6_addr16 or s6_addr32.
27721 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
27724 o Major bugfixes (stream expiration):
27725 - Expire not-yet-successful application streams in all cases if
27726 they've been around longer than SocksTimeout. Right now there are
27727 some cases where the stream will live forever, demanding a new
27728 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
27729 reported by lodger.
27731 o Minor features (directory servers):
27732 - When somebody requests a list of statuses or servers, and we have
27733 none of those, return a 404 rather than an empty 200.
27735 o Minor features (directory voting):
27736 - Store v3 consensus status consensuses on disk, and reload them
27739 o Minor features (security):
27740 - Warn about unsafe ControlPort configurations.
27741 - Refuse to start with certain directory authority keys, and
27742 encourage people using them to stop.
27744 o Minor features (controller):
27745 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27746 is valid before any authentication has been received. It tells
27747 a controller what kind of authentication is expected, and what
27748 protocol is spoken. Implements proposal 119.
27749 - New config option CookieAuthFile to choose a new location for the
27750 cookie authentication file, and config option
27751 CookieAuthFileGroupReadable to make it group-readable.
27753 o Minor features (unit testing):
27754 - Add command-line arguments to unit-test executable so that we can
27755 invoke any chosen test from the command line rather than having
27756 to run the whole test suite at once; and so that we can turn on
27757 logging for the unit tests.
27759 o Minor bugfixes (on 0.1.2.x):
27760 - If we require CookieAuthentication but we fail to write the
27761 cookie file, we would warn but not exit, and end up in a state
27762 where no controller could authenticate. Now we exit.
27763 - If we require CookieAuthentication, stop generating a new cookie
27764 every time we change any piece of our config.
27765 - When loading bandwidth history, do not believe any information in
27766 the future. Fixes bug 434.
27767 - When loading entry guard information, do not believe any information
27769 - When we have our clock set far in the future and generate an
27770 onion key, then re-set our clock to be correct, we should not stop
27771 the onion key from getting rotated.
27772 - Clean up torrc sample config file.
27773 - Do not automatically run configure from autogen.sh. This
27774 non-standard behavior tended to annoy people who have built other
27777 o Minor bugfixes (on 0.2.0.x):
27778 - Fix a bug with AutomapHostsOnResolve that would always cause
27779 the second request to fail. Bug reported by Kate. Bugfix on
27781 - Fix a bug in ADDRMAP controller replies that would sometimes
27782 try to print a NULL. Patch from tup.
27783 - Read v3 directory authority keys from the right location.
27784 - Numerous bugfixes to directory voting code.
27787 Changes in version 0.1.2.16 - 2007-08-01
27788 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
27789 remote attacker in certain situations to rewrite the user's torrc
27790 configuration file. This can completely compromise anonymity of users
27791 in most configurations, including those running the Vidalia bundles,
27792 TorK, etc. Or worse.
27794 o Major security fixes:
27795 - Close immediately after missing authentication on control port;
27796 do not allow multiple authentication attempts.
27799 Changes in version 0.2.0.4-alpha - 2007-08-01
27800 This fourth development snapshot fixes a critical security vulnerability
27801 for most users, specifically those running Vidalia, TorK, etc. Everybody
27802 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
27804 o Major security fixes:
27805 - Close immediately after missing authentication on control port;
27806 do not allow multiple authentication attempts.
27808 o Major bugfixes (compilation):
27809 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
27812 o Minor features (performance):
27813 - Be even more aggressive about releasing RAM from small
27814 empty buffers. Thanks to our free-list code, this shouldn't be too
27815 performance-intensive.
27816 - Disable sentinel-based debugging for buffer code: we squashed all
27817 the bugs that this was supposed to detect a long time ago, and
27818 now its only effect is to change our buffer sizes from nice
27819 powers of two (which platform mallocs tend to like) to values
27820 slightly over powers of two (which make some platform mallocs sad).
27821 - Log malloc statistics from mallinfo() on platforms where it
27825 Changes in version 0.2.0.3-alpha - 2007-07-29
27826 This third development snapshot introduces new experimental
27827 blocking-resistance features and a preliminary version of the v3
27828 directory voting design, and includes many other smaller features
27832 - The first pieces of our "bridge" design for blocking-resistance
27833 are implemented. People can run bridge directory authorities;
27834 people can run bridges; and people can configure their Tor clients
27835 with a set of bridges to use as the first hop into the Tor network.
27836 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
27838 - Create listener connections before we setuid to the configured
27839 User and Group. Now non-Windows users can choose port values
27840 under 1024, start Tor as root, and have Tor bind those ports
27841 before it changes to another UID. (Windows users could already
27843 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
27844 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
27845 on "vserver" accounts. (Patch from coderman.)
27846 - Be even more aggressive about separating local traffic from relayed
27847 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
27849 o Major features (experimental):
27850 - First cut of code for "v3 dir voting": directory authorities will
27851 vote on a common network status document rather than each publishing
27852 their own opinion. This code needs more testing and more corner-case
27853 handling before it's ready for use.
27856 - Directory authorities now call routers Fast if their bandwidth is
27857 at least 100KB/s, and consider their bandwidth adequate to be a
27858 Guard if it is at least 250KB/s, no matter the medians. This fix
27859 complements proposal 107. [Bugfix on 0.1.2.x]
27860 - Directory authorities now never mark more than 3 servers per IP as
27861 Valid and Running. (Implements proposal 109, by Kevin Bauer and
27863 - Minor change to organizationName and commonName generation
27864 procedures in TLS certificates during Tor handshakes, to invalidate
27865 some earlier censorware approaches. This is not a long-term
27866 solution, but applying it will give us a bit of time to look into
27867 the epidemiology of countermeasures as they spread.
27869 o Major bugfixes (directory):
27870 - Rewrite directory tokenization code to never run off the end of
27871 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
27873 o Minor features (controller):
27874 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
27875 match requests to applications. (Patch from Robert Hogan.)
27876 - Report address and port correctly on connections to DNSPort. (Patch
27877 from Robert Hogan.)
27878 - Add a RESOLVE command to launch hostname lookups. (Original patch
27879 from Robert Hogan.)
27880 - Add GETINFO status/enough-dir-info to let controllers tell whether
27881 Tor has downloaded sufficient directory information. (Patch
27883 - You can now use the ControlSocket option to tell Tor to listen for
27884 controller connections on Unix domain sockets on systems that
27885 support them. (Patch from Peter Palfrader.)
27886 - STREAM NEW events are generated for DNSPort requests and for
27887 tunneled directory connections. (Patch from Robert Hogan.)
27888 - New "GETINFO address-mappings/*" command to get address mappings
27889 with expiry information. "addr-mappings/*" is now deprecated.
27892 o Minor features (misc):
27893 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
27895 - The tor-gencert tool for v3 directory authorities now creates all
27896 files as readable to the file creator only, and write-protects
27897 the authority identity key.
27898 - When dumping memory usage, list bytes used in buffer memory
27900 - When running with dmalloc, dump more stats on hup and on exit.
27901 - Directory authorities now fail quickly and (relatively) harmlessly
27902 if they generate a network status document that is somehow
27905 o Traffic load balancing improvements:
27906 - If exit bandwidth ever exceeds one third of total bandwidth, then
27907 use the correct formula to weight exit nodes when choosing paths.
27908 (Based on patch from Mike Perry.)
27909 - Choose perfectly fairly among routers when choosing by bandwidth and
27910 weighting by fraction of bandwidth provided by exits. Previously, we
27911 would choose with only approximate fairness, and correct ourselves
27912 if we ran off the end of the list. [Bugfix on 0.1.2.x]
27914 o Performance improvements:
27915 - Be more aggressive with freeing buffer RAM or putting it on the
27917 - Use Critical Sections rather than Mutexes for synchronizing threads
27918 on win32; Mutexes are heavier-weight, and designed for synchronizing
27921 o Deprecated and removed features:
27922 - RedirectExits is now deprecated.
27923 - Stop allowing address masks that do not correspond to bit prefixes.
27924 We have warned about these for a really long time; now it's time
27925 to reject them. (Patch from croup.)
27927 o Minor bugfixes (directory):
27928 - Fix another crash bug related to extra-info caching. (Bug found by
27929 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
27930 - Directories no longer return a "304 not modified" when they don't
27931 have the networkstatus the client asked for. Also fix a memory
27932 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
27933 - We had accidentally labelled 0.1.2.x directory servers as not
27934 suitable for begin_dir requests, and had labelled no directory
27935 servers as suitable for uploading extra-info documents. [Bugfix
27938 o Minor bugfixes (dns):
27939 - Fix a crash when DNSPort is set more than once. (Patch from Robert
27940 Hogan.) [Bugfix on 0.2.0.2-alpha]
27941 - Add DNSPort connections to the global connection list, so that we
27942 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
27944 - Fix a dangling reference that could lead to a crash when DNSPort is
27945 changed or closed (Patch from Robert Hogan.) [Bugfix on
27948 o Minor bugfixes (controller):
27949 - Provide DNS expiry times in GMT, not in local time. For backward
27950 compatibility, ADDRMAP events only provide GMT expiry in an extended
27951 field. "GETINFO address-mappings" always does the right thing.
27952 - Use CRLF line endings properly in NS events.
27953 - Terminate multi-line control events properly. (Original patch
27954 from tup.) [Bugfix on 0.1.2.x-alpha]
27955 - Do not include spaces in SOURCE_ADDR fields in STREAM
27956 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
27959 Changes in version 0.1.2.15 - 2007-07-17
27960 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
27961 problems, fixes compilation on BSD, and fixes a variety of other
27962 bugs. Everybody should upgrade.
27964 o Major bugfixes (compilation):
27965 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
27967 o Major bugfixes (crashes):
27968 - Try even harder not to dereference the first character after
27969 an mmap(). Reported by lodger.
27970 - Fix a crash bug in directory authorities when we re-number the
27971 routerlist while inserting a new router.
27972 - When the cached-routers file is an even multiple of the page size,
27973 don't run off the end and crash. (Fixes bug 455; based on idea
27975 - Fix eventdns.c behavior on Solaris: It is critical to include
27976 orconfig.h _before_ sys/types.h, so that we can get the expected
27977 definition of _FILE_OFFSET_BITS.
27979 o Major bugfixes (security):
27980 - Fix a possible buffer overrun when using BSD natd support. Bug
27982 - When sending destroy cells from a circuit's origin, don't include
27983 the reason for tearing down the circuit. The spec says we didn't,
27984 and now we actually don't. Reported by lodger.
27985 - Keep streamids from different exits on a circuit separate. This
27986 bug may have allowed other routers on a given circuit to inject
27987 cells into streams. Reported by lodger; fixes bug 446.
27988 - If there's a never-before-connected-to guard node in our list,
27989 never choose any guards past it. This way we don't expand our
27990 guard list unless we need to.
27992 o Minor bugfixes (guard nodes):
27993 - Weight guard selection by bandwidth, so that low-bandwidth nodes
27994 don't get overused as guards.
27996 o Minor bugfixes (directory):
27997 - Correctly count the number of authorities that recommend each
27998 version. Previously, we were under-counting by 1.
27999 - Fix a potential crash bug when we load many server descriptors at
28000 once and some of them make others of them obsolete. Fixes bug 458.
28002 o Minor bugfixes (hidden services):
28003 - Stop tearing down the whole circuit when the user asks for a
28004 connection to a port that the hidden service didn't configure.
28007 o Minor bugfixes (misc):
28008 - On Windows, we were preventing other processes from reading
28009 cached-routers while Tor was running. Reported by janbar.
28010 - Fix a possible (but very unlikely) bug in picking routers by
28011 bandwidth. Add a log message to confirm that it is in fact
28012 unlikely. Patch from lodger.
28013 - Backport a couple of memory leak fixes.
28014 - Backport miscellaneous cosmetic bugfixes.
28017 Changes in version 0.2.0.2-alpha - 2007-06-02
28018 o Major bugfixes on 0.2.0.1-alpha:
28019 - Fix an assertion failure related to servers without extra-info digests.
28020 Resolves bugs 441 and 442.
28022 o Minor features (directory):
28023 - Support "If-Modified-Since" when answering HTTP requests for
28024 directories, running-routers documents, and network-status documents.
28025 (There's no need to support it for router descriptors, since those
28026 are downloaded by descriptor digest.)
28028 o Minor build issues:
28029 - Clear up some MIPSPro compiler warnings.
28030 - When building from a tarball on a machine that happens to have SVK
28031 installed, report the micro-revision as whatever version existed
28032 in the tarball, not as "x".
28035 Changes in version 0.2.0.1-alpha - 2007-06-01
28036 This early development snapshot provides new features for people running
28037 Tor as both a client and a server (check out the new RelayBandwidth
28038 config options); lets Tor run as a DNS proxy; and generally moves us
28039 forward on a lot of fronts.
28041 o Major features, server usability:
28042 - New config options RelayBandwidthRate and RelayBandwidthBurst:
28043 a separate set of token buckets for relayed traffic. Right now
28044 relayed traffic is defined as answers to directory requests, and
28045 OR connections that don't have any local circuits on them.
28047 o Major features, client usability:
28048 - A client-side DNS proxy feature to replace the need for
28049 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
28050 for DNS requests on port 9999, use the Tor network to resolve them
28051 anonymously, and send the reply back like a regular DNS server.
28052 The code still only implements a subset of DNS.
28053 - Make PreferTunneledDirConns and TunnelDirConns work even when
28054 we have no cached directory info. This means Tor clients can now
28055 do all of their connections protected by TLS.
28057 o Major features, performance and efficiency:
28058 - Directory authorities accept and serve "extra info" documents for
28059 routers. These documents contain fields from router descriptors
28060 that aren't usually needed, and that use a lot of excess
28061 bandwidth. Once these fields are removed from router descriptors,
28062 the bandwidth savings should be about 60%. [Partially implements
28064 - Servers upload extra-info documents to any authority that accepts
28065 them. Authorities (and caches that have been configured to download
28066 extra-info documents) download them as needed. [Partially implements
28068 - Change the way that Tor buffers data that it is waiting to write.
28069 Instead of queueing data cells in an enormous ring buffer for each
28070 client->OR or OR->OR connection, we now queue cells on a separate
28071 queue for each circuit. This lets us use less slack memory, and
28072 will eventually let us be smarter about prioritizing different kinds
28074 - Use memory pools to allocate cells with better speed and memory
28075 efficiency, especially on platforms where malloc() is inefficient.
28076 - Stop reading on edge connections when their corresponding circuit
28077 buffers are full; start again as the circuits empty out.
28079 o Major features, other:
28080 - Add an HSAuthorityRecordStats option that hidden service authorities
28081 can use to track statistics of overall hidden service usage without
28082 logging information that would be very useful to an attacker.
28083 - Start work implementing multi-level keys for directory authorities:
28084 Add a standalone tool to generate key certificates. (Proposal 103.)
28087 - Directory authorities now call routers Stable if they have an
28088 uptime of at least 30 days, even if that's not the median uptime
28089 in the network. Implements proposal 107, suggested by Kevin Bauer
28092 o Minor fixes (resource management):
28093 - Count the number of open sockets separately from the number
28094 of active connection_t objects. This will let us avoid underusing
28095 our allocated connection limit.
28096 - We no longer use socket pairs to link an edge connection to an
28097 anonymous directory connection or a DirPort test connection.
28098 Instead, we track the link internally and transfer the data
28099 in-process. This saves two sockets per "linked" connection (at the
28100 client and at the server), and avoids the nasty Windows socketpair()
28102 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
28103 for every single inactive connection_t. Free items from the
28104 4k/16k-buffer free lists when they haven't been used for a while.
28106 o Minor features (build):
28107 - Make autoconf search for libevent, openssl, and zlib consistently.
28108 - Update deprecated macros in configure.in.
28109 - When warning about missing headers, tell the user to let us
28110 know if the compile succeeds anyway, so we can downgrade the
28112 - Include the current subversion revision as part of the version
28113 string: either fetch it directly if we're in an SVN checkout, do
28114 some magic to guess it if we're in an SVK checkout, or use
28115 the last-detected version if we're building from a .tar.gz.
28116 Use this version consistently in log messages.
28118 o Minor features (logging):
28119 - Always prepend "Bug: " to any log message about a bug.
28120 - Put a platform string (e.g. "Linux i686") in the startup log
28121 message, so when people paste just their logs, we know if it's
28122 OpenBSD or Windows or what.
28123 - When logging memory usage, break down memory used in buffers by
28126 o Minor features (directory system):
28127 - New config option V2AuthoritativeDirectory that all directory
28128 authorities should set. This will let future authorities choose
28129 not to serve V2 directory information.
28130 - Directory authorities allow multiple router descriptors and/or extra
28131 info documents to be uploaded in a single go. This will make
28132 implementing proposal 104 simpler.
28134 o Minor features (controller):
28135 - Add a new config option __DisablePredictedCircuits designed for
28136 use by the controller, when we don't want Tor to build any circuits
28138 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
28139 so we can exit from the middle of the circuit.
28140 - Implement "getinfo status/circuit-established".
28141 - Implement "getinfo status/version/..." so a controller can tell
28142 whether the current version is recommended, and whether any versions
28143 are good, and how many authorities agree. (Patch from shibz.)
28145 o Minor features (hidden services):
28146 - Allow multiple HiddenServicePort directives with the same virtual
28147 port; when they occur, the user is sent round-robin to one
28148 of the target ports chosen at random. Partially fixes bug 393 by
28149 adding limited ad-hoc round-robining.
28151 o Minor features (other):
28153 - Add a new AutomapHostsOnResolve option: when it is enabled, any
28154 resolve request for hosts matching a given pattern causes Tor to
28155 generate an internal virtual address mapping for that host. This
28156 allows DNSPort to work sensibly with hidden service users. By
28157 default, .exit and .onion addresses are remapped; the list of
28158 patterns can be reconfigured with AutomapHostsSuffixes.
28159 - Add an "-F" option to tor-resolve to force a resolve for a .onion
28160 address. Thanks to the AutomapHostsOnResolve option, this is no
28161 longer a completely silly thing to do.
28162 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
28163 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
28164 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
28165 minus 1 byte: the actual maximum declared bandwidth.
28167 o Removed features:
28168 - Removed support for the old binary "version 0" controller protocol.
28169 This has been deprecated since 0.1.1, and warnings have been issued
28170 since 0.1.2. When we encounter a v0 control message, we now send
28171 back an error and close the connection.
28172 - Remove the old "dns worker" server DNS code: it hasn't been default
28173 since 0.1.2.2-alpha, and all the servers seem to be using the new
28176 o Minor bugfixes (portability):
28177 - Even though Windows is equally happy with / and \ as path separators,
28178 try to use \ consistently on Windows and / consistently on Unix: it
28179 makes the log messages nicer.
28180 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
28181 - Read resolv.conf files correctly on platforms where read() returns
28182 partial results on small file reads.
28184 o Minor bugfixes (directory):
28185 - Correctly enforce that elements of directory objects do not appear
28186 more often than they are allowed to appear.
28187 - When we are reporting the DirServer line we just parsed, we were
28188 logging the second stanza of the key fingerprint, not the first.
28190 o Minor bugfixes (logging):
28191 - When we hit an EOF on a log (probably because we're shutting down),
28192 don't try to remove the log from the list: just mark it as
28193 unusable. (Bulletproofs against bug 222.)
28195 o Minor bugfixes (other):
28196 - In the exitlist script, only consider the most recently published
28197 server descriptor for each server. Also, when the user requests
28198 a list of servers that _reject_ connections to a given address,
28199 explicitly exclude the IPs that also have servers that accept
28200 connections to that address. (Resolves bug 405.)
28201 - Stop allowing hibernating servers to be "stable" or "fast".
28202 - On Windows, we were preventing other processes from reading
28203 cached-routers while Tor was running. (Reported by janbar)
28204 - Make the NodeFamilies config option work. (Reported by
28205 lodger -- it has never actually worked, even though we added it
28207 - Check return values from pthread_mutex functions.
28208 - Don't save non-general-purpose router descriptors to the disk cache,
28209 because we have no way of remembering what their purpose was when
28211 - Add even more asserts to hunt down bug 417.
28212 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
28213 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
28214 Add a log message to confirm that it is in fact unlikely.
28216 o Minor bugfixes (controller):
28217 - Make 'getinfo fingerprint' return a 551 error if we're not a
28218 server, so we match what the control spec claims we do. Reported
28220 - Fix a typo in an error message when extendcircuit fails that
28221 caused us to not follow the \r\n-based delimiter protocol. Reported
28224 o Code simplifications and refactoring:
28225 - Stop passing around circuit_t and crypt_path_t pointers that are
28226 implicit in other procedure arguments.
28227 - Drop the old code to choke directory connections when the
28228 corresponding OR connections got full: thanks to the cell queue
28229 feature, OR conns don't get full any more.
28230 - Make dns_resolve() handle attaching connections to circuits
28231 properly, so the caller doesn't have to.
28232 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
28233 - Keep the connection array as a dynamic smartlist_t, rather than as
28234 a fixed-sized array. This is important, as the number of connections
28235 is becoming increasingly decoupled from the number of sockets.
28238 Changes in version 0.1.2.14 - 2007-05-25
28239 Tor 0.1.2.14 changes the addresses of two directory authorities (this
28240 change especially affects those who serve or use hidden services),
28241 and fixes several other crash- and security-related bugs.
28243 o Directory authority changes:
28244 - Two directory authorities (moria1 and moria2) just moved to new
28245 IP addresses. This change will particularly affect those who serve
28246 or use hidden services.
28248 o Major bugfixes (crashes):
28249 - If a directory server runs out of space in the connection table
28250 as it's processing a begin_dir request, it will free the exit stream
28251 but leave it attached to the circuit, leading to unpredictable
28252 behavior. (Reported by seeess, fixes bug 425.)
28253 - Fix a bug in dirserv_remove_invalid() that would cause authorities
28254 to corrupt memory under some really unlikely scenarios.
28255 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
28256 - Avoid segfaults when reading from mmaped descriptor file. (Reported
28259 o Major bugfixes (security):
28260 - When choosing an entry guard for a circuit, avoid using guards
28261 that are in the same family as the chosen exit -- not just guards
28262 that are exactly the chosen exit. (Reported by lodger.)
28264 o Major bugfixes (resource management):
28265 - If a directory authority is down, skip it when deciding where to get
28266 networkstatus objects or descriptors. Otherwise we keep asking
28267 every 10 seconds forever. Fixes bug 384.
28268 - Count it as a failure if we fetch a valid network-status but we
28269 don't want to keep it. Otherwise we'll keep fetching it and keep
28270 not wanting to keep it. Fixes part of bug 422.
28271 - If all of our dirservers have given us bad or no networkstatuses
28272 lately, then stop hammering them once per minute even when we
28273 think they're failed. Fixes another part of bug 422.
28276 - Actually set the purpose correctly for descriptors inserted with
28277 purpose=controller.
28278 - When we have k non-v2 authorities in our DirServer config,
28279 we ignored the last k authorities in the list when updating our
28281 - Correctly back-off from requesting router descriptors that we are
28282 having a hard time downloading.
28283 - Read resolv.conf files correctly on platforms where read() returns
28284 partial results on small file reads.
28285 - Don't rebuild the entire router store every time we get 32K of
28286 routers: rebuild it when the journal gets very large, or when
28287 the gaps in the store get very large.
28290 - When routers publish SVN revisions in their router descriptors,
28291 authorities now include those versions correctly in networkstatus
28293 - Warn when using a version of libevent before 1.3b to run a server on
28294 OSX or BSD: these versions interact badly with userspace threads.
28297 Changes in version 0.1.2.13 - 2007-04-24
28298 This release features some major anonymity fixes, such as safer path
28299 selection; better client performance; faster bootstrapping, better
28300 address detection, and better DNS support for servers; write limiting as
28301 well as read limiting to make servers easier to run; and a huge pile of
28302 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
28304 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
28305 of the Freenode IRC network, remembering his patience and vision for
28306 free speech on the Internet.
28309 - Fix a memory leak when we ask for "all" networkstatuses and we
28310 get one we don't recognize.
28311 - Add more asserts to hunt down bug 417.
28312 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
28315 Changes in version 0.1.2.12-rc - 2007-03-16
28317 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
28318 directory information requested inside Tor connections (i.e. via
28319 begin_dir cells). It only triggered when the same connection was
28320 serving other data at the same time. Reported by seeess.
28323 - When creating a circuit via the controller, send a 'launched'
28324 event when we're done, so we follow the spec better.
28327 Changes in version 0.1.2.11-rc - 2007-03-15
28328 o Minor bugfixes (controller), reported by daejees:
28329 - Correct the control spec to match how the code actually responds
28330 to 'getinfo addr-mappings/*'.
28331 - The control spec described a GUARDS event, but the code
28332 implemented a GUARD event. Standardize on GUARD, but let people
28333 ask for GUARDS too.
28336 Changes in version 0.1.2.10-rc - 2007-03-07
28337 o Major bugfixes (Windows):
28338 - Do not load the NT services library functions (which may not exist)
28339 just to detect if we're a service trying to shut down. Now we run
28340 on Win98 and friends again.
28342 o Minor bugfixes (other):
28343 - Clarify a couple of log messages.
28344 - Fix a misleading socks5 error number.
28347 Changes in version 0.1.2.9-rc - 2007-03-02
28348 o Major bugfixes (Windows):
28349 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
28350 of the usual GCC "%llu". This prevents a bug when saving 64-bit
28351 int configuration values: the high-order 32 bits would get
28352 truncated. In particular, we were being bitten by the default
28353 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
28354 and maybe also bug 397.)
28356 o Minor bugfixes (performance):
28357 - Use OpenSSL's AES implementation on platforms where it's faster.
28358 This could save us as much as 10% CPU usage.
28360 o Minor bugfixes (server):
28361 - Do not rotate onion key immediately after setting it for the first
28364 o Minor bugfixes (directory authorities):
28365 - Stop calling servers that have been hibernating for a long time
28366 "stable". Also, stop letting hibernating or obsolete servers affect
28367 uptime and bandwidth cutoffs.
28368 - Stop listing hibernating servers in the v1 directory.
28370 o Minor bugfixes (hidden services):
28371 - Upload hidden service descriptors slightly less often, to reduce
28372 load on authorities.
28374 o Minor bugfixes (other):
28375 - Fix an assert that could trigger if a controller quickly set then
28376 cleared EntryNodes. Bug found by Udo van den Heuvel.
28377 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
28379 - Fix a potential race condition in the rpm installer. Found by
28381 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
28382 of 2 as indicating that the server is completely bad; it sometimes
28383 means that the server is just bad for the request in question. (may fix
28384 the last of bug 326.)
28385 - Disable encrypted directory connections when we don't have a server
28386 descriptor for the destination. We'll get this working again in
28390 Changes in version 0.1.2.8-beta - 2007-02-26
28391 o Major bugfixes (crashes):
28392 - Stop crashing when the controller asks us to resetconf more than
28393 one config option at once. (Vidalia 0.0.11 does this.)
28394 - Fix a crash that happened on Win98 when we're given command-line
28395 arguments: don't try to load NT service functions from advapi32.dll
28396 except when we need them. (Bug introduced in 0.1.2.7-alpha;
28398 - Fix a longstanding obscure crash bug that could occur when
28399 we run out of DNS worker processes. (Resolves bug 390.)
28401 o Major bugfixes (hidden services):
28402 - Correctly detect whether hidden service descriptor downloads are
28403 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
28405 o Major bugfixes (accounting):
28406 - When we start during an accounting interval before it's time to wake
28407 up, remember to wake up at the correct time. (May fix bug 342.)
28409 o Minor bugfixes (controller):
28410 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
28411 clear the corresponding on_circuit variable, and remember later
28412 that we don't need to send a redundant CLOSED event. Resolves part
28414 - Report events where a resolve succeeded or where we got a socks
28415 protocol error correctly, rather than calling both of them
28417 - Change reported stream target addresses to IP consistently when
28418 we finally get the IP from an exit node.
28419 - Send log messages to the controller even if they happen to be very
28422 o Minor bugfixes (other):
28423 - Display correct results when reporting which versions are
28424 recommended, and how recommended they are. (Resolves bug 383.)
28425 - Improve our estimates for directory bandwidth to be less random:
28426 guess that an unrecognized directory will have the average bandwidth
28427 from all known directories, not that it will have the average
28428 bandwidth from those directories earlier than it on the list.
28429 - If we start a server with ClientOnly 1, then set ClientOnly to 0
28430 and hup, stop triggering an assert based on an empty onion_key.
28431 - On platforms with no working mmap() equivalent, don't warn the
28432 user when cached-routers doesn't exist.
28433 - Warn the user when mmap() [or its equivalent] fails for some reason
28434 other than file-not-found.
28435 - Don't warn the user when cached-routers.new doesn't exist: that's
28436 perfectly fine when starting up for the first time.
28437 - When EntryNodes are configured, rebuild the guard list to contain,
28438 in order: the EntryNodes that were guards before; the rest of the
28439 EntryNodes; the nodes that were guards before.
28440 - Mask out all signals in sub-threads; only the libevent signal
28441 handler should be processing them. This should prevent some crashes
28442 on some machines using pthreads. (Patch from coderman.)
28443 - Fix switched arguments on memset in the implementation of
28444 tor_munmap() for systems with no mmap() call.
28445 - When Tor receives a router descriptor that it asked for, but
28446 no longer wants (because it has received fresh networkstatuses
28447 in the meantime), do not warn the user. Cache the descriptor if
28448 we're a cache; drop it if we aren't.
28449 - Make earlier entry guards _really_ get retried when the network
28451 - On a malformed DNS reply, always give an error to the corresponding
28453 - Build with recent libevents on platforms that do not define the
28454 nonstandard types "u_int8_t" and friends.
28456 o Minor features (controller):
28457 - Warn the user when an application uses the obsolete binary v0
28458 control protocol. We're planning to remove support for it during
28459 the next development series, so it's good to give people some
28461 - Add STREAM_BW events to report per-entry-stream bandwidth
28462 use. (Patch from Robert Hogan.)
28463 - Rate-limit SIGNEWNYM signals in response to controllers that
28464 impolitely generate them for every single stream. (Patch from
28465 mwenge; closes bug 394.)
28466 - Make REMAP stream events have a SOURCE (cache or exit), and
28467 make them generated in every case where we get a successful
28468 connected or resolved cell.
28470 o Minor bugfixes (performance):
28471 - Call router_have_min_dir_info half as often. (This is showing up in
28472 some profiles, but not others.)
28473 - When using GCC, make log_debug never get called at all, and its
28474 arguments never get evaluated, when no debug logs are configured.
28475 (This is showing up in some profiles, but not others.)
28478 - Remove some never-implemented options. Mark PathlenCoinWeight as
28480 - Implement proposal 106: Stop requiring clients to have well-formed
28481 certificates; stop checking nicknames in certificates. (Clients
28482 have certificates so that they can look like Tor servers, but in
28483 the future we might want to allow them to look like regular TLS
28484 clients instead. Nicknames in certificates serve no purpose other
28485 than making our protocol easier to recognize on the wire.)
28486 - Revise messages on handshake failure again to be even more clear about
28487 which are incoming connections and which are outgoing.
28488 - Discard any v1 directory info that's over 1 month old (for
28489 directories) or over 1 week old (for running-routers lists).
28490 - Do not warn when individual nodes in the configuration's EntryNodes,
28491 ExitNodes, etc are down: warn only when all possible nodes
28492 are down. (Fixes bug 348.)
28493 - Always remove expired routers and networkstatus docs before checking
28494 whether we have enough information to build circuits. (Fixes
28496 - Put a lower-bound on MaxAdvertisedBandwidth.
28499 Changes in version 0.1.2.7-alpha - 2007-02-06
28500 o Major bugfixes (rate limiting):
28501 - Servers decline directory requests much more aggressively when
28502 they're low on bandwidth. Otherwise they end up queueing more and
28503 more directory responses, which can't be good for latency.
28504 - But never refuse directory requests from local addresses.
28505 - Fix a memory leak when sending a 503 response for a networkstatus
28507 - Be willing to read or write on local connections (e.g. controller
28508 connections) even when the global rate limiting buckets are empty.
28509 - If our system clock jumps back in time, don't publish a negative
28510 uptime in the descriptor. Also, don't let the global rate limiting
28511 buckets go absurdly negative.
28512 - Flush local controller connection buffers periodically as we're
28513 writing to them, so we avoid queueing 4+ megabytes of data before
28516 o Major bugfixes (NT services):
28517 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
28518 command-line flag so that admins can override the default by saying
28519 "tor --service install --user "SomeUser"". This will not affect
28520 existing installed services. Also, warn the user that the service
28521 will look for its configuration file in the service user's
28522 %appdata% directory. (We can't do the 'hardwire the user's appdata
28523 directory' trick any more, since we may not have read access to that
28526 o Major bugfixes (other):
28527 - Previously, we would cache up to 16 old networkstatus documents
28528 indefinitely, if they came from nontrusted authorities. Now we
28529 discard them if they are more than 10 days old.
28530 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
28532 - Detect and reject malformed DNS responses containing circular
28534 - If exits are rare enough that we're not marking exits as guards,
28535 ignore exit bandwidth when we're deciding the required bandwidth
28537 - When we're handling a directory connection tunneled over Tor,
28538 don't fill up internal memory buffers with all the data we want
28539 to tunnel; instead, only add it if the OR connection that will
28540 eventually receive it has some room for it. (This can lead to
28541 slowdowns in tunneled dir connections; a better solution will have
28542 to wait for 0.2.0.)
28544 o Minor bugfixes (dns):
28545 - Add some defensive programming to eventdns.c in an attempt to catch
28546 possible memory-stomping bugs.
28547 - Detect and reject DNS replies containing IPv4 or IPv6 records with
28548 an incorrect number of bytes. (Previously, we would ignore the
28550 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
28551 in the correct order, and doesn't crash.
28552 - Free memory held in recently-completed DNS lookup attempts on exit.
28553 This was not a memory leak, but may have been hiding memory leaks.
28554 - Handle TTL values correctly on reverse DNS lookups.
28555 - Treat failure to parse resolv.conf as an error.
28557 o Minor bugfixes (other):
28558 - Fix crash with "tor --list-fingerprint" (reported by seeess).
28559 - When computing clock skew from directory HTTP headers, consider what
28560 time it was when we finished asking for the directory, not what
28562 - Expire socks connections if they spend too long waiting for the
28563 handshake to finish. Previously we would let them sit around for
28564 days, if the connecting application didn't close them either.
28565 - And if the socks handshake hasn't started, don't send a
28566 "DNS resolve socks failed" handshake reply; just close it.
28567 - Stop using C functions that OpenBSD's linker doesn't like.
28568 - Don't launch requests for descriptors unless we have networkstatuses
28569 from at least half of the authorities. This delays the first
28570 download slightly under pathological circumstances, but can prevent
28571 us from downloading a bunch of descriptors we don't need.
28572 - Do not log IPs with TLS failures for incoming TLS
28573 connections. (Fixes bug 382.)
28574 - If the user asks to use invalid exit nodes, be willing to use
28576 - Stop using the reserved ac_cv namespace in our configure script.
28577 - Call stat() slightly less often; use fstat() when possible.
28578 - Refactor the way we handle pending circuits when an OR connection
28579 completes or fails, in an attempt to fix a rare crash bug.
28580 - Only rewrite a conn's address based on X-Forwarded-For: headers
28581 if it's a parseable public IP address; and stop adding extra quotes
28582 to the resulting address.
28585 - Weight directory requests by advertised bandwidth. Now we can
28586 let servers enable write limiting but still allow most clients to
28587 succeed at their directory requests. (We still ignore weights when
28588 choosing a directory authority; I hope this is a feature.)
28591 - Create a new file ReleaseNotes which was the old ChangeLog. The
28592 new ChangeLog file now includes the summaries for all development
28594 - Check for addresses with invalid characters at the exit as well
28595 as at the client, and warn less verbosely when they fail. You can
28596 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
28597 - Adapt a patch from goodell to let the contrib/exitlist script
28598 take arguments rather than require direct editing.
28599 - Inform the server operator when we decide not to advertise a
28600 DirPort due to AccountingMax enabled or a low BandwidthRate. It
28601 was confusing Zax, so now we're hopefully more helpful.
28602 - Bring us one step closer to being able to establish an encrypted
28603 directory tunnel without knowing a descriptor first. Still not
28604 ready yet. As part of the change, now assume we can use a
28605 create_fast cell if we don't know anything about a router.
28606 - Allow exit nodes to use nameservers running on ports other than 53.
28607 - Servers now cache reverse DNS replies.
28608 - Add an --ignore-missing-torrc command-line option so that we can
28609 get the "use sensible defaults if the configuration file doesn't
28610 exist" behavior even when specifying a torrc location on the command
28613 o Minor features (controller):
28614 - Track reasons for OR connection failure; make these reasons
28615 available via the controller interface. (Patch from Mike Perry.)
28616 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
28617 can learn when clients are sending malformed hostnames to Tor.
28618 - Clean up documentation for controller status events.
28619 - Add a REMAP status to stream events to note that a stream's
28620 address has changed because of a cached address or a MapAddress
28624 Changes in version 0.1.2.6-alpha - 2007-01-09
28626 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
28627 connection handles more than 4 gigs in either direction, we crash.
28628 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
28629 advertised exit node, somebody might try to exit from us when
28630 we're bootstrapping and before we've built our descriptor yet.
28631 Refuse the connection rather than crashing.
28634 - Warn if we (as a server) find that we've resolved an address that we
28635 weren't planning to resolve.
28636 - Warn that using select() on any libevent version before 1.1 will be
28637 unnecessarily slow (even for select()).
28638 - Flush ERR-level controller status events just like we currently
28639 flush ERR-level log events, so that a Tor shutdown doesn't prevent
28640 the controller from learning about current events.
28642 o Minor features (more controller status events):
28643 - Implement EXTERNAL_ADDRESS server status event so controllers can
28644 learn when our address changes.
28645 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
28646 can learn when directories reject our descriptor.
28647 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
28648 can learn when a client application is speaking a non-socks protocol
28650 - Implement DANGEROUS_SOCKS client status event so controllers
28651 can learn when a client application is leaking DNS addresses.
28652 - Implement BUG general status event so controllers can learn when
28653 Tor is unhappy about its internal invariants.
28654 - Implement CLOCK_SKEW general status event so controllers can learn
28655 when Tor thinks the system clock is set incorrectly.
28656 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
28657 server status events so controllers can learn when their descriptors
28658 are accepted by a directory.
28659 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
28660 server status events so controllers can learn about Tor's progress in
28661 deciding whether it's reachable from the outside.
28662 - Implement BAD_LIBEVENT general status event so controllers can learn
28663 when we have a version/method combination in libevent that needs to
28665 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
28666 and DNS_USELESS server status events so controllers can learn
28667 about changes to DNS server status.
28669 o Minor features (directory):
28670 - Authorities no longer recommend exits as guards if this would shift
28671 too much load to the exit nodes.
28674 Changes in version 0.1.2.5-alpha - 2007-01-06
28676 - Enable write limiting as well as read limiting. Now we sacrifice
28677 capacity if we're pushing out lots of directory traffic, rather
28678 than overrunning the user's intended bandwidth limits.
28679 - Include TLS overhead when counting bandwidth usage; previously, we
28680 would count only the bytes sent over TLS, but not the bytes used
28682 - Support running the Tor service with a torrc not in the same
28683 directory as tor.exe and default to using the torrc located in
28684 the %appdata%\Tor\ of the user who installed the service. Patch
28686 - Servers now check for the case when common DNS requests are going to
28687 wildcarded addresses (i.e. all getting the same answer), and change
28688 their exit policy to reject *:* if it's happening.
28689 - Implement BEGIN_DIR cells, so we can connect to the directory
28690 server via TLS to do encrypted directory requests rather than
28691 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
28692 config options if you like.
28694 o Minor features (config and docs):
28695 - Start using the state file to store bandwidth accounting data:
28696 the bw_accounting file is now obsolete. We'll keep generating it
28697 for a while for people who are still using 0.1.2.4-alpha.
28698 - Try to batch changes to the state file so that we do as few
28699 disk writes as possible while still storing important things in
28701 - The state file and the bw_accounting file get saved less often when
28702 the AvoidDiskWrites config option is set.
28703 - Make PIDFile work on Windows (untested).
28704 - Add internal descriptions for a bunch of configuration options:
28705 accessible via controller interface and in comments in saved
28707 - Reject *:563 (NNTPS) in the default exit policy. We already reject
28708 NNTP by default, so this seems like a sensible addition.
28709 - Clients now reject hostnames with invalid characters. This should
28710 avoid some inadvertent info leaks. Add an option
28711 AllowNonRFC953Hostnames to disable this behavior, in case somebody
28712 is running a private network with hosts called @, !, and #.
28713 - Add a maintainer script to tell us which options are missing
28714 documentation: "make check-docs".
28715 - Add a new address-spec.txt document to describe our special-case
28716 addresses: .exit, .onion, and .noconnnect.
28718 o Minor features (DNS):
28719 - Ongoing work on eventdns infrastructure: now it has dns server
28720 and ipv6 support. One day Tor will make use of it.
28721 - Add client-side caching for reverse DNS lookups.
28722 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
28723 - When we change nameservers or IP addresses, reset and re-launch
28724 our tests for DNS hijacking.
28726 o Minor features (directory):
28727 - Authorities now specify server versions in networkstatus. This adds
28728 about 2% to the size of compressed networkstatus docs, and allows
28729 clients to tell which servers support BEGIN_DIR and which don't.
28730 The implementation is forward-compatible with a proposed future
28731 protocol version scheme not tied to Tor versions.
28732 - DirServer configuration lines now have an orport= option so
28733 clients can open encrypted tunnels to the authorities without
28734 having downloaded their descriptors yet. Enabled for moria1,
28735 moria2, tor26, and lefkada now in the default configuration.
28736 - Directory servers are more willing to send a 503 "busy" if they
28737 are near their write limit, especially for v1 directory requests.
28738 Now they can use their limited bandwidth for actual Tor traffic.
28739 - Clients track responses with status 503 from dirservers. After a
28740 dirserver has given us a 503, we try not to use it until an hour has
28741 gone by, or until we have no dirservers that haven't given us a 503.
28742 - When we get a 503 from a directory, and we're not a server, we don't
28743 count the failure against the total number of failures allowed
28744 for the thing we're trying to download.
28745 - Report X-Your-Address-Is correctly from tunneled directory
28746 connections; don't report X-Your-Address-Is when it's an internal
28747 address; and never believe reported remote addresses when they're
28749 - Protect against an unlikely DoS attack on directory servers.
28750 - Add a BadDirectory flag to network status docs so that authorities
28751 can (eventually) tell clients about caches they believe to be
28754 o Minor features (controller):
28755 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
28756 - Reimplement GETINFO so that info/names stays in sync with the
28758 - Implement "GETINFO fingerprint".
28759 - Implement "SETEVENTS GUARD" so controllers can get updates on
28760 entry guard status as it changes.
28762 o Minor features (clean up obsolete pieces):
28763 - Remove some options that have been deprecated since at least
28764 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
28765 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
28766 to set log options.
28767 - We no longer look for identity and onion keys in "identity.key" and
28768 "onion.key" -- these were replaced by secret_id_key and
28769 secret_onion_key in 0.0.8pre1.
28770 - We no longer require unrecognized directory entries to be
28773 o Major bugfixes (security):
28774 - Stop sending the HttpProxyAuthenticator string to directory
28775 servers when directory connections are tunnelled through Tor.
28776 - Clients no longer store bandwidth history in the state file.
28777 - Do not log introduction points for hidden services if SafeLogging
28779 - When generating bandwidth history, round down to the nearest
28780 1k. When storing accounting data, round up to the nearest 1k.
28781 - When we're running as a server, remember when we last rotated onion
28782 keys, so that we will rotate keys once they're a week old even if
28783 we never stay up for a week ourselves.
28785 o Major bugfixes (other):
28786 - Fix a longstanding bug in eventdns that prevented the count of
28787 timed-out resolves from ever being reset. This bug caused us to
28788 give up on a nameserver the third time it timed out, and try it
28789 10 seconds later... and to give up on it every time it timed out
28791 - Take out the '5 second' timeout from the connection retry
28792 schedule. Now the first connect attempt will wait a full 10
28793 seconds before switching to a new circuit. Perhaps this will help
28794 a lot. Based on observations from Mike Perry.
28795 - Fix a bug on the Windows implementation of tor_mmap_file() that
28796 would prevent the cached-routers file from ever loading. Reported
28800 - Fix an assert failure when a directory authority sets
28801 AuthDirRejectUnlisted and then receives a descriptor from an
28802 unlisted router. Reported by seeess.
28803 - Avoid a double-free when parsing malformed DirServer lines.
28804 - Fix a bug when a BSD-style PF socket is first used. Patch from
28806 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
28807 to resolve an address at a given exit node even when they ask for
28809 - Servers no longer ever list themselves in their "family" line,
28810 even if configured to do so. This makes it easier to configure
28811 family lists conveniently.
28812 - When running as a server, don't fall back to 127.0.0.1 when no
28813 nameservers are configured in /etc/resolv.conf; instead, make the
28814 user fix resolv.conf or specify nameservers explicitly. (Resolves
28816 - Stop accepting certain malformed ports in configured exit policies.
28817 - Don't re-write the fingerprint file every restart, unless it has
28819 - Stop warning when a single nameserver fails: only warn when _all_ of
28820 our nameservers have failed. Also, when we only have one nameserver,
28821 raise the threshold for deciding that the nameserver is dead.
28822 - Directory authorities now only decide that routers are reachable
28823 if their identity keys are as expected.
28824 - When the user uses bad syntax in the Log config line, stop
28825 suggesting other bad syntax as a replacement.
28826 - Correctly detect ipv6 DNS capability on OpenBSD.
28828 o Minor bugfixes (controller):
28829 - Report the circuit number correctly in STREAM CLOSED events. Bug
28830 reported by Mike Perry.
28831 - Do not report bizarre values for results of accounting GETINFOs
28832 when the last second's write or read exceeds the allotted bandwidth.
28833 - Report "unrecognized key" rather than an empty string when the
28834 controller tries to fetch a networkstatus that doesn't exist.
28837 Changes in version 0.1.1.26 - 2006-12-14
28838 o Security bugfixes:
28839 - Stop sending the HttpProxyAuthenticator string to directory
28840 servers when directory connections are tunnelled through Tor.
28841 - Clients no longer store bandwidth history in the state file.
28842 - Do not log introduction points for hidden services if SafeLogging
28846 - Fix an assert failure when a directory authority sets
28847 AuthDirRejectUnlisted and then receives a descriptor from an
28848 unlisted router (reported by seeess).
28851 Changes in version 0.1.2.4-alpha - 2006-12-03
28853 - Add support for using natd; this allows FreeBSDs earlier than
28854 5.1.2 to have ipfw send connections through Tor without using
28855 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
28858 - Make all connections to addresses of the form ".noconnect"
28859 immediately get closed. This lets application/controller combos
28860 successfully test whether they're talking to the same Tor by
28861 watching for STREAM events.
28862 - Make cross.sh cross-compilation script work even when autogen.sh
28863 hasn't been run. (Patch from Michael Mohr.)
28864 - Statistics dumped by -USR2 now include a breakdown of public key
28865 operations, for profiling.
28868 - Fix a major leak when directory authorities parse their
28869 approved-routers list, a minor memory leak when we fail to pick
28870 an exit node, and a few rare leaks on errors.
28871 - Handle TransPort connections even when the server sends data before
28872 the client sends data. Previously, the connection would just hang
28873 until the client sent data. (Patch from tup based on patch from
28875 - Avoid assert failure when our cached-routers file is empty on
28879 - Don't log spurious warnings when we see a circuit close reason we
28880 don't recognize; it's probably just from a newer version of Tor.
28881 - Have directory authorities allow larger amounts of drift in uptime
28882 without replacing the server descriptor: previously, a server that
28883 restarted every 30 minutes could have 48 "interesting" descriptors
28885 - Start linking to the Tor specification and Tor reference manual
28886 correctly in the Windows installer.
28887 - Add Vidalia to the OS X uninstaller script, so when we uninstall
28888 Tor/Privoxy we also uninstall Vidalia.
28889 - Resume building on Irix64, and fix a lot of warnings from its
28890 MIPSpro C compiler.
28891 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
28892 when we're running as a client.
28895 Changes in version 0.1.1.25 - 2006-11-04
28897 - When a client asks us to resolve (rather than connect to)
28898 an address, and we have a cached answer, give them the cached
28899 answer. Previously, we would give them no answer at all.
28900 - We were building exactly the wrong circuits when we predict
28901 hidden service requirements, meaning Tor would have to build all
28902 its circuits on demand.
28903 - If none of our live entry guards have a high uptime, but we
28904 require a guard with a high uptime, try adding a new guard before
28905 we give up on the requirement. This patch should make long-lived
28906 connections more stable on average.
28907 - When testing reachability of our DirPort, don't launch new
28908 tests when there's already one in progress -- unreachable
28909 servers were stacking up dozens of testing streams.
28911 o Security bugfixes:
28912 - When the user sends a NEWNYM signal, clear the client-side DNS
28913 cache too. Otherwise we continue to act on previous information.
28916 - Avoid a memory corruption bug when creating a hash table for
28918 - Avoid possibility of controller-triggered crash when misusing
28919 certain commands from a v0 controller on platforms that do not
28920 handle printf("%s",NULL) gracefully.
28921 - Avoid infinite loop on unexpected controller input.
28922 - Don't log spurious warnings when we see a circuit close reason we
28923 don't recognize; it's probably just from a newer version of Tor.
28924 - Add Vidalia to the OS X uninstaller script, so when we uninstall
28925 Tor/Privoxy we also uninstall Vidalia.
28928 Changes in version 0.1.2.3-alpha - 2006-10-29
28930 - Prepare for servers to publish descriptors less often: never
28931 discard a descriptor simply for being too old until either it is
28932 recommended by no authorities, or until we get a better one for
28933 the same router. Make caches consider retaining old recommended
28934 routers for even longer.
28935 - If most authorities set a BadExit flag for a server, clients
28936 don't think of it as a general-purpose exit. Clients only consider
28937 authorities that advertise themselves as listing bad exits.
28938 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
28939 headers for content, so that we can work better in the presence of
28940 caching HTTP proxies.
28941 - Allow authorities to list nodes as bad exits by fingerprint or by
28944 o Minor features, controller:
28945 - Add a REASON field to CIRC events; for backward compatibility, this
28946 field is sent only to controllers that have enabled the extended
28947 event format. Also, add additional reason codes to explain why
28948 a given circuit has been destroyed or truncated. (Patches from
28950 - Add a REMOTE_REASON field to extended CIRC events to tell the
28951 controller about why a remote OR told us to close a circuit.
28952 - Stream events also now have REASON and REMOTE_REASON fields,
28953 working much like those for circuit events.
28954 - There's now a GETINFO ns/... field so that controllers can ask Tor
28955 about the current status of a router.
28956 - A new event type "NS" to inform a controller when our opinion of
28957 a router's status has changed.
28958 - Add a GETINFO events/names and GETINFO features/names so controllers
28959 can tell which events and features are supported.
28960 - A new CLEARDNSCACHE signal to allow controllers to clear the
28961 client-side DNS cache without expiring circuits.
28963 o Security bugfixes:
28964 - When the user sends a NEWNYM signal, clear the client-side DNS
28965 cache too. Otherwise we continue to act on previous information.
28968 - Avoid sending junk to controllers or segfaulting when a controller
28969 uses EVENT_NEW_DESC with verbose nicknames.
28970 - Stop triggering asserts if the controller tries to extend hidden
28971 service circuits (reported by mwenge).
28972 - Avoid infinite loop on unexpected controller input.
28973 - When the controller does a "GETINFO network-status", tell it
28974 about even those routers whose descriptors are very old, and use
28975 long nicknames where appropriate.
28976 - Change NT service functions to be loaded on demand. This lets us
28977 build with MinGW without breaking Tor for Windows 98 users.
28978 - Do DirPort reachability tests less often, since a single test
28979 chews through many circuits before giving up.
28980 - In the hidden service example in torrc.sample, stop recommending
28981 esoteric and discouraged hidden service options.
28982 - When stopping an NT service, wait up to 10 sec for it to actually
28983 stop. Patch from Matt Edman; resolves bug 295.
28984 - Fix handling of verbose nicknames with ORCONN controller events:
28985 make them show up exactly when requested, rather than exactly when
28987 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
28988 printing a duplicate "$" in the keys we send (reported by mwenge).
28989 - Correctly set maximum connection limit on Cygwin. (This time
28991 - Try to detect Windows correctly when cross-compiling.
28992 - Detect the size of the routers file correctly even if it is
28993 corrupted (on systems without mmap) or not page-aligned (on systems
28994 with mmap). This bug was harmless.
28995 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
28996 to open a stream fails; now we do in more cases. This should
28997 make clients able to find a good exit faster in some cases, since
28998 unhandleable requests will now get an error rather than timing out.
28999 - Resolve two memory leaks when rebuilding the on-disk router cache
29000 (reported by fookoowa).
29001 - Clean up minor code warnings suggested by the MIPSpro C compiler,
29002 and reported by some Centos users.
29003 - Controller signals now work on non-Unix platforms that don't define
29004 SIGUSR1 and SIGUSR2 the way we expect.
29005 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
29006 values before failing, and always enables eventdns.
29007 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
29008 Try to fix this in configure.in by checking for most functions
29009 before we check for libevent.
29012 Changes in version 0.1.2.2-alpha - 2006-10-07
29014 - Make our async eventdns library on-by-default for Tor servers,
29015 and plan to deprecate the separate dnsworker threads.
29016 - Add server-side support for "reverse" DNS lookups (using PTR
29017 records so clients can determine the canonical hostname for a given
29018 IPv4 address). Only supported by servers using eventdns; servers
29019 now announce in their descriptors whether they support eventdns.
29020 - Specify and implement client-side SOCKS5 interface for reverse DNS
29021 lookups (see doc/socks-extensions.txt).
29022 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
29023 connect to directory servers through Tor. Previously, clients needed
29024 to find Tor exits to make private connections to directory servers.
29025 - Avoid choosing Exit nodes for entry or middle hops when the
29026 total bandwidth available from non-Exit nodes is much higher than
29027 the total bandwidth available from Exit nodes.
29028 - Workaround for name servers (like Earthlink's) that hijack failing
29029 DNS requests and replace the no-such-server answer with a "helpful"
29030 redirect to an advertising-driven search portal. Also work around
29031 DNS hijackers who "helpfully" decline to hijack known-invalid
29032 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
29033 lets you turn it off.
29034 - Send out a burst of long-range padding cells once we've established
29035 that we're reachable. Spread them over 4 circuits, so hopefully
29036 a few will be fast. This exercises our bandwidth and bootstraps
29037 us into the directory more quickly.
29039 o New/improved config options:
29040 - Add new config option "ResolvConf" to let the server operator
29041 choose an alternate resolve.conf file when using eventdns.
29042 - Add an "EnforceDistinctSubnets" option to control our "exclude
29043 servers on the same /16" behavior. It's still on by default; this
29044 is mostly for people who want to operate private test networks with
29045 all the machines on the same subnet.
29046 - If one of our entry guards is on the ExcludeNodes list, or the
29047 directory authorities don't think it's a good guard, treat it as
29048 if it were unlisted: stop using it as a guard, and throw it off
29049 the guards list if it stays that way for a long time.
29050 - Allow directory authorities to be marked separately as authorities
29051 for the v1 directory protocol, the v2 directory protocol, and
29052 as hidden service directories, to make it easier to retire old
29053 authorities. V1 authorities should set "HSAuthoritativeDir 1"
29054 to continue being hidden service authorities too.
29055 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
29057 o Minor features, controller:
29058 - Fix CIRC controller events so that controllers can learn the
29059 identity digests of non-Named servers used in circuit paths.
29060 - Let controllers ask for more useful identifiers for servers. Instead
29061 of learning identity digests for un-Named servers and nicknames
29062 for Named servers, the new identifiers include digest, nickname,
29063 and indication of Named status. Off by default; see control-spec.txt
29064 for more information.
29065 - Add a "getinfo address" controller command so it can display Tor's
29066 best guess to the user.
29067 - New controller event to alert the controller when our server
29068 descriptor has changed.
29069 - Give more meaningful errors on controller authentication failure.
29071 o Minor features, other:
29072 - When asked to resolve a hostname, don't use non-exit servers unless
29073 requested to do so. This allows servers with broken DNS to be
29074 useful to the network.
29075 - Divide eventdns log messages into warn and info messages.
29076 - Reserve the nickname "Unnamed" for routers that can't pick
29077 a hostname: any router can call itself Unnamed; directory
29078 authorities will never allocate Unnamed to any particular router;
29079 clients won't believe that any router is the canonical Unnamed.
29080 - Only include function names in log messages for info/debug messages.
29081 For notice/warn/err, the content of the message should be clear on
29082 its own, and printing the function name only confuses users.
29083 - Avoid some false positives during reachability testing: don't try
29084 to test via a server that's on the same /24 as us.
29085 - If we fail to build a circuit to an intended enclave, and it's
29086 not mandatory that we use that enclave, stop wanting it.
29087 - When eventdns is enabled, allow multithreaded builds on NetBSD and
29088 OpenBSD. (We had previously disabled threads on these platforms
29089 because they didn't have working thread-safe resolver functions.)
29091 o Major bugfixes, anonymity/security:
29092 - If a client asked for a server by name, and there's a named server
29093 in our network-status but we don't have its descriptor yet, we
29094 could return an unnamed server instead.
29095 - Fix NetBSD bug that could allow someone to force uninitialized RAM
29096 to be sent to a server's DNS resolver. This only affects NetBSD
29097 and other platforms that do not bounds-check tolower().
29098 - Reject (most) attempts to use Tor circuits with length one. (If
29099 many people start using Tor as a one-hop proxy, exit nodes become
29100 a more attractive target for compromise.)
29101 - Just because your DirPort is open doesn't mean people should be
29102 able to remotely teach you about hidden service descriptors. Now
29103 only accept rendezvous posts if you've got HSAuthoritativeDir set.
29105 o Major bugfixes, other:
29106 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
29107 - When a client asks the server to resolve (not connect to)
29108 an address, and it has a cached answer, give them the cached answer.
29109 Previously, the server would give them no answer at all.
29110 - Allow really slow clients to not hang up five minutes into their
29111 directory downloads (suggested by Adam J. Richter).
29112 - We were building exactly the wrong circuits when we anticipated
29113 hidden service requirements, meaning Tor would have to build all
29114 its circuits on demand.
29115 - Avoid crashing when we mmap a router cache file of size 0.
29116 - When testing reachability of our DirPort, don't launch new
29117 tests when there's already one in progress -- unreachable
29118 servers were stacking up dozens of testing streams.
29120 o Minor bugfixes, correctness:
29121 - If we're a directory mirror and we ask for "all" network status
29122 documents, we would discard status documents from authorities
29123 we don't recognize.
29124 - Avoid a memory corruption bug when creating a hash table for
29126 - Avoid controller-triggered crash when misusing certain commands
29127 from a v0 controller on platforms that do not handle
29128 printf("%s",NULL) gracefully.
29129 - Don't crash when a controller sends a third argument to an
29130 "extendcircuit" request.
29131 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29132 response; fix error code when "getinfo dir/status/" fails.
29133 - Avoid crash when telling controller stream-status and a stream
29135 - Patch from Adam Langley to fix assert() in eventdns.c.
29136 - Fix a debug log message in eventdns to say "X resolved to Y"
29137 instead of "X resolved to X".
29138 - Make eventdns give strings for DNS errors, not just error numbers.
29139 - Track unreachable entry guards correctly: don't conflate
29140 'unreachable by us right now' with 'listed as down by the directory
29141 authorities'. With the old code, if a guard was unreachable by
29142 us but listed as running, it would clog our guard list forever.
29143 - Behave correctly in case we ever have a network with more than
29144 2GB/s total advertised capacity.
29145 - Make TrackExitHosts case-insensitive, and fix the behavior of
29146 ".suffix" TrackExitHosts items to avoid matching in the middle of
29148 - Finally fix the openssl warnings from newer gccs that believe that
29149 ignoring a return value is okay, but casting a return value and
29150 then ignoring it is a sign of madness.
29151 - Prevent the contrib/exitlist script from printing the same
29152 result more than once.
29153 - Patch from Steve Hildrey: Generate network status correctly on
29154 non-versioning dirservers.
29155 - Don't listen to the X-Your-Address-Is hint if you did the lookup
29156 via Tor; otherwise you'll think you're the exit node's IP address.
29158 o Minor bugfixes, performance:
29159 - Two small performance improvements on parsing descriptors.
29160 - Major performance improvement on inserting descriptors: change
29161 algorithm from O(n^2) to O(n).
29162 - Make the common memory allocation path faster on machines where
29163 malloc(0) returns a pointer.
29164 - Start remembering X-Your-Address-Is directory hints even if you're
29165 a client, so you can become a server more smoothly.
29166 - Avoid duplicate entries on MyFamily line in server descriptor.
29168 o Packaging, features:
29169 - Remove architecture from OS X builds. The official builds are
29170 now universal binaries.
29171 - The Debian package now uses --verify-config when (re)starting,
29172 to distinguish configuration errors from other errors.
29173 - Update RPMs to require libevent 1.1b.
29175 o Packaging, bugfixes:
29176 - Patches so Tor builds with MinGW on Windows.
29177 - Patches so Tor might run on Cygwin again.
29178 - Resume building on non-gcc compilers and ancient gcc. Resume
29179 building with the -O0 compile flag. Resume building cleanly on
29181 - Run correctly on OS X platforms with case-sensitive filesystems.
29182 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
29183 - Add autoconf checks so Tor can build on Solaris x86 again.
29186 - Documented (and renamed) ServerDNSSearchDomains and
29187 ServerDNSResolvConfFile options.
29188 - Be clearer that the *ListenAddress directives can be repeated
29192 Changes in version 0.1.1.24 - 2006-09-29
29194 - Allow really slow clients to not hang up five minutes into their
29195 directory downloads (suggested by Adam J. Richter).
29196 - Fix major performance regression from 0.1.0.x: instead of checking
29197 whether we have enough directory information every time we want to
29198 do something, only check when the directory information has changed.
29199 This should improve client CPU usage by 25-50%.
29200 - Don't crash if, after a server has been running for a while,
29201 it can't resolve its hostname.
29204 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29205 - Don't crash when the controller receives a third argument to an
29206 "extendcircuit" request.
29207 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29208 response; fix error code when "getinfo dir/status/" fails.
29209 - Fix configure.in to not produce broken configure files with
29210 more recent versions of autoconf. Thanks to Clint for his auto*
29212 - Fix security bug on NetBSD that could allow someone to force
29213 uninitialized RAM to be sent to a server's DNS resolver. This
29214 only affects NetBSD and other platforms that do not bounds-check
29216 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
29217 methods: these are known to be buggy.
29218 - If we're a directory mirror and we ask for "all" network status
29219 documents, we would discard status documents from authorities
29220 we don't recognize.
29223 Changes in version 0.1.2.1-alpha - 2006-08-27
29225 - Add "eventdns" async dns library from Adam Langley, tweaked to
29226 build on OSX and Windows. Only enabled if you pass the
29227 --enable-eventdns argument to configure.
29228 - Allow servers with no hostname or IP address to learn their
29229 IP address by asking the directory authorities. This code only
29230 kicks in when you would normally have exited with a "no address"
29231 error. Nothing's authenticated, so use with care.
29232 - Rather than waiting a fixed amount of time between retrying
29233 application connections, we wait only 5 seconds for the first,
29234 10 seconds for the second, and 15 seconds for each retry after
29235 that. Hopefully this will improve the expected user experience.
29236 - Patch from Tup to add support for transparent AP connections:
29237 this basically bundles the functionality of trans-proxy-tor
29238 into the Tor mainline. Now hosts with compliant pf/netfilter
29239 implementations can redirect TCP connections straight to Tor
29240 without diverting through SOCKS. Needs docs.
29241 - Busy directory servers save lots of memory by spooling server
29242 descriptors, v1 directories, and v2 networkstatus docs to buffers
29243 as needed rather than en masse. Also mmap the cached-routers
29244 files, so we don't need to keep the whole thing in memory too.
29245 - Automatically avoid picking more than one node from the same
29246 /16 network when constructing a circuit.
29247 - Revise and clean up the torrc.sample that we ship with; add
29248 a section for BandwidthRate and BandwidthBurst.
29251 - Split circuit_t into origin_circuit_t and or_circuit_t, and
29252 split connection_t into edge, or, dir, control, and base structs.
29253 These will save quite a bit of memory on busy servers, and they'll
29254 also help us track down bugs in the code and bugs in the spec.
29255 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
29256 or later. Log when we are doing this, so we can diagnose it when
29257 it fails. (Also, recommend libevent 1.1b for kqueue and
29258 win32 methods; deprecate libevent 1.0b harder; make libevent
29259 recommendation system saner.)
29260 - Start being able to build universal binaries on OS X (thanks
29262 - Export the default exit policy via the control port, so controllers
29263 don't need to guess what it is / will be later.
29264 - Add a man page entry for ProtocolWarnings.
29265 - Add TestVia config option to the man page.
29266 - Remove even more protocol-related warnings from Tor server logs,
29267 such as bad TLS handshakes and malformed begin cells.
29268 - Stop fetching descriptors if you're not a dir mirror and you
29269 haven't tried to establish any circuits lately. [This currently
29270 causes some dangerous behavior, because when you start up again
29271 you'll use your ancient server descriptors.]
29272 - New DirPort behavior: if you have your dirport set, you download
29273 descriptors aggressively like a directory mirror, whether or not
29274 your ORPort is set.
29275 - Get rid of the router_retry_connections notion. Now routers
29276 no longer try to rebuild long-term connections to directory
29277 authorities, and directory authorities no longer try to rebuild
29278 long-term connections to all servers. We still don't hang up
29279 connections in these two cases though -- we need to look at it
29280 more carefully to avoid flapping, and we likely need to wait til
29281 0.1.1.x is obsolete.
29282 - Drop compatibility with obsolete Tors that permit create cells
29283 to have the wrong circ_id_type.
29284 - Re-enable per-connection rate limiting. Get rid of the "OP
29285 bandwidth" concept. Lay groundwork for "bandwidth classes" --
29286 separate global buckets that apply depending on what sort of conn
29288 - Start publishing one minute or so after we find our ORPort
29289 to be reachable. This will help reduce the number of descriptors
29290 we have for ourselves floating around, since it's quite likely
29291 other things (e.g. DirPort) will change during that minute too.
29292 - Fork the v1 directory protocol into its own spec document,
29293 and mark dir-spec.txt as the currently correct (v2) spec.
29296 - When we find our DirPort to be reachable, publish a new descriptor
29297 so we'll tell the world (reported by pnx).
29298 - Publish a new descriptor after we hup/reload. This is important
29299 if our config has changed such that we'll want to start advertising
29300 our DirPort now, etc.
29301 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29302 - When we have a state file we cannot parse, tell the user and
29303 move it aside. Now we avoid situations where the user starts
29304 Tor in 1904, Tor writes a state file with that timestamp in it,
29305 the user fixes her clock, and Tor refuses to start.
29306 - Fix configure.in to not produce broken configure files with
29307 more recent versions of autoconf. Thanks to Clint for his auto*
29309 - "tor --verify-config" now exits with -1(255) or 0 depending on
29310 whether the config options are bad or good.
29311 - Resolve bug 321 when using dnsworkers: append a period to every
29312 address we resolve at the exit node, so that we do not accidentally
29313 pick up local addresses, and so that failing searches are retried
29314 in the resolver search domains. (This is already solved for
29315 eventdns.) (This breaks Blossom servers for now.)
29316 - If we are using an exit enclave and we can't connect, e.g. because
29317 its webserver is misconfigured to not listen on localhost, then
29318 back off and try connecting from somewhere else before we fail.
29321 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
29322 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
29323 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
29324 when the IP address is mapped through MapAddress to a hostname.
29325 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
29326 useless IPv6 DNS resolves.
29327 - Patch suggested by Karsten Loesing: respond to SIGNAL command
29328 before we execute the signal, in case the signal shuts us down.
29329 - Clean up AllowInvalidNodes man page entry.
29330 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
29331 - Add more asserts to track down an assert error on a windows Tor
29332 server with connection_add being called with socket == -1.
29333 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
29334 - Fix misleading log messages: an entry guard that is "unlisted",
29335 as well as not known to be "down" (because we've never heard
29336 of it), is not therefore "up".
29337 - Remove code to special-case "-cvs" ending, since it has not
29338 actually mattered since 0.0.9.
29339 - Make our socks5 handling more robust to broken socks clients:
29340 throw out everything waiting on the buffer in between socks
29341 handshake phases, since they can't possibly (so the theory
29342 goes) have predicted what we plan to respond to them.
29345 Changes in version 0.1.1.23 - 2006-07-30
29347 - Fast Tor servers, especially exit nodes, were triggering asserts
29348 due to a bug in handling the list of pending DNS resolves. Some
29349 bugs still remain here; we're hunting them.
29350 - Entry guards could crash clients by sending unexpected input.
29351 - More fixes on reachability testing: if you find yourself reachable,
29352 then don't ever make any client requests (so you stop predicting
29353 circuits), then hup or have your clock jump, then later your IP
29354 changes, you won't think circuits are working, so you won't try to
29355 test reachability, so you won't publish.
29358 - Avoid a crash if the controller does a resetconf firewallports
29359 and then a setconf fascistfirewall=1.
29360 - Avoid an integer underflow when the dir authority decides whether
29361 a router is stable: we might wrongly label it stable, and compute
29362 a slightly wrong median stability, when a descriptor is published
29364 - Fix a place where we might trigger an assert if we can't build our
29365 own server descriptor yet.
29368 Changes in version 0.1.1.22 - 2006-07-05
29370 - Fix a big bug that was causing servers to not find themselves
29371 reachable if they changed IP addresses. Since only 0.1.1.22+
29372 servers can do reachability testing correctly, now we automatically
29373 make sure to test via one of these.
29374 - Fix to allow clients and mirrors to learn directory info from
29375 descriptor downloads that get cut off partway through.
29376 - Directory authorities had a bug in deciding if a newly published
29377 descriptor was novel enough to make everybody want a copy -- a few
29378 servers seem to be publishing new descriptors many times a minute.
29380 - Fix a rare bug that was causing some servers to complain about
29381 "closing wedged cpuworkers" and skip some circuit create requests.
29382 - Make the Exit flag in directory status documents actually work.
29385 Changes in version 0.1.1.21 - 2006-06-10
29386 o Crash and assert fixes from 0.1.1.20:
29387 - Fix a rare crash on Tor servers that have enabled hibernation.
29388 - Fix a seg fault on startup for Tor networks that use only one
29389 directory authority.
29390 - Fix an assert from a race condition that occurs on Tor servers
29391 while exiting, where various threads are trying to log that they're
29392 exiting, and delete the logs, at the same time.
29393 - Make our unit tests pass again on certain obscure platforms.
29396 - Add support for building SUSE RPM packages.
29397 - Speed up initial bootstrapping for clients: if we are making our
29398 first ever connection to any entry guard, then don't mark it down
29400 - When only one Tor server in the network is labelled as a guard,
29401 and we've already picked him, we would cycle endlessly picking him
29402 again, being unhappy about it, etc. Now we specifically exclude
29403 current guards when picking a new guard.
29404 - Servers send create cells more reliably after the TLS connection
29405 is established: we were sometimes forgetting to send half of them
29406 when we had more than one pending.
29407 - If we get a create cell that asks us to extend somewhere, but the
29408 Tor server there doesn't match the expected digest, we now send
29409 a destroy cell back, rather than silently doing nothing.
29410 - Make options->RedirectExit work again.
29411 - Make cookie authentication for the controller work again.
29412 - Stop being picky about unusual characters in the arguments to
29413 mapaddress. It's none of our business.
29414 - Add a new config option "TestVia" that lets you specify preferred
29415 middle hops to use for test circuits. Perhaps this will let me
29416 debug the reachability problems better.
29418 o Log / documentation fixes:
29419 - If we're a server and some peer has a broken TLS certificate, don't
29420 log about it unless ProtocolWarnings is set, i.e., we want to hear
29421 about protocol violations by others.
29422 - Fix spelling of VirtualAddrNetwork in man page.
29423 - Add a better explanation at the top of the autogenerated torrc file
29424 about what happened to our old torrc.
29427 Changes in version 0.1.1.20 - 2006-05-23
29429 - Downgrade a log severity where servers complain that they're
29431 - Avoid a compile warning on FreeBSD.
29432 - Remove string size limit on NEWDESC messages; solve bug 291.
29433 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
29434 more thoroughly when we're running on windows.
29437 Changes in version 0.1.1.19-rc - 2006-05-03
29439 - Regenerate our local descriptor if it's dirty and we try to use
29440 it locally (e.g. if it changes during reachability detection).
29441 - If we setconf our ORPort to 0, we continued to listen on the
29442 old ORPort and receive connections.
29443 - Avoid a second warning about machine/limits.h on Debian
29445 - Be willing to add our own routerinfo into the routerlist.
29446 Now authorities will include themselves in their directories
29447 and network-statuses.
29448 - Stop trying to upload rendezvous descriptors to every
29449 directory authority: only try the v1 authorities.
29450 - Servers no longer complain when they think they're not
29451 registered with the directory authorities. There were too many
29453 - Backport dist-rpm changes so rpms can be built without errors.
29456 - Implement an option, VirtualAddrMask, to set which addresses
29457 get handed out in response to mapaddress requests. This works
29458 around a bug in tsocks where 127.0.0.0/8 is never socksified.
29461 Changes in version 0.1.1.18-rc - 2006-04-10
29463 - Work harder to download live network-statuses from all the
29464 directory authorities we know about. Improve the threshold
29465 decision logic so we're more robust to edge cases.
29466 - When fetching rendezvous descriptors, we were willing to ask
29467 v2 authorities too, which would always return 404.
29470 - Stop listing down or invalid nodes in the v1 directory. This will
29471 reduce its bulk by about 1/3, and reduce load on directory
29473 - When deciding whether a router is Fast or Guard-worthy, consider
29474 his advertised BandwidthRate and not just the BandwidthCapacity.
29475 - No longer ship INSTALL and README files -- they are useless now.
29476 - Force rpmbuild to behave and honor target_cpu.
29477 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
29478 - Start to include translated versions of the tor-doc-*.html
29479 files, along with the screenshots. Still needs more work.
29480 - Start sending back 512 and 451 errors if mapaddress fails,
29481 rather than not sending anything back at all.
29482 - When we fail to bind or listen on an incoming or outgoing
29483 socket, we should close it before failing. otherwise we just
29484 leak it. (thanks to weasel for finding.)
29485 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
29486 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
29487 - Make NoPublish (even though deprecated) work again.
29488 - Fix a minor security flaw where a versioning auth dirserver
29489 could list a recommended version many times in a row to make
29490 clients more convinced that it's recommended.
29491 - Fix crash bug if there are two unregistered servers running
29492 with the same nickname, one of them is down, and you ask for
29493 them by nickname in your EntryNodes or ExitNodes. Also, try
29494 to pick the one that's running rather than an arbitrary one.
29495 - Fix an infinite loop we could hit if we go offline for too long.
29496 - Complain when we hit WSAENOBUFS on recv() or write() too.
29497 Perhaps this will help us hunt the bug.
29498 - If you're not a versioning dirserver, don't put the string
29499 "client-versions \nserver-versions \n" in your network-status.
29500 - Lower the minimum required number of file descriptors to 1000,
29501 so we can have some overhead for Valgrind on Linux, where the
29502 default ulimit -n is 1024.
29505 - Add tor.dizum.com as the fifth authoritative directory server.
29506 - Add a new config option FetchUselessDescriptors, off by default,
29507 for when you plan to run "exitlist" on your client and you want
29508 to know about even the non-running descriptors.
29511 Changes in version 0.1.1.17-rc - 2006-03-28
29513 - Clients and servers since 0.1.1.10-alpha have been expiring
29514 connections whenever they are idle for 5 minutes and they *do*
29515 have circuits on them. Oops. With this new version, clients will
29516 discard their previous entry guard choices and avoid choosing
29517 entry guards running these flawed versions.
29518 - Fix memory leak when uncompressing concatenated zlib streams. This
29519 was causing substantial leaks over time on Tor servers.
29520 - The v1 directory was including servers as much as 48 hours old,
29521 because that's how the new routerlist->routers works. Now only
29522 include them if they're 20 hours old or less.
29525 - Resume building on irix64, netbsd 2.0, etc.
29526 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
29528 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
29529 and it is confusing some users.
29530 - Mirrors stop caching the v1 directory so often.
29531 - Make the max number of old descriptors that a cache will hold
29532 rise with the number of directory authorities, so we can scale.
29533 - Change our win32 uname() hack to be more forgiving about what
29534 win32 versions it thinks it's found.
29537 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
29539 - When the controller's *setconf commands fail, collect an error
29540 message in a string and hand it back to the controller.
29541 - Make the v2 dir's "Fast" flag based on relative capacity, just
29542 like "Stable" is based on median uptime. Name everything in the
29543 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
29544 - Log server fingerprint on startup, so new server operators don't
29545 have to go hunting around their filesystem for it.
29546 - Return a robots.txt on our dirport to discourage google indexing.
29547 - Let the controller ask for GETINFO dir/status/foo so it can ask
29548 directly rather than connecting to the dir port. Only works when
29549 dirport is set for now.
29551 o New config options rather than constants in the code:
29552 - SocksTimeout: How long do we let a socks connection wait
29553 unattached before we fail it?
29554 - CircuitBuildTimeout: Cull non-open circuits that were born
29555 at least this many seconds ago.
29556 - CircuitIdleTimeout: Cull open clean circuits that were born
29557 at least this many seconds ago.
29560 Changes in version 0.1.1.16-rc - 2006-03-18
29561 o Bugfixes on 0.1.1.15-rc:
29562 - Fix assert when the controller asks to attachstream a connect-wait
29563 or resolve-wait stream.
29564 - Now do address rewriting when the controller asks us to attach
29565 to a particular circuit too. This will let Blossom specify
29566 "moria2.exit" without having to learn what moria2's IP address is.
29567 - Make the "tor --verify-config" command-line work again, so people
29568 can automatically check if their torrc will parse.
29569 - Authoritative dirservers no longer require an open connection from
29570 a server to consider him "reachable". We need this change because
29571 when we add new auth dirservers, old servers won't know not to
29573 - Let Tor build on Sun CC again.
29574 - Fix an off-by-one buffer size in dirserv.c that magically never
29575 hit our three authorities but broke sjmurdoch's own tor network.
29576 - If we as a directory mirror don't know of any v1 directory
29577 authorities, then don't try to cache any v1 directories.
29578 - Stop warning about unknown servers in our family when they are
29579 given as hex digests.
29580 - Stop complaining as quickly to the server operator that he
29581 hasn't registered his nickname/key binding.
29582 - Various cleanups so we can add new V2 Auth Dirservers.
29583 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
29584 reflect the updated flags in our v2 dir protocol.
29585 - Resume allowing non-printable characters for exit streams (both
29586 for connecting and for resolving). Now we tolerate applications
29587 that don't follow the RFCs. But continue to block malformed names
29590 o Bugfixes on 0.1.0.x:
29591 - Fix assert bug in close_logs(): when we close and delete logs,
29592 remove them all from the global "logfiles" list.
29593 - Fix minor integer overflow in calculating when we expect to use up
29594 our bandwidth allocation before hibernating.
29595 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
29596 there are multiple SSLs installed with different versions.
29597 - When we try to be a server and Address is not explicitly set and
29598 our hostname resolves to a private IP address, try to use an
29599 interface address if it has a public address. Now Windows machines
29600 that think of themselves as localhost can work by default.
29603 - Let the controller ask for GETINFO dir/server/foo so it can ask
29604 directly rather than connecting to the dir port.
29605 - Let the controller tell us about certain router descriptors
29606 that it doesn't want Tor to use in circuits. Implement
29607 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
29608 - New config option SafeSocks to reject all application connections
29609 using unsafe socks protocols. Defaults to off.
29612 Changes in version 0.1.1.15-rc - 2006-03-11
29613 o Bugfixes and cleanups:
29614 - When we're printing strings from the network, don't try to print
29615 non-printable characters. This protects us against shell escape
29616 sequence exploits, and also against attacks to fool humans into
29617 misreading their logs.
29618 - Fix a bug where Tor would fail to establish any connections if you
29619 left it off for 24 hours and then started it: we were happy with
29620 the obsolete network statuses, but they all referred to router
29621 descriptors that were too old to fetch, so we ended up with no
29622 valid router descriptors.
29623 - Fix a seg fault in the controller's "getinfo orconn-status"
29624 command while listing status on incoming handshaking connections.
29625 Introduce a status name "NEW" for these connections.
29626 - If we get a linelist or linelist_s config option from the torrc
29627 (e.g. ExitPolicy) and it has no value, warn and skip rather than
29628 silently resetting it to its default.
29629 - Don't abandon entry guards until they've been down or gone for
29631 - Cleaner and quieter log messages.
29634 - New controller signal NEWNYM that makes new application requests
29635 use clean circuits.
29636 - Add a new circuit purpose 'controller' to let the controller ask
29637 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
29638 controller command to let you specify the purpose if you're
29639 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
29640 command to let you change a circuit's purpose after it's been
29642 - Accept "private:*" in routerdesc exit policies; not generated yet
29643 because older Tors do not understand it.
29644 - Add BSD-style contributed startup script "rc.subr" from Peter
29648 Changes in version 0.1.1.14-alpha - 2006-02-20
29649 o Bugfixes on 0.1.1.x:
29650 - Don't die if we ask for a stdout or stderr log (even implicitly)
29651 and we're set to RunAsDaemon -- just warn.
29652 - We still had a few bugs in the OR connection rotation code that
29653 caused directory servers to slowly aggregate connections to other
29654 fast Tor servers. This time for sure!
29655 - Make log entries on Win32 include the name of the function again.
29656 - We were treating a pair of exit policies if they were equal even
29657 if one said accept and the other said reject -- causing us to
29658 not always publish a new descriptor since we thought nothing
29660 - Retry pending server downloads as well as pending networkstatus
29661 downloads when we unexpectedly get a socks request.
29662 - We were ignoring the IS_FAST flag in the directory status,
29663 meaning we were willing to pick trivial-bandwidth nodes for "fast"
29665 - If the controller's SAVECONF command fails (e.g. due to file
29666 permissions), let the controller know that it failed.
29669 - If we're trying to be a Tor server and running Windows 95/98/ME
29670 as a server, explain that we'll likely crash.
29671 - When we're a server, a client asks for an old-style directory,
29672 and our write bucket is empty, don't give it to him. This way
29673 small servers can continue to serve the directory *sometimes*,
29674 without getting overloaded.
29675 - Compress exit policies even more -- look for duplicate lines
29677 - Clients now honor the "guard" flag in the router status when
29678 picking entry guards, rather than looking at is_fast or is_stable.
29679 - Retain unrecognized lines in $DATADIR/state file, so that we can
29680 be forward-compatible.
29681 - Generate 18.0.0.0/8 address policy format in descs when we can;
29682 warn when the mask is not reducible to a bit-prefix.
29683 - Let the user set ControlListenAddress in the torrc. This can be
29684 dangerous, but there are some cases (like a secured LAN) where it
29686 - Split ReachableAddresses into ReachableDirAddresses and
29687 ReachableORAddresses, so we can restrict Dir conns to port 80
29688 and OR conns to port 443.
29689 - Now we can target arch and OS in rpm builds (contributed by
29690 Phobos). Also make the resulting dist-rpm filename match the
29692 - New config options to help controllers: FetchServerDescriptors
29693 and FetchHidServDescriptors for whether to fetch server
29694 info and hidserv info or let the controller do it, and
29695 PublishServerDescriptor and PublishHidServDescriptors.
29696 - Also let the controller set the __AllDirActionsPrivate config
29697 option if you want all directory fetches/publishes to happen via
29698 Tor (it assumes your controller bootstraps your circuits).
29701 Changes in version 0.1.0.17 - 2006-02-17
29702 o Crash bugfixes on 0.1.0.x:
29703 - When servers with a non-zero DirPort came out of hibernation,
29704 sometimes they would trigger an assert.
29706 o Other important bugfixes:
29707 - On platforms that don't have getrlimit (like Windows), we were
29708 artificially constraining ourselves to a max of 1024
29709 connections. Now just assume that we can handle as many as 15000
29710 connections. Hopefully this won't cause other problems.
29712 o Backported features:
29713 - When we're a server, a client asks for an old-style directory,
29714 and our write bucket is empty, don't give it to him. This way
29715 small servers can continue to serve the directory *sometimes*,
29716 without getting overloaded.
29717 - Whenever you get a 503 in response to a directory fetch, try
29718 once more. This will become important once servers start sending
29719 503's whenever they feel busy.
29720 - Fetch a new directory every 120 minutes, not every 40 minutes.
29721 Now that we have hundreds of thousands of users running the old
29722 directory algorithm, it's starting to hurt a lot.
29723 - Bump up the period for forcing a hidden service descriptor upload
29724 from 20 minutes to 1 hour.
29727 Changes in version 0.1.1.13-alpha - 2006-02-09
29728 o Crashes in 0.1.1.x:
29729 - When you tried to setconf ORPort via the controller, Tor would
29730 crash. So people using TorCP to become a server were sad.
29731 - Solve (I hope) the stack-smashing bug that we were seeing on fast
29732 servers. The problem appears to be something do with OpenSSL's
29733 random number generation, or how we call it, or something. Let me
29734 know if the crashes continue.
29735 - Turn crypto hardware acceleration off by default, until we find
29736 somebody smart who can test it for us. (It appears to produce
29737 seg faults in at least some cases.)
29738 - Fix a rare assert error when we've tried all intro points for
29739 a hidden service and we try fetching the service descriptor again:
29740 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
29743 - Fix a major load balance bug: we were round-robining in 16 KB
29744 chunks, and servers with bandwidthrate of 20 KB, while downloading
29745 a 600 KB directory, would starve their other connections. Now we
29746 try to be a bit more fair.
29747 - Dir authorities and mirrors were never expiring the newest
29748 descriptor for each server, causing memory and directory bloat.
29749 - Fix memory-bloating and connection-bloating bug on servers: We
29750 were never closing any connection that had ever had a circuit on
29751 it, because we were checking conn->n_circuits == 0, yet we had a
29752 bug that let it go negative.
29753 - Make Tor work using squid as your http proxy again -- squid
29754 returns an error if you ask for a URL that's too long, and it uses
29755 a really generic error message. Plus, many people are behind a
29756 transparent squid so they don't even realize it.
29757 - On platforms that don't have getrlimit (like Windows), we were
29758 artificially constraining ourselves to a max of 1024
29759 connections. Now just assume that we can handle as many as 15000
29760 connections. Hopefully this won't cause other problems.
29761 - Add a new config option ExitPolicyRejectPrivate which defaults to
29762 1. This means all exit policies will begin with rejecting private
29763 addresses, unless the server operator explicitly turns it off.
29766 - Clients no longer download descriptors for non-running
29768 - Before we add new directory authorities, we should make it
29769 clear that only v1 authorities should receive/publish hidden
29770 service descriptors.
29773 - As soon as we've fetched some more directory info, immediately
29774 try to download more server descriptors. This way we don't have
29775 a 10 second pause during initial bootstrapping.
29776 - Remove even more loud log messages that the server operator can't
29778 - When we're running an obsolete or un-recommended version, make
29779 the log message more clear about what the problem is and what
29780 versions *are* still recommended.
29781 - Provide a more useful warn message when our onion queue gets full:
29782 the CPU is too slow or the exit policy is too liberal.
29783 - Don't warn when we receive a 503 from a dirserver/cache -- this
29784 will pave the way for them being able to refuse if they're busy.
29785 - When we fail to bind a listener, try to provide a more useful
29786 log message: e.g., "Is Tor already running?"
29787 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
29788 Goldberg can prove things about our handshake protocol more
29790 - MaxConn has been obsolete for a while now. Document the ConnLimit
29791 config option, which is a *minimum* number of file descriptors
29792 that must be available else Tor refuses to start.
29793 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
29794 if you log to syslog and want something other than LOG_DAEMON.
29795 - Make dirservers generate a separate "guard" flag to mean,
29796 "would make a good entry guard". Make clients parse it and vote
29797 on it. Not used by clients yet.
29798 - Implement --with-libevent-dir option to ./configure. Also, improve
29799 search techniques to find libevent, and use those for openssl too.
29800 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
29801 - Only start testing reachability once we've established a
29802 circuit. This will make startup on dirservers less noisy.
29803 - Don't try to upload hidden service descriptors until we have
29804 established a circuit.
29805 - Fix the controller's "attachstream 0" command to treat conn like
29806 it just connected, doing address remapping, handling .exit and
29807 .onion idioms, and so on. Now we're more uniform in making sure
29808 that the controller hears about new and closing connections.
29811 Changes in version 0.1.1.12-alpha - 2006-01-11
29812 o Bugfixes on 0.1.1.x:
29813 - The fix to close duplicate server connections was closing all
29814 Tor client connections if they didn't establish a circuit
29815 quickly enough. Oops.
29816 - Fix minor memory issue (double-free) that happened on exit.
29818 o Bugfixes on 0.1.0.x:
29819 - Tor didn't warn when it failed to open a log file.
29822 Changes in version 0.1.1.11-alpha - 2006-01-10
29823 o Crashes in 0.1.1.x:
29824 - Include all the assert/crash fixes from 0.1.0.16.
29825 - If you start Tor and then quit very quickly, there were some
29826 races that tried to free things that weren't allocated yet.
29827 - Fix a rare memory stomp if you're running hidden services.
29828 - Fix segfault when specifying DirServer in config without nickname.
29829 - Fix a seg fault when you finish connecting to a server but at
29830 that moment you dump his server descriptor.
29831 - Extendcircuit and Attachstream controller commands would
29832 assert/crash if you don't give them enough arguments.
29833 - Fix an assert error when we're out of space in the connection_list
29834 and we try to post a hidden service descriptor (reported by weasel).
29835 - If you specify a relative torrc path and you set RunAsDaemon in
29836 your torrc, then it chdir()'s to the new directory. If you HUP,
29837 it tries to load the new torrc location, fails, and exits.
29838 The fix: no longer allow a relative path to torrc using -f.
29841 - Implement "entry guards": automatically choose a handful of entry
29842 nodes and stick with them for all circuits. Only pick new guards
29843 when the ones you have are unsuitable, and if the old guards
29844 become suitable again, switch back. This will increase security
29845 dramatically against certain end-point attacks. The EntryNodes
29846 config option now provides some hints about which entry guards you
29847 want to use most; and StrictEntryNodes means to only use those.
29848 - New directory logic: download by descriptor digest, not by
29849 fingerprint. Caches try to download all listed digests from
29850 authorities; clients try to download "best" digests from caches.
29851 This avoids partitioning and isolating attacks better.
29852 - Make the "stable" router flag in network-status be the median of
29853 the uptimes of running valid servers, and make clients pay
29854 attention to the network-status flags. Thus the cutoff adapts
29855 to the stability of the network as a whole, making IRC, IM, etc
29856 connections more reliable.
29859 - Tor servers with dynamic IP addresses were needing to wait 18
29860 hours before they could start doing reachability testing using
29861 the new IP address and ports. This is because they were using
29862 the internal descriptor to learn what to test, yet they were only
29863 rebuilding the descriptor once they decided they were reachable.
29864 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
29865 to download certain server descriptors, throw them away, and then
29866 fetch them again after 30 minutes. Now mirrors throw away these
29867 server descriptors so clients can't get them.
29868 - We were leaving duplicate connections to other ORs open for a week,
29869 rather than closing them once we detect a duplicate. This only
29870 really affected authdirservers, but it affected them a lot.
29871 - Spread the authdirservers' reachability testing over the entire
29872 testing interval, so we don't try to do 500 TLS's at once every
29876 - If the network is down, and we try to connect to a conn because
29877 we have a circuit in mind, and we timeout (30 seconds) because the
29878 network never answers, we were expiring the circuit, but we weren't
29879 obsoleting the connection or telling the entry_guards functions.
29880 - Some Tor servers process billions of cells per day. These statistics
29881 need to be uint64_t's.
29882 - Check for integer overflows in more places, when adding elements
29883 to smartlists. This could possibly prevent a buffer overflow
29884 on malicious huge inputs. I don't see any, but I haven't looked
29886 - ReachableAddresses kept growing new "reject *:*" lines on every
29888 - When you "setconf log" via the controller, it should remove all
29889 logs. We were automatically adding back in a "log notice stdout".
29890 - Newly bootstrapped Tor networks couldn't establish hidden service
29891 circuits until they had nodes with high uptime. Be more tolerant.
29892 - We were marking servers down when they could not answer every piece
29893 of the directory request we sent them. This was far too harsh.
29894 - Fix the torify (tsocks) config file to not use Tor for localhost
29896 - Directory authorities now go to the proper authority when asking for
29897 a networkstatus, even when they want a compressed one.
29898 - Fix a harmless bug that was causing Tor servers to log
29899 "Got an end because of misc error, but we're not an AP. Closing."
29900 - Authorities were treating their own descriptor changes as cosmetic,
29901 meaning the descriptor available in the network-status and the
29902 descriptor that clients downloaded were different.
29903 - The OS X installer was adding a symlink for tor_resolve but
29904 the binary was called tor-resolve (reported by Thomas Hardly).
29905 - Workaround a problem with some http proxies where they refuse GET
29906 requests that specify "Content-Length: 0" (reported by Adrian).
29907 - Fix wrong log message when you add a "HiddenServiceNodes" config
29908 line without any HiddenServiceDir line (reported by Chris Thomas).
29911 - Write the TorVersion into the state file so we have a prayer of
29912 keeping forward and backward compatibility.
29913 - Revive the FascistFirewall config option rather than eliminating it:
29914 now it's a synonym for ReachableAddresses *:80,*:443.
29915 - Clients choose directory servers from the network status lists,
29916 not from their internal list of router descriptors. Now they can
29917 go to caches directly rather than needing to go to authorities
29919 - Directory authorities ignore router descriptors that have only
29920 cosmetic differences: do this for 0.1.0.x servers now too.
29921 - Add a new flag to network-status indicating whether the server
29922 can answer v2 directory requests too.
29923 - Authdirs now stop whining so loudly about bad descriptors that
29924 they fetch from other dirservers. So when there's a log complaint,
29925 it's for sure from a freshly uploaded descriptor.
29926 - Reduce memory requirements in our structs by changing the order
29928 - There used to be two ways to specify your listening ports in a
29929 server descriptor: on the "router" line and with a separate "ports"
29930 line. Remove support for the "ports" line.
29931 - New config option "AuthDirRejectUnlisted" for auth dirservers as
29932 a panic button: if we get flooded with unusable servers we can
29933 revert to only listing servers in the approved-routers file.
29934 - Auth dir servers can now mark a fingerprint as "!reject" or
29935 "!invalid" in the approved-routers file (as its nickname), to
29936 refuse descriptors outright or include them but marked as invalid.
29937 - Servers store bandwidth history across restarts/crashes.
29938 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
29939 get a better idea of why their circuits failed. Not used yet.
29940 - Directory mirrors now cache up to 16 unrecognized network-status
29941 docs. Now we can add new authdirservers and they'll be cached too.
29942 - When picking a random directory, prefer non-authorities if any
29944 - New controller option "getinfo desc/all-recent" to fetch the
29945 latest server descriptor for every router that Tor knows about.
29948 Changes in version 0.1.0.16 - 2006-01-02
29949 o Crash bugfixes on 0.1.0.x:
29950 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29951 corrupting the heap, losing FDs, or crashing when we need to resize
29952 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29953 - It turns out sparc64 platforms crash on unaligned memory access
29954 too -- so detect and avoid this.
29955 - Handle truncated compressed data correctly (by detecting it and
29957 - Fix possible-but-unlikely free(NULL) in control.c.
29958 - When we were closing connections, there was a rare case that
29959 stomped on memory, triggering seg faults and asserts.
29960 - Avoid potential infinite recursion when building a descriptor. (We
29961 don't know that it ever happened, but better to fix it anyway.)
29962 - We were neglecting to unlink marked circuits from soon-to-close OR
29963 connections, which caused some rare scribbling on freed memory.
29964 - Fix a memory stomping race bug when closing the joining point of two
29965 rendezvous circuits.
29966 - Fix an assert in time parsing found by Steven Murdoch.
29968 o Other bugfixes on 0.1.0.x:
29969 - When we're doing reachability testing, provide more useful log
29970 messages so the operator knows what to expect.
29971 - Do not check whether DirPort is reachable when we are suppressing
29972 advertising it because of hibernation.
29973 - When building with -static or on Solaris, we sometimes needed -ldl.
29974 - When we're deciding whether a stream has enough circuits around
29975 that can handle it, count the freshly dirty ones and not the ones
29976 that are so dirty they won't be able to handle it.
29977 - When we're expiring old circuits, we had a logic error that caused
29978 us to close new rendezvous circuits rather than old ones.
29979 - Give a more helpful log message when you try to change ORPort via
29980 the controller: you should upgrade Tor if you want that to work.
29981 - We were failing to parse Tor versions that start with "Tor ".
29982 - Tolerate faulty streams better: when a stream fails for reason
29983 exitpolicy, stop assuming that the router is lying about his exit
29984 policy. When a stream fails for reason misc, allow it to retry just
29985 as if it was resolvefailed. When a stream has failed three times,
29986 reset its failure count so we can try again and get all three tries.
29989 Changes in version 0.1.1.10-alpha - 2005-12-11
29990 o Correctness bugfixes on 0.1.0.x:
29991 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29992 corrupting the heap, losing FDs, or crashing when we need to resize
29993 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29994 - Stop doing the complex voodoo overkill checking for insecure
29995 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
29996 - When we were closing connections, there was a rare case that
29997 stomped on memory, triggering seg faults and asserts.
29998 - We were neglecting to unlink marked circuits from soon-to-close OR
29999 connections, which caused some rare scribbling on freed memory.
30000 - When we're deciding whether a stream has enough circuits around
30001 that can handle it, count the freshly dirty ones and not the ones
30002 that are so dirty they won't be able to handle it.
30003 - Recover better from TCP connections to Tor servers that are
30004 broken but don't tell you (it happens!); and rotate TLS
30005 connections once a week.
30006 - When we're expiring old circuits, we had a logic error that caused
30007 us to close new rendezvous circuits rather than old ones.
30008 - Fix a scary-looking but apparently harmless bug where circuits
30009 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
30010 servers, and never switch to state CIRCUIT_STATE_OPEN.
30011 - When building with -static or on Solaris, we sometimes needed to
30013 - Give a useful message when people run Tor as the wrong user,
30014 rather than telling them to start chowning random directories.
30015 - We were failing to inform the controller about new .onion streams.
30017 o Security bugfixes on 0.1.0.x:
30018 - Refuse server descriptors if the fingerprint line doesn't match
30019 the included identity key. Tor doesn't care, but other apps (and
30020 humans) might actually be trusting the fingerprint line.
30021 - We used to kill the circuit when we receive a relay command we
30022 don't recognize. Now we just drop it.
30023 - Start obeying our firewall options more rigorously:
30024 . If we can't get to a dirserver directly, try going via Tor.
30025 . Don't ever try to connect (as a client) to a place our
30026 firewall options forbid.
30027 . If we specify a proxy and also firewall options, obey the
30028 firewall options even when we're using the proxy: some proxies
30029 can only proxy to certain destinations.
30030 - Fix a bug found by Lasse Overlier: when we were making internal
30031 circuits (intended to be cannibalized later for rendezvous and
30032 introduction circuits), we were picking them so that they had
30033 useful exit nodes. There was no need for this, and it actually
30034 aids some statistical attacks.
30035 - Start treating internal circuits and exit circuits separately.
30036 It's important to keep them separate because internal circuits
30037 have their last hops picked like middle hops, rather than like
30038 exit hops. So exiting on them will break the user's expectations.
30040 o Bugfixes on 0.1.1.x:
30041 - Take out the mis-feature where we tried to detect IP address
30042 flapping for people with DynDNS, and chose not to upload a new
30043 server descriptor sometimes.
30044 - Try to be compatible with OpenSSL 0.9.6 again.
30045 - Log fix: when the controller is logging about .onion addresses,
30046 sometimes it didn't include the ".onion" part of the address.
30047 - Don't try to modify options->DirServers internally -- if the
30048 user didn't specify any, just add the default ones directly to
30049 the trusted dirserver list. This fixes a bug where people running
30050 controllers would use SETCONF on some totally unrelated config
30051 option, and Tor would start yelling at them about changing their
30053 - Let the controller's redirectstream command specify a port, in
30054 case the controller wants to change that too.
30055 - When we requested a pile of server descriptors, we sometimes
30056 accidentally launched a duplicate request for the first one.
30057 - Bugfix for trackhostexits: write down the fingerprint of the
30058 chosen exit, not its nickname, because the chosen exit might not
30060 - When parsing foo.exit, if foo is unknown, and we are leaving
30061 circuits unattached, set the chosen_exit field and leave the
30062 address empty. This matters because controllers got confused
30064 - Directory authorities no longer try to download server
30065 descriptors that they know they will reject.
30067 o Features and updates:
30068 - Replace balanced trees with hash tables: this should make stuff
30069 significantly faster.
30070 - Resume using the AES counter-mode implementation that we ship,
30071 rather than OpenSSL's. Ours is significantly faster.
30072 - Many other CPU and memory improvements.
30073 - Add a new config option FastFirstHopPK (on by default) so clients
30074 do a trivial crypto handshake for their first hop, since TLS has
30075 already taken care of confidentiality and authentication.
30076 - Add a new config option TestSocks so people can see if their
30077 applications are using socks4, socks4a, socks5-with-ip, or
30078 socks5-with-hostname. This way they don't have to keep mucking
30079 with tcpdump and wondering if something got cached somewhere.
30080 - Warn when listening on a public address for socks. I suspect a
30081 lot of people are setting themselves up as open socks proxies,
30082 and they have no idea that jerks on the Internet are using them,
30083 since they simply proxy the traffic into the Tor network.
30084 - Add "private:*" as an alias in configuration for policies. Now
30085 you can simplify your exit policy rather than needing to list
30086 every single internal or nonroutable network space.
30087 - Add a new controller event type that allows controllers to get
30088 all server descriptors that were uploaded to a router in its role
30089 as authoritative dirserver.
30090 - Start shipping socks-extensions.txt, tor-doc-unix.html,
30091 tor-doc-server.html, and stylesheet.css in the tarball.
30092 - Stop shipping tor-doc.html in the tarball.
30095 Changes in version 0.1.1.9-alpha - 2005-11-15
30096 o Usability improvements:
30097 - Start calling it FooListenAddress rather than FooBindAddress,
30098 since few of our users know what it means to bind an address
30100 - Reduce clutter in server logs. We're going to try to make
30101 them actually usable now. New config option ProtocolWarnings that
30102 lets you hear about how _other Tors_ are breaking the protocol. Off
30104 - Divide log messages into logging domains. Once we put some sort
30105 of interface on this, it will let people looking at more verbose
30106 log levels specify the topics they want to hear more about.
30107 - Make directory servers return better http 404 error messages
30108 instead of a generic "Servers unavailable".
30109 - Check for even more Windows version flags when writing the platform
30110 string in server descriptors, and note any we don't recognize.
30111 - Clean up more of the OpenSSL memory when exiting, so we can detect
30112 memory leaks better.
30113 - Make directory authorities be non-versioning, non-naming by
30114 default. Now we can add new directory servers without requiring
30115 their operators to pay close attention.
30116 - When logging via syslog, include the pid whenever we provide
30117 a log entry. Suggested by Todd Fries.
30119 o Performance improvements:
30120 - Directory servers now silently throw away new descriptors that
30121 haven't changed much if the timestamps are similar. We do this to
30122 tolerate older Tor servers that upload a new descriptor every 15
30123 minutes. (It seemed like a good idea at the time.)
30124 - Inline bottleneck smartlist functions; use fast versions by default.
30125 - Add a "Map from digest to void*" abstraction digestmap_t so we
30126 can do less hex encoding/decoding. Use it in router_get_by_digest()
30127 to resolve a performance bottleneck.
30128 - Allow tor_gzip_uncompress to extract as much as possible from
30129 truncated compressed data. Try to extract as many
30130 descriptors as possible from truncated http responses (when
30131 DIR_PURPOSE_FETCH_ROUTERDESC).
30132 - Make circ->onionskin a pointer, not a static array. moria2 was using
30133 125000 circuit_t's after it had been up for a few weeks, which
30134 translates to 20+ megs of wasted space.
30135 - The private half of our EDH handshake keys are now chosen out
30136 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
30138 o Security improvements:
30139 - Start making directory caches retain old routerinfos, so soon
30140 clients can start asking by digest of descriptor rather than by
30141 fingerprint of server.
30142 - Add half our entropy from RAND_poll in OpenSSL. This knows how
30143 to use egd (if present), openbsd weirdness (if present), vms/os2
30144 weirdness (if we ever port there), and more in the future.
30146 o Bugfixes on 0.1.0.x:
30147 - Do round-robin writes of at most 16 kB per write. This might be
30148 more fair on loaded Tor servers, and it might resolve our Windows
30149 crash bug. It might also slow things down.
30150 - Our TLS handshakes were generating a single public/private
30151 keypair for the TLS context, rather than making a new one for
30152 each new connections. Oops. (But we were still rotating them
30153 periodically, so it's not so bad.)
30154 - When we were cannibalizing a circuit with a particular exit
30155 node in mind, we weren't checking to see if that exit node was
30156 already present earlier in the circuit. Oops.
30157 - When a Tor server's IP changes (e.g. from a dyndns address),
30158 upload a new descriptor so clients will learn too.
30159 - Really busy servers were keeping enough circuits open on stable
30160 connections that they were wrapping around the circuit_id
30161 space. (It's only two bytes.) This exposed a bug where we would
30162 feel free to reuse a circuit_id even if it still exists but has
30163 been marked for close. Try to fix this bug. Some bug remains.
30164 - If we would close a stream early (e.g. it asks for a .exit that
30165 we know would refuse it) but the LeaveStreamsUnattached config
30166 option is set by the controller, then don't close it.
30168 o Bugfixes on 0.1.1.8-alpha:
30169 - Fix a big pile of memory leaks, some of them serious.
30170 - Do not try to download a routerdesc if we would immediately reject
30172 - Resume inserting a newline between all router descriptors when
30173 generating (old style) signed directories, since our spec says
30175 - When providing content-type application/octet-stream for
30176 server descriptors using .z, we were leaving out the
30177 content-encoding header. Oops. (Everything tolerated this just
30178 fine, but that doesn't mean we need to be part of the problem.)
30179 - Fix a potential seg fault in getconf and getinfo using version 1
30180 of the controller protocol.
30181 - Avoid crash: do not check whether DirPort is reachable when we
30182 are suppressing it because of hibernation.
30183 - Make --hash-password not crash on exit.
30186 Changes in version 0.1.1.8-alpha - 2005-10-07
30187 o New features (major):
30188 - Clients don't download or use the directory anymore. Now they
30189 download and use network-statuses from the trusted dirservers,
30190 and fetch individual server descriptors as needed from mirrors.
30191 See dir-spec.txt for all the gory details.
30192 - Be more conservative about whether to advertise our DirPort.
30193 The main change is to not advertise if we're running at capacity
30194 and either a) we could hibernate or b) our capacity is low and
30195 we're using a default DirPort.
30196 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
30198 o New features (minor):
30199 - Try to be smart about when to retry network-status and
30200 server-descriptor fetches. Still needs some tuning.
30201 - Stop parsing, storing, or using running-routers output (but
30202 mirrors still cache and serve it).
30203 - Consider a threshold of versioning dirservers (dirservers who have
30204 an opinion about which Tor versions are still recommended) before
30205 deciding whether to warn the user that he's obsolete.
30206 - Dirservers can now reject/invalidate by key and IP, with the
30207 config options "AuthDirInvalid" and "AuthDirReject". This is
30208 useful since currently we automatically list servers as running
30209 and usable even if we know they're jerks.
30210 - Provide dire warnings to any users who set DirServer; move it out
30211 of torrc.sample and into torrc.complete.
30212 - Add MyFamily to torrc.sample in the server section.
30213 - Add nicknames to the DirServer line, so we can refer to them
30214 without requiring all our users to memorize their IP addresses.
30215 - When we get an EOF or a timeout on a directory connection, note
30216 how many bytes of serverdesc we are dropping. This will help
30217 us determine whether it is smart to parse incomplete serverdesc
30219 - Add a new function to "change pseudonyms" -- that is, to stop
30220 using any currently-dirty circuits for new streams, so we don't
30221 link new actions to old actions. Currently it's only called on
30222 HUP (or SIGNAL RELOAD).
30223 - On sighup, if UseHelperNodes changed to 1, use new circuits.
30224 - Start using RAND_bytes rather than RAND_pseudo_bytes from
30225 OpenSSL. Also, reseed our entropy every hour, not just at
30226 startup. And entropy in 512-bit chunks, not 160-bit chunks.
30228 o Fixes on 0.1.1.7-alpha:
30229 - Nobody ever implemented EVENT_ADDRMAP for control protocol
30230 version 0, so don't let version 0 controllers ask for it.
30231 - If you requested something with too many newlines via the
30232 v1 controller protocol, you could crash tor.
30233 - Fix a number of memory leaks, including some pretty serious ones.
30234 - Re-enable DirPort testing again, so Tor servers will be willing
30235 to advertise their DirPort if it's reachable.
30236 - On TLS handshake, only check the other router's nickname against
30237 its expected nickname if is_named is set.
30239 o Fixes forward-ported from 0.1.0.15:
30240 - Don't crash when we don't have any spare file descriptors and we
30241 try to spawn a dns or cpu worker.
30242 - Make the numbers in read-history and write-history into uint64s,
30243 so they don't overflow and publish negatives in the descriptor.
30245 o Fixes on 0.1.0.x:
30246 - For the OS X package's modified privoxy config file, comment
30247 out the "logfile" line so we don't log everything passed
30249 - We were whining about using socks4 or socks5-with-local-lookup
30250 even when it's an IP in the "virtual" range we designed exactly
30252 - We were leaking some memory every time the client changes IPs.
30253 - Never call free() on tor_malloc()d memory. This will help us
30254 use dmalloc to detect memory leaks.
30255 - Check for named servers when looking them up by nickname;
30256 warn when we'recalling a non-named server by its nickname;
30257 don't warn twice about the same name.
30258 - Try to list MyFamily elements by key, not by nickname, and warn
30259 if we've not heard of the server.
30260 - Make windows platform detection (uname equivalent) smarter.
30261 - It turns out sparc64 doesn't like unaligned access either.
30264 Changes in version 0.1.0.15 - 2005-09-23
30265 o Bugfixes on 0.1.0.x:
30266 - Reject ports 465 and 587 (spam targets) in default exit policy.
30267 - Don't crash when we don't have any spare file descriptors and we
30268 try to spawn a dns or cpu worker.
30269 - Get rid of IgnoreVersion undocumented config option, and make us
30270 only warn, never exit, when we're running an obsolete version.
30271 - Don't try to print a null string when your server finds itself to
30272 be unreachable and the Address config option is empty.
30273 - Make the numbers in read-history and write-history into uint64s,
30274 so they don't overflow and publish negatives in the descriptor.
30275 - Fix a minor memory leak in smartlist_string_remove().
30276 - We were only allowing ourselves to upload a server descriptor at
30277 most every 20 minutes, even if it changed earlier than that.
30278 - Clean up log entries that pointed to old URLs.
30281 Changes in version 0.1.1.7-alpha - 2005-09-14
30282 o Fixes on 0.1.1.6-alpha:
30283 - Exit servers were crashing when people asked them to make a
30284 connection to an address not in their exit policy.
30285 - Looking up a non-existent stream for a v1 control connection would
30287 - Fix a seg fault if we ask a dirserver for a descriptor by
30288 fingerprint but he doesn't know about him.
30289 - SETCONF was appending items to linelists, not clearing them.
30290 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
30291 out and refuse the setconf if it would fail.
30292 - Downgrade the dirserver log messages when whining about
30296 - Add Peter Palfrader's check-tor script to tor/contrib/
30297 It lets you easily check whether a given server (referenced by
30298 nickname) is reachable by you.
30299 - Numerous changes to move towards client-side v2 directories. Not
30302 o Fixes on 0.1.0.x:
30303 - If the user gave tor an odd number of command-line arguments,
30304 we were silently ignoring the last one. Now we complain and fail.
30305 [This wins the oldest-bug prize -- this bug has been present since
30306 November 2002, as released in Tor 0.0.0.]
30307 - Do not use unaligned memory access on alpha, mips, or mipsel.
30308 It *works*, but is very slow, so we treat them as if it doesn't.
30309 - Retry directory requests if we fail to get an answer we like
30310 from a given dirserver (we were retrying before, but only if
30311 we fail to connect).
30312 - When writing the RecommendedVersions line, sort them first.
30313 - When the client asked for a rendezvous port that the hidden
30314 service didn't want to provide, we were sending an IP address
30315 back along with the end cell. Fortunately, it was zero. But stop
30317 - Correct "your server is reachable" log entries to indicate that
30318 it was self-testing that told us so.
30321 Changes in version 0.1.1.6-alpha - 2005-09-09
30322 o Fixes on 0.1.1.5-alpha:
30323 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
30324 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
30325 - Fix bug with tor_memmem finding a match at the end of the string.
30326 - Make unit tests run without segfaulting.
30327 - Resolve some solaris x86 compile warnings.
30328 - Handle duplicate lines in approved-routers files without warning.
30329 - Fix bug where as soon as a server refused any requests due to his
30330 exit policy (e.g. when we ask for localhost and he tells us that's
30331 127.0.0.1 and he won't do it), we decided he wasn't obeying his
30332 exit policy using him for any exits.
30333 - Only do openssl hardware accelerator stuff if openssl version is
30336 o New controller features/fixes:
30337 - Add a "RESETCONF" command so you can set config options like
30338 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
30339 a config option in the torrc with no value, then it clears it
30340 entirely (rather than setting it to its default).
30341 - Add a "GETINFO config-file" to tell us where torrc is.
30342 - Avoid sending blank lines when GETINFO replies should be empty.
30343 - Add a QUIT command for the controller (for using it manually).
30344 - Fix a bug in SAVECONF that was adding default dirservers and
30345 other redundant entries to the torrc file.
30347 o Start on the new directory design:
30348 - Generate, publish, cache, serve new network-status format.
30349 - Publish individual descriptors (by fingerprint, by "all", and by
30351 - Publish client and server recommended versions separately.
30352 - Allow tor_gzip_uncompress() to handle multiple concatenated
30353 compressed strings. Serve compressed groups of router
30354 descriptors. The compression logic here could be more
30356 - Distinguish v1 authorities (all currently trusted directories)
30357 from v2 authorities (all trusted directories).
30358 - Change DirServers config line to note which dirs are v1 authorities.
30359 - Add configuration option "V1AuthoritativeDirectory 1" which
30360 moria1, moria2, and tor26 should set.
30361 - Remove option when getting directory cache to see whether they
30362 support running-routers; they all do now. Replace it with one
30363 to see whether caches support v2 stuff.
30366 - Dirservers now do their own external reachability testing of each
30367 Tor server, and only list them as running if they've been found to
30368 be reachable. We also send back warnings to the server's logs if
30369 it uploads a descriptor that we already believe is unreachable.
30370 - Implement exit enclaves: if we know an IP address for the
30371 destination, and there's a running Tor server at that address
30372 which allows exit to the destination, then extend the circuit to
30373 that exit first. This provides end-to-end encryption and end-to-end
30374 authentication. Also, if the user wants a .exit address or enclave,
30375 use 4 hops rather than 3, and cannibalize a general circ for it
30377 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
30378 controller. Also, rotate dns and cpu workers if the controller
30379 changes options that will affect them; and initialize the dns
30380 worker cache tree whether or not we start out as a server.
30381 - Only upload a new server descriptor when options change, 18
30382 hours have passed, uptime is reset, or bandwidth changes a lot.
30383 - Check [X-]Forwarded-For headers in HTTP requests when generating
30384 log messages. This lets people run dirservers (and caches) behind
30385 Apache but still know which IP addresses are causing warnings.
30387 o Config option changes:
30388 - Replace (Fascist)Firewall* config options with a new
30389 ReachableAddresses option that understands address policies.
30390 For example, "ReachableAddresses *:80,*:443"
30391 - Get rid of IgnoreVersion undocumented config option, and make us
30392 only warn, never exit, when we're running an obsolete version.
30393 - Make MonthlyAccountingStart config option truly obsolete now.
30395 o Fixes on 0.1.0.x:
30396 - Reject ports 465 and 587 in the default exit policy, since
30397 people have started using them for spam too.
30398 - It turns out we couldn't bootstrap a network since we added
30399 reachability detection in 0.1.0.1-rc. Good thing the Tor network
30400 has never gone down. Add an AssumeReachable config option to let
30401 servers and dirservers bootstrap. When we're trying to build a
30402 high-uptime or high-bandwidth circuit but there aren't enough
30403 suitable servers, try being less picky rather than simply failing.
30404 - Our logic to decide if the OR we connected to was the right guy
30405 was brittle and maybe open to a mitm for unverified routers.
30406 - We weren't cannibalizing circuits correctly for
30407 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
30408 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
30409 build those from scratch. This should make hidden services faster.
30410 - Predict required circuits better, with an eye toward making hidden
30411 services faster on the service end.
30412 - Retry streams if the exit node sends back a 'misc' failure. This
30413 should result in fewer random failures. Also, after failing
30414 from resolve failed or misc, reset the num failures, so we give
30415 it a fair shake next time we try.
30416 - Clean up the rendezvous warn log msgs, and downgrade some to info.
30417 - Reduce severity on logs about dns worker spawning and culling.
30418 - When we're shutting down and we do something like try to post a
30419 server descriptor or rendezvous descriptor, don't complain that
30420 we seem to be unreachable. Of course we are, we're shutting down.
30421 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
30422 We don't use them yet, but maybe one day our DNS resolver will be
30423 able to discover them.
30424 - Make ContactInfo mandatory for authoritative directory servers.
30425 - Require server descriptors to list IPv4 addresses -- hostnames
30426 are no longer allowed. This also fixes some potential security
30427 problems with people providing hostnames as their address and then
30428 preferentially resolving them to partition users.
30429 - Change log line for unreachability to explicitly suggest /etc/hosts
30430 as the culprit. Also make it clearer what IP address and ports we're
30431 testing for reachability.
30432 - Put quotes around user-supplied strings when logging so users are
30433 more likely to realize if they add bad characters (like quotes)
30435 - Let auth dir servers start without specifying an Address config
30437 - Make unit tests (and other invocations that aren't the real Tor)
30438 run without launching listeners, creating subdirectories, and so on.
30441 Changes in version 0.1.1.5-alpha - 2005-08-08
30442 o Bugfixes included in 0.1.0.14.
30444 o Bugfixes on 0.1.0.x:
30445 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
30446 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
30447 it would silently using ignore the 6668.
30450 Changes in version 0.1.0.14 - 2005-08-08
30451 o Bugfixes on 0.1.0.x:
30452 - Fix the other half of the bug with crypto handshakes
30454 - Fix an assert trigger if you send a 'signal term' via the
30455 controller when it's listening for 'event info' messages.
30458 Changes in version 0.1.1.4-alpha - 2005-08-04
30459 o Bugfixes included in 0.1.0.13.
30462 - Improve tor_gettimeofday() granularity on windows.
30463 - Make clients regenerate their keys when their IP address changes.
30464 - Implement some more GETINFO goodness: expose helper nodes, config
30465 options, getinfo keys.
30468 Changes in version 0.1.0.13 - 2005-08-04
30469 o Bugfixes on 0.1.0.x:
30470 - Fix a critical bug in the security of our crypto handshakes.
30471 - Fix a size_t underflow in smartlist_join_strings2() that made
30472 it do bad things when you hand it an empty smartlist.
30473 - Fix Windows installer to ship Tor license (thanks to Aphex for
30474 pointing out this oversight) and put a link to the doc directory
30476 - Explicitly set no-unaligned-access for sparc: it turns out the
30477 new gcc's let you compile broken code, but that doesn't make it
30481 Changes in version 0.1.1.3-alpha - 2005-07-23
30482 o Bugfixes on 0.1.1.2-alpha:
30483 - Fix a bug in handling the controller's "post descriptor"
30485 - Fix several bugs in handling the controller's "extend circuit"
30487 - Fix a bug in handling the controller's "stream status" event.
30488 - Fix an assert failure if we have a controller listening for
30489 circuit events and we go offline.
30490 - Re-allow hidden service descriptors to publish 0 intro points.
30491 - Fix a crash when generating your hidden service descriptor if
30492 you don't have enough intro points already.
30494 o New features on 0.1.1.2-alpha:
30495 - New controller function "getinfo accounting", to ask how
30496 many bytes we've used in this time period.
30497 - Experimental support for helper nodes: a lot of the risk from
30498 a small static adversary comes because users pick new random
30499 nodes every time they rebuild a circuit. Now users will try to
30500 stick to the same small set of entry nodes if they can. Not
30501 enabled by default yet.
30503 o Bugfixes on 0.1.0.12:
30504 - If you're an auth dir server, always publish your dirport,
30505 even if you haven't yet found yourself to be reachable.
30506 - Fix a size_t underflow in smartlist_join_strings2() that made
30507 it do bad things when you hand it an empty smartlist.
30510 Changes in version 0.1.0.12 - 2005-07-18
30511 o New directory servers:
30512 - tor26 has changed IP address.
30514 o Bugfixes on 0.1.0.x:
30515 - Fix a possible double-free in tor_gzip_uncompress().
30516 - When --disable-threads is set, do not search for or link against
30517 pthreads libraries.
30518 - Don't trigger an assert if an authoritative directory server
30519 claims its dirport is 0.
30520 - Fix bug with removing Tor as an NT service: some people were
30521 getting "The service did not return an error." Thanks to Matt
30525 Changes in version 0.1.1.2-alpha - 2005-07-15
30526 o New directory servers:
30527 - tor26 has changed IP address.
30529 o Bugfixes on 0.1.0.x, crashes/leaks:
30530 - Port the servers-not-obeying-their-exit-policies fix from
30532 - Fix an fd leak in start_daemon().
30533 - On Windows, you can't always reopen a port right after you've
30534 closed it. So change retry_listeners() to only close and re-open
30535 ports that have changed.
30536 - Fix a possible double-free in tor_gzip_uncompress().
30538 o Bugfixes on 0.1.0.x, usability:
30539 - When tor_socketpair() fails in Windows, give a reasonable
30540 Windows-style errno back.
30541 - Let people type "tor --install" as well as "tor -install" when
30543 want to make it an NT service.
30544 - NT service patch from Matt Edman to improve error messages.
30545 - When the controller asks for a config option with an abbreviated
30546 name, give the full name in our response.
30547 - Correct the man page entry on TrackHostExitsExpire.
30548 - Looks like we were never delivering deflated (i.e. compressed)
30549 running-routers lists, even when asked. Oops.
30550 - When --disable-threads is set, do not search for or link against
30551 pthreads libraries.
30553 o Bugfixes on 0.1.1.x:
30554 - Fix a seg fault with autodetecting which controller version is
30558 - New hidden service descriptor format: put a version in it, and
30559 let people specify introduction/rendezvous points that aren't
30560 in "the directory" (which is subjective anyway).
30561 - Allow the DEBUG controller event to work again. Mark certain log
30562 entries as "don't tell this to controllers", so we avoid cycles.
30565 Changes in version 0.1.0.11 - 2005-06-30
30566 o Bugfixes on 0.1.0.x:
30567 - Fix major security bug: servers were disregarding their
30568 exit policies if clients behaved unexpectedly.
30569 - Make OS X init script check for missing argument, so we don't
30570 confuse users who invoke it incorrectly.
30571 - Fix a seg fault in "tor --hash-password foo".
30572 - The MAPADDRESS control command was broken.
30575 Changes in version 0.1.1.1-alpha - 2005-06-29
30577 - Make OS X init script check for missing argument, so we don't
30578 confuse users who invoke it incorrectly.
30579 - Fix a seg fault in "tor --hash-password foo".
30580 - Fix a possible way to DoS dirservers.
30581 - When we complain that your exit policy implicitly allows local or
30582 private address spaces, name them explicitly so operators can
30584 - Make the log message less scary when all the dirservers are
30585 temporarily unreachable.
30586 - We were printing the number of idle dns workers incorrectly when
30590 - Revised controller protocol (version 1) that uses ascii rather
30591 than binary. Add supporting libraries in python and java so you
30592 can use the controller from your applications without caring how
30593 our protocol works.
30594 - Spiffy new support for crypto hardware accelerators. Can somebody
30598 Changes in version 0.0.9.10 - 2005-06-16
30599 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
30600 - Refuse relay cells that claim to have a length larger than the
30601 maximum allowed. This prevents a potential attack that could read
30602 arbitrary memory (e.g. keys) from an exit server's process
30606 Changes in version 0.1.0.10 - 2005-06-14
30607 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
30608 libevent before 1.1a.
30611 Changes in version 0.1.0.9-rc - 2005-06-09
30613 - Reset buf->highwater every time buf_shrink() is called, not just on
30614 a successful shrink. This was causing significant memory bloat.
30615 - Fix buffer overflow when checking hashed passwords.
30616 - Security fix: if seeding the RNG on Win32 fails, quit.
30617 - Allow seeding the RNG on Win32 even when you're not running as
30619 - Disable threading on Solaris too. Something is wonky with it,
30620 cpuworkers, and reentrant libs.
30621 - Reenable the part of the code that tries to flush as soon as an
30622 OR outbuf has a full TLS record available. Perhaps this will make
30623 OR outbufs not grow as huge except in rare cases, thus saving lots
30624 of CPU time plus memory.
30625 - Reject malformed .onion addresses rather then passing them on as
30626 normal web requests.
30627 - Adapt patch from Adam Langley: fix possible memory leak in
30628 tor_lookup_hostname().
30629 - Initialize libevent later in the startup process, so the logs are
30630 already established by the time we start logging libevent warns.
30631 - Use correct errno on win32 if libevent fails.
30632 - Check and warn about known-bad/slow libevent versions.
30633 - Pay more attention to the ClientOnly config option.
30634 - Have torctl.in/tor.sh.in check for location of su binary (needed
30636 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
30637 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
30638 HttpProxyAuthenticator
30639 - Stop warning about sigpipes in the logs. We're going to
30640 pretend that getting these occasionally is normal and fine.
30641 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
30643 installer screens; and don't put stuff into StartupItems unless
30644 the user asks you to.
30645 - Require servers that use the default dirservers to have public IP
30646 addresses. We have too many servers that are configured with private
30647 IPs and their admins never notice the log entries complaining that
30648 their descriptors are being rejected.
30649 - Add OSX uninstall instructions. An actual uninstall script will
30653 Changes in version 0.1.0.8-rc - 2005-05-23
30655 - It turns out that kqueue on OS X 10.3.9 was causing kernel
30656 panics. Disable kqueue on all OS X Tors.
30657 - Fix RPM: remove duplicate line accidentally added to the rpm
30659 - Disable threads on openbsd too, since its gethostaddr is not
30661 - Tolerate libevent 0.8 since it still works, even though it's
30663 - Enable building on Red Hat 9.0 again.
30664 - Allow the middle hop of the testing circuit to be running any
30665 version, now that most of them have the bugfix to let them connect
30666 to unknown servers. This will allow reachability testing to work
30667 even when 0.0.9.7-0.0.9.9 become obsolete.
30668 - Handle relay cells with rh.length too large. This prevents
30669 a potential attack that could read arbitrary memory (maybe even
30670 keys) from the exit server's process.
30671 - We screwed up the dirport reachability testing when we don't yet
30672 have a cached version of the directory. Hopefully now fixed.
30673 - Clean up router_load_single_router() (used by the controller),
30674 so it doesn't seg fault on error.
30675 - Fix a minor memory leak when somebody establishes an introduction
30676 point at your Tor server.
30677 - If a socks connection ends because read fails, don't warn that
30678 you're not sending a socks reply back.
30681 - Add HttpProxyAuthenticator config option too, that works like
30682 the HttpsProxyAuthenticator config option.
30683 - Encode hashed controller passwords in hex instead of base64,
30684 to make it easier to write controllers.
30687 Changes in version 0.1.0.7-rc - 2005-05-17
30689 - Fix a bug in the OS X package installer that prevented it from
30690 installing on Tiger.
30691 - Fix a script bug in the OS X package installer that made it
30692 complain during installation.
30693 - Find libevent even if it's hiding in /usr/local/ and your
30694 CFLAGS and LDFLAGS don't tell you to look there.
30695 - Be able to link with libevent as a shared library (the default
30696 after 1.0d), even if it's hiding in /usr/local/lib and even
30697 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
30698 assuming you're running gcc. Otherwise fail and give a useful
30700 - Fix a bug in the RPM packager: set home directory for _tor to
30701 something more reasonable when first installing.
30702 - Free a minor amount of memory that is still reachable on exit.
30705 Changes in version 0.1.0.6-rc - 2005-05-14
30707 - Implement --disable-threads configure option. Disable threads on
30708 netbsd by default, because it appears to have no reentrant resolver
30710 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
30711 release (1.1) detects and disables kqueue if it's broken.
30712 - Append default exit policy before checking for implicit internal
30713 addresses. Now we don't log a bunch of complaints on startup
30714 when using the default exit policy.
30715 - Some people were putting "Address " in their torrc, and they had
30716 a buggy resolver that resolved " " to 0.0.0.0. Oops.
30717 - If DataDir is ~/.tor, and that expands to /.tor, then default to
30718 LOCALSTATEDIR/tor instead.
30719 - Fix fragmented-message bug in TorControl.py.
30720 - Resolve a minor bug which would prevent unreachable dirports
30721 from getting suppressed in the published descriptor.
30722 - When the controller gave us a new descriptor, we weren't resolving
30723 it immediately, so Tor would think its address was 0.0.0.0 until
30724 we fetched a new directory.
30725 - Fix an uppercase/lowercase case error in suppressing a bogus
30726 libevent warning on some Linuxes.
30729 - Begin scrubbing sensitive strings from logs by default. Turn off
30730 the config option SafeLogging if you need to do debugging.
30731 - Switch to a new buffer management algorithm, which tries to avoid
30732 reallocing and copying quite as much. In first tests it looks like
30733 it uses *more* memory on average, but less cpu.
30734 - First cut at support for "create-fast" cells. Clients can use
30735 these when extending to their first hop, since the TLS already
30736 provides forward secrecy and authentication. Not enabled on
30738 - When dirservers refuse a router descriptor, we now log its
30739 contactinfo, platform, and the poster's IP address.
30740 - Call tor_free_all instead of connections_free_all after forking, to
30741 save memory on systems that need to fork.
30742 - Whine at you if you're a server and you don't set your contactinfo.
30743 - Implement --verify-config command-line option to check if your torrc
30744 is valid without actually launching Tor.
30745 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
30746 rather than just rejecting it.
30749 Changes in version 0.1.0.5-rc - 2005-04-27
30751 - Stop trying to print a null pointer if an OR conn fails because
30752 we didn't like its cert.
30754 - Switch our internal buffers implementation to use a ring buffer,
30755 to hopefully improve performance for fast servers a lot.
30756 - Add HttpsProxyAuthenticator support (basic auth only), based
30757 on patch from Adam Langley.
30758 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
30759 the fast servers that have been joining lately.
30760 - Give hidden service accesses extra time on the first attempt,
30761 since 60 seconds is often only barely enough. This might improve
30763 - Improve performance for dirservers: stop re-parsing the whole
30764 directory every time you regenerate it.
30765 - Add more debugging info to help us find the weird dns freebsd
30766 pthreads bug; cleaner debug messages to help track future issues.
30769 Changes in version 0.0.9.9 - 2005-04-23
30770 o Bugfixes on 0.0.9.x:
30771 - If unofficial Tor clients connect and send weird TLS certs, our
30772 Tor server triggers an assert. This release contains a minimal
30773 backport from the broader fix that we put into 0.1.0.4-rc.
30776 Changes in version 0.1.0.4-rc - 2005-04-23
30778 - If unofficial Tor clients connect and send weird TLS certs, our
30779 Tor server triggers an assert. Stop asserting, and start handling
30780 TLS errors better in other situations too.
30781 - When the controller asks us to tell it about all the debug-level
30782 logs, it turns out we were generating debug-level logs while
30783 telling it about them, which turns into a bad loop. Now keep
30784 track of whether you're sending a debug log to the controller,
30785 and don't log when you are.
30786 - Fix the "postdescriptor" feature of the controller interface: on
30787 non-complete success, only say "done" once.
30789 - Clients are now willing to load balance over up to 2mB, not 1mB,
30790 of advertised bandwidth capacity.
30791 - Add a NoPublish config option, so you can be a server (e.g. for
30792 testing running Tor servers in other Tor networks) without
30793 publishing your descriptor to the primary dirservers.
30796 Changes in version 0.1.0.3-rc - 2005-04-08
30797 o Improvements on 0.1.0.2-rc:
30798 - Client now retries when streams end early for 'hibernating' or
30799 'resource limit' reasons, rather than failing them.
30800 - More automated handling for dirserver operators:
30801 - Automatically approve nodes running 0.1.0.2-rc or later,
30802 now that the the reachability detection stuff is working.
30803 - Now we allow two unverified servers with the same nickname
30804 but different keys. But if a nickname is verified, only that
30805 nickname+key are allowed.
30806 - If you're an authdirserver connecting to an address:port,
30807 and it's not the OR you were expecting, forget about that
30808 descriptor. If he *was* the one you were expecting, then forget
30809 about all other descriptors for that address:port.
30810 - Allow servers to publish descriptors from 12 hours in the future.
30811 Corollary: only whine about clock skew from the dirserver if
30812 he's a trusted dirserver (since now even verified servers could
30813 have quite wrong clocks).
30814 - Adjust maximum skew and age for rendezvous descriptors: let skew
30815 be 48 hours rather than 90 minutes.
30816 - Efficiency improvements:
30817 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
30818 it much faster to look up a circuit for each relay cell.
30819 - Remove most calls to assert_all_pending_dns_resolves_ok(),
30820 since they're eating our cpu on exit nodes.
30821 - Stop wasting time doing a case insensitive comparison for every
30822 dns name every time we do any lookup. Canonicalize the names to
30823 lowercase and be done with it.
30824 - Start sending 'truncated' cells back rather than destroy cells,
30825 if the circuit closes in front of you. This means we won't have
30826 to abandon partially built circuits.
30827 - Only warn once per nickname from add_nickname_list_to_smartlist
30828 per failure, so an entrynode or exitnode choice that's down won't
30830 - Put a note in the torrc about abuse potential with the default
30832 - Revise control spec and implementation to allow all log messages to
30833 be sent to controller with their severities intact (suggested by
30834 Matt Edman). Update TorControl to handle new log event types.
30835 - Provide better explanation messages when controller's POSTDESCRIPTOR
30837 - Stop putting nodename in the Platform string in server descriptors.
30838 It doesn't actually help, and it is confusing/upsetting some people.
30840 o Bugfixes on 0.1.0.2-rc:
30841 - We were printing the host mask wrong in exit policies in server
30842 descriptors. This isn't a critical bug though, since we were still
30843 obeying the exit policy internally.
30844 - Fix Tor when compiled with libevent but without pthreads: move
30845 connection_unregister() from _connection_free() to
30847 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
30848 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
30849 when we look through the connection array, we'll find any of the
30850 cpu/dnsworkers. This is no good.
30852 o Bugfixes on 0.0.9.8:
30853 - Fix possible bug on threading platforms (e.g. win32) which was
30854 leaking a file descriptor whenever a cpuworker or dnsworker died.
30855 - When using preferred entry or exit nodes, ignore whether the
30856 circuit wants uptime or capacity. They asked for the nodes, they
30858 - chdir() to your datadirectory at the *end* of the daemonize process,
30859 not the beginning. This was a problem because the first time you
30860 run tor, if your datadir isn't there, and you have runasdaemon set
30861 to 1, it will try to chdir to it before it tries to create it. Oops.
30862 - Handle changed router status correctly when dirserver reloads
30863 fingerprint file. We used to be dropping all unverified descriptors
30864 right then. The bug was hidden because we would immediately
30865 fetch a directory from another dirserver, which would include the
30866 descriptors we just dropped.
30867 - When we're connecting to an OR and he's got a different nickname/key
30868 than we were expecting, only complain loudly if we're an OP or a
30869 dirserver. Complaining loudly to the OR admins just confuses them.
30870 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
30871 artificially capped at 500kB.
30874 Changes in version 0.0.9.8 - 2005-04-07
30875 o Bugfixes on 0.0.9.x:
30876 - We have a bug that I haven't found yet. Sometimes, very rarely,
30877 cpuworkers get stuck in the 'busy' state, even though the cpuworker
30878 thinks of itself as idle. This meant that no new circuits ever got
30879 established. Here's a workaround to kill any cpuworker that's been
30880 busy for more than 100 seconds.
30883 Changes in version 0.1.0.2-rc - 2005-04-01
30884 o Bugfixes on 0.1.0.1-rc:
30885 - Fixes on reachability detection:
30886 - Don't check for reachability while hibernating.
30887 - If ORPort is reachable but DirPort isn't, still publish the
30888 descriptor, but zero out DirPort until it's found reachable.
30889 - When building testing circs for ORPort testing, use only
30890 high-bandwidth nodes, so fewer circuits fail.
30891 - Complain about unreachable ORPort separately from unreachable
30892 DirPort, so the user knows what's going on.
30893 - Make sure we only conclude ORPort reachability if we didn't
30894 initiate the conn. Otherwise we could falsely conclude that
30895 we're reachable just because we connected to the guy earlier
30896 and he used that same pipe to extend to us.
30897 - Authdirservers shouldn't do ORPort reachability detection,
30898 since they're in clique mode, so it will be rare to find a
30899 server not already connected to them.
30900 - When building testing circuits, always pick middle hops running
30901 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
30902 bug. (This is a kludge; it will go away when 0.0.9.x becomes
30904 - When we decide we're reachable, actually publish our descriptor
30906 - Fix bug in redirectstream in the controller.
30907 - Fix the state descriptor strings so logs don't claim edge streams
30908 are in a different state than they actually are.
30909 - Use recent libevent features when possible (this only really affects
30910 win32 and osx right now, because the new libevent with these
30911 features hasn't been released yet). Add code to suppress spurious
30913 - Prevent possible segfault in connection_close_unattached_ap().
30914 - Fix newlines on torrc in win32.
30915 - Improve error msgs when tor-resolve fails.
30917 o Improvements on 0.0.9.x:
30918 - New experimental script tor/contrib/ExerciseServer.py (needs more
30919 work) that uses the controller interface to build circuits and
30920 fetch pages over them. This will help us bootstrap servers that
30921 have lots of capacity but haven't noticed it yet.
30922 - New experimental script tor/contrib/PathDemo.py (needs more work)
30923 that uses the controller interface to let you choose whole paths
30925 "<hostname>.<path,separated by dots>.<length of path>.path"
30926 - When we've connected to an OR and handshaked but didn't like
30927 the result, we were closing the conn without sending destroy
30928 cells back for pending circuits. Now send those destroys.
30931 Changes in version 0.0.9.7 - 2005-04-01
30932 o Bugfixes on 0.0.9.x:
30933 - Fix another race crash bug (thanks to Glenn Fink for reporting).
30934 - Compare identity to identity, not to nickname, when extending to
30935 a router not already in the directory. This was preventing us from
30936 extending to unknown routers. Oops.
30937 - Make sure to create OS X Tor user in <500 range, so we aren't
30938 creating actual system users.
30939 - Note where connection-that-hasn't-sent-end was marked, and fix
30940 a few really loud instances of this harmless bug (it's fixed more
30944 Changes in version 0.1.0.1-rc - 2005-03-28
30946 - Add reachability testing. Your Tor server will automatically try
30947 to see if its ORPort and DirPort are reachable from the outside,
30948 and it won't upload its descriptor until it decides they are.
30949 - Handle unavailable hidden services better. Handle slow or busy
30950 hidden services better.
30951 - Add support for CONNECTing through https proxies, with "HttpsProxy"
30953 - New exit policy: accept most low-numbered ports, rather than
30954 rejecting most low-numbered ports.
30955 - More Tor controller support (still experimental). See
30956 http://tor.eff.org/doc/control-spec.txt for all the new features,
30957 including signals to emulate unix signals from any platform;
30958 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
30959 closestream; closecircuit; etc.
30960 - Make nt services work and start on startup on win32 (based on
30961 patch by Matt Edman).
30962 - Add a new AddressMap config directive to rewrite incoming socks
30963 addresses. This lets you, for example, declare an implicit
30964 required exit node for certain sites.
30965 - Add a new TrackHostExits config directive to trigger addressmaps
30966 for certain incoming socks addresses -- for sites that break when
30967 your exit keeps changing (based on patch by Mike Perry).
30968 - Redo the client-side dns cache so it's just an addressmap too.
30969 - Notice when our IP changes, and reset stats/uptime/reachability.
30970 - When an application is using socks5, give him the whole variety of
30971 potential socks5 responses (connect refused, host unreachable, etc),
30972 rather than just "success" or "failure".
30973 - A more sane version numbering system. See
30974 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
30975 - New contributed script "exitlist": a simple python script to
30976 parse directories and find Tor nodes that exit to listed
30978 - New contributed script "privoxy-tor-toggle" to toggle whether
30979 Privoxy uses Tor. Seems to be configured for Debian by default.
30980 - Report HTTP reasons to client when getting a response from directory
30981 servers -- so you can actually know what went wrong.
30982 - New config option MaxAdvertisedBandwidth which lets you advertise
30983 a low bandwidthrate (to not attract as many circuits) while still
30984 allowing a higher bandwidthrate in reality.
30986 o Robustness/stability fixes:
30987 - Make Tor use Niels Provos's libevent instead of its current
30988 poll-but-sometimes-select mess. This will let us use faster async
30989 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
30991 - pthread support now too. This was forced because when we forked,
30992 we ended up wasting a lot of duplicate ram over time. Also switch
30993 to foo_r versions of some library calls to allow reentry and
30995 - Better handling for heterogeneous / unreliable nodes:
30996 - Annotate circuits w/ whether they aim to contain high uptime nodes
30997 and/or high capacity nodes. When building circuits, choose
30999 - This means that every single node in an intro rend circuit,
31000 not just the last one, will have a minimum uptime.
31001 - New config option LongLivedPorts to indicate application streams
31002 that will want high uptime circuits.
31003 - Servers reset uptime when a dir fetch entirely fails. This
31004 hopefully reflects stability of the server's network connectivity.
31005 - If somebody starts his tor server in Jan 2004 and then fixes his
31006 clock, don't make his published uptime be a year.
31007 - Reset published uptime when you wake up from hibernation.
31008 - Introduce a notion of 'internal' circs, which are chosen without
31009 regard to the exit policy of the last hop. Intro and rendezvous
31010 circs must be internal circs, to avoid leaking information. Resolve
31011 and connect streams can use internal circs if they want.
31012 - New circuit pooling algorithm: make sure to have enough circs around
31013 to satisfy any predicted ports, and also make sure to have 2 internal
31014 circs around if we've required internal circs lately (and with high
31015 uptime if we've seen that lately too).
31016 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
31017 which describes how often we retry making new circuits if current
31018 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
31019 how long we're willing to make use of an already-dirty circuit.
31020 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
31021 circ as necessary, if there are any completed ones lying around
31022 when we try to launch one.
31023 - Make hidden services try to establish a rendezvous for 30 seconds,
31024 rather than for n (where n=3) attempts to build a circuit.
31025 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
31026 "ShutdownWaitLength".
31027 - Try to be more zealous about calling connection_edge_end when
31028 things go bad with edge conns in connection.c.
31029 - Revise tor-spec to add more/better stream end reasons.
31030 - Revise all calls to connection_edge_end to avoid sending "misc",
31031 and to take errno into account where possible.
31034 - Fix a race condition that can trigger an assert, when we have a
31035 pending create cell and an OR connection fails right then.
31036 - Fix several double-mark-for-close bugs, e.g. where we were finding
31037 a conn for a cell even if that conn is already marked for close.
31038 - Make sequence of log messages when starting on win32 with no config
31039 file more reasonable.
31040 - When choosing an exit node for a new non-internal circ, don't take
31041 into account whether it'll be useful for any pending x.onion
31042 addresses -- it won't.
31043 - Turn addr_policy_compare from a tristate to a quadstate; this should
31044 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
31045 for google.com" problem.
31046 - Make "platform" string in descriptor more accurate for Win32 servers,
31047 so it's not just "unknown platform".
31048 - Fix an edge case in parsing config options (thanks weasel).
31049 If they say "--" on the commandline, it's not an option.
31050 - Reject odd-looking addresses at the client (e.g. addresses that
31051 contain a colon), rather than having the server drop them because
31053 - tor-resolve requests were ignoring .exit if there was a working circuit
31054 they could use instead.
31055 - REUSEADDR on normal platforms means you can rebind to the port
31056 right after somebody else has let it go. But REUSEADDR on win32
31057 means to let you bind to the port _even when somebody else
31058 already has it bound_! So, don't do that on Win32.
31059 - Change version parsing logic: a version is "obsolete" if it is not
31060 recommended and (1) there is a newer recommended version in the
31061 same series, or (2) there are no recommended versions in the same
31062 series, but there are some recommended versions in a newer series.
31063 A version is "new" if it is newer than any recommended version in
31065 - Stop most cases of hanging up on a socks connection without sending
31069 - Require BandwidthRate to be at least 20kB/s for servers.
31070 - When a dirserver causes you to give a warn, mention which dirserver
31072 - New config option DirAllowPrivateAddresses for authdirservers.
31073 Now by default they refuse router descriptors that have non-IP or
31074 private-IP addresses.
31075 - Stop publishing socksport in the directory, since it's not
31076 actually meant to be public. For compatibility, publish a 0 there
31078 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
31079 smart" value, that is low for servers and high for clients.
31080 - If our clock jumps forward by 100 seconds or more, assume something
31081 has gone wrong with our network and abandon all not-yet-used circs.
31082 - Warn when exit policy implicitly allows local addresses.
31083 - If we get an incredibly skewed timestamp from a dirserver mirror
31084 that isn't a verified OR, don't warn -- it's probably him that's
31086 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
31087 cookies to disk and doesn't log each web request to disk. (Thanks
31088 to Brett Carrington for pointing this out.)
31089 - When a client asks us for a dir mirror and we don't have one,
31090 launch an attempt to get a fresh one.
31091 - If we're hibernating and we get a SIGINT, exit immediately.
31092 - Add --with-dmalloc ./configure option, to track memory leaks.
31093 - And try to free all memory on closing, so we can detect what
31095 - Cache local dns resolves correctly even when they're .exit
31097 - Give a better warning when some other server advertises an
31098 ORPort that is actually an apache running ssl.
31099 - Add "opt hibernating 1" to server descriptor to make it clearer
31100 whether the server is hibernating.
31103 Changes in version 0.0.9.6 - 2005-03-24
31104 o Bugfixes on 0.0.9.x (crashes and asserts):
31105 - Add new end stream reasons to maintenance branch. Fix bug where
31106 reason (8) could trigger an assert. Prevent bug from recurring.
31107 - Apparently win32 stat wants paths to not end with a slash.
31108 - Fix assert triggers in assert_cpath_layer_ok(), where we were
31109 blowing away the circuit that conn->cpath_layer points to, then
31110 checking to see if the circ is well-formed. Backport check to make
31111 sure we dont use the cpath on a closed connection.
31112 - Prevent circuit_resume_edge_reading_helper() from trying to package
31113 inbufs for marked-for-close streams.
31114 - Don't crash on hup if your options->address has become unresolvable.
31115 - Some systems (like OS X) sometimes accept() a connection and tell
31116 you the remote host is 0.0.0.0:0. If this happens, due to some
31117 other mis-features, we get confused; so refuse the conn for now.
31119 o Bugfixes on 0.0.9.x (other):
31120 - Fix harmless but scary "Unrecognized content encoding" warn message.
31121 - Add new stream error reason: TORPROTOCOL reason means "you are not
31122 speaking a version of Tor I understand; say bye-bye to your stream."
31123 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
31124 into the future, now that we are more tolerant of skew. This
31125 resolves a bug where a Tor server would refuse to cache a directory
31126 because all the directories it gets are too far in the future;
31127 yet the Tor server never logs any complaints about clock skew.
31128 - Mac packaging magic: make man pages useable, and do not overwrite
31129 existing torrc files.
31130 - Make OS X log happily to /var/log/tor/tor.log
31133 Changes in version 0.0.9.5 - 2005-02-22
31134 o Bugfixes on 0.0.9.x:
31135 - Fix an assert race at exit nodes when resolve requests fail.
31136 - Stop picking unverified dir mirrors--it only leads to misery.
31137 - Patch from Matt Edman to make NT services work better. Service
31138 support is still not compiled into the executable by default.
31139 - Patch from Dmitri Bely so the Tor service runs better under
31140 the win32 SYSTEM account.
31141 - Make tor-resolve actually work (?) on Win32.
31142 - Fix a sign bug when getrlimit claims to have 4+ billion
31143 file descriptors available.
31144 - Stop refusing to start when bandwidthburst == bandwidthrate.
31145 - When create cells have been on the onion queue more than five
31146 seconds, just send back a destroy and take them off the list.
31149 Changes in version 0.0.9.4 - 2005-02-03
31150 o Bugfixes on 0.0.9:
31151 - Fix an assert bug that took down most of our servers: when
31152 a server claims to have 1 GB of bandwidthburst, don't
31154 - Don't crash as badly if we have spawned the max allowed number
31155 of dnsworkers, or we're out of file descriptors.
31156 - Block more file-sharing ports in the default exit policy.
31157 - MaxConn is now automatically set to the hard limit of max
31158 file descriptors we're allowed (ulimit -n), minus a few for
31160 - Give a clearer message when servers need to raise their
31161 ulimit -n when they start running out of file descriptors.
31162 - SGI Compatibility patches from Jan Schaumann.
31163 - Tolerate a corrupt cached directory better.
31164 - When a dirserver hasn't approved your server, list which one.
31165 - Go into soft hibernation after 95% of the bandwidth is used,
31166 not 99%. This is especially important for daily hibernators who
31167 have a small accounting max. Hopefully it will result in fewer
31168 cut connections when the hard hibernation starts.
31169 - Load-balance better when using servers that claim more than
31170 800kB/s of capacity.
31171 - Make NT services work (experimental, only used if compiled in).
31174 Changes in version 0.0.9.3 - 2005-01-21
31175 o Bugfixes on 0.0.9:
31176 - Backport the cpu use fixes from main branch, so busy servers won't
31177 need as much processor time.
31178 - Work better when we go offline and then come back, or when we
31179 run Tor at boot before the network is up. We do this by
31180 optimistically trying to fetch a new directory whenever an
31181 application request comes in and we think we're offline -- the
31182 human is hopefully a good measure of when the network is back.
31183 - Backport some minimal hidserv bugfixes: keep rend circuits open as
31184 long as you keep using them; actually publish hidserv descriptors
31185 shortly after they change, rather than waiting 20-40 minutes.
31186 - Enable Mac startup script by default.
31187 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
31188 - When you update AllowUnverifiedNodes or FirewallPorts via the
31189 controller's setconf feature, we were always appending, never
31191 - When you update HiddenServiceDir via setconf, it was screwing up
31192 the order of reading the lines, making it fail.
31193 - Do not rewrite a cached directory back to the cache; otherwise we
31194 will think it is recent and not fetch a newer one on startup.
31195 - Workaround for webservers that lie about Content-Encoding: Tor
31196 now tries to autodetect compressed directories and compression
31197 itself. This lets us Proxypass dir fetches through apache.
31200 Changes in version 0.0.9.2 - 2005-01-04
31201 o Bugfixes on 0.0.9 (crashes and asserts):
31202 - Fix an assert on startup when the disk is full and you're logging
31204 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
31205 style address, then we'd crash.
31206 - Fix an assert trigger when the running-routers string we get from
31207 a dirserver is broken.
31208 - Make worker threads start and run on win32. Now win32 servers
31210 - Bandaid (not actually fix, but now it doesn't crash) an assert
31211 where the dns worker dies mysteriously and the main Tor process
31212 doesn't remember anything about the address it was resolving.
31214 o Bugfixes on 0.0.9 (Win32):
31215 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
31216 name out of the warning/assert messages.
31217 - Fix a superficial "unhandled error on read" bug on win32.
31218 - The win32 installer no longer requires a click-through for our
31219 license, since our Free Software license grants rights but does not
31221 - Win32: When connecting to a dirserver fails, try another one
31222 immediately. (This was already working for non-win32 Tors.)
31223 - Stop trying to parse $HOME on win32 when hunting for default
31225 - Make tor-resolve.c work on win32 by calling network_init().
31227 o Bugfixes on 0.0.9 (other):
31228 - Make 0.0.9.x build on Solaris again.
31229 - Due to a fencepost error, we were blowing away the \n when reporting
31230 confvalue items in the controller. So asking for multiple config
31231 values at once couldn't work.
31232 - When listing circuits that are pending on an opening OR connection,
31233 if we're an OR we were listing circuits that *end* at us as
31234 being pending on every listener, dns/cpu worker, etc. Stop that.
31235 - Dirservers were failing to create 'running-routers' or 'directory'
31236 strings if we had more than some threshold of routers. Fix them so
31237 they can handle any number of routers.
31238 - Fix a superficial "Duplicate mark for close" bug.
31239 - Stop checking for clock skew for OR connections, even for servers.
31240 - Fix a fencepost error that was chopping off the last letter of any
31241 nickname that is the maximum allowed nickname length.
31242 - Update URLs in log messages so they point to the new website.
31243 - Fix a potential problem in mangling server private keys while
31244 writing to disk (not triggered yet, as far as we know).
31245 - Include the licenses for other free software we include in Tor,
31246 now that we're shipping binary distributions more regularly.
31249 Changes in version 0.0.9.1 - 2004-12-15
31250 o Bugfixes on 0.0.9:
31251 - Make hibernation actually work.
31252 - Make HashedControlPassword config option work.
31253 - When we're reporting event circuit status to a controller,
31254 don't use the stream status code.
31257 Changes in version 0.0.9 - 2004-12-12
31259 - Clean up manpage and torrc.sample file.
31260 - Clean up severities and text of log warnings.
31262 - Make servers trigger an assert when they enter hibernation.
31265 Changes in version 0.0.9rc7 - 2004-12-08
31266 o Bugfixes on 0.0.9rc:
31267 - Fix a stack-trashing crash when an exit node begins hibernating.
31268 - Avoid looking at unallocated memory while considering which
31269 ports we need to build circuits to cover.
31270 - Stop a sigpipe: when an 'end' cell races with eof from the app,
31271 we shouldn't hold-open-until-flush if the eof arrived first.
31272 - Fix a bug with init_cookie_authentication() in the controller.
31273 - When recommending new-format log lines, if the upper bound is
31274 LOG_ERR, leave it implicit.
31276 o Bugfixes on 0.0.8.1:
31277 - Fix a whole slew of memory leaks.
31278 - Fix isspace() and friends so they still make Solaris happy
31279 but also so they don't trigger asserts on win32.
31280 - Fix parse_iso_time on platforms without strptime (eg win32).
31281 - win32: tolerate extra "readable" events better.
31282 - win32: when being multithreaded, leave parent fdarray open.
31283 - Make unit tests work on win32.
31286 Changes in version 0.0.9rc6 - 2004-12-06
31287 o Bugfixes on 0.0.9pre:
31288 - Clean up some more integer underflow opportunities (not exploitable
31290 - While hibernating, hup should not regrow our listeners.
31291 - Send an end to the streams we close when we hibernate, rather
31292 than just chopping them off.
31293 - React to eof immediately on non-open edge connections.
31295 o Bugfixes on 0.0.8.1:
31296 - Calculate timeout for waiting for a connected cell from the time
31297 we sent the begin cell, not from the time the stream started. If
31298 it took a long time to establish the circuit, we would time out
31299 right after sending the begin cell.
31300 - Fix router_compare_addr_to_addr_policy: it was not treating a port
31301 of * as always matching, so we were picking reject *:* nodes as
31302 exit nodes too. Oops.
31305 - New circuit building strategy: keep a list of ports that we've
31306 used in the past 6 hours, and always try to have 2 circuits open
31307 or on the way that will handle each such port. Seed us with port
31308 80 so web users won't complain that Tor is "slow to start up".
31309 - Make kill -USR1 dump more useful stats about circuits.
31310 - When warning about retrying or giving up, print the address, so
31311 the user knows which one it's talking about.
31312 - If you haven't used a clean circuit in an hour, throw it away,
31313 just to be on the safe side. (This means after 6 hours a totally
31314 unused Tor client will have no circuits open.)
31317 Changes in version 0.0.9rc5 - 2004-12-01
31318 o Bugfixes on 0.0.8.1:
31319 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
31320 - Let resolve conns retry/expire also, rather than sticking around
31322 - If we are using select, make sure we stay within FD_SETSIZE.
31324 o Bugfixes on 0.0.9pre:
31325 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
31326 but doesn't seem to be currently; thanks to Ilja van Sprundel for
31328 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
31329 instead. Impose minima and maxima for all *Period options; impose
31330 even tighter maxima for fetching if we are a caching dirserver.
31331 Clip rather than rejecting.
31332 - Fetch cached running-routers from servers that serve it (that is,
31333 authdirservers and servers running 0.0.9rc5-cvs or later.)
31336 - Accept *:706 (silc) in default exit policy.
31337 - Implement new versioning format for post 0.1.
31338 - Support "foo.nickname.exit" addresses, to let Alice request the
31339 address "foo" as viewed by exit node "nickname". Based on a patch
31341 - Make tor --version --version dump the cvs Id of every file.
31344 Changes in version 0.0.9rc4 - 2004-11-28
31345 o Bugfixes on 0.0.8.1:
31346 - Make windows sockets actually non-blocking (oops), and handle
31347 win32 socket errors better.
31349 o Bugfixes on 0.0.9rc1:
31350 - Actually catch the -USR2 signal.
31353 Changes in version 0.0.9rc3 - 2004-11-25
31354 o Bugfixes on 0.0.8.1:
31355 - Flush the log file descriptor after we print "Tor opening log file",
31356 so we don't see those messages days later.
31358 o Bugfixes on 0.0.9rc1:
31359 - Make tor-resolve work again.
31360 - Avoid infinite loop in tor-resolve if tor hangs up on it.
31361 - Fix an assert trigger for clients/servers handling resolves.
31364 Changes in version 0.0.9rc2 - 2004-11-24
31365 o Bugfixes on 0.0.9rc1:
31366 - I broke socks5 support while fixing the eof bug.
31367 - Allow unitless bandwidths and intervals; they default to bytes
31369 - New servers don't start out hibernating; they are active until
31370 they run out of bytes, so they have a better estimate of how
31371 long it takes, and so their operators can know they're working.
31374 Changes in version 0.0.9rc1 - 2004-11-23
31375 o Bugfixes on 0.0.8.1:
31376 - Finally fix a bug that's been plaguing us for a year:
31377 With high load, circuit package window was reaching 0. Whenever
31378 we got a circuit-level sendme, we were reading a lot on each
31379 socket, but only writing out a bit. So we would eventually reach
31380 eof. This would be noticed and acted on even when there were still
31381 bytes sitting in the inbuf.
31382 - When poll() is interrupted, we shouldn't believe the revents values.
31384 o Bugfixes on 0.0.9pre6:
31385 - Fix hibernate bug that caused pre6 to be broken.
31386 - Don't keep rephist info for routers that haven't had activity for
31387 24 hours. (This matters now that clients have keys, since we track
31389 - Never call close_temp_logs while validating log options.
31390 - Fix backslash-escaping on tor.sh.in and torctl.in.
31393 - Implement weekly/monthly/daily accounting: now you specify your
31394 hibernation properties by
31395 AccountingMax N bytes|KB|MB|GB|TB
31396 AccountingStart day|week|month [day] HH:MM
31397 Defaults to "month 1 0:00".
31398 - Let bandwidth and interval config options be specified as 5 bytes,
31399 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
31400 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
31401 get back to normal.)
31402 - If your requested entry or exit node has advertised bandwidth 0,
31404 - Be more greedy about filling up relay cells -- we try reading again
31405 once we've processed the stuff we read, in case enough has arrived
31406 to fill the last cell completely.
31407 - Apply NT service patch from Osamu Fujino. Still needs more work.
31410 Changes in version 0.0.9pre6 - 2004-11-15
31411 o Bugfixes on 0.0.8.1:
31412 - Fix assert failure on malformed socks4a requests.
31413 - Use identity comparison, not nickname comparison, to choose which
31414 half of circuit-ID-space each side gets to use. This is needed
31415 because sometimes we think of a router as a nickname, and sometimes
31416 as a hex ID, and we can't predict what the other side will do.
31417 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
31418 write() call will fail and we handle it there.
31419 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
31420 and smartlist_len, which are two major profiling offenders.
31422 o Bugfixes on 0.0.9pre5:
31423 - Fix a bug in read_all that was corrupting config files on windows.
31424 - When we're raising the max number of open file descriptors to
31425 'unlimited', don't log that we just raised it to '-1'.
31426 - Include event code with events, as required by control-spec.txt.
31427 - Don't give a fingerprint when clients do --list-fingerprint:
31428 it's misleading, because it will never be the same again.
31429 - Stop using strlcpy in tor_strndup, since it was slowing us
31431 - Remove warn on startup about missing cached-directory file.
31432 - Make kill -USR1 work again.
31433 - Hibernate if we start tor during the "wait for wakeup-time" phase
31434 of an accounting interval. Log our hibernation plans better.
31435 - Authoritative dirservers now also cache their directory, so they
31436 have it on start-up.
31439 - Fetch running-routers; cache running-routers; compress
31440 running-routers; serve compressed running-routers.z
31441 - Add NSI installer script contributed by J Doe.
31442 - Commit VC6 and VC7 workspace/project files.
31443 - Commit a tor.spec for making RPM files, with help from jbash.
31444 - Add contrib/torctl.in contributed by Glenn Fink.
31445 - Implement the control-spec's SAVECONF command, to write your
31446 configuration to torrc.
31447 - Get cookie authentication for the controller closer to working.
31448 - Include control-spec.txt in the tarball.
31449 - When set_conf changes our server descriptor, upload a new copy.
31450 But don't upload it too often if there are frequent changes.
31451 - Document authentication config in man page, and document signals
31453 - Clean up confusing parts of man page and torrc.sample.
31454 - Make expand_filename handle ~ and ~username.
31455 - Use autoconf to enable largefile support where necessary. Use
31456 ftello where available, since ftell can fail at 2GB.
31457 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
31458 log more informatively.
31459 - Give a slightly more useful output for "tor -h".
31460 - Refuse application socks connections to port 0.
31461 - Check clock skew for verified servers, but allow unverified
31462 servers and clients to have any clock skew.
31463 - Break DirFetchPostPeriod into:
31464 - DirFetchPeriod for fetching full directory,
31465 - StatusFetchPeriod for fetching running-routers,
31466 - DirPostPeriod for posting server descriptor,
31467 - RendPostPeriod for posting hidden service descriptors.
31468 - Make sure the hidden service descriptors are at a random offset
31469 from each other, to hinder linkability.
31472 Changes in version 0.0.9pre5 - 2004-11-09
31473 o Bugfixes on 0.0.9pre4:
31474 - Fix a seg fault in unit tests (doesn't affect main program).
31475 - Fix an assert bug where a hidden service provider would fail if
31476 the first hop of his rendezvous circuit was down.
31477 - Hidden service operators now correctly handle version 1 style
31478 INTRODUCE1 cells (nobody generates them still, so not a critical
31480 - If do_hup fails, actually notice.
31481 - Handle more errnos from accept() without closing the listener.
31482 Some OpenBSD machines were closing their listeners because
31483 they ran out of file descriptors.
31484 - Send resolve cells to exit routers that are running a new
31485 enough version of the resolve code to work right.
31486 - Better handling of winsock includes on non-MSV win32 compilers.
31487 - Some people had wrapped their tor client/server in a script
31488 that would restart it whenever it died. This did not play well
31489 with our "shut down if your version is obsolete" code. Now people
31490 don't fetch a new directory if their local cached version is
31492 - Make our autogen.sh work on ksh as well as bash.
31495 - Hibernation: New config option "AccountingMaxKB" lets you
31496 set how many KBytes per month you want to allow your server to
31497 consume. Rather than spreading those bytes out evenly over the
31498 month, we instead hibernate for some of the month and pop up
31499 at a deterministic time, work until the bytes are consumed, then
31500 hibernate again. Config option "MonthlyAccountingStart" lets you
31501 specify which day of the month your billing cycle starts on.
31502 - Control interface: a separate program can now talk to your
31503 client/server over a socket, and get/set config options, receive
31504 notifications of circuits and streams starting/finishing/dying,
31505 bandwidth used, etc. The next step is to get some GUIs working.
31506 Let us know if you want to help out. See doc/control-spec.txt .
31507 - Ship a contrib/tor-control.py as an example script to interact
31508 with the control port.
31509 - "tor --hash-password zzyxz" will output a salted password for
31510 use in authenticating to the control interface.
31511 - New log format in config:
31512 "Log minsev[-maxsev] stdout|stderr|syslog" or
31513 "Log minsev[-maxsev] file /var/foo"
31516 - DirPolicy config option, to let people reject incoming addresses
31517 from their dirserver.
31518 - "tor --list-fingerprint" will list your identity key fingerprint
31520 - Add "pass" target for RedirectExit, to make it easier to break
31521 out of a sequence of RedirectExit rules.
31522 - Clients now generate a TLS cert too, in preparation for having
31523 them act more like real nodes.
31524 - Ship src/win32/ in the tarball, so people can use it to build.
31525 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
31527 - New "router-status" line in directory, to better bind each verified
31528 nickname to its identity key.
31529 - Deprecate unofficial config option abbreviations, and abbreviations
31530 not on the command line.
31531 - Add a pure-C tor-resolve implementation.
31532 - Use getrlimit and friends to ensure we can reach MaxConn (currently
31533 1024) file descriptors.
31535 o Code security improvements, inspired by Ilja:
31536 - Replace sprintf with snprintf. (I think they were all safe, but
31538 - Replace strcpy/strncpy with strlcpy in more places.
31539 - Avoid strcat; use snprintf or strlcat instead.
31540 - snprintf wrapper with consistent (though not C99) overflow behavior.
31543 Changes in version 0.0.9pre4 - 2004-10-17
31544 o Bugfixes on 0.0.9pre3:
31545 - If the server doesn't specify an exit policy, use the real default
31546 exit policy, not reject *:*.
31547 - Ignore fascistfirewall when uploading/downloading hidden service
31548 descriptors, since we go through Tor for those; and when using
31549 an HttpProxy, since we assume it can reach them all.
31550 - When looking for an authoritative dirserver, use only the ones
31551 configured at boot. Don't bother looking in the directory.
31552 - The rest of the fix for get_default_conf_file() on older win32.
31553 - Make 'Routerfile' config option obsolete.
31556 - New 'MyFamily nick1,...' config option for a server to
31557 specify other servers that shouldn't be used in the same circuit
31558 with it. Only believed if nick1 also specifies us.
31559 - New 'NodeFamily nick1,nick2,...' config option for a client to
31560 specify nodes that it doesn't want to use in the same circuit.
31561 - New 'Redirectexit pattern address:port' config option for a
31562 server to redirect exit connections, e.g. to a local squid.
31565 Changes in version 0.0.9pre3 - 2004-10-13
31566 o Bugfixes on 0.0.8.1:
31567 - Better torrc example lines for dirbindaddress and orbindaddress.
31568 - Improved bounds checking on parsed ints (e.g. config options and
31569 the ones we find in directories.)
31570 - Better handling of size_t vs int, so we're more robust on 64
31572 - Fix the rest of the bug where a newly started OR would appear
31573 as unverified even after we've added his fingerprint and hupped
31575 - Fix a bug from 0.0.7: when read() failed on a stream, we would
31576 close it without sending back an end. So 'connection refused'
31577 would simply be ignored and the user would get no response.
31579 o Bugfixes on 0.0.9pre2:
31580 - Serving the cached-on-disk directory to people is bad. We now
31581 provide no directory until we've fetched a fresh one.
31582 - Workaround for bug on windows where cached-directories get crlf
31584 - Make get_default_conf_file() work on older windows too.
31585 - If we write a *:* exit policy line in the descriptor, don't write
31586 any more exit policy lines.
31589 - Use only 0.0.9pre1 and later servers for resolve cells.
31590 - Make the dirservers file obsolete.
31591 - Include a dir-signing-key token in directories to tell the
31592 parsing entity which key is being used to sign.
31593 - Remove the built-in bulky default dirservers string.
31594 - New config option "Dirserver %s:%d [fingerprint]", which can be
31595 repeated as many times as needed. If no dirservers specified,
31596 default to moria1,moria2,tor26.
31597 - Make moria2 advertise a dirport of 80, so people behind firewalls
31598 will be able to get a directory.
31599 - Http proxy support
31600 - Dirservers translate requests for http://%s:%d/x to /x
31601 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
31602 be routed through this host.
31603 - Clients ask for /tor/x rather than /x for new enough dirservers.
31604 This way we can one day coexist peacefully with apache.
31605 - Clients specify a "Host: %s%d" http header, to be compatible
31606 with more proxies, and so running squid on an exit node can work.
31609 Changes in version 0.0.8.1 - 2004-10-13
31611 - Fix a seg fault that can be triggered remotely for Tor
31612 clients/servers with an open dirport.
31613 - Fix a rare assert trigger, where routerinfos for entries in
31614 our cpath would expire while we're building the path.
31615 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31616 - Fix a rare seg fault for people running hidden services on
31617 intermittent connections.
31618 - Fix a bug in parsing opt keywords with objects.
31619 - Fix a stale pointer assert bug when a stream detaches and
31621 - Fix a string format vulnerability (probably not exploitable)
31622 in reporting stats locally.
31623 - Fix an assert trigger: sometimes launching circuits can fail
31624 immediately, e.g. because too many circuits have failed recently.
31625 - Fix a compile warning on 64 bit platforms.
31628 Changes in version 0.0.9pre2 - 2004-10-03
31630 - Make fetching a cached directory work for 64-bit platforms too.
31631 - Make zlib.h a required header, not an optional header.
31634 Changes in version 0.0.9pre1 - 2004-10-01
31636 - Stop using separate defaults for no-config-file and
31637 empty-config-file. Now you have to explicitly turn off SocksPort,
31638 if you don't want it open.
31639 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31640 - Improve man page to mention more of the 0.0.8 features.
31641 - Fix a rare seg fault for people running hidden services on
31642 intermittent connections.
31643 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
31645 - Fix more dns related bugs: send back resolve_failed and end cells
31646 more reliably when the resolve fails, rather than closing the
31647 circuit and then trying to send the cell. Also attach dummy resolve
31648 connections to a circuit *before* calling dns_resolve(), to fix
31649 a bug where cached answers would never be sent in RESOLVED cells.
31650 - When we run out of disk space, or other log writing error, don't
31651 crash. Just stop logging to that log and continue.
31652 - We were starting to daemonize before we opened our logs, so if
31653 there were any problems opening logs, we would complain to stderr,
31654 which wouldn't work, and then mysteriously exit.
31655 - Fix a rare bug where sometimes a verified OR would connect to us
31656 before he'd uploaded his descriptor, which would cause us to
31657 assign conn->nickname as though he's unverified. Now we look through
31658 the fingerprint list to see if he's there.
31659 - Fix a rare assert trigger, where routerinfos for entries in
31660 our cpath would expire while we're building the path.
31663 - Clients can ask dirservers for /dir.z to get a compressed version
31664 of the directory. Only works for servers running 0.0.9, of course.
31665 - Make clients cache directories and use them to seed their router
31666 lists at startup. This means clients have a datadir again.
31667 - Configuration infrastructure support for warning on obsolete
31669 - Respond to content-encoding headers by trying to uncompress as
31671 - Reply with a deflated directory when a client asks for "dir.z".
31672 We could use allow-encodings instead, but allow-encodings isn't
31673 specified in HTTP 1.0.
31674 - Raise the max dns workers from 50 to 100.
31675 - Discourage people from setting their dirfetchpostperiod more often
31676 than once per minute.
31677 - Protect dirservers from overzealous descriptor uploading -- wait
31678 10 seconds after directory gets dirty, before regenerating.
31681 Changes in version 0.0.8 - 2004-08-25
31682 o Port it to SunOS 5.9 / Athena
31685 Changes in version 0.0.8rc2 - 2004-08-20
31686 o Make it compile on cygwin again.
31687 o When picking unverified routers, skip those with low uptime and/or
31688 low bandwidth, depending on what properties you care about.
31691 Changes in version 0.0.8rc1 - 2004-08-18
31692 o Changes from 0.0.7.3:
31694 - Fix assert triggers: if the other side returns an address 0.0.0.0,
31695 don't put it into the client dns cache.
31696 - If a begin failed due to exit policy, but we believe the IP address
31697 should have been allowed, switch that router to exitpolicy reject *:*
31698 until we get our next directory.
31700 - Clients choose nodes proportional to advertised bandwidth.
31701 - Avoid using nodes with low uptime as introduction points.
31702 - Handle servers with dynamic IP addresses: don't replace
31703 options->Address with the resolved one at startup, and
31704 detect our address right before we make a routerinfo each time.
31705 - 'FascistFirewall' option to pick dirservers and ORs on specific
31706 ports; plus 'FirewallPorts' config option to tell FascistFirewall
31707 which ports are open. (Defaults to 80,443)
31708 - Be more aggressive about trying to make circuits when the network
31709 has changed (e.g. when you unsuspend your laptop).
31710 - Check for time skew on http headers; report date in response to
31712 - If the entrynode config line has only one node, don't pick it as
31714 - Add strict{entry|exit}nodes config options. If set to 1, then
31715 we refuse to build circuits that don't include the specified entry
31717 - OutboundBindAddress config option, to bind to a specific
31718 IP address for outgoing connect()s.
31719 - End truncated log entries (e.g. directories) with "[truncated]".
31721 o Patches to 0.0.8preX:
31723 - Patches to compile and run on win32 again (maybe)?
31724 - Fix crash when looking for ~/.torrc with no $HOME set.
31725 - Fix a race bug in the unit tests.
31726 - Handle verified/unverified name collisions better when new
31727 routerinfo's arrive in a directory.
31728 - Sometimes routers were getting entered into the stats before
31729 we'd assigned their identity_digest. Oops.
31730 - Only pick and establish intro points after we've gotten a
31733 - AllowUnverifiedNodes config option to let circuits choose no-name
31734 routers in entry,middle,exit,introduction,rendezvous positions.
31735 Allow middle and rendezvous positions by default.
31736 - Add a man page for tor-resolve.
31739 Changes in version 0.0.7.3 - 2004-08-12
31740 o Stop dnsworkers from triggering an assert failure when you
31741 ask them to resolve the host "".
31744 Changes in version 0.0.8pre3 - 2004-08-09
31745 o Changes from 0.0.7.2:
31746 - Allow multiple ORs with same nickname in routerlist -- now when
31747 people give us one identity key for a nickname, then later
31748 another, we don't constantly complain until the first expires.
31749 - Remember used bandwidth (both in and out), and publish 15-minute
31750 snapshots for the past day into our descriptor.
31751 - You can now fetch $DIRURL/running-routers to get just the
31752 running-routers line, not the whole descriptor list. (But
31753 clients don't use this yet.)
31754 - When people mistakenly use Tor as an http proxy, point them
31755 at the tor-doc.html rather than the INSTALL.
31756 - Remove our mostly unused -- and broken -- hex_encode()
31757 function. Use base16_encode() instead. (Thanks to Timo Lindfors
31758 for pointing out this bug.)
31759 - Rotate onion keys every 12 hours, not every 2 hours, so we have
31760 fewer problems with people using the wrong key.
31761 - Change the default exit policy to reject the default edonkey,
31762 kazaa, gnutella ports.
31763 - Add replace_file() to util.[ch] to handle win32's rename().
31765 o Changes from 0.0.8preX:
31766 - Fix two bugs in saving onion keys to disk when rotating, so
31767 hopefully we'll get fewer people using old onion keys.
31768 - Fix an assert error that was making SocksPolicy not work.
31769 - Be willing to expire routers that have an open dirport -- it's
31770 just the authoritative dirservers we want to not forget.
31771 - Reject tor-resolve requests for .onion addresses early, so we
31772 don't build a whole rendezvous circuit and then fail.
31773 - When you're warning a server that he's unverified, don't cry
31774 wolf unpredictably.
31775 - Fix a race condition: don't try to extend onto a connection
31776 that's still handshaking.
31777 - For servers in clique mode, require the conn to be open before
31778 you'll choose it for your path.
31779 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
31780 end relay cell, etc.
31781 - Measure bandwidth capacity over the last 24 hours, not just 12
31782 - Bugfix: authoritative dirservers were making and signing a new
31783 directory for each client, rather than reusing the cached one.
31786 Changes in version 0.0.8pre2 - 2004-08-04
31787 o Changes from 0.0.7.2:
31789 - Check directory signature _before_ you decide whether you're
31790 you're running an obsolete version and should exit.
31791 - Check directory signature _before_ you parse the running-routers
31792 list to decide who's running or verified.
31793 - Bugfixes and features:
31794 - Check return value of fclose while writing to disk, so we don't
31795 end up with broken files when servers run out of disk space.
31796 - Log a warning if the user uses an unsafe socks variant, so people
31797 are more likely to learn about privoxy or socat.
31798 - Dirservers now include RFC1123-style dates in the HTTP headers,
31799 which one day we will use to better detect clock skew.
31801 o Changes from 0.0.8pre1:
31802 - Make it compile without warnings again on win32.
31803 - Log a warning if you're running an unverified server, to let you
31804 know you might want to get it verified.
31805 - Only pick a default nickname if you plan to be a server.
31808 Changes in version 0.0.8pre1 - 2004-07-23
31810 - Made our unit tests compile again on OpenBSD 3.5, and tor
31811 itself compile again on OpenBSD on a sparc64.
31812 - We were neglecting milliseconds when logging on win32, so
31813 everything appeared to happen at the beginning of each second.
31815 o Protocol changes:
31816 - 'Extend' relay cell payloads now include the digest of the
31817 intended next hop's identity key. Now we can verify that we're
31818 extending to the right router, and also extend to routers we
31819 hadn't heard of before.
31822 - Tor nodes can now act as relays (with an advertised ORPort)
31823 without being manually verified by the dirserver operators.
31824 - Uploaded descriptors of unverified routers are now accepted
31825 by the dirservers, and included in the directory.
31826 - Verified routers are listed by nickname in the running-routers
31827 list; unverified routers are listed as "$<fingerprint>".
31828 - We now use hash-of-identity-key in most places rather than
31829 nickname or addr:port, for improved security/flexibility.
31830 - To avoid Sybil attacks, paths still use only verified servers.
31831 But now we have a chance to play around with hybrid approaches.
31832 - Nodes track bandwidth usage to estimate capacity (not used yet).
31833 - ClientOnly option for nodes that never want to become servers.
31834 - Directory caching.
31835 - "AuthoritativeDir 1" option for the official dirservers.
31836 - Now other nodes (clients and servers) will cache the latest
31837 directory they've pulled down.
31838 - They can enable their DirPort to serve it to others.
31839 - Clients will pull down a directory from any node with an open
31840 DirPort, and check the signature/timestamp correctly.
31841 - Authoritative dirservers now fetch directories from other
31842 authdirservers, to stay better synced.
31843 - Running-routers list tells who's down also, along with noting
31844 if they're verified (listed by nickname) or unverified (listed
31846 - Allow dirservers to serve running-router list separately.
31847 This isn't used yet.
31848 - ORs connect-on-demand to other ORs
31849 - If you get an extend cell to an OR you're not connected to,
31850 connect, handshake, and forward the create cell.
31851 - The authoritative dirservers stay connected to everybody,
31852 and everybody stays connected to 0.0.7 servers, but otherwise
31853 clients/servers expire unused connections after 5 minutes.
31854 - When servers get a sigint, they delay 30 seconds (refusing new
31855 connections) then exit. A second sigint causes immediate exit.
31856 - File and name management:
31857 - Look for .torrc if no CONFDIR "torrc" is found.
31858 - If no datadir is defined, then choose, make, and secure ~/.tor
31860 - If torrc not found, exitpolicy reject *:*.
31861 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
31862 - If no nickname is defined, derive default from hostname.
31863 - Rename secret key files, e.g. identity.key -> secret_id_key,
31864 to discourage people from mailing their identity key to tor-ops.
31865 - Refuse to build a circuit before the directory has arrived --
31866 it won't work anyway, since you won't know the right onion keys
31868 - Try other dirservers immediately if the one you try is down. This
31869 should tolerate down dirservers better now.
31870 - Parse tor version numbers so we can do an is-newer-than check
31871 rather than an is-in-the-list check.
31872 - New socks command 'resolve', to let us shim gethostbyname()
31874 - A 'tor_resolve' script to access the socks resolve functionality.
31875 - A new socks-extensions.txt doc file to describe our
31876 interpretation and extensions to the socks protocols.
31877 - Add a ContactInfo option, which gets published in descriptor.
31878 - Publish OR uptime in descriptor (and thus in directory) too.
31879 - Write tor version at the top of each log file
31880 - New docs in the tarball:
31882 - Document that you should proxy your SSL traffic too.
31885 Changes in version 0.0.7.2 - 2004-07-07
31886 o A better fix for the 0.0.0.0 problem, that will hopefully
31887 eliminate the remaining related assertion failures.
31890 Changes in version 0.0.7.1 - 2004-07-04
31891 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
31892 since internally we use 0.0.0.0 to signify "not yet resolved".
31895 Changes in version 0.0.7 - 2004-06-07
31896 o Updated the man page to reflect the new features.
31899 Changes in version 0.0.7rc2 - 2004-06-06
31900 o Changes from 0.0.7rc1:
31901 - Make it build on Win32 again.
31902 o Changes from 0.0.6.2:
31903 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
31907 Changes in version 0.0.7rc1 - 2004-06-02
31909 - On sighup, we were adding another log without removing the first
31910 one. So log messages would get duplicated n times for n sighups.
31911 - Several cases of using a connection after we'd freed it. The
31912 problem was that connections that are pending resolve are in both
31913 the pending_resolve tree, and also the circuit's resolving_streams
31914 list. When you want to remove one, you must remove it from both.
31915 - Fix a double-mark-for-close where an end cell arrived for a
31916 resolving stream, and then the resolve failed.
31917 - Check directory signatures based on name of signer, not on whom
31918 we got the directory from. This will let us cache directories more
31921 - Crank up some of our constants to handle more users.
31924 Changes in version 0.0.7pre1 - 2004-06-02
31925 o Fixes for crashes and other obnoxious bugs:
31926 - Fix an epipe bug: sometimes when directory connections failed
31927 to connect, we would give them a chance to flush before closing
31929 - When we detached from a circuit because of resolvefailed, we
31930 would immediately try the same circuit twice more, and then
31931 give up on the resolve thinking we'd tried three different
31933 - Limit the number of intro circuits we'll attempt to build for a
31934 hidden service per 15-minute period.
31935 - Check recommended-software string *early*, before actually parsing
31936 the directory. Thus we can detect an obsolete version and exit,
31937 even if the new directory format doesn't parse.
31938 o Fixes for security bugs:
31939 - Remember which nodes are dirservers when you startup, and if a
31940 random OR enables his dirport, don't automatically assume he's
31941 a trusted dirserver.
31943 - Directory connections were asking the wrong poll socket to
31944 start writing, and not asking themselves to start writing.
31945 - When we detached from a circuit because we sent a begin but
31946 didn't get a connected, we would use it again the first time;
31947 but after that we would correctly switch to a different one.
31948 - Stop warning when the first onion decrypt attempt fails; they
31949 will sometimes legitimately fail now that we rotate keys.
31950 - Override unaligned-access-ok check when $host_cpu is ia64 or
31951 arm. Apparently they allow it but the kernel whines.
31952 - Dirservers try to reconnect periodically too, in case connections
31954 - Fix some memory leaks in directory servers.
31955 - Allow backslash in Win32 filenames.
31956 - Made Tor build complain-free on FreeBSD, hopefully without
31957 breaking other BSD builds. We'll see.
31959 - Doxygen markup on all functions and global variables.
31960 - Make directory functions update routerlist, not replace it. So
31961 now directory disagreements are not so critical a problem.
31962 - Remove the upper limit on number of descriptors in a dirserver's
31963 directory (not that we were anywhere close).
31964 - Allow multiple logfiles at different severity ranges.
31965 - Allow *BindAddress to specify ":port" rather than setting *Port
31966 separately. Allow multiple instances of each BindAddress config
31967 option, so you can bind to multiple interfaces if you want.
31968 - Allow multiple exit policy lines, which are processed in order.
31969 Now we don't need that huge line with all the commas in it.
31970 - Enable accept/reject policies on SOCKS connections, so you can bind
31971 to 0.0.0.0 but still control who can use your OP.
31974 Changes in version 0.0.6.2 - 2004-05-16
31975 o Our integrity-checking digest was checking only the most recent cell,
31976 not the previous cells like we'd thought.
31977 Thanks to Stefan Mark for finding the flaw!
31980 Changes in version 0.0.6.1 - 2004-05-06
31981 o Fix two bugs in our AES counter-mode implementation (this affected
31982 onion-level stream encryption, but not TLS-level). It turns
31983 out we were doing something much more akin to a 16-character
31984 polyalphabetic cipher. Oops.
31985 Thanks to Stefan Mark for finding the flaw!
31986 o Retire moria3 as a directory server, and add tor26 as a directory
31990 Changes in version 0.0.6 - 2004-05-02
31991 [version bump only]
31994 Changes in version 0.0.6rc4 - 2004-05-01
31995 o Update the built-in dirservers list to use the new directory format
31996 o Fix a rare seg fault: if a node offering a hidden service attempts
31997 to build a circuit to Alice's rendezvous point and fails before it
31998 reaches the last hop, it retries with a different circuit, but
32000 o Handle windows socket errors correctly.
32003 Changes in version 0.0.6rc3 - 2004-04-28
32004 o Don't expire non-general excess circuits (if we had enough
32005 circuits open, we were expiring rendezvous circuits -- even
32006 when they had a stream attached. oops.)
32007 o Fetch randomness from /dev/urandom better (not via fopen/fread)
32008 o Better debugging for tls errors
32009 o Some versions of openssl have an SSL_pending function that erroneously
32010 returns bytes when there is a non-application record pending.
32011 o Set Content-Type on the directory and hidserv descriptor.
32012 o Remove IVs from cipher code, since AES-ctr has none.
32013 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
32014 o We were using an array of length zero in a few places.
32015 o win32's gethostbyname can't resolve an IP to an IP.
32016 o win32's close can't close a socket.
32019 Changes in version 0.0.6rc2 - 2004-04-26
32020 o Fix a bug where we were closing tls connections intermittently.
32021 It turns out openssl keeps its errors around -- so if an error
32022 happens, and you don't ask about it, and then another openssl
32023 operation happens and succeeds, and you ask if there was an error,
32024 it tells you about the first error. Fun fun.
32025 o Fix a bug that's been lurking since 27 may 03 (!)
32026 When passing back a destroy cell, we would use the wrong circ id.
32027 'Mostly harmless', but still worth fixing.
32028 o Since we don't support truncateds much, don't bother sending them;
32029 just close the circ.
32030 o check for <machine/limits.h> so we build on NetBSD again (I hope).
32031 o don't crash if a conn that sent a begin has suddenly lost its circuit
32032 (this was quite rare).
32035 Changes in version 0.0.6rc1 - 2004-04-25
32036 o We now rotate link (tls context) keys and onion keys.
32037 o CREATE cells now include oaep padding, so you can tell
32038 if you decrypted them correctly.
32039 o Add bandwidthburst to server descriptor.
32040 o Directories now say which dirserver signed them.
32041 o Use a tor_assert macro that logs failed assertions too.
32044 Changes in version 0.0.6pre5 - 2004-04-18
32045 o changes from 0.0.6pre4:
32046 - make tor build on broken freebsd 5.2 installs
32047 - fix a failed assert when you try an intro point, get a nack, and try
32048 a second one and it works.
32049 - when alice uses a port that the hidden service doesn't accept,
32050 it now sends back an end cell (denied by exit policy). otherwise
32051 alice would just have to wait to time out.
32052 - fix another rare bug: when we had tried all the intro
32053 points for a hidden service, we fetched the descriptor
32054 again, but we left our introcirc thinking it had already
32055 sent an intro, so it kept waiting for a response...
32056 - bugfix: when you sleep your hidden-service laptop, as soon
32057 as it wakes up it tries to upload a service descriptor, but
32058 socketpair fails for some reason (localhost not up yet?).
32059 now we simply give up on that upload, and we'll try again later.
32060 i'd still like to find the bug though.
32061 - if an intro circ waiting for an ack dies before getting one, then
32063 - we were reusing stale service descriptors and refetching usable
32067 Changes in version 0.0.6pre4 - 2004-04-14
32068 o changes from 0.0.6pre3:
32069 - when bob fails to connect to the rendezvous point, and his
32070 circ didn't fail because of the rendezvous point itself, then
32071 he retries a couple of times
32072 - we expire introduction and rendezvous circs more thoroughly
32073 (sometimes they were hanging around forever)
32074 - we expire unattached rendezvous streams that have been around
32075 too long (they were sticking around forever).
32076 - fix a measly fencepost error that was crashing everybody with
32080 Changes in version 0.0.6pre3 - 2004-04-14
32081 o changes from 0.0.6pre2:
32082 - make hup work again
32083 - fix some memory leaks for dirservers
32084 - allow more skew in rendezvous descriptor timestamps, to help
32085 handle people like blanu who don't know what time it is
32086 - normal circs are 3 hops, but some rend/intro circs are 4, if
32087 the initiator doesn't get to choose the last hop
32088 - send acks for introductions, so alice can know whether to try
32090 - bob publishes intro points more correctly
32091 o changes from 0.0.5:
32092 - fix an assert trigger that's been plaguing us since the days
32093 of 0.0.2prexx (thanks weasel!)
32094 - retry stream correctly when we fail to connect because of
32095 exit-policy-reject (should try another) or can't-resolve-address
32096 (also should try another, because dns on random internet servers
32098 - when we hup a dirserver and we've *removed* a server from the
32099 approved-routers list, now we remove that server from the
32100 in-memory directories too
32103 Changes in version 0.0.6pre2 - 2004-04-08
32104 o We fixed our base32 implementation. Now it works on all architectures.
32107 Changes in version 0.0.6pre1 - 2004-04-08
32109 - Hidden services and rendezvous points are implemented. Go to
32110 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
32111 hidden services. (This only works via a socks4a proxy such as
32112 Privoxy, and currently it's quite slow.)
32115 Changes in version 0.0.5 - 2004-03-30
32116 [version bump only]
32119 Changes in version 0.0.5rc3 - 2004-03-29
32120 o Install torrc as torrc.sample -- we no longer clobber your
32122 o Re-enable recommendedversion checking (we broke it in rc2, oops)
32123 o Add in a 'notice' log level for things the operator should hear
32124 but that aren't warnings
32127 Changes in version 0.0.5rc2 - 2004-03-29
32128 o Hold socks connection open until reply is flushed (if possible)
32129 o Make exit nodes resolve IPs to IPs immediately, rather than asking
32130 the dns farm to do it.
32131 o Fix c99 aliasing warnings in rephist.c
32132 o Don't include server descriptors that are older than 24 hours in the
32134 o Give socks 'reject' replies their whole 15s to attempt to flush,
32135 rather than seeing the 60s timeout and assuming the flush had failed.
32136 o Clean automake droppings from the cvs repository
32139 Changes in version 0.0.5rc1 - 2004-03-28
32140 o Fix mangled-state bug in directory fetching (was causing sigpipes).
32141 o Only build circuits after we've fetched the directory: clients were
32142 using only the directory servers before they'd fetched a directory.
32143 This also means longer startup time; so it goes.
32144 o Fix an assert trigger where an OP would fail to handshake, and we'd
32145 expect it to have a nickname.
32146 o Work around a tsocks bug: do a socks reject when AP connection dies
32147 early, else tsocks goes into an infinite loop.
32150 Changes in version 0.0.4 - 2004-03-26
32151 o When connecting to a dirserver or OR and the network is down,
32155 Changes in version 0.0.3 - 2004-03-26
32156 o Warn and fail if server chose a nickname with illegal characters
32157 o Port to Solaris and Sparc:
32158 - include missing header fcntl.h
32159 - have autoconf find -lsocket -lnsl automatically
32160 - deal with hardware word alignment
32161 - make uname() work (solaris has a different return convention)
32162 - switch from using signal() to sigaction()
32163 o Preliminary work on reputation system:
32164 - Keep statistics on success/fail of connect attempts; they're published
32165 by kill -USR1 currently.
32166 - Add a RunTesting option to try to learn link state by creating test
32167 circuits, even when SocksPort is off.
32168 - Remove unused open circuits when there are too many.
32171 Changes in version 0.0.2 - 2004-03-19
32172 - Include strlcpy and strlcat for safer string ops
32173 - define INADDR_NONE so we compile (but still not run) on solaris
32176 Changes in version 0.0.2pre27 - 2004-03-14
32178 - Allow internal tor networks (we were rejecting internal IPs,
32179 now we allow them if they're set explicitly).
32180 - And fix a few endian issues.
32183 Changes in version 0.0.2pre26 - 2004-03-14
32185 - If a stream times out after 15s without a connected cell, don't
32186 try that circuit again: try a new one.
32187 - Retry streams at most 4 times. Then give up.
32188 - When a dirserver gets a descriptor from an unknown router, it
32189 logs its fingerprint (so the dirserver operator can choose to
32190 accept it even without mail from the server operator).
32191 - Inform unapproved servers when we reject their descriptors.
32192 - Make tor build on Windows again. It works as a client, who knows
32194 - Clearer instructions in the torrc for how to set up a server.
32195 - Be more efficient about reading fd's when our global token bucket
32196 (used for rate limiting) becomes empty.
32198 - Stop asserting that computers always go forward in time. It's
32200 - When we sent a cell (e.g. destroy) and then marked an OR connection
32201 expired, we might close it before finishing a flush if the other
32202 side isn't reading right then.
32203 - Don't allow dirservers to start if they haven't defined
32204 RecommendedVersions
32205 - We were caching transient dns failures. Oops.
32206 - Prevent servers from publishing an internal IP as their address.
32207 - Address a strcat vulnerability in circuit.c
32210 Changes in version 0.0.2pre25 - 2004-03-04
32212 - Put the OR's IP in its router descriptor, not its fqdn. That way
32213 we'll stop being stalled by gethostbyname for nodes with flaky dns,
32216 - If the user typed in an address that didn't resolve, the server
32220 Changes in version 0.0.2pre24 - 2004-03-03
32222 - Fix an assertion failure in dns.c, where we were trying to dequeue
32223 a pending dns resolve even if it wasn't pending
32224 - Fix a spurious socks5 warning about still trying to write after the
32225 connection is finished.
32226 - Hold certain marked_for_close connections open until they're finished
32227 flushing, rather than losing bytes by closing them too early.
32228 - Correctly report the reason for ending a stream
32229 - Remove some duplicate calls to connection_mark_for_close
32230 - Put switch_id and start_daemon earlier in the boot sequence, so it
32231 will actually try to chdir() to options.DataDirectory
32232 - Make 'make test' exit(1) if a test fails; fix some unit tests
32233 - Make tor fail when you use a config option it doesn't know about,
32234 rather than warn and continue.
32235 - Make --version work
32236 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
32239 Changes in version 0.0.2pre23 - 2004-02-29
32241 - Print a statement when the first circ is finished, so the user
32242 knows it's working.
32243 - If a relay cell is unrecognized at the end of the circuit,
32244 send back a destroy. (So attacks to mutate cells are more
32246 - New config option 'excludenodes' to avoid certain nodes for circuits.
32247 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
32248 so you can collect coredumps there.
32250 - Fix a bug in tls flushing where sometimes data got wedged and
32251 didn't flush until more data got sent. Hopefully this bug was
32252 a big factor in the random delays we were seeing.
32253 - Make 'connected' cells include the resolved IP, so the client
32254 dns cache actually gets populated.
32255 - Disallow changing from ORPort=0 to ORPort>0 on hup.
32256 - When we time-out on a stream and detach from the circuit, send an
32257 end cell down it first.
32258 - Only warn about an unknown router (in exitnodes, entrynodes,
32259 excludenodes) after we've fetched a directory.
32262 Changes in version 0.0.2pre22 - 2004-02-26
32264 - Servers publish less revealing uname information in descriptors.
32265 - More memory tracking and assertions, to crash more usefully when
32267 - If the default torrc isn't there, just use some default defaults.
32268 Plus provide an internal dirservers file if they don't have one.
32269 - When the user tries to use Tor as an http proxy, give them an http
32270 501 failure explaining that we're a socks proxy.
32271 - Dump a new router.desc on hup, to help confused people who change
32272 their exit policies and then wonder why router.desc doesn't reflect
32274 - Clean up the generic tor.sh init script that we ship with.
32276 - If the exit stream is pending on the resolve, and a destroy arrives,
32277 then the stream wasn't getting removed from the pending list. I
32278 think this was the one causing recent server crashes.
32279 - Use a more robust poll on OSX 10.3, since their poll is flaky.
32280 - When it couldn't resolve any dirservers, it was useless from then on.
32281 Now it reloads the RouterFile (or default dirservers) if it has no
32283 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
32284 many users don't even *have* a /usr/local/sbin/.
32287 Changes in version 0.0.2pre21 - 2004-02-18
32289 - There's a ChangeLog file that actually reflects the changelog.
32290 - There's a 'torify' wrapper script, with an accompanying
32291 tor-tsocks.conf, that simplifies the process of using tsocks for
32292 tor. It even has a man page.
32293 - The tor binary gets installed to sbin rather than bin now.
32294 - Retry streams where the connected cell hasn't arrived in 15 seconds
32295 - Clean up exit policy handling -- get the default out of the torrc,
32296 so we can update it without forcing each server operator to fix
32298 - Allow imaps and pop3s in default exit policy
32300 - Prevent picking middleman nodes as the last node in the circuit
32303 Changes in version 0.0.2pre20 - 2004-01-30
32305 - We now have a deb package, and it's in debian unstable. Go to
32306 it, apt-getters. :)
32307 - I've split the TotalBandwidth option into BandwidthRate (how many
32308 bytes per second you want to allow, long-term) and
32309 BandwidthBurst (how many bytes you will allow at once before the cap
32310 kicks in). This better token bucket approach lets you, say, set
32311 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
32312 performance while not exceeding your monthly bandwidth quota.
32313 - Push out a tls record's worth of data once you've got it, rather
32314 than waiting until you've read everything waiting to be read. This
32315 may improve performance by pipelining better. We'll see.
32316 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
32317 from failed circuits (if they haven't been connected yet) and attach
32319 - Expire old streams that haven't managed to connect. Some day we'll
32320 have them reattach to new circuits instead.
32323 - Fix several memory leaks that were causing servers to become bloated
32325 - Fix a few very rare assert triggers. A few more remain.
32326 - Setuid to User _before_ complaining about running as root.
32329 Changes in version 0.0.2pre19 - 2004-01-07
32331 - Fix deadlock condition in dns farm. We were telling a child to die by
32332 closing the parent's file descriptor to him. But newer children were
32333 inheriting the open file descriptor from the parent, and since they
32334 weren't closing it, the socket never closed, so the child never read
32335 eof, so he never knew to exit. Similarly, dns workers were holding
32336 open other sockets, leading to all sorts of chaos.
32337 - New cleaner daemon() code for forking and backgrounding.
32338 - If you log to a file, it now prints an entry at the top of the
32339 logfile so you know it's working.
32340 - The onionskin challenge length was 30 bytes longer than necessary.
32341 - Started to patch up the spec so it's not quite so out of date.
32344 Changes in version 0.0.2pre18 - 2004-01-02
32346 - Fix endian issues with the 'integrity' field in the relay header.
32347 - Fix a potential bug where connections in state
32348 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
32351 Changes in version 0.0.2pre17 - 2003-12-30
32353 - Made --debuglogfile (or any second log file, actually) work.
32354 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
32355 adversary could force us into an infinite loop.
32358 - Each onionskin handshake now includes a hash of the computed key,
32359 to prove the server's identity and help perfect forward secrecy.
32360 - Changed cell size from 256 to 512 bytes (working toward compatibility
32362 - Changed cell length to 2 bytes, and moved it to the relay header.
32363 - Implemented end-to-end integrity checking for the payloads of
32365 - Separated streamid from 'recognized' (otherwise circuits will get
32366 messed up when we try to have streams exit from the middle). We
32367 use the integrity-checking to confirm that a cell is addressed to
32369 - Randomize the initial circid and streamid values, so an adversary who
32370 breaks into a node can't learn how many circuits or streams have
32374 Changes in version 0.0.2pre16 - 2003-12-14
32376 - Fixed a bug that made HUP trigger an assert
32377 - Fixed a bug where a circuit that immediately failed wasn't being
32378 counted as a failed circuit in counting retries.
32381 - Now we close the circuit when we get a truncated cell: otherwise we're
32382 open to an anonymity attack where a bad node in the path truncates
32383 the circuit and then we open streams at him.
32384 - Add port ranges to exit policies
32385 - Add a conservative default exit policy
32386 - Warn if you're running tor as root
32387 - on HUP, retry OR connections and close/rebind listeners
32388 - options.EntryNodes: try these nodes first when picking the first node
32389 - options.ExitNodes: if your best choices happen to include any of
32390 your preferred exit nodes, you choose among just those preferred
32392 - options.ExcludedNodes: nodes that are never picked in path building
32395 Changes in version 0.0.2pre15 - 2003-12-03
32396 o Robustness and bugfixes:
32397 - Sometimes clients would cache incorrect DNS resolves, which would
32398 really screw things up.
32399 - An OP that goes offline would slowly leak all its sockets and stop
32401 - A wide variety of bugfixes in exit node selection, exit policy
32402 handling, and processing pending streams when a new circuit is
32404 - Pick nodes for a path only from those the directory says are up
32405 - Choose randomly from all running dirservers, not always the first one
32406 - Increase allowed http header size for directory fetch.
32407 - Stop writing to stderr (if we're daemonized it will be closed).
32408 - Enable -g always, so cores will be more useful to me.
32409 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
32412 - Wrote a man page. It lists commonly used options.
32415 - Change default loglevel to warn.
32416 - Make PidFile default to null rather than littering in your CWD.
32417 - OnionRouter config option is now obsolete. Instead it just checks
32419 - Moved to a single unified torrc file for both clients and servers.
32422 Changes in version 0.0.2pre14 - 2003-11-29
32423 o Robustness and bugfixes:
32424 - Force the admin to make the DataDirectory himself
32425 - to get ownership/permissions right
32426 - so clients no longer make a DataDirectory and then never use it
32427 - fix bug where a client who was offline for 45 minutes would never
32428 pull down a directory again
32429 - fix (or at least hide really well) the dns assert bug that was
32430 causing server crashes
32431 - warnings and improved robustness wrt clockskew for certs
32432 - use the native daemon(3) to daemonize, when available
32433 - exit if bind() fails
32434 - exit if neither socksport nor orport is defined
32435 - include our own tor_timegm (Win32 doesn't have its own)
32436 - bugfix for win32 with lots of connections
32437 - fix minor bias in PRNG
32438 - make dirserver more robust to corrupt cached directory
32441 - Wrote the design document (woo)
32443 o Circuit building and exit policies:
32444 - Circuits no longer try to use nodes that the directory has told them
32446 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
32447 bitcounts (18.0.0.0/8).
32448 - Make AP connections standby for a circuit if no suitable circuit
32449 exists, rather than failing
32450 - Circuits choose exit node based on addr/port, exit policies, and
32451 which AP connections are standing by
32452 - Bump min pathlen from 2 to 3
32453 - Relay end cells have a payload to describe why the stream ended.
32454 - If the stream failed because of exit policy, try again with a new
32456 - Clients have a dns cache to remember resolved addresses.
32457 - Notice more quickly when we have no working circuits
32460 - APPort is now called SocksPort
32461 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
32463 - RecommendedVersions is now a config variable rather than
32464 hardcoded (for dirservers)
32465 - Reloads config on HUP
32466 - Usage info on -h or --help
32467 - If you set User and Group config vars, it'll setu/gid to them.
32470 Changes in version 0.0.2pre13 - 2003-10-19
32471 o General stability:
32472 - SSL_write no longer fails when it returns WANTWRITE and the number
32473 of bytes in the buf has changed by the next SSL_write call.
32474 - Fix segfault fetching directory when network is down
32475 - Fix a variety of minor memory leaks
32476 - Dirservers reload the fingerprints file on HUP, so I don't have
32477 to take down the network when I approve a new router
32478 - Default server config file has explicit Address line to specify fqdn
32481 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
32482 - Make listener connections not ever alloc bufs
32484 o Autoconf improvements:
32485 - don't clobber an external CFLAGS in ./configure
32486 - Make install now works
32487 - create var/lib/tor on make install
32488 - autocreate a tor.sh initscript to help distribs
32489 - autocreate the torrc and sample-server-torrc with correct paths
32491 o Log files and Daemonizing now work:
32492 - If --DebugLogFile is specified, log to it at -l debug
32493 - If --LogFile is specified, use it instead of commandline
32494 - If --RunAsDaemon is set, tor forks and backgrounds on startup